Professional Documents
Culture Documents
Document properties
Subject Manual type Version Code Modification date Crocus SHDSL G703 User and reference manual 1.8 500871 13 November 2007 OneAccess
Copyright notice
The information and descriptions contained in this publication are the property of OneAccess. Such information and descriptions must not be copied or reproduced by any means, or disseminated or distributed without the express prior written permission of OneAccess. This publication could include technical inaccuracies or typographical errors, for which OneAccess never can or shall be held liable. Changes are made periodically to the information herein; these changes will be incorporated in new editions of this publication. OneAccess may make improvements and/or changes in the product(s) described in this publication at any time, without prior notice.
Safety requirements
Carefully read the safety instructions, installation precautions and connection precautions as stated in chapter 2 - Installing and connecting the Crocus SHDSL G703 on page 13.
Statements
www.oneaccess-net.com/telindus Products choose a product Downloads Certificates
Hereby, OneAccess declares that this Crocus SHDSL G703 complies with the essential requirements and other relevant provisions of Directive 1999/5/EC. Hierbij verklaart OneAccess dat deze Crocus SHDSL G703 overeenstemt met de essentile vereisten en andere relevante bepalingen van Richtlijn 1999/5/EC. Par la prsente, OneAccess dclare que ce Crocus SHDSL G703 est en conformit avec les exigences essentielles et autres articles applicables de la Directive 1999/5/EC. Hiermit, OneAccess erklrt da dieser Crocus SHDSL G703 in Fgsamkeit ist mit den wesentlichen Anforderungen und anderen relevanten Bereitstellungen von Direktive 1999/5/EC. Mediante la presente, OneAccess declara que el Crocus SHDSL G703 cumple con los requisitos esenciales y las dems prescripciones relevantes de la Directiva 1999/5/CE. A OneAccess declara que o Crocus SHDSL G703 cumpre os principais requisitos e outras disposies da Directiva 1999/5/EC. Col presente, OneAccess dichiara che questo Crocus SHDSL G703 in acquiescenza coi requisiti essenziali e stipulazioni attinenti ed altre di Direttivo 1999/5/EC. OneAccess Crocus SHDSL G703 1999/5/EC.
Environmental information
The crossed-out wheeled bin means that within the European Union the product must be taken to separate collection at the product end of life. This applies to the device but also to any accessories marked with this symbol. Do not dispose of these products as unsorted municipal waste. If you need more information on the collection, reuse and recycling systems, please contact your local waste administration. You can also contact us for more information on the environmental specifications of our products. De doorgestreepte container wil zeggen dat binnen de Europese gemeenschap het product voor gescheiden afvalverzameling moet worden aangeboden aan het einde van de levensduur van het product. Dit geldt voor het toestel, maar ook voor alle toebehoren dia van dit symbool voorzien zijn. Bied deze producten niet aan bij het gewone huisvuil. Indien u meer informatie wenst over de systemen voor inzameling, hergebruik en recyclage, gelieve dan uw lokale afvaldiensten te contacteren. U kan ook ons contacteren wanneer u informatie wenst over de milieu aspecten van onze producten. Le symbole de la poubelle sur roues barre dune croix signifie que ce produit doit faire lobjet dune collecte slective en fin de vie au sein de lUnion Europenne. Cette mesure sapplique non seulement vorte appareil mais galement tout autre accessoire marqu de ce symbole. Ne jetez pas ces produits dans les ordures mnagres non sujettes au tri slectif. Si vous souhaitez plus d'information concernant les systmes de collecte, de rutilisation et de recyclage, veuillez contactez votre service de gestion de dchets local. Vous pouvez galement nous contacter pour obtenir plus dinformation au sujet des spcifications environnementales de nos produits. Das Symbol der durchgestrichenen Abfalltonne auf Rdern bedeutet dass das Produkt in der Europischen Union einer getrennten Mlsammlung zugefhrt werden muss. Dies gilt sowohl fr das Produkt selbst, als auch fr alle mit diesem Symbol gekennzeichneten Zubehrteile. Diese Produkte drfen nicht ber den unsortierten Hausmll entsorgt werden. Wenn Sie mehr Informationen brauchen ber die Sammlung und Recycling Systemen, bitte konsultieren Sie Ihre rtliche Abflle Verwaltung. Fr mehr Informationen ber die Umweltaspekten unserer Produkte, wenden Sie sich an unserer Kundendienst.
Preface v
Documentation set
The documentation set of the Crocus SHDSL G703 currently consists of the following: Document Crocus SHDSL G703 manual (this manual) Description This is the manual you are reading now. It shows you how to install and connect the Crocus SHDSL G703 and gives you a basic configuration. It also contains a complete description of all the configuration, status, performance and alarm parameters for look-up purposes. The Crocus SHDSL G703 can be maintained and managed by a variety of maintenance and management tools. Refer to 1.5 - Maintenance and management tools on page 9 for an introduction on these tools and for a reference to the manual of these tools. A wide variety of cables exist to connect the Crocus SHDSL G703. The Data cables document (PDF) and the Management cables document (PDF) describe these cables.
cable documents
Annex
Refer to the Table of contents on page x for a detailed overview of this manual.
Preface
Typographical conventions
The following typographical conventions are used in this manual: The format Normal Italic indicates normal text.
Computer
new or emphasised words application windows, buttons and fields. E.g. In the File name field enter
text you have to enter at the DOS or CLI prompt, computer output and code examples. E.g. NOK,1,1,Invalid command.
Computer Bold
text you have to enter at the DOS or CLI prompt when it is part of a mix of computer input and output. E.g.
/o1003:"Edit Configuration" >get sysName sysName = "Orchid 1003 LAN" /o1003:"Edit Configuration" >
Narrow
containment tree objects and attributes of a device when they are mentioned in the normal text. I.e. when they are not a part of computer input or output. E.g. Use the sysName attribute in order to
<Narrow>
containment tree objects or attributes or part of them that are variable. I.e. depending on the product version, used interface, etc. the names of these objects or attributes are slightly different. E.g. topObject/<modularIf>/someAttribute means that the name of the object <modularIf> depends on which modular interface you use. For example, v35 in case of a V.35 interface, g703 in case of a G.703 interface, etc.
Blue
references to other parts in the manual. E.g. Refer to xx - Title for more information.
Blue underline
a hyperlink to a web site. E.g. www.oneaccess-net.com a reference to another manual. E.g. Refer to the TMA manual (PDF) for more information. The abbreviation between brackets is an indication of the file format (PDF = Portable Document Format / CHM = Compiled HTML Help).
Preface vii
Graphical conventions
The following icons are used in this manual: Icon Name Remark Caution Warning DIP switch Basic attribute Advanced attribute Structured attribute Action This icon indicates remarks or useful tips. text to be read carefully in order to avoid damage to the device. text to be read carefully in order to avoid injury. a DIP switch or strap table. a basic attribute in the containment tree of the Crocus SHDSL G703. an advanced attribute in the containment tree of the Crocus SHDSL G703. a structured attribute within another attribute in the containment tree of the Crocus SHDSL G703. an action in the containment tree of the Crocus SHDSL G703.
Preface
The following table explains the DIP switch configuration table layout: Number 1 2 This position displays the DIP switch icon. the DIP switch name Example: Load default configuration 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 1 4 5 the possible settings of the DIP switch: on and off. The default setting is printed in bold. the function associated with the corresponding DIP switch setting.
The following table explains the attribute string layout: Number 1 2 3 This position displays the attribute icon. It indicates that the string which follows is an attribute string. Refer to Graphical conventions on page vii for more information. the attribute name and its position in the containment tree. the default value of a configuration attribute.
Preface ix
Hardware version
This manual describes the hardware of the Crocus SHDSL G703 PCB version 2.0 and higher.
Audience
This manual is intended for computer-literate people, who have a working knowledge of computing and networking principles.
Your feedback
Your satisfaction about this purchase is an extremely important priority to all of us at OneAccess. Accordingly, all electronic, functional and cosmetic aspects of this new unit have been carefully and thoroughly tested and inspected. If any fault is found with this unit or should you have any other quality-related comment concerning this delivery, please submit the Quality Comment Form on our web page at www.oneaccess-net.com/telindus Support.
Rating plate
For exact identification, you will find the model designation and serial number on the rating plate on the bottom of the housing. Please note this information here before installation in order to have it to hand in the event of queries or spare parts orders.
Table of contents
3 4
Table of contents xi
Table of contents
Index ........................................................................................................ 1
User manual
This chapter introduces the Crocus SHDSL G703. The following gives an overview of this chapter:
1.1
The Crocus SHDSL G.703 (Symmetric High Bit Rate Digital Subscriber Line) is a manageable baseband modem offering full 2,3 Mbps duplex transmission over unconditioned unshielded twisted-pair cable. A dedicated 2-pair version offers the possibility to extend the reach to longer distances or higher speeds (up to 4.6 Mbps). For extreme long distances, the equipment can fall back to a lower transmission rate, offering reduced speeds on the Fractional E1 (FE1) operation. The equipment is based on the TC-PAM (Trellis Coded Pulse Amplitude Modulation) modulation, which guarantees higher speeds and longer loop performance. It also guarantees spectral compatibility with legacy and ADSL transmission systems in the same cable bundle. The unit can be used in a point-to-point configuration, or can be used with a central solution based on card-nest 4 (CN4) or the OneAccess 2300. The Crocus SHDSL G.703 is available as a locally or remotely powered (RP) unit. The remotely powered unit can also be locally powered at -48VDC directly or by 230Vac through an external power adapter. The unit is designed for integration into demanding network environments and can be controlled by the complete set of network maintenance and management tools.
1.2
The following Crocus SHDSL G703 product versions exist: Crocus SHDSL product Crocus SHDSL TT RS530 Crocus SHDSL 2P TT RS530 Crocus SHDSL TT RS530 RP Crocus SHDSL 2P TT RS530 RP OneAccess 2300 SHDSL Series Crocus SHDSL 2P G703 CV TWIN-CN7 RP unframed Crocus SHDSL 2P G703 NX64K TWIN-CN7 RP Crocus SHDSL 2P G703 NX64K TWIN-CN7 Crocus SHDSL G703 NX64K TWIN-CN7 RP Crocus SHDSL G703 NX64K TWIN-CN7 These versions are described in the manual OneAccess 2300 SHDSL Series. These versions are described in the Crocus SHDSL CN7 manual. These versions are described in the manual Crocus SHDSL RS530. Crocus SHDSL BU Crocus SHDSL 2P BU Crocus SHDSL LCD BU Crocus SHDSL 2P LCD BU Crocus SHDSL TT G703 Crocus SHDSL 2P TT G703 Crocus SHDSL TT G703 RP Crocus SHDSL 2P TT G703 RP Crocus SHDSL INF G703 1P TT Vac Crocus SHDSL INF G703 1P TT NPWR Crocus SHDSL INF G703 1P TT RP Crocus SHDSL INF G703 2P TT Vac Crocus SHDSL INF G703 2P TT NPWR Crocus SHDSL INF G703 2P TT RP These versions are described in the manual Crocus SHDSL INF TT G703. These versions are described in the manual Crocus SHDSL G703. Manual These versions are described in the Crocus SHDSL manual.
The following table gives a description of the used abbreviations: Abbreviation 1P 2P 4P BU In full 1 pair 2 pair 4 pair Basic Unit Explanation This version has 1 line pair. This version has 2 line pairs. This version has 4 line pairs. This is the Crocus SHDSL basic unit.
Abbreviation TT
Explanation This version is a stand-alone version of the Crocus SHDSL G703. It is available with or without an LCD display and keyboard. This version is a card that has to be inserted into the CN4 card nest. The connections (power and line) are made through the CN4 card nest. This version is a card that has to be inserted into the CN4 card nest. It incorporates two Crocus SHDSL G703 modems on one card (hence the name Twin). As a result, one CN4 card nest can contain up to 30 modems. The connections (power and line) are made through the CN4 card nest. This version has to be powered with 115 or 230 Vac. This version has to be powered with -48 Vdc. This version can be powered with remote power (i.e. power coming from the central side, over the line). This version has a fixed G.703 DTE interface instead of an empty interface slot in which you can insert a modular interface. This version has a fixed RS530 DTE interface. This version is a card that has to be inserted into the CN7 card nest. The connections (power and line) are made through the CN7 card nest.
CV
Card Version
CV Twin
Volts - Alternate Current -48 Volts - Direct Current Remote Power G703 interface
RS530 CN7
1.3
This manual describes both the Crocus SHDSL G703 and Crocus SHDSL G703 RP version. The front panel of the Crocus SHDSL G703 (i.e. the non-RP version) and the Crocus SHDSL G703 RP are the same. However, you can identify them by looking at the back panel: Version Crocus SHDSL G703 Back panel Crocus SHDSL G703 RP 12 Vdc power connector RJ45/BNC 12 Vdc power connector 48 Vdc power connector RJ45/BNC
For a view of the back panels of both Crocus SHDSL G703 versions, refer to 2.6 - Connecting the Crocus SHDSL G703 Table Top on page 20. The Crocus SHDSL G703 (i.e. the non-RP version) can not be powered by remote power. Only use the Crocus SHDSL G703 RP version in a remote power setup.
1.4
Power back-off
The Crocus SHDSL G703 features power back-off. Power back-off is a part of the ITU-T G.991.2 SHDSL recommendation. It reduces the maximum transmit power level if the line conditions are sufficiently good to operate at a lower transmit level. Power back-off is performed by default (no configuration attribute). During the ITU-T G.994.1 handshake, the two sides of the line mutually agree on the transmit level. The transmit level is lowered between 0 and 6 dB in steps of 1dB. Important remark When 2 devices are connected point to point using the lowest speeds, an attenuation is always needed to get into data state, despite the power back-off mechanism. Connecting the devices with a cable of 1 meter for instance will not work. For the lowest speeds, a minimum distance of 2 kilometers (simulated or not) is required between the devices.
1.5
The Crocus SHDSL G703 is manageable in many different ways. This section gives a quick overview of the various maintenance and management tools. Maintenance or management tool TMA Description and reference
TMA (Total Maintenance Application) is a free Windows software package with a comprehensive graphical user interface that enables you to control the OneAccess products completely. I.e. to access their configuration attributes and look at status, performance and alarm information. Refer to 4 - Maintaining the Crocus SHDSL G703 on page 41 and the TMA manual (PDF) for more information.
TMA CLI
TMA CLI (TMA Command Line Interface) enables you to use its commands in scripts in order to automate management actions. This is particularly useful in large networks. Refer to the TMA CLI manual (PDF) for more information.
ATWIN
ATWIN is a menu-driven user interface. You can read and change all attributes as with TMA, but in a more basic, textual representation using a VT100 terminal. Refer to the Maintenance tools manual (PDF) for more information.
CLI
CLI is also a Command Line Interface, although not so extensive as TMA CLI. Experienced users who are familiar with the syntax can access the OneAccess devices more quickly than with TMA or ATWIN. Refer to the Maintenance tools manual (PDF) for more information.
TMA Element Management is a management application designed to monitor large numbers of OneAccess devices. It combines the easy to use graphical interface of the stand-alone version of TMA with an event-logging application called the Element Viewer. Refer to the TMA Element Management manual (PDF/CHM) for more information.
TMA for HP OpenView is the management application that runs on the widely spread network management platform HP OpenView. It combines the easy to use graphical interface of the stand-alone version of TMA with the advantages and features of HP OpenView. Refer to the TMA for HP OpenView manual (PDF) for more information.
You can manage the Crocus SHDSL G703 through SNMP using any SNMP browser. The Crocus SHDSL G703 supports MIB2 and a private MIB, including traps. The private MIB comes with your copy of TMA. After installation of the TMA data files, the private MIB file is available in directory C:\Program Files\TMA\snmp1 with the name <filename>.mib2. Refer to the documentation of your SNMP browser for more information.
Web Interface
The Web Interface is an ATWIN alike menu-driven user interface. You can read and change all attributes as with TMA, but in a more basic representation using a web browser. Refer to the Maintenance tools manual (PDF) for more information.
Easy Configurator
The Easy Configurator allows you to add HTML pages on top of the standard Web Interface by adding a set of specific files on the file system of the Crocus SHDSL G703. These files can be made either by OneAccess or by the customer itself. The goal is to offer a simple, custom made web interface which allows only to change or show those parameters that are relevant for a certain application or customer. Refer to the Maintenance tools manual (PDF) for more information.
1. The first part of the directory path may be different if you did not choose the default path during the installation of the TMA data files. 2. The filename is product dependent. To determine which MIB file corresponds with which product, refer to the models.nms file (located in C:\Program Files\TMA\model1).
1.6
The following table gives an overview of all the maintenance and management tools and how you can connect them with the Crocus SHDSL G703: Maintenance or management tool Tool - Crocus SHDSL G703 connection Serial2 Keyboard4 CLI ATWIN TMA TMA CLI TMA Element Management TMA for HP OpenView SNMP7 Web Interface8 Easy Configurator X5 X5 X X X5 X5 X X X6 X6 X X X X X X X9 IP3 Tool - management concentrator connection1 Serial2 IP3
1. Examples of management concentrators are the Orchid 1003 LAN, the OneAccess 1030 Router series, the OneAccess 2300 SHDSL series, etc. Refer to their corresponding manuals for more information on how to set these devices up as management proxy. 2. A serial connection is a connection between the COM port of your PC and the control connector of the device using a male-female DB9 cable. 3. An IP connection is a connection between your PC and the device over an IP network. 4. Connection with the Crocus SHDSL G703 is internal. Keyboard and LCD are not available on all models. 5. Using a VT100 terminal (emulation program). 6. Using Telnet. 7. Using an SNMP browser. 8. Using a web browser. 9. The proper XML files must be present on the file system of the management concentrator.
First this chapter gives some important safety instructions. Then it explains how to install and connect the Crocus SHDSL G703. You are advised to read this chapter in a sequential manner, from the beginning to the end, without skipping any part. By doing so, your Crocus SHDSL G703 will be completely installed and ready for configuration when you reach the end of this chapter. The following gives an overview of this chapter: 2.1 - Safety instructions on page 14 2.2 - Unpacking on page 15 2.3 - Selecting a site on page 16 2.4 - Wall mounting on page 17 2.5 - Installation and connection precautions on page 19 2.6 - Connecting the Crocus SHDSL G703 Table Top on page 20 2.7 - Remote power operation on page 25 2.8 - Using a repeater on page 29 2.9 - Front panel LED indicators on page 30
2.1
Safety instructions
IMPORTANT SAFETY INSTRUCTIONS Unplug the unit from the wall power outlet or remove it from the card nest before installing, adjusting or servicing. The safety of this unit depends upon the third pin (ground pin) of the 3-wire grounding type plug. Do not defeat this safety feature. If the power outlet at your site only has 2 pins, please consult a qualified electrician.
WICHTIGE SICHERHEITSINSTRUKTIONEN Vor smtlichen Arbeiten am Gert (Installation, Einstellungen, Reparaturen etc.) sollten Sie den Netzstecker aus der Steckdose ziehen. Die Sicherheit dieses Gertes ist abhngig von dem dritten Kontakt (dem Erdungspin) des 3-poligen Steckers. Beachten Sie unbedingt diese Sicherheitsstandard. Sollten Sie nur eine ltere 2-polige Steckdose zur Verfgung haben, lassen Sie diese von einem Elektriker gegen eine 3-polige Steckdose auswechseln.
SAFETY WARNING To avoid damage to the unit, please observe all procedures described in this chapter.
SICHERHEITSBESTIMMUNGEN Um eine Beschdigung des Gertes zu verhindern, beachten Sie bitte unbedingt die Sicherheitsbestimmungen, die in diesem Abschnitt beschrieben werden. Ensure that the unit and its connected equipment all use the same AC power and ground, to reduce noise interference and possible safety hazards caused by differences in ground or earth potentials.
2.2
Unpacking
Checking the shipping carton Rough handling during shipping causes most early failures. Before installation, check the shipping carton for 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 in the future.
Package contents The box should contain the following items: Crocus SHDSL G703 TMA CD-ROM including the TMA software and appropriate model files and the User and Reference manual in PDF format. RJ45 to RJ12 adapter
Optionally (depending which sales item you ordered): 12 Vdc power connector and external power adapter 48 Vdc power connector
2.3
Selecting a site
WARNING Always 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 could damage the equipment.
ACHTUNG Stellen Sie das Gert niemals seitlich, sondern nur auf den Fen auf und achten Sie darauf, da die Lftungsschlitze an der Seitenverkleidung frei bleiben. Stapeln Sie nicht mehrere Gerte direkt bereinander, dies kann zu einem Hitzestau fhren. Install the unit in an area free of extreme temperatures, humidity, shock and vibration. Position it so that you can easily see and access the front panel and its control indicators. Leave enough clearance at the back for cables and wires. Position the unit within the correct distances for the different accesses and within 2m of a power outlet.
2.4
Wall mounting
The Crocus SHDSL G703 TT can be mounted on a wall. Proceed as follows: Step 1 Action Drill two holes in the wall, according to the following specifications: 2 diameter of the drill: 4 mm distance between the holes: 120 mm depth of the holes: at least 25 mm
Insert two wall plugs in the holes, with following specifications: diameter: 4 mm length: 20 mm
Screw two square hooks (steel zinc plated and white epox) in the plugs, with following dimensions:
4 5
Slide the Crocus SHDSL G703 over the hooks until it touches the wall. This is indicated with a in the figure below. Slide the Crocus SHDSL G703 down until it is firmly attached. This is indicated with b in the following figure.
The following figure illustrates how to mount the Crocus SHDSL G703 against the wall:
2.5
ESD WARNING The circuit boards are sensitive to electrostatic discharges (ESD) and should be handled with care. It is advisable to ensure an optimal electrical contact between yourself, the working area and a safety ground before touching any circuit board. Take special care not to touch any component or connector on the circuit board.
EMC WARNING The complete Crocus family and the CN4 card nest are fully EMC compliant. Because of the modular structure of the CN4 card nest, all unused slots (power slots, card slots and interface slots) have to be covered 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.
NOTE This unit may be powered by an IT Power System. The connectors of the Crocus SHDSL G703 should only be connected to the following circuit types: Connector name line management G703 interface Connector label line CTRL Connector type RJ45 subD RJ45/BNC Circuit type TNV-11 TNV-32 SELV SELV
1. Without Remote Power 2. With Remote Power SELV (Safety Extra Low Voltage): local connection (e.g. PC to Crocus SHDSL G703) or leased line inside the building. TNV-1 (Telecom Network Voltage): leased line outside the building. TNV-2: PSTN from PABX inside the building. TNV-3: PSTN from operator PABX outside the building.
2.6
This section explains how to connect the Crocus SHDSL G703 TT. The following gives an overview of this section: 2.6.1 - Table Top connections on page 21 2.6.2 - Connecting the power supply to the Table Top on page 22 2.6.3 - Signal and protective ground interconnection on page 23 2.6.4 - Connecting the line to the Table Top on page 24
2.6.1
All the connections have to be made at the back of the Table Top. Crocus SHDSL G703 (non-RP version)
The following table labels the different parts located at the back of the Crocus SHDSL G703: Label 12VDC 48VDC G703 CTRL LINE Part power inlet (12 Vdc / 48 Vdc) BNC / RJ45 interface connectors SUBD9 control connector RJ45 line connector
2.6.2
The following table explains how to connect the power supply. The TT exists in two different models: TT model -48 Vdc Connector type 48 V power supply connector Connecting the power supply For a -48 Vdc model, a power supply connector is delivered with the Crocus SHDSL G703.The + and - indications are with respect to each other, not to ground level. This means that for a standard -48 Vdc connection, the ground has to be connected to +, while the negative voltage has to be connected to the -.When the -48 Vdc power supply connector is wired, connect it to the power inlet. Refer to Crocus SHDSL G703 RP on page 21. Insert the plug of the 12 Vdc power adapter in the 12 Vdc power inlet.
12 Vdc
2.6.3
You can configure the interconnection between signal ground and protective ground (earth). Do this by means of the appropriate strap located on the TT motherboard. For more information, refer to 3.1.3 Straps of the TT on page 37.
2.6.4
In order to connect the line to the Table Top, proceed as follows: Step 1 Action If you have a line cable with an RJ45 connector, you can immediately plug one end of the cable in the line connector of the Crocus SHDSL G703. RJ12 connector, then first plug in the RJ45 to RJ12 adapter in the line connector of the Crocus SHDSL G703. Then plug one end of the cable in the adapter.
For more information on the line connector and adapter layout, refer to 13.2 - Line specifications on page 259 and 13.3 - RJ45 - RJ12 adapter specifications on page 261. 2 Plug the other end of the cable in the DSL outlet.
For optimum performance, the used line pairs have to be properly twisted pairs.
2.7
This section gives an overview of the remote power functionalities and indicates how to activate them. The following gives an overview of the section. 2.7.1 - What is remote power (RP)? on page 26 2.7.2 - Remote power operation overview on page 27 2.7.3 - Remote power sink operation: how to remote power the Crocus SHDSL G703 RP? on page 28
Important remarks The Crocus SHDSL G703 and RS530 (i.e. the non-RP version) can not be powered by remote power. Only use the Crocus SHDSL G703 RP and RS530 RP version in a remote power setup. When using remote power, certain limitations apply with regards to the number of Card Versions that can be inserted in the CN4, CN4-4 and CN4-2 rack; refer to 13.10 - Thermal behaviour when providing remote power on page 268. Not complying with these rules will result in irreversible damage to the device.
2.7.1
Remote powering means that a local modem (RP source modem) supplies operational power over the line to a remote modem (RP sink modem). Remote powering is in accordance with the ITU-T recommendation K.15.
The RP sink modem typically is dual powered. This means that it is either powered by a local power supply or by remote power over the line. If the local power supply fails, then the RP sink modem is still powered over the line by the RP source modem. As soon as the local power supply is reactivated, the RP sink modem is powered again by this power supply.
2.7.2
Some versions of the Crocus SHDSL family can work as remote power source, while others can only work as remote power sink. The following table gives an overview of the remote power functionality in the different Crocus SHDSL versions: Version Crocus SHDSL CV Crocus SHDSL TT Crocus SHDSL G703 TT Crocus SHDSL G703 TT RP Crocus SHDSL RS530 TT Crocus SHDSL RS530 TT RP Crocus SHDSL xP CV CN7 RP Crocus SHDSL Repeater RP source X X RP sink X X X
When using a TT device as remote power sink, no DIP switches or straps have to be adjusted in the device.
2.7.3
Remote power sink operation: how to remote power the Crocus SHDSL G703 RP?
The Crocus SHDSL G703 and RS530 (i.e. the non-RP version) can not be powered by remote power. Only use the Crocus SHDSL G703 RP and RS530 RP version in a remote power setup. The Crocus SHDSL G703 RP can be remotely powered in the following ways: A central CN4 with a Remote Power option board on a Crocus SHDSL CV Quad DXC / Crocus SHDSL CV.
For more information on how to set up remote powering in the configuration as depicted above, refer to the Crocus SHDSL CV Quad DXC manual. In this manual it is described how a Crocus SHDSL CV Quad DXC has to be configured for remote powering. A central OneAccess 2321 or 2323 with a Remote Power option board.
For more information on how to set up remote powering in the configuration as depicted above, refer to the OneAccess 2321/2323 manual. In this manual it is described how a OneAccess 2321/2323 has to be configured for remote powering.
2.8
Using a repeater
You can use the Crocus SHDSL Repeater to increase the maximum distance between two Crocus SHDSL modems.
There are however some issues to consider when using a repeater: The customer side (C-side) of the Crocus SHDSL Repeater always slaves on the network side (Nside). This means that the LTU or central modem has to generate a clock for the N-side of the Crocus SHDSL Repeater. Therefore the LTU or central modem can not be configured in slave-receive clocking. In case you have two Crocus SHDSL G703 2P (2 pair) versions, you can not use two Crocus SHDSL Repeater 1P (1 pair) version on each line pair. This does not work.
For more information on the Crocus SHDSL Repeater, refer to the Crocus SHDSL Repeater manual. Maximum 8 Crocus SHDSL repeaters can be used on a link.
2.9
This section gives an overview of the front panel LEDs and what they indicate. The following gives an overview of this section. 2.9.1 - Introducing the front panel LEDs on page 31 2.9.2 - Power LED (PWR, green) on page 32 2.9.3 - Data carrier detect LED (DCD/109, green) on page 32 2.9.4 - Serial LED (SERIAL, green) on page 32
2.9.1
When all the connections are made and the Crocus SHDSL G703is powered, the LEDs on the front panel reflect the actual status of the Crocus SHDSL G703. The figure below shows the front panel LED indicators of the Crocus SHDSL G703:
Front panel LED status modes For some front panel LED indicators (TST, AIS ERR and DCD) different status modes exist. These status modes can be distinguished by the way the LED lights up: LED status continuously off continuously on blinking flashing monitoring LED duty cycle 0% 100% 50% 20% Description The LED never lights up. The LED lights up continuously. The LED is as much lit as it is out. The LED only lights up during 20% of the time. The LED lights up irregularly. For instance, it lights up on detection of a certain signal. I.e. it monitors this signal.
2.9.2
This LED indicates the power state of the Crocus SHDSL G703: LED status on flashing Description The Crocus SHDSL G703 is powered locally. The Crocus SHDSL G703 is powered remotely.
2.9.3
This LED indicates whether the central Crocus SHDSL G703 is in synchronisation with the remote SHDSL device. Three different modes can be distinguished: LED status off blinking on Description No signal is detected on the line. A training cycle between central and remote SHDSL device is in progress. The central and remote SHDSL devices are synchronised. A data link is present.
In case of a Crocus SHDSL G7032P two DCD LEDs are present, one for each line pair.
2.9.4
This LED indicates the state of the Crocus SHDSL G703 interface: LED status on off Description The Crocus SHDSL G703 interface is up. The Crocus SHDSL G703 interface is down.
This chapter locates the DIP switches and straps on the Crocus SHDSL G703 motherboard. It gives an overview of their function and it explains how to change their settings. The following gives an overview of this chapter. 3.1 - DIP switches and straps on page 34
3.1
This section locates the DIP switches and straps on the TT motherboard. It gives an overview of their function and it explains how to change their settings. Disconnect the Crocus SHDSL G703 from the mains before you open the housing to change DIP switch and/or strap settings. The following gives an overview of this chapter. 3.1.1 - The TTmotherboard on page 35 3.1.2 - DIP switches of the TT on page 36 3.1.3 - Straps of the TT on page 37 3.1.4 - Changing DIP switch and strap settings of the TT on page 39
3.1.1
The TTmotherboard
The figure below shows the position of the DIP switches and straps on the TT motherboard.
3.1.2
The following table gives an overview of DIP switch bank DS1 of the TT: DIP switch name loader mode DS1 no. 1 Setting on off load default configuration 2 on off Function Normal operation. Start up in loader mode. Normal operation. Load default configuration.
For more information on DIP switch and strap location on the TT motherboard, refer to 3.1.1 - The TTmotherboard on page 35. changing DIP switch and strap settings on the TT, refer to 3.1.4 - Changing DIP switch and strap settings of the TT on page 39.
3.1.3
Straps of the TT
Strap ST1 Using strap ST1 you can configure the interconnection between signal ground and protective ground (earth): ST1 strap position 1-2 Connection disconnected (default) Description By default, the signal ground is disconnected from the earth. This avoids problems which might occur when the earth potential of the Crocus SHDSL G703 and the connected application is not the same. In such a situation earth current loops may induce distortion on the transmitted data, resulting in transmission errors. Sometimes it is not possible to connect the application directly to the earth. In that case you can earth the application through the Crocus Crocus SHDSL G703 by connecting the Crocus SHDSL G703 to the earth and setting strap ST1.Also the opposite situation might occur: it is not possible to earth the Crocus SHDSL G703. In that case you can earth the Crocus SHDSL G703 through the application by connecting the application to the earth and setting strap ST1.
2-3
directly connected
Straps ST3, ST4 and ST5 Using straps ST3, ST4 and ST5 you can select which connector you want to use: the RJ45 connector or the BNC connectors. choose whether the shield of the TX-IN BNC connector is connected to the PGN or not. Function RJ45 (default) ST3 strap position 2-3 ST4 strap position 2-3 ST5 strap position 2-3
1-2
1-2
1-2
1-2
1-2
2-3
For more information on DIP switch and strap location on the Crocus SHDSL G703 motherboard, refer to 3.1.1 - The TTmotherboard on page 35.
changing DIP switch and strap settings on the Crocus SHDSL G703, refer to 3.1.4 - Changing DIP switch and strap settings of the TT on page 39.
3.1.4
To change the DIP switch and/or strap settings of the Crocus SHDSL G703, proceed as follows: Step 1 2 3 Action Switch the Crocus SHDSL G703 off. Disconnect the Crocus SHDSL G703 from the mains. Unscrew the two screws located at the back of the Crocus SHDSL G703.
Remove the cover as follows: 1. Carefully lift the back of the cover a few centimetres. 2. Gently pull the cover backwards from under the nose of the Crocus SHDSL G703.
5 6 7 8 9
Change the DIP switch and/or strap settings. Replace the cover and close tight. Fasten the two screws located at the back of the Crocus SHDSL G703. Reconnect the Crocus SHDSL G703 to the mains. Switch the Crocus SHDSL G703 on.
Once you installed the Crocus SHDSL G703, you can proceed with the configuration. You can do this using any of the management tools introduced in 1.6 - Maintenance and management tools connection possibilities on page 11. This chapter briefly highlights two of those management tools: the Total Maintenance Application (TMA). It gives an introduction and describes how to start a management session on the Crocus SHDSL G703. Furthermore, it also introduces the terminology concerning the management of a OneAccess device. The following gives an overview of this chapter. 4.1 - Starting TMA on the Crocus SHDSL G703 on page 42 4.2 - Introducing the management attributes of the Crocus SHDSL G703 on page 47
4.1
This section introduces the Total Maintenance Applications (TMA). Then it explains how you can start a TMA session on the Crocus SHDSL G703. The following gives an overview of this section: 4.1.1 - Introducing TMA on page 43 4.1.2 - Starting a TMA session through the control connector on page 44 4.1.3 - Starting a TMA session through a management concentrator on page 46
4.1.1
Introducing TMA
What is the Total Maintenance Application? TMA is a free Windows software package that enables you to maintain the Crocus SHDSL G703, i.e. to access its configuration attributes and look at status, performance and alarm information using a user friendly graphical user interface. TMA is an excellent tool for complete management of the OneAccess access devices. When using TMA in combination with a network management system such as HP OpenView, complete networks can be managed 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 of the Crocus SHDSL G703. The most recent model files can always be downloaded from the OneAccess web site at www.oneaccess-net.com/telindus/downloads Download Center. How to connect TMA? There are two ways to establish a connection between the computer running TMA and the Crocus SHDSL G703: over a serial connection, through the control connector of the Crocus SHDSL G703. over an IP or a serial connection, through a management concentrator.
4.1.2
To establish a connection between the computer running TMA and the Crocus SHDSL G703 through the control connector, proceed as follows: Step 1 Action Connect a serial port of your computer (e.g. COM1) through a straight DB9 male - female cable with the control connector of the Crocus modem. Start TMA. 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 device button:
2 3
The Connect (to a device) window is being displayed as in the following figure:
In the Connect (to a device) window, configure the following parameters: Select the option Serial, and specify the COM port of your computer the Crocus SHDSL G703 is connected to. If a password has previously been configured in the Crocus SHDSL G703 then also fill in the password field.
If the necessary parameters are filled in, press the Next > button.
Step 6
Action 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 being displayed as in the following figure:
In order to connect to the local Crocus SHDSL G703, choose On device. the remote Crocus SHDSL G703, choose After device and enter relative NMS address 1 or higher.
If a password has previously been configured in the Crocus SHDSL G703 then also fill in the password field. 8 9 If the necessary parameters are filled in, press the Finish button. After a couple of seconds, the attributes of the selected Crocus SHDSL G703 appear in the TMA window.
4.1.3
On central locations with many access devices, the Crocus SHDSL G703 can be connected to a management concentrator (e.g. Orchid 1003 LAN or 1035 Orchid). In this case the management concentrator is a proxy device for the Crocus SHDSL G703. This means you can connect TMA to the Crocus SHDSL G703 through the management concentrator. What is more, the management concentrator can act as an IP proxy device for the Crocus SHDSL G703. The IP address related to the Crocus SHDSL G703 is defined in the management concentrator. Refer to the manual of the management concentrator for more information on the configuration and management capabilities of this device.
4.2
This section gives an introduction to the management attributes of the Crocus SHDSL G703. It introduces terms such as containment tree, group, object, attribute, value and action. The following gives an overview of this section: 4.2.1 - Containment tree terminology on page 48 4.2.2 - The Crocus SHDSL G703 containment tree on page 50 4.2.3 - Crocus SHDSL G703 attribute overview on page 51
4.2.1
The following figure depicts the TMA window containing the Crocus SHDSL G703 containment tree.
The following table explains the terminology associated with the containment tree. Term containment tree Description The containment tree represents the hierarchical structure of the Crocus SHDSL G703. It is composed of a number of objects that are ordered in a tree. This tree resembles a Windows directory structure: object 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.
An object represents a physical interface, an application or a combination of both. Each object has its own set of attributes. Example: The top object crocusShdslTtRpG703 contains the sub object line. On its turn, the sub object line contains the sub object linePair [1]. This object contains all the attributes concerning the line pair. E.g. the status attribute lineAttenuation (dB).
attribute
An attribute is a parameter related to a certain object. It has a certain value. Example: The object line contains the attribute channel, which has the values central and remote.
value
An 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 channel can be set to the value central or remote. structured value Some attribute values contain underlying values: a structured value. These values are displayed in the structured value window. If an attribute contains structured values then a bit string, <Table> or <Struct> is displayed after the attribute. Example: The alarmLevel attribute contains a structured value which displays alarms and their corresponding priority level. group Groups assemble a set of attributes related by functionality. There are four groups in TMA, which correspond with the four tabs in the attribute window: action configuration status performance alarms.
A group in combination with an object may have actions assigned to them. These actions are displayed in the action window. Example: The Cold Boot action only appears when the top object crocusShdslTtRpG703 is selected in combination with the group Configuration.
4.2.2
The following table lists the different objects of the Crocus SHDSL G703 containment tree. Object > crocusShdslTtRpG703 This object contains the general system attributes. It is the top object in the containment tree. E.g. the status attribute sysUpTime: 00005d 02h 53m 16s. >> line the general line attributes. E.g. the configuration attribute channel. >>> linePair[ ] the specific line pair attributes. E.g. the status attribute lineAttenuation (dB). >> g703 the DTE interface attributes of the G703 interface. E.g. the configuration attribute clocking. >> management the network management attributes. E.g. the configuration attribute consoleNoTrafficTimeOut. >> operatingSystem the operating system attributes. E.g. the performance attribute currUsedProcPower (%). >> fileSystem the file system attributes. E.g. the status attribute fileList
4.2.3
The reference part of this manual explains all the attributes of the Crocus SHDSL G703. One chapter describes one 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.
Step-by-step configuration
This chapter describes in a step-by-step manner how to perform a basic configuration on Crocus SHDSL G703. You are advised to read this chapter in a sequential manner, from the beginning to the end, without skipping any part. By doing so, your Crocus SHDSL G703 will be completely configured and ready for use when you reach the end of this chapter. The following gives an overview of this chapter. 5.1 - Configuring the basic line parameters on page 54 5.2 - Configuring EOC handling on page 57 5.3 - Configuring the timing mode on page 64 5.4 - Clocking of Crocus devices to access PDH and SDH networks on page 65 5.5 - Configuring the clocking mode on page 82 5.6 - Configuring the minimum line speed on page 87 5.7 - Configuring framing and time slots on page 93 5.8 - Low speed limitations on the G703 interfaces on page 97 5.9 - Configuring the interface specific attributes on page 98 5.10 - Configuring the management attributes on page 99 5.11 - Configuring passwords on page 111 5.12 - Executing configuration actions on page 113 5.13 - Troubleshooting the Crocus SHDSL G703 on page 118 5.14 - Crocus SHDSL G703 compatibility with other SHDSL devices on page 119
For a complete overview of the attributes of the Crocus SHDSL G703, refer to the reference manual.
5.1
crocusShdslTtRpG703/line/channel
The channel attribute defines which modem is the central and which the remote modem. I.e. it determines which modem acts as master and which as slave during the synchronisation procedure of the modem. The default channel setting of a TT is remote, while that of a CV is central. Therefore there will never be a synchronisation problem when a CV and a TT are used in a regular set-up, the CV at the backbone side and the TT at the customer side. If two TTs are used at each end of the data link, make sure to change the channel attribute of one of the TTs into central. If two CVs are used at each end of the data link, make sure to change the channel attribute of one of the CVs into remote.
crocusShdslTtRpG703/line/region The region attribute defines which S-HDSL standard is used: Value annexA annexB auto Description The American S-HDSL standard is used. The European S-HDSL standard is used. The S-HDSL standard is selected automatically.
For compatibility with other SHDSL devices, setting this attribute to the correct value might be essential. Refer to 5.14 - Crocus SHDSL G703 compatibility with other SHDSL devices on page 119.
crocusShdslTtRpG703/line/mode
This attribute is only present on the Crocus SHDSL G703 2P (2 pair) version. Use the mode attribute to select between single pair or dual pair operation.
When you change the mode attribute, then make sure that you use the correct speed attribute to set the user speed: If the mode attribute is set to singlePair, dualPair, then use the attribute speed to configure the user speed. speed2P to configure the user speed.
crocusShdslTtRpG703/line/eocChannel
Use the eocChannel attribute to determine how the checksum of Embedded Operations Channel (EOC) messages is calculated. Make sure that on both the central and the remote device the eocChannel attribute is set to the same value. The eocChannel attribute has the following values: Value proprietary itu-G.991.2 Description The checksum is calculated using a proprietary method. The checksum is calculated using the G.SHDSL standard method.
For compatibility with other SHDSL devices, setting this attribute to the correct value might be essential. Refer to 5.14 - Crocus SHDSL G703 compatibility with other SHDSL devices on page 119.
5.2
This section explains what EOC is. Then it explains how you can configure the handling of the EOC messages. Finally, it discusses which information is retrieved depending on the setting of the eocHandling attribute. The following gives an overview of this section. 5.2.1 - What is EOC? on page 58 5.2.2 - The EOC handling attribute on page 59 5.2.3 - Discovering devices on the SHDSL line on page 60 5.2.4 - EOC retrieved information on page 60
5.2.1
What is EOC?
SHDSL devices can communicate with each other through the Embedded Operations Channel (EOC). For instance the Crocus SHDSL G703 can send the following types of EOC requests: inventory, to get information (manufacturer, release, etc.) about the remote SHDSL device, enable / disable network loop-backs on the remote SHDSL device, retrieve statistics or failure information (SNR Margin, loop attenuation, number of CRC errors, etc.).
5.2.2
crocusShdslTtRpG703/line/eocHandling Use the eocHandling attribute to define the handling of the EOC messages. The eocHandling attribute has the following values: Value passive Description
In this mode, the Crocus SHDSL G703 will never send any spontaneous standard EOC messages. It will only answer to standard EOC requests coming from the other side. Also, after getting into datastate, no OneAccess specific EOC data will be sent the first 2 minutes, unless the device has received a OneAccess specific frame from the other side (e.g. o10 data, or a test or configuration frame). Use this value when the Crocus SHDSL G703 is connected to the 2300.
none
The Crocus SHDSL G703 does not send any spontaneous EOC requests, except for discovery probes, they are still sent. The Crocus SHDSL G703 will also answer to EOC requests coming from other SHDSL devices. The Crocus SHDSL G703 "scans" the SHDSL line. For every device it discovers, it adds an object to the containment tree. Refer to 5.2.3 - Discovering devices on the SHDSL line on page 60. Then the Crocus SHDSL G703 retrieves information from these devices and displays it in the corresponding objects. Exactly which information is retrieved depends on the setting of the eocHandling attribute. Refer to 5.2.4 - EOC retrieved information on page 60. Also in this case the Crocus SHDSL G703 "scans" the SHDSL line, adds the objects to the containment tree and retrieves information from the devices. Refer to 5.2.3 - Discovering devices on the SHDSL line on page 60 and 5.2.4 - EOC retrieved information on page 60. Additionally, the central1 SHDSL device forces the remote2 SHDSL device and any intermediary repeater to use the link alarm thresholds lineAttenuation and signalNoise as configured on the central device in the attribute line/linkAlarmThresholds. In other words, the settings of the lineAttenuation and signalNoise on the central device overrule those of the remote device and repeaters. Refer to crocusShdslTtRpG703/line/linkAlarmThresholds on page 140 for more information.
alarmConfiguration
1. The central device is the device on which the channel attribute is set to central. 2. The remote device is the device on which the channel attribute is set to remote.
5.2.3
When you change the eocHandling attribute from none to any other value, the Crocus SHDSL G703 starts "scanning" the SHDSL line in order to determine which devices are present between itself and its remote counterpart. When the scan is finished, some new objects are added to the containment tree on the same level as the line object: If one or more repeaters are present on the SHDSL line, a repeater[ ] object is added for every repeater. For the remote counterpart, an end object is added.
The new objects are not added instantaneously. It can take up to 5 minutes before these objects appear in the containment tree. For example, suppose you have a link with a Crocus SHDSL G703 as central device, a 1421 SHDSL Router as remote device and one Crocus SHDSL G703 Repeater in between. Suppose you set the eocHandling attribute to discovery. In that case the one repeater[ ] object and an end object is added to the containment tree as can be seen in the screenshot:
The first discovered repeater will have id 3, the second one will have id 4, etc.
5.2.4
As said before, exactly which information is retrieved from the remote SHDSL device(s) through the EOC channel depends on the setting of the eocHandling attribute. This section gives an overview in which case which information is retrieved: EOC status information, refer to EOC status information. EOC performance information, refer to EOC performance information. EOC alarm information, refer to EOC alarm information.
Does the attribute or element display relevant information in case eocHandling is set to ?
User manual
Object crocusShdslTtRpG7 03/ No. The value is always 0.0. Yes. Yes. On the remote2: no. The value is always 0.0. On the central1: yes. The values are those as set in the linkAlarmThresholds attribute.
Attribute (Element)
line
eocAlarmThresholds
(lineAttenuation, signalNoise)
Yes. The values are those as set in the linkAlarmThresholds attribute on the central device.3
numDiscoveredRepeaters
repeater[ ]
vendorId
or No. No. No. Yes. Yes. Yes. No. The value is always 0.0. Yes. Yes. Yes.
end
vendorModel
vendorSerial
vendorSoftVersion
eocSoftVersion
shdslVersion
eocState
eocAlarmThresholds
Yes. The values are those as set in the linkAlarmThresholds attribute on the remote device.
Yes. The values are those as set in the linkAlarmThresholds attribute on the central device.
repeater[ ]/linePair[ ]
lineAttenuation
or
signalNoise
Step-by-step configuration
Chapter 5 61
end/linePair[ ]
Yes. The values are the actual line attenuation and signal noise as measured on the remote device.
1. The central device is the device on which the channel attribute is set to central. 2. The remote device is the device on which the channel attribute is set to remote. 3. Refer to 5.2.2 - The EOC handling attribute on page 59 for more information on the alarmConfiguration value.
Does the attribute or element display relevant information in case eocHandling is set to ?
User manual
Object crocusShdslTtRpG7 03/ No. The value is always 0.0. Yes. The values are the same as those on the remote device.
Attribute
repeater[ ]/linePair[ ]
lineParameters
or
performance
end/linePair[ ]
h2LineParameters
h2Performance
h24LineParameters
Note that in this case the sysUpTime is not the elapsed time since the last cold boot, but the elapsed time since the creation of the repeater[ ] or end object.
h24Performance
d7LineParameters
d7Performance
Chapter 5
Step-by-step configuration
Does the attribute or element display relevant information in case eocHandling is set to ?
User manual
Object crocusShdslTtRpG7 03/ The thresholds as configured in the linkAlarmThresholds attribute on the local device are used to generate the alarms.
Attribute
line/linePair[ ]
lineAttenuation
signalNoise
The thresholds as configured in the linkAlarmThresholds attribute on the central1 device are used to generate the alarms2.
repeater[ ]/linePair[ ] No alarms are generated. The thresholds as configured in the linkAlarmThresholds attribute on the local device are used to generate the alarms.
lineAttenuation
or
signalNoise
end/linePair[ ]
The thresholds as configured in the linkAlarmThresholds attribute on the central device are used to generate the alarms.
errSecExceeded
sevErrSecExceeded
The thresholds as configured in the linkAlarmThresholds attribute on the local device are used to generate the alarms. Step-by-step configuration
1. The central device is the device on which the channel attribute is set to central. 2. Refer to 5.2.2 - The EOC handling attribute on page 59 for more information on the alarmConfiguration value.
Chapter 5 63
5.3
crocusShdslTtRpG703/line/timingMode Use the timingMode attribute to set the timing mode. The Crocus SHDSL G703 has two clock sources: one takes care of the clocking on the SHDSL line. one takes care of the clocking on the modular user interface.
Using the timingMode attribute you can define whether these two clocks run independent from each other (i.e. plesiochronous mode) or whether they are "coupled" with each other (i.e. synchronous mode). The timingMode attribute has the following values: Value plesiochronous Description In this mode each SHDSL frame has 0 or 4 stuffing bits to compensate clock deviations towards the user interface clock. In this mode, all possible clocking modes can be selected. In this mode the SHDSL frame does not have stuffing bits to compensate clock deviations towards the user interface clock. In this case only internal and slave receive clocking is allowed. What is more, internal clocking is only allowed at one side of the link (e.g. the central side) and slave receive clocking at the other side (e.g. the remote side). Synchronous mode is the typical timing mode in DSLAM set-ups.
synchronous
If you set the framing attribute to framed, then the Crocus SHDSL G703 always operates in plesiochronous mode regardless of the setting of the timingMode attribute. You always have to work in the same timing mode at both sides of the link. In other words: central: synchronous - remote: synchronous allowed central: plesiochronous - remote: plesiochronous allowed central: synchronous - remote: plesiochronous or vice versa not allowed
For compatibility with other SHDSL devices, setting this attribute to the correct value might be essential. Refer to 5.14 - Crocus SHDSL G703 compatibility with other SHDSL devices on page 119.
5.4
This section explains the principles of network clocking and is a guideline for configuring the Crocus SHDSL G703 to interface to the carrier networks. A good knowledge and understanding about clocking mechanisms is essential to correctly build error free synchronous networks, connecting end users to PDH and SDH infrastructures. As this section gives a general explanation about clocking, section 5.5 - Configuring the clocking mode on page 82 actually describes how to configure the clocking mode on the Crocus SHDSL G703. The following gives an overview of this section: 5.4.1 - Introduction on page 66 5.4.2 - Network clocking principles on page 67 5.4.3 - The Plesiochronous Digital Hierarchy (PDH) networks on page 68 5.4.4 - The Synchronous Digital Hierarchy (SDH) networks on page 70 5.4.5 - Access to PDH networks on page 73 5.4.6 - Access to SDH networks on page 76 5.4.7 - Synchronous interfaces on page 80
5.4.1
Introduction
Since transmission and switching in carrier networks has become digital, network synchronisation has an increasing importance in telecommunications. Basically there was no need for network synchronisation to interconnect analogue switching machines over digital transport networks. Transmission equipment based on the Plesiochronous Digital Hierarchy (PDH) must not be synchronised, it allows multiplexing of asynchronous channels with substantial frequency offsets using the bit justification technique. When digital switching machines such as ISDN exchanges and cross-connect switches were introduced, problems arose with asynchronous architectures as PDH because digital switching equipment requires to be synchronised in order to avoid slips. By the introduction of the circuit switched data networks, there was a need of more stringent synchronisation requirements. In the 90s, the ongoing spreading of Synchronous Digital Hierarchy (SDH) technology in transmission networks has created a need for adequate network synchronisation facilities. For this reason, network operators have set up synchronisation networks. In this section, clocking principles for access to and data transfer over PDH and SDH transmission networks are explained.
5.4.2
Central clock To guarantee good synchronisation in digital networks, all network elements are synchronised to a central 2.048 kHz clock with long term accuracy. This central clock is generated by a high precision Primary Reference Clock (PRC) with an accuracy of 1x10-11 or better with verification to Coordinated Universal Time (UTC) as specified in ITU-T Recommendation G.811. A PRC can be realised as an autonomous clock or can be controlled by UTC-derived precision signals received from a radio or satellite system (GPS). Hierarchical structure To distribute this clock through the network, a hierarchical structure is defined in ITU-T standards G.812 & G.813. Refer to the following figure:
The PRC is transported via the clock network to the slave units. This clock signal is regenerated in the SSUs and SECs with the aid of phase-locked loops (PLLs). If the clock supply fails, the slave unit applies the stored frequency correction to keep a relatively accurate clock signal. The clock signal paths through the network can be the same as those used for the data transport. Station clock Modern synchronisation networks are based on the concept of a building clock, this is a slave clock unit as the SSUs and SECs, that supplies timing to all the equipment deployed in that location, including digital exchanges, cross-connects, terminal equipment and multiplexers. This clock signal is what we call station clock.
5.4.3
Asynchronous tributaries PDH systems allow multiplexing of asynchronous tributaries with substantial frequency offsets based on bit justification. Therefore PDH networks do not need to be synchronised. Every equipment clock is independent from the others, but their frequencies are kept close to the nominal values within a specified tolerance (for example: +/- 50 ppm at 2 Mbit/s). PDH systems are transparent to the timing content of the transported digital signals. This means that, despite the fact that the multiplexer clocks are independent, the transported signal keeps its frequency, only gathering some jitter due to transmission lines and justification. The bit justification technique allows to transfer the timing content of a digital signal across a transmission chain where clocks are asynchronous, as shown in the figure below.
Timing Because E1 signals coming from PCM multiplexers or cross connect switches need to be synchronised to avoid slips, this equipment is enslaved to a master clock, delivered by a Primary Reference Clock (PRC) via the clock synchronisation network. The synchronous E1 signals are multiplexed into asynchronous E2 and further on in E3 and E4 signals. E2, E3 and E4 are asynchronous multiplex signals with the 2M timing signal embedded. This allows transferring 2 Mbps timing across PDH networks to synchronise clocks located in far locations.
Gateways By the introduction of the PDH infrastructure, two different multiplex stages were defined: one based on a primary rate of 2 Mbit/s and one based on 1,5 Mbit/s as used in North America and Japan. Gateways between these networks were very difficult and expensive to realize. Disadvantages Inherent to plesiochronous transport is the generation of important jitter and wander at the tributary interfaces. Another disadvantage of PDH is that, once multiplexed, there is no simple way to extract an E1 bearer without fully demultiplexing down from the E4 level towards E1, requiring a complete hierarchy of multiplexers.
5.4.4
SDH hierarchy To eliminate the disadvantages of the PDH infrastructure, the SDH hierarchy was developed, bringing the following advantages: high transmission rates, up to 10 Gbit/s over fiber optic links more efficient and flexible add & drop function high availability, reliability and robustness multi-service platform: able to handle PSTN, ISDN, Frame Relay, ATM, IP, etc. interfaces are globally standardized, easier to interconnect carriers
The basic SDH frame is called a Synchronous Transport Module (STM-N), in which heterogeneous asynchronous and synchronous tributary channels as PDH and ATM can be mapped. Frame speeds can be between 52 Mbit/s and 10 Gbit/s. The basic package unit for tributary channels is the container C-n. For each PDH speed a special container is provided. These containers are much larger than the payload to be transported, the remaining capacity is used for justification.
Network elements Current SDH networks are build with four different types of network elements: regenerators: regenerate the clock and amplitude relationships of the incoming data signals.
terminal multiplexers: combine asynchronous and synchronous input signals into higher bit rate STMN signals.
add & drop multiplexers: asynchronous and lower speed synchronous signals can be extracted from or inserted into higher speed SDH bitstreams.
digital cross-connects (DXC): allows mapping of PDH channels in SDH virtual containers as well as switching of various containers.
Synchronisation In networks using SDH transport infrastructure, not only primary rate multiplexers and switching equipment are synchronized, but also the nodes of the SDH transport network, limiting jitter and wander generation at the interfaces.
Redundant ring structures SDH infrastructures typically are hybrid communication networks, build in redundant ring structures with various asynchronous and synchronous tributaries as in the example below.
5.4.5
Synchronisation on the same clock As the 2 Mbps and Nx64 Kbps signals in the PDH networks are synchronized on the 2.048 kHz Primary Reference Clock, also all access devices must be synchronized on the same clock. This can be done by applying the network clock to the station clock input of the devices or by operating in external clock. Therefore these interfaces are synchronous, allowing transporting clock from one device to another. Clock signals can be transferred separately from the data signals (e.g. station clock) or can be encoded in the data, as done in the G.703 interfaces which are typically used to connect to PDH/SDH infrastructures.
Typical Nx64 Kbps connections to a PDH infrastructure are shown below. As the backbone imposes the clock, the equipment connected to the network necessarily operates in external or station clock, the end points in slave receive. In external clock, the modem clock is derived from the incoming G.703 signal, in case of station clock, the clock signal is transferred separately.
The Crocus SHDSL QUAD DXC is perfectly suitable to be used in PDH environment as it can use the station clock or can slave on one of the four E1 interfaces. The most convenient configuration is to use the station clock as master and fallback to the E1 interfaces if the station clock fails.
If no station clock is available, the QUAD has to search for a clock on the E1 interfaces as shown in the next picture.
5.4.6
Asynchronous or synchronous Channel inputs on Add & Drop Multiplexers in SDH networks can be asynchronous or synchronous. The most common way to connect PDH tributaries to ADMs is asynchronous, also for the 2.048 Kbps signals, without giving a clock at his interfaces. This implicates that, when we interconnect two end-users over a SDH backbone, the clock must be generated by other means. This can be the station clock, derived from the PRC, or an internal clock generator from one of the transmission devices, such as modems, or by the end user application. This clock generator must operate within the required specifications regarding accuracy and stability, for example +/- 50 ppm at 2.048 Kbps. Typical 2 Mbit/s connections Some typical 2 Mbit/s connections to a SDH infrastructure are shown below. It is clear that the clock configuration at the end-points depends on the type of used interfaces and the end-user equipment.
Modems with integrated cross-connect functionalities Special attention must be paid in case modems with integrated cross-connect functionalities are used. As a DXC supports only one clock to synchronize all ports, all modems connected to the DXC must use this same clock. In this case the use of the station clock is strongly advised. Refer to the figure below for an example.
Accessing SDH networks - examples Below some examples of topologies to access SDH networks are given, using different types of access equipment. To keep the drawings orderly, the ADM symbols are skipped. It must be clear that these drawings are just some examples and do not exclude many other clock configurations and combinations in access topologies. Example 1: accessing SDH networks using the Crocus SHDSL QUAD DXC
When using the Crocus SHDSL QUAD DXC, only one clock can be used by all interfaces of this card. As shown below, this clock can be the station clock or the internal clock. All end-to-end connections running over the QUAD are slaved on this clock: Using the station clock:
As in an SDH network the connections are made to an ADM and not to a DXC, clock slaving on the E1 ports of the SHDSL QUAD is not recommended and this also means that end-user equipment should not generate the clock.
In case a Crocus SHDSL CV or 2300 is installed, each interface may have an independent clocking, allowing end-user equipment to generate the clock. Using a Crocus SHDSL CV:
Using a 2300:
5.4.7
Synchronous interfaces
Data transfer On a synchronous interface, data transfer between DTE and DCE is done at the rhythm of a clock signal. This timing signal is used to sample the transmit data in the transmitter of the DCE. The transmitter also uses this timing signal to modulate his carrier in case of a voice band modem or to encode the data in case of a baseband modem. This means that the clock frequency of the transmit clock is transported by the line signal to the remote end. The transport of the synchronous user data over the link can be synchronous or plesiochronous.
In the receiver at the remote end, the line signal is demodulated or decoded and receive clock is derived from the received line signal. By doing this, the receive clock has the same frequency as the transmit clock at the other side of the link. In this way the transmitter at one side and the receiver at the other side of the link are perfectly synchronized.
Exchange of clock signals The way clock signals are exchanged between DTE and DCE depends on the type of interface: V24, V35, V36, RS530, HSSI: these interfaces have separated clock signals to synchronize transmit (TxClk or ExClk) and receive (RxClk) data:
X21 interface uses only one clock signal (S or X) to synchronize both transmit and receive data:
G703 interface uses codirectional timing, this means that clock information is encoded in the data signal:
5.5
This section explains how to configure the clocking mode on the Crocus SHDSL G703. It also explains how the auto clocking mechanism works. The following gives an overview of this section. 5.5.1 - Configuring the clocking mode on the Crocus SHDSL G703 on page 83 5.5.2 - Schematic overview of the different clocking modes for G703 type of interfaces on page 84 5.5.3 - Possible clocking modes versus DTE interface on page 86
5.5.1
The location of the clocking attribute in the Crocus SHDSL G703 containment tree is: crocusShdslTtRpG703/g703/clocking Use the clocking attribute to select a clocking mode. The following table gives an overview: Clocking mode internal Description The Crocus SHDSL G703 generates the transmit clock signal and sends it to the application via the R circuit. Internal clocking mode implies that the applications on both sides of the link should be in slave receive clocking mode. In other words, there can be only one master clock in a G703 system. The application takes its timing from the network. The extracted clock is sent together with the TxD over the T circuit to the DCE. If no valid receive clock is found while in external clock mode, the modem switches to internal clock mode. Default:external Range: internal/external
external
5.5.2
Schematic overview of the different clocking modes for G703 type of interfaces
One encoded signal As G703 interfaces are codirectional interfaces, they transport both data and clock in the same encoded signal. On this way they can transport clock information from a higher network level to a lower network level in the digital hierarchy. For this reason, the default configuration of G703 interfaces is external clock. G703 interfaces are typically used to give access to carrier backbones and to interconnect backbone equipment such as cross-connect switches (DXC), TDM multiplexers and PABXs in PDH infrastructures. In these networks, only one master clock is allowed to synchronize all devices at the E1 level (2.048 kbps). Crocus SHDSL TT vs. Crocus SHDSL CV On a Crocus table-top modem, the G703 interface can be configured for internal or external clock operation. A card version modem also supports the use of a station clock that can be applied via the backplane of the cardnest. When station clock is selected, also a backup clock can be provided in case the station clock is not present. Clock functionalities Depending on the type of equipment, the clock functionalities can differ: when multiple modems and multiple interfaces are available on the same device, there is a main difference in clock functionalities depending on the fact of a DXC feature is present or not. If no DXC is present, the clocking on all interfaces is independent and so we may have different clocking on each interface (Crocus SHDSL TWIN, 2300). In case a DXC is present only one clock is allowed for all interfaces (Crocus SHDSL QUAD DXC).
Crocus SHDSL TT The figures below show the relationships between clock and data in the different configurations for the Crocus SHDSL TT:
5.5.3
The following table gives an overview of the clocking modes which are available on the different Crocus SHDSL devices: EXT LOOPBACK SLV RCV PREF Device SLV RCV ALT
INT PREF
STATION X X X
SLV RCV
INT ALT
Crocus SHDSL TT Vxx/RS530/X21 G703 DUAL PORT ROUTER Crocus SHDSL TWIN CV Vxx/RS530/X21 G703 DUAL PORT ROUTER Crocus SHDSL TT G703 Crocus SHDSL TT RS530 Crocus SHDSL QUAD CV DXC 23002 X X X X X X X X X X X X X1 X X X X X X X X X X X X X X X X X X X X X X X X X X
1. EXT on the Crocus SHDSL QUAD CV DXC means that the modem can be slaved on one of the E1 interfaces 2. Clocking parameters on the 2300 refers to the receive clocking, refer to the 2300 manual for more information
AUTO X
LINE
EXT
INT
5.6
This section starts with an important remark on setting the minimum line pair speed. Then it explains how to configure a minimum line speed and what the purpose is of doing this. The following gives an overview of this section: 5.6.1 - Important remark on the minimum line pair speed on page 88 5.6.2 - The minimum line pair speed attribute on page 89 5.6.3 - Purpose of the minimum line pair speed on page 92
5.6.1
If you configure the minimum line pair speed (i.e. you set the minLinePairSpeed attribute to any value different from <opt>), then only one master clock is allowed in the system. In other words, only the following clocking combinations are allowed: One side internal external external station Other side always slave receive slave receive external (provided the application on both sides use the same network clock) station or slave receive
Executing an ET test on both sides will not work in case both sides change their clocking modes to internal! Example The following is a perfectly legal set-up as long as the minimum line pair speed is not configured (i.e. minLinePairSpeed = <opt>):
However, if you set the minimum line pair speed to a value higher than the user speed, then the SHDSL line operates in slotted E1 mode. In that case, only one master clock is allowed in the system. So you would have to change the configuration to, for example:
In these general examples, serial interfaces are used, but the principle stays the same for G703 interfaces.
5.6.2
Also see 5.6.1 - Important remark on the minimum line pair speed on page 88. The location of the minimum line pair speed attribute in the Crocus SHDSL G703 containment tree is: crocusShdslTtRpG703/line/minLinePairSpeed Use the minLinePairSpeed attribute to determine what the minimum speed on the line pair has to be when the Crocus SHDSL G703 trains. The purpose of this is: To be able to set the line speed independently from the user speed. This allows easy upgrading to a higher user speed. To be able to use less than 3 time slots (or 6 time slots on a 2 pair version). Default:<opt> Range: 192kbps up to 2048kbps (in steps of 64kbps)
The minLinePairSpeed attribute has the following values: Value <opt> Description The line speed follows the user speed. For example, if the user speed is set to 640 kbps (speed(2P) = 640kbps), then the speed on the line pair equals 192kbps up to 2048kbps (in steps of 64kbps) 640 kbps in case of a Crocus SHDSL G703 1P (1 pair) version. 320 kbps on each line pair in case of a Crocus SHDSL G703 2P (2 pair) version.
The line speed no longer follows the user speed. The line trains on the speed as set with the minLinePairSpeed attribute. For example, if the user speed is set to 640 kbps (speed(2P) = 640kbps) and the minimum line speed is set to 1024 kbps (minLinePairSpeed = 1024kbps), then the speed on the line pair(s) equals 1024 kbps. (On a Crocus SHDSL G703 1P (1 pair) version this is also the total line speed. On a Crocus SHDSL G703 2P (2 pair) version, however, the total line speed then is 2048 kbps since the minLinePairSpeed attribute sets, as the name implies, the minimum speed on the line pair.) Remark Note that the maximum total line speed that you can set using the minLinePairSpeed attribute is 2048 kbps. So for a Crocus SHDSL G703 1P (1 pair) version you can set the minLinePairSpeed attribute to its maximum value (being 2048 kbps). For a Crocus SHDSL G703 2P (2 pair) version, however, you can only set it up to 1024 kbps (which is a total line speed of 2048 kbps). If you nevertheless set the minLinePairSpeed attribute to a value higher than 1024 kbps, then a message is displayed in the messages table and the Crocus SHDSL G703 2P continues to operate with a total line speed of 2048 kbps.
Make sure that you set the minLinePairSpeed attribute to the same value on both the central and remote SHDSL device. When using the minLinePairSpeed attribute on the central or remote SHDSL device, the user speed of the other device may not be set to autospeed.
5.6.3
Easily upgrading the user speed You could determine in advance what the maximum speed is that can be achieved on the line (e.g. 1024 kbps) and set the minimum line pair speed to this value (e.g. minLinePairSpeed = 1024kbps). Suppose the customer initially wants 256 kbps. So you set the user speed to 256 kbps (speed(2P) = 256kbps). Now when the customer decides he wants a higher user speed (e.g. 640kbps), then you can easily change the user speed to this higher speed (e.g. speed(2P) = 640kbps) without first having to determine again whether the line can handle this speed. What is more, the line does not have to retrain after you changed the user speed. So you can perform user speed upgrades in an easy, cost-efficient way. Low speed operation - compatibility with other SHDSL devices If you want to use only 1 or 2 time slots (or 2 or 4 time slots in case of a 2 pair version), then you have to set the minimum line pair speed to 192 kbps (minLinePairSpeed = 192kbps). This to insure correct time slot synchronisation on both sides. Low speed operation - 2 time slots and 2 applications If you want to use only 2 time slots (or 4 time slots in case of a 2 pair version) and each time slot carries the data of a different application, then you also have to set the minimum line pair speed to 192 kbps (minLinePairSpeed = 192kbps). This to insure that on the remote side the data is separated correctly. The reason is the following: In case you select only 2 time slots (or 4 time slots in case of a 2 pair version) but you do not configure the minimum line pair speed (minLinePairSpeed = <opt>), then the SHDSL line operates in Nx64 mode (refer to crocusShdslTtRpG703/line/framerType on page 166 for more information on this mode). Since in this case the user data has become a continuous bit stream on the SHDSL line, it is almost impossible to correctly separate the data from the two different applications at the remote end. In case you select only 2 time slots (or 4 time slots in case of a 2 pair version) but you configure the minimum line pair speed to be 192 kbps (minLinePairSpeed = 192kbps), then the SHDSL line operates in slotted E1 mode (refer to crocusShdslTtRpG703/line/framerType on page 166 for more information on this mode). Since in this case the user data is also put in time slots on the SHDSL line, it is perfectly possible to separate the data from the two different applications at the remote end.
5.7
This section explains how to select the framing mode and how to allocate time slots on a Crocus SHDSL G703. The following gives an overview of this section: 5.7.1 - Selecting unframed or framed mode on page 94 5.7.2 - Selecting the time slots on page 95 5.7.3 - Time slot transposition on page 96
5.7.1
crocusShdslTtRpG703/g703/framing Use the framing attribute to select between unframed or framed mode: Value unframed Description
In unframed (or transparent) mode, a 2 Mbps data stream is sent transparently over the line. The attributes timeSlots and crc4Insertion are of no use in unframed mode.
framed
In framed (G.704 framing) mode and in case of a Crocus SHDSL G703 1P (1 pair), up to 32 time slots each containing a 64 kbps data stream can be sent over the line. Each 64 kbps time slot can be enabled or disabled. Crocus SHDSL G703 2P (2 pair), up to 16 time slots pairs together containing a 128 kbps data stream can be sent over the line. Each 128 kbps time slot pair can be enabled or disabled. I.e. you always have to select an even number of time slots. E.g. 2, 4, 10, etc.
Remark If you set the framing attribute to framed, then the Crocus SHDSL G703 always operates in plesiochronous mode regardless of the setting of the timingMode attribute.
auto
If after the training sequence the chosen line speed is 2 Mbps, then the G703 interface automatically works in unframed mode. lower than 2 Mbps, then the G703 interface automatically works in framed mode. Which timeslots will be used, depends on the line speed and the timeslots configured in the timeslot attribute: If the line speed is lower than the configured timeslots, then the corresponding number of timeslots starting from the lowest configured will be used. If the line speed is higher than or equal to the configured timeslots, only the configured timeslots will be active.
In all cases the timeslot attribute in the status group reflects the timeslots used. Important remark In case of a Crocus SHDSL G703 2P (2 pair) version, set the framing attribute of either the central or remote Crocus SHDSL G703 to auto, but not of both. Else the 2 line pairs could train at a different speed which is not allowed. The number of selected timeslots must be higher then or equal to the line speed to have a good configuration.
5.7.2
crocusShdslTtRpG703/g703/timeSlots Use the timeSlots attribute to enable or disable the individual 64 kbps time slots in the framed data stream. By default, timeslot 0 is disabled and timeslots 1 up to 31 are enabled. Important remark
Do not enable time slot 0 in the local Crocus SHDSL G703 and a non-G703 interface in the remote Crocus SHDSL G703. The Crocus SHDSL G703 does not work on line speeds 64 and 128 kbps (i.e. 1 and 2 time slots) in case of a 1 pair version. 128 and 256 (i.e. 2 and 4 time slots) in case of a 2 pair version.
When line speeds 64 or 128 kbps are selected, the modem will train on 192 kbps (3 time slots). So when one timeslot is selected, the line will train on 192 kbps and there will be two dummy time slots added on the line. When line speeds 64 or 128 kbps are selected, the modem will train on 192 kbps (3 time slots), while only one timeslot can be selected on the G703 interface. When an ET test is started at the side where auto framing (with all timeslots enabled) is set, the pattern of the ET test will be placed in 3 timeslots, and not in the one selected timeslot.
5.7.3
If at both sides of the link a G703 Nx64k interface is used, it is possible to perform a time slot transposition. Such a transposition is realised by setting the G703 Nx64k in framed mode and enabling at both sides the time slots which have to be transposed. The first time slot at the local side will be put in the first time slot at the remote side, the second in the second, and so on. Example:
In this example, TS6 of the local Crocus SHDSL G703 is put in TS10 of the remote Crocus SHDSL G703, TS12 in TS16 and TS25 in TS26. A similar mechanism exists in the receive direction. The following figure shows the time slot transposition mechanism:
5.8
When configuring low speed on the G703 interfaces, there are some limitations. The following tables give an overview of the possible speeds on the G703 interfaces while combining different G703 interfaces. The first table gives all the combinations for the 1 pair SHDSL devices, while the second table gives the combinations for the 2 pair SHDSL devices. 1 Pair version 1 Pair version Crocus SHDSL G703 G703 Crocus SHDSL G703 +G703 Nx64K N=3,4, 32 Crocus SHDSL G703 +Dual Port if Crocus SHDSL G703 +Nx64K if 1421 SHDSL Router in plesiochronous mode N=3,4, 32 1421 SHDSL Router in synchronous mode 2M fixed (unframed)
N=3,4, 32
N=3,4, 32
N=3,4, 32
N=6,8, 32
N=6,8, 32
5.9
crocusShdslTtRpG703/g703/coding Use the coding attribute to set the G703 interface encoding mode. Possible values are: Value ami hdb3 Description
Alternate Mark Inversion is selected. This is a bipolar code with no zero substitution. High Density Bipolar 3 is selected. This is a modified bipolar code.With HDB3 encoding, more than three consecutive zeroes occurring in the data are replaced 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. Most of the G703 applications use HDB3 encoding.
Use the crc4Insertion attribute to determine whether the CRC-4 (cyclic redundancy check) is recalculated before sending it to the interface. The CRC is used to check the data integrity on the G.703 connection. The crc4Insertion attribute has the following possible values: Value auto Description In auto mode, CRC-4 insertion is disabled enabled disabled if the data is unframed, enabled if the data is G.704 framed.
5.10
This section explains the management attributes of the Crocus SHDSL G703. These attributes allow you to make all 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 Crocus SHDSL G703 in a network. Then it explains the attributes that have an impact on the management of the Crocus SHDSL G703. Finally, it gives some examples of networks and how to configure the Crocus SHDSL G703 to make it accessible for the central management system. The following gives an overview of this section: 5.10.1 - Rules of thumb and remarks concerning management on page 100 5.10.2 - Using relative or absolute addressing on page 101 5.10.3 - Selecting the purpose of the control connector on page 102 5.10.4 - Forwarding management data to the line and control connector on page 103 5.10.5 - Configuring the management data on the line on page 105 5.10.6 - Configuring the management data on a G703 interface on page 106 5.10.7 - Example - management over the line and the control port on page 107 5.10.8 - Example - management over the line and the E1 interface on page 109
Changing the ctrlPortProtocol attribute causes the Crocus SHDSL G703 to reboot. When sending management information to the three management interfaces (the line, the G703 interface using SA bits, and the CTRL port), a problem may occur. Due to insufficient processing power of the Crocus SHDSL G703, it could occur that a device connected to the Crocus SHDSL G703 cannot be reached anymore (on management level). Conclusion is that sending management information to the three management interfaces simultaneously is not possible, due to lack of processing power of the Crocus SHDSL G703.
Remark * An extended management connection is realised with a crossed cable between the control connectors of the two OneAccess devices. You also have to set the ctrlPortProtocol attribute to the value management. absolute This type of addressing is meant for a network topology where the devices are not connected in-line on management level. I.e. when there is a digital multipoint device present (e.g. the Orchid DM). To enable absolute addressing, an address has to be specified in the device. Do this using the cms2Address attribute. The absolute addressing range goes from 1 up to 65535. Refer to crocusShdslTtRpG703/management/cms2Address on page 152. Absolute addressing
The setting of the ctrlPortProtocol attribute depends on what you connect to the control connector of the Crocus SHDSL G703. This is explained in the following table: Value management Description
Select this value if you want to connect the control connector of the Crocus SHDSL G703 to a management concentrator (e.g. the Orchid 1003 LAN or 1035 Orchid) for management purposes. the control connector of another OneAccess device using a crossed cable (i.e. back-to-back) in order to create an extended management link. For more information on extended management links, refer to Relative addressing on page 101 and Forwarding management information on page 103).
When connecting the control connector of the Crocus SHDSL G703 to a COM port of your computer, you can still open a TMA session on the Crocus SHDSL G703. However, you can not open a CLI or ATWIN session console Select this value if you want to connect the control connector of the Crocus SHDSL G703 to a COM port of your computer in order to manage the Crocus SHDSL G703 locally using TMA, CLI or ATWIN.
Enables or disables propagation of management information to the control port. This allows you to cascade management information through the control port towards another OneAccess device. The forwardTmaToCtrlPort attribute is only present on the TT. crocusShdslTtRpG703/forwardTmaToLine Enables or disables propagation of management information to the line. Default:enabled Range: disabled / enabled
If forwardTmaToLine is enabled, management data is sent over the line via a dedicated management channel towards the remote Crocus SHDSL. To determine which management data is forwarded over the line, refer to crocusShdslTtRpG703/line/management on page 142. If forwardTmaToLine is disabled, O10 management data can still be passed over the line: disabling forwardTmaToLine is not enough to avoid management loops. Forwarding management information The management system has been designed to provide access not only to the local Crocus SHDSL G703, but also to all remote Crocus SHDSL G703s or other OneAccess devices in a network.
If the attribute forwardTmaToLine is enabled on Crocus SHDSL G703 1, then management information can be propagated over the line (via a dedicated management channel) from Crocus SHDSL G703 1 in site A to Crocus SHDSL G703 2 in site B. If the attribute forwardTmaToCtrlPort is enabled on Crocus SHDSL G703 2 and if the control connector of Crocus SHDSL G703 2 is connected with a crossed cable (i.e. back-to-back) to the control connector of Crocus SHDSL G703 3, then the management information can also be propagated to Crocus SHDSL G703 3. If the attribute forwardTmaToLine is enabled on Crocus SHDSL G703 3, then the management information can even be propagated to the remote of Crocus SHDSL G703 3. Etceteras.
Use the management attribute to determine whether and which management data is forwarded over the line (also refer to crocusShdslTtRpG703/forwardTmaToLine on page 128 to enable or disable propagation of management information to the line). The management attribute has the following possible values: Value transparent o10Management Description No management data is forwarded over the SHDSL line. The data is passed transparently over the line. This forwards the proprietary OneAccess O10 protocol over the SHDSL line. This allows you to manage the remote SHDSL device (and possibly other OneAccess devices connected to the SHDSL device). This forwards path management information over the SHDSL line. This allows you to manage complete paths instead of managing individual devices (i.e. elements).For more information on path management, refer to the TMA Path Management manual. This forwards both the proprietary OneAccess O10 protocol as the path management information over the SHDSL line.
pathManagement
o10-PathManagement
Use the saBits attribute to determine whether and which management data is inserted in the SA-bits. If management data is inserted in the SA-bits, then it is inserted in SA registers SA5, SA7 and SA8. SA4 is used as a control register and contains bandwidth information. The saBits attribute has the following possible values: Value transparent o10Management Description No management data is inserted in the SA-bits. The SA-bits are passed transparently. This inserts the proprietary OneAccess O10 protocol in the SA-bits. This allows you to forward management data over the G703 interface in a similar way as you can over the line or the control port. This allows more flexibility in managing your network of OneAccess devices. This inserts path management information in the SA-bits. This allows you to manage complete paths instead of managing individual devices (i.e. elements). For more information on path management, refer to the Path Management manual. o10-PathManagement This insert both the proprietary OneAccess O10 protocol as the path management information in the SA-bits.
pathManagement
Note that forwarding management data over the G703 interface can be very slow. The speed lies between 200 and 2400 bps.
5.10.7 Example - management over the line and the control port
In the network depicted on the previous page, the control ports of the modems that reside in the same site are connected to each other. By doing so (and by setting the appropriate attributes as seen on the previous page), the management data can pass from one device to another, not only over the line but also over the control port. Special points of interest in this network are: You have to enable internalDmm on CV 1, because the management data has to be able to pass from modem B to modem A. By doing so, you are able to forward management data over the line to TT 3, control port to CV 2 (on a CV the control port is "linked" to modem A).
You have to enable internalDmm on CV 2, because the management data has to be able to pass from modem A to modem B. By doing so, you are able to forward management data over the line to both CV 3 modem A and B. You have to disable internalDmm on CV 3, else you have two possible paths towards the management system for CV 3. E.g. if you would enable internalDmm, then modem A could contact the management system either over the line and then through CV 2 modem A etc. or through CV 3 modem B, over the line and then through CV2 modem B etc.
In this case, you might get unexpected results. Therefore, make sure there is only one path towards the management system! You have to enable internalDmm on CV 4, because the management data has to be able to pass from modem A to modem B. By doing so, you are able to forward management data over the line to both CV 5 modem A and B. You have to disable internalDmm on CV 5, else you have two possible paths towards the management system for CV 5. Make sure there is only one path towards the management system!
In the network depicted on the previous page, the E1 interfaces of the modems that reside in the same site are connected to each other. By doing so (and by setting the appropriate attributes as seen on the previous page), the management data can pass from one device to another, not only over the line but also over the E1 interface. Special points of interest in this network are: On TT 2 and TT 4, you have to set the saBits to o10Management or o10-pathManagement. By doing so, you are able to forward management data over the E1 interface connection between TT 2 and TT 4. On TT 3, however, you have to set the saBits to transparent, because on CV 1 internalDmm is enabled. Else you have two possible paths towards the management system for CV 1 and all modems after CV 1: one path through TT 3, one path through TT4.
In this case, you might get unexpected results. Therefore, make sure there is only one path towards the management system! You have to enable internalDmm on CV 1, because the management data has to be able to pass from modem B to modem A. By doing so, you are able to forward management data over the line to TT 3, E1 interface connection between CV 1 modem A and CV 2 modem A.
On modem A of both CV 1 and CV 2, you have to set the saBits to o10Management or o10-pathManagement. By doing so, you are able to forward management data over the E1 interface connection between modem A of CV 1 and CV 2. On modem B of both CV 1 and CV 2, however, you have to set the saBits to transparent, because on CV 1 and CV 2 internalDmm is enabled. Else you have two possible paths towards the management system. Make sure there is only one path towards the management system! You have to enable internalDmm on CV 2, because the management data has to be able to pass from modem A to modem B. By doing so, you are able to forward management data over the line to both CV 3 modem A and B. You have to disable internalDmm on CV 3, because else you have two possible paths towards the management system for CV 3. E.g. if you would enable internalDmm, then modem A could contact the management system either over the line and then through CV 2 modem A etc. or through CV 3 modem B, over the line and then through CV2 modem B etc.
In this case, you might get unexpected results. Therefore, make sure there is only one path towards the management system! Etceteras.
5.11
Configuring passwords
This section shows you how to create a (list of) password(s) with associated access level in the security table. It also explains how to correct the security table in case of error or in case you forgot your password. Furthermore, this section shows you how to enter the passwords in the different maintenance tools. The following gives an overview of this section: 5.11.1 - Adding passwords to the security table on page 112 5.11.2 - Entering passwords in the different management tools on page 112
If no passwords are created, everybody has complete access. If you define at least one password, it is impossible to access the Crocus SHDSL G703 with TMA if you do not enter the correct password. If you create a list of passwords, you should create at least one with write and security access. If not, you will be unable to make configuration and password changes after activation of the new configuration.
5.12
This section shows you how to execute actions on the configuration. The following gives an overview of this section: 5.12.1 - What are the different configuration types? on page 114 5.12.2 - Activating the configuration on page 115 5.12.3 - Loading the default configuration on page 115 5.12.4 - The load default configuration action in TMA on page 116 5.12.5 - Loading the default configuration using a DIP switch on page 117
Explaining the configuration types When you configure the Crocus SHDSL G703, the following happens: Phase 1 2 Action Connect the computer running the maintenance tool to the Crocus SHDSL G703. Modify the non-active configuration. Result The non-active configuration is displayed on the screen. The modifications have no immediate influence on the active configuration currently used by the Crocus SHDSL G703. The non-active configuration has to be activated. The non-active configuration becomes the active configuration.
3 4
Complete the modifications on the nonactive configuration. In case of TMA, click on the TMA button Send all attributes to device: . any other maintenance tool than the graphical user interface based TMA (e.g. ATWIN, CLI, Web Interface, EasyConnect terminal, TMA CLI), then execute the Activate Configuration action.
Which are the configuration actions? You can execute the following actions on the configuration: crocusShdslTtRpG703/Activate Configuration on page 129 crocusShdslTtRpG703/Load Default Configuration on page 129 crocusShdslTtRpG703/Load Saved Configuration on page 130 crocusShdslTtRpG703/Cold Boot on page 130
any other maintenance tool than the graphical user interface based TMA (e.g. ATWIN, CLI, Web Interface, EasyConnect terminal, TMA CLI), then execute the Activate Configuration action.
The Crocus SHDSL G703 reboots and loads the default configuration.
4 Activate the loaded default configuration: 1. Open a management session (e.g. TMA, ATWIN, ) on the Crocus SHDSL G703. Refer to 4.1 - Starting TMA on the Crocus SHDSL G703 on page 42. 2. Execute the Activate Configuration action. 5 6 7 Again, disconnect the Crocus SHDSL G703 from the power supply. Reset the appropriate DIP switch to on (see step 2). Properly replace the cover as described in 3.1.4 - Changing DIP switch and strap settings of the TT on page 39 and reconnect the power supply.
5.13
If you experience trouble when installing, configuring or operating the Crocus SHDSL G703, then check the following: Check power connections Description Is the Crocus SHDSL G703 powered properly? Are all the necessary cables connected to the Crocus SHDSL G703? Are they connected to the correct connectors of the Crocus SHDSL G703? Are they connected properly? Did you use the correct cables (straight, crossed, )? Refer to 2.6 - Connecting the Crocus SHDSL G703 Table Top on page 20.
Are the devices that are connected to the Crocus SHDSL G703 working properly (are they powered, are they operational, )? What do the LEDs of the Crocus SHDSL G703 indicate? Do they indicate a fault condition? Refer to 2.9 - Front panel LED indicators on page 30
messages
What messages are displayed in the messages table? This table displays informative and error messages. Refer to crocusShdslTtRpG703/messages on page 160
status
What do the status attributes of the Crocus SHDSL G703 indicate? What is the status of the different interfaces (up, down, testing, )? Refer to 7 - Status attributes on page 155.
performance
What do the performance attributes of the Crocus SHDSL G703 indicate? What is the performance of the different interfaces (does the data pass the interface, is the interface up or down, when did it go up or down, )? Refer to 8 - Performance attributes on page 187.
alarms
What do the alarm attributes of the Crocus SHDSL G703 indicate? What is the alarm status of the different interfaces (link down, errors, )? Refer to 9 - Alarm attributes on page 207.
5.14
The Crocus SHDSL G703 can be used in combination with other (OneAccess) SHDSL devices. The document Interoperability for OneAccess SHDSL products (PDF) gives an overview of the interoperability.
Reference manual
Configuration attributes
This chapter discusses the configuration attributes of the Crocus SHDSL G703. The following gives an overview of this chapter. 6.1 - Configuration attribute overview on page 124 6.2 - General configuration attributes on page 126 6.3 - Line configuration attributes on page 131 6.4 - Line pair configuration attributes on page 145 6.5 - Repeater and end configuration attributes on page 147 6.6 - DTE Interface configuration attributes on page 148 6.7 - Management configuration attributes on page 151
6.1
> crocusShdslTtRpG703 sysName sysContact sysLocation security forwardTmaToCtrlPort forwardTmaToLine alarmMask alarmLevel remoteAlarmMask Action: Activate Configuration Action: Load Saved Configuration Action: Load Default Configuration Action: Cold Boot >> line channel region timingMode mode1 minLinePairSpeed retrain startupMargin testDuration asymmetricPsd eocChannel txEocMessages1 eocHandling numExpectedRepeaters linkAlarmThresholds management name alarmMask alarmLevel remoteAlarmMask repeaterAlarmMask repeaterAlarmLevel repeaterLinePairAlarmMask repeaterLinePairAlarmLevel endAlarmMask endAlarmLevel endLinePairAlarmMask endLinePairAlarmLevel
1. 2P version only
>>> linePair[ ]2 alarmMask alarmLevel remoteAlarmMask >> g703 name framingtimeSlotsclocking coding crc4InsertionaisDetection sqThreshold sqTime jitterAttenuation saBitsrdlDetect tests alarmMask alarmLevel >> remoteAlarmMaskmanagement cms2Address consoleNoTrafficTimeOut ctrlPortProtocol
2. in case of a 2P version, two linePair objects are present: linePair[1] and linePair[2]
6.2
This section describes the following configuration attributes: crocusShdslTtRpG703/sysName on page 127 crocusShdslTtRpG703/sysContact on page 127 crocusShdslTtRpG703/sysLocation on page 127 crocusShdslTtRpG703/security on page 127 crocusShdslTtRpG703/forwardTmaToCtrlPort on page 128 crocusShdslTtRpG703/forwardTmaToLine on page 128 crocusShdslTtRpG703/<configurationAlarmAttributes> on page 128
This section describes the following actions: crocusShdslTtRpG703/Activate Configuration on page 129 crocusShdslTtRpG703/Load Default Configuration on page 129 crocusShdslTtRpG703/Load Saved Configuration on page 130 crocusShdslTtRpG703/Cold Boot on page 130
crocusShdslTtRpG703/sysName This is a field where you can assign a name to the Crocus SHDSL G703. The field has a limit of 64 characters. This is a SNMP MIB2 parameter. crocusShdslTtRpG703/sysContact
This is a field where you can fill in the name of a contact person together with information on how to contact this person. The field has a limit of 64 characters. This is a SNMP MIB2 parameter. crocusShdslTtRpG703/sysLocation This is a field where you can fill in the physical location of the Crocus SHDSL G703. The field has a limit of 64 characters. This is a SNMP MIB2 parameter. crocusShdslTtRpG703/security
In order to avoid unauthorised access to the network and the Crocus SHDSL G703, you can create a list of passwords with associated access levels. The security attribute contains the following elements: Element password Description The password is a string of maximum 10 characters. Default:<empty> Range: 0 10 characters
accessRights
This attribute represents the access levels assigned Default:11111 to a password. It is a bit string whereof each bit corre- Range: bit string, see below sponds to an access level. The different access levels are: readAccess writeAccess securityAccess fileSystemAccess testAccess
The following table shows, for each access level, what you can or can not do: Access level readAccess writeAccess securityAccess fileSystemAccess testAccess Read attributes yes yes yes no yes3 Change attributes no yes yes no no Read security attributes1 no no yes no no Change security attributes1 no no yes no no Execute actions2 no yes yes no yes4 Access file system no no no yes no
1. The Crocus SHDSL G703 has the following security attributes: crocusShdslTtRpG703/sysName crocusShdslTtRpG703/security 2. Actions are e.g. Cold Boot, testActivation, retrain, etc. 3. It is possible to see status and performance attributes of the line object that are applicable to modem tests (AL, DL, RDL, ...). 4. It is possible to execute actions applicable to modem tests (AL, DL, RDL, ...).
crocusShdslTtRpG703/forwardTmaToCtrlPort
Enables or disables propagation of management information to the control port. This allows you to cascade management information through the control port towards another OneAccess device. The forwardTmaToCtrlPort attribute is only present on the TT. crocusShdslTtRpG703/forwardTmaToLine Enables or disables propagation of management information to the line. Default:enabled Range: enabled / disabled
If forwardTmaToLine is enabled, management data is sent over the line via a dedicated management channel towards the remote remote Crocus SHDSL. To determine which management data is forwarded over the line, refer to crocusShdslTtRpG703/line/management on page 142. If forwardTmaToLine is disabled, O10 managment data can still be passed over the line : disabling forwardTmaToLine is not enough to avoid management loops. For more information, refer to 5.10.4 - Forwarding management data to the line and control connector on page 103. crocusShdslTtRpG703/<configurationAlarmAttributes> For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask, alarmContactHighMask, alarmContactLowMask and on the alarms in general, refer to 9.2 - Introducing the alarm attributes on page 210. For more information on the alarms of the crocusShdslTtRpG703 object, refer to 9.3 - General alarms on page 218.
crocusShdslTtRpG703/Activate Configuration If you execute this action, the editable non-active configuration becomes the active configuration. When use this action? If you configure the Crocus SHDSL G703 using any other maintenance tool than the graphical user interface based TMA (e.g. ATWIN, CLI, Web Interface, EasyConnect terminal, TMA CLI), then execute the Activate Configuration action to activate the configuration after you finished configuring the Crocus SHDSL G703 or after you executed the Load Saved Configuration or Load Default Configuration action. TMA, then do not just execute the Activate Configuration action to activate the configuration after you finished configuring the Crocus SHDSL G703, but use the TMA button Send all attributes to device instead. You can, however, execute the Activate Configuration action after you executed the Load Saved Configuration or Load Default Configuration action.
crocusShdslTtRpG703/Load Default Configuration If you execute this action, the non-active configuration is overwritten by the default configuration. When use this action? If you install the Crocus SHDSL G703 for the first time, all configuration attributes have their default values. If the Crocus SHDSL G703 has already been configured but you want to start from scratch, then use this action to revert to the default configuration. In case of TMA, click on the TMA button Retrieve all attributes from device Configuration action to see the new non-active configuration. after executing the Load Default
crocusShdslTtRpG703/Load Saved Configuration If you execute this action, the non-active configuration is overwritten by the active configuration currently used by the Crocus SHDSL G703. When use this action? If you are in the progress of modifying the non-active configuration but made some mistakes, then use this action to revert to the active configuration. In case of TMA, click on the TMA button Retrieve all attributes from device Configuration action to see the new non-active configuration. crocusShdslTtRpG703/Cold Boot If you execute this action, the Crocus SHDSL G703 reboots. As a result, the Crocus SHDSL G703 performs a self-test. checks the software. reads the saved configuration and restarts program execution. after executing the Load Default
When use this action? Use this action, for instance, to activate new application software.
6.3
This section describes the following configuration attributes: crocusShdslTtRpG703/line/channel on page 132 crocusShdslTtRpG703/line/region on page 132 crocusShdslTtRpG703/line/timingMode on page 133 crocusShdslTtRpG703/line/mode on page 134 crocusShdslTtRpG703/line/minLinePairSpeed on page 135 crocusShdslTtRpG703/line/retrain on page 135 crocusShdslTtRpG703/line/startupMargin on page 138 crocusShdslTtRpG703/line/testDuration on page 138 crocusShdslTtRpG703/line/asymmetricPsd on page 138 crocusShdslTtRpG703/line/eocChannel on page 139 crocusShdslTtRpG703/line/txEocMessages on page 139 crocusShdslTtRpG703/line/eocHandling on page 139 crocusShdslTtRpG703/line/numExpectedRepeaters on page 139 crocusShdslTtRpG703/line/linkAlarmThresholds on page 140 crocusShdslTtRpG703/line/management on page 142 crocusShdslTtRpG703/line/name on page 142 crocusShdslTtRpG703/line/dualPairMode on page 143 crocusShdslTtRpG703/line/<configurationAlarmAttributes> on page 144
crocusShdslTtRpG703/line/channel Use the channel attribute to define which modem is the master (central) and which the slave (remote) during the synchronisation procedure of the modems.
The default channel setting of a TT is remote, while that of a CV is central. Therefore there will never be a synchronisation problem when a CV and a TT are used in a regular set-up, the CV at the backbone side and the TT at the customer side. If two TTs are used at each end of the data link, make sure to change the channel attribute of one of the TTs into central. If two CVs are used at each end of the data link, make sure to change the channel attribute of one of the CVs into remote.
crocusShdslTtRpG703/line/region Use the region attribute to set the S-HDSL standard. The region attribute has the following values: Value annexA annexB auto Description The American S-HDSL standard is used. The European S-HDSL standard is used. The S-HDSL standard is selected automatically.
crocusShdslTtRpG703/line/timingMode
Default:pleisiochronous Range: pleisiochronous / synUse the timingMode attribute to set the timing mode. It influences the relationchronous ship between the line clock and the user interface clock. Use the timingMode attribute to set the timing mode. The Crocus SHDSL G703 has two clock sources: one takes care of the clocking on the SHDSL line. one takes care of the clocking on the modular user interface.
Using the timingMode attribute you can define whether these two clocks run independent from each other (i.e. plesiochronous mode) or whether they are "coupled" with each other (i.e. synchronous mode). The timingMode attribute has the following values: Value plesiochronous Description In this mode each SHDSL frame has 0 or 4 stuffing bits to compensate clock deviations towards the user interface clock. In this mode, all possible clocking modes can be selected. In this mode the SHDSL frame does not have stuffing bits to compensate clock deviations towards the user interface clock. In this case only internal and slave receive clocking is allowed. What is more, internal clocking is only allowed at one side of the link (e.g. the central side) and slave receive clocking at the other side (e.g. the remote side).Synchronous mode is the typical timing mode in DSLAM setups.
synchronous
You always have to work in the same timing mode at both sides of the link. In other words: central: synchronous - remote: synchronous allowed central: plesiochronous - remote: plesiochronous allowed central: synchronous - remote: plesiochronous or vice versa not allowed
For compatibility with other SHDSL devices, setting this attribute to the correct value might be essential. Refer to 5.14 - Crocus SHDSL G703 compatibility with other SHDSL devices on page 119
crocusShdslTtRpG703/line/mode This attribute is only present on a Crocus SHDSL G703 2P (2 pair) version. Use the mode attribute to select between single pair or dual pair operation. When the mode attribute is changed, the Crocus SHDSL G703 reboots.
When you change the mode attribute, then make sure that you use the correct speed attribute to set the user speed: If the mode attribute is set to singlePair, dualPair, then use the attribute speed to configure the user speed. speed2P to configure the user speed.
crocusShdslTtRpG703/line/minLinePairSpeed Use the minLinePairSpeed attribute to determine what the minimum speed on the line pair has to be when the Crocus SHDSL G703 trains. For more information on the minimum line pair speed, refer to 5.6 - Configuring the minimum line speed on page 87. crocusShdslTtRpG703/line/retrain Use the retrain attribute to determine when the Crocus SHDSL G703 should retrain. The retrain criteria The following criteria determine when to retrain: Criterion no SHDSL frame synchronisation SHDSL frame CRC error threshold exceeded signal to noise too low Description
When the Crocus SHDSL G703 cannot synchronise on the SHDSL framing, it retrains. SHDSL framing sends 166 blocks per second over the line, independently of the speed. Each block has a CRC check. When a certain percentage of frames has a CRC error, the Crocus SHDSL G703 retrains. When the signal to noise ratio becomes too low during a certain period of time, the Crocus SHDSL G703 retrains.
Configuring the retrain criteria The retrain structure contains the following elements: Element enabled Description Use this element to enable (yes) or disable (no) retrain- Default:yes ing. So when selecting no, the Crocus SHDSL G703 Range: will never retrain (even not when the line is disconnected). Use this element to set the period, in seconds, during which each criterion is measured. If within this period the predefined criterion value is equalled or exceeded, the Crocus SHDSL G703 retrains. Default:10 Range: -1 30
errorPersistenceTime
The errorPersistenceTime functions as a moving window, so it s always the last seconds, equal to the errorPersistenceTime, that are used to calculate the average. errorThreshold Use this element to set the amount of CRC errors, per Default:10 mille, at which the Crocus SHDSL G703 should Range: 1 300 retrain. If the amount of CRC errors exceeds this value (measured during the errorPersistenceTime), then the Crocus SHDSL G703 retrains. Remark The errored SHDSL frames can be monitored using the performance attribute crocusShdslTtRpG703/line/linePair[ ]/performance/codeViolations. snrThreshold Use this element to set the signal to noise ratio, in dB, Default:23 which has to be maintained. If the measured signal to Range: 20 25 noise ratio drops below this value (measured during the errorPersistenceTime), then the Crocus SHDSL G703 retrains. If you configured the Crocus SHDSL G703 in a fixed speed, then the Crocus SHDSL G703 tries to retrain again at this fixed speed. If the retrain is successful, then the Crocus SHDSL G703 operates at this fixed speed again. If the retrain is not successful, then the Crocus SHDSL G703 retrains again. If the line conditions are so bad that the fixed speed can no longer be attained, then the Crocus SHDSL G703 keeps retraining. auto speed, then the Crocus SHDSL G703 initially tries to retrain at the speed it was trained before. If this does not work, then it tries to train on a lower speed. Remark The snrThreshold is only taken into account as a retrain criterion after the line has been in data state for 2 minutes.
Element stepupMargin
Description Use this element to enable or disable the step-up retrain mechanism. Default:disabled Range: 3 15
If you set the stepupMargin to a value other than disabled, then the Crocus SHDSL G703 retrains at a higher speed (because of the improved line conditions) when the current signal to noise ratio of the line exceeds the sum of + the stepupMargin value. the signal to noise ratio at the moment the line entered the data state (i.e. shortly after a successful training cycle)
The result of this sum can be seen in the status attribute stepupThreshold. Remark Note that the stepupMargin element is only considered when both the central and remote Crocus SHDSL G703 are in auto speed mode.
Example Suppose in the retrain structure you set the enabled element to yes. snrThreshold element to 25 (dB). stepupMargin element to 3 (dB).
Suppose that at the moment the line entered the data state the measured signal to noise ratio was 27 dB. In that case the stepupThreshold value is 27 dB + 3 dB = 30 dB. Now, if the signal to noise ratio drops below 25 dB (i.e. the value set using the snrThreshold attribute), then the Crocus SHDSL G703 retrains at a lower speed (because of the deteriorated line conditions). exceeds 27 dB (i.e. the stepupThreshold value), then the Crocus SHDSL G703 retrains at a higher speed (because of the improved line conditions).
crocusShdslTtRpG703/line/startupMargin
Use the startupMargin attribute to define for which signal to noise margin a line speed is selected during the ITU-T G.994.1 auto speed negotiation. The startupMargin attribute is only relevant in case both central and remote Crocus SHDSL G703 are set to auto speed mode. The higher the startupMargin, the lower the selected line speed but the more stable the line will be. The startupMargin attribute has the following values: disabled, 0dB, 1dB, 2dB, 3dB, 4dB, 5dB, 6dB, 7dB, 8dB, 9dB, 10dB. When you set the startupMargin to disabled, the signal to noise margin is not considered during the ITU-T G.994.1 auto speed negotiation. I.e. the complete speed range is available. crocusShdslTtRpG703/line/testDuration Use the testDuration attribute to set the time-out period of diagnostic tests. Default:00000d 00h 03m 00s Range: 00000d 00h 00m 01s00000d 18h 12m 15s
It is possible to perform diagnostic tests on the Crocus SHDSL G703 (refer to Chapter 12 - Diagnostic tests on page 245). However, these tests cause an interruption of the normal data transfer. Some tests even cause a contact loss between the management system and the remote Crocus SHDSL G703. Therefore, tests are automatically terminated after a time-out period which is specified with the testDuration attribute. The time-out ranges from 00000d 00h 00m 01s up to 00000d 18h 12m 15s. Entering 00000d 00h 00m 00s disables the time-out period (i.e. diagnostic tests are not terminated after a time-out period). crocusShdslTtRpG703/line/asymmetricPsd Default:disabled Range: enabled / disabled
Use the asymmetricPsd attribute to enable or disable the asymmetrical Power Spectral Density. This feature, described in the SHDSL standard, increases the transmit power for the fixed speeds 768 kbps and 1536 kbps in case of Annex A. 2048 kbps and 2304 kbps in case of Annex B.
To enable asymmetrical PSD, proceed as follows: Step 1 Action Select the speed for which you want to enable asymmetrical PSD using the speed(2P) attribute: 2 768 kbps or 1536 kbps in case of Annex A. 2048 kbps or 2304 kbps in case of Annex B.
Select the correct regional standard using the region attribute: Annex A in case of a speed of 768 kbps or 1536 kbps. Annex B in case of a speed of 2048 kbps or 2304 kbps.
If asymmetricPsd is enabled then the device on which the channel attribute is set to "remote" will even have a slightly higher transmit power, than the device on which the channel attribute is set to "central". When asymmetricPsd is enabled, you should be able to cover a slightly higher distance at the given speeds.
crocusShdslTtRpG703/line/eocChannel
Use the eocChannel attribute to determine how the checksum of Embedded Operations Channel (EOC) messages is calculated. Make sure that on both the central and the remote device the eocChannel attribute is set to the same value. The eocChannel attribute has the following values: Value proprietary itu-G.991.2 Description The checksum is calculated using a proprietary method.
crocusShdslTtRpG703/line/txEocMessages
This attribute is only present on a Crocus SHDSL G703 2P (2 pair) version. Use the txEocMessages attribute to send EOC messages on both line pair 1 and 2 (bothPairs) or on line pair 1 only (pair1). crocusShdslTtRpG703/line/eocHandling Default:none Range: enumerated, see below
SHDSL devices can communicate with each other through the Embedded Operations Channel (EOC). Use the eocHandling attribute to define the handling of the EOC messages. For more information on EOC handling, refer to 5.2 - Configuring EOC handling on page 57. crocusShdslTtRpG703/line/numExpectedRepeaters Default:0 Range: 0 8
Use the numExpectedRepeaters attribute to set the number of Crocus SHDSL G703 Repeaters that the Crocus SHDSL G703 can expect to find on the SHDSL line. If the actual number of repeaters does not match the number you entered in the numExpectedRepeaters attribute, then the invalidNumRepeaters alarm is raised.
crocusShdslTtRpG703/line/linkAlarmThresholds
Use the linkAlarmThresholds attribute to set the alarm threshold values of the most important line parameters. If this predefined threshold value is exceeded, then a corresponding alarm is generated. The linkAlarmThresholds structure contains the following elements: Element lineAttenuation Description Use this element to set the alarm threshold value of the line attenuation in dB. If the line attenuation exceeds this value during at least 10 seconds, then the lineAttenuation alarm is raised. drops below this value during at least 10 seconds, then the lineAttenuation alarm is cleared. Remark Note that if you set the eocHandling attribute to alarmConfiguration, then the central SHDSL device forces the remote SHDSL device and any intermediary repeater to use the link alarm thresholds lineAttenuation and signalNoise as configured on the central device. In other words, the settings of the lineAttenuation and signalNoise on the central device overrule those of the remote device and repeaters. signalNoise Use this element to set the alarm threshold value of the signal noise in dB. If the signal noise exceeds this value during at least 10 seconds, then the signalNoise alarm is raised. drops below this value during at least 10 seconds, then the signalNoise alarm is cleared. Remark Note that if you set the eocHandling attribute to alarmConfiguration, then the central1 SHDSL device forces the remote2 SHDSL device and any intermediary repeater to use the link alarm thresholds lineAttenuation and signalNoise as configured on the central device. In other words, the settings of the lineAttenuation and signalNoise on the central device overrule those of the remote device and repeaters.
Element errSecRatioExceeded
Description Use this element to set the alarm threshold value of the errored seconds ratio. The errored seconds ratio is the ratio of errored seconds to total seconds during a 15 minute time interval. So if the errored seconds ratio exceeds this value within a 15 minute period3, then the errSecRatioExceeded alarm is raised. drops below this value within a 15 minute period, then the errSecRatioExceeded alarm is cleared.
sevErrSecRatioExceeded
Use this element to set the alarm threshold value of the severely errored seconds ratio. The severely errored seconds ratio is the ratio of severely errored seconds to total seconds during a 15 minute interval. So if the severely errored seconds ratio exceeds this value within a 15 minute period3, then the sevErrSecRatioExceeded alarm is raised. drops below this value within a 15 minute period, then the sevErrSecRatioExceeded alarm is cleared.
bBErrRatioExceeded
Use this element to set the alarm threshold value of the background block error ratio. The background block error ratio is the ratio of background block errors to total blocks during a 15 minute time interval. The count of total blocks excludes all blocks during severely errored seconds. So if the background block error ratio exceeds this value within a 15 minute period3, then the bBErrRatioExceeded alarm is raised. drops below this value within a 15 minute period, then the bBErrRatioExceeded alarm is cleared.
1. The central device is the device on which the channel attribute is set to central. 2. The remote device is the device on which the channel attribute is set to remote. 3. The 15 minute periods run synchronous with the 2 hour periods of the line/h2Line performance attribute. Because alarms are raised or cleared within 15 minute periods, there is a delay in the alarm status. For example, suppose that in the first minute of a 15 minute period the errSecRatioExceeded value is exceeded, then the errSecRatioExceeded alarm is raised when the full 15 minute period has passed. The alarm is only cleared if in the next 15 minute period the errSecRatioExceeded value is not exceeded.
crocusShdslTtRpG703/line/management
Use the management attribute to determine whether and which management data is forwarded over the line (also refer to crocusShdslTtRpG703/forwardTmaToLine on page 128 to enable or disable propagation of management information to the line). The management attribute has the following possible values: Value transparent o10Management Description No management data is forwarded over the SHDSL line. The data is passed transparently over the line. This forwards the proprietary OneAccess O10 protocol over the SHDSL line. This allows you to manage the remote SHDSL device (and possibly other OneAccess devices connected to the SHDSL device). This forwards path management information over the SHDSL line. This allows you to manage complete paths instead of managing individual devices (i.e. elements).For more information on path management, refer to the TMA Path Management manual. This forwards both the proprietary OneAccess O10 protocol as the path management information over the SHDSL line.
pathManagement
o10-PathManagement
crocusShdslTtRpG703/line/dualPairMode This attribute is only present on the Crocus SHDSL G703 2 pair version.
If the mode attribute is set to dualPair, then use the dualPairMode attribute to set the dual pair operation mode. The dualPairMode attribute has the following possible values: Value standard Description The dual pair SHDSL line operates strictly as described in the SHDSL standard. If the Crocus SHDSL G703 is connected to a remote device that operates strictly according to the SHDSL standard, then select the standard value. The dual pair SHDSL line operates slightly different than described in the SHDSL standard (some enhancements are present). If you select the enhanced value, then it is possible that you experience problems when connecting to third party SHDSL devices. In that case, select the standard value.
enhanced
If you have two Crocus SHDSL G703s connected to each other in a point-to-point set-up, then make sure that you set the dualPairMode attribute to the same value at both sides!
crocusShdslTtRpG703/line/<configurationAlarmAttributes> Use the alarm related configuration attributes to configure the alarm behaviour of the line object (use alarmMask, alarmLevel, remoteAlarmMask, alarmContactHighMask and alarmContactLowMask). the repeater object (use repeaterAlarmMask, repeaterAlarmLevel, repeaterLinePairAlarmMask and repeaterLinePairAlarmLevel). the end object (use endAlarmMask, endAlarmLevel, endLinePairAlarmMask and endLinePairAlarmLevel).
For more information on the alarm configuration attributes and on the alarms in general, refer to 9.2 - Introducing the alarm attributes on page 210. the alarms of the line object, refer to 9.4 - Line alarms on page 221. the alarms of the repeater object, refer to 9.6 - Repeater and end alarms on page 226. the alarms of the end object, refer to 9.6 - Repeater and end alarms on page 226.
6.4
This section describes the following configuration attributes: crocusShdslTtRpG703/line/linePair[ ]/<configurationAlarmAttributes> on page 146
In case of a Crocus SHDSL G703 2P, two linePair objects are present: linePair [1] and linePair [2].
crocusShdslTtRpG703/line/linePair[ ]/<configurationAlarmAttributes> For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask, alarmContactHighMask, alarmContactLowMask and on the alarms in general, refer to 9.2 - Introducing the alarm attributes on page 210. For more information on the alarms of the linePair[ ] object, refer to 9.5 - Line pair alarms on page 223.
6.5
The repeater[ ] and the end objects are not present in the containment tree by default. They are added automatically when you configure the eocHandling attribute. Refer to 5.2 - Configuring EOC handling on page 57. crocusShdsl/repeater[ ]/<configurationAlarmAttributes> crocusShdsl/end[ ]/<configurationAlarmAttributes> For more information on the configuration alarm attributes alarmMask and alarmLevel and on the alarms in general, refer to 9.2 - Introducing the alarm attributes on page 210. For more information on the alarms of the repeater[ ] and end[ ] object, refer to 9.6 - Repeater and end alarms on page 226.
6.6
-This section describes the following configuration attributes: crocusShdslTtRpG703/g703/timeSlots on page 149 crocusShdslTtRpG703/g703/coding on page 149 crocusShdslTtRpG703/g703/aisDetection on page 149 crocusShdslTtRpG703/g703/sqThreshold on page 149 crocusShdslTtRpG703/g703/sqTime on page 149 crocusShdslTtRpG703/g703/name on page 150 crocusShdslTtRpG703/g703/clocking on page 150 crocusShdslTtRpG703/g703/rdlDetect on page 150 crocusShdslTtRpG703/g703/<configurationAlarmAttributes> on page 150
Use the timeSlots attribute to enable or disable the individual 64 kbps time slots in the framed data stream. Important remark Do not enable time slot 0 in the local Crocus SHDSL G703 and a non-G703 interface in the remote Crocus SHDSL G703. In case you use a G703 interface in one Crocus SHDSL and a serial interface is the other Crocus SHDSL, then the auto speed only works when more than 2 time slots (in case of a Crocus SHDSL 1 pair version) or 4 time slots (in case of a Crocus SHDSL 2 pair version) are selected.
For more information, refer to 5.7 - Configuring framing and time slots on page 93. crocusShdslTtRpG703/g703/coding Use the coding attribute to set the G703 interface encoding mode. Possible values are: Value ami hdb3 Description Alternate Mark Inversion is selected. This is a bipolar code with no zero substitution. High Density Bipolar 3 is selected. This is a modified bipolar code.With HDB3 encoding, more than three consecutive zeroes occurring in the data are replaced 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. Most of the G703 applications use HDB3 encoding. Default:hdb3 Range: ami / hdb3
crocusShdslTtRpG703/g703/aisDetection Use this attribute to enable or disable the detection of the Alarm Indication Signal. crocusShdslTtRpG703/g703/sqThreshold Use this attribute to set the signal quality threshold. This is the number of errored seconds for which a signal quality alarm is generated.
If the sqThreshold value, i.e. the number of errored seconds, is exceeded within the sqTime, then a signal quality (sq) alarm is generated. For example, if 10 (default) or more errored seconds occur within 1 minute (default), then a signal quality alarm is generated. The sqThreshold value ranges from 0 up to 65535. crocusShdslTtRpG703/g703/sqTime Use 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. Default:00000d 00h 01m 00s Range: 00000d 00h 00m 00s 24855d 03h 14m 07s
If the sqThreshold value, i.e. the number of errored seconds, is exceeded within the sqTime, then a signal quality (sq) alarm is generated. For example, if 10 (default) or more errored seconds occur within 1 minute (default), then a signal quality alarm is generated. The sqTime value ranges from 00000d 00h 00m 00s up to 24855d 03h 14m 07s. crocusShdslTtRpG703/g703/name Use the name attribute to assign an administrative name to the DTE interface. crocusShdslTtRpG703/g703/clocking Use the clocking attribute to select a clocking mode. Default:<empty> Range: 0 24 characters
For more information, refer to 5.5 - Configuring the clocking mode on page 82. crocusShdslTtRpG703/g703/rdlDetect Default:enabled Range: disabled / enabled
When set to disabled, this attribute prevents that a digital loop can be performed by a remote Crocus SHDSL G703 on the local Crocus SHDSL G703.
When rdlDetect is disabled, and a remote Crocus SHDSL G703 initiates an RDL test, the local Crocus SHDSL G703 will not go in digital loop. However, the DTE interface of the remote Crocus SHDSL G703 will be clamped and data transfer is interrupted. crocusShdslTtRpG703/g703/<configurationAlarmAttributes> For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask, alarmContactHighMask, alarmContactLowMask and on the alarms in general, refer to 9.2 - Introducing the alarm attributes on page 210. For more information on the alarms of the <dteInterface> object, refer to 9.7 - Interface alarms on page 229.
6.7
This section describes the following configuration attributes: crocusShdslTtRpG703/management/cms2Address on page 152 crocusShdslTtRpG703/management/consoleNoTrafficTimeOut on page 152 crocusShdslTtRpG703/management/ctrlPortProtocol on page 153
Also refer to 5.10.1 - Rules of thumb and remarks concerning management on page 100 for important rules of thumb regading management.
crocusShdslTtRpG703/management/cms2Address
Use the cms2Address attribute to configure an absolute address in the Crocus SHDSL G703. The absolute addressing range goes from 1 up to 65535. This address can then be used to connect with TMA. Refer to 4.1 - Starting TMA on the Crocus SHDSL G703 on page 42. 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 default value, being 0. Refer to 5.10.2 - Using relative or absolute addressing on page 101 for more information on relative and absolute addressing. crocusShdslTtRpG703/management/consoleNoTrafficTimeOut Default:00000d 00h 30m00s Range: 00000d 00h 30m 24855d 03h 14m 07s
You can open a TMA, CLI or ATWIN session on the Crocus SHDSL G703 through the control connector. These sessions close automatically if there is no user interaction during a certain time-out period. This time-out period can be set with the consoleNoTrafficTimeOut attribute.
The purpose of such a timer is to protect the Crocus SHDSL G703 against unauthorised access in case the last user did not close his session. The consoleNoTrafficTimeOut value ranges from 00000d 00h 00m 00s up to 24855d 03h 14m 07s.
crocusShdslTtRpG703/management/ctrlPortProtocol
The setting of the ctrlPortProtocol attribute depends on what you connect to the control connector of the Crocus SHDSL G703. This is explained in the following table: Value management Description
Select this value if you want to connect the control connector of the Crocus SHDSL G703 to a management concentrator (e.g. the Orchid 1003 LAN or 1035 Orchid) for management purposes. the control connector of another OneAccess device using a crossed cable (i.e. back-to-back) in order to create an extended management link. For more information on extended management links, refer to Relative addressing on page 101 and Forwarding management information on page 103).
When connecting the control connector of the Crocus SHDSL G703 to a COM port of your computer, you can still open a TMA session on the Crocus SHDSL G703. However, you can not open a CLI or ATWIN session. console Select this value if you want to connect the control connector of the Crocus SHDSL G703 to a COM port of your computer in order to manage the Crocus SHDSL G703 locally using TMA, CLI or ATWIN.
Status attributes
This chapter discusses the status attributes of the Crocus SHDSL G703. The following gives an overview of this chapter. 7.1 - Status attribute overview on page 156 7.2 - General status attributes on page 159 7.3 - Line status attributes on page 163 7.4 - Line pair status attributes on page 172 7.5 - Repeater and end status attributes on page 175 7.6 - DTE Interface status attributes on page 180 7.7 - Operating system status attributes on page 184
7.1
> crocusShdslTtRpG703 sysDescr sysObjectID sysUpTime sysServices messages deviceId configurationSaving bootVersion loaderVersion flash1Version powerSource Action: Cold Boot >> line ifDescr ifType ifSpeed ifOperStatus minLinePairSpeed maxLinePairSpeed framerType testType testOriginator testStatus maxSpeedSearch maxSpeedResult errorCount region asymmetricPsd linePairsSwapped1 numDiscoveredRepeaters eocAlarmThresholds Action: clearErrorCounter Action: maximumSpeedSearch
1. 2P version only
>>> linePair[ ]2 ifSpeed ifOperStatus status timeSinceLastRetrain transmitPower lineAttenuation signalNoise stepupThreshold actualBitRate >> repeater[ ]3 vendorId vendorModel vendorSerial vendorSoftVersion eocSoftVersion shdslVersion eocState eocAlarmThresholds Action: loopbackActivation >>> networkLinePair[ ]2 lineAttenuation signalNoise >>> customerLinePair[ ]2 lineAttenuation signalNoise >> end3 vendorId vendorModel vendorSerial vendorSoftVersion eocSoftVersion shdslVersion eocState eocAlarmThresholds >>> linePair[ ]2 lineAttenuation signalNoise
2. in case of a 2P version, two linePair objects are present: linePair[1] and linePair[2]. 3. not present by default, is added automatically when setting the line/eocHandling attribute.
>> g7034 timeslots5 txdItu103 rxdItu104 los ais lfa5 rai5 ifDescr ifType ifSpeed ifClocking ifOperStatus >> operatingSystem taskInfo
7.2
This section describes the following status attributes: crocusShdslTtRpG703/sysDescr on page 160 crocusShdslTtRpG703/sysObjectID on page 160 crocusShdslTtRpG703/sysUpTime on page 160 crocusShdslTtRpG703/sysServices on page 160 crocusShdslTtRpG703/messages on page 160 crocusShdslTtRpG703/deviceId on page 161 crocusShdslTtRpG703/configurationSaving on page 161 crocusShdslTtRpG703/bootVersion on page 161 crocusShdslTtRpG703/loaderVersion on page 161 crocusShdslTtRpG703/flash1Version on page 162 crocusShdslTtRpG703/powerSource on page 162
This section describes the following actions: crocusShdslTtRpG703/Cold Boot on page 162
crocusShdslTtRpG703/sysDescr This is a textual description of the device. This is an SNMP MIB2 parameter. Example: OneAccess Crocus SHDSL TT V35 T1234/00100 01/01/00 12:00. In this example the following parameters are visible: OneAccess Crocus SHDSL is the modem type TT is the modem version V35 is the interface type T1234/00100 is the application software code and version 01/01/00 12:00 is the application software release date and time.
crocusShdslTtRpG703/sysObjectID This is the SNMP identification string. It is an SNMP MIB2 parameter. Example: 1.3.6.1.4.1.776.22. crocusShdslTtRpG703/sysUpTime This is the elapsed time since last power-on or cold boot of the Crocus SHDSL G703. Example: 00005d 02h 42m 15s, which means 5 days, 2 hours, 42 minutes and 15 seconds. crocusShdslTtRpG703/sysServices This is the SNMP service identification. It is an SNMP MIB2 parameter. crocusShdslTtRpG703/messages This table displays informative and error messages, e.g. Reconfigured, Cold Boot, The messages table displays maximum 20 messages. If no TMA, CLI or ATWIN session is established through the control connector, then the messages are also sent to the control connector. This means that if you open a terminal emulation session on the control connector, you can monitor these messages. If you hit the ENTER key, the messages stop and you get a password prompt (CLI mode).
crocusShdslTtRpG703/deviceId This displays a unique code. This code is programmed into the Crocus SHDSL G703before it leaves the factory. You can use this code for inventory purposes. crocusShdslTtRpG703/configurationSaving This attribute indicates when the Crocus SHDSL G703 is writing its (new) configuration to the flash memory. Value busy Description The Crocus SHDSL G703 is busy writing its configuration to the flash memory. During this state, do not power-down or reboot the Crocus SHDSL G703 else the new configuration will be lost. The Crocus SHDSL G703 has finished writing its configuration to the flash memory.
done
crocusShdslTtRpG703/bootVersion This displays the code and version of the boot software currently used in the Crocus SHDSL G703. For more information on boot software, refer to 11.1 - What is boot, loader and application software? on page 236. Example: Txxxx/xxxxx 01/01/00 12:00. In this example the following parameters are visible: Txxxx is the boot software code for this device /xxxxx is the boot software version 01/01/00 is the boot software release date 12:00 is the boot software release time.
crocusShdslTtRpG703/loaderVersion This displays the code and version of the loader software currently used in the Crocus SHDSL G703. For more information on loader software, refer to 11.1 - What is boot, loader and application software? on page 236. Example: Txxxx/xxxxx 01/01/00 12:00. In this example the following parameters are visible: Txxxx is the loader software code for this device /xxxxx is the loader software version 01/01/00 is the loader software release date 12:00 is the loader software release time.
crocusShdslTtRpG703/flash1Version This displays the code and version of the application software, also called firmware, currently used in the Crocus SHDSL G703. For more information on application software, refer to 11.1 - What is boot, loader and application software? on page 236. Example: Txxxx/xxxxx 01/01/00 12:00. In this example the following parameters are visible: Txxxx is the application software code for this device /xxxxx is the application software version 01/01/00 is the application software release date 12:00 is the application software release time.
crocusShdslTtRpG703/powerSource This attribute displays how the Crocus SHDSL G703 is powered. crocusShdslTtRpG703/Cold Boot This action will reboot the Crocus SHDSL G703 while the power stays up (the Crocus SHDSL G703 also reboots if it is powered down and up again).
7.3
This section describes the following status attributes: crocusShdslTtRpG703/line/ifDescr on page 164 crocusShdslTtRpG703/line/ifType on page 164 crocusShdslTtRpG703/line/ifSpeed on page 164 crocusShdslTtRpG703/line/ifOperStatus on page 164 crocusShdslTtRpG703/line/minLinePairSpeed on page 164 crocusShdslTtRpG703/line/maxLinePairSpeed on page 165 crocusShdslTtRpG703/line/framerType on page 166 crocusShdslTtRpG703/line/testType on page 166 crocusShdslTtRpG703/line/testOriginator on page 167 crocusShdslTtRpG703/line/testStatus on page 167 crocusShdslTtRpG703/line/maxSpeedSearch on page 168 crocusShdslTtRpG703/line/maxSpeedResult on page 168 crocusShdslTtRpG703/line/errorCount on page 169 crocusShdslTtRpG703/line/region on page 169 crocusShdslTtRpG703/line/asymmetricPsd on page 169 crocusShdslTtRpG703/line/linePairsSwapped on page 169 crocusShdslTtRpG703/line/numDiscoveredRepeaters on page 169 crocusShdslTtRpG703/line/eocAlarmThresholds on page 170
This section describes the following actions: crocusShdslTtRpG703/line/clearErrorCounter on page 170 crocusShdslTtRpG703/line/maximumSpeedSearch on page 171
crocusShdslTtRpG703/line/ifDescr This attribute displays the interface description. It is an SNMP MIB2 parameter. The ifDescr value for the line object is line. crocusShdslTtRpG703/line/ifType This attribute displays the interface type. It is an SNMP MIB2 parameter. The ifType value for the line object is other. crocusShdslTtRpG703/line/ifSpeed This attribute displays the current line speed in bits per second (bps), e.g. 2048000. crocusShdslTtRpG703/line/ifOperStatus This attribute displays the current operation status of the line. Possible operation status values are: Value up down testing Description The line is up, data transfer is possible. The line is down, data transfer is not possible. A test is active. For more information on type, originator and status of the test refer to the line status attributes testType, testOriginator and testStatus.
crocusShdslTtRpG703/line/minLinePairSpeed This attribute displays the minimum line pair speed. The value depends on how the user speed and/or the minimum line pair speed are configured. Refer to What do the minLinePairSpeed and maxLinePairSpeed status attributes display? on page 165 for more information.
crocusShdslTtRpG703/line/maxLinePairSpeed This attribute displays the maximum line pair speed. The value depends on how the user speed and/or the minimum line pair speed are configured. Refer to What do the minLinePairSpeed and maxLinePairSpeed status attributes display? for more information. What do the minLinePairSpeed and maxLinePairSpeed status attributes display? What is configured? user speed (fixed) Description In case you configure a fixed user speed (i.e. you set the configuration attribute speed(2P) to a fixed value), then the line trains at the fixed user speed.So in this case, the status attribute minLinePairSpeed displays a speed that is equal to the fixed user speed (or half the fixed user speed in case of a 2P version). What is more, the status attributes minLinePairSpeed and maxLinePairSpeed display the same speed. In case you configure an auto user speed (i.e. you set the configuration attribute speed(2P) to auto), then during the training cycle the lowest and highest possible line speed is determined. Then the line trains at the highest possible speed and this becomes the user speed.So in this case, the status attribute minLinePairSpeed displays the lowest possible speed that could be achieved on the line pair(s) during the training cycle. The status attribute maxLinePairSpeed displays the highest possible speed that could be achieved on the line pair(s) during the training cycle. In case you configure a fixed user speed (i.e. you set the configuration attribute speed(2P) to a fixed value) and a minimum line pair speed (using the configuration attribute minLinePairSpeed) and the user speed is lower than the line speed, then the line trains at the configured line speed.So in this case, the status attribute minLinePairSpeed displays a speed that is equal to the configured minimum line pair speed. What is more, the status attributes minLinePairSpeed and maxLinePairSpeed display the same speed. Remark Note that this only applies when the configured user speed is lower than the configured line speed. In case the configured user speed is higher than the configured line speed, the user speed (fixed) situation applies. See above. user speed (auto) + line speed In case you configure an auto user speed (i.e. you set the configuration attribute speed(2P) to auto) and a minimum line pair speed (using the configuration attribute minLinePairSpeed), then during the training cycle the lowest (which is the minimum line pair speed) and highest possible line speed is determined. Then the line trains at the highest possible speed and this becomes the user speed.So in this case, the status attribute minLinePairSpeed displays a speed that is equal to the configured minimum line pair speed. The status attribute maxLinePairSpeed displays the highest possible speed that could be achieved on the line pair(s) during the training cycle.
crocusShdslTtRpG703/line/framerType This attribute displays which type of framing is used on the SHDSL line: Nx64 or slotted E1. The line of the Crocus SHDSL G703 can operate in two modes: Nx64 or slotted E1. These modes are not directly user configurable (i.e. there is no attribute with which you can select these modes), but depending on which interface is used, which user/line speed is chosen, etc. the Crocus SHDSL G703 will select one of these modes. Mode Nx64 Description In this mode the data on the SHDSL line is a continuous bit stream with a speed of N x 64 kbps, where N ranges from 1 up to 36 (or from 2 up to 72 in case of a Crocus SHDSL G703 2 pair version). So the line speed ranges from 64 kbps up to 2304 kbps (or 128 kbps up to 4608 kbps in case of a Crocus SHDSL G703 2 pair version). In this mode the data on the SHDSL line is put in N x 64 kbps time slots (similar to framed data on a G.703 interface), where N ranges from 3 up to 32 (or from 6 up to 64 in case of a Crocus SHDSL G703 2 pair version). So the line speed ranges from 192 kbps up to 2048 kbps (or 384 kbps up to 4096 kbps in case of a Crocus SHDSL G703 2 pair version).
slotted E1
crocusShdslTtRpG703/line/testType This attribute displays which test is currently active. The possible indications are: Value no al dl rdl et alEt rdlEt Description No test is active. An analogue loop is active. A digital loop is active. A remote digital loop is active. The error test pattern generator / detector is active. An analogue loop in combination with an error test is active. A remote digital loop in combination with an error test is active.
crocusShdslTtRpG703/line/testOriginator This attribute displays the origin of the active test. The possible indications are: Value nms interface remote unknown Description The 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 Crocus SHDSL G703. There are two possibilities: No test is running. For some reason it is not possible to define the origin of the test.
crocusShdslTtRpG703/line/testStatus This attribute displays the status of the active test. The possible indications are: Value progressing running ending unknown Description The 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.
crocusShdslTtRpG703/line/maxSpeedSearch This attribute shows the status of the maximumSpeedSearch action: refer to crocusShdslTtRpG703/line/maximumSpeedSearch on page 171. The possible indications are: Value idle progressing aborted completed Description No maximumSpeedSearch action has been performed. The maximumSpeedSearch action is running. The maximumSpeedSearch action stopped without result. The maximumSpeedSearch action is finished. The result is displayed in the maxSpeedResult attribute.
crocusShdslTtRpG703/line/maxSpeedResult This attribute displays the maximum speed that was achieved during the execution of the maximumSpeedSearch action: refer to crocusShdslTtRpG703/line/maximumSpeedSearch on page 171.
crocusShdslTtRpG703/line/errorCount This attribute displays the amount of detected errors since the start of an ET, AL-ET or RDL-ET test. Every time a new ET, AL-ET or RDL-ET is started, the errorCount attribute is reset to 0. crocusShdslTtRpG703/line/region This attribute displays how you configured the region configuration attribute (annexA, annexB or auto). crocusShdslTtRpG703/line/asymmetricPsd This attribute displays whether asymmetric PSD is currently active or not. crocusShdslTtRpG703/line/linePairsSwapped This attribute is only present on the Crocus SHDSL G703 2P version. This attribute indicates whether the 2 line pairs have been swapped when connecting the central with the remote device. Possible values are: Value yes no unknown Description The line pairs are swapped. The line pairs are not swapped. The Crocus SHDSL G703 is unable to determine whether the line pairs have been swapped (e.g. because it is still training).
crocusShdslTtRpG703/line/numDiscoveredRepeaters This attribute displays the number of Crocus SHDSL G703 Repeaters that the Crocus SHDSL G703 discovered on the SHDSL line.
crocusShdslTtRpG703/line/eocAlarmThresholds This attribute displays the value of the lineAttenuation and signalNoise elements as set in configuration attribute crocusShdslTtRpG703/line/linkAlarmThresholds. However, when the configuration attribute crocusShdslTtRpG703/line/eocHandling of the central device in the link has been set to alarmConfiguration, the central device will impose its values of lineAttenuation and signalNoise elements on the other devices in the link, as described in 5.2.2 - The EOC handling attribute on page 59. The eocAlarmTresholds attribute will then display the values of the lineAttenuation and signalNoise elements of the central device in the link. The eocAlarmThresholds structure contains the following elements: lineAttenuation signalNoise
crocusShdslTtRpG703/line/clearErrorCounter Use this action to clear the value of the errorCount attribute. This could be useful, for example, to reset the error counter after the unstable period (in which errors occur anyhow) shortly after the initiation of a test. Double click on the clearErrorCounter string to execute the action.
crocusShdslTtRpG703/line/maximumSpeedSearch Use this action to determine the highest possible line speed that can be achieved between the central and remote Crocus SHDSL G703. Double click on the maximumSpeedSearch string to execute the action. When you execute this test, the following happens: Phase 1 2 Action The Crocus SHDSL G703 interrupts the normal data transfer. Both local and remote Crocus SHDSL G703 go to auto speed mode in order to determine the highest possible line speed. Meanwhile, the status of the test can be monitored with the maxSpeedSearch attribute. When the test ends, the result is displayed by the maxSpeedResult attribute. The Crocus SHDSL G703 resumes normal data transfer at the speed that was selected before the test.
3 4
The Crocus SHDSL G703 has to be in data state (i.e. after a successful training sequence and when the data connection is up) before you can execute the maximumSpeedSearch action. While the maximumSpeedSearch action is running, no data transmission is possible.
7.4
This section describes the following status attributes: crocusShdslTtRpG703/line/linePair[ ]/ifSpeed on page 173 crocusShdslTtRpG703/line/linePair[ ]/ifOperStatus on page 173 crocusShdslTtRpG703/line/linePair[ ]/status on page 173 crocusShdslTtRpG703/line/linePair[ ]/timeSinceLastRetrain on page 173 crocusShdslTtRpG703/line/linePair[ ]/transmitPower on page 174 crocusShdslTtRpG703/line/linePair[ ]/lineAttenuation on page 174 crocusShdslTtRpG703/line/linePair[ ]/signalNoise on page 174 crocusShdslTtRpG703/line/linePair[ ]/stepupThreshold on page 174 crocusShdslTtRpG703/line/linePair[ ]/actualBitRate on page 174
In case of a Crocus SHDSL G703 2P, two linePair objects are present: linePair [1] and linePair [2].
crocusShdslTtRpG703/line/linePair[ ]/ifSpeed This attribute displays the line pair speed, in bits per second (bps), when the line pair is in data state. crocusShdslTtRpG703/line/linePair[ ]/ifOperStatus This attribute displays the current operation status of the line. The possible indications are: Value up down testing Description The line is up, data transfer is possible. The line is down, data transfer is not possible. A test is active. For more information on type, originator and status of the test refer to the line status attributes testType, testOriginator and testStatus.
crocusShdslTtRpG703/line/linePair[ ]/status This attribute displays the bit-pump its training state machine stages. It shows the progress of the training sequence. The most important indications are: Value idle dataState Description No data connection is present. This is the initial state. A data connection is present. The training sequence was successful and the bitpumps are ready to transmit data.
crocusShdslTtRpG703/line/linePair[ ]/timeSinceLastRetrain This attribute displays the time the line is in data state since the last retrain cycle.
crocusShdslTtRpG703/line/linePair[ ]/transmitPower This attribute displays the current transmit power in dB, e.g. 7.5. crocusShdslTtRpG703/line/linePair[ ]/lineAttenuation This attribute displays the current line attenuation in dB, e.g. 11.0. crocusShdslTtRpG703/line/linePair[ ]/signalNoise This attribute displays the current signal to noise ratio of the line in dB, e.g. 2.5. The status attributes transmitPower, lineAttenuation and signalNoise do not display meaningful information when the line is in analogue loop (AL) or when it is not trained. These attributes are only relevant for a trained line.
crocusShdslTtRpG703/line/linePair[ ]/stepupThreshold This attribute displays the step-up threshold in dB. If step-up retraining is enabled (i.e. the stepupMargin element in the line/retrain configuration structure is set to any value other than disabled), then the Crocus SHDSL G703 will retrain at a higher speed if the measured signal to noise ratio exceeds the step-up threshold value. The stepupThreshold value = + the stepupMargin value. the signal to noise ratio at the moment the line entered the data state (i.e. shortly after a successful training cycle)
Refer to crocusShdslTtRpG703/line/retrain on page 135 for more information. If the stepupThreshold attribute displays 0.0, then this means that step-up retraining is disabled (i.e. the stepupMargin element in the line/retrain configuration is set to disabled). crocusShdslTtRpG703/line/linePair[ ]/actualBitRate This attribute displays the maximum speed, in bits per second (bps), that could be negotiated on the line pair during the training sequence. The actualBitRate can be higher than the ifSpeed, eg. if the minLinePairSpeed is enabled.
7.5
This section describes the following status attributes: crocusShdslTtRpG703/end/vendorId on page 176 crocusShdslTtRpG703/end/vendorModel on page 176 crocusShdslTtRpG703/end/vendorSerial on page 176 crocusShdslTtRpG703/end/vendorSoftVersion on page 176 crocusShdslTtRpG703/end/eocSoftVersion on page 177 crocusShdslTtRpG703/end/shdslVersion on page 177 crocusShdslTtRpG703/end/eocState on page 177 crocusShdslTtRpG703/end/eocAlarmThresholds on page 178 crocusShdslTtRpG703/end/linePair[ ]/lineAttenuation on page 179 crocusShdslTtRpG703/end/linePair[ ]/signalNoise on page 179
This section describes the following actions: crocusShdslTtRpG703/repeater/loopbackActivation on page 179 The repeater[ ] and the end objects are not present in the containment tree by default. They are added automatically when you configure the eocHandling attribute. Refer to 5.2 - Configuring EOC handling on page 57. Exactly which information is retrieved from the remote SHDSL device(s) through the EOC channel depends on the setting of the eocHandling attribute. Refer to 5.2.4 - EOC retrieved information on page 60. The repeater[ ] and end objects contain the same attributes, therefore only the attributes of the end object are listed here. When the Crocus SHDSL G703 is configured for 1 pair operation, the repeater[ ] and end[ ] objects networkLinePair[2] and customerLinePair[2] still appear in the containment tree (although 1 pair operation has been configured).
crocusShdslTtRpG703/end/vendorId This attribute is only retrieved in case the eocHandling attribute is set to discovery, inventory, info or alarmConfiguration. This attribute displays information about the vendor of the repeater or end device. The vendorId structure contains the following elements: countryCode E.g. 65295 for Belgium. providerCode E.g. TLS_ for OneAccess. vendorSpecific
crocusShdslTtRpG703/end/vendorModel This attribute is only retrieved in case the eocHandling attribute is set to inventory, info or alarmConfiguration. This attribute displays the model of the repeater or end device. E.g. SHDSL TT 2P for a Crocus SHDSL Table Top 2 pair version. crocusShdslTtRpG703/end/vendorSerial This attribute is only retrieved in case the eocHandling attribute is set to inventory, info or alarmConfiguration. This attribute displays the serial number of the repeater or end device. For a OneAccess devices this is the deviceId attribute. crocusShdslTtRpG703/end/vendorSoftVersion This attribute is only retrieved in case the eocHandling attribute is set to inventory, info or alarmConfiguration. This attribute displays the version of the firmware used on the repeater or end device. For a OneAccess device this is the part after "/" of the T-code string displayed in the flashVersion attribute.
crocusShdslTtRpG703/end/eocSoftVersion This attribute is only retrieved in case the eocHandling attribute is set to discovery, inventory, info or alarmConfiguration. This attribute displays the EOC software version used on the repeater or end device. crocusShdslTtRpG703/end/shdslVersion This attribute is only retrieved in case the eocHandling attribute is set to discovery, inventory, info or alarmConfiguration. This attribute displays the SHDSL version used on the repeater or end device. crocusShdslTtRpG703/end/eocState This attribute is only retrieved in case the eocHandling attribute is set to discovery, inventory, info or alarmConfiguration. This attribute displays the state of the EOC channel. Remark about the repeater object While the modem is in loop condition (AL), the repeater cannot be reached. Therefore, the repeater/ eocState attribute will show offline while an AL test is activated. During a DL test, the eocState is not changed because the repeater can still be reached with EOC messages.
crocusShdslTtRpG703/end/eocAlarmThresholds This attribute is only retrieved in case the eocHandling attribute is set to info or alarmConfiguration. What this attribute displays depends on the setting of the line/eocHandling attribute: If eocHandling is set to info alarmConfiguration then the eocAlarmThresholds attribute displays the values as set in the line/linkAlarmThresholds attribute on the remote1 device or repeater. the eocAlarmThresholds attribute displays the values as set in the line/linkAlarmThresholds attribute on the central2 device. Remark Note that the values are rounded off. E.g. when 28.6 dB is configured on the central modem, then 28 dB is shown on the remote device or repeater.
1. The remote device is the device on which the channel attribute is set to remote. 2. The central device is the device on which the channel attribute is set to central. The eocAlarmThresholds structure contains the following elements: lineAttenuation signalNoise
crocusShdslTtRpG703/end/linePair[ ]/lineAttenuation This attribute is only retrieved in case the eocHandling attribute is set to info or alarmConfiguration. This attribute displays the line attenuation, in dB, as it is measured on the line pair of the repeater or end device. crocusShdslTtRpG703/end/linePair[ ]/signalNoise This attribute is only retrieved in case the eocHandling attribute is set to info or alarmConfiguration. This attribute displays the noise margin, in dB, as it is measured on the line pair of the repeater or end device. crocusShdslTtRpG703/repeater/loopbackActivation This action is only present in the repeater[ ] object. Use this action to set up a loop at the network side of the Crocus SHDSL Repeater:
Set the loop by selecting the action argument value initiateNetworkLoopback and executing the action (double-click the loopbackActivation string). Stop the loop by selecting the action argument value clearAllMaintenanceStates and executing the action (double-click the loopbackActivation string). Important remarks
.
You can only set up a loop at the network side of the Crocus SHDSL Repeater. Not at the customer side. You can only start the loopbackActivation action on the central device. Not on the remote device. You can only start the loopbackActivation action in case the line/eocHandling attribute is set to alarmConfiguration. The loopbackActivation action argument value noAction does nothing. It is only present to have a default value.
7.6
This section describes the following status attributes: crocusShdslTtRpG703/g703/timeSlots on page 181 crocusShdslTtRpG703/g703/los on page 181 crocusShdslTtRpG703/g703/ais on page 181 crocusShdslTtRpG703/g703/lfa on page 182 crocusShdslTtRpG703/g703/ifDescr on page 182 crocusShdslTtRpG703/g703/ifType on page 183 crocusShdslTtRpG703/g703/ifSpeed on page 183 crocusShdslTtRpG703/g703/ifClocking on page 183 crocusShdslTtRpG703/g703/ifOperStatus on page 183
crocusShdslTtRpG703/g703/timeSlots This attribute displays the time slots that are being used. This is especially useful in case you set the framing attribute to auto. Refer to 5.7.1 - Selecting unframed or framed mode on page 94. crocusShdslTtRpG703/g703/los This attribute displays (on / off) whether a Loss Of Signal has been detected. LOS is on when the incoming data is no longer present. E.g. the connection from the application towards the Crocus SHDSL G703 is interrupted. crocusShdslTtRpG703/g703/ais This attribute displays (on / off) whether an Alarm Indication Signal has been detected. AIS is on when the AIS signal (also called all ones) is detected on the incoming data. E.g. the application detected a problem and communicates this to the Crocus SHDSL G703.
crocusShdslTtRpG703/g703/lfa This attribute displays (on / off) whether a Loss of Frame Alignment has been detected. LFA is on when the Frame Alignment Signal (FAS), which is present in time slot 0 of the G.704 framed data, is not detected after a certain period. crocusShdslTtRpG703/g703/ifDescr This attribute displays the DTE interface description. It is an SNMP MIB2 parameter.
crocusShdslTtRpG703/g703/ifType This attribute displays the DTE interface type. It is an SNMP MIB2 parameter. The following table shows the default ifDescr and ifType attribute for each DTE interface. DTE interface G703 ifDescr value g703 ifType value other when the G703 interface is used in unframed mode e1 when the G703 interface is used in framed mode
crocusShdslTtRpG703/g703/ifSpeed This attribute displays the current DTE interface speed in bits per second (bps), e.g. 640000. When the DTE interface is down (ifOperStatus = down), the DTE interface speed is 0. crocusShdslTtRpG703/g703/ifClocking This attribute displays the clocking mode which is actually used by the Crocus SHDSL G703, e.g. internalPreferred. This is not necessarily the clocking mode you configured. It can be a clocking mode that is selected by the Crocus SHDSL G703 because it was not possible to select the clocking mode of your choice (for example, because the external clock signal is lost). crocusShdslTtRpG703/g703/ifOperStatus This attribute displays the current operational status of the DTE interface. The possible indications are: Value up down Description The DTE interface is up, data transfer is possible. The DTE interface is down, data transfer is not possible. For example, because there is no connection between the interface and the DTE.
7.7
This section describes the following status attributes: crocusShdslTtRpG703/operatingSystem/taskInfo on page 185
crocusShdslTtRpG703/operatingSystem/taskInfo The taskInfo table displays status information about the operating system. The table contains the following attributes: Attribute taskName taskStatus Description Name of the task. Current status. The task can have the following status values: load30s (%) load5m (%) runningInMedium (%) runningInHigh (%) awake: This task is actually running. asleep: This task is waiting on an event. inactive: This task slot is not active, i.e. no task has been assigned to this slot.
This 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 gives the percentage of time this task is running with medium priority during the last 30 seconds. Each task can be running with a low, medium or high priority. This element gives the percentage of time this task is running with high priority during the last 30 seconds. The percentage of time this task is running with low priority can be calculated using the following formula:100% - runningInMedium (%) - runningInHigh (%). This is the current value of the program counter. The program counter is the memory address for the current instruction of this task.
programCounter
Performance attributes
This chapter discusses the performance attributes of the Crocus SHDSL G703. The following gives an overview of this chapter. 8.1 - Performance attribute overview on page 188 8.2 - Introducing the performance attributes on page 190 8.3 - Line performance attributes on page 193 8.4 - Line pair performance attributes on page 196 8.5 - Repeater and end performance attributes on page 199 8.6 - G703 interface performance attributes on page 200 8.7 - Operating system performance attributes on page 204
8.1
> crocusShdslTtRpG703 Action: Cold Boot >> line h2Line h24Line d7Line line errorCount Action: retrain Action: testActivation Action: clearErrorCounter >>> linePair[ ]1 h2LineParameters h2Performance h24LineParameters h24Performance d7LineParameters d7Performance lineParameters performance >> repeater[ ]2 h2Line h24Line d7Line line >>> networkLinePair[ ]1 h2LineParameters h2Performance h24LineParameters h24Performance d7LineParameters d7Performance lineParameters performance
1. in case of a 2P version, two linePair objects are present: linePair [1] and linePair [2] 2. not present by default, is added automatically when setting the line/eocHandling attribute
>>> customerLinePair[ ]1 h2LineParameters h2Performance h24LineParameters h24Performance d7LineParameters d7Performance lineParameters performance >> end2 h2Line h24Line d7Line line >>> linePair[ ]1 h2LineParameters h2Performance h24LineParameters h24Performance d7LineParameters d7Performance lineParameters performance >> g7033 h2G703Performance h24G703Performance d7G703Performance g703Performance h2G826Performance h24G826Performance d7G826Performance g826Performance >> operatingSytem currUsedProcPower freeDataBuffers totalDataBuffers largestFreeBlockSize freeBlockCount freeMemory totalMemory usedProcPower taskInfo
8.2
Performance information can be used for the following: If network problems arise, information about the history of the communication link can be reviewed and 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 the network, e.g. network bottlenecks can be traced, etc.
Before discussing the performance attributes of the Crocus SHDSL G703 in detail, some general information on the performance attributes of the Crocus SHDSL G703 is given. The following gives an overview of this section: 8.2.1 - Introducing the performance timing on page 191 8.2.2 - Introducing the performance terms on page 192
8.2.1
The following table explains the performance information timing. Performance timing 2 hours,24 hours,7 days Description The performance information is accumulated during a certain time span, called a period. After a period, the accumulated performance information is written into a buffer. Then a new period starts. An interval contains several periods: 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. every period (15 minutes, 2 hours or 24 hours) the most recent measured and calculated values are added, and the oldest values are lost. since boot In this case, the performance information is kept since the latest cold boot of the Crocus SHDSL G703. This can be considered as a performance information summary.
The Crocus SHDSL G703 does not contain a real-time clock, therefore time information is related to its internal clock. To allow you to situate the time intervals in the real time, the sysUpTime attribute is returned together with the performance information. It reflects the time since the latest cold boot of the Crocus SHDSL G703. Only the available performance information is displayed. If the interrogation happens shortly after boot, no values are displayed. For example for the 24 hours intervals, the new performance information is available only when a complete time span (i.e. 2 hours) has elapsed.
8.2.2
The following table explains the performance information terms. Term sysUpTime min, max, avrg count time Description Reflects the time since the latest cold boot of the Crocus SHDSL G703. Display the minimum, maximum and average values calculated for the corresponding period.E.g. min-max-avrg value of the noise margin. Counts the number of times an event occurred during the corresponding period.E.g. the number of retrains. Indicates the duration of an event during the corresponding period.E.g. the time during which the line is up.
8.3
This section describes the following performance attributes: crocusShdslTtRpG703/line/<h2/h24/d7>Line on page 194 crocusShdslTtRpG703/line/line on page 194 crocusShdslTtRpG703/line/errorCount on page 194
This section describes the following actions: crocusShdslTtRpG703/line/retrain on page 195 crocusShdslTtRpG703/line/testActivation on page 195 crocusShdslTtRpG703/line/clearErrorCounter on page 195
crocusShdslTtRpG703/line/<h2/h24/d7>Line This structured value displays the 2 hours, 24 hours and 7 days line performance. The <h2/h24/d7>Line structured value elements are the following: Element sysUpTime linkDownCount linkDownTime For the corresponding period, this value displays the elapsed time since the last cold boot. the number of times the link went down. the total amount of time the link was down.
crocusShdslTtRpG703/line/line This structured value displays the line performance since the last cold boot. Except for sysUpTime, the structured value elements are the same as for the <h2/h24/d7>Line attribute. crocusShdslTtRpG703/line/errorCount This attribute displays the amount of detected errors since the start of an ET, AL-ET or RDL-ET test. Every time a new ET, AL-ET or RDL-ET is started, the errorCount attribute is reset to 0.
crocusShdslTtRpG703/line/retrain Use this action to initiate a retrain cycle. Double click on the retrain string to execute the action. crocusShdslTtRpG703/line/testActivation Use this action to perform a test on the Crocus SHDSL G703. These tests are useful to trace possible problems. Possible tests are: no, al, dl, rdl, et, alEt, rdlEt. To execute a test, proceed as follows: Step 1 2 Action In the TMA window, select the object line and the group Performance or Status. In the action window of TMA, click the left mouse button on the field under the heading Argument Value.
For more information on these tests, refer to Chapter 12 - Diagnostic tests on page 245. crocusShdslTtRpG703/line/clearErrorCounter Use this action to clear the value of the errorCount attribute. This could be useful, for example, to reset the error counter after the unstable period (in which errors occur anyhow) shortly after the initiation of a test. Double click on the clearErrorCounter string to execute the action.
8.4
This section describes the following performance attributes: crocusShdslTtRpG703/line/linePair[ ]/<h2/h24/d7>LineParameters on page 197 crocusShdslTtRpG703/line/linePair[ ]/lineParameters on page 197 crocusShdslTtRpG703/line/linePair[ ]/<h2/h24/d7>Performance on page 198 crocusShdslTtRpG703/line/linePair[ ]/performance on page 198
In case of a Crocus SHDSL G703 2P, two linePair objects are present: linePair [1] and linePair [2].
crocusShdslTtRpG703/line/linePair[ ]/<h2/h24/d7>LineParameters This structured value displays the 2 hours, 24 hours and 7 days line pair parameters. The <h2/h24/ d7>LineParameters structured value elements are the following: Element sysUpTime lineAttenuationMin (dB) lineAttenuationMax (dB) lineAttenuationAvrg (dB) signalNoiseMin (dB) signalNoiseMax (dB) signalNoiseAvrg (dB) For the corresponding period, this value displays the elapsed time since the last cold boot. the minimum line attenuation that was measured. the maximum line attenuation that was measured. the average line attenuation that was calculated. the minimum signal to noise ratio that was measured. the maximum signal to noise ratio that was measured. the average signal to noise ratio that was calculated.
crocusShdslTtRpG703/line/linePair[ ]/lineParameters This structured value displays the line pair parameters since the last cold boot. Except for sysUpTime, the structured value elements are the same as for the <h2/h24/d7>LineParameters attribute.
crocusShdslTtRpG703/line/linePair[ ]/<h2/h24/d7>Performance This structured value displays the 2 hours, 24 hours and 7 days line pair performance. The <h2/h24/d7>Performance structured value elements are the following: Attribute sysUpTime codeViolations errSec sevErrSec unavailableSec loswSec moniSec For the corresponding period, this attribute displays the time since the latest cold boot. the number of errored SHDSL frames that was counted. the number of errored seconds that was counted. the number of severely errored seconds that was counted. the number of unavailable seconds that was counted. the number of lost synchronisation words that was counted. the number of monitored seconds.
For the correct and unambiguous definition of code violations, errored and severely errored seconds, unavailability and lost sync words, refer to the recommendation G.826. crocusShdslTtRpG703/line/linePair[ ]/performance This structured value displays the line pair performance since the last cold boot. Except for sysUpTime, the structured value elements are the same as for the <h2/h24/d7>Performance attribute.
8.5
The repeater[ ] and the end objects are not present in the containment tree by default. They are added automatically when you configure the eocHandling attribute. Refer to 5.2 - Configuring EOC handling on page 57. Exactly which information is retrieved from the remote SHDSL device(s) through the EOC channel depends on the setting of the eocHandling attribute. Refer to 5.2.4 - EOC retrieved information on page 60. The performance information of the line and line pairs of the repeater and end device is only retrieved in case the eocHandling attribute is set to info or alarmConfiguration. Other than that, the repeater[ ] and end objects contain the same performance attributes as the line object. Refer to 8.3 - Line performance attributes on page 193 for more information on the line attributes. 8.4 - Line pair performance attributes on page 196 for more information on the line pair attributes.
When the Crocus SHDSL G703 is configured for 1 pair operation, the repeater[ ] and end[ ] objects networkLinePair[2] and customerLinePair[2] still appear in the containment tree (although 1 pair operation has been configured).
Note that the sysUpTime in the performance attributes of the repeater[ ] and end objects is not the elapsed time since the last cold boot, but the elapsed time since the creation of the repeater[ ] or end object.
8.6
This section describes the following performance attributes: crocusShdslTtRpG703/g703/<h2/h24/d7>G703Performance on page 201 crocusShdslTtRpG703/g703/g703Performance on page 201 crocusShdslTtRpG703/g703/<h2/h24/d7>G826Performance on page 202 crocusShdslTtRpG703/g703/g826Performance on page 202
crocusShdslTtRpG703/g703/<h2/h24/d7>G703Performance This structured value displays the 2 hours, 24 hours and 7 days performance summary of the G703 interface. The <h2/h24/d7>G703Performance structured value elements are the following: Element sysUpTime losCount losTime aisCount aisTime lfaCount lfaTime For 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. This is only relevant when working in framed mode. the amount of time a Loss of Frame Alignment condition was active. This is only relevant when working in framed mode.
Also see G703 interface performance definitions. crocusShdslTtRpG703/g703/g703Performance This structured value displays the performance summary of the G703 interface since the last cold boot. Except for sysUpTime, the structured value elements are the same as for the <h2/h24/d7>G703Performance attribute.
crocusShdslTtRpG703/g703/<h2/h24/d7>G826Performance This structured value displays the 2 hours, 24 hours and 7 days G.826 performance summary of the G703 interface. The <h2/h24/d7>G826Performance structured value elements are the following: Element sysUpTime errBlocks errSec sevErrSec unavailCount unavailTime bBErrors For 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-T recommendation G.826 Annex A). the amount of time the interface was down. the number of background block errors that was counted.
Also refer to G703 interface performance definitions. crocusShdslTtRpG703/g703/g826Performance This structured value displays the G.826 performance summary of the G703 interface since the last cold boot. Except for sysUpTime, the structured value elements are the same as for the <h2/h24/ d7>G826Performance attribute. crocusShdslTtRpG703/g703/testActivation Use this action to activate a test on the G703 interface. These tests are useful to trace possible problems. First select the test (i.e. the argument value), then execute the testActivation action. You can limit the duration of an active test on the G703 interface by using the attribute crocusShdslTtRpG703/line/testDuration on page 138. The testActivation action has the following argument values: Value no internalLoopback Description No test is activated. In case you want to stop a test, then select this value and execute the testActivation action. Starting an internalLoopback test on the G703 interface loops the data coming from the DTE back to the DTE.
G703 interface performance definitions The following table lists some of the definitions that are used in the ITU-T recommendations that apply on the G703 interface. They are listed here for completeness only. For more detailed information, refer to the recommendations themselves. Term defect Definition A defect is one of the following conditions: Errored Block (EB) Errored Second (ES) Severely Errored Second (SES) 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).
A data frame that contains one or more errors. In case of G.704 framing a frame is time slot 0 up to time slot 31. 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 1 defect. The measurement of EBs depends on the operation mode: Framed without CRC-4: the error detection occurs based on the detected Frame Alignment Signal (FAS) bit errors; 28 FAS bit errors per second matches a Bit Error Rate (BER) of 10-3 or more. Framed with CRC-4: the error detection occurs based on CRC-4.
unavailability
Matches a period of 10 or more consecutive SESs. Refer to G.826 Annex A for a complete definition.
8.7
This section describes the following performance attributes: crocusShdslTtRpG703/operatingSystem/currUsedProcPower on page 205 crocusShdslTtRpG703/operatingSystem/freeDataBuffers on page 205 crocusShdslTtRpG703/operatingSystem/totalDataBuffers on page 205 crocusShdslTtRpG703/operatingSystem/largestFreeBlockSize on page 205 crocusShdslTtRpG703/operatingSystem/freeBlockCount on page 205 crocusShdslTtRpG703/operatingSystem/freeMemory on page 205 crocusShdslTtRpG703/operatingSystem/totalMemory on page 205 crocusShdslTtRpG703/operatingSystem/usedProcPower on page 206 crocusShdslTtRpG703/operatingSystem/taskInfo on page 206
crocusShdslTtRpG703/operatingSystem/currUsedProcPower This is the amount of processing power used during the last 650 milliseconds, expressed as a percentage of the total available processing power. crocusShdslTtRpG703/operatingSystem/freeDataBuffers The processor uses buffers for storing the packets during processing and/or queuing. Each buffer has a 256 byte size, headers included. This attribute is the number of data buffers currently not in use and available for e.g. incoming data. crocusShdslTtRpG703/operatingSystem/totalDataBuffers This is the total number of available data buffers. crocusShdslTtRpG703/operatingSystem/largestFreeBlockSize The processor uses RAM memory for storing internal information and buffering (see totalDataBuffers). The different tasks allocate RAM memory on request. Tasks may also free memory again. In this way the total RAM memory becomes fragmented. This attribute gives the size of the largest contiguous free memory block expressed in bytes. crocusShdslTtRpG703/operatingSystem/freeBlockCount This is the number of free contiguous memory blocks. crocusShdslTtRpG703/operatingSystem/freeMemory This is the total free memory expressed in bytes. crocusShdslTtRpG703/operatingSystem/totalMemory This is the total RAM memory expressed in bytes.
crocusShdslTtRpG703/operatingSystem/usedProcPower This table lists the used processing power for the 11 most recent 30 seconds intervals. The processing power is expressed as a percentage of the total processing power. Each entry in the attribute usedProcPower is composed of the following attributes: Value sysUpTime minimumPP (%) averagePP (%) maximumPP (%) Description Displays the elapsed time since the last cold boot. The next values are for the 30 seconds period before this relative time stamp. This is the minimum percentage of processing power in use during the last 30 seconds. This is the average percentage of processing power in use during the last 30 seconds. This is the maximum percentage of processing power in use during the last 30 seconds.
crocusShdslTtRpG703/operatingSystem/taskInfo This attribute contains status information concerning the different tasks running on the processor. It is a table grouping up to 31 task slots, which is the maximum number of parallel tasks running on the processor's operating system. This attribute contains the same information as taskInfo in the status group (refer to 7.7 - Operating system status attributes on page 184).
Alarm attributes
This chapter discusses the alarm attributes of the Crocus SHDSL G703. The following gives an overview of this chapter. 9.1 - Alarm attribute overview on page 208 9.2 - Introducing the alarm attributes on page 210 9.3 - General alarms on page 218 9.4 - Line alarms on page 221 9.5 - Line pair alarms on page 223 9.6 - Repeater and end alarms on page 226 9.7 - Interface alarms on page 229
9.1
> crocusShdslTtRpG703 totalAlarmLevel alarmInfo notResponding alarmSyncLoss configChanged access remoteAlarm unknownState coldBoot warmBoot localPowerFail codeConsistencyFail configConsistencyFail Action: Cold Boot >> line alarmInfo linkDown testActive invalidNumRepeaters >>> linePair[ ]1 alarmInfo linkDown lineAttenuation signalNoise errSecRatioExceeded sevErrSecRatioExceeded >> repeater[ ]2 alarmInfo linkDown >>> networkLinePair[ ]1 alarmInfo linkDown lineAttenuation signalNoise errSecRatioExceeded sevErrSecRatioExceeded
1. in case of a 2P version, two linePair objects are present: linePair [1] and linePair [2] 2. not present by default, is added automatically when setting the line/eocHandling attribute
>>> customerLinePair[ ]1 alarmInfo linkDown lineAttenuation signalNoise errSecRatioExceeded sevErrSecRatioExceeded >> end2 alarmInfo linkDown >>> linePair[ ]1 alarmInfo linkDown lineAttenuation signalNoise errSecRatioExceeded sevErrSecRatioExceeded >> g7033 alarmInfo linkDown ais sq lossOfTiming
9.2
Before discussing the alarm attributes of the Crocus SHDSL G703 in detail, some general information on the alarm attributes of the Crocus SHDSL G703 is given. The following gives an overview of this section: 9.2.1 - Configuration alarm attributes on page 211 9.2.2 - General alarm attributes on page 215 9.2.3 - Alarm signalling on page 217
9.2.1
This section explains the attributes that allow you to configure the alarm behaviour of the Crocus SHDSL G703. These configuration alarm attributes are: crocusShdslTtRpG703//alarmMask on page 212 crocusShdslTtRpG703//alarmLevel on page 212 crocusShdslTtRpG703//remoteAlarmMask on page 214
crocusShdslTtRpG703//alarmMask Use this attribute to mask or unmask the alarms of an object. This determines whether an active alarm is forwarded to the central management system (e.g. TMA Element Management or HP OpenView) or not. causes a change of colour in the subsystem picture (refer to Chapter 10 - TMA subsystem picture of the Crocus SHDSL G703 on page 231).
The alarms in the alarmMask attribute have the following values: Value enabled disabled Is the active alarm being forwarded to the central management system? Does the active alarm cause a change of colour in the subsystem picture? 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 the alarm. I.e. even if an alarm is set to disabled in the alarmMask of an object, if the alarm condition is fulfilled then the alarm will be set to on in the alarmInfo of that object. However, because this alarm is disabled it will not be sent to the central management system. Only the most important alarms are unmasked (i.e. enabled) by default. All other alarms are masked (i.e. disabled).
crocusShdslTtRpG703//alarmLevel Use this attribute to assign a priority level to each alarm of the corresponding object. The alarm level range 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 of the top object crocusShdslTtRpG703.
crocusShdslTtRpG703//remoteAlarmMask This attribute is present on the TT only. The remoteAlarmMask attribute enables or disables for each alarm of the corresponding object, whether: a visual indication is generated (blinking error LED). an alarm is sent to the remote Crocus SHDSL G703.
9.2.2
This section describes the following alarm attributes: crocusShdslTtRpG703/totalAlarmLevel on page 216 crocusShdslTtRpG703//alarmInfo on page 216
crocusShdslTtRpG703/totalAlarmLevel This attribute is only present in the top object of the containment tree of the Crocus SHDSL G703, crocusShdslTtRpG703. It displays the priority level of an unmasked, active alarm. When several alarms are generated at the same time, the highest priority level is shown. If the alarm levels are set in a structured manner, one look at 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. TMA Element Management or HP OpenView) where it determines the colour of the icon. This colour is an indication of the severity of the alarm. crocusShdslTtRpG703//alarmInfo The alarmInfo contains the actual alarm information of the corresponding object. This information is updated each time there is a change in the status of an alarm within this object. The alarmInfo attributes are: Attribute discriminator currentAlarms previousAlarms alarmMask alarmLevel Displays for the corresponding object the total number of alarm status changes in this object since the last cold boot. the current alarm status of this object. the previous alarm status of this object. the alarmMask as configured in the Configuration group. the alarmLevel as configured in the Configuration group.
9.2.3
Alarm signalling
If you do not have a central management system, you could perform alarm signalling with the alarm contacts of the CN4 card nest. Example Suppose the following situation: On a remote Crocus SHDSL TT the configChanged alarm of the Crocus SHDSL G703 object is set to enabled in the remoteAlarmMask. In other words: crocusShdslTtRpG703/remoteAlarmMask/configChanged = enabled. On a central Crocus SHDSL CV the remoteAlarm of the top object is set to enabled in the alarmContactHighMask. In other words: crocusShdslTtRpG703/alarmContactHighMask/remoteAlarm = enabled. The high alarm contacts of the CN4 card nest are connected in a circuit with a light bulb.
Now the following happens: Phase 1 2 3 4 Situation Someone changes the configuration of the Crocus SHDSL TT. On the Crocus SHDSL TT the configChanged alarm is enabled in the remoteAlarmMask. On the Crocus SHDSL CV the remoteAlarm is enabled in the alarmContactHighMask. The high alarm contacts of the CN4 card nest close. Result On the Crocus SHDSL TT the configChanged alarm becomes active. A remote alarm is sent to the Crocus SHDSL CV. The high alarm contacts of the CN4 card nest close. The light bulb lights up.
9.3
General alarms
This section describes the following alarm attributes: crocusShdslTtRpG703/alarmInfo on page 219
This section describes the following action: crocusShdslTtRpG703/Cold Boot on page 220
Refer to 9.2 - Introducing the alarm attributes on page 210 for the general alarm attributes.
crocusShdslTtRpG703/alarmInfo The different alarms related to the crocusShdslTtRpG703 object together with their explanation and their default alarmMask and alarmLevel value are given in the following table: The alarm is generated Default value alarmMask notResponding when the Crocus SHDSL G703 does not respond on the polling session of the management concentrator. when the internal alarm buffer overflows. when the configuration of the Crocus SHDSL G703 is changed. when a management session is started on the Crocus SHDSL G703 itself. This alarm is not activated when the management session is established through a management concentrator. Example The alarm is activated in case of a TMA, TMA CLI, terminal (CLI or ATWIN) or EasyConnect session via the control connector of the Crocus SHDSL G703. is not activated in case of any management session (TMA, terminal, Telnet, HTTP, etc.) established through a management concentrator on the Crocus SHDSL G703. disabled disabled 0 0 enabled alarmLevel 4
4 1 1
remoteAlarm unknownState
when the remote Crocus SHDSL G703 is in alarm condition. each time a new Crocus SHDSL G703 is added to the network and before the management concentrator has completed a first successful polling session. when the Crocus SHDSL G703 performs a cold boot. when the Crocus SHDSL G703 performs a warm boot.
coldBoot warmBoot
disabled disabled
1 1
The alarm
is generated
localPowerFail codeConsistencyFail
when the local power of the Crocus SHDSL G703 fails when the software consistency imposed by the management concentrator on the Crocus SHDSL G703 fails. For example, because of a loss of contact. On the management concentrator, check the status attribute nmsgroup/softConsistencyStatus to determine the problem.
disabled disabled
configConsistencyFail
when the configuration consistency imposed by the management concentrator on the Crocus SHDSL G703 fails. For example, because of a loss of contact.On the management concentrator, check the status attributes nmsgroup/objectTable/configState and configDiag to determine the problem.
disabled
crocusShdslTtRpG703/Cold Boot This action will reboot the Crocus SHDSL G703 while the power stays up (the Crocus SHDSL G703 also reboots if it is powered down and up again).
9.4
Line alarms
This section describes the following alarm attribute: crocusShdslTtRpG703/line/alarmInfo on page 222
Refer to 9.2 - Introducing the alarm attributes on page 210 for the general alarm attributes.
crocusShdslTtRpG703/line/alarmInfo The different alarms related to the line object together with their explanation and their default alarmMask and alarmLevel value are given in the following table: The alarm is generated Default value alarmMask linkDown when no data link towards the remote Crocus SHDSL G703 is present.It does not necessarily mean that the line pair is disconnected. If the line quality is so bad that data transfer is not possible, a linkDown alarm is generated. when the number of repeaters you entered in the line/numExpectedRepeaters configuration attribute does not match the actual number of repeaters discovered by the Crocus SHDSL G703.The actual number of repeaters discovered by the Crocus SHDSL G703 can be seen in the line/numDiscoveredRepeaters status attribute. when a test is active. enabled alarmLevel 3
invalidNumRepeaters
disabled
testActive
disabled
9.5
This section describes the following alarm attributes: crocusShdslTtRpG703/line/linePair[ ]/alarmInfo on page 224
In case of a Crocus SHDSL G703 2P, two linePair objects are present: linePair [1] and linePair [2]. Refer to 9.2 - Introducing the alarm attributes on page 210 for the general alarm attributes.
crocusShdslTtRpG703/line/linePair[ ]/alarmInfo The different alarms related to the linePair[ ] object together with their explanation and their default alarmMask and alarmLevel value are given in the following table: The alarm is generated Default value alarmMask linkDown when no data link towards the remote Crocus SHDSL G703 is present. It does not necessarily mean that the line pair is disconnected. If the line quality is so bad that data transfer is not possible, a linkDown alarm is generated. lineAttenuation when the line attenuation exceeds the value configured in the line/linkAlarmThresholds configuration attribute for at least 10 seconds. The alarm is cleared when the line attenuation drops below this value for at least 10 seconds. Note however that in case the line/eocHandling configuration attribute is set to alarmConfiguration, the central SHDSL device forces the remote SHDSL device to use the linkAlarmThresholds/lineAttenuation as configured on the central device. For more information, refer to 5.2.2 - The EOC handling attribute on page 59 5.2.4 - EOC retrieved information on page 60 disabled 1 enabled alarmLevel 3
The alarm
is generated
signalNoise
when the signal noise exceeds the value configured in the line/linkAlarmThresholds configuration attribute for at least 10 seconds. The alarm is cleared when the signal noise drops below this value for at least 10 seconds. Note however that in case the line/eocHandling configuration attribute is set to alarmConfiguration, the central SHDSL device forces the remote SHDSL device to use the linkAlarmThresholds/signalNoise as configured on the central device. For more information, refer to 5.2.2 - The EOC handling attribute on page 59 5.2.4 - EOC retrieved information on page 60
disabled
errSecRatioExceeded
when the errored seconds ratio exceeds the value configured in the line/linkAlarmThresholds configuration attribute within a 15 minute period1. The alarm is cleared when the errored seconds ratio drops below this value within a 15 minute period. when the severely errored seconds ratio exceeds the value configured in the line/ linkAlarmThresholds configuration attribute within a 15 minute period1. The alarm is cleared when the severely errored seconds ratio drops below this value within a 15 minute period.
disabled
sevErrSecRatioExceeded
disabled
1. The 15 minute periods run synchronous with the 2 hour periods of the line/h2Line performance attribute. Because alarms are raised or cleared within 15 minute periods, there is a delay in the alarm status. For example, suppose that in the first minute of a 15 minute period the errSecRatioExceeded value is exceeded, then the errSecRatioExceeded alarm is raised when the full 15 minute period has passed. The alarm is only cleared if in the next 15 minute period the errSecRatioExceeded value is not exceeded.
9.6
This section describes the following alarm attributes: crocusShdslTtRpG703/end/linePair[ ]/alarmInfo on page 227 The repeater[ ] and the end objects are not present in the containment tree by default. They are added automatically when you configure the eocHandling attribute. Refer to 5.2 - Configuring EOC handling on page 57 Exactly which information is retrieved from the remote SHDSL device(s) through the EOC channel depends on the setting of the eocHandling attribute. Refer to 5.2.4 - EOC retrieved information on page 60. The repeater[ ] and end objects contain the same attributes, therefore only the attributes of the end object are listed here. When the Crocus SHDSL G703 is configured for 1 pair operation, the repeater[ ] and end[ ] objects networkLinePair[2] and customerLinePair[2] still appear in the containment tree (although 1 pair operation has been configured).
crocusShdslTtRpG703/end/linePair[ ]/alarmInfo The different alarms related to the linePair[ ] object together with their explanation and their default alarmMask and alarmLevel value are given in the following table:l The alarm is generated Default value alarmMask linkDown when no data link towards the remote Crocus SHDSL G703 is present. It does not necessarily mean that the line pair is disconnected. If the line quality is so bad that data transfer is not possible, a linkDown alarm is generated. lineAttenuation when the line attenuation exceeds the value configured in the line/linkAlarmThresholds configuration attribute of the local device for at least 10 seconds. The alarm is cleared when the line attenuation drops below this value for at least 10 seconds. Note however that in case the line/eocHandling configuration attribute is set to alarmConfiguration, the central SHDSL device forces the remote SHDSL device and any intermediary repeater to use the linkAlarmThresholds/lineAttenuation as configured on the central device. For more information, refer to 5.2.2 - The EOC handling attribute on page 59 5.2.4 - EOC retrieved information on page 60 disabled 1 enabled alarmLevel 3
The alarm
is generated
signalNoise
when the signal noise exceeds the value configured in the line/linkAlarmThresholds configuration attribute of the local device for at least 10 seconds. The alarm is cleared when the signal noise drops below this value for at least 10 seconds. Note however that in case the line/eocHandling configuration attribute is set to alarmConfiguration, the central SHDSL device forces the remote SHDSL device and any intermediary repeater to use the linkAlarmThresholds/signalNoise as configured on the central device. For more information, refer to 5.2.2 - The EOC handling attribute on page 59 5.2.4 - EOC retrieved information on page 60
disabled
errSecRatioExceeded
when the errored seconds ratio exceeds the value configured in the line/linkAlarmThresholds configuration attribute of the local device within a 15 minute period1. The alarm is cleared when the errored seconds ratio drops below this value within a 15 minute period. when the severely errored seconds ratio exceeds the value configured in the line/ linkAlarmThresholds configuration attribute of the local device within a 15 minute period1. The alarm is cleared when the severely errored seconds ratio drops below this value within a 15 minute period.
disabled
sevErrSecRatioExceeded
disabled
1. The 15 minute periods run synchronous with the 2 hour periods of the line/h2Line performance attribute. Because alarms are raised or cleared within 15 minute periods, there is a delay in the alarm status. For example, suppose that in the first minute of a 15 minute period the errSecRatioExceeded value is exceeded, then the errSecRatioExceeded alarm is raised when the full 15 minute period has passed. The alarm is only cleared if in the next 15 minute period the errSecRatioExceeded value is not exceeded. The local configured thresholds are used to generate the errSecRatioExceeded alarm, the sevErrSecRatioExceeded alarm and the bBErrRatioExceeded alarm, so these alarms can differ from the alarms generated on the device at the other site of the line.
9.7
Interface alarms
This section describes the following alarm attributes: crocusShdslTtRpG703/<dteInterface>/alarmInfo on page 230
Refer to 9.2 - Introducing the alarm attributes on page 210 for the general alarm attributes.
crocusShdslTtRpG703/<dteInterface>/alarmInfo The different alarms related to the <dteInterface> object together with their explanation and their default alarmMask and alarmLevel value are given in the following table: The alarm is generated Default value alarmMask linkDown (for G703) ais (G703) when there is a loss of signal. I.e. the transmit data is no longer present. when an Alarm Indication Signal (AIS) has been detected in the incoming G703 transmit data (the alarm signal needs to be active for at least one sceond). It means the application has detected an error. when the Frame Alignment Signal (FAS), which is present in time slot 0 of the G.704 framed data, is not detected after a certain period.This alarm is also generated when the attribute crc4Insertion is set to enabled, but no CRC is sent by the application. (This does not apply when the crc4Insertion is set to auto.) enabled alarmLevel 3
disabled
lfa
disabled
sq (G703)
when the sqThreshold value, i.e. the number disabled of errored seconds, is exceeded within the sqTime.For example, if 10 (default) or more errored seconds occur within 1 minute (default), then a signal quality alarm is generated.Refer to the configuration attributes sqThreshold and sqTime for more information. when an external clocking mode is configured but the external clock signal is not present. In that case the Crocus SHDSL G703 switches to internal clocking mode. enabled
lossOfTiming
10.1
To display the subsystem picture of the Crocus SHDSL G703, proceed as follows: Step 1 2 Action Open a TMA session on the Crocus SHDSL G703. Refer to 4.1 - Starting TMA on the Crocus SHDSL G703 on page 42. In the TMA window, press on the subsystem picture button: The subsystem picture is displayed: .
10.2
This section displays and labels the different elements of the subsystem picture. It also explains how the visual indications should be interpreted. Below, the Crocus SHDSL G703 subsystem picture is displayed.
When TMA fails to upload the sub-system picture info (e.g. because TMA is disconnected), then the LEDs and connectors are greyed-out.
The table below gives an overview of the subsystem picture elements and what they indicate: Element LED indicators Description They reflect the actual status of the Crocus SHDSL G703. The LED indication on the subsystem picture corresponds with the LED indication on the Crocus SHDSL G703 itself. For more information on the interpretation of the LEDs, refer to 2.9 Front panel LED indicators on page 30.
DTE interface
This reflects the status of the DTE interface. The possible indications are: green: No alarm of the <dteInterface> object is active. red: An (unmasked) alarm of the <dteInterface> object is active.
The layout of the connector also gives an indication of the type of DTE interface which is currently used in the Crocus SHDSL G703. Remark The colours of the DTE interface only change if the alarms related to the <dteInterface> object are set to enabled in the alarmMask. For more information, refer to 9.2.1 - Configuration alarm attributes on page 211.
line
This reflects the status of the line. The possible indications are: green outside: No (unmasked) alarm of the line object is active. red outside: An (unmasked) alarm of the line object is active. green inside: No (unmasked) alarm of the linePair object is active. red inside: An (unmasked) alarm of the linePair object is active.
The colours of the interfaces only change if the alarms related to the line and/or linePair object are set to enabled in the alarmMask. For more information, refer to 9.2.1 - Configuration alarm attributes on page 211. Example: If you want to avoid that the outside of the line connector turns red every time you execute a test, set the alarm testActive in the alarmMask of the line object to disabled. Note that by doing so, you also disable the sending of the testActive alarm to the central management system (e.g. HP OpenView).
11 Software download
This chapter explains how to download new loader and application software (also called firmware) into the flash memory of the Crocus SHDSL G703. The following gives an overview of this chapter. 11.1 - What is boot, loader and application software? on page 236 11.2 - Important download issues on page 240 11.3 - Downloading with TMA on page 241 11.4 - Downloading with TML on page 242 11.5 - Downloading in loader mode on page 243
11.1
This section explains the difference between boot, loader and application software. The following gives an overview of this section: 11.1.1 - What is boot software? on page 237 11.1.2 - What is loader software? on page 238 11.1.3 - What is application software? on page 239
However, while in loader mode the Crocus SHDSL G703 can not transfer data be accessed with TMA be configured.
The loader mode DIP switch You can force the Crocus SHDSL G703 in loader mode using a DIP switch. This is necessary in case you want to download new application software. How to identify the Crocus SHDSL G703 runs in loader mode? When the Crocus SHDSL G703 runs in loader mode the PWR LED is on the TST LED is on.
When the Crocus SHDSL G703 switches from loader mode to application mode, the TST LED flashes 5 times.
11.2
When you upgrade the application software of the Crocus SHDSL G703, do not power off the Crocus SHDSL G703 until the TST LED stops blinking. Else the application software upgrade will fail. When you upgrade the application software of the Crocus SHDSL G703, do not power off the Crocus SHDSL G703 as long as only the PWR LED blinks and all the other LEDs are off. Else the application software upgrade will fail. When a Crocus SHDSL G703 is managed by a management concentrator (i.e. it is present in the management concentrator its objectTable and being polled), it is no longer possible to download software through the Crocus SHDSL G703 its control connector using TMA or TML. Instead, use the software distribution feature of the management concentrator. It is not possible to use the software distribution feature of a management concentrator to download loader software to a Crocus SHDSL G703. When you download new loader software, you also have to download the application software again.
11.3
To download application software with TMA, proceed as follows: Step 1 2 3 Action Establish a link between TMA and the Crocus SHDSL G703 through the control connector. Refer to 4.1 - Starting TMA on the Crocus SHDSL G703 on page 42. In the TMA window select Tools Download In the TMA - Download window, select the Options tab:
Set the initial transfer speed to 9600 bps. If you set the maximum transfer speed to 115200 bps, the actual transfer speed will be negotiated between the computer and the Crocus SHDSL G703 and will be between 9600 bps and 115200 bps.
4 5
In the TMA - Download window, select the Configuration tab, and press Add In the Remote filename window:
1. Select the filename you want to download (Txxxxxxx.00). 2. Type CONTROL in the Remote file field. 3. Press Open. 6 When the TMA - Download window reappears, press OK.
The Crocus SHDSL G703 falls back to loader mode, then a DOS window opens
and shows the download progress.
11.4
When downloading with TMA (as explained in the previous section), you actually evoke TML (Total Memory Loader) through TMA. You can also use TML without opening TMA. To download application software with TML, proceed as follows: Step 1 Action Connect a serial port of your computer (e.g. COM1) through a straight DB9 male - female cable with the control connector of your Crocus SHDSL G703 as shown in the following figure:
2 3 4 5
Open a DOS window on your computer. Go to the directory where the TML executable is located. Typically this is C:\Program Files\TMA. Place the software file you want to download in this directory. Type the following command to download: application software: tml -c1 -v -f<Txxxxxxx.00>@CONTROL loader software: tml -c1 -b -f<Txxxxxxx.00>@CONTROL
where
tml is the executable (Total Memory Loader) to download files to the OneAccess
SHDSL G703. To see a list of all the possible TML options: type TML in your DOS windows and press the ENTER key. 6 If you press the ENTER key, the software download begins.If you used the -v option together with the TML command, a graphical bar shows the download progress.
11.5
When a download of application software has failed or when a flash memory error occurs, the Crocus SHDSL G703 normally remains in loader mode. In other words, you can immediately retry to download the application software again. However, it may be possible that the application software becomes corrupt making the Crocus SHDSL G703 inoperative and inaccessible to TMA. In that case, new application software can still be downloaded by forcing the Crocus SHDSL G703 in loader mode using a DIP switch (refer to 3.1.2 - DIP switches of the TT on page 36. To download application software to a Crocus SHDSL G703 in loader mode, proceed as follows: Step 1 2 Action Disconnect the Crocus SHDSL G703 from the power supply. Set DIP switch bank DS1 position 2 to off. To locate this DIP switch bank and for the DIP switch setting procedure, refer to 3 - DIP switches and straps of the Crocus SHDSL G703 on page 33. 3 Reconnect the power supply to the Crocus SHDSL G703.
12 Diagnostic tests
This chapter describes the diagnostic tests of the Crocus SHDSL G703. The following gives an overview of this chapter. 12.1 - Introducing the diagnostic tests on page 246 12.2 - Line tests on page 247 12.3 - Interface tests on page 255
12.1
This section gives some introductory notes on the diagnostic tests. Test originators and corresponding priority levels The following table shows the possible test originators and their priority level. Diagnostic tests can be generated by the management system, the keyboard, the application via the interface, the remote Crocus SHDSL G703,(RDL test only) Example Phase 1 2 Action Start an interface test, for example AL. Start a test in TMA, for example RDL. Result The AL test is started. The AL test stops, and the RDL test starts. This because the interface test has a lower priority than the TMA test. The interface test, in this case AL, is restarted. with the priority level high. medium. low. low.
Important remarks Within the same priority level, the rule "first come, first served" applies. The management system can stop a test started by any originator. During the execution of a test, no normal data communication is possible. In order to avoid that the test would stay active for an indefinite time, and thus blocking the normal data transfer, a testDuration attribute is linked to the tests (refer to 6.3 - Line configuration attributes on page 131). This attribute determines how long a test lasts.
12.2
Line tests
This section describes the diagnostic tests you can start on the line of the Crocus SHDSL G703. The following gives an overview of this section: 12.2.1 - The line test action on page 248 12.2.2 - Error test on page 250 12.2.3 - Analogue loop on page 251 12.2.4 - Remote digital loop on page 252 12.2.5 - Digital loop on page 254
The location of the testActivation attribute in the Crocus SHDSL G703 containment tree is: crocusShdslTtRpG703/line/testActivation (Status + Performance group)
Use this action to perform a test on the Crocus SHDSL G703. These tests are useful to trace possible problems. Possible tests are: no, al, dl, rdl, et, alEt, rdlEt. To execute a test, proceed as follows: Step 1 2 Action In the TMA window, select the object line and the group Performance or Status. In the action window of TMA, click the left mouse button on the field under the heading Argument Value.
crocusShdslTtRpG703/line/testDuration Use the testDuration attribute to set the time-out period of diagnostic tests. Tests are automatically terminated after this time-out period.
Default:00000d 00h 03m 00s Range: 00000d 00h 00m 01s 00000d 18h 12m 15s
The time-out ranges from 00000d 00h 00m 01s up to 00000d 18h 12m 15s. Entering 00000d 00h 00m 00s disables the time-out period (i.e. diagnostic tests are not terminated after a time-out period).
The detector of the remote Crocus SHDSL G703 receives this test pattern,
and looks for possible errors in the pattern. The quantity of errors could be an indication of the line quality. Clocking during an ET test When an ET test is activated, the Crocus SHDSL G703 switches to internal clocking mode.
How to use this test? Example: Phase 1 Description Start an AL test on the local Crocus SHDSL G703.
If this data is received again by the application, the connection between the DTE
and the Crocus SHDSL G703 is OK. If not, it is possible that there is a bad connection between the DTE and the Crocus SHDSL G703. In combination with the ET test, the AL test can also be used as a self-test of the Crocus SHDSL G703. Clocking during an AL test The following table shows what happens with the clocking on the Crocus SHDSL G703 when an AL test is activated: If the Crocus SHDSL G703 is in internal clocking mode external clocking mode slave receive clocking mode and an AL test is activated, then it remains in internal clocking mode. remains in external clocking mode. switches to internal clocking mode.
Make sure that on the remote Crocus SHDSL G703 the rdlDetect attribute is set to enabled (refer to 6.6 DTE Interface configuration attributes on page 148). Else it is not possible to initiate an RDL test on the remote. How to use this test? Example: Phase 1 Description Start an RDL-ET test on the local Crocus SHDSL G703.
A digital loop is established on the remote Crocus SHDSL G703 and a test pattern
is sent down the line. 2 3 Because the remote side is in a digital loop, the test pattern returns to the local Crocus SHDSL G703. The detector receives this test pattern, and can compare it with the original transmitted pattern.
The quantity of inconsistencies that might exist between the original and the
returned pattern could be an indication of the line quality.
Clocking during an RDL test The following table shows what happens with the clocking on the Crocus SHDSL G703 when an RDL test is activated: If the Crocus SHDSL G703 local is in internal clocking mode external clocking mode slave receive clocking mode remote any clocking mode and an RDL test is activated, then it . remains in internal clocking mode. remains in external clocking mode. switches to internal clocking mode. switches to slave receive clocking mode.
How to use this test? With this test, you can verify the same things as with the remote digital loop. The only difference is that the loop is not made on the remote Crocus SHDSL G703 (as with RDL), but on the local Crocus SHDSL G703. This can be necessary when, for example, the remote Crocus SHDSL G703 is unable to initiate a remote digital loop test. Clocking during a DL test When a DL test is activated, the Crocus SHDSL G703 switches to slave receive clocking mode.
12.3
Interface tests
For some DTE interfaces it is possible that the application (the DTE) initiates a test on the Crocus SHDSL G703 via the interface. The following table gives an overview of which tests are available on which interfaces. It also gives a short description of the available tests. Available tests Analog loop (AL) Description For G703 the sending of the Sa6 bit sequence 1111
initiates an analogue loop (loop 3) on the local Crocus SHDSL G703, in compliance with ITU-T recommendation V.54. Refer to 12.2.3 - Analogue loop on page 251. Remote Digital Loop (RDL) For G703 the sending of the Sa6 bit sequence 1010
initiates a digital loop (loop 2) on the remote Crocus SHDSL G703, in compliance with ITU-T recommendation V.54. Refer to 12.2.4 - Remote digital loop on page 252.
Note that also these tests are automatically terminated after the time-out period as set using the testDuration attribute. The interface tests can be disabled via the tests attribute.
13 Technical specifications
This chapter gives the technical specifications of the Crocus SHDSL G703. The following gives an overview of this chapter. 13.1 - Crocus SHDSL G703 types on page 258 13.2 - Line specifications on page 259 13.3 - RJ45 - RJ12 adapter specifications on page 261 13.4 - Maximum covered distance on a noise free line on page 262 13.5 - G703 interface specifications on page 263 13.6 - Management interface connectors on page 264 13.7 - Control connector on page 265 13.8 - Diagnostic tests on page 266 13.9 - Power requirements on page 267 13.10 - Thermal behaviour when providing remote power on page 268 13.11 - Environmental compliance on page 269 13.12 - Safety compliance on page 270 13.13 - Over-voltage and over-current protection compliance on page 270 13.14 - EMC compliance on page 270 13.15 - Mechanical dimensions on page 270
13.1
The following Crocus SHDSL G703 types exist: Crocus SHDSL TT G703 Crocus SHDSL 2P TT G703 Crocus SHDSL TT G703 RP Crocus SHDSL 2P TT G703 RP
13.2
Line specifications
Single pair or two pair line access Full duplex transmission Connector: RJ45 Impedance: 135 ohm Coding: TC PAM, compliant to ITU-T G.991.2 (G.SHDSL) Line speeds: 1 pair: N x 64 kbps (N = 1 36) 2 pair: N x 128 kbps (N = 1 36)
Handshaking: compliant to G.994.1 (automatic speed negotiation) or fixed speed Performance monitoring: compliant to G.826 (errored seconds, severely errored seconds, unavailability seconds) Round trip delay: 0.6 ms In case of a G.703 Nx64k interface, the round trip delay ranges from 0.6 ms (unframed) over 0.8 ms (framed, all timeslots on) up to 3.1 ms (framed, 3 timeslots on).
The following table shows the connector layout of the RJ45 line connector. Pin 1 2 3 4 5 6 7 8 Signal not used not used line 21 line 1 line 1 line 21 not used not used 1. For a Crocus SHDSL G703 2P (2 pair) version only Figure
13.3
If you have a line cable with an RJ12 connector, you first have to plug in the RJ45 to RJ12 adapter in the line connector of the Crocus SHDSL G703. The following table shows the connector layout of the RJ12 adapter connector. Pin 1 2 3 4 5 6 Signal not used line 21 line 1 line 1 line 21 not used 1. For a Crocus SHDSL G703 2P (2 pair) version only Figure
13.4
Line speed (kbps) 1P 64 128 256 512 1024 1536 2048 2304 2P 128 256 512 1024 2048 3072 4096 4608
Wire diameter (mm) 0.4 11,0 8,0 8,2 7,2 5,5 4,0 4,2 4,0 0.5 15,1 11,0 11,3 9,9 7,6 5,5 5,8 5,5 0.6 21,5 15,6 16,0 14,0 10,7 7,8 8,2 7,8 0.7 22,5 16,4 16,8 14,7 11,3 8,2 8,6 8,2 0.8 27,2 19,8 20,3 17,8 13,6 9,9 10,4 9,9 0.9 34,6 25,2 25,8 22,7 17,3 12,6 13,2 12,6 1,1 39,3 28,6 29,3 25,7 19,6 14,3 15 14,3
These values are valid starting from Crocus SHDSL G703 PCB revision 1.2 and firmware revision T2141/00800, T2145/00600 and T2136/01300 and higher. If the Signal to Noise ratio is 23dB, this matches a noise margin of 0dB. A noise margin of minimum 2dB is considered a minimum for an error ratio that matches at least 10E-7 (= S/N ratio of 25dB). In performance tests with noise, a noise margin of 6dB is usually taken (matching S/N ratio 29dB). From experience, it can be concluded that a 27dB S/N ratio gives no errors, at 25dB errors are rare.
13.5
Types: G703 and G703 Nx64k Compliance: ITU-T G.703 Connector: 2 BNCs, 1 RJ45 Impedance: 75 or 120 ohm (strap selectable) Coding: AMI or HDB3 (configurable) Performance monitoring: compliant to G.826 Jitter and wander: compliant to G.823 Speed (G703): fixed 2 Mbps user and line speed Speed (G703 Nx64k): fixed 2 Mbps user speed (for this interface, time slots have to be configured instead of a user speed). Line speeds up to 2 Mbps. Framing (G703 Nx64k): framed or unframed (configurable), framing compliant to G.704 Time slots (G703 Nx64k): 1 pair: N x 64 kbps (N = 1 32) 2 pair: N x 128 kbps (N = 1 16)
CRC4 insertion (G703 Nx64k): enabled, disabled or automatic detection (configurable), frame alignment and cyclic redundancy check compliant to ITU-T G.706 Defect detection: compliant to ITU-T G.775 The following table shows the connector layout of the RJ45 line connector. Pin 1 2 3 4 5 6 7 8 Signal receive A (+) receive B (-) signal ground transmit A (+) transmit B (-) signal ground not used not used DCE output output input input Figure
13.6
The possible management interface connectors are: Management interface connector asynchronous through the control connector Connector type 9 pins subD (on the Crocus SHDSL G703) Speed 9600 bps, 8+N
800 kbps
For all available management tools, refer to 1.6 - Maintenance and management tools connection possibilities on page 11.
13.7
Control connector
The control connector (sometimes also called control port) is a 9 pins subD connector that is labelled CTRL. The signals on this connector are V.24 / V.28 signals. The control connector layout The control connector has the following pin layout: Pin 1 2 3 4 5 6 7 8 9 Table Top The connection with the computer running TMA can be made with a straight 9 pins subD (Male/ Female) cable or a regular 25/9 pins subD adapter cable. The cable which is used to connect the TT with the 1035 Orchid LAN management concentrator can be ordered at the distributor (code 149220). Signal not used NMS RxD NMS TxD not used GND not used not used not used not used DCE output input Figure
13.8
Diagnostic tests
The following diagnostic test are available on the Crocus SHDSL G703: Analogue Loop (AL) Digital Loop (DL) Remote Digital Loop (RDL) Error Test (ET) (test pattern ITU 2E15-1)
13.9
Power requirements
The power requirements for the different Crocus SHDSL G703 types are as follows: Pmax Version G703 1P 12 Vdc G703 1P RP G703 2P RP Input power 230 Vac (85 265 Vac)1 3W 3W 4W -48 Vdc (-36 Vdc -72 Vdc)2 4W 5W
1. Using switched AC/DC adapter, 230Vac 12Vdc/1A, approx. 80% efficiency, sales code 202752. 2. Using the PST30 DC/DC adapter, 48Vdc 12Vdc/1A, approx. 73% efficiency, sales code 191706.
Thermal Maximum 4 cards that provide remote power are allowed. Natural cooling of the CN4-4 must be effective : the CN4-4 must be used in an upright position, not lying flat on its side. Ambient temperature must not be higher than 45 C.
Power CN4 DC or AC powering. AC powering with 300W PSU. AC power redundancy is allowed (if 2 AC PSU 's are present).
Thermal If forced cooling is available, up to 12 cards delivering remote power can be installed. If only natural cooling is available, maximum 7 cards delivering remote power can be installed, provided that a slot is left free between each card. Ambient temperature must not be higher than 40 C.
Power DC or AC powering AC powering with 2 300W PSU 's. No AC power redundancy allowed
Maximum altitude: 3000m International protection (IP) class of protection against solid and liquids: IP40
Annex
Product name
Crocus SHDSL RJ45 TT BU VAC
Description
Crocus SHDSL table top on 1 line pair, Basic Unit, no interface provided. Interface module available as separate sales item. wide-range Vac (Replacement for code 170814) Crocus SHDSL table top on 1 line pair, Basic Unit, no interface provided. Interface module available as separate sales item. 48 Vdc (Replacement of code: 171284) Crocus SHDSL table top on 1 line pair, Basic Unit, Keyboard and LCD for local programming, no interface provided. Interface module available as separate sales item. wide-range Vac (Replacement of code: 177936) Crocus SHDSL table top on 2 line pairs for longer distances or speeds up to 4Mbit/s, Basic Unit, no interface provided. Interface module available as separate sales item. wide-range Vac (Replacement for code 171975) Crocus SHDSL table top on 2 line pairs for longer distances or speeds up to 4Mbit/s, Basic Unit, no interface provided. Interface module available as separate sales item. 48 Vdc Crocus SHDSL table top on 2 line pairs for longer distances or speeds up to 4Mbit/s, Basic Unit, Keyboard and LCD for local programming, no interface provided. Interface module available as separate sales item. wide-range Vac (Only manufactured after order!) Crocus SHDSL table top on 2 line pairs for longer distances or speeds up to 4Mbit/s, Basic Unit, Keyboard and LCD for local programming, no interface provided. Interface module available as separate sales item. 48 Vdc. (Only manufactured after order !) Crocus SHDSL twin CV on 1 line pair, suitable for CN4. Can alternatively be used as single 2 line pair modem. Basic Unit, no interfaces provided. Interface modules (1 or 2 modules required) available as separate sales items. (Replacement of code: 180057 Crocus SHDSL CV on 2 line pairs for longer distances or speeds up to 4Mbit/s, suitable for CN4. Basic Unit, no interfaces provided. Interface modules available as separate sales items. (Replacement of code: 171977) Replaced by item 180056. Crocus SHDSL table top on 1 line pair, Basic Unit, Keyboard and LCD for local programming, no interface provided. Interface module available as separate sales item. 48 Vdc (Only manufactured after order !) Crocus SHDSL table top on 1 line pair with fixed G703 onboard interface. Includes European 230VAC external power adapter
180056
180054
180053
171976
177938
177939
193491
193492
177937
181080
Sales code
178713
Product name
CROCUS SHDSL 2P TT G703 RP
Description
Crocus SHDSL table top on 2 line pairs with fixed G703 onboard interface. Remotely powered. Can locally be powered directly with -48Vdc or via an external power plug, not included, on Vac. (Suitable power plug 175590 PWR-PLUG (EUR VERSION) 230VAC >9VDC) Crocus SHDSL table top on 1 line pair with fixed G703 onboard interface. Remotely powered. Can locally be powered directly with -48Vdc or via an external power plug, not included, on Vac. (Suitable power plug 175590 PWR-PLUG (EUR VERSION) 230VAC >9VDC) Crocus SHDSL table top on 1 line pair with fixed G703 onboard interface. Delivered without power adapter Crocus SHDSL table top on 2 line pairs with fixed G703 onboard interface. Includes European 230VAC external power adapter Crocus SHDSL table top on 2 line pairs with fixed G703 onboard interface. Delivered without power adapter Crocus SHDSL table top on 1 line pair with fixed RS530 onboard interface (V35, V36 & X21 through conversion cables, not included). Includes European 230VAC external power adapter Crocus SHDSL table top on 1 line pair with fixed RS530 onboard interface (V35, V36 & X21 through conversion cables, not included). Delivered without power adapter Crocus SHDSL table top on 1 line pair with fixed RS530 onboard interface (V35, V36 & X21 through conversion cables, not included). Remotely powered. Can locally be powered directly with -48Vdc or via an external power plug, not included, on Vac. Crocus SHDSL table top on 2 line pairs with fixed RS530 onboard interface (V35, V36 & X21 through conversion cables, not included). Remotely powered. Can locally be powered directly with -48Vdc or via an external power plug, not included, on Vac. Crocus SHDSL table top on 2 line pairs with fixed RS530 onboard interface (V35, V36 & X21 through conversion cables, not included). Includes European 230VAC external power adapter
178715
181081
196336
196337
181082
181083
178716
178714
196338
Sales code
196339
Product name
CROCUS SHDSL 2P TT RS530 NPWR
Description
Crocus SHDSL table top on 2 line pairs with fixed RS530 onboard interface (V35, V36 & X21 through conversion cables, not included). Delivered without power adapter Wallplug power module with input range: 18 to 72Vdc and output: 7,5 / 12Vdc for Desktop units delivered without power adapter. (xxx NPWR). Fully isolated input. Suitable for + & - DC input voltages. See doc OneAccess Product Quick Reference for compatibility with xxx NPWR item Wallplug Switched Power Module EUR type, 230Vac -> 12Vdc for Desktop units delivered without power adapter. (xxx NPWR). See doc OneAccess Product Quick Reference for compatibility with xxx NPWR item
191706
202752
The following table displays the product information of the Crocus SHDSL DTE interfaces. Sales code
143666 142199 161611 142200 175253
Product name
V35 INTF. CROCUS V36 INTF.CROCUS RS-530 INTF.CROCUS X21 INTF.CROCUS G703 INTF 2M CROCUS
Description
Plug-in modular interface V.35 transparent. Plug-in modular interface V.36 transparent. Plug-in modular interface RS-530 transparent. Plug-in modular interface X.21 transparent. G.703 interface module for the Crocus SHDSL. Can only work with line speed 2Mbit/s. BNC connectors. G.703 interface module for the Crocus SHDSL. Can work with line speeds below 2Mbit/s. BNC connectors. Plug-in modular interface Ethernet Bridge for direct UTP LAN connection. IEEE 802.3 compliant. Plug-in modular interface Ethernet Router for direct UTP LAN connection. IEEE 802.3 compliant. Limited to 2M. Plug-in modular interface Ethernet Router for direct UTP LAN connection. IEEE 802.3 compliant. Up to 10M.
175254
150466
BRIDGE INTF.CROCUS
161613
ROUTER 2M INTF.CROCUS
177455
The following table displays cables to be used in combination with the Crocus SHDSL RS530: Sales code
182968
Product name
CBL DCE RS530 (DB25M) - DTE V36M SH 2M
Description
Data-Cabling for TOP items: Serial CBL. See doc OneAccess Access Product Quick Reference. For application, details and pin layout see document: -Data cables- on the OneAccess Product dBase. -> Cable layout-19 Data-Cabling for TOP items: Serial CBL. See doc OneAccess Access Product Quick Reference. For application, details and pin layout see document: -Data cables- on the OneAccess Product dBase. -> Cable layout-19 Data-Cabling for TOP items: Serial CBL. See doc OneAccess Access Product Quick Reference. For application, details and pin layout see document: -Data cables- on the OneAccess Product dBase. -> Cable layout-20 Data-Cabling for TOP items: Serial CBL. See doc OneAccess Access Product Quick Reference. For application, details and pin layout see document: -Data cables- on the OneAccess Product dBase. -> Cable layout-20
182969
182970
182971
The following table displays the product information of the CN7: Sales code
198344 198346
Product name
Card nest CN7 Crocus SHDSL G703 NX64K TWIN-CN7 RP
Description
ETSI card nest with 17 slots, 7U high. SHDSL card with 2 single pair SHDSL modems with each a G703 interface and remote power feeding. Fits into CN7. Line speeds 192- 2048 kbps. SHDSL card with 2 dual pair SHDSL modems with each a G703 interface and remote power feeding. Fits into CN7. Line speeds 384 - 2048 kbps. SHDSL card with 2 single pair SHDSL modems with each a G703 interface. Fits into CN7. Line speeds 192- 2048 kbps. SHDSL card with 2 dual pair SHDSL modems with each a G703 interface. Fits into CN7. Line speeds 384 - 2048 kbps. Management concentrator card for CN7. Includes a CTRL interface for local management and an Ethernet interface for remote management. Desktop SHDSL 2 pair repeater. Remotely powered or locally powered (external power adapter not included). Suitable for indoor use. Desktop SHDSL single pair modem with a G703 interface with 120 Ohm RJ45 connector and 75 Ohm BNC connectors and local 230VAC powering. Line speeds 192 - 2048 kbps. Desktop SHDSL single pair modem with a G703 interface with 120 Ohm RJ45 connector and 75 Ohm BNC connectors and local 48Vdc powering. Line speeds 192 - 2048 kbps.
198347
202755
202756
198345
Orchid CN7
203420
Crocus SHDSL 2P G703 NX64K Repeater indoor RP/NPWR Crocus SHDSL G703 NX64K RJ45 TT 230VAC
203421
203422
Sales code
203423
Product name
Crocus SHDSL G703 2M RJ45 TT RP
Description
Desktop SHDSL single pair modem with a G703 interface with 120 Ohm RJ45 connector and remote powered. Line speed 2Mbps. Desktop SHDSL single pair modem with a G703 interface with 120 Ohm RJ45 connector and remote powered. Line speeds 192 - 2048kbit/s Desktop SHDSL single pair modem with a G703 interface with 120 Ohm RJ45 connector and 75 Ohm BNC connectors and remote powered. Connector for local powering (power adapter not included). Line speeds 192 - 2048 kbps. Desktop SHDSL 2 pair modem with a G703 interface with 120 Ohm RJ45 connector and 75 Ohm BNC connectors and local 230VAC powering. Line speeds 384 - 2048 kbps. Desktop SHDSL 2 pair modem with a G703 interface with 120 Ohm RJ45 connector and 75 Ohm BNC connectors and local 48Vdc powering. Line speeds 384 - 2048 kbps. Desktop SHDSL 2 pair modem with a G703 interface with 120 Ohm RJ45 connector and 75 Ohm BNC connectors and remote powered. Line speed 2Mbps Desktop SHDSL 2 pair modem with a G703 interface with 120 Ohm RJ45 connector and remote powered. Line speeds 192 - 2048kbit/s Desktop SHDSL 2 pair modem with a G703 interface with 120 Ohm RJ45 connector and 75 Ohm BNC connectors and remote powered. Connector for local powering (power adapter not included). Line speeds 384 - 2048 kbps. Wallplug power module with input range: 18 to 72Vdc and output: 7,5 / 12Vdc for Desktop units delivered without power adapter. (xxx NPWR). Fully isolated input. Suitable for + & - DC input voltages. See doc OneAccess Product Quick Reference for compatibility with xxx NPWR item Wallplug Switched Power Module EUR type, 230Vac -> 12Vdc for Desktop units delivered without power adapter. (xxx NPWR). See doc OneAccess Product Quick Reference for compatibility with xxx NPWR item
203455
203424
203425
203426
203427
203457
203428
191706
202752
Annex B: abbreviations
The following table gives a list of abbreviations and their description. Terms/abbreviations -48Vdc 1P 2P 4P 12Vdc ABR ADSL AIS AL AL-ET AMI ARP ATM BOOTP bps C-Side CBR CCP CHAP CLI CN7 CO CPE CRC CTRL CTS CV CV Twin CV-A CV-B dB Description -48 Volts - Direct Current 1 pair 2 pair 4 pair 12 Volts - Direct Current Available Bit Rate Asymmetric Digital Subscriber Line Alarm Indication Signal Analogue Loop Analogue Loop - Error Test Alternate Mark Inversion Address Resolution Protocol Asynchronous Transfer Mode Bootstrap Protocol bits per second Customer Side Constant Bit Rate Compression Control Protocol Challenge Handshake Authentication Protocol Command Line Interface Card Nest 7 Central Office Customer Premises Equipment Cyclic Redundancy Check Control Clear To Send Card Version Card Version Twin Card Version modem A Card Version modem B decibel
Annex B: abbreviations
Terms/abbreviations DCD DCE DHCP DIP DL DLCI DP DS DSLAM DTE EB EMC EOC ERR ES ESD ExtTxClk ET ETSI FAS FR FS FTP Gb GB Gbps G703 HDB3 HDLC ICMP if IGMP IMAP
Description Data Carrier Detect Data Communications Equipment Dynamic Host Configuration Protocol Dual In line Pin Digital Loop Data Link Connection Identifier Dual Power/ Dual Port Dip Switch bank Digital Subscriber Line Access Multiplexer Data Terminal Equipment Errored Block Electromagnetic Compatibility Embedded Operations Channel Error Errored Second Electrostatic Discharge External Transmit Clock Error Test European Telecommunications Standards Institute Frame Alignment Signal Frame Relay Fuse File Transfer Protocol Gigabit Gigabyte Gigabits Per Second G703 interface High Density Bipolar 3 High-level Data Link Control Internet Control Message Protocol Interface Internet Group Management Protocol Integrated Multi-service Access Platform
Terms/abbreviations IP IPCP IPSEC ITU-T Kb KB Kbps L2TP LAN LCP LED LFA LOS LTU MAC Mb MB Mbps MIB N-side NAT NCP NMS NTU PAP PAT PCB PCR PDH PPP PPPoA PPPoE PVC
Description Internet Protocol Internet Protocol Control Protocol Internet Protocol Security International Telecommunication Union - Telecommunication Standardization Sector Kilobit Kilobyte Kilobits Per Second Layer 2 Tunnelling Protocol Local Area Network Link Control Protocol Light Emitting Diode Loss of Frame Alignment Loss Of Signal Line Terminating Unit Media Access Control Megabit Megabyte Megabits Per Second Management Information Base Network Side Network Address Translation Network Control Protocols Network Management System Network Terminating Unit Password Authentication Protocol Port Address Translation Printed Circuit Board Peak Cell Rate Plesiochronous Digital Hierarchy Point-to-Point Protocol PPP over ATM PPP over Ethernet Permanent Virtual Circuits
Annex B: abbreviations
Terms/abbreviations PWR RAI RDL RDL-ET RFC RIP RP RS530 RTS Rx RxClk RxD SA SDH SELV SES SHDSL SNMP SPI SQ SSR ST TCP TC-PAM TFTP TMA TMA CLI TML TNV TS TST TT Tx
Description Power Remote Alarm Indication Remote Digital Loop Remote Digital Loop - Error Test Request For Comments Routing Information Protocol Remote Power RS530 interface Request To Send Receive Receive Clock Receive Data Security Association Synchronous Digital Hierarchy Safety Extra Low Voltage Severely Errored Second Symmetric High-Bitrate Digital Subscriber Line Simple Network Management Protocol Security Parameter Index Signal Quality Solid State Relay Strap Transmission Control Protocol Trellis Coded Pulse Amplitude Modulation Trivial File Transfer Protocol Total Management Application TMA Command Line Interface Total Memory Loader Telecom Network Voltage Timeslot Test Table Top Transmit
Terms/abbreviations TxClk TxD UBR UDP Vac VBR VBR-rt VBR-nrt VCI Vdc VLAN VPN VPI WAN
Description Transmit Clock Transmit Data Unspecified Bit Rate User Datagram Protocol Volts - Alternate Current Variable Bit Rate Variable Bit Rate real-time Variable Bit Rate non-real-time Virtual Channel Identifier Volts - Direct Current Virtual Local Area Network Virtual Private Networks Virtual Path Identifiers Wide Area Network
Annex B: abbreviations
Index 1
Index
A absolute addressing use 101 access to PDH networks 73 examples 74 synchronisation 73 access to SDH networks 76 asynchronous or synchronous 76 DXC 77 examples 78 typical 2 Mbit/s connections 76 accessing PDH and SDH networks clocking 65 action, what is 49 activating configuration 115 alarm attributes 207 configuration 211 general 215 introduction 210 overview 208 alarm signalling 217 alarms end 226 general 218 interface 229 line 221 line pair 223 repeater 226 analogue loop 251 application software what is 236, 239 attribute - action activate configuration 129 clearErrorCounter 170 Cold Boot 162 cold boot 130 load default configuration 116, 129 load saved configuration 130 loopbackActivation 179 maximumSpeedSearch 171 attribute - alarm alarmInfo 216, 219, 222, 224, 227, 230 alarmLevel 212 alarmMask 212 Cold Boot 220 remoteAlarmMask 214 totalAlarmLevel 216 attribute - configuration aisDetection 149
alarmContactHighMask top object 128 alarmContactLowMask top object 128 alarmLevel dteInterface object 150 line object 144 linePair object 146 top object 128 alarmMask dteInterface object 150 line object 144 linePair object 146 top object 128 asymmetricPsd 138 channel 54, 132 clocking 83, 150 cms2Address 152 coding 98, 149 consoleNoTrafficTimeOut 152 crc4Insertion 98 ctrlPortProtocol 102, 153 dualPairMode 143 eocChannel 56, 139 eocHandling 59, 139 forwardTmaToCtrlPort 103, 128 forwardTmaToLine 103, 128 framing 94 linkAlarmThresholds 140 management 105, 142 minLinePairSpeed 89, 135 mode 55, 134 name 142, 150 numExpectedRepeaters 139 rdlDetect 150 region 54, 132 remoteAlarmMask top object 128 retrain 135 saBits 106 security 127 sqThreshold 149 sqTime 149 startupMargin 138 sysContact 127 sysLocation 127 sysName 127 testDuration 138, 249 timeSlots 95, 149 timingMode 64, 133 txEocMessages 139 attribute - performance <h2/h24/d7>G703Performance 201 <h2/h24/d7>G826Performance 202 <h2/h24/d7>Line 194 <h2/h24/d7>LineParameters 197 <h2/h24/d7>Performance 198 clearErrorCounter 195
Index
currUsedProcPower 205 errorCount 194 freeBlockCount 205 freeDataBuffers 205 freeMemory 205 g703Performance 201 g826Performance 202 largestFreeBlockSize 205 line 194 lineParameters 197 performance 198 retrain 195 taskInfo 206 testActivation 195, 202, 249 totalDataBuffers 205 totalMemory 205 usedProcPower 206 attribute - status actualBitRate 174 ais 181 asymmetricPsd 169 bootVersion 161 configurationSaving 161 deviceId 161 eocAlarmThresholds 170, 178 eocSoftVersion 177 eocState 177 errorCount 169 flash1Version 162 framerType 166 ifClocking 183 ifDescr 164, 182 ifOperStatus 164, 173, 183 ifSpeed 164, 173, 183 ifType 164, 183 lfa 182 lineAttenuation 174, 179 linePairsSwapped 169 loaderVersion 161 los 181 maxLinePairSpeed 165 maxSpeedResult 168 maxSpeedSearch 168 messages 160 minLinePairSpeed 164 numDiscoveredRepeaters 169 powerSource 162 region 169 shdslVersion 177 signalNoise 174, 179 status 173 stepupThreshold 174 sysDescr 160 sysObjectID 160 sysServices 160 sysUpTime 160 taskInfo 185 testOriginator 167
testStatus 167 testType 166 timeSinceLastRetrain 173 timeSlots 181 transmitPower 174 vendorId 176 vendorModel 176 vendorSerial 176 vendorSoftVersion 176 attribute string, reading viii attribute, what is 49 B basic configuration passwords 111 basic line parameters configuring 54 boot software what is 236, 237 C changing DIP switch settings of the TT 39 changing strap settings of the TT 39 clocking accessing PDH and SDH networks 65 clocking mode configuring 82 configuring on the Crocus SHDSL G703 83 compatibility with other SHDSL devices 119 configuration activating 115 alarm attributes 211 configuration actions executing 113 what is 114 configuration attributes 123 general 126 interface 148 line 131 line pair 145 management 151 overview 124 configuration types 114 configuring basic line parameters 54 clocking mode 82 clocking mode on the Crocus SHDSL G703 83 EOC handling 57 framing 93 interface specific attributes 98
Index 3
management attributes 99 management data on a G703 interface 106 management data on the line 105 minimum line speed 87 time slots 93 timing mode 64 connecting Crocus SHDSL TT 20 line to Table Top 24 power supply 22 containment tree 50 terminology 48 what is 49 control connector forwarding management data 103 selecting the purpose 102 specifications 265 conventions in this manual graphical vii typographical vi copyright notice ii Crocus SHDSL attribute overview 51 connecting the TT 20 DIP switches 33 features 4 introduction 3 maintaining 41 product overview 5 straps 33 types 258 crocusShdslTtRpG703 143 D data carrier detect LED (DCD/109) 32 diagnostic tests 245 introduction 246 specifications 266 digital loop 254 DIP switch table, reading viii DIP switches 33 changing settings of the TT 39 of the TT 34, 36 displaying the subsystem picture 232 document conventions graphical vii typographical vi copyright notice ii documentation set v environmental information iv firmware version described in this ix intended audience ix
organisation v properties ii statements iii your feedback ix documentation set v downloading in loader mode 243 with TMA 241 with TML 242 E EMC compliance specifications 270 end alarms 226 performance attributes 199 status attributes 175 environmental compliance specifications 269 environmental information iv EOC configuring handling 57 discovering devices on the SHDSL line 60 EOC handling attribute 59 retrieved information 60 what is 58 error test 250 example management over the line and the control port 107 management over the line and the E1 interface 109 executing configuration actions 113 F feedback ix firmware version ix forwarding management data to the line and control connector 103 framed mode selecting 94 framing configuring 93 front panel LEDs indicators 30 introduction 31 G G703 interface configuring management data 106 interface performance attributes 200
Index
specifications 263 general alarm attributes 215 alarms 218 configuration attributes 126 status attributes 159 group, what is 49 I Identification ix important download issues 240 important remark on the minimum line pair speed 88 installation and connection precautions 19 Installing and connecting 13 interface alarms 229 configuration attributes 148 status attributes 180 tests 255 interface performance attributes G703 interface 200 interface specific attributes configuring 98 introducing maintenance and management tools 9 introduction alarm attributes 210 Crocus SHDSL 3 diagnostic tests 246 front panel LEDs 31 management attributes 47 performance terms 192 performance timing 191 TMA 43 L LED data carrier detect (DCD/109) 32 power (PWR) 32 serial (SERIAL) 32 LED indicators front panel 30 line alarms 221 configuration attributes 131 configuring management data 105 forwarding management data 103 performance attributes 193 specifications 259 status attributes 163 tests 247
line pair alarms 223 configuration attributes 145 performance attributes 196 status attributes 172 line test action 248 load default configuration 115 action in TMA 116 using a DIP switch 117 loader software what is 236, 238 low speed limitations on the G703 Nx64k interfaces 97 M maintaining the Crocus SHDSL 41 maintenance and management connection possibilities 11 maintenance and management tools introducing 9 management configuration attributes 151 rules of thumb and remarks 100 management attributes configuring 99 management interface connectors specifications 264 management tools entering passwords 112 maximum covered distance on a noise free line specifications 262 mechanical dimensions specifications 270 minimum line pair speed attribute 89 important remark 88 purpose 92 minimum line speed configuring 87 motherboard Table Top 35 N network clocking principles 67 central clock 67 hierarchical structure 67 station clock 67 O object, what is 49 operating system
Index 5
performance attributes 204 status 184 organisation of this manual v over-current protection compliance specifications 270 overview alarm attributes 208 configuration attributes 124 performance attributes 188 remote power operation 27 status attributes 156 over-voltage protection compliance specifications 270 P passwords adding to the security table 112 basic configuration 111 entering in the different management tools 112 PDH networks 68 asynchronous tributaries 68 disadvantages 69 gateways 69 timing 69 performance attributes 187 end 199 line 193 line pair 196 operating system 204 overview 188 repeater 199 performance terms introduction 192 performance timing introduction 191 possible clocking modes versus DTE interface 86 Power back-off 8 power LED (PWR) 32 power requirements specifications 267 power supply connecting 22 product information 273, 279 DTE interfaces 276 product overview Crocus SHDSL 5 purpose of the minimum line pair speed 92 R reading
a DIP switch table viii an attribute string viii relative addressing use 101 remarks on dualPairMode attribute 143 opening the housing 34 RP sink 28 selecting a site 16 remote digital loop 252 remote power what is 26 remote power operation 25 overview 27 remote power sink operation how? 28 repeater alarms 226 performance attributes 199 status attributes 175 use 29 RJ45 - RJ12 adapter specifications 261 rules of thumb and remarks concerning management 100 S safety instructions 14 requirements ii safety compliance specifications 270 SDH networks 70 network elements 71 redundant ring structures 72 SDH hierarchy 70 synchronisation 72 security table adding passwords 112 selecting a site 16 purpose of the control connector 102 time slots 95 unframed or framed mode 94 serial LED (SERIAL) 32 signal and protective ground interconnection 23 software download 235 specifications control connector 265 Crocus SHDSL types 258 diagnostic tests 266 EMC compliance 270 environmental compliance 269
Index
G703 interface 263 line 259 management interface connectors 264 maximum covered distance on a noise free line 262 mechanical dimensions 270 over-current protection compliance 270 over-voltage protection compliance 270 power requirements 267 RJ45 - RJ12 adapter 261 safety compliance 270 starting a TMA session through a management concentrator 46 through the control connector 44 starting TMA on the Crocus SHDSL 42 statements iii status attributes 155 end 175 general 159 interfaces 180 line 163 line pair 172 overview 156 repeater 175 step-by-step configuration 53 straps 33 changing settings of the TT 39 of the TT 34, 37 structured value, what is 49 subsystem picture display 232 elements 233 synchronous interfaces 80 data transfer 80 exchange of clock signals 81 T Table Top connections 21 motherboard 35 technical specifications 257 time slots configuring 93 selecting 95 transposition 96 timing mode configuring 64 TMA subsystem picture 231 transposition time slots 96 troubleshooting 118
U unframed mode selecting 94 unpacking 15 using a repeater 29 relative or absolute addressing 101 V value, what is 49 W wall mounting 17 warning EMC 19 ESD 19 important safety instructions 14 safety warning 14 what is application software 236, 239 boot software 236, 237 containment tree 49 EOC 58 loader software 236, 238 remote power 26