Crocus DXC - Route 66 Communications

Crocus DXC - Route 66 Communications Crocus DXC - Route 66 Communications

route66com.com
from route66com.com More from this publisher
11.07.2015 Views

Crocus DXCCrocus DXCUSER and REFERENCE MANUALVersion: 1.4 188913Telindus Technical Publications – Geldenaaksebaan 335 ⋅ B-3001 Leuven ⋅ Belgium – tel. +32 16 382011

<strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>USER and REFERENCE MANUALVersion: 1.4 188913Telindus Technical Publications – Geldenaaksebaan 335 ⋅ B-3001 Leuven ⋅ Belgium – tel. +32 16 382011


Human Services Department emphasized those carve-outs in newly issued regulations Wednesday." Notably, "HHS clarified that themandate doesn't apply to people who are eligible for Medicaid but live in states that don't take part in the law's Medicaid expansion."In a separate report, The Hill (1/30, Baker) "Healthwatch" blog writes, "The Obama administration took new steps Wednesdaytoward implementing the individual mandate in its signature healthcare law, downplaying the scope of the unpopular provision by stressingrules that allow exemptions from the requirement to purchase insurance." In announcing the exemptions, HHS said, "A principle inimplementing the individual shared responsibility provision is that the shared responsibility payment should not apply to any taxpayer forwhom coverage is unaffordable, who has other good cause for going without coverage, or who goes without coverage for only a shorttime."Modern Healthcare (1/31, Daly, Subscription Publication) reports that in a fact sheet accompanying the regulations, CMS said,"Both agencies' proposed regulations include rules that will ease implementation and help to ensure that the payment applies only to thelimited group of taxpayers who choose to spend a substantial period of time without coverage despite having ready access to affordablecoverage."From NAHUAccess NAHU's latest information on PPACA, including a timeline, through our Compliance Corner by clickinghere. This section of the website is constantly being updated, so be sure to check in often!| |Legislation and PolicyBill Would Eliminate Part Of ACA.The Washington Times (1/31, Howell) reports that Sens. Tom Coburn and Claire McCaskill on Wednesday announced "a bill todissolve part of President Obama's health care law that critics say skews some of the benefits to hospitals in Massachusetts, at theexpense of other states." The bill "would eliminate a money-shifting 'gimmick' that resulted from the use of rural hospitals as the wage floorfor Medicare reimbursements - a system that went askew because the Bay State's benchmark hospital happens to be on Nantucket, thewell-to-do island off the Atlantic Coast."Unions Push White House For Healthcare Subsidies.In a front-page article, the Wall Street Journal (1/31, A1, Adamy, Trottman, Subscription Publication) reports on the concerns somelabor unions have with the Affordable Care Act. Union leaders worry that some of its requirements will increase healthcare costs, giving anedge to smaller, non-unionized contractors. Because these contractors will likely have fewer than 50 employees, they will also not have topay a penalty for not providing health insurance, thus being able to provide a workforce at a lower cost. Unions are asking the ObamaAdministration to provide Federal subsidies to their lowest-paid members while also staying on their plans. The Administration is wary ofupsetting unions, a stout ally, but acknowledges the subsidies will also raise the cost of the new law..Medicare Adjusting Reimbursement For Dialysis.The Washington Post (1/31, Whoriskey) reports, "The Medicare system is recalculating how much it will reimburse hospitals andclinics for the drugs used to treat dialysis patients after federal auditors found recently that the program could save as much as $880million annually." An August analysis by the Post "showed that the government was overspending by hundreds of millions for just onegroup of those drugs." This occurred because the government was reimbursing for a dose that was higher than most people received.Dennis Cotter, president of the Medical Technology and Practice Patterns Institute, a research group, who called for price changes in2011, said, "It's good that Medicare is finally going to set a new, more accurate price. It's unfortunate that they could have done this twoyears ago. This has so far cost taxpayers more than $1.6 billion."Growing Healthcare Costs Straining Texas Budget.The AP (1/31, Tomlinson) reports, "Texas will use 'all the money that there is available to spend' in the state budget just paying thehealth care costs of the growing number of poor, disabled and elderly unless dramatic changes are made to the Medicaid system, the


Preface<strong>Crocus</strong> <strong>DXC</strong>Organisation of this manualThis manual contains three main parts.PartUser manualReference manualAnnexesThis part …shows you how to install and connect the <strong>Crocus</strong> <strong>DXC</strong>.gives more detailed information on the <strong>Crocus</strong> <strong>DXC</strong>. It contains a completedescription for lookup purposes.gives additional information.The following table gives an overview of the chapters in the user manual.ChapterThis chapter …1 introduces the <strong>Crocus</strong> <strong>DXC</strong>.2 explains how to install and connect the <strong>Crocus</strong> <strong>DXC</strong>. It also describes the front panelLED indicators.3 locates the DIP switches and straps of the <strong>Crocus</strong> <strong>DXC</strong> on the motherboard. It alsoexplains their function.4 introduces the Telindus Maintenance Application (TMA). It also shows how to start aTMA session on the <strong>Crocus</strong> <strong>DXC</strong>. Furthermore, it introduces the management attributesof the <strong>Crocus</strong> <strong>DXC</strong>.5 teaches you the basics to configure the <strong>Crocus</strong> <strong>DXC</strong>, in a step-by-step manner.The following table gives an overview of the chapters in the reference manual.ChapterThis chapter …6, 7, 8, 9 describes the configuration, status, performance and alarm attributes, respectively.10 displays and labels the different elements of the Telindus Maintenance Applicationsubsystem picture.11 gives a firmware download procedure.12 summarises the technical specifications of the <strong>Crocus</strong> <strong>DXC</strong>.The following table gives an overview of the annexes.AnnexAnnex AThis annex …shows ordering information.iv


<strong>Crocus</strong> <strong>DXC</strong>PrefaceConventions used in this manualTypographical conventionsThe following typographical conventions are used in this manual.The format …NormalItalicComputerComputer BoldNarrowBlueBlue underlinedis used to indicate …normal text.• new or emphasised words• file names and directory paths, e.g. C:\Program Files\TMA\bin\Tma.execomputer output and code examples, e.g. NOK,1,1,Invalid command.text you have to enter at the prompt, e.g. Get sysName.objects and attributes in the containment tree of a device when they arementioned in the normal text. I.e. when they are not a part of computer input oroutput.references to other parts in the manual, e.g. refer to Chapter xx - Technicalspecifications.a hyperlink to a web site, e.g. www.telindus.comIconsThe following icons are used throughout the manual.Icon Name DescriptionRemarkUseful information or tips.CautionWarningRead the text that follows carefully in order to avoid damage to thedevice.Read the text that follows carefully in order to avoid injury.DIP switchBasic TMAparameterAdvanced TMAparameterActionA configuration attribute of the <strong>Crocus</strong> <strong>DXC</strong> which can be set with theDIP switches.A basic attribute of the <strong>Crocus</strong> <strong>DXC</strong> which can be set with the TelindusMaintenance Application (TMA).An advanced attribute of the <strong>Crocus</strong> <strong>DXC</strong> which can be set with theTelindus Maintenance Application (TMA).An action which can be executed on the <strong>Crocus</strong> <strong>DXC</strong> with the TelindusMaintenance Application (TMA).v


Preface<strong>Crocus</strong> <strong>DXC</strong>Firmware versionThis manual describes the features, containment tree and attributes of the <strong>Crocus</strong> <strong>DXC</strong> applicationsoftware version T2741/00900.AudienceThis manual is intended for computer-literate people, who have a working knowledge of computing andnetworking principles.Related documentationThis manual describes the hardware and features of the <strong>Crocus</strong> <strong>DXC</strong>. This manual also often refers tomanuals of other Telindus products. As the manual of this product, also these manuals can be found onthe Telindus Access Products distribution CD that is delivered with the Telindus products. This CD notonly contains all the Telindus product manuals, but also the free maintenance tool TMA and the firmwareof the Telindus devices.Your feedbackYour satisfaction about this purchase is an extremely important priority to all of us at Telindus.Accordingly, all electronic, functional and cosmetic aspects of this new unit have been carefully andthoroughly tested and inspected. If any fault is found with this unit or should you have any other qualityrelatedcomment concerning this delivery, please submit the Quality Comment Form on our web page athttp://www.telindusproducts.com/quality.vi


Table of contents<strong>Crocus</strong> <strong>DXC</strong>Table of contents (continued)Reference manual .................................................................................... 596 Configuration attributes........................................................................................616.1 Configuration attribute overview .................................................................................626.2 General configuration attributes .................................................................................636.3 Cross connect configuration attributes .......................................................................716.4 E1 interface configuration attributes ...........................................................................726.5 Management configuration attributes .........................................................................747 Status attributes ....................................................................................................757.1 Status attribute overview ............................................................................................767.2 General status attributes ............................................................................................777.3 Cross connect status attributes ..................................................................................807.4 E1 interface status attributes ......................................................................................827.5 Management status attributes ....................................................................................847.6 Operating system status attributes .............................................................................858 Performance attributes .........................................................................................868.1 Performance attribute overview..................................................................................878.2 Introducing the performance attributes.......................................................................888.3 E1 interface performance attributes ...........................................................................898.4 Operating system performance attributes...................................................................969 Alarm attributes.....................................................................................................989.1 Alarm attribute overview .............................................................................................999.2 Introduction to the alarm attributes ...........................................................................1009.3 General alarms .........................................................................................................1059.4 Cross connect alarms...............................................................................................1069.5 E1 interface alarms...................................................................................................1079.6 Fault condition – alarm table ....................................................................................10810 TMA subsystem picture of the <strong>Crocus</strong> <strong>DXC</strong>......................................................10910.1 Displaying the subsystem picture .............................................................................11010.2 Subsystem picture elements ....................................................................................11111 Firmware download.............................................................................................11311.1 Downloading with TMA.............................................................................................11411.2 Downloading with TML .............................................................................................11511.3 Downloading in boot mode .......................................................................................11611.4 Downloading via a management concentrator .........................................................117Continued on next pageviii


<strong>Crocus</strong> <strong>DXC</strong>Table of contentsTable of contents (continued)12 Technical specifications.....................................................................................11812.1 <strong>Crocus</strong> <strong>DXC</strong> types ....................................................................................................11912.2 E1 interface...............................................................................................................11912.3 Management interface ..............................................................................................12012.4 Control connector......................................................................................................12012.5 Power requirements..................................................................................................12112.6 Mechanical dimensions.............................................................................................12112.7 Environmental compliance........................................................................................12112.8 Safety compliance.....................................................................................................12212.9 Over-voltage and over-current protection compliance ..............................................12212.10 EMC compliance .......................................................................................................122Annexes ..................................................................................................123Annex A: product information..................................................................................125ix


<strong>Crocus</strong> <strong>DXC</strong>User manualUser manual 1


<strong>Crocus</strong> <strong>DXC</strong>2 User manual


<strong>Crocus</strong> <strong>DXC</strong>Introduction1 Introduction to the <strong>Crocus</strong> <strong>DXC</strong>This chapter gives an introduction to the <strong>Crocus</strong> <strong>DXC</strong>. The following table gives an overview of thischapter.Section Title Page1.1 <strong>Crocus</strong> <strong>DXC</strong> features 41.2 <strong>Crocus</strong> <strong>DXC</strong> product overview 41.3 CN4 card nest 41.4 Management overview 5User manual 3


Introduction<strong>Crocus</strong> <strong>DXC</strong>1.1 <strong>Crocus</strong> <strong>DXC</strong> featuresThe <strong>Crocus</strong> <strong>DXC</strong> (Digital Access Cross Connect) provides programmable non-blocking cross connectionbetween 8 or 16 E1 or fractional E1 interfaces. The cross connection can be performed per 64 kbpschannel. The <strong>Crocus</strong> <strong>DXC</strong> complies with ETSI recommendations ETS 300 010-1 and ETS 300 010-2.In combination with the <strong>Crocus</strong> baseband modems with G.703 interfaces, the <strong>Crocus</strong> <strong>DXC</strong> is a low costalternative for cross-connect cards in backbone switches, allowing local switching and grooming ofNx64kbps channels. This solution is in particular useful for smaller concentration points where theinvestment in backbone switching equipment is too expensive. It can be combined with e.g. the <strong>Crocus</strong>FO with 4E1 interface for extension from a central office location.The <strong>Crocus</strong> <strong>DXC</strong> offers the following features:• up to 8 or 16 E1 or fractional E1 interfaces• cross connection is possible per 64 kbps channel• extended management possibilities for configuration and inspection purposes• easy test functions• flash memory for easy firmware updating• as the other <strong>Crocus</strong> products, the <strong>Crocus</strong> <strong>DXC</strong> fits in the CN4 card nest• different powering possibilities through the CN4 card nest (230/115 Vac or -48 Vdc)1.2 <strong>Crocus</strong> <strong>DXC</strong> product overviewThe <strong>Crocus</strong> <strong>DXC</strong> exists in two versions:Version<strong>Crocus</strong> <strong>DXC</strong> 8<strong>Crocus</strong> <strong>DXC</strong> 16Specific propertyThis is a <strong>Crocus</strong> <strong>DXC</strong> card with 8 E1 or fractional E1 interfaces.This is a <strong>Crocus</strong> <strong>DXC</strong> card with 16 E1 or fractional E1 interfaces.1.3 CN4 card nestThe Telindus CN4 card nest is based on a standard card nest which fits in a standard 19” rack. The CN4card nest can hold up to 15 cards. It can be powered with:• -48 Vdc (no power modules required)• 230/115 Vac (one or two power module(s) required)• both -48 Vdc and 230/115 Vac (for back-up purposes).The CN4 card nest supports the complete <strong>Crocus</strong> range. For more information on the CN4 card nest,refer to the CN4 manual.4 User manual


<strong>Crocus</strong> <strong>DXC</strong>Introduction1.4 Management overviewThe <strong>Crocus</strong> <strong>DXC</strong> is manageable in many different ways. This section gives a quick overview of thevarious management possibilities.EasyConnect terminalConnecting the Telindus EasyConnect hand-held terminal over a serial connection (i.e. through thecontrol connector) to the <strong>Crocus</strong> <strong>DXC</strong>, allows you to manage the <strong>Crocus</strong> <strong>DXC</strong> in a basic way using theEasyConnect its keyboard.CLI and ATWINConnecting a VT100 terminal (emulation program) over a serial connection (i.e. through the controlconnector) to the <strong>Crocus</strong> <strong>DXC</strong>, you can evoke the following onboard management applications:• CLI. The Command Line Interface allows you to manage the <strong>Crocus</strong> <strong>DXC</strong> through a text basedinterface.• ATWIN. This is a basic, menu-driven user interface.TMA and TMA CLIConnecting your computer over a serial connection (i.e. through the control connector) to the <strong>Crocus</strong><strong>DXC</strong>, you can use the following management applications:• TMA. The Telindus Maintenance Application is a free management application for Windows. It allowsyou to manage the <strong>Crocus</strong> <strong>DXC</strong> using a user friendly GUI.To find out more about TMA, refer to the TMA manual.• TMA CLI. This is an advanced Command Line Interface with extra scripting capabilities.To find out more about TMA CLI, refer to the TMA CLI manual.Management concentratorConnecting the <strong>Crocus</strong> <strong>DXC</strong> to a management concentrator (e.g. the Orchid 1003 LAN or Telindus 1035Orchid) offers the following possibilities:• Using the management concentrator as an IP proxy agent, you have the possibility to connect to the<strong>Crocus</strong> <strong>DXC</strong> over an IP network. In that case you can establish an IP connection with the <strong>Crocus</strong> <strong>DXC</strong>and run TMA, TMA CLI or the Web Interface over this connection. Using Telnet, you can also runATWIN and CLI.For more information on how to use the management concentrator as an IP proxy agent, refer to themanual of the management concentrator.• Using the management concentrator as an SNMP proxy agent, you can manage the <strong>Crocus</strong> <strong>DXC</strong>through SNMP.For more information on how to use the management concentrator as an SNMP proxy agent, refer tothe manual of the management concentrator.• The management concentrator allows you to manage the <strong>Crocus</strong> <strong>DXC</strong> with TMA for HP OpenView,the Telindus integrated management application that runs on the HP OpenView platform.To find out more about TMA for HP OpenView, refer to the TMA for HP OpenView manual.Continued on next pageUser manual 5


Introduction<strong>Crocus</strong> <strong>DXC</strong>Management overview (continued)Management overviewThe following table gives an overview of all the management possibilities and how you can connect them:ManagementtoolPC – <strong>Crocus</strong> <strong>DXC</strong> connectionPC – management concentratorconnectionSerial IP Serial IPEasyConnect X XCLI X 1 X 1 X 2ATWIN X 1 X 1 X 2TMA X X XTMA CLI X X XTMA for HPOVSNMP 3Web Interface 4XXX1 Using a VT100 terminal (emulation program).2 Using Telnet.3 Using any SNMP browser.4 Using a web browser.6 User manual


<strong>Crocus</strong> <strong>DXC</strong>Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong>2 Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong>First this chapter gives some important safety instructions. Then it explains how to install and connect the<strong>Crocus</strong> <strong>DXC</strong>.You are advised to read this chapter in a sequential manner, from the beginning to the end, withoutskipping any part. By doing so, your <strong>Crocus</strong> <strong>DXC</strong> will be completely installed and ready for configurationwhen you reach the end of this chapter.The following table gives an overview of this chapter.Section Title Page2.1 Safety instructions 82.2 Unpacking 92.3 Selecting a site 102.4 Installation and connection precautions 112.5 Connecting the <strong>Crocus</strong> <strong>DXC</strong> 122.6 Front panel LED indicators 17User manual 7


Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>2.1 Safety instructionsIMPORTANT SAFETY INSTRUCTIONSUnplug the unit from the wall power outlet or remove it from the card nest before installing, adjusting orservicing.The safety of this unit depends upon the third pin (ground pin) of the 3-wire grounding type plug. Do notdefeat this safety feature. If the power outlet at your site only has 2 pins, please consult a qualifiedelectrician.ACHTUNG! WICHTIGE SICHERHEITSINSTRUKTIONENVor sämtlichen Arbeiten am Gerät (Installation, Einstellungen, Reparaturen etc.) sollten Sie denNetzstecker aus der Steckdose ziehen.Die Sicherheit dieses Gerätes ist abhängig von dem dritten Kontakt (dem Erdungspin) des 3-poligenSteckers. Beachten Sie unbedingt diese Sicherheitsstandard. Sollten Sie nur eine ältere 2-poligeSteckdose zur Verfügung haben, lassen Sie diese von einem Elektriker gegen eine 3-polige Steckdoseauswechseln.SAFETY WARNINGTo avoid damage to the unit, please observe all procedures described in this chapter.SICHERHEITSBESTIMMUNGENUm eine Beschädigung des Gerätes zu verhindern, beachten Sie bitte unbedingt dieSicherheitsbestimmungen, die in diesem Abschnitt beschrieben werden.Ensure that the unit and its connected equipment all use the same AC power and ground, to reducenoise interference and possible safety hazards caused by differences in ground or earth potentials.8 User manual


<strong>Crocus</strong> <strong>DXC</strong>Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong>2.2 UnpackingChecking the shipping cartonRough handling during shipping causes most early failures. Before installation, check the shipping cartonfor signs of damage:• If the shipping carton is damaged, please place a claim with the carrier company immediately.• If the shipping carton is undamaged, do not dispose of it in case you need to store the unit or ship it inthe future.Package contentsThe box should contain the following items:• <strong>Crocus</strong> <strong>DXC</strong>• TMA CD-ROM (including this User and Reference manual in PDF format)User manual 9


Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>2.3 Selecting a siteWARNINGAlways place the unit on its feet without blocking the air vents.Do not stack multiple units directly onto each other, as stacking can cause heat build-up that coulddamage the equipment.ACHTUNGStellen Sie das Gerät niemals seitlich, sondern nur auf den Füßen auf und achten Sie darauf, daß dieLüftungsschlitze an der Seitenverkleidung frei bleiben.Stapeln Sie nicht mehrere Geräte direkt übereinander, dies kann zu einem Hitzestau führen.Install the unit in an area free of extreme temperatures, humidity, shock and vibration. Position it so thatyou can easily see and access the front panel and its control indicators. Leave enough clearance at theback for cables and wires. Position the unit within the correct distances for the different accesses andwithin 2m of a power outlet.10 User manual


<strong>Crocus</strong> <strong>DXC</strong>Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong>2.4 Installation and connection precautionsESD WARNINGThe circuit boards are sensitive to electrostatic discharges (ESD) and should be handled with care. It isadvisable to ensure an optimal electrical contact between yourself, the working area and a safety groundbefore touching any circuit board. Take special care not to touch any component or connector on thecircuit board.EMC WARNINGEMC compliant installationThe complete <strong>Crocus</strong> family and the CN4 card nest are fully EMC compliant. Because of the modularstructure of the CN4 card nest, all unused slots (power slots, card slots and interface slots) have to becovered with the appropriate blanking modules at installation time.To ensure compliance with EMC directive 89/336/EEC, shielded cables or ferrite beads have to be used.This unit may be powered by an IT Power System.NOTEANMERKUNGDas Gerät kann gespeist wurden durch ein IT Power System.User manual 11


Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>2.5 Connecting the <strong>Crocus</strong> <strong>DXC</strong>This section explains how to connect the <strong>Crocus</strong> <strong>DXC</strong>. The following table gives an overview of thissection.Section Title Page2.5.1 <strong>Crocus</strong> <strong>DXC</strong> front and rear view 132.5.2 Inserting the <strong>Crocus</strong> <strong>DXC</strong> in the CN4 card nest 142.5.3 Mounting the blanking panels 152.5.4 Connecting the interfaces 1612 User manual


<strong>Crocus</strong> <strong>DXC</strong>Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong>2.5.1 <strong>Crocus</strong> <strong>DXC</strong> front and rear viewBelow a front and rear view of the <strong>Crocus</strong> <strong>DXC</strong> 8 and <strong>Crocus</strong> <strong>DXC</strong> 16 is given.191PWR2PWR102123129101133311444121245513<strong>66</strong>1477158TST ERR8TST ERRTST ERR16CTRLCTRLCLOCKCLOCKSTATIONSTATION112235313544INTERNA6INTERNA1467157CROCUS<strong>DXC</strong> 88CROCUS<strong>DXC</strong> 16168User manual 13


Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>2.5.2 Inserting the <strong>Crocus</strong> <strong>DXC</strong> in the CN4 card nestThe <strong>Crocus</strong> <strong>DXC</strong> consists of a stuffed print provided with a front panel. The <strong>Crocus</strong> <strong>DXC</strong> has to beinserted in the CN4 card nest. Power supply and management connections are made through the DINconnector towards the card nest. The interface connections are made through the RJ45 connectors.To insert the <strong>Crocus</strong> <strong>DXC</strong> in the CN4 card nest, proceed as follows:StepAction1 Gently slide the <strong>Crocus</strong> <strong>DXC</strong> on the two inner slides into an available slot.The following figureshows this procedure:15 slots2 When nearly inserted, press tight.3 Lock both screws.Filling an entire CN4 card nestFor EMC reasons the cards all fit closely to each other. Therefore, you will experience that inserting thelast card in a completely filled up rack happens to be more stiffly. To fill up an entire rack, it is best toproceed as follows:StepAction1 Insert card 1 up to 14 in slot 0 up to 13 of the CN4 card nest.2 Fasten the screws of card 1 up to 14.3 Insert the last card in slot 14 of the CN4 card nest.4 Fasten the screws of the last card.14 User manual


<strong>Crocus</strong> <strong>DXC</strong>Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong>2.5.3 Mounting the blanking panelsThe <strong>Crocus</strong> <strong>DXC</strong> is delivered with blanking panels. For EMC reasons, these panels have to be mountedon the interfaces at the back of the <strong>Crocus</strong> <strong>DXC</strong>.To mount the interface blanking panels, proceed as follows:StepAction1 Gently slide the blanking panel over the interfaces at the back of the <strong>Crocus</strong> <strong>DXC</strong>.The following figure shows this procedure:2 Gently press the blanking panel against the CN4 card nest chassis.3 Lock both screws.User manual 15


Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>2.5.4 Connecting the interfacesThe <strong>Crocus</strong> <strong>DXC</strong> is defined as Data Terminal Equipment (DTE). Depending whether you connect theinterfaces of the <strong>Crocus</strong> <strong>DXC</strong> to e.g. a <strong>Crocus</strong> SDSL Quad (DCE) or e.g. a backbone node (DTE), youhave to use a straight or crossed RJ45 interconnection cable.In order to clarify this, the following figure shows an example of a set-up with a <strong>Crocus</strong> <strong>DXC</strong>:DTEE.g. backbone nodeDTE<strong>Crocus</strong> <strong>DXC</strong>DCEE.g. <strong>Crocus</strong> SDSL Quadwith G703 interfacecrossedRJ45 cablestraightRJ45 cableSummarised, when connecting the <strong>Crocus</strong> <strong>DXC</strong> to …• a DTE device, use a crossed RJ45 cable.• a DCE device, use a straight RJ45 cable.16 User manual


<strong>Crocus</strong> <strong>DXC</strong>Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong>2.6 Front panel LED indicatorsThis section gives an overview of the front panel LEDs and what they indicate The following table givesan overview of this section.Section Title Page2.6.1 Introduction to the front panel LEDs 182.6.2 Power LED 192.6.3 Test LED 192.6.4 Error LED 192.6.5 Clock LEDs 19User manual 17


Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>2.6.1 Introduction to the front panel LEDsWhen all the connections are made and the <strong>Crocus</strong> <strong>DXC</strong> is powered, the LEDs on thefront panel reflect the actual status of the device.LED label and colourThe following table lists the front panel LED indicators with their corresponding label andcolour.Front panel LED indicator Label Colourpower LED PWR greentest LED TST rederror LED ERR redstation clock LED STATION greenE1 interface 1 clock LED 1 greenE1 interface 2 clock LED 2 greenE1 interface 3 clock LED 3 greenE1 interface 4 clock LED 4 greeninternal clock LED INTERNAL green12345678PWRTST ERRLED status modesFor some front panel LED indicators different status modes exist. These status modescan be distinguished by the way the LED is lit up:CTRLLED status LED duty cycle Descriptioncontinuously off 0 % The LED never lights up.continuously on 100 % The LED lights up continuously.blinking 50 % The LED is as much lit as it is out.flashing 20 % The LED only lights up during 20% of thetime.mostly off - The LED occasionally lights up, without afixed duty cycle.mostly on - The LED occasionally goes out, without afixed duty cycle.CLOCKSTATION1234INTERNALmonitoring - The LED lights up irregularly. For instance,it lights up on detection of a certain signal.I.e. it monitors this signal.CROCUS<strong>DXC</strong> 818 User manual


<strong>Crocus</strong> <strong>DXC</strong>Installing and connecting the <strong>Crocus</strong> <strong>DXC</strong>2.6.2 Power LEDThis LED indicates that the <strong>Crocus</strong> <strong>DXC</strong> is connected to the power supply and is switched on.2.6.3 Test LEDThis LED indicates per E1 interface whether it is in test or not. Two different status modes can bedistinguished:offLED statusblinkingDescriptionThe corresponding E1 interface is in normal condition.The corresponding E1 interface is in test condition (external or internal loop-back).2.6.4 Error LEDThis LED indicates per E1 interface whether an error has occurred. Three different status modes can bedistinguished:LED statusDescriptionoffcontinuously onNo error has occurred.There are three possibilities:• LOS: a Loss Of Signal is detected• LFA: a Loss of Frame Alignment is detected• AIS: an Alarm Indication Signal is received.blinkingflashingA RAI (Remote Alarm Indication) is received.Alarm signalling is active and an alarm has been detected.For more information on alarm signalling, refer to Section 9.2.3 - Alarm signalling.2.6.5 Clock LEDsThese LEDs indicate which clocking mode is currently active. There are six possibilities:Clocking LEDSTATIONDescriptionIndicates that the station clock is the master clock.1 Indicates that the clock of E1 interface 1 is the master clock.2 Indicates that the clock of E1 interface 2 is the master clock.3 Indicates that the clock of E1 interface 3 is the master clock.4 Indicates that the clock of E1 interface 4 is the master clock.INTERNALIndicates that the internal clock is the master clock.User manual 19


<strong>Crocus</strong> <strong>DXC</strong>DIP switches and straps of the <strong>Crocus</strong> <strong>DXC</strong>3.1 Location of the DIP switches and strapsThe figure below shows the position of the DIP switches and straps on the <strong>Crocus</strong> <strong>DXC</strong> motherboard.DS11234910111212349101112567813141516567813141516User manual 21


DIP switches and straps of the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>3.2 Function of the DIP switchesThe following table gives an overview of the DIP switches on DIP switch bank DS1:DIP switch name DS1 no. Setting Functionstart-up mode1 on Start up from flash memory.offStart up in boot mode.load defaultconfiguration2 on Normal operation.offLoad default configuration.3.3 Function of the strapsUsing the straps you can change the termination impedance of each E1 interface. You can choosebetween 120 ohm or 75 ohm.Strap name Setting per channel (x) Functionimpedance selectionxx120 ohmwithout jumpersxx75 ohmwith jumpers3.4 Changing the DIP switch and strap settingsTo change the DIP switch and / or strap settings of the <strong>Crocus</strong> <strong>DXC</strong>, proceed as follows:StepAction1 Loosen the screws of the <strong>Crocus</strong> <strong>DXC</strong>.2 Gently pull the <strong>Crocus</strong> <strong>DXC</strong> out of the CN4 card nest.3 Change the DIP switch and / or strap settings.4 Gently slide the <strong>Crocus</strong> <strong>DXC</strong> in the CN4 card nest.5 Fasten the screws of the <strong>Crocus</strong> <strong>DXC</strong>.22 User manual


<strong>Crocus</strong> <strong>DXC</strong>Maintenance of the <strong>Crocus</strong> <strong>DXC</strong>4 Maintenance of the <strong>Crocus</strong> <strong>DXC</strong>Once you installed the <strong>Crocus</strong> <strong>DXC</strong>, you can proceed with the configuration. You can do this using any ofthe management tools introduced in Section 1.4 - Management overview.This chapter briefly highlights one of those management tools: the Telindus Maintenance Application(TMA). It gives an introduction and describes how to start a TMA session on the <strong>Crocus</strong> <strong>DXC</strong>.Furthermore, it also introduces the terminology concerning the management of a Telindus device.The following table gives an overview of this chapter.Section Title Page4.1 Starting a TMA session on the <strong>Crocus</strong> <strong>DXC</strong> 244.2 Introducing the attributes of the <strong>Crocus</strong> <strong>DXC</strong> 29User manual 23


Maintenance of the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>4.1 Starting a TMA session on the <strong>Crocus</strong> <strong>DXC</strong>This section introduces the Telindus Maintenance Application (TMA) and describes how to start a TMAsession on the <strong>Crocus</strong> <strong>DXC</strong>.The following table gives an overview of this chapter.Section Title Page4.1.1 Introducing TMA 254.1.2 Starting a TMA session through the control connector 264.1.3 Starting a TMA session through a management concentrator 2824 User manual


<strong>Crocus</strong> <strong>DXC</strong>Maintenance of the <strong>Crocus</strong> <strong>DXC</strong>4.1.1 Introducing TMAWhat is the Telindus Maintenance Application?TMA is a free Windows software package that enables you to maintain the <strong>Crocus</strong> <strong>DXC</strong>, i.e. to access itsconfiguration attributes and look at status, performance and alarm information using a user friendlygraphical user interface.TMA is an excellent tool for complete management of the Telindus access devices. When using TMA incombination with a network management system such as HP OpenView, complete networks can bemanaged from one central site.Consult the TMA user manual to install it and get acquainted with the TMA user interface.You will need a new version of the model file distribution if changes have been made to the attributes ofthe <strong>Crocus</strong> <strong>DXC</strong>. The most recent model files can always be downloaded from the Telindus web site athttp://www.telindusproducts.com/tma.How to connect TMA?There are two ways to establish a connection between the computer running TMA and the <strong>Crocus</strong> <strong>DXC</strong>:• over a serial connection, through the control connector of the <strong>Crocus</strong> <strong>DXC</strong>.• over an IP or a serial connection, through a management concentrator.User manual 25


Maintenance of the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>4.1.2 Starting a TMA session through the control connectorTo start a TMA session on the <strong>Crocus</strong> <strong>DXC</strong> through the control connector, proceed as follows:StepAction1 Connect the COM port of your PC througha straight DB9 male-female cable with thecontrol connector of your <strong>Crocus</strong> <strong>DXC</strong> asshown in the following figure:2 Start TMA.3 In the TMA window, either …• select from the menu bar: Connect !Device…• or press the shortcut key: Ctrl+N• or press on the Connect to devicebutton:The Connect (to a device) window is beingdisplayed as in the following figure:4 In the Connect (to a device) window, configure the following parameters:• Select the option Serial, and specify the COM port of your computer the <strong>Crocus</strong> <strong>DXC</strong>is connected to.• If a password has previously been configured in the <strong>Crocus</strong> <strong>DXC</strong> then also fill in thepassword field.5 If the necessary parameters are filled in, press the Next > button.Continued on next page26 User manual


<strong>Crocus</strong> <strong>DXC</strong>Maintenance of the <strong>Crocus</strong> <strong>DXC</strong>Starting a TMA session through the control connector (continued)StepAction6 In the TMA window, either …• select from the menu bar: Connect !Select device…• or press the shortcut key: Ctrl+D• or press on the Select device button:The Connect (select a device) window is beingdisplayed as in the following figure:7 In the Connect (select a device) window, configure the following parameters:• Select the option On device.• If a password has previously been configured in the <strong>Crocus</strong> <strong>DXC</strong> then also fill in thepassword field.8 If the necessary parameters are filled in, press the Finish button.9 After a couple of seconds, the attributes of the selected <strong>Crocus</strong> <strong>DXC</strong> appear in the TMAwindow.User manual 27


Maintenance of the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>4.1.3 Starting a TMA session through a management concentratorOn central locations with many access devices, the <strong>Crocus</strong> <strong>DXC</strong> can be connected to a managementconcentrator (e.g. Orchid 1003 LAN or Telindus 1035 Orchid). In this case the management concentratoris a proxy device for the <strong>Crocus</strong> <strong>DXC</strong>. This means you can connect TMA to the <strong>Crocus</strong> <strong>DXC</strong> through themanagement concentrator.What is more, the management concentrator can act as an IP proxy device for the <strong>Crocus</strong> <strong>DXC</strong>. The IPaddress related to the <strong>Crocus</strong> <strong>DXC</strong> is defined in the management concentrator.Refer to the manual of the management concentrator for more information on the configuration andmanagement capabilities of this device.28 User manual


<strong>Crocus</strong> <strong>DXC</strong>Maintenance of the <strong>Crocus</strong> <strong>DXC</strong>4.2 Introducing the attributes of the <strong>Crocus</strong> <strong>DXC</strong>This section gives an introduction to the attributes of the <strong>Crocus</strong> <strong>DXC</strong>. It also introduces terms such ascontainment tree, group, object, attribute, value and action.The following table gives an overview of this section.Section Title Page4.2.1 Containment tree terminology 304.2.2 The <strong>Crocus</strong> <strong>DXC</strong> containment tree 324.2.3 <strong>Crocus</strong> <strong>DXC</strong> attribute overview 33User manual 29


Maintenance of the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>4.2.1 Containment tree terminologyThe following figure depicts the TMA window containing the <strong>Crocus</strong> <strong>DXC</strong> containment tree.Containment treeGroupsAttributesAttribute valuesActionsObjectsStructured valuesContinued on next page30 User manual


<strong>Crocus</strong> <strong>DXC</strong>Maintenance of the <strong>Crocus</strong> <strong>DXC</strong>Containment tree terminology (continued)The following table explains the terminology associated with the containment tree.TermcontainmenttreeDescriptionThe containment tree represents the hierarchical structure of the <strong>Crocus</strong> <strong>DXC</strong>. It iscomposed of a number of objects that are ordered in a tree. This tree resembles aWindows directory structure:• it is also a levelled structure, with nodes which can be expanded or reduced• the containment tree objects can be compared with file folders• the objects contain attributes like file folders contain files.objectAn object represents a physical interface, an application or a combination of both.Each object has its own set of attributes.Example:The top object crocus<strong>DXC</strong> contains the sub-object crossConnect. This object containsall the attributes concerning the cross connections. E.g. the configuration attributecrossConnectTable.attributeAn attribute is a parameter related to a certain object. It has a certain value.Example:The object e1Interface[ ] contains the status attribute ifOperStatus, which has aspossible values up and down.valueAn attribute has a certain value which is …• changeable in case of a configuration attribute (provided you have write access)• read only in case of a status, performance and alarm attribute.Example:The configuration attribute stationClock can be set to the value enabled or disabled.structured valueSome attribute values contain underlying values: a structured value. These valuesare displayed in the structured value window. If an attribute contains structuredvalues then a bit string, or is displayed after the attribute.Example:The alarmLevel attribute contains a structured value which displays alarms and theircorresponding priority level.groupGroups assemble a set of attributes related by functionality. There are four groupsin TMA, which correspond with the four tabs in the attribute window:• configuration• status• performance• alarms.actionA group in combination with an object may have actions assigned to them. Theseactions are displayed in the action window.Example:The Activate Configuration action only appears when the object crocus<strong>DXC</strong> is selected incombination with the group Configuration.User manual 31


Maintenance of the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>4.2.2 The <strong>Crocus</strong> <strong>DXC</strong> containment treeThe following table lists the different objects of the <strong>Crocus</strong> <strong>DXC</strong> containment tree.ObjectThis object contains …> crocus<strong>DXC</strong> the general system attributes. It is the top object in the containment tree.E.g. the status attribute sysUpTime: 00005d 02h 53m 16s.>> crossConnect the cross connect attributes.E.g. the configuration attribute crossConnectTable.>> e1Interface[ ] the attributes of the E1 interfaces.E.g. the configuration attribute g703Coding.>> management the network management attributes.E.g. the status attribute ifSpeed.>> operatingSystem the operating system attributes.E.g. the performance attribute currUsedProcPower (%).32 User manual


<strong>Crocus</strong> <strong>DXC</strong>Maintenance of the <strong>Crocus</strong> <strong>DXC</strong>4.2.3 <strong>Crocus</strong> <strong>DXC</strong> attribute overviewWhere can you find an overview of all the attributes?The reference part of this manual explains all the attributes of the <strong>Crocus</strong> <strong>DXC</strong>. One chapter describesone group of attributes:• chapter 6 describes the configuration attributes• chapter 7 describes the status attributes• chapter 8 describes the performance attributes• chapter 9 describes the alarm attributes.Within a chapter, the objects and their underlying attributes are discussed in a sequential manner. I.e.from top to bottom, as they appear in the attribute window.User manual 33


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5 Step-by-step configurationThis chapter describes in a step-by-step method how to perform a basic configuration on <strong>Crocus</strong> <strong>DXC</strong>. Italso explains how DIP switch configuration tables and TMA attribute strings should be interpreted.You are advised to read this chapter in a sequential manner, from the beginning to the end, withoutskipping any part. By doing so, your <strong>Crocus</strong> <strong>DXC</strong> will be completely configured and ready for use whenyou reach the end of this chapter.The following table gives an overview of this chapter.Section Title Page5.1 Reading the configuration settings 355.2 Loading the default configuration 385.3 Configuring the clocking mode 415.4 Defining the cross connections 465.5 Configuring the E1 interfaces 505.6 Configuring the management attributes 515.7 Activating the configuration 58For a complete overview of the attributes of the <strong>Crocus</strong> <strong>DXC</strong>, refer to the reference manual.34 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configuration5.1 Reading the configuration settingsAs this chapter explains the basic configuration of the <strong>Crocus</strong> <strong>DXC</strong>, it contains some DIP switchconfiguration tables and a lot of TMA attribute strings. To enable you to read this information in a correctmanner, this section explains the structure of such tables and strings.The following table gives an overview of this section.Section Title Page5.1.1 Reading a DIP switch configuration table 365.1.2 Reading a TMA attribute string 37User manual 35


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.1.1 Reading a DIP switch configuration tableA DIP switch configuration table has the following layout:DIP switch name DS1 no. Setting Functionstart-up mode1 on Start up from flash memory.offStart up in boot mode.1 2 3 4 5The following table explains the DIP switch configuration table layout.NumberThis position displays …1 the DIP switch icon. It indicates that the table which follows is a DIP switch configurationtable.2 the DIP switch name.3 the DIP switch position on the DIP switch bank.The abbreviations mean the following:DS1 no. 1: DIP switch bank number 1, switch position number 14 the possible settings of the DIP switch: on and off. The default setting is printed in bold.5 the function associated with the corresponding DIP switch setting.36 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configuration5.1.2 Reading a TMA attribute stringA TMA attribute string has the following layout:crocus<strong>DXC</strong>/crossConnect/stationClockdefault: enabled1 2 3The following table explains the TMA attribute string layout.NumberThis position displays …1 the TMA attribute icon. It indicates that the string which follows is a TMA attribute string.Two different TMA attribute icons exist:• a basic attribute icon• an advanced attribute icon.For more information refer to Preface – Conventions used in this manual.2 the attribute name and its position in the containment tree.In the figure above, the string crocus<strong>DXC</strong>/crossConnect/stationClock means the following:• the attribute name is stationClock• this attribute is located in the sub-object crossConnect• this sub-object is located in the top object crocus<strong>DXC</strong>.3 the default value of a configuration attribute.User manual 37


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.2 Loading the default configurationIf you install the <strong>Crocus</strong> <strong>DXC</strong> for the first time, all configuration attributes are set to their default value. Ifthe <strong>Crocus</strong> <strong>DXC</strong> has already been configured a number of times and you want to reconfigure it startingfrom scratch, it might be best to load the default configuration.Also, when you accidentally made a configuration error which, for some reason, makes the <strong>Crocus</strong> <strong>DXC</strong>inaccessible for TMA, you can load the default configuration using the appropriate DIP switch. Forinstance: you defined a password in the <strong>Crocus</strong> <strong>DXC</strong> but you can not remember it. In that case you cannot access the <strong>Crocus</strong> <strong>DXC</strong> with TMA if you do not supply the correct password.You can load the default configurationby means of …a DIP switch.an action in TMA.For more information, refer to Section …5.2.1 - The load default configuration DIP switch5.2.2 - The Load Default Configuration action in TMA38 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configuration5.2.1 The load default configuration DIP switchThe location of the load default configuration DIP switch is:DIP switch name DS1 no. Setting Functionload defaultconfiguration2 on Normal operation.offLoad default configuration.To load the default configuration using the appropriate DIP switch, proceed as follows:StepAction1 Remove the <strong>Crocus</strong> <strong>DXC</strong> from the CN4 card nest as described in Section 3.4 -Changing the DIP switch and strap settings.2 Set DIP switch bank DS1 position 2 to off.To locate this DIP switch bank, refer to Section 3.1 - Location of the DIP switches andstraps.3 Re-insert the <strong>Crocus</strong> <strong>DXC</strong> in the CN4 card nest.⇒ The <strong>Crocus</strong> <strong>DXC</strong> reboots and loads the default configuration.4 Activate the loaded default configuration:1. Open a TMA session on the <strong>Crocus</strong> <strong>DXC</strong> (refer to Section 4.1 - Starting a TMAsession on the <strong>Crocus</strong> <strong>DXC</strong>). (✱)2. Execute the Activate Configuration command.(✱) If you are performing this load default configuration procedure because youaccidentally made a configuration error, you have the possibility to retrieve thiserroneous configuration before executing the Activate Configuration command. In that caseyou do not have to reconfigure the complete device again, but you only have to correctthe error in question. Retrieve the erroneous configuration by executing the Load savedconfiguration command.5 Reset DIP switch bank DS1 position 2 to on.6 Re-insert the <strong>Crocus</strong> <strong>DXC</strong> in the CN4 card nest as described in Section 3.4 - Changingthe DIP switch and strap settings.⇒ The <strong>Crocus</strong> <strong>DXC</strong> reboots in normal operation mode.User manual 39


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.2.2 The Load Default Configuration action in TMAThe location of the Load Default Configuration action in the <strong>Crocus</strong> <strong>DXC</strong> containment tree is:crocus<strong>DXC</strong>/Load Default ConfigurationTo load the default configuration, proceed as follows:StepAction1 In the TMA window, select the top object crocus<strong>DXC</strong> and the group Configuration.2 In the action window of TMA, click the left mouse button on Load Default Configuration sothat this action is selected.3 Press the right mouse button and select Execute.4 To see the default configuration, press the Retrieve all attributes from device button.5 In the action window of TMA, click the left mouse button on Activate Configuration so thatthis action is selected.6 Press the right mouse button and select Execute.40 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configuration5.3 Configuring the clocking modeThis section explains how to configure the clocking mode on the <strong>Crocus</strong> <strong>DXC</strong>. There are two attributesthat allow you to select a clocking mode.The following table gives an overview of this section.Section Title Page5.3.1 Selecting the station clock 425.3.2 Selecting the line clock 435.3.3 Clocking mode priority 445.3.4 Displaying the clocking mode in use 45User manual 41


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.3.1 Selecting the station clockcrocus<strong>DXC</strong>/crossConnect/stationClockdefault: enabledUse this attribute to indicate whether the station clock should be used as master clock or not.The station clock is a 2 MHz clock signal that is applied to a connector on the back of the CN4 card nest.This clock signal is then routed to the <strong>Crocus</strong> <strong>DXC</strong> via the backplane of the nest.ValueDescriptionenabledThe station clock is used as master clock.If no valid station clock signal is present or if it is lost, then the <strong>Crocus</strong> <strong>DXC</strong> willuse the lineClocks attribute in order to determine its master clock.However, the <strong>Crocus</strong> <strong>DXC</strong> regularly checks the presence of a valid station clocksignal. If the station clock is present (again), then the <strong>Crocus</strong> <strong>DXC</strong> goes (returns)to station clocking mode.disabledThe station clock is not used as master clock. The <strong>Crocus</strong> <strong>DXC</strong> will use thelineClocks attribute in order to determine its master clock.42 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configuration5.3.2 Selecting the line clockcrocus<strong>DXC</strong>/crossConnect/lineClocksdefault: e1AIn case the station clock is not present or the stationClock attribute is set to disabled, the <strong>Crocus</strong> <strong>DXC</strong> usesthe lineClocks attribute in order to determine its master clock.ValueDescriptiondisabledline 1Lines 1, 2None of the first four E1 interface clocks is used as master clock.If present, the first E1 interface clock is used as master clock.The <strong>Crocus</strong> <strong>DXC</strong> scans the first two E1 interfaces, in order to find a valid clocksignal:• First, the <strong>Crocus</strong> <strong>DXC</strong> verifies whether a valid clock signal is present on E1interface 1.• If a valid clock signal is present on E1 interface 1, then it is used as masterclock.• If no valid clock signal is present on E1 interface 1, then the <strong>Crocus</strong> <strong>DXC</strong>verifies whether a valid clock signal is present on E1 interface 2.• If a valid clock signal is present on E1 interface 2, then it is used as masterclock.• If no valid clock signal is present on E1 interface 2, then the <strong>Crocus</strong> <strong>DXC</strong>goes to internal clocking mode.Lines 1, 2, 3The <strong>Crocus</strong> <strong>DXC</strong> scans the first three E1 interfaces, as described above, inorder to find a valid clock signal.If not one of the three E1 interfaces carries a valid clock signal, then the <strong>Crocus</strong><strong>DXC</strong> goes to internal clocking mode.Lines 1, 2, 3, 4The <strong>Crocus</strong> <strong>DXC</strong> scans the first four E1 interfaces, as described above, in orderto find a valid clock signal.If not one of the four E1 interfaces carries a valid clock signal, then the <strong>Crocus</strong><strong>DXC</strong> goes to internal clocking mode.Remarks• If not one E1 interface carries a valid clock signal or if it is lost, then the <strong>Crocus</strong> <strong>DXC</strong> goes to internalclocking mode. However, the <strong>Crocus</strong> <strong>DXC</strong> regularly checks the presence of a valid clock signal on theE1 interfaces (depending on the settings of the lineClocks attribute). If the <strong>Crocus</strong> <strong>DXC</strong> finds one(again), then it uses this as master clock.• A cross connection is only defined in one direction. In other words, transmit and receive data arealways cross connected on the same interface and time slots. I.e. in and out are symmetric.• If the signal on an E1 interface is used as master clock signal and if you execute an external loopbacktest on this E1 interface, then the <strong>Crocus</strong> <strong>DXC</strong> checks the presence of a valid clock signal on theremaining E1 interfaces (depending on the settings of the lineClocks attribute) or falls back to internalclocking mode.User manual 43


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.3.3 Clocking mode priorityDepending on which clocking modes are enabled (stationClock or lineClocks) the <strong>Crocus</strong> <strong>DXC</strong> always tries toselect a clocking mode with the highest priority. The clocking mode priority is as follows:PriorityClocking modeHighmediumlowstation clockingE1 interface clockinginternal clockingExampleSuppose the stationClock attribute is set to enabled and the lineClocks attribute is set to lines 1, 2, 3, 4. Thisresults in the following:PhaseAction1 The <strong>Crocus</strong> <strong>DXC</strong> tries to select the station clock.2 If no valid station clock signal is present, then the <strong>Crocus</strong> <strong>DXC</strong> scans the first four E1interfaces and tries to select a clock on one of these interfaces.3 If no valid clock signal is present on any of the first four E1 interfaces, then the <strong>Crocus</strong><strong>DXC</strong> goes to internal clocking.However, the <strong>Crocus</strong> <strong>DXC</strong> regularly verifies all the different clocking possibilities. If the<strong>Crocus</strong> <strong>DXC</strong> detects it can select a clocking mode with a higher priority than the currentclocking mode, the <strong>Crocus</strong> <strong>DXC</strong> will do so.44 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configuration5.3.4 Displaying the clocking mode in usecrocus<strong>DXC</strong>/crossConnect/masterClockThis status attribute displays the clocking mode which is effectively used by the <strong>Crocus</strong> <strong>DXC</strong>.This is not necessarily the clocking mode you selected using the configuration attributes stationClock orlineClocks. It can be a clocking mode that is selected by the <strong>Crocus</strong> <strong>DXC</strong> because the clocking mode ofyour choice failed.User manual 45


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.4 Defining the cross connectionsThis section explains how to define the cross connections. It also tells you how to detect invalid entriesand how to look up the unused time slots.The following table gives an overview of this section.Section Title Page5.4.1 Filling in the cross connect table 475.4.2 Detecting invalid entries 485.4.3 Looking up unused time slots 4946 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configuration5.4.1 Filling in the cross connect tablecrocus<strong>DXC</strong>/crossConnect/crossConnectTabledefault: In this table you can specify the cross connections. A line in this table contains the following attributes:Attribute Description DefaultnameEnter here the name of the cross connection. Because this name isused as a cross-reference in other attributes, it is essential that it isspecified.inInterface Enter here the number of the E1 interface with the incoming 64kbps channels.noneinTimeSlotoutInterfaceoutTimeSlotThis is the bit string which represents time slots 1 up to 31 of the E1interface with the incoming 64 kbps channels. A grey bit means it isset to 0, a black bit means it is set to 1.If a bit is set to 1, then the corresponding time slot is crossconnected.Enter here the number of the E1 interface with the outgoing 64 kbpschannels.This is the bit string which represents time slots 1 up to 31 of the E1interface with the outgoing 64 kbps channels. A grey bit means it isset to 0, a black bit means it is set to 1.If a bit is set to 1, then the corresponding time slot is crossconnected.noneRemarks• Time slot 0 can not be cross connected.• A cross connection is only defined in one direction. In other words, transmit and receive data arealways cross connected on the same interface and time slots. I.e. in and out are symmetric.ExampleThe following figure shows an example of a filled in cross connect table:User manual 47


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.4.2 Detecting invalid entriesIn case you entered invalid entries in the crossConnectTable, an error message appears in the messages table(refer to Section 7.2 - General status attributes). The following table lists the possible invalid entries andthe corresponding error message:No name is specified.Invalid entryA name is used twice in the table.The “in” interface number is 0.The “out” interface number is 0.All the time slots of the “in” interface are 0.All the time slots of the “out” interface are 0.The amount of “in” time slots does not equal theamount of “out” time slots.The time slots overlap on the same interface.The time slots overlap on different interfaces.Error messagecrossConnect/table[n].name is invalidcrossConnect/table[n].name “name” already used incrossConnect/table[m]crossConnect/table[n].inInterface 0 is invalidcrossConnect/table[n].outInterface 0 is invalidcrossConnect/table[n].inTimeSlot 0 is invalidcrossConnect/table[n].outTimeSlot 0 is invalidcrossConnect/table[n]: nr of inTimeSlots [x] is not equal to nrof outTimeSlots [y]crossConnect/table[n]: inTimeSlot and outTimeSlot overlap• crossConnect/table[n].inTimeSlot overlaps withcrossConnect/table[m].inTimeSlot• crossConnect/table[n].inTimeSlot overlaps withcrossConnect/table[m].outTimeSlot• crossConnect/table[n].outTimeSlot overlaps withcrossConnect/table[m].inTimeSlot• crossConnect/table[n].outTimeSlot overlaps withcrossConnect/table[m].outTimeSlotIn the table above, [n] and [m] indicate a row number in the cross connect table. [x] and [y] represent anamount of time slots.ExampleThe following figure shows an example of a messages table containing a cross connect error message:48 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configuration5.4.3 Looking up unused time slotscrocus<strong>DXC</strong>/crossConnect/timeSlotUnusedTableThis status table gives an overview of used and unused time slots on the E1 interfaces. Therepresentation is as follows:• a used time slot is grey,• an unused timeslot is black.The following figure shows an example of used/unused time slot table:User manual 49


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.5 Configuring the E1 interfacescrocus<strong>DXC</strong>/e1Interface[ ]/g703Codingdefault: HDB3Use this attribute to set the G703 interface encoding mode. Two encoding modes are available:ValueDescriptionAMIHDB3Alternate Mark Inversion is a bipolar code with no zero substitution.High Density Bipolar 3 is a modified bipolar code.With HDB3 encoding, more than three consecutive zeroes occurring in the data arereplaced by a substitution word. This to ensure a high pulse density. Therefore,data links using the HDB3 code can carry data patterns with a low 1 density. Mostof the G703 applications use HDB3 encoding.crocus<strong>DXC</strong>/e1Interface[ ]/aisDetectiondefault: enabledUse this attribute to enable or disable the detection of the Alarm Indication Signal.crocus<strong>DXC</strong>/e1Interface[ ]/cRC4Insertiondefault: enabledUse this attribute to enable or disable the Cyclic Redundancy Check (CRC):enabledValueCRC-4 is calculated on the interface.DescriptionA Cyclic Redundancy Check is inserted in time slot 0 of the G.704 framed datastream. This CRC is used to check the data integrity on the G.703 connection.disabled All the CRC bits are set to 0.The setting of the cRC4Insertion attribute also has an impact on the E-bit:cRC4InsertionsettingenableddisabledImpact on the E-bitA CRC-4 error on reception causes the E-bit to be set to 0 on transmission.The E-bit is always 1 on transmission.50 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configuration5.6 Configuring the management attributesThis section explains the management attributes of the <strong>Crocus</strong> <strong>DXC</strong>. These attributes allow you to makeall the devices in your network accessible for management from one central location.First this section gives you some rules of thumb and remarks concerning the management of the <strong>Crocus</strong><strong>DXC</strong> in a network. Then it explains the attributes that have an impact on the management of the <strong>Crocus</strong><strong>DXC</strong>. Finally, it gives an example of a network and how to configure the <strong>Crocus</strong> <strong>DXC</strong> to make itaccessible for the central management system.The following table gives an overview of this section:Section Title Page5.6.1 Rules of thumb and remarks concerning management 525.6.2 Using relative or absolute addressing 535.6.2 Selecting the purpose of the control connector 535.6.4 Configuring the SA-bits on an E1 interface 555.6.5 Example – management over the E1 interfaces 56User manual 51


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.6.1 Rules of thumb and remarks concerning managementThe following lists some rules of thumb concerning the management of Telindus devices in a network:• Make sure there is only one path towards the management system. Else you might get unexpectedresults (e.g. devices that do not answer to polling, answer of several devices at once when polling onedevice, etc.).• Once your network starts to become complex on management level (i.e. more than just in-lineconnections as depicted in Relative addressing on page 53), you are advised to use absoluteaddressing instead of relative addressing (refer to Absolute addressing on page 53).In practice, it is best to use absolute addressing when you configure one of the attributes listed belowas follows:− ctrlPortProtocol attribute to management,− e1Interface[ ]/saBits to anything else than transparent.• Changing the ctrlPortProtocol attribute causes the <strong>Crocus</strong> <strong>DXC</strong> to reboot.52 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configuration5.6.2 Using relative or absolute addressingIn order to connect with TMA to the <strong>Crocus</strong> <strong>DXC</strong> (refer to Section 4.1 - Starting a TMA session on the<strong>Crocus</strong> <strong>DXC</strong>), you can use two addressing schemes:Address typerelativeDescriptionThis type of addressing is meant for a network topology where the devices areconnected in-line on management level. I.e. with extended managementconnections between two devices.To enable relative addressing, no address has to be specified in the device. In otherwords, you can leave the cms2Address attribute at its default value, being 0.Relative addressingAn extended management connection is realised with a crossed cable between thecontrol connectors of the two Telindus devices. You also have to set thectrlPortProtocol attribute to the value management.absoluteThis type of addressing is meant for a network topology where the devices are notconnected in-line on management level. I.e. when there is a digital multipoint devicepresent (e.g. the Orchid DM).To enable absolute addressing, an address has to be specified in the device. Dothis using the cms2Address attribute. The absolute addressing range goes from 1 upto 65535. Refer to crocus<strong>DXC</strong>/management/cms2Address.Absolute addressingUser manual 53


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.6.3 Selecting the purpose of the control connectorcrocus<strong>DXC</strong>/management/ctrlPortProtocoldefault: consoleThe setting of the ctrlPortProtocol attribute depends on what purpose the control connector of the <strong>Crocus</strong><strong>DXC</strong> has to serve. This is explained in the following table:ValuemanagementDescriptionSelect this value if you want to connect the control connector of the <strong>Crocus</strong> <strong>DXC</strong> to…• a management concentrator (e.g. the Orchid 1003 LAN or Telindus 1035 Orchid)for management purposes.• the control connector of another Telindus device using a crossed cable (i.e. theyare connected back-to-back) in order to create an extended management link.For more information on extended management links, refer to Relativeaddressing on page 53.When connecting the control connector of the <strong>Crocus</strong> <strong>DXC</strong> to a COM port of yourcomputer, you can still open a TMA session on the <strong>Crocus</strong> <strong>DXC</strong>. You can howevernot open a CLI or ATWIN session.consoleSelect this value if you want to connect the control connector of the <strong>Crocus</strong> <strong>DXC</strong> toa COM port of your computer in order to manage the <strong>Crocus</strong> <strong>DXC</strong> using TMA, CLIor ATWIN.54 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configuration5.6.4 Configuring the SA-bits on an E1 interfacecrocus<strong>DXC</strong>/e1Interface[ ]/saBitsdefault: pathManagementUse the saBits attribute to determine whether and which management data is inserted in the SA-bits. Ifmanagement data is inserted in the SA-bits, then it is inserted in SA registers SA5, SA7 and SA8. SA4 isused as a control register and contains bandwidth information.The saBits attribute has the following possible values:ValueTransparento10ManagementpathManagementDescriptionNo management data is inserted in the SA-bits. The SA-bits are passedtransparently.This inserts the proprietary Telindus O10 protocol in the SA-bits. This allows youto forward management data over the E1 interface in a similar way as you canover the control port. This allows more flexibility in managing your network ofTelindus devices.This inserts path management information in the SA-bits. This allows you tomanage complete paths instead of managing individual devices (i.e. elements).For more information on path management, refer to the Path Managementmanual.o10-PathManagementThis inserts both the proprietary Telindus O10 protocol as the path managementinformation in the SA-bits.• Note that forwarding management data over the E1 interface can be very slow. The speed liesbetween 200 and 1200 bps.• When running an external loop-back test on an E1 interface, AIS bits are only sent to the application ifthe value of the saBits attribute is set to transparent. In all other cases, timeslot 0 is unchanged in ordernot to lose O10 and/or path management information.• It is important to enable CRC-4 insertion when the saBits attribute is set to include O10 and/or pathmanagement information. Refer to Section 5.5 - Configuring the E1 interfaces.User manual 55


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.6.5 Example – management over the E1 interfacesUsing the saBits attribute, you can forward management data over an E1 interface. The following figureshows an example:<strong>DXC</strong>(abs. 1)E1-1E1TT 1(abs. 10)CV 1E1-2E1modem A(abs. 11)E1-3E1modem B(abs. 12)CV 2E1-4E1modem A(abs. 13)E1-5E1modem B(abs. 14)E1-6LegendmanagementsystemE1-7E1-8Note that for the <strong>Crocus</strong><strong>DXC</strong> the ctrlPortProtocolattribute is set tomanagement.TTCVE1abs.Table Top modemCard Version modemG.703 DTE interfaceabsolute addresscontrol portmanagement connectioninterface connectionsaBits = o10Management oro10-pathManagementsaBits = transparentinternalDmm = enabledinternalDmm = disabledmanagement data flowContinued on next page56 User manual


<strong>Crocus</strong> <strong>DXC</strong>Step-by-step configurationExample – management over the E1 interfaces (continued)In the network depicted on the previous page, the E1 interfaces of the <strong>Crocus</strong> <strong>DXC</strong> are connected to theE1 interfaces of several modems. By setting the appropriate attributes, the management data can passfrom the <strong>Crocus</strong> <strong>DXC</strong> to the modems.Special points of interest in this network are:• On E1 interface 1 and TT 1, you have to set the saBits to o10Management or o10-pathManagement. By doingso, you are able to forward management data over the E1 interface connection between the <strong>Crocus</strong><strong>DXC</strong> and TT 1.• On E1 interface 2 and 3 and on both modem A and B of CV 1, you have to set the saBits too10Management or o10-pathManagement. By doing so, you are able to forward management data over theE1 interface connection between …− E1 interface 2 and CV 1 modem A.− E1 interface 3 and CV 1 modem B.• On CV 2 the situation is different than on CV 1, because on CV 2 internalDmm is enabled. This meansthat management data is exchanged between modem A and B. This implies that …− you can reach modem B through modem A and vice versa.− you can not set the saBits to o10Management or o10-pathManagement on the E1 interface connectionbetween E1 interface 5 and modem B. Else you create two possible paths towards themanagement system. E.g. modem A could be reached over its E1 interface connection as well asthrough modem B. In this case, you might get unexpected results. Therefore, make sure there isonly one path towards the management system!User manual 57


Step-by-step configuration<strong>Crocus</strong> <strong>DXC</strong>5.7 Activating the configurationOnce the basic configuration of the <strong>Crocus</strong> <strong>DXC</strong> is made, it has to be activated. Do this by pressing theSend all attributes to device button in TMA:If you experience problems of any kind, you can always consult the status, performance and alarmattributes in order to determine the problem. For more information on these attributes, refer to thereference manual.58 User manual


<strong>Crocus</strong> <strong>DXC</strong>Reference manualReference manual 59


<strong>Crocus</strong> <strong>DXC</strong>60 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Configuration attributes6 Configuration attributesThis chapter discusses the configuration attributes of the <strong>Crocus</strong> <strong>DXC</strong>. The following table gives anoverview of this chapter.Section Title Page6.1 Configuration attribute overview 626.2 General configuration attributes 636.3 Cross connect configuration attributes 716.4 E1 interface configuration attributes 726.5 Management configuration attributes 74Reference manual 61


Configuration attributes<strong>Crocus</strong> <strong>DXC</strong>6.1 Configuration attribute overview> crocus<strong>DXC</strong>sysNamesysContactsysLocationbootFromFlashsecurityalarmMaskalarmLevelalarmContactHighMaskalarmContactLowMaskAction: Activate ConfigurationAction: Load Saved ConfigurationAction: Load Default ConfigurationAction: Cold Boot(continued)>> managementcms2AddressconsoleNoTrafficTimeoutctrlPortProtocol>> crossConnectstationClocklineClockscrossConnectTablealarmMaskalarmLevelalarmContactHighMaskalarmContactLowMask>> e1Interface[ ] (1)nameg703CodingaisDetectioncRC4InsertionsaBitssqTimesqThresholdtestDurationalarmMaskalarmLevelalarmContactHighMaskalarmContactLowMask(1) In case of …• a <strong>Crocus</strong> <strong>DXC</strong> 8, the containment treecontains 8 e1Interface[ ] objects• a <strong>Crocus</strong> <strong>DXC</strong> 16, the containment treecontains 16 e1Interface[ ] objects.All e1Interface[ ] objects contain the sameattributes.Continued in next column62 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Configuration attributes6.2 General configuration attributescrocus<strong>DXC</strong>/sysNamedefault: This is a field where you can assign a name to the <strong>Crocus</strong> <strong>DXC</strong>. The field has a limit of 64 characters.crocus<strong>DXC</strong>/sysContactdefault: This is a field where you can fill in the name of a contact person together with information on how tocontact this person. The field has a limit of 64 characters.crocus<strong>DXC</strong>/sysLocationdefault: This is a field where you can fill in the physical location of the <strong>Crocus</strong> <strong>DXC</strong>. The field has a limit of 64characters.crocus<strong>DXC</strong>/bootFromFlashdefault: AutoThe <strong>Crocus</strong> <strong>DXC</strong> has two flash memory banks. Each flash memory can contain a complete firmwareversion, but only one can be active. You can choose from the following settings:ValueIf you boot the <strong>Crocus</strong> <strong>DXC</strong> then …flash1flash2autothe first flash memory bank is activated.the second flash memory bank is activated.the <strong>Crocus</strong> <strong>DXC</strong> automatically chooses the flash memory bank containing the mostrecent firmware. It does this by comparing the version numbers of the firmware.Continued on next pageReference manual 63


Configuration attributes<strong>Crocus</strong> <strong>DXC</strong>General configuration attributes (continued)crocus<strong>DXC</strong>/securitydefault: In order to avoid unauthorised access to the network and the <strong>Crocus</strong> <strong>DXC</strong>, you can create a list ofpasswords with associated access levels. The security attribute contains the following elements:Element Description Default valuepassword The password is a string of maximum 10 characters. accessRightsThis attribute represents the access levels assigned to apassword. It is a bit string whereof each bit corresponds to anaccess level. The different access levels are:• readAccess• writeAccess• securityAccess111The following table shows, for each access level, what you can or can not do:Access levelReadattributesChangeattributesRead securityattributes (1)Change securityattributes (1)Executeactions (2)readAccess yes no no no nowriteAccess yes yes no no yessecurityAccess yes yes yes yes yes(1) The <strong>Crocus</strong> <strong>DXC</strong> has the following security attributes:• crocus<strong>DXC</strong>/sysName• crocus<strong>DXC</strong>/security(2) Actions are e.g. Activate Configuration, Cold Boot, etc.Continued on next page64 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Configuration attributescrocus<strong>DXC</strong>/security (continued)Entering passwordsThe table below explains how to enter passwords in the different management systems.Management systemTMATelnetSNMPTMLTMA CLI and TMA forHP OpenViewHow to enter the password?You can enter the password in the connect windows.You are prompted to enter the password when the session starts.You should use the defined passwords as community strings. If nopasswords are defined then you can use any string as community strings.Similar to TFTP you can send the password after the destination file name,separated by a ‘?’.Example: tml –fsourcefile@destinationfile?pwdUse the application TmaUserConf.exe to create a TMA user and assign apassword to this user. The password should correspond with a passwordconfigured in the device.If no passwords are created, everybody has complete access.If you define at least one password, it is impossible to access the <strong>Crocus</strong> <strong>DXC</strong> with TMA if you do notenter the correct password.If you create a list of passwords, you should create at least one with write and security access. If not, youwill be unable to make configuration and password changes after activation of the new configuration.Continued on next pageReference manual 65


Configuration attributes<strong>Crocus</strong> <strong>DXC</strong>crocus<strong>DXC</strong>/security (continued)Correcting the security tableIf you forgot your password or you forgot to create one with write and security access, then you can setthe Load Default Configuration DIP switch. As a result, the <strong>Crocus</strong> <strong>DXC</strong> reboots in its defaultconfiguration. You can then retrieve the erroneous configuration and correct it.To correct the security table, proceed as follows:StepAction1 Remove the <strong>Crocus</strong> <strong>DXC</strong> from the CN4 card nest as described in Section 3.4 -Changing the DIP switch and strap settings.2 Set DIP switch bank DS1 position 2 to off.To locate this DIP switch bank, refer to Section 3.1 - Location of the DIP switches andstraps.3 Re-insert the <strong>Crocus</strong> <strong>DXC</strong> in the CN4 card nest.⇒ The <strong>Crocus</strong> <strong>DXC</strong> reboots and loads the default configuration.4 Retrieve the erroneous configuration:1. Open a TMA session on the <strong>Crocus</strong> <strong>DXC</strong> (refer to Section 4.1 - Starting a TMAsession on the <strong>Crocus</strong> <strong>DXC</strong>).2. Execute the Load saved configuration command.3. Correct the error in the security table.4. Execute the Activate Configuration command.5 Reset DIP switch bank DS1 position 2 to on.6 Re-insert the <strong>Crocus</strong> <strong>DXC</strong> in the CN4 card nest as described in Section 3.4 - Changingthe DIP switch and strap settings.⇒ The <strong>Crocus</strong> <strong>DXC</strong> reboots in normal operation mode.Continued on next page<strong>66</strong> Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Configuration attributesGeneral configuration attributes (continued)crocus<strong>DXC</strong>/alarmMaskThe alarmMask attribute enables or disables for each alarm of the corresponding object, whether it iscommunicated to the central management system (e.g. HP OpenView) or not.For more information on …• alarms in general, refer to Chapter 9 - Alarm attributes.• the alarms of the crocus<strong>DXC</strong> object, refer to Section 9.3 - General alarms.crocus<strong>DXC</strong>/alarmLevelWith this attribute, a priority level can be assigned to each alarm of the corresponding object. The alarmlevel range goes from 0 to 254, where 0 is the lowest and 254 is the highest priority level.crocus<strong>DXC</strong>/alarmContactHighMaskThe alarmContactHighMask attribute enables or disables for each alarm of the corresponding object,whether:• a visual indication is generated (blinking error LED)• the high alarm contacts on the CN4 card nest are driven.For more information on the alarm contacts of the CN4 card nest, refer to the CN4 manual.crocus<strong>DXC</strong>/alarmContactLowMaskThe alarmContactLowMask attribute enables or disables for each alarm of the corresponding object, whether:• a visual indication is generated (blinking error LED)• the low alarm contacts on the CN4 card nest are driven.For more information on the alarm contacts of the CN4 card nest, refer to the CN4 manual.Continued on next pageReference manual 67


Configuration attributes<strong>Crocus</strong> <strong>DXC</strong>General configuration attributes (continued)Configuration actionsThree types of configuration are present in the <strong>Crocus</strong> <strong>DXC</strong>:• the non-active configuration• the active configuration• the default configuration.When you configure the <strong>Crocus</strong> <strong>DXC</strong>, the following happens:Phase Action Result1 Connect the computer running themaintenance tool to the <strong>Crocus</strong> <strong>DXC</strong>.The non-active configuration is displayedon the screen.2 Modify the non-active configuration. The modifications have no immediateinfluence on the active configurationcurrently used by the <strong>Crocus</strong> <strong>DXC</strong>.3 Complete the modifications on the nonactiveconfiguration.4 In case of …• TMA, click on the TMA button Send allThe non-active configuration has to beactivated.The non-active configuration becomes theactive configuration.attributes to device: .• any other maintenance tool than thegraphical user interface based TMA(e.g. ATWIN, CLI, Web Interface,EasyConnect terminal, TMA CLI), thenexecute the Activate Configuration action.Continued on next page68 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Configuration attributesGeneral configuration attributes (continued)crocus<strong>DXC</strong>/Activate ConfigurationIf you execute this action, the editable non-active configuration becomes the active configuration.When use this action?If you configure the <strong>Crocus</strong> <strong>DXC</strong> using …• any other maintenance tool than the graphical user interface based TMA (e.g. ATWIN, CLI, WebInterface, EasyConnect terminal, TMA CLI), then execute the Activate Configuration action to activate theconfiguration after you finished configuring the <strong>Crocus</strong> <strong>DXC</strong> or after you executed the Load SavedConfiguration or Load Default Configuration action.• TMA, then do not just execute the Activate Configuration action to activate the configuration after youfinished configuring the <strong>Crocus</strong> <strong>DXC</strong>, but use the TMA button Send all attributes to deviceinstead. You can, however, execute the Activate Configuration action after you executed the Load SavedConfiguration or Load Default Configuration action.crocus<strong>DXC</strong>/Load Default ConfigurationIf you execute this action, the non-active configuration is overwritten by the default configuration.When use this action?If you install the <strong>Crocus</strong> <strong>DXC</strong> for the first time, all configuration attributes have their default values. If the<strong>Crocus</strong> <strong>DXC</strong> has already been configured but you want to start from scratch, then use this action to revertto the default configuration.In case of TMA, click on the TMA button Retrieve all attributes from deviceDefault Configuration action to see the new non-active configuration.after executing the Loadcrocus<strong>DXC</strong>/Load Saved ConfigurationIf you execute this action, the non-active configuration is overwritten by the active configuration currentlyused by the <strong>Crocus</strong> <strong>DXC</strong>.When use this action?If you are in the progress of modifying the non-active configuration but made some mistakes, then usethis action to revert to the active configuration.In case of TMA, click on the TMA button Retrieve all attributes from deviceDefault Configuration action to see the new non-active configuration.after executing the LoadContinued on next pageReference manual 69


Configuration attributes<strong>Crocus</strong> <strong>DXC</strong>General configuration attributes (continued)crocus<strong>DXC</strong>/Cold BootIf you execute this action, the <strong>Crocus</strong> <strong>DXC</strong> reboots. As a result, the <strong>Crocus</strong> <strong>DXC</strong> …• performs a self-test.• checks the software.• reads the saved configuration and restarts program execution.When use this action?Use this action, for instance, to activate new application software.70 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Configuration attributes6.3 Cross connect configuration attributescrocus<strong>DXC</strong>/crossConnect/stationClockdefault: enabledUse this attribute to indicate whether the station clock should be used as master clock or not.For more information, refer to Section 5.3.1 - Selecting the station clock.crocus<strong>DXC</strong>/crossConnect/lineClocks default: line 1In case the station clock is not present or the stationClock attribute is set to disabled, the <strong>Crocus</strong> <strong>DXC</strong> usesthe lineClocks attribute in order to determine its master clock.For more information, refer to Section 5.3.2 - Selecting the line clock.crocus<strong>DXC</strong>/crossConnect/crossConnectTabledefault: Use this table to specify the cross connections.For more information, refer to Section 5.4.1 - Filling in the cross connect table.crocus<strong>DXC</strong>/crossConnect/alarmMaskThe alarmMask attribute enables or disables for each alarm of the corresponding object, whether it iscommunicated to the central management system (e.g. HP OpenView) or not.For more information on …• alarms in general, refer to Chapter 9 - Alarm attributes.• the alarms of the crossConnect object, refer to Section 9.4 - Cross connect alarms.crocus<strong>DXC</strong>/crossConnect/alarmLevelWith this attribute, a priority level can be assigned to each alarm of the corresponding object. The alarmlevel range goes from 0 to 254, where 0 is the lowest and 254 is the highest priority level.crocus<strong>DXC</strong>/crossConnect/alarmContactHighMaskThe alarmContactHighMask attribute enables or disables for each alarm of the corresponding object,whether:• a visual indication is generated (blinking error LED)• the high alarm contacts on the CN4 card nest are driven.For more information on the alarm contacts of the CN4 card nest, refer to the CN4 manual.crocus<strong>DXC</strong>/crossConnect/alarmContactLowMaskThe alarmContactLowMask attribute enables or disables for each alarm of the corresponding object, whether:• a visual indication is generated (blinking error LED)• the low alarm contacts on the CN4 card nest are driven.For more information on the alarm contacts of the CN4 card nest, refer to the CN4 manual.Reference manual 71


Configuration attributes<strong>Crocus</strong> <strong>DXC</strong>6.4 E1 interface configuration attributescrocus<strong>DXC</strong>/e1Interface[ ]/namedefault:Use this attribute to define a name for the E1 interface in question.crocus<strong>DXC</strong>/e1Interface[ ]/codingdefault: hdb3Use this attribute to set the G703 interface encoding mode.For more information, refer to Section 5.5 - Configuring the E1 interfaces.crocus<strong>DXC</strong>/e1Interface[ ]/aisDetectiondefault: enabledUse this attribute to enable or disable the detection of the Alarm Indication Signal.crocus<strong>DXC</strong>/e1Interface[ ]/cRC4Insertiondefault: enabledUse this attribute to enable or disable the Cyclic Redundancy Check (CRC).For more information, refer to Section 5.5 - Configuring the E1 interfaces.crocus<strong>DXC</strong>/e1Interface[ ]/sqThreshold default: 10Use this attribute to set the signal quality threshold. This is the number of erroneous seconds for which asignal quality alarm is generated. If the sqThreshold value, i.e. the number of erroneous seconds, isexceeded within the sqTime, then a signal quality (sq) alarm is generated.For example, if 10 (default) or more erroneous seconds occur within 1 minute (default), then a signalquality alarm is generated.crocus<strong>DXC</strong>/e1Interface[ ]/sqTimedefault: 00000d 00h 01m 00sUse this attribute to set the signal quality time. This is the period (in days, hours, minutes and seconds)during which the signal quality threshold is measured. If the sqThreshold value, i.e. the number oferroneous seconds, is exceeded within the sqTime, then a signal quality (sq) alarm is generated.For example, if 10 (default) or more erroneous seconds occur within 1 minute (default), then a signalquality alarm is generated.crocus<strong>DXC</strong>/e1Interface[ ]/saBitsdefault: pathManagementUse this attribute to determine whether and which management data is inserted in the SA-bits.For more information, refer to Section 5.6.4 - Configuring the SA-bits on an E1 interface.crocus<strong>DXC</strong>/e1Interface[ ]/testDurationdefault: 00000d 00h 03m 00sIt is possible to perform diagnostic tests on the E1 interfaces. However, these tests cause an interruptionof the normal data transfer. Some tests even cause a contact loss between the management system andthe remote <strong>Crocus</strong> <strong>DXC</strong>. Therefore, tests are automatically terminated after a time-out period which isspecified with the testDuration attribute.The time-out ranges from 00000d 00h 00m 01s up to 00000d 18h 12m 15s. Entering 00000d 00h 00m 00s disablesthe time-out period.Continued on next page72 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Configuration attributesE1 interface configuration attributes (continued)crocus<strong>DXC</strong>/e1Interface[ ]/alarmMaskThe alarmMask attribute enables or disables for each alarm of the corresponding object, whether it iscommunicated to the central management system (e.g. HP OpenView) or not.For more information on …• alarms in general, refer to Chapter 9 - Alarm attributes.• the alarms of the e1Interface[ ] object, refer to Section 9.5 - E1 interface alarms.crocus<strong>DXC</strong>/e1Interface[ ]/alarmLevelWith this attribute, a priority level can be assigned to each alarm of the corresponding object. The alarmlevel range goes from 0 to 254, where 0 is the lowest and 254 is the highest priority level.crocus<strong>DXC</strong>/e1Interface[ ]/alarmContactHighMaskThe alarmContactHighMask attribute enables or disables for each alarm of the corresponding object,whether:• a visual indication is generated (blinking error LED)• the high alarm contacts on the CN4 card nest are driven.For more information on the alarm contacts of the CN4 card nest, refer to the CN4 manual.crocus<strong>DXC</strong>/e1Interface[ ]/alarmContactLowMaskThe alarmContactLowMask attribute enables or disables for each alarm of the corresponding object, whether:• a visual indication is generated (blinking error LED)• the low alarm contacts on the CN4 card nest are driven.For more information on the alarm contacts of the CN4 card nest, refer to the CN4 manual.Reference manual 73


Configuration attributes<strong>Crocus</strong> <strong>DXC</strong>6.5 Management configuration attributescrocus<strong>DXC</strong>/management/cms2Address default: 0Use this attribute to configure an absolute address in the <strong>Crocus</strong> SHDSL. The absolute addressing rangegoes from 1 up to 65535. This address can then be used to connect with TMA. Refer to Section 4.1Starting a TMA session on the <strong>Crocus</strong> <strong>DXC</strong>. If you want to connect with TMA using relative addressing,you do not have to configure anything. In that case you can leave the cms2Address attribute at its defaultvalue, being 0.Refer to Section 5.6.2 - Using relative or absolute addressing for more information on relative andabsolute addressing.crocus<strong>DXC</strong>/management/consoleNoTrafficTimeoutdefault: 30m 00sYou can open a management session on the <strong>Crocus</strong> <strong>DXC</strong> through the control connector. This sessioncloses automatically if there is no user interaction during a certain time-out period. This time-out periodcan be set with the consoleNoTrafficTimeOut attribute.The purpose of such a timer is to protect the <strong>Crocus</strong> <strong>DXC</strong> against unauthorised access in case the lastuser did not close his session.The consoleNoTrafficTimeOut value ranges from 00000d 00h 00m 00s up to 24855d 03h 14m 07s.crocus<strong>DXC</strong>/management/ctrlPortProtocoldefault: consoleThe setting of the ctrlPortProtocol attribute depends on what purpose the control connector of the <strong>Crocus</strong><strong>DXC</strong> has to serve.For more information, refer to Section 5.6.3 - Selecting the purpose of the control connector.74 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Status attributes7 Status attributesThis chapter discusses the status attributes of the <strong>Crocus</strong> <strong>DXC</strong>. The following table gives an overview ofthis chapter.Section Title Page7.1 Status attribute overview 767.2 General status attributes 777.3 Cross connect status attributes 807.4 E1 interface status attributes 827.5 Management status attributes 847.6 Operating system status attributes 85Reference manual 75


Status attributes<strong>Crocus</strong> <strong>DXC</strong>7.1 Status attribute overview> crocus<strong>DXC</strong>sysDescrsysObjectIDsysUpTimesysServicesflash1Versionflash2VersionactiveFlashbootVersionflashVersionsmessagesconfigurationSavingdeviceID(continued)>> managementcardSlotNumbercardNestNumber>> operatingSystemtaskInfo>> crossConnectcrossConnectTabletimeSlotUnusedTablemasterClock>> e1Interface[ ] (1)ifDescrifTypeifSpeedifOperstatustxdItu103rxdItu104losaislfaraitestTypetestOriginatortestStatus(1) In case of …• a <strong>Crocus</strong> <strong>DXC</strong> 8, the containment treecontains 8 e1Interface[ ] objects• a <strong>Crocus</strong> <strong>DXC</strong> 16, the containment treecontains 16 e1Interface[ ] objects.All e1Interface[ ] objects contain the sameattributes.Continued in next column76 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Status attributes7.2 General status attributescrocus<strong>DXC</strong>/sysDescrThis is a textual description of the device.Example: <strong>Crocus</strong> <strong>DXC</strong> 16 T2741/00100 07/03/00 10:00. In this example the following parameters are visible:• <strong>Crocus</strong> <strong>DXC</strong> 16 is the device name• T2741/00100 is the firmware code and version• 07/03/00 is the firmware release date• 10:00 is the firmware release timecrocus<strong>DXC</strong>/sysObjectIDThis is the SNMP identification string.Example: 1.3.6.1.4.1.776.30.crocus<strong>DXC</strong>/sysUpTimeThis is the time since last power-on or cold boot of the <strong>Crocus</strong> <strong>DXC</strong>.Example: 00005d 02h 42m 15s, which means 5 days, 2 hours, 42 minutes and 15 seconds.crocus<strong>DXC</strong>/sysServicesThis is the SNMP service identification.Example: 4, which indicates that the <strong>Crocus</strong> <strong>DXC</strong> has an end-to-end functionality.crocus<strong>DXC</strong>/flash1Versioncrocus<strong>DXC</strong>/flash2VersionThis displays the code and version of the firmware currently stored in flash bank 1 and 2, respectively. If aflash bank does not contain firmware then the value is empty.Example: T2741/00100. In this example the following parameters are visible:• T2741 is the firmware code for this device• 00100 is the firmware version.crocus<strong>DXC</strong>/activeFlashThis displays which flash bank is currently active.Example: Flash2, which means the firmware stored in flash bank 2 currently controls the device.crocus<strong>DXC</strong>/flashVersionsThis displays the number of firmware versions that can be stored in the flash banks.crocus<strong>DXC</strong>/bootVersionThis displays the code and version of the boot software currently used in the <strong>Crocus</strong> <strong>DXC</strong>.Example: T2130/00100. In this example the following parameters are visible:• T2130 is the boot software code for this device• 00100 is the boot software version.Continued on next pageReference manual 77


Status attributes<strong>Crocus</strong> <strong>DXC</strong>General status attributes (continued)crocus<strong>DXC</strong>/messagesThis table displays messages which can be:• informative messages, e.g. Reconfigured, Cold Boot, …• error messages, e.g. crossConnect/table[n].inInterface 0 is invalidThe messages table displays maximum 20 messages. The following figure gives an example of amessage table:If you open a TMA session on the <strong>Crocus</strong> <strong>DXC</strong> over IP, i.e. not through the control connector, then themessages are also sent to the control port.If you open a terminal emulation session on the control port, you can monitor these messages. If you hitthe ENTER key, the messages stop and you get the password prompt.Continued on next page78 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Status attributesGeneral status attributes (continued)crocus<strong>DXC</strong>/configurationSavingThis attribute indicates when the <strong>Crocus</strong> <strong>DXC</strong> is writing its (new) configuration to the flash memory.ValueDescriptionbusydoneThe <strong>Crocus</strong> <strong>DXC</strong> is busy writing its configuration to the flash memory. During thisstate, do not power-down or reboot the <strong>Crocus</strong> <strong>DXC</strong> else the new configuration willbe lost.The <strong>Crocus</strong> <strong>DXC</strong> has finished writing its configuration to the flash memory.crocus<strong>DXC</strong>/deviceIDThis displays a unique code. This code is programmed into the <strong>Crocus</strong> <strong>DXC</strong> before it leaves the factory.You can use this code for inventory purposes.Reference manual 79


Status attributes<strong>Crocus</strong> <strong>DXC</strong>7.3 Cross connect status attributescrocus<strong>DXC</strong>/crossConnect/crossConnectTableThis is the status cross connect table. It displays the cross connect table as you configured it. The onlydifference between the configuration and status cross connect table is that the status cross connect tabledoes not display lines which contain errors. Therefore, the combination of status cross connect table andmessages table is useful to locate and troubleshoot erroneous lines.The following figure displays the configuration cross connect table. Line number 9 contains an error:The following figure displays the message table. An error message notifies you that the configurationcross connect table contains an error:The following figure displays the status cross connect table. Only the lines without errors are displayed,i.e. line number 9 is not visible:For more information on identifying incorrect entries, refer to Section 5.4.2 - Detecting invalid entries.Continued on next page80 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Status attributesCross connect status attributes (continued)crocus<strong>DXC</strong>/crossConnect/timeSlotUnusedTableThis table gives an overview of used and unused time slots on the E1 interfaces.For more information, refer to Section 5.4.3 - Looking up unused time slots.crocus<strong>DXC</strong>/crossConnect/masterClockThis attribute displays the clocking mode which is effectively used by the <strong>Crocus</strong> <strong>DXC</strong>.This is not necessarily the clocking mode you selected using the configuration attributes stationClock orlineClocks. It can be a clocking mode that is selected by the <strong>Crocus</strong> <strong>DXC</strong> because the clocking mode ofyour choice failed.Reference manual 81


Status attributes<strong>Crocus</strong> <strong>DXC</strong>7.4 E1 interface status attributescrocus<strong>DXC</strong>/e1Interface[ ]/ifDescrThis is a textual description of the DTE interface.crocus<strong>DXC</strong>/e1Interface[ ]/ifTypeThis attribute displays the DTE interface type.crocus<strong>DXC</strong>/e1Interface[ ]/ifSpeedThis attribute displays the DTE interface speed in bits per second (bps).crocus<strong>DXC</strong>/e1Interface[ ]/ifOperstatusThis attribute indicates the global operational status of the E1 interface. This matches the unavailabilitycondition as defined in ITU-T recommendation G.826 (Annex A). Possible values are:ValueDescriptionupdowntestingThe interface is up, data transfer is possible.The interface is down, data transfer is not possible. For example, because theE1 interface is not connected.A test is active on the interface.crocus<strong>DXC</strong>/e1Interface[ ]/txdItu103This attribute displays the status (on / off) of the transmit data signal. The txdItu103 attribute only indicatesthe presence of the TxD signal, it does not monitor the real data signal.crocus<strong>DXC</strong>/e1Interface[ ]/rxdItu104This attribute displays the status (on / off) of the receive data signal. The rxdItu104 attribute only indicatesthe presence of the RxD signal, it does not monitor the real data signal.crocus<strong>DXC</strong>/e1Interface[ ]/losThis attribute displays (on / off) whether a Loss Of Signal has been detected. LOS is on when theincoming data is no longer present.crocus<strong>DXC</strong>/e1Interface[ ]/lfaThis attribute displays (on / off) whether a Loss of Frame Alignment has been detected. LFA is on whenthe Frame Alignment Signal (FAS), which is present in time slot 0 of the G.704 framed data, is notdetected after a certain period.crocus<strong>DXC</strong>/e1Interface[ ]/aisThis attribute displays (on / off) whether an Alarm Indication Signal has been detected. AIS is on whenthe AIS signal (also called all ones) is detected on the incoming data. I.e. the remote end detected aproblem and communicates this to the <strong>Crocus</strong> <strong>DXC</strong>.Continued on next page82 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Status attributesE1 interface status attributes (continued)crocus<strong>DXC</strong>/e1Interface[ ]/raiThis attribute displays (on / off) whether a Remote Alarm Indication signal has been detected. RAI is onwhen the RAI signal is detected on the incoming data. RAI means the far-end equipment has a problemwith the signal it is receiving from the local equipment.crocus<strong>DXC</strong>/e1Interface[ ]testTypeThis attribute displays which test is currently active. The possible indications are:ValueDescriptioninternalLoopbackexternalLoopbackAn internal loop-back test is active.An external loop-back test is active.crocus<strong>DXC</strong>/e1Interface[ ]/testOriginatorThis attribute displays the origin of the active test. The possible indications are:ValueDescriptionnmsinterfaceremoteunknownThe test is initiated by the management system (e.g. TMA).The test is initiated by the application, via the interface.The test is initiated by the remote modem.There are two possibilities:• No test is running.• For some reason it is not possible to define the origin of the test.crocus<strong>DXC</strong>/e1Interface[ ]/testStatusThis attribute displays the status of the active test. The possible indications are:ValueDescriptionprogressingrunningendingunknownThe test is starting.The test is running.The test is ending.There are two possibilities:• No test is running.• For some reason it is not possible to retrieve the status of the test.Reference manual 83


Status attributes<strong>Crocus</strong> <strong>DXC</strong>7.5 Management status attributescrocus<strong>DXC</strong>/management/cardSlotNumberThis attribute displays in which slot of the CN4 card nest the <strong>Crocus</strong> <strong>DXC</strong> is situated.It is possible to make a management connection to a <strong>Crocus</strong> <strong>DXC</strong> with, for instance, HP OpenView via amanagement concentrator. In that case, the <strong>Crocus</strong> <strong>DXC</strong> its position in the CN4 card nest has to beknown so that the management concentrator can address the <strong>Crocus</strong> <strong>DXC</strong>.crocus<strong>DXC</strong>/management/cardNestNumberThis attribute displays the CN4 card nest address.It is possible to make a management connection to a <strong>Crocus</strong> <strong>DXC</strong> with, for instance, HP OpenView via amanagement concentrator. As the cardSlotNumber status attribute, the cardNestNumber status attribute has tobe known for addressing purposes.The CN4 card nest address can be set with DIP switches at the back of the card nest. For moreinformation, refer to the CN4 manual.84 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Status attributes7.6 Operating system status attributescrocus<strong>DXC</strong>/operatingSystem/taskInfoThe taskInfo table displays status information about the operating system. The table contains the followingattributes:AttributeDescriptiontaskNametaskStatusName of the task.Current status. The task can have the following status values:ValueawakeasleepinactiveThis task is actually running.DescriptionThis task is waiting on an event.This task slot is not active, i.e. no task has been assigned tothis slot.load30s (%)load5m (%)runningInMedium(%)runningInHigh (%)programCounterThis is the load on the processor during the last 30 seconds.This is the load on the processor during the last 5 minutes.Each task can be running with a low, medium or high priority. This element givesthe percentage of time this task is running with medium priority during the last 30seconds.Each task can be running with a low, medium or high priority. This element givesthe percentage of time this task is running with high priority during the last 30seconds. The percentage of time this task is running with low priority can becalculated using the following formula:100% - runningInMedium (%) - runningInHigh (%).This is the current value of the program counter. The program counter is thememory address for the current instruction of this task.Reference manual 85


Performance attributes<strong>Crocus</strong> <strong>DXC</strong>8 Performance attributesThis chapter discusses the performance attributes of the <strong>Crocus</strong> <strong>DXC</strong>. The following table gives anoverview of this chapter.Section Title Page8.1 Performance attribute overview 878.2 Introducing the performance attributes 888.3 E1 interface performance attributes 898.4 Operating system performance attributes 9686 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Performance attributes8.1 Performance attribute overview> crocus<strong>DXC</strong>>> e1Interface[ ] (1)g703Performanceh2G703Performanceh24G703Performanced7G703Performanceg826Performanceh2G826Performanceh24G826Performanced7G826PerformanceAction: Activate Test(1) In case of …• a <strong>Crocus</strong> <strong>DXC</strong> 8, the containment treecontains 8 e1Interface[ ] objects• a <strong>Crocus</strong> <strong>DXC</strong> 16, the containment treecontains 16 e1Interface[ ] objects.All e1Interface[ ] objects contain the sameattributes.>> operatingSystemcurrUsedProcPowerusedProcPowerfreeDataBufferstotalDataBufferslargestFreeBlockSizefreeBlockCountfreeMemorytotalMemorytaskInfoReference manual 87


Performance attributes<strong>Crocus</strong> <strong>DXC</strong>8.2 Introducing the performance attributesPerformance information can be used for the following:• If network problems arise, information about the history of the communication link can be reviewedand analysed. These statistics can be useful to locate and solve the problem.• By collecting performance information, an operator can keep track of the global performance of thenetwork, e.g. network bottlenecks can be traced, etc.The following table explains the performance information timing.Performance timing2 hours,24 hours,7 daysDescriptionThe performance information is accumulated during a certain time span,called a period. After a period, the accumulated performance information iswritten into a buffer. Then a new period starts. An interval contains severalperiods:• To cover a 2 hours interval, 8 periods of 15 minutes are kept.• To cover a 24 hours interval, 12 periods of 2 hours are kept.• To cover a 7 days interval, 7 periods of 24 hours are kept.The buffer in which the information is stored, is a circular buffer. I.e. everyperiod (15 minutes, 2 hours or 24 hours) the most recent measured andcalculated values are added, and the oldest values are lost.since bootIn this case, the performance information is kept since the latest cold boot ofthe <strong>Crocus</strong> <strong>DXC</strong>. This can be considered as a performance informationsummary.The <strong>Crocus</strong> <strong>DXC</strong> does not contain a real-time clock, therefore time information is related to its internalclock. To allow you to situate the time intervals in the real time, the sysUpTime attribute is returned togetherwith the performance information. It reflects the time since the latest cold boot of the <strong>Crocus</strong> <strong>DXC</strong>.Only the available performance information is displayed. If the interrogation happens shortly after boot, novalues are displayed. For example for the 24 hours intervals, the new performance information isavailable only when a complete time span (i.e. 2 hours) has elapsed.88 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Performance attributes8.3 E1 interface performance attributesFirst this section lists the ITU-T recommendations that apply on G.703 interfaces for reference purposes.Then it lists some of the definitions that are used in the G.703 interface recommendations forcompleteness. Finally, this section explains the different E1 interface performance attributes.The following table gives an overview of this section.Section Title Page8.3.1 ITU-T recommendations 908.3.2 ITU-T definitions 918.3.3 G.703 performance attributes 928.3.4 G.826 performance attributes 938.3.5 E1 interface tests 94Reference manual 89


Performance attributes<strong>Crocus</strong> <strong>DXC</strong>8.3.1 ITU-T recommendationsThe following table lists the ITU-T recommendations that apply on G.703 interfaces:RecommendationTitleG.703 Physical/electrical characteristics of hierarchical digital interfaces.G.704 Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44736 kbpshierarchical levels (only at 2048 kbps).G.706 Frame alignment and cyclic redundancy check (CRC) procedures relating tobasic frame structures defined in Recommendation G.704.G.775 Loss of Signal (LOS), Alarm Indication Signal (AIS) and Remote DefectIndication (RDI) defect detection and clearance criteria for PDH signals.G.821 Error performance of an international digital connection operating at a bit ratebelow the primary rate and forming part of an integrated services digital network.G.826 Error performance parameters and objectives for international, constant bit ratedigital paths at or above the primary rate.90 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Performance attributes8.3.2 ITU-T definitionsThe following table lists some of the definitions that are used in the G.703 interface recommendations.They are listed here for completeness only. For more detailed information, refer to the recommendationsthemselves.TermDefinitiondefectA defect is one of the following conditions:• Loss Of Signal (LOS, defined in G.775).• Alarm Indication Signal (AIS, defined in G.775).• Loss of Frame Alignment (LFA, defined in G.706).Errored Block (EB)Errored Second(ES)Severely ErroredSecond (SES)A data frame that contains one or more errors. In case of G.704 framing a frameis TS0 ! TS31.A 1 second period where at least 1 EB or defect occurred.A 1 second period where equal to or more than 30% EBs occur or at least 1defect. The measurement of EBs depends on the operation mode:• Framed without CRC-4: the error detection occurs based on the detectedFrame Alignment Signal (FAS) bit errors: 28 FAS bit errors per secondmatches a Bit Error Rate (BER) of 10 -3 or more.• Framed with CRC-4: the error detection occurs based on CRC-4.unavailabilityMatches a period of 10 or more consecutive SESs. Refer to G.826 Annex A for acomplete definition.Reference manual 91


Performance attributes<strong>Crocus</strong> <strong>DXC</strong>8.3.3 G.703 performance attributescrocus<strong>DXC</strong>/e1Interface[ ]/G703PerformanceThis structured value displays the 2 hours, 24 hours and 7 days performance summary of the E1interface. The G703Performance structured value elements are the following:ElementsysUpTimelosCountlosTimeaisCountaisTimelfaCountlfaTimeFor the corresponding period, this value displays …the elapsed time since the last cold boot.the number of times a Loss Of Signal condition occurred.the amount of time a Loss Of Signal condition was active.the number of times an Alarm Indication Signal condition occurred.the amount of time an Alarm Indication Signal condition was active.the number of times a Loss of Frame Alignment condition occurred.the amount of time a Loss of Frame Alignment condition was active.crocus<strong>DXC</strong>/e1Interface[ ]/g703PerformanceThis structured value displays the performance summary of the E1 interface since the last cold boot.Except for sysUpTime, the structured value elements are the same as for the G703Performanceattribute.92 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Performance attributes8.3.4 G.826 performance attributescrocus<strong>DXC</strong>/e1Interface[ ]/G826PerformanceThis structured value displays the 2 hours, 24 hours and 7 days G.826 performance summary of the E1interface. The G703Performance structured value elements are the following:ElementsysUpTimeerrBlockserrSecsevErrSecunavailCountunavailTimebBErrorsFor the corresponding period, this value displays …the elapsed time since the last cold boot.the number of errored blocks that was counted.the number of errored seconds that was counted.the number of severely errored seconds that was counted.the number of times the interface was down (i.e. unavailable, as defined in ITU-Trecommendation G.826 Annex A).the amount of time the interface was down.the number of background block errors that was counted.For more information on these performance attributes, refer to the ITU-T recommendation G.826.crocus<strong>DXC</strong>/e1Interface[ ]/g826PerformanceThis structured value displays the G.826 performance summary of the E1 interface since the last coldboot. Except for sysUpTime, the structured value elements are the same as for theG826Performance attribute.Reference manual 93


Performance attributes<strong>Crocus</strong> <strong>DXC</strong>8.3.5 E1 interface testscrocus<strong>DXC</strong>/e1Interface[ ]/Activate TestUse this action to perform a test on an interface of the <strong>Crocus</strong> <strong>DXC</strong>. These tests are useful to tracepossible problems.The Activate Test action has the following argument values:Argument valueDescriptionNO TestExternal loopbackNo test is activated.The outgoing data on the E1 interface is immediately looped back into the<strong>Crocus</strong> <strong>DXC</strong>. In other words, the transmit data is taken as receive data.receive data<strong>Crocus</strong> <strong>DXC</strong>transmit dataE1 interfaceInternal loopbackThe incoming data on the E1 interface is immediately looped back out of the<strong>Crocus</strong> <strong>DXC</strong>. In other words, the receive data is the transmit data.receive data<strong>Crocus</strong> <strong>DXC</strong>transmit dataE1 interfaceTo execute a test, proceed as follows:StepAction1 In the TMA window, select the object e1Interface[ ] and the group Performance.2 In the action window of TMA, click the left mouse button on the field under the headingArgument Value.⇒ A drop down box appears.3 In the drop down box, select the action you want to execute.4 Press the right mouse button and select Execute.Continued on next page94 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Performance attributesE1 interface tests (continued)• If the signal on an E1 interface is used as master clock signal and if you execute an external loopbacktest on this E1 interface, then the <strong>Crocus</strong> <strong>DXC</strong> checks the presence of a valid clock signal on theremaining E1 interfaces (depending on the settings of the lineClocks attribute) or falls back to internalclocking mode.• When running an external loopback test on an E1 interface, AIS bits are only sent to the application ifthe value of the saBits attribute is set to transparent. In all other cases, timeslot 0 is unchanged in ordernot to lose O10 and/or path management informationReference manual 95


Performance attributes<strong>Crocus</strong> <strong>DXC</strong>8.4 Operating system performance attributescrocus<strong>DXC</strong>/operatingSystem/currUsedProcPowerThis is the amount of processing power used during the last 650 milliseconds, expressed as apercentage of the total available processing power.crocus<strong>DXC</strong>/operatingSystem/usedProcPowerThis table lists the used processing power for the 11 most recent 30 seconds intervals. The processingpower is expressed as a percentage of the total processing power. Each entry in the attributeusedProcPower is composed of the following attributes:ValueDescriptionsysUpTime Displays the elapsed time since the last cold boot. The next values are for the 30seconds period before this relative time stamp.minimumPP (%) This is the minimum percentage of processing power in use during the last 30seconds.averagePP (%) This is the average percentage of processing power in use during the last 30seconds.maximumPP (%) This is the maximum percentage of processing power in use during the last 30seconds.crocus<strong>DXC</strong>/operatingSystem/freeDataBuffersThe processor uses buffers for storing the packets during processing and/or queuing. Each buffer has a256 byte size, headers included. This parameter is the number of data buffers currently not in use andavailable for e.g. incoming data.crocus<strong>DXC</strong>/operatingSystem/totalDataBuffersThis is the total number of available data buffers.crocus<strong>DXC</strong>/operatingSystem/largestFreeBlockSizeThe processor uses RAM memory for storing internal information and buffering (see totalDataBuffers). Thedifferent tasks allocate RAM memory on request. Tasks may also free memory again. In this way the totalRAM memory becomes fragmented. This attribute gives the size of the largest contiguous free memoryblock expressed in bytes.crocus<strong>DXC</strong>/operatingSystem/freeBlockCountThis is the number of free contiguous memory blocks.crocus<strong>DXC</strong>/operatingSystem/freeMemoryThis is the total free memory expressed in bytes.crocus<strong>DXC</strong>/operatingSystem/totalMemoryThis is the total RAM memory expressed in bytes.Continued on next page96 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Performance attributesOperating system performance attributes (continued)crocus<strong>DXC</strong>/operatingSystem/taskInfoThis attribute contains status information concerning the different tasks running on the processor. It is atable grouping up to 31 task slots, which is the maximum number of parallel tasks running on theprocessor’s operating system.This attribute contains the same information as taskInfo in the status group (refer to Section 7.6 -Operating system status attributes).Reference manual 97


Alarm attributes<strong>Crocus</strong> <strong>DXC</strong>9 Alarm attributesThis chapter discusses the alarm attributes of the <strong>Crocus</strong> <strong>DXC</strong>. The following table gives an overview ofthis chapter.Section Title Page9.1 Alarm attribute overview 999.2 Introduction to the alarm attributes 1009.3 General alarms 1059.4 Cross connect alarms 1069.5 E1 interface alarms 1079.6 Fault condition – alarm table 10898 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Alarm attributes9.1 Alarm attribute overview> crocus<strong>DXC</strong>totalAlarmLevelalarmInfoNotRespondingAlarmSyncLossConfigChangedAccessPowerSupply1CVFailurePowerSupply2CVFailurePowerSupply48VFailureUnknownStateColdBootWarmBootCodeConsistencyFailConfigConsistencyFail>> crossConnectalarmInfotimeSlotConflbackupTiminglossOfTiming>> e1Interface[ ] (1)alarmInfolinkDownaislfaraisqtestActive(1) In case of …• a <strong>Crocus</strong> <strong>DXC</strong> 8, the containment treecontains 8 e1Interface[ ] objects• a <strong>Crocus</strong> <strong>DXC</strong> 16, the containment treecontains 16 e1Interface[ ] objects.All e1Interface[ ] objects contain the sameattributes.Reference manual 99


Alarm attributes<strong>Crocus</strong> <strong>DXC</strong>9.2 Introduction to the alarm attributesBefore discussing the alarm attributes of the <strong>Crocus</strong> <strong>DXC</strong> in detail, some general information on thealarm attributes of the <strong>Crocus</strong> <strong>DXC</strong> is given.The following table gives an overview of this section.Section Title Page9.2.1 Configuration alarm attributes 1019.2.2 General alarm attributes 1039.2.3 Alarm signalling 104100 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Alarm attributes9.2.1 Configuration alarm attributesThe following four configuration alarm attributes are already explained in Chapter 6 - Configurationattributes, but are explained more thoroughly below.crocus<strong>DXC</strong>/…/alarmMaskUse this attribute to mask or unmask the alarms of an object. This determines whether an active alarm isforwarded to the central management system (e.g. HP OpenView) or not.The alarms in the alarmMask attribute have the following values:enableddisabledValueIs the active alarm being forwarded to the central management system?Yes. So the alarm is unmasked.No. So the alarm is masked.Alarms are always seen in the alarmInfo alarm attribute of an object, regardless of the masking of thealarm. I.e. even if an alarm is set to disabled in the alarmMask of an object, if the alarm condition is fulfilledthen the alarm will be set to on in the alarmInfo of that object. However, because this alarm is disabled itwill not be sent to the central management system (e.g. HP OpenView).Only the most important alarms are unmasked (i.e. enabled) by default. All other alarms are masked (i.e.disabled).crocus<strong>DXC</strong>/…/alarmLevelUse this attribute to assign a priority level to each alarm of the corresponding object. The alarm levelrange goes from 0 to 254, where 0 is the lowest and 254 is the highest priority level.The alarmLevel of an unmasked, active alarm is sent to the totalAlarmLevel alarm attribute of the top objectcrocus<strong>DXC</strong>.Continued on next pageReference manual 101


Alarm attributes<strong>Crocus</strong> <strong>DXC</strong>Configuration alarm attributes (continued)crocus<strong>DXC</strong>/…/alarmContactHighMaskUse this attribute to mask or unmask the alarms of an object. This determines whether an active alarmactivates the high alarm contact of the CN4 card nest or not. By connecting an alarm circuit to the alarmcontact, e.g. a light bulb or a buzzer, you can generate an external alarm.The alarms in the alarmContactHighMask attribute have the following values:enableddisabledValueDoes the active alarm activate the high alarm contact of the CN4 card nest?Yes. So the alarm is unmasked.No. So the alarm is masked.For more information on the high alarm contacts, refer to the CN4 card nest manual.All alarms are masked (i.e. disabled) by default.crocus<strong>DXC</strong>/…/alarmContactLowMaskUse this attribute to mask or unmask the alarms of an object. This determines whether an active alarmactivates the low alarm contact of the CN4 card nest or not. By connecting an alarm circuit to the alarmcontact, e.g. a light bulb or a buzzer, you can generate an external alarm.The alarms in the alarmContactLowMask attribute have the following values:enableddisabledValueDoes the active alarm activate the low alarm contact of the CN4 card nest?Yes. So the alarm is unmasked.No. So the alarm is masked.For more information on the high alarm contacts, refer to the CN4 card nest manual.All alarms are masked (i.e. disabled) by default.102 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Alarm attributes9.2.2 General alarm attributesThe general alarm attributes totalAlarmLevel and alarmInfo are explained below.crocus<strong>DXC</strong>/totalAlarmLevelThis attribute is only present in the top object of the containment tree of the <strong>Crocus</strong> <strong>DXC</strong>, crocus<strong>DXC</strong>.It displays the priority level of an unmasked, active alarm. When several alarms are generated at thesame time, the highest priority level is shown. If the alarm levels are set in a structured manner, one lookat the totalAlarmLevel attribute enables the operator to make a quick estimation of the problem.The value of the totalAlarmLevel attribute is also communicated to the central management system (e.g. HPOpenView) where it determines the colour of the icon. This colour is an indication of the severity of thealarm.crocus<strong>DXC</strong>/…/alarmInfoThe alarmInfo contains the actual alarm information of the corresponding object. The alarmInfo attributesare:AttributediscriminatorcurrentAlarmspreviousAlarmsDisplays for the corresponding object …the total alarm count since the last cold boot.the current alarms.the second most recent alarms.alarmMask the alarmMask as configured in the Configuration group. Refer to Chapter 6 -Configuration attributes.alarmLevel the alarmLevel as configured in the Configuration group. Refer to Chapter 6 -Configuration attributes.Reference manual 103


Alarm attributes<strong>Crocus</strong> <strong>DXC</strong>9.2.3 Alarm signallingIf you do not have a central management system, you could perform alarm signalling with the alarmcontacts of the CN4 card nest.ExampleSuppose that you …• set the LOS alarm of the e1Interface[ ] objects to enabled in the alarmContactHighMask.• connect the high alarm contacts of the CN4 card nest to an external alarm circuit (e.g. with a lightbulb).Now, when on one of the E1 interfaces an LOS alarm occurs, the light bulb will light up.104 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Alarm attributes9.3 General alarmsSee Section 9.2 - Introduction to the alarm attributes for the general alarm attributes.crocus<strong>DXC</strong>/alarmInfoThe different alarms related to the object crocus<strong>DXC</strong> together with their explanation and their defaultalarmMask and alarmLevel value are given in the following table:The alarm …is generated …Default valuealarmMaskalarmLevelNotRespondingby the management concentrator when the <strong>Crocus</strong><strong>DXC</strong> does not respond on the managementconcentrator its polling session.enabled 4AlarmSyncLoss when the internal alarm buffer overflows. enabled 4ConfigChanged when the local configuration has been changed. disabled 1AccessPowerSupply1CVFailurePowerSupply2CVFailurePowerSupply48VFailureUnknownStatewhen TMA is connected locally (through the controlconnector) to the <strong>Crocus</strong> <strong>DXC</strong>.when the upper power supply in the CN4 card nestis not present or fails.when the lower power supply in the CN4 card nestis not present or fails.when the directly connected -48Vdc on the CN4card nest is no longer present. This means that the230/115 Vac back-up power supply has taken over.each time a new <strong>Crocus</strong> <strong>DXC</strong> is added to thenetwork, and before the management concentratorhas completed a first successful polling session.disabled 1disabled 3disabled 3disabled 3disabled 0ColdBoot each time the <strong>Crocus</strong> <strong>DXC</strong> performs a cold boot. disabled 1WarmBoot each time the <strong>Crocus</strong> <strong>DXC</strong> performs a warm boot. disabled 1CodeConsistencyFailConfigConsistencyFailwhen the version of the firmware stored in themanagement concentrator does not correspondwith the version of the firmware stored in the<strong>Crocus</strong> <strong>DXC</strong>.when the <strong>Crocus</strong> <strong>DXC</strong> configuration stored in themanagement concentrator does not correspondwith the actual configuration of the <strong>Crocus</strong> <strong>DXC</strong>.disabled 1disabled 1Reference manual 105


Alarm attributes<strong>Crocus</strong> <strong>DXC</strong>9.4 Cross connect alarmsSee Section 9.2 - Introduction to the alarm attributes for the general alarm attributes.crocus<strong>DXC</strong>/crossConnect/alarmInfoThe different alarms related to the object crossConnect together with their explanation and their defaultalarmMask and alarmLevel value are given in the following table:The alarm …is generated …Default valuealarmMaskalarmLeveltimeSlotConflictbackupTiminglossOfTimingwhen there are invalid entries in the configurationcross connect table.For more information on invalid entries, refer toSection 5.4.2 - Detecting invalid entries.when the clocking has fallen back to a clockingmode that was not the preferred clocking mode.E.g. when you set the stationClock attribute toenabled and the station clock is present, then the<strong>Crocus</strong> <strong>DXC</strong> uses the station clock as master clock.Suppose the station clock signal goes down, thenthe <strong>Crocus</strong> <strong>DXC</strong> falls back to a lower priorityclocking mode. Also see 5.3.3 - Clocking modepriority.when the clocking mode has fallen back to internalclocking mode.enabled 3enabled 2enabled 3106 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Alarm attributes9.5 E1 interface alarmsSee Section 9.2 - Introduction to the alarm attributes for the general alarm attributes.crocus<strong>DXC</strong>/e1interface[ ]/alarmInfoThe different alarms related to the object e1interface[ ] together with their explanation and their defaultalarmMask and alarmLevel value are given in the following table:The alarm …is generated …Default valuealarmMaskalarmLevellinkDownaislfaraisqwhen a Loss Of Signal occurs. I.e. the incomingsignal on the interface is lost.when an Alarm Indication Signal is received on theinterface, i.e. the remote end sends an AIS.The AIS alarm is …• set when the AIS condition is present• cleared when the AIS condition has disappeared… for a period of at least 1 second.when the Frame Alignment Signal (FAS), which ispresent in time slot 0 of the G.704 framed data, isnot detected after a certain period.The LFA alarm is …• set when the LFA condition is present• cleared when the LFA condition hasdisappeared… for a period of at least 1 second.when an RAI signal is detected on the incomingdata. An RAI means the far-end equipment has aproblem with the signal it is receiving from the localequipment.when the sqThreshold value, i.e. the number oferroneous seconds, is exceeded within the sqTime.For example, if 10 (default) or more erroneousseconds occur within 1 minute (default), then asignal quality alarm is generated.Also see the E1 configuration attributes sqThresholdand sqTime.enabled 2disabled 2disabled 2disabled 2disabled 2testActive when a test is active. disabled 1In case a LOS alarm, an AIS alarm or both alarms are active, then consequently the LFA alarm is alsoactivated. However, this is a derived alarm. In other words, it does not indicate the real problem (wherethe LOS or AIS alarm does). Therefore, a derived LFA alarm does not appear in the alarmInfo object. Thestatus attribute crocus<strong>DXC</strong>/e1Interface[ ]/lfa however, will be set to on.Reference manual 107


Alarm attributes<strong>Crocus</strong> <strong>DXC</strong>9.6 Fault condition – alarm tableThe following table gives some fault conditions and the corresponding alarms that are generated. It alsoshows when an alarm indication signal (AIS) is generated.Suppose time slot X of interface M is cross connected to time slot Y of interface N. In that case thefollowing fault condition versus alarm relationship applies:Fault condition Corresponding alarm Alarm indicationon the interfaceM transmit data?AIS applied totime slot Y ofinterface N?power supply failureNone. Only the alarm contactson the CN4 card nest are driven.nonoloss of incoming signalon interface Mloss of frame alignmenton interface Mbit error rate exceeds10 -3 on interface MLOS alarm on interface M A bit is set. yesLFA alarm on interface M A bit is set. yes10E-3 alarm on interface M A bit is set. yesalarm indication signalreceived on interface Mfrom remote endNone. Only the ERR LED ofinterface M blinks.nonoalarm indication signalreceived on interface MAIS alarm on interface M - yesIf AIS is applied to a time slot, it means that this time slot sends all ones.For all time slots that are not specified in the cross connect table, AIS is applied on the outgoing data.108 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>TMA subsystem picture of the <strong>Crocus</strong> <strong>DXC</strong>10 TMA subsystem picture of the <strong>Crocus</strong> <strong>DXC</strong>The subsystem picture is a TMA tool which visualises the status information of the <strong>Crocus</strong> <strong>DXC</strong>. Thischapter explains how to display the subsystem picture, and how to interpret the visual indications. Thefollowing table gives an overview of this chapter.Section Title Page10.1 Displaying the subsystem picture 11010.2 Subsystem picture elements 111Reference manual 109


TMA subsystem picture of the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>10.1 Displaying the subsystem pictureTo display the subsystem picture of the <strong>Crocus</strong> <strong>DXC</strong>, proceed as follows:StepAction1 Start a TMA session on the <strong>Crocus</strong> <strong>DXC</strong>. Refer to Section 4.1 - Starting a TMA sessionon the <strong>Crocus</strong> <strong>DXC</strong>.2In the TMA window, press on the subsystem picture button: .The subsystem picture isdisplayed:3 To close the subsystem picture, press .110 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>TMA subsystem picture of the <strong>Crocus</strong> <strong>DXC</strong>10.2 Subsystem picture elementsThis section displays and labels the different elements of the subsystem picture. It also explains how thevisual indications should be interpreted. Below, the <strong>Crocus</strong> <strong>DXC</strong> CV subsystem picture is displayed.interface LEDindicatorsE1 interfacesclocking LEDindicatorsContinued on next pageReference manual 111


TMA subsystem picture of the <strong>Crocus</strong> <strong>DXC</strong><strong>Crocus</strong> <strong>DXC</strong>Subsystem picture elements (continued)The table below gives an overview of the subsystem picture elements and what they indicate.Elementinterface LEDindicatorsclocking LEDindicatorsE1 interfacesDescriptionThey reflect the status of the E1 interfaces.The LED indication on the subsystem picture always corresponds with the LEDindication on the <strong>Crocus</strong> <strong>DXC</strong> itself. For more information on the interpretation ofthe LEDs, refer to Section 2.6 - Front panel LED indicators.They reflect which clocking mode is currently active.The LED indication on the subsystem picture always corresponds with the LEDindication on the <strong>Crocus</strong> <strong>DXC</strong> itself. For more information on the interpretation ofthe LEDs, refer to Section 2.6 - Front panel LED indicators.This reflects the status of the E1 interfaces. The possible indications are:ColourgreenredExplanationNo (unmasked) alarm of the e1Interface[ ] object is active.An (unmasked) alarm of the e1Interface[ ] object is active.The colours of the E1 interfaces only change if the alarms related to thee1Interface[ ] object are set to enabled in the alarmMask. Refer to Section 6.4 - E1interface configuration attributes.112 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Firmware download11 Firmware downloadThis chapter explains how to download new firmware into the flash memory of the <strong>Crocus</strong> <strong>DXC</strong>. Thefollowing table gives an overview of this chapter.Section Title Page11.1 Downloading with TMA 11411.2 Downloading with TML 11511.3 Downloading in boot mode 11611.4 Downloading via a management concentrator 117Reference manual 113


Firmware download<strong>Crocus</strong> <strong>DXC</strong>11.1 Downloading with TMATo download firmware with TMA, proceed as follows:StepAction1 Establish a link between TMA and the <strong>Crocus</strong> <strong>DXC</strong> through the control connector. Referto Section 4.1 - Starting a TMA session on the <strong>Crocus</strong> <strong>DXC</strong>.2 In the TMA window select Tools ! Download…3 In the TMA – Download window, select theOptions tab.Here it is a good practice to set the initialtransfer speed to 9600 bps.If you set the maximum transfer speed to115200 bps, the actual transfer speed will benegotiated between the computer and the<strong>Crocus</strong> <strong>DXC</strong> and will be between 9600 bpsand 115200 bps.4 In the TMA – Download window, select the Configuration tab, and press Add…5 In the Remote filename window:1. Select the filename you want todownload (Txxxxxxx.00).2. Type CONTROL in the Remote filefield.3. Press Open.6 When the TMA – Download window reappears, press OK.⇒ A DOS window opens and shows the download progress.114 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Firmware download11.2 Downloading with TMLWhen downloading with TMA (as explained in the previous section), you actually evoke TML (TelindusMemory Loader) through TMA. You can also use TML without opening TMA.To download firmware with TML, proceed as follows:StepAction1 Connect a serial port of your computer(e.g. COM1) through a straight DB9male - female cable with the controlconnector of your <strong>Crocus</strong> <strong>DXC</strong> asshown in the following figure:2 Open a DOS window on your computer.3 Go to the directory where the TML executable is located. Typically this isC:\Program Files\TMA.4 Place the firmware file you want to download in this directory.5 Type the following command: tml -c1 –v -f@CONTROLwhere …• tml is the executable (Telindus Memory Loader) to download files to the Telindusdevices through their control port• -c1 specifies the COM port of the computer connected to the <strong>Crocus</strong> <strong>DXC</strong> (in thisexample COM1)• -v returns graphical information on the download status• -f is the firmware file you want to download (e.g. T1212001.00)• CONTROL (in capitals!) specifies that the destination is a flash bank of the <strong>Crocus</strong><strong>DXC</strong>.To see a list of all the possible TML options: type TML in your DOS windows and pressthe ENTER key.6 If you press the ENTER key, the firmware download begins.If you used the –v option together with the TML command, a graphical bar shows thedownload progress.Reference manual 115


Firmware download<strong>Crocus</strong> <strong>DXC</strong>11.3 Downloading in boot modeWhen a flash memory software download has failed or when a flash memory error occurs, it may bepossible that the <strong>Crocus</strong> <strong>DXC</strong> becomes inaccessible. In that case, new software can still be downloadedby setting the <strong>Crocus</strong> <strong>DXC</strong> in boot mode. This is done by means of the start-up mode DIP switch.The location of the start-up mode DIP switch is:DIP switch name DS1 no. Setting Functionstart-up mode1 on Start up from flash memory.offStart up in boot mode.The <strong>Crocus</strong> <strong>DXC</strong> can be forced in boot mode by setting DIP switch bank DS1 position 1 to off. If a newsoftware download is successfully completed, the DIP switch must be reset to on in order to restartoperation from flash memory.Note that this DIP switch setting cannot be overruled by TMA.To download firmware to a <strong>Crocus</strong> <strong>DXC</strong> in boot mode, proceed as follows:StepAction1 Disconnect the <strong>Crocus</strong> <strong>DXC</strong> from the power supply.2 Set DIP switch bank DS1 position 1 to off.To locate this DIP switch bank and for the DIP switch setting procedure, refer to Chapter3 - DIP switches and straps of the <strong>Crocus</strong> <strong>DXC</strong>.3 Reconnect the power supply to the <strong>Crocus</strong> <strong>DXC</strong>.⇒ The <strong>Crocus</strong> <strong>DXC</strong> is now in boot mode.4 Now proceed as explained in the previous section, Section 11.2 - Downloading withTML.5 When the download is finished, disconnect the <strong>Crocus</strong> <strong>DXC</strong> from the power supplyagain.6 Reset DIP switch bank DS1 position 1 to on.7 Reconnect the power supply to the <strong>Crocus</strong> <strong>DXC</strong>.116 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Firmware download11.4 Downloading via a management concentratorIf many <strong>Crocus</strong> <strong>DXC</strong> Card Version modems need a firmware update, it is more efficient to use thesoftware distribution feature of a management concentrator (e.g. the Orchid 1003 LAN or Telindus 1035Orchid). In that case, the firmware file that is present on the file system of the management concentratoris downloaded over the high speed bus to the <strong>Crocus</strong> <strong>DXC</strong> CV.Also the <strong>Crocus</strong> <strong>DXC</strong> CVs their remote counterparts (which are often Table Tops) can get a firmwareupdate using the management concentrator its software distribution feature.For more information, refer to the manual of the management concentrator.Reference manual 117


Technical specifications<strong>Crocus</strong> <strong>DXC</strong>12 Technical specificationsThis chapter gives the technical specifications of the <strong>Crocus</strong> <strong>DXC</strong>. The following table gives an overviewof this chapter.Section Title Page12.1 <strong>Crocus</strong> <strong>DXC</strong> types 11912.2 E1 interface 11912.3 Management interface 12012.4 Control connector 12012.5 Power requirements 12112.6 Mechanical dimensions 12112.7 Environmental compliance 12112.8 Safety compliance 12212.9 Over-voltage and over-current protection compliance 12212.10 EMC compliance 122118 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Technical specifications12.1 <strong>Crocus</strong> <strong>DXC</strong> typesThe basic types of the <strong>Crocus</strong> <strong>DXC</strong> are:• <strong>Crocus</strong> <strong>DXC</strong> 8• <strong>Crocus</strong> <strong>DXC</strong> 16Both types can be powered with either 230/115 Vac or -48 Vdc via the CN4 card nest.12.2 E1 interface• Connector: RJ45 (DTE)• Impedance: 120 ohm balanced• Physical and electrical compliance: ITU-T G.703• Cable to be used: 4*2*CAT5E shielded twisted pair• Coding: AMI or HDB3 (configurable)• Speed: 2 Mbps• Clocking: station, line or internal (configurable)• Framing: compliant to ITU-T G.704• Time slots: N x 64 kbps (N = 1 … 32)• CRC4 insertion: enabled or disabled (configurable), frame alignment and cyclic redundancy checkcompliant to ITU-T G.706• Defect detection: compliant to ITU-T G.775• Performance monitoring: compliant to ITU-T G.821 and G.826• Jitter and wander: compliant to G.823The following table shows the connector layout of the RJ45 E1 interface connector:Pin Signal Input / Output Figure1 receive A input2 receive B input3 signal ground -4 transmit A output5 transmit B output1 … 86 signal ground -7 not used -8 not used -Reference manual 119


Technical specifications<strong>Crocus</strong> <strong>DXC</strong>12.3 Management interfaceThe possible management interface connectors are:Management interface connector Connector type Speedasynchronous through the control connectorsynchronous through a managementconcentrator and the high speed bus9 pins subD(on the <strong>Crocus</strong> <strong>DXC</strong>)backplane DIN(on the CN4 card nest)9600 bps, 8+N800 kbpsFor all available management tools, refer to Section 1.4 - Management overview.12.4 Control connector• Connector: female DB9 labeled CTRL• Applicable standards: ITU-T V.24, V.28, EIA/TIA 574• Data:− asynchronous− 9600 bps− 8 data bits− no parity− 1 stop bit− no flow controlThe control connector has the following pin layout:Pin Signal Input / Output Figure1 - -2 NMS RxD output3 NMS TxD input4 not used -5 GND -6 not used -7 NMS RTS input8 NMS CTS output9 - -123456789120 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>Technical specifications12.5 Power requirementsThe power requirements for the different <strong>Crocus</strong> <strong>DXC</strong> types (8 and 16) are:Parameterinput voltagemaximum current @ -30 Vdcmaximum current @ -48 VdcDescription-48 Vdc (-30 Vdc ! -80 Vdc)195 mA165 mA12.6 Mechanical dimensionsThe mechanical dimensions are as follows:Dimensions <strong>Crocus</strong> <strong>DXC</strong> 8 <strong>Crocus</strong> <strong>DXC</strong> 16 CN4 Card Nestheight (mm) 25 50 270width (mm) 235 235 445 without rackmountsdepth (mm) 335 335 330weight (kg) 1 1 6.112.7 Environmental compliance• Storage conditions: ETSI ETS 300 019-1-1 Class 1.1. In addition, the storage temperature has to bebetween -25 to +70°C• Transport conditions : ETSI ETS 300 019-1-2 Class 2.3• Stationary use conditions: ETSI ETS 300 019-1-3 Class 3.2. In addition, the requirements belowapply:− relative humidity 5 to 95% non-condensing and ambient operational temperature -5 to 45°Cor− relative humidity 0 to 95% non-condensing and ambient operational temperature -10 to 50°C• Maximum altitude: 3000m• International protection (IP) class of protection against solid and liquids: IP20Reference manual 121


Technical specifications<strong>Crocus</strong> <strong>DXC</strong>12.8 Safety compliance• EN60950• Class 1 equipment for Table Tops with 115/230 Vac internal power supply.• Class 3 equipment for …− Table Tops with 115/230 Vac external power supply adapter− Table Tops with -48 Vdc internal power supply− Card Versions.12.9 Over-voltage and over-current protection complianceThe over-voltage and over-current protection complies with ITU-T K.44 and ETSI ETS 300 386-2recommendations.12.10 EMC compliance• EN55022 B Emissions• EN55024 Immunity• EN61000-3-2 Harmonics• EN61000-3-3 Voltage fluctuations and flicker• EN61000-4-2 ESD• EN61000-4-3 Radiated immunity• EN61000-4-4 EFT/burst• EN61000-4-5 Surge• EN61000-4-6 Conducted immunity• EN61000-4-8 Power magnetic field immunity• EN61000-4-11 Voltage dips & drops• ENV50204 Radiated immunity against digital radio telephone122 Reference manual


<strong>Crocus</strong> <strong>DXC</strong>AnnexesAnnexes 123


<strong>Crocus</strong> <strong>DXC</strong>124 Annexes


<strong>Crocus</strong> <strong>DXC</strong>Annex A: product informationAnnex A: product informationThe following table displays the product information of the <strong>Crocus</strong> <strong>DXC</strong> basic units.Sales code Product name Description167322 CROCUS <strong>DXC</strong> 8CV The <strong>Crocus</strong> <strong>DXC</strong> 8 CV (Digital Access Cross Connect)provides programmable non-blocking cross connectionbetween up to 8 fractional E1 or E1 interfaces. The crossconnection occurs per 64kbps channel. Uses 1 CN4 slot.167323 CROCUS <strong>DXC</strong> 16CV The <strong>Crocus</strong> <strong>DXC</strong> 16 CV (Digital Access Cross Connect)provides programmable non-blocking cross connectionbetween up to 16 fractional E1 or E1 interfaces. The crossconnection occurs per 64kbps channel. Uses 2 CN4 Slots.170219 MANUAL CROCUS <strong>DXC</strong> (E) Manuals are delivered with the product in electronic format(CD-ROM) for environmental reasons. If however a hardcopy(print-out) of the manual is required, this sales item can beused. Between brackets an indication of the language.Annexes 125

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!