Top Banner
Telindus Technical Publications Geldenaaksebaan 335 - B-3001 Leuven - Belgium Tel. +32 16 382011 Crocus SHDSL Crocus SHDSL User and reference manual Version: 2.4 - 197254
380
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: m Crocus SHDSL

Telindus Technical Publications � Geldenaaksebaan 335 - B-3001 Leuven - Belgium � Tel. +32 16 382011

Crocus SHDSL

Crocus SHDSL

User and reference manual

Version: 2.4 - 197254

SAFETY WARNING
Carefully read the safety instructions at the beginning of Chapter 2 - Installing and connecting the Crocus SHDSL.
How to navigate in this document?
(Scroll down to see entire note) This document contains bookmarks, links and cross-references to allow easy navigation. The following paragraphs of this note describe what you can use to navigate and how to use it. 1. Bookmarks ------------------- Bookmarks are located in the bookmark window of the Acrobat Reader. Click on a bookmark and you jump to the corresponding part in the document. The bookmark window also gives you an overview of the document structure. It is a handy tool because it is always visible. 2. Table of contents (complete manual) ----------------------------------------------------- In the preface you find a table of contents covering the complete document. Click on a title in the table of contents and you jump to the corresponding part in the document. 3. Table of contents (per section) --------------------------------------------- Every chapter or section containing numbered sub-titles starts with a table of contents covering that chapter or section. Click on a title in this table and you jump to the corresponding part in the document. 4. Cross-references ---------------------------- Throughout the text, there are cross-references to other chapters, sections or paragraphs. They usually start with "Refer to" and are blue in colour. Click on such a cross-reference and you jump to the corresponding part in the document. 5. Figure links -------------------- Some figures also may contain cross-references (also blue in colour). Click on such a link and you jump to that part in the document which explains that particular part of the figure. 6. Internet links ---------------------- This document also contains Internet links. Click on such a link and you are redirected to the corresponding web page. 7. Index ----------- At the end of the manual you find an index containing several keywords. Click on the page number after such a keyword and you jump to the corresponding part in the document. Note ------- If you click on a bookmark, link or cross-reference, you jump to the corresponding part in the document. You can always go back to that part in the document where you clicked on the link. Do this by pressing simultaneously the control and left arrow key: CTRL + <- For more navigation tools, refer to the Document menu of your Acrobat Reader.
Page 2: m Crocus SHDSL

Crocus SHDSL Copyright, safety and statements

User manual

ii

Document properties

Copyright notice

The information and descriptions contained in this publication are the property of Telindus. Such infor-mation and descriptions must not be copied or reproduced by any means, or disseminated or distributed without the express prior written permission of Telindus.

This publication could include technical inaccuracies or typographical errors, for which Telindus 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. Telindus 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 at the beginning of 2.1 - Safety instructions on page 14

The connectors of the Crocus SHDSL should only be connected to the following circuit types:

� SELV (Safety Extra Low Voltage): local connection (e.g. PC to Crocus SHDSL) 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.

Subject Crocus SHDSL

Manual type User and reference manual

Version 2.4

Code 197254

Modification date 9 May 2005 ©Telindus

Connector name Connector label Connector type Circuit type

line line RJ45 TNV-1

management CTRL subD SELV

Page 3: m Crocus SHDSL

Crocus SHDSL Copyright, safety and statements

User manual

iii

Statements

www.telindusproducts.com → Telindus Access Solutions → Products → Choose a product → Down-loads → Certificates

Hereby, Telindus declares that this Crocus SHDSL complies with the essential requirements and other relevant provisions of Directive 1999/5/EC.

Hierbij verklaart Telindus dat deze Crocus SHDSL overeenstemt met de essentiële vereisten en andere relevante bepalingen van Richtlijn 1999/5/EC.

Par la présente, Telindus déclare que ce Crocus SHDSL est en conformité avec les exigences essen-tielles et autres articles applicables de la Directive 1999/5/EC.

Hiermit, Telindus erklärt daß dieser Crocus SHDSL in Fügsamkeit ist mit den wesentlichen Anforderun-gen und anderen relevanten Bereitstellungen von Direktive 1999/5/EC.

Mediante la presente, Telindus declara que el Crocus SHDSL cumple con los requisitos esenciales y las demás prescripciones relevantes de la Directiva 1999/5/CE.

A Telindus declara que o Crocus SHDSL cumpre os principais requisitos e outras disposições da Direc-tiva 1999/5/EC.

Col presente, Telindus dichiara che questo Crocus SHDSL è in acquiescenza coi requisiti essenziali e stipulazioni attinenti ed altre di Direttivo 1999/5/EC.

Με το παρόν η Telindus δηλώνει ότι το Crocus SHDSL είναι συµµορφούµενο µε τις βασικές απαιτήσεις και µε τις υπόλοιπες σχετικές διατάξες της οδηγίας 1999/5/EC.

Page 4: m Crocus SHDSL

Crocus SHDSL Preface

User manual

iv

Organisation of this manual

This manual contains the following main parts:

Refer to the Table of contents on page x for a detailed overview of this manual.

Typographical conventions

The following typographical conventions are used in this manual:

Part This part �

User manual shows you how to install and connect the Crocus SHDSL. It also gives a basic configuration of the Crocus SHDSL.

Reference manual gives more detailed information on the Crocus SHDSL. It contains a complete description for lookup purposes.

Annex gives additional information, such as product sales codes.

The format � indicates �

Normal normal text.

Italic � new or emphasised words� application windows, buttons and fields. E.g. In the File name field enter �

Computer 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 com-puter 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 �

Page 5: m Crocus SHDSL

Crocus SHDSL Preface

User manual

v

Graphical conventions

The following icons are used in this manual:

<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.telindus.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).

Icon Name This icon indicates �

Remark remarks or useful tips.

Caution text to be read carefully in order to avoid damage to the device.

Warning text to be read carefully in order to avoid injury.

DIP switch a DIP switch or strap table.

Basic attribute a basic attribute in the containment tree of the Crocus SHDSL.

Advanced attribute an advanced attribute in the containment tree of the Crocus SHDSL.

Structured attribute a structured attribute within another attribute in the containment tree of the Crocus SHDSL.

Action an action in the containment tree of the Crocus SHDSL.

The format � indicates �

Page 6: m Crocus SHDSL

Crocus SHDSL Preface

User manual

vi

Reading a DIP switch table

At several places in this manual DIP switch tables are shown. To enable you to read such a table in a correct manner it is explained below.

A DIP switch table has the following layout:

The following table explains the DIP switch configuration table layout:

Number This position displays �

1 the DIP switch icon.

2 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

Example:

3 (TT & CV-A)4 (CV-B)

The abbreviations mean the following:

� DS1 no. 3 (TT & CV-A): DIP switch bank number 1, switch position number 3, for Table Top and Card Version modem A

� DS1 no. 4 (CV-B): DIP switch bank number 1, switch position number 4, for Card Ver-sion modem B.

4 the possible settings of the DIP switch: on and off. The default setting is printed in bold.

5 the function associated with the corresponding DIP switch setting.

Page 7: m Crocus SHDSL

Crocus SHDSL Preface

User manual

vii

Reading an attribute string

At several places in this manual attribute strings are shown. To enable you to read such a string in a correct manner it is explained below.

An attribute string has the following layout:

The following table explains the attribute string layout:

Number This position displays �

1 the attribute icon. It indicates that the string which follows is an attribute string. Refer to Graphical conventions on page v for more information.

2 the attribute name and its position in the containment tree.

3 the default value of a configuration attribute.

Page 8: m Crocus SHDSL

Crocus SHDSL Preface

User manual

viii

Hardware version

This manual describes the hardware of the Crocus SHDSL PCB version 2.0 and higher.

Application software version

This manual describes the features, containment tree and attributes of the Crocus SHDSL application software version T2136/01500, T2145/00800 and T2141/01500.

For more information on these different application software types, refer to 1.4 - Application software overview on page 7.

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 Telindus. Accord-ingly, 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 com-ment concerning this delivery, please submit the Quality Comment Form on our web page atwww.telindusproducts.com/quality.

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.

Page 9: m Crocus SHDSL

Crocus SHDSL Preface

User manual

ix

Page 10: m Crocus SHDSL

Crocus SHDSL Table of contents

User and reference manual

x

Table of contents

User manual............................................................................................ 1

1 Introducing the Crocus SHDSL ..........................................................................31.1 Crocus SHDSL features ............................................................................................. 41.2 Crocus SHDSL product overview............................................................................... 51.3 DTE interface overview .............................................................................................. 61.4 Application software overview .................................................................................... 71.5 Power back-off ........................................................................................................... 81.6 CN4 card nest ............................................................................................................ 81.7 Management overview ............................................................................................... 9

2 Installing and connecting the Crocus SHDSL.................................................132.1 Safety instructions .................................................................................................... 142.2 Unpacking ................................................................................................................ 152.3 Selecting a site ......................................................................................................... 162.4 Wall mounting........................................................................................................... 172.5 Installation and connection precautions ................................................................... 192.6 Connecting the Crocus SHDSL TT .......................................................................... 202.7 Connecting the Crocus SHDSL Card Version.......................................................... 262.8 Remote power operation .......................................................................................... 332.9 Using a repeater....................................................................................................... 392.10 Front panel LED indicators....................................................................................... 40

3 DIP switches and straps of the Crocus SHDSL ..............................................453.1 DIP switches and straps........................................................................................... 463.2 DIP switches and straps of the Crocus SHDSL Card Version ................................. 51

4 Managing the Crocus SHDSL ...........................................................................574.1 Starting TMA on the Crocus SHDSL ........................................................................ 584.2 Starting keyboard management on the Crocus SHDSL........................................... 644.3 Introducing the management attributes of the Crocus SHDSL ................................ 65

5 The front panel display .....................................................................................715.1 The "windows" of the front panel display.................................................................. 725.2 The main window ..................................................................................................... 735.3 The line window........................................................................................................ 755.4 The DTE window ...................................................................................................... 765.5 The test window ....................................................................................................... 775.6 The model browsing window .................................................................................... 785.7 The connect remote window .................................................................................... 785.8 The version window.................................................................................................. 78

Page 11: m Crocus SHDSL

Crocus SHDSL Table of contents

User and reference manual

xi

6 Step-by-step configuration ...............................................................................796.1 Configuring the basic line parameters...................................................................... 806.2 Configuring EOC handling........................................................................................ 826.3 Configuring the timing mode .................................................................................... 886.4 Configuring the clocking mode ................................................................................. 896.5 Configuring the user speed .................................................................................... 1086.6 Configuring the minimum line speed ...................................................................... 1136.7 Configuring framing and time slots......................................................................... 1186.8 Configuring the user speed and time slots on the Dual Port G703-Serial interface1226.9 Low speed limitations on the G703 Nx64k interfaces ............................................ 1256.10 Configuring the interface specific attributes ........................................................... 1276.11 Configuring the management attributes ................................................................. 1336.12 Configuring remote power operation ...................................................................... 1466.13 Configuring passwords........................................................................................... 1476.14 Executing configuration actions.............................................................................. 1496.15 Troubleshooting the Crocus SHDSL ...................................................................... 1536.16 Crocus SHDSL compatibility with other SHDSL devices ....................................... 154

Reference manual .............................................................................. 155

7 Configuration attributes..................................................................................1577.1 Configuration attribute overview............................................................................. 1587.2 General configuration attributes ............................................................................. 1637.3 Line configuration attributes ................................................................................... 1687.4 Line pair configuration attributes ............................................................................ 1797.5 Remote power configuration attributes................................................................... 1817.6 DTE Interface configuration attributes.................................................................... 1837.7 Management configuration attributes ..................................................................... 205

8 Status attributes ..............................................................................................2098.1 Status attribute overview ........................................................................................ 2108.2 General status attributes ........................................................................................ 2158.3 Line status attributes .............................................................................................. 2198.4 Line pair status attributes ....................................................................................... 2278.5 Remote power status attributes.............................................................................. 2308.6 Repeater and end status attributes ........................................................................ 2328.7 DTE Interface status attributes............................................................................... 2378.8 Management status attributes ................................................................................ 2558.9 Operating system status......................................................................................... 257

Page 12: m Crocus SHDSL

Crocus SHDSL Table of contents

User and reference manual

xii

9 Performance attributes ...................................................................................2599.1 Performance attribute overview.............................................................................. 2609.2 Introducing the performance attributes................................................................... 2639.3 Line performance attributes.................................................................................... 2669.4 Line pair performance attributes............................................................................. 2689.5 Repeater and end performance attributes.............................................................. 2719.6 G703 interface performance attributes................................................................... 2729.7 Dual Port G703-Serial interface performance attributes ........................................ 2769.8 Operating system performance attributes .............................................................. 277

10 Alarm attributes ...............................................................................................28110.1 Alarm attribute overview......................................................................................... 28210.2 Introducing the alarm attributes.............................................................................. 28510.3 General alarms....................................................................................................... 29210.4 Line alarms............................................................................................................. 29510.5 Line pair alarms...................................................................................................... 29710.6 Remote power alarms ............................................................................................ 30010.7 Repeater and end alarms....................................................................................... 30210.8 Interface alarms...................................................................................................... 306

11 TMA subsystem picture of the Crocus SHDSL.............................................30911.1 Displaying the subsystem picture........................................................................... 31011.2 Subsystem picture elements .................................................................................. 311

12 Software download..........................................................................................31312.1 What is boot, loader and application software?...................................................... 31412.2 Important download issues..................................................................................... 31812.3 Downloading with TMA........................................................................................... 31912.4 Downloading with TML ........................................................................................... 32012.5 Downloading in loader mode.................................................................................. 32112.6 Downloading in boot mode..................................................................................... 32212.7 Downloading via a management concentrator ....................................................... 323

13 Diagnostic tests ...............................................................................................32513.1 Introducing the diagnostic tests.............................................................................. 32613.2 Line tests ................................................................................................................ 32713.3 Interface tests......................................................................................................... 33513.4 Repeater tests ........................................................................................................ 336

Page 13: m Crocus SHDSL

Crocus SHDSL Table of contents

User and reference manual

xiii

14 Technical specifications .................................................................................33914.1 Crocus SHDSL types ............................................................................................. 34014.2 Line specifications .................................................................................................. 34014.3 RJ45 - RJ12 adapter specifications........................................................................ 34214.4 Maximum covered distance on a noise free line .................................................... 34314.5 G703 interface specifications ................................................................................. 34414.6 RS530 interface specifications ............................................................................... 34514.7 Management interface connectors ......................................................................... 34714.8 Control connector ................................................................................................... 34814.9 Diagnostic tests ...................................................................................................... 34914.10Power requirements ............................................................................................... 34914.11Environmental compliance ..................................................................................... 35014.12Safety compliance .................................................................................................. 35114.13Over-voltage and over-current protection compliance ........................................... 35114.14EMC compliance .................................................................................................... 35114.15Mechanical dimensions .......................................................................................... 351

Annex .................................................................................................. 353

Annex A:product information ...............................................................................355

Index........................................................................................................ 1

Page 14: m Crocus SHDSL

Crocus SHDSL Table of contents

User and reference manual

xiv

Page 15: m Crocus SHDSL

Crocus SHDSL

User manual

1

User manual

Page 16: m Crocus SHDSL

Crocus SHDSL

User manual

2

Page 17: m Crocus SHDSL

Crocus SHDSL Chapter 1

User manual Introducing the Crocus SHDSL

3

1 Introducing the Crocus SHDSL

This chapter introduces the Crocus SHDSL. The following gives an overview of this chapter:

� 1.1 - Crocus SHDSL features on page 4� 1.2 - Crocus SHDSL product overview on page 5� 1.3 - DTE interface overview on page 6� 1.4 - Application software overview on page 7� 1.5 - Power back-off on page 8� 1.6 - CN4 card nest on page 8� 1.7 - Management overview on page 9

Page 18: m Crocus SHDSL

Crocus SHDSL Chapter 1

User manual Introducing the Crocus SHDSL

4

1.1 Crocus SHDSL features

The Crocus SHDSL (Single-Pair High Bit Rate Digital Subscriber Line) is a new generation manageable baseband modem offering full duplex transmission up to 2,3 Mbps over a single two-wire unconditioned unshielded twisted-pair cable.

A special 2-pair version offers the possibility to extend the speed range to 4,6 Mbps. The line speed of the modem can be automatically adapted to optimise the throughput as a function of the characteristics of the local loop. The equipment is based on a modulation technology called TC-PAM (Trellis Coded Pulse Amplitude Modulation), which guarantees higher speeds and longer loop performance.

The TC-PAM modulation also guarantees spectral compatibility with legacy and ADSL transmission sys-tems in the same cable bundle, offering an attractive solution for high-speed backbone access, for LAN to LAN connections, as well as for imaging and other bandwidth-demanding applications.

A complete range of plug-in interface boards makes the Crocus SHDSL ideal for interfacing with almost every application. Not only traditional serial interfaces like V.35, V.36, RS-530 and X.21 (configurable for Nx64 kbps operation), but also G703 (transparent or with G.704 framing) and direct Ethernet 10/100Base-T connections with integrated router functionality are available. All these interface boards can be exchanged in only a few seconds, so flexibility is maximised. For large concentration sites, rack-mount versions are mounted in a standard 19" card-nest and can offer densities of up to 30 modems per nest.

Both 230/115 Vac and direct 48 Vdc powering can be used. With a free user-friendly graphical Windows application, the operator can configure the local or remotely installed equipment. It is a valuable tool for the field engineer as it supports performance monitoring, retrieval of statistics and troubleshooting.

Alternatively one can obtain a comparable functionality through the use of a VT100 terminal. The Crocus SHDSL also offers an automatic installation mode, which allows standard configurations to be set up in only a few seconds. For larger networks, the Crocus SHDSL can be managed with a management appli-cation running on the SNMP based HP OpenView® management platform. On this platform one can combine the management of the Crocus SHDSL with the management of all Telindus and many third party equipment. The integrated management allows one to configure the modem remotely, to query the actual status of the modems, to permanently monitor the performance (real-time and statistical informa-tion), to conduct fault analysis, and to report alarms to the operator.

Summarised:

� data transmission rates up to 2304 kbps (Crocus SHDSL 1 pair version) or even 4608 kbps (Crocus SHDSL 2 pair version)

� a flexible data interface adaptation through modular interfaces� extended management possibilities for configuration and inspection purposes� easy self-test and link-test functions� flash memory for easy software updating� different powering possibilities (115/230 Vac or -48 Vdc)� central site high density card nest solution.

Page 19: m Crocus SHDSL

Crocus SHDSL Chapter 1

User manual Introducing the Crocus SHDSL

5

1.2 Crocus SHDSL product overview

The following Crocus SHDSL product versions exist:

The following table gives a description of the used abbreviations:

Crocus SHDSL product Manual

� Crocus SHDSL 1P TT Vac� Crocus SHDSL 1P TT -48Vdc� Crocus SHDSL 1P CV Twin� Crocus SHDSL 2P TT Vac� Crocus SHDSL 2P TT -48Vdc� Crocus SHDSL 2P CV Twin

These versions are described in the Crocus SHDSL manual.

Abbreviation In full Explanation

TT Table Top This version is a stand-alone version of the Crocus SHDSL. It is available with or without an LCD display and keyboard.

CV Card Version 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.

CV Twin Card Version Twin This version is a card that has to be inserted into the CN4 card nest. It incorporates two Crocus SHDSL 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.

1P 1 pair This version has 1 line pair.

2P 2 pair This version has 2 line pairs.

Vac Volts - Alternate Current This version has to be powered with 115 or 230 Vac.

-48Vdc -48 Volts - Direct Current This version has to be powered with -48 Vdc.

9Vdc 9 Volts - Direct Current This version has to be powered with 9 Vdc (using a Vac/9Vdc power adapter).

RP Remote Power This version can be powered with remote power (i.e. power coming from the central side, over the line).

DP Dual Power This version can be powered either with 9 Vdc (using a Vac/9Vdc power adapter) or with -48 Vdc.

Page 20: m Crocus SHDSL

Crocus SHDSL Chapter 1

User manual Introducing the Crocus SHDSL

6

1.3 DTE interface overview

A complete range of plug-in DTE interface modules makes the Crocus SHDSL ideal for interfacing with almost any application. All these DTE interface modules can be exchanged in only a few seconds.

The Crocus SHDSL only supports transparent DTE interfaces (except for the G703 Nx64k interface). The following table lists the DTE interfaces modules which can be used in the Crocus SHDSL:

DTE interface Supported user and line speeds

RS530, V36, X21 All user and corresponding line speeds are supported:

� 1 pair: 64 kbps up to 2304 kbps� 2 pair: 64 kbps up to 4608 kbps

Refer to 6.5.2 - Using odd speeds on the Crocus SHDSL 2P when using serial interfaces on page 110.

V35 V.35 is only specified up to 2 Mbps. V35 interfaces with PCB version �

� 0.2 or lower only support speeds up to 2304 kbps.� 0.3 or higher support all user and corresponding line speeds, provided

short cables are used:- 1 pair: 64 kbps up to 2304 kbps- 2 pair: 64 kbps up to 4608 kbps

G703 Fixed 2 Mbps user and line speed.

G703 Nx64k Fixed 2 Mbps user speed (time slots have to be configured instead of a user speed). All line speeds between 64 kbps and 2 Mbps are supported.

Dual Port G703-Serial All user and line speeds starting from 64 kbps are supported:

� 1 pair: 64 kbps up to 2304 kbps� 2 pair: 64 kbps up to 4608 kbps

10baseT Bridge All user and corresponding line speeds are supported:

� 1 pair: 64 kbps up to 2304 kbps� 2 pair: 64 kbps up to 4608 kbps

10baseT Router 2M All user and corresponding line speeds up to 2 Mbps (hardware limitation).

10baseT Router 10M All user and corresponding line speeds are supported:

� 1 pair: 64 kbps up to 2304 kbps� 2 pair: 64 kbps up to 4608 kbps

Page 21: m Crocus SHDSL

Crocus SHDSL Chapter 1

User manual Introducing the Crocus SHDSL

7

1.4 Application software overview

There are three different application software codes for the Crocus SHDSL, each with their own T-code and possibly different revisions. These software codes are not straightforward interchangeable.

The following table shows you the relationship between boot, loader and application software and the hardware (PCB) and related features:

For more information on downloading software, refer to 12 - Software download on page 313.

Software PCB 0.x & long serv-ice down time1

1. With this boot, loader, application software and hardware combination the data traffic is inter-rupted when downloading new application software into the Crocus SHDSL.

PCB 0.x & short serv-ice down time2

2. With this boot, loader, application software and hardware combination the data traffic is only interrupted for a short time (less than 3 minutes) when downloading new application software into the Crocus SHDSL. As you can see in the table, switching from PCB 0.x with long service down time to PCB 0.x with short service down time requires that the loader code is replaced first (local download), followed by the application code.

PCB 1.x3

3. All revisions of this boot, loader, application software and hardware combination support non-interrupted data traffic when downloading new application software.

boot T2135xxx T2135xxx T2140xxx

loader T2137003 T2137004 T2142xxx

application T2136xxx T2145xxx T2141xxx

Page 22: m Crocus SHDSL

Crocus SHDSL Chapter 1

User manual Introducing the Crocus SHDSL

8

1.5 Power back-off

The Crocus SHDSL features power back-off. Power back-off is a part of the ITU-T G.991.2 SHDSL rec-ommendation. 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 hand-shake, 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.6 CN4 card nest

The Telindus CN4 card nest is based on a standard card nest which fits in a standard 19" rack. The CN4 card nest can hold up to 15 cards. It can be powered with:

� -48 Vdc (no power modules required)� 115/230 Vac (one or two power module(s) required)� both -48 Vdc and 115/230 Vac (for back-up purposes).

The CN4 card nest supports the complete Crocus range. For more information on the CN4 card nest, refer to the CN4 manual.

Page 23: m Crocus SHDSL

Crocus SHDSL Chapter 1

User manual Introducing the Crocus SHDSL

9

1.7 Management overview

The Crocus SHDSL is manageable in many different ways. This section gives a quick overview of the various management possibilities.

Keyboard management

The Crocus SHDSL Table Top is also available in a version with an LCD display and a keyboard. Using this display and keyboard you can manage the Crocus SHDSL TT in a basic way. This is called keyboard management.

CLI and ATWIN

Connecting a VT100 terminal (emulation program) over a serial connection (i.e. through the control con-nector) to the Crocus SHDSL, you can evoke the following onboard management applications:

� CLI. The Command Line Interface allows you to manage the Crocus SHDSL through a text based interface.

� ATWIN. This is a basic, menu-driven user interface.

TMA and TMA CLI

Connecting your computer over a serial connection (i.e. through the control connector) to the Crocus SHDSL, you can use the following management applications:

� TMA. The Telindus Maintenance Application is a free management application for Windows. It allows you to manage the Crocus SHDSL using a user friendly GUI. To find out more about TMA, refer to the TMA manual.

� TMA CLI. This is an advanced Command Line Interface with extra scripting capabilities.To find out more about TMA CLI, refer to the TMA CLI manual.

Page 24: m Crocus SHDSL

Crocus SHDSL Chapter 1

User manual Introducing the Crocus SHDSL

10

Management concentrator

Connecting the Crocus SHDSL to a management concentrator (e.g. the Orchid 1003 LAN or Telindus 1035 Orchid) offers the following possibilities:

� Using the management concentrator as an IP proxy agent, you have the possibility to connect to the Crocus SHDSLover an IP network. In that case you can establish an IP connection with the Crocus SHDSLand run TMA, TMA CLI or the Web Interface over this connection. Using Telnet, you can also run ATWIN and CLI. For more information on how to use the management concentrator as an IP proxy agent, refer to the manual of the management concentrator.

� Using the management concentrator as an SNMP proxy agent, you can manage the Crocus SHDS-Lusing any SNMP management application. For more information on how to use the management concentrator as an SNMP proxy agent, refer to the manual of the management concentrator.

� The management concentrator allows you to manage the Crocus SHDSLwith TMA Element Manage-ment, a network management application that allows you to manage complete networks of Telindus devices.To find out more about TMA Element Management, refer to the TMA Element Management manual.

� The management concentrator allows you to manage the Crocus SHDSLwith TMA for HP OpenView, a network management application that runs on the HP OpenView platform. To find out more about TMA for HP OpenView, refer to the TMA for HP OpenView manual.

Page 25: m Crocus SHDSL

Crocus SHDSL Chapter 1

User manual Introducing the Crocus SHDSL

11

Management overview

The following table gives an overview of all the management possibilities and how you can connect them:

Management tool

Tool - Crocus SHDSL connection Tool - management concentrator connection

Serial1

1. Serial means through the control connector of the Crocus SHDSL.

IP2

2. IP means through the LAN connector of the management concentrator.

Serial1 IP2

Keyboard3

3. Connection with the Crocus SHDSL is internal. Keyboard and LCD are not available on all models.

CLI X4

4. Using a VT100 terminal (emulation program).

X4 X5

5. Using Telnet.

ATWIN X4 X4 X5

TMA X X X

TMA CLI X X X

TMA Element Mgt X

TMA for HPOV X

SNMP6

6. Using any SNMP browser.

X

Web Interface7

7. Using a web browser.

X

Page 26: m Crocus SHDSL

Crocus SHDSL Chapter 1

User manual Introducing the Crocus SHDSL

12

Page 27: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

13

2 Installing and connecting the Crocus SHDSL

First this chapter gives some important safety instructions. Then it explains how to install and connect the Crocus SHDSL TT and CV.

You are advised to read this chapter in a sequential manner, from the beginning to the end, without skip-ping any part. By doing so, your Crocus SHDSL 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 TT on page 20� 2.7 - Connecting the Crocus SHDSL Card Version on page 26� 2.8 - Remote power operation on page 33� 2.9 - Using a repeater on page 39� 2.10 - Front panel LED indicators on page 40

Page 28: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

14

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 elec-trician.

ACHTUNG! WICHTIGE SICHERHEITSINSTRUKTIONEN

Vor sämtlichen Arbeiten am Gerät (Installation, Einstellungen, Reparaturen etc.) sollten Sie den Netzstecker aus der Steckdose ziehen.Die Sicherheit dieses Gerätes ist abhängig von dem dritten Kontakt (dem Erdungspin) des 3-poligen Steckers. Beachten Sie unbedingt diese Sicherheitsstandard. Sollten Sie nur eine ältere 2-polige Steck-dose zur Verfügung 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 Beschädigung des Gerätes zu verhindern, beachten Sie bitte unbedingt die Sicherheitsbestim-mungen, 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.

Page 29: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

15

2.2 Unpacking

Checking the shipping carton

Rough handling during shipping causes most early failures. Before installation, check the shipping car-ton 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� TMA CD-ROM (including this User and Reference manual in PDF format)

Optionally (depending which sales item you ordered):

� power cord (Crocus SHDSL 115/230 Vac)

Page 30: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

16

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 dam-age the equipment.

ACHTUNG

Stellen Sie das Gerät niemals seitlich, sondern nur auf den Füßen auf und achten Sie darauf, daß die Lüftungsschlitze an der Seitenverkleidung frei bleiben.Stapeln Sie nicht mehrere Geräte direkt übereinander, dies kann zu einem Hitzestau führen.

Install the unit in an area free of extreme temperatures, humidity, shock and vibration. Position it so 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.

Page 31: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

17

2.4 Wall mounting

The Crocus SHDSL TT can be mounted on a wall. Proceed as follows:

Step Action

1 Drill two holes in the wall, according to the following specifications:·

� diameter of the drill: 4 mm� distance between the holes: 120 mm� depth of the holes: at least 25 mm

2 Insert two wall plugs in the holes, with following specifications:·

� diameter: 4 mm·� length: 20 mm

3 Screw two square hooks (steel zinc plated and white epox) in the plugs, with following dimensions:

4 Slide the Crocus SHDSL over the hooks until it touches the wall. This is indicated with in the figure below.

5 Slide the Crocus SHDSL down until it is firmly attached. This is indicated with in the following figure.

a

b

Page 32: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

18

The following figure illustrates how to mount the Crocus SHDSL against the wall:

Page 33: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

19

2.5 Installation and connection precautions

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

EMC compliant installation

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.

ANMERKUNG

Das Gerät kann gespeist wurden durch ein IT Power System.

Page 34: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

20

2.6 Connecting the Crocus SHDSL TT

This section explains how to connect the Crocus SHDSL TT. The following gives an overview of this sec-tion:

� 2.6.1 - Table Top connections on page 21� 2.6.2 - Connecting the power supply 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.5 - Inserting the DTE interface in the Table Top on page 25

Page 35: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

21

2.6.1 Table Top connections

All the connections have to be made at the back of the Table Top.

Crocus SHDSL - 115/230 Vac model

The following figure gives a rear view of the Crocus SHDSL TT.

Crocus SHDSL - 48V model

The following table labels the different parts located at the back of the Crocus SHDSL.

Part label Part description

PWR power switch

115/230 Vac-48Vdc

power inlet

Interface DTE interface slot

CTRL DB9 control connector (sometimes also called auxiliary or NMS connector)

LINE RJ45 line connector

Page 36: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

22

2.6.2 Connecting the power supply

The following table explains how to connect the power supply. The TT exists in two different models:

TT model Connector type Connecting the power supply

115/230 Vac standard IEC power supply connector

For a 115/230 Vac model, connect the standard IEC power supply connector to the power inlet. Refer to Crocus SHDSL - 115/230 Vac model on page 21.

-48 Vdc 48 V power sup-ply connector

For a -48 Vdc model, a power supply connector is delivered with the Crocus SHDSL.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 con-nected to +, while the negative voltage has to be connected to the -.When the -48 Vdc power supply connector is wired, con-nect it to the power inlet. Refer to Crocus SHDSL - 48V model on page 21.

Page 37: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

23

2.6.3 Signal and protective ground interconnection

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 49.

Page 38: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

24

2.6.4 Connecting the line to the Table Top

In order to connect the line to the Table Top, proceed as follows:

For optimum performance, the used line pairs have to be properly twisted pairs.

Step Action

1 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.

� RJ12 connector, then first plug in the RJ45 to RJ12 adapter in the line connector of the Crocus SHDSL. Then plug one end of the cable in the adapter.

For more information on the line connector and adapter layout, refer to 14.2 - Line spec-ifications on page 340 and 14.3 - RJ45 - RJ12 adapter specifications on page 342.

2 Plug the other end of the cable in the DSL outlet.

Page 39: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

25

2.6.5 Inserting the DTE interface in the Table Top

At the back of the TT, an empty slot is provided in which you can insert the desired DTE interface module without opening the housing.

To insert the DTE interface in the TT, proceed as follows:

Step Action

1 Gently slide the DTE interface on the two inner slides into the empty slot.The following figure shows this procedure:

2 When nearly inserted, press tight.

3 Lock both screws.

4 When the DTE interface is present, connect the application.

Page 40: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

26

2.7 Connecting the Crocus SHDSL Card Version

This section explains how to connect the Crocus SHDSL CV. The following gives an overview of this section.

� 2.7.1 - Inserting the Card Version in the CN4 card nest on page 27� 2.7.2 - Filling an entire CN4 card nest on page 28� 2.7.3 - The CN4 card nest line connector on page 29� 2.7.4 - Connecting the line to the Card Version on page 30� 2.7.5 - Inserting the DTE interface in the Card Version on page 31� 2.7.6 - Choosing 1 pair or 2 pair operation on the Crocus SHDSL 1P CV Twin on page 32

Page 41: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

27

2.7.1 Inserting the Card Version in the CN4 card nest

The CV consists of a stuffed print, provided with a front panel. The CV has to be inserted in the CN4 card nest. Most connections to this card are performed via 3 DIN-connectors on the back of the card:

� the middle connector for power supply, line and management connections� the two extreme connectors for interface connections.

To insert the CV in the CN4 card nest, proceed as follows:

Step Action

1 Gently slide the CV on the two inner slides into an available slot.The following figure shows this procedure:

2 When nearly inserted, press tight.

3 Fasten the two screws located at the front of the CV.

Page 42: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

28

2.7.2 Filling an entire CN4 card nest

For EMC reasons the cards all fit closely to each other. Therefore, you will experience that inserting the last card in a completely filled up rack is somewhat difficult. To fill up an entire rack, it is best to proceed as follows:

Step Action

1 Insert card 1 up to 14 in slot 0 up to 13 of the CN4 card nest.

2 Fasten the screws of card 1 up to 14.

3 Insert the last card in slot 14 of the CN4 card nest.

4 Fasten the screws of the last card.

Page 43: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

29

2.7.3 The CN4 card nest line connector

The line connector for the CV is provided at the back of the CN4 card nest. The following table explains which line pair has to be connected to which connector position:

For optimum performance, the used line pairs have to be properly twisted pairs.

Indication What to connect Figure

L1 � 1P CV Twin: line pair of modem A� 1P CV Twin as 2P1: line pair 1 of modem A� 2P CV Twin: line pair 1 of modem A

1. A Crocus SHDSL 1P CV Twin can be strapped to operate as a 2P (2 pair) version. However, in that case only modem A is operational and modem B is not used. Hence, connector posi-tions L1 and L3 are used to connect respectively line pair 1 and 2 of modem A. For more infor-mation, refer to 3.2.3 - Straps of the Crocus SHDSL 1P CV Twin on page 55.

L2 � 2P CV Twin: line pair 2 of modem A

L3 � 1P CV Twin: line pair of modem B� 1P CV Twin as 2P*: line pair 2 of modem A� 2P CV Twin: line pair 1 of modem B

L4 � 2P CV Twin: line pair 2 of modem B

Page 44: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

30

2.7.4 Connecting the line to the Card Version

The line connector for the CV is provided at the back of the CN4 card nest. To connect a line pair to the CN4 line connector, proceed as follows:

For more information on how to connect the line pairs to the CN4 card nest, refer to the manual of the CN4 card nest.

Step Action

1 Slide the wires of the line pair in the connector positions as indicated in 2.7.3 - The CN4 card nest line connector on page 29.

2 Fasten the line connector screws.

Page 45: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

31

2.7.5 Inserting the DTE interface in the Card Version

At the back of the CN4 card nest, empty slots are provided in which the desired DTE interface module can be inserted without extracting the card from the card nest. The upper interface slot is used for modem A and the lower interface slot is used for modem B.

To insert the DTE interface in the CN4 card nest, proceed as follows:

Step Action

1 Gently slide the DTE interface on the two inner slides into the slot that lies in line with the CV.The following figure shows this procedure:

2 When nearly inserted, press tight.

3 Fasten the two screws of the DTE interface.

4 When the DTE interface is present, connect the application.

Page 46: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

32

2.7.6 Choosing 1 pair or 2 pair operation on the Crocus SHDSL 1P CV Twin

A Crocus SHDSL 1P CV Twin can be strapped to operate as a 2P (2 pair) version. Do this by means of the appropriate straps located on the Crocus SHDSL CV motherboard. For more information, refer to 3.2.3 - Straps of the Crocus SHDSL 1P CV Twin on page 55.

Page 47: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

33

2.8 Remote power operation

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.8.1 - What is remote power (RP)? on page 34� 2.8.2 - Remote power operation overview on page 35� 2.8.3 - Activating remote power source operation on page 36� 2.8.4 - Installing the optional module for remote power source operation on page 37

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.

Page 48: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

34

2.8.1 What is remote power (RP)?

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 recommen-dation K.15.

The RP sink modem typically is dual powered. This means that it is either powered by a local power sup-ply or by remote power over the line. If the local power supply fails, then the RP sink modem is still pow-ered 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.

Page 49: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

35

2.8.2 Remote power operation overview

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:

Refer to 3.2.2 - DIP switches of the CV on page 53 for more information about the settings of the DIP switches of a CV device.

Version RP source RP sink

Crocus SHDSL CV X -

Crocus SHDSL TT - -

Crocus SHDSL G703 TT - -

Crocus SHDSL G703 TT RP - X

Crocus SHDSL RS530 TT - -

Crocus SHDSL RS530 TT RP - X

Page 50: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

36

2.8.3 Activating remote power source operation

The remote power is provided by an optional remote power module mounted on the Crocus SHDSL CV PCB.

Important remarks

� Only a Crocus SHDSL CV in combination with a remote power module can act as a remote power source.

� Only a Crocus SHDSL G703 RP or RS530 RP can act as remote power sink.

In order to activate remote power operation, proceed as follows:

Step Action

1 Install the optional remote power module. Refer to 2.8.4 - Installing the optional module for remote power source operation on page 37.

2 Set the appropriate DIP switches on the Crocus SHDSL CV PCB. Refer to 3.2.2 - DIP switches of the CV on page 53

3 Add the pwrSource object to the containment tree to enable remote power operation. Refer to 6.12 - Configuring remote power operation on page 146.

4 Install a Crocus SHDSL G703 RP or RS530 RP modem at the remote side of the link.

Page 51: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

37

2.8.4 Installing the optional module for remote power source operation

To enable remote power operation on the Crocus SHDSL CV, the optional module on the CV mother-board must be used.

When mounting the RP source module, it is important that the appropriate DIP switch is set correctly. Refer to 3.2.2 - DIP switches of the CV on page 53 for more information about the DIP switch.Failure to comply with this rule will result in irreversible damage to the Crocus SHDSL.

To install the remote power module, proceed as follows:

Step Action

1 Place the CV on a flat surface in front of you, with the DIP switches, straps, etc. facing up and the front panel facing the left side.

2 Take the optional module and hold it in such a way that the connectors and metal spacers are facing down.

To avoid damage to the Crocus SHDSL motherboard, mount the module with the con-nectors and metal spacers facing down!

3 Take the optional module and position the connectors of the module over the pin headers Jx-A and Jx-B of the CV motherboard (see figure below). Make sure the component side of the module is facing down.

4 Push the module down so that the pin headers slide in the connectors.

5 Turn the CV around, i.e. with the DIP switches, straps, etc. facing down.

6 Fasten the screw of the module through the hole in the CV motherboard.

⇒The optional remote power module is installed.

Page 52: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

38

Page 53: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

39

2.9 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 (N-side). 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 clock-ing.

� In case you have two Crocus SHDSL 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.

Page 54: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

40

2.10 Front panel LED indicators

This section gives an overview of the front panel LEDs and what they indicate. The following gives an overview of this section.

� 2.10.1 - Introducing the front panel LEDs on page 41� 2.10.2 - Power LED (PWR, green) on page 42� 2.10.3 - Test LED (TST/142, red) on page 42� 2.10.4 - Error LED (AIS/ERR, red) on page 43� 2.10.5 - Request to send LED (RTS/105, green) on page 43� 2.10.6 - Transmit data LED (TXD/103, green) on page 44� 2.10.7 - Receive data LED (RXD/104, green) on page 44� 2.10.8 - Data carrier detect LED (DCD/109, green) on page 44

Page 55: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

41

2.10.1 Introducing the front panel LEDs

When all the connections are made and the Crocus SHDSLis powered, the LEDs on the front panel reflect the actual status of the Crocus SHDSL.

The figures below show the front panel LED indicators of the Crocus SHDSL:

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 LED duty cycle Description

continuously off 0% The LED never lights up.

continuously on 100% The LED lights up continuously.

blinking 50% The LED is as much lit as it is out.

flashing 20% The LED only lights up during 20% of the time.

monitoring - The LED lights up irregularly. For instance, it lights up on detection of a certain signal. I.e. it monitors this signal.

Page 56: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

42

2.10.2 Power LED (PWR, green)

This LED indicates that the Crocus SHDSL is connected to the power supply and is switched on.

2.10.3 Test LED (TST/142, red)

This LED indicates whether the Crocus SHDSL is in normal operation or in test condition (ET, AL, RDL, DL or a combination of them). Four different status modes can be distinguished:

Termination of an active test by the management system is necessary to prevent hang-up situations caused by accidental activation of a test. Once the test indicator starts flashing, all active test conditions should be removed first, before initiating a new test session.

LED status Description

off No test is active.

continuously on An interface test is active.

In case the test LED and the power LED are on (all other LEDs are in a random state), then the Crocus SHDSL runs in loader mode. For more information on loader mode, refer to 12.1.2 - What is loader software? on page 316.

blinking A test initiated by the management system is active.

flashing An interface test has been terminated by the management system.

When the Crocus SHDSL switches from loader mode to application mode, the TST LED flashes 5 times.

Page 57: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

43

2.10.4 Error LED (AIS/ERR, red)

This LED indicates an error has occurred. The errors have different priority levels. I.e. when two errors of different origin occur at the same time, one error will get priority over the other error. The different error LED status modes and error priorities are displayed in the following table:

2.10.5 Request to send LED (RTS/105, green)

This LED indicates the state of the connected DTE equipment. It indicates the inverse of the linkDown status attribute of the modular interface. For the different modular interface types, this means the follow-ing:

LED status Description Error priority

off No error has occurred. -

monitoring The Crocus SHDSL its internal error test pattern generator / detector (ET) is active and received bit errors.

high

continuously on In case a G703 interface is used, it indicates an Alarm Indica-tion Signal (AIS) has been detected on the incoming G.704 transmit data. This means that the application has detected an error, and it communicates this to the interface by setting all data bits to 1 (which is the AIS condition).

medium

flashing (CV only)

Alarm signalling is active and an alarm has been detected.

For more information on alarm signalling, refer to 10.2.3 - Alarm signalling on page 291

low

Interface What the RTS LED indicates

RS530, V35, V36, HSSI

The LED is on when an RTS signal is detected. I.e. the connection between the Crocus SHDSL and the DTE is up.

X21 The LED is on when a valid C signal is detected. I.e. the connection between the Crocus SHDSL and the DTE is up.

G703 The LED is on when there is no loss of signal.

Bridge The LED is on when the LAN connector is plugged in the interface.

Router The LED is on when there is a connection between the Crocus SHDSL and the router interface.

Dual Port inter-faces

Both interfaces have to be up (as defined above), before the RTS LED lights up.

Page 58: m Crocus SHDSL

Crocus SHDSL Chapter 2

User manual Installing and connecting the Crocus SHDSL

44

2.10.6 Transmit data LED (TXD/103, green)

This LED monitors the data sent by the application (Data Terminal Equipment) to the DTE interface mod-ule of the Crocus SHDSL.

Note that the data is monitored after it went through the DTE interface circuitry. Some interfaces (G703, Bridge and Router) add framing information which activates the TXD LED even if no real user data is being transmitted.

2.10.7 Receive data LED (RXD/104, green)

This LED monitors the data sent to the application (Data Terminal Equipment) by the DTE interface mod-ule of the Crocus SHDSL.

Note that the data is monitored before it went through the DTE interface circuitry. Some interfaces (G703, Bridge and Router) used on the remote side add framing information which activates the RXD LED even if no real user data is being received.

2.10.8 Data carrier detect LED (DCD/109, green)

This LED indicates whether the central Crocus SHDSL is in synchronisation with the remote Crocus SHDSL. Three different modes can be distinguished:

In case of a Crocus SHDSL2P two DCD LEDs are present, one for each line pair.

LED status Description

off No signal is detected on the line.

blinking A training cycle between central and remote Crocus SHDSLis in progress.

on The central and remote Crocus SHDSLare synchronised. A data link is present.

Page 59: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

45

3 DIP switches and straps of the Crocus SHDSL

This chapter locates the DIP switches and straps on the Crocus SHDSL TT and Card Version mother-board. 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 46� 3.2 - DIP switches and straps of the Crocus SHDSL Card Version on page 51

Default settings are printed in bold.

Page 60: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

46

3.1 DIP switches and straps

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 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 47� 3.1.2 - DIP switches of the TT on page 48� 3.1.3 - Straps of the TT on page 49� 3.1.4 - Changing DIP switch and strap settings of the TT on page 50

Default settings are printed in bold.

Page 61: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

47

3.1.1 The TTmotherboard

The figure below shows the position of the DIP switches and straps on the TT motherboard.

Page 62: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

48

3.1.2 DIP switches of the TT

The following table gives an overview of DIP switch bank DS1 of the TT:

For more information on �

� DIP switch and strap location on the TT motherboard, refer to 3.1.1 - The TTmotherboard on page 47.� changing DIP switch and strap settings on the TT, refer to 3.1.4 - Changing DIP switch and strap set-

tings of the TT on page 50.

DIP switch name DS1 no. Setting Function

boot mode 1 on Normal operation.

off Start up in boot mode.

loader mode 2 on Normal operation.

off Start up in loader mode.

load default configura-tion

3 on Normal operation.

off Load default configura-tion.

- 4 - - not used -

Page 63: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

49

3.1.3 Straps of the TT

On the TT, you can configure the interconnection between signal ground and protective ground (earth). To do so, use strap ST9:

For more information on �

� DIP switch and strap location on the Crocus SHDSL motherboard, refer to 3.1.1 - The TTmotherboard on page 47.

� changing DIP switch and strap settings on the Crocus SHDSL, refer to 3.1.4 - Changing DIP switch and strap settings of the TT on page 50.

Strap settings Connection Description

disconnected As default, the signal ground is disconnected from the earth. This avoids problems which might occur when the earth potential of the Crocus SHDSL and the connected application is not the same. In such a situation earth cur-rent loops may induce distortion on the transmitted data, resulting in transmission errors.

connected through 100 ohms resistor

Sometimes you might want to connect the Crocus SHDSL earth to the application earth although both earth potentials are not the same. (E.g. to avoid a big dif-ference between both earth potentials.) To avoid that high earth currents are generated, you can make this connection through a 100 ohms resistor.

directly con-nected

Sometimes it is not possible to connect the application directly to the earth. In that case you can earth the appli-cation through the Crocus SHDSL by connecting the Crocus SHDSL to the earth and setting strap ST9 in position 3.Also the opposite situation might occur: it is not possible to earth the Crocus SHDSL. In that case you can earth the Crocus SHDSL through the applica-tion by connecting the application to the earth and set-ting strap ST9 in position 3.

Page 64: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

50

3.1.4 Changing DIP switch and strap settings of the TT

To change the DIP switch and/or strap settings of the Crocus SHDSL, proceed as follows:

Step Action

1 Switch the Crocus SHDSL off.

2 Disconnect the Crocus SHDSL from the mains.

3 Unscrew the two screws located at the back of the Crocus SHDSL.

4 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.

5 Change the DIP switch and/or strap settings.

6 Replace the cover and close tight.

7 Fasten the two screws located at the back of the Crocus SHDSL.

8 Reconnect the Crocus SHDSL to the mains.

9 Switch the Crocus SHDSL on.

Page 65: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

51

3.2 DIP switches and straps of the Crocus SHDSL Card Version

This section locates the DIP switches and straps on the Crocus SHDSL Card Version 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.2.1 - The CV motherboard on page 52� 3.2.2 - DIP switches of the CV on page 53� 3.2.3 - Straps of the Crocus SHDSL 1P CV Twin on page 55� 3.2.4 - Changing DIP switch and strap settings of the CV on page 56

Page 66: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

52

3.2.1 The CV motherboard

The figure below shows the position of the DIP switches and straps on the Crocus SHDSL CV mother-board.

Page 67: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

53

3.2.2 DIP switches of the CV

DIP switch bank DS1

The following table gives an overview of DIP switch bank DS1 of the Crocus SHDSL CV:

DIP switch name DS1 no. Setting Function

Boot mode 1 on Normal operation.

off Start up in boot mode.

loader mode 2 on Normal operation.

off Start up in loader mode.

load default configura-tion - modem A

3 on Normal operation.

off Load default configura-tion.

load default configura-tion - modem B

4 on Normal operation.

off Load default configura-tion.

optional powering mod-ule

5 on Normal operation

off On board powering module used, for remote power source operation

- 6 - - not used -

- 7 - - not used -

- 8 - - not used -

Page 68: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

54

DIP switch bank #ADS1 and #CDS1

Use DIP switch banks #ADS1 and #CDS1 to enable remote power source operation:

When mounting the RP source module, it is important that these DIP switches are set to off.Failure to comply with this rule will result in irreversible damage to the Crocus SHDSL.

Refer to 2.8.4 - Installing the optional module for remote power source operation on page 37 for more information on how to install the optional module.

For more information on �

� DIP switch and strap location on the CV motherboard, refer to 3.2.1 - The CV motherboard on page 52.

� changing DIP switch and strap settings on the CV, refer to 3.2.4 - Changing DIP switch and strap settings of the CV on page 56.

DIP switch name #ADS1 and #CDS1 no.

Setting Function

remote power 1, 2, 3 and 4 on remote power source operation disabled

off remote power source operation enabled

Page 69: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

55

3.2.3 Straps of the Crocus SHDSL 1P CV Twin

A Crocus SHDSL 1P CV Twin can be strapped to operate as a 2P (2 pair) version. To do so, use straps ST2, ST4 and ST6:

For more information on �

� DIP switch and strap location on the CV motherboard, refer to 3.2.1 - The CV motherboard on page 52.

� changing DIP switch and strap settings on the CV, refer to 3.1.4 - Changing DIP switch and strap settings of the TT on page 50.

Strap settings Function

The Crocus SHDSL CV operates as a 1P CV Twin, i.e. two modems (A and B) on one card each with 1 line pair.

The Crocus SHDSL CV operates as a 2P CV Single, i.e. one modem (A) on one card with 2 line pairs.In this case, modem B can not be used.

Page 70: m Crocus SHDSL

Crocus SHDSL Chapter 3

User manual DIP switches and straps of the Crocus SHDSL

56

3.2.4 Changing DIP switch and strap settings of the CV

To change the DIP switch settings of the CV, proceed as follows:

Step Action

1 Loosen the two screws located at the front of the CV.

2 Slide the CV out of the CN4 card nest.

3 Change the DIP switch and/or strap settings.

4 Gently slide the CV on the two inner slides into the CN4 card nest again.The following figure shows this procedure:

5 When nearly inserted, press tight.

6 Fasten the two screws located at the front of the CV.

Page 71: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

57

4 Managing the Crocus SHDSL

Once you installed the Crocus SHDSL, you can proceed with the configuration. You can do this using any of the management tools introduced in 1.7 - Management overview on page 9.

This chapter briefly highlights two of those management tools: the Telindus Maintenance Application (TMA) and keyboard management. It gives an introduction and describes how to start a management session on the Crocus SHDSL. Furthermore, it also introduces the terminology concerning the manage-ment of a Telindus device.

The following gives an overview of this chapter.

� 4.1 - Starting TMA on the Crocus SHDSL on page 58� 4.2 - Starting keyboard management on the Crocus SHDSL on page 64� 4.3 - Introducing the management attributes of the Crocus SHDSL on page 65

Page 72: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

58

4.1 Starting TMA on the Crocus SHDSL

This section introduces the Telindus Maintenance Applications (TMA). Then it explains how you can start a TMA session on the Crocus SHDSL.

The following gives an overview of this section.

� 4.1.1 - Introducing TMA on page 59� 4.1.2 - Starting a TMA session through the control connector on page 60� 4.1.3 - Starting a TMA session through a management concentrator on page 62� 4.1.4 - Important remarks on starting a TMA session on page 63

Page 73: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

59

4.1.1 Introducing TMA

What is the Telindus Maintenance Application?

TMA is a free Windows software package that enables you to maintain the Crocus SHDSL, 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 Telindus 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. The most recent model files can always be downloaded from the Telindus web site at http://www.telindusproducts.com/tma.

How to connect TMA?

There are two ways to establish a connection between the computer running TMA and the Crocus SHDSL:

� over a serial connection, through the control connector of the Crocus SHDSL.� over an IP or a serial connection, through a management concentrator.

Page 74: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

60

4.1.2 Starting a TMA session through the control connector

To establish a connection between the computer running TMA and the Crocus SHDSL through the con-trol connector, proceed as follows:

Step Action

1 Connect the COM port of your PC through a straight DB9 male-female cable with the con-trol connector of your Crocus SHDSL as shown in the following figure:

2 Start TMA.

3 In the TMA window, either �

� select from the menu bar: Connect → Device�� or press the shortcut key: Ctrl+N� or press on the Connect to device button:

The Connect (to a device) window is being displayed as in the following figure:

4 In the Connect (to a device) window, configure the following parameters:

� Select the option Serial, and specify the COM port of your computer the Crocus SHDSL is connected to.

� If a password has previously been configured in the Crocus SHDSL then also fill in the password field.

5 If the necessary parameters are filled in, press the Next > button.

Page 75: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

61

6 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:

7 Two situations can be distinguished depending on establishing a connection to a Crocus SHDSL TT, CV or CV Twin:

� For a Crocus SHDSL TT and CV, the following applies:- In order to connect to the local Crocus SHDSL, choose On device.- In order to connect to the remote Crocus SHDSL, choose After device and enter

relative NMS address 1 or higher.� For a Crocus SHDSL CV Twin, select the following:

- In order to connect to the local Crocus SHDSL, choose On device and select modem A or modem B.

- In order to connect to the remote Crocus SHDSL choose After device, enter rela-tive NMS address 1 or higher and select modem A or modem B.

If a password has previously been configured in the Crocus SHDSL then also fill in the password field.

8 If the necessary parameters are filled in, press the Finish button.

9 After a couple of seconds, the attributes of the selected Crocus SHDSL appear in the TMA window.

Step Action

Page 76: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

62

4.1.3 Starting a TMA session through a management concentrator

On central locations with many access devices, the Crocus SHDSL can be connected to a management concentrator (e.g. Orchid 1003 LAN or Telindus 1035 Orchid). In this case the management concentrator is a proxy device for the Crocus SHDSL. This means you can connect TMA to the Crocus SHDSL through the management concentrator.

What is more, the management concentrator can act as an IP proxy device for the Crocus SHDSL. The IP address related to the Crocus SHDSL is defined in the management concentrator.

Refer to the manual of the management concentrator for more information on the configuration and man-agement capabilities of this device.

Page 77: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

63

4.1.4 Important remarks on starting a TMA session

Starting a TMA session on modem B of a Crocus SHDSL CV Twin

Suppose that both modem A and B of a Crocus SHDSL CV Twin have a password. In that case, if you want to connect with TMA to modem B �

� first enter the password of modem A in the Connect device window (refer to 4.1.2 - Starting a TMA session through the control connector on page 60, step 3).

� then enter the password of modem B in the Select device window (refer to 4.1.2 - Starting a TMA session through the control connector on page 60, step 6).

Starting a TMA session on a remote device

The following table shows you which attributes are of importance when starting a TMA session on a remote device:

Obviously, you can only start a TMA session on the remote device if the data link is up.

If you want to open a TMA session on a remote �

then set the attribute �

Crocus SHDSL TT, ctrlPortProtocol to management.

What is more, if the remote Crocus SHDSL TT contains a router interface and you want to man-age this "remote" interface, then also the ctrlPort-Protocol of the remote Crocus SHDSL TT has to be set to management.

Telindus 1420 SHDSL Router, eocChannel to itu-G.991.2.

Page 78: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

64

4.2 Starting keyboard management on the Crocus SHDSL

Keyboard management on the Table Top

If you have an Crocus SHDSL Table Top that is equipped with an LCD display and a keyboard, you can use this display and keyboard to manage the Crocus SHDSL TT.

Keyboard management on the Card Version

The Crocus SHDSL Card Version does not exist in a version with LCD display and keyboard. Instead, you can use the Telindus EasyConnect hand-held terminal to manage the Crocus SHDSL CV. This is comparable to the LCD display and keyboard on the Crocus SHDSL TT.

How to start keyboard management?

In order to start keyboard management, proceed as follows:

Status information on the display

When you are not busy managing the Crocus SHDSL with the keyboard, the display shows status infor-mation. For more information, refer to Chapter 5 - The front panel display on page 71.

Step Action

1 On the keyboard, press the key until the following string is displayed:

<Model Browsing>

2 Press the Enter key. Now the following is displayed:

PASSWORD:←

3 In case previously �

� a password has been configured in the Crocus SHDSL, then �- Press the enter the key.- Select the needed characters by means of the , and Enter keys.- When finished, press the Enter key.

� no password has been configured in the Crocus SHDSL, then just press the Enter key.

4 Now you are ready to manage the Crocus SHDSL TT using the keyboard.

To find out how exactly you can use the keyboard to browse the containment tree, to change attribute values, etc., refer to the Telindus EasyConnect manual (PDF) and more specifically to the section "How to browse a model?".

In order to exit keyboard management, repeatedly press the Esc key until the main dis-play window appears again.

Page 79: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

65

4.3 Introducing the management attributes of the Crocus SHDSL

This section gives an introduction to the management attributes of the Crocus SHDSL. It introduces terms such as containment tree, group, object, attribute, value and action.

The following gives an overview of this section.

� 4.3.1 - Containment tree terminology on page 66� 4.3.2 - The Crocus SHDSL containment tree on page 68� 4.3.3 - Crocus SHDSL attribute overview on page 69

Page 80: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

66

4.3.1 Containment tree terminology

The following figure depicts the TMA window containing the Crocus SHDSL containment tree.

Page 81: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

67

The following table explains the terminology associated with the containment tree.

Term Description

contain-ment tree

The containment tree represents the hierarchical structure of the Crocus SHDSL. It is composed of a number of objects that are ordered in a tree. This tree resembles a Win-dows directory structure:

� it is also a levelled structure, with nodes which can be expanded or reduced� the containment tree objects can be compared with file folders� the objects contain attributes like file folders contain files.

object 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 crocusShdsl<Tt|Cv> 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 cor-responding 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:

� configuration� status� performance� alarms.

action 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 crocusShdsl<Tt|Cv> is selected in combination with the group Configuration.

Page 82: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

68

4.3.2 The Crocus SHDSL containment tree

The following table lists the different objects of the Crocus SHDSL containment tree.

Object This object contains �

> crocusShdsl<Tt|Cv> the general system attributes. It is the top object in the containment tree.

E.g. the status attribute sysUpTime: 00005d 02h 53m 16s.

Note that:

� for a TT this object is called crocusShdslTt� for a CV this object is called crocusShdslCv.

>> line the general line attributes.

E.g. the configuration attribute channel.

>>> linePair[ ] the specific line pair attributes.

E.g. the status attribute lineAttenuation (dB).

>> <dteInterface> the DTE interface attributes.

E.g. the configuration attribute clocking.

The name of this object depends on the type of DTE interface.

E.g. v35 in case of a V35 interface, g703 in case of a G703 interface, �

>> management the network management attributes.

E.g. the configuration attribute consoleNoTrafficTimeOut.

>> operatingSystem the operating system attributes.

E.g. the performance attribute currUsedProcPower (%).

Page 83: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

69

4.3.3 Crocus SHDSL attribute overview

The reference part of this manual explains all the attributes of the Crocus SHDSL. One chapter describes one group of attributes:

� chapter 7 describes the configuration attributes� chapter 8 describes the status attributes� chapter 9 describes the performance attributes� chapter 10 describes the alarm attributes.

Page 84: m Crocus SHDSL

Crocus SHDSL Chapter 4

User manual Managing the Crocus SHDSL

70

Page 85: m Crocus SHDSL

Crocus SHDSL Chapter 5

User manual The front panel display

71

5 The front panel display

The Crocus SHDSL Table Top is also available in a version with an LCD display and a keyboard. Using this display and keyboard you can manage the Crocus SHDSL TT in a basic way. By connecting the Telindus EasyConnect hand-held terminal to a Crocus SHDSL Card Version you can manage it in a sim-ilar way.

When you are not busy managing the Crocus SHDSL with the keyboard, the display shows status infor-mation. This chapter describes the information that can be seen on the display.

The following gives an overview of this chapter.

� 5.1 - The "windows" of the front panel display on page 72� 5.2 - The main window on page 73� 5.3 - The line window on page 75� 5.4 - The DTE window on page 76� 5.5 - The test window on page 77� 5.6 - The model browsing window on page 78� 5.7 - The connect remote window on page 78� 5.8 - The version window on page 78

Page 86: m Crocus SHDSL

Crocus SHDSL Chapter 5

User manual The front panel display

72

5.1 The "windows" of the front panel display

Pressing the or key on the keyboard, allows you to navigate through the different front panel display "win-dows". The following gives an overview of the different front panel display windows:

Pressing the Esc key in any window returns you to the main window.

Page 87: m Crocus SHDSL

Crocus SHDSL Chapter 5

User manual The front panel display

73

5.2 The main window

The main window displays general status information. The structure of the window is as follows:

The following table clarifies the main window display structure:

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

1 C d o w n V 3 5 f b

2 S H D S L c 2 0 4 8 / 2 0 4 8 i n t p

Display position Field Description

row 1 - column 2 consistency Displays whether the Crocus SHDSL is under consistency of a management concentrator or not:·

� C: under consistency,·� blank: not under consistency.

row 1 - column 3 � 6 general status Displays the general state of the Crocus SHDSL: up, down, test.

row 1 - column 13 � 18 DTE type Displays the DTE interface type currently in use: V35, V36, X21, G703, RS530, BRIDGE, ROUTER, �

row 1 - column 20 & 21 fallback speed Displays whether the Crocus SHDSL operates in fallback speed or not:

� fb: fallback speed,� blank: no fallback speed.

row 2 - column 1 � 5 modem type Displays the modem type: SHDSL.

row 2 - column 6 channel Displays the channel currently in use:

� c: central channel,� r: remote channel.

Page 88: m Crocus SHDSL

Crocus SHDSL Chapter 5

User manual The front panel display

74

row 2 - column 8 � 11 line speed (kbps) Displays the line speed currently in use: from 64 up to 2304.

row 2 - column 13 � 16 DTE speed (kbps)

Displays the DTE interface speed currently in use: from 64 up to 2304.

row 2 - column 18 � 21 clocking Displays the clocking mode currently in use:

� int: internal clocking� inta: internal alternative clocking� intp: internal preferred clocking� sr: slave-receive clocking� sr-a: slave-receive alternative clocking� sr-p: slave-receive preferred clocking� ext: external clocking� exlb: external loop-back clocking� stat: station clocking.

Display position Field Description

Page 89: m Crocus SHDSL

Crocus SHDSL Chapter 5

User manual The front panel display

75

5.3 The line window

The line window displays status information of the line. The structure of the window is as follows:

The following table clarifies the line window display structure:

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

1 l i n e : t e s t 2 0 4 8 d a t a

2 a t t : 2 6 . 5 d B n m r : 2 7 . 5 d B

Display position Field Description

row 1 - column 1 signal quality Displays the signal quality pyramid.

row 1 - column 2 � 6 line pairs Displays for which line pair the status information is being displayed:

� line: there is only 1 line pair,� l1: status information of line pair 1 is being dis-

played,� l2: status information of line pair 2 is being dis-

played.

row 1 - column 7� 10 line status Displays the state of the line: up, down, test.

row 1 - column 12 � 15 line speed (kbps) Displays the line speed currently in use: from 64 up to 2304.

row 1 - column 17 � 24 modem status Displays the state of the modem: idle, data, hs_preac, hs_activ, ch_bitrt, equ_trn, etc.

row 2 - column 1 � 10 attenuation Displays the attenuation in dB.

row 2 - column 12 � 21 noise margin Displays the noise margin in dB.

Page 90: m Crocus SHDSL

Crocus SHDSL Chapter 5

User manual The front panel display

76

5.4 The DTE window

The DTE window displays status information of the DTE interface. The structure of the window is as fol-lows:

The following table clarifies the DTE window display structure:

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

1 V 3 5 : u p 2 0 4 8 i n t p

2 t d r d r t s c t s d s r d c d

Display position Field Description

row 1 - column 1 � 7 DTE type Displays the DTE interface type currently in use: V35, V36, X21, G703, RS530, BRIDGE, ROUTER, �

row 1 - column 8 � 11 DTE status Displays the state of the DTE interface: up, down, test.

row 1 - column 13 � 16 DTE speed (kbps)

Displays the DTE interface speed currently in use: from 64 up to 2304.

row 1 - column 18 � 21 clocking Displays the clocking mode currently in use:

� int: internal clocking� inta: internal alternative clocking� intp: internal preferred clocking� sr: slave-receive clocking� sr-a: slave-receive alternative clocking� sr-p: slave-receive preferred clocking� ext: external clocking� exlb: external loop-back clocking� stat: station clocking.

row 2 DTE signals Displays the state of the DTE interface signals:

� lowercase: the corresponding signal is off (not active).� uppercase: the corresponding signal is on (active).

The following indications are possible:

� td: transmit data� rd: receive data� rts: request to send� cts: clear to send� dsr: data set ready� dcd: data carrier detect� ind: indicator signal� ais: alarm indication signal� lfa: loss of frame alignment� los: loss of signal

Page 91: m Crocus SHDSL

Crocus SHDSL Chapter 5

User manual The front panel display

77

5.5 The test window

In the test window you can �

� execute a diagnostic test.� clear the error counter.� monitor the status of a diagnostic test.

The structure of the window is as follows:

The following table clarifies the test window display structure:

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

1 r l + e t

2 e t a l r l d l c l r

Display position Field Description

row 1 - column 1 � 7 test type Displays the type of test currently in use: no test, et, al, rl, dl, al+et and rl+et.

row 1 - column 7 � 15 test status and origina-tor

Briefly displays the status of the test currently in use: progress or ending,

and then displays the originator of the test cur-rently in use: keyboard, nms, interface, remote, cmditpr, network or layer2.

row 1 - column 17 � 24 error counter Displays the number of detected errors since the start of an ET, AL-ET or RL-ET test: 0 up to 65534. An overflow condition is indicated by 65535 or *****.

row 2 - column 3 & 4 error test Using these actions you can start a diagnostic test. Proceed as follows:

1. Move the cursor with the and keys underneath the string of the test you want to start.

2. Press the Enter key.⇒The test starts and the corresponding test

string becomes uppercase.

3. To stop the test, press the Enter key again.Þ The test stops and the corresponding test string becomes lowercase again.

row 2 - column 7 & 8 analogue loop

row 2 - column 11 & 12 remote digital loop

row 2 - column 15 & 16 digital loop

row 2 - column 20 � 21 clear error counter Using this action you can clear the error counter. Move the cursor with the and keys under-neath the clr string and press the Enter key.

Page 92: m Crocus SHDSL

Crocus SHDSL Chapter 5

User manual The front panel display

78

5.6 The model browsing window

The model browsing window allows you to enter the containment tree of the Crocus SHDSL. This allows you to manage the Crocus SHDSL using the keyboard. This is called keyboard management.

For more information, refer to 4.2 - Starting keyboard management on the Crocus SHDSL on page 64

5.7 The connect remote window

Using the connect remote action allows you to display and operate the front panel windows of the remote Crocus SHDSL from your local Crocus SHDSL. This means you can also perform keyboard manage-ment on the remote Crocus SHDSL using the local keyboard and display.

5.8 The version window

The version window displays the version of the application software (also called control software or firmware) and the DSP software. The structure of the window is as follows:

The following table clarifies the line window display structure:

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

1 C T L / T 2 1 3 6 / 0 0 1 0 0 0 1 / 0 1 / 0 2

2 L D R : T 2 1 3 7 / 0 0 1 0 0 0 1 / 0 1 / 0 2

Display position Field Description

row 1 control version Displays the control software code, version and release date.

row 2 loader version Displays the loader software code, version and release date.

Page 93: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

79

6 Step-by-step configuration

This chapter describes in a step-by-step manner how to perform a basic configuration on Crocus SHDSL.

You are advised to read this chapter in a sequential manner, from the beginning to the end, without skip-ping any part. By doing so, your Crocus SHDSL will be completely configured and ready for use when you reach the end of this chapter.

The following gives an overview of this chapter.

� 6.1 - Configuring the basic line parameters on page 80� 6.2 - Configuring EOC handling on page 82� 6.3 - Configuring the timing mode on page 88� 6.4 - Configuring the clocking mode on page 89� 6.5 - Configuring the user speed on page 108� 6.6 - Configuring the minimum line speed on page 113� 6.7 - Configuring framing and time slots on page 118� 6.8 - Configuring the user speed and time slots on the Dual Port G703-Serial interface on page 122� 6.9 - Low speed limitations on the G703 Nx64k interfaces on page 125� 6.10 - Configuring the interface specific attributes on page 127� 6.11 - Configuring the management attributes on page 133� 6.12 - Configuring remote power operation on page 146� 6.13 - Configuring passwords on page 147� 6.14 - Executing configuration actions on page 149� 6.15 - Troubleshooting the Crocus SHDSL on page 153� 6.16 - Crocus SHDSL compatibility with other SHDSL devices on page 154

For a complete overview of the attributes of the Crocus SHDSL, refer to the reference manual.

Page 94: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

80

6.1 Configuring the basic line parameters

crocusShdsl<Tt|Cv>/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 synchro-nisation procedure of the modem.

The default channel setting of a Crocus SHDSL is remote, while that of a Crocus SHDSL 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.

crocusShdsl<Tt|Cv>/line/region

The region attribute defines which S-HDSL standard is used:

For compatibility with other SHDSL devices, setting this attribute to the correct value might be essential. Refer to 6.16 - Crocus SHDSL compatibility with other SHDSL devices on page 154.

crocusShdsl<Tt|Cv>/line/mode

This attribute is only present on a Crocus SHDSL 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:

Value Description

annexA The American S-HDSL standard is used.

annexB The European S-HDSL standard is used.

auto The S-HDSL standard is selected automatically.

If the mode attribute is set to � then use the attribute �

singlePair, speed to configure the user speed.

dualPair, speed2P to configure the user speed.

Default:remote for TT / central for CVRange: remote / central

Default:annexBRange: enumerated, see below

Default:dualPairRange: singlePair / dualPair

Page 95: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

81

crocusShdsl<Tt|Cv>/line/eocChannel

Use the eocChannel attribute to determine how the checksum of Embed-ded 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:

For compatibility with other SHDSL devices, setting this attribute to the correct value might be essential. Refer to 6.16 - Crocus SHDSL compatibility with other SHDSL devices on page 154.

Value Description

proprietary The checksum is calculated using a proprietary method.

itu-G.991.2 The checksum is calculated using the G.SHDSL standard method.

Default:itu-G.991.2Range: itu-G.991.2 / proprietary

Page 96: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

82

6.2 Configuring EOC handling

This section explains what EOC is. Then it explains how you can configure the handling of the EOC mes-sages. Finally, it discusses which information is retrieved depending on the setting of the eocHandling attribute.

The following gives an overview of this section.

� 6.2.1 - What is EOC? on page 83� 6.2.2 - The EOC handling attribute on page 83� 6.2.3 - Discovering devices on the SHDSL line on page 84� 6.2.4 - EOC retrieved information on page 84

Page 97: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

83

6.2.1 What is EOC?

SHDSL devices can communicate with each other through the Embedded Operations Channel (EOC). For instance the Crocus SHDSL 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.).

The EOC messages are defined in G.991.2 to provide interoperability.

6.2.2 The EOC handling attribute

crocusShdsl<Tt|Cv>/line/eocHandling

Use the eocHandling attribute to define the handling of the EOC messages.

The eocHandling attribute has the following values:

Value Description

none The Crocus SHDSL does not send EOC requests. However, the Crocus SHDSL will answer on EOC requests coming from other SHDSL devices.

discovery The Crocus SHDSL "scans" the SHDSL line. For every device it discovers, it adds an object to the containment tree. Refer to 6.2.3 - Discovering devices on the SHDSL line on page 84.

Then the Crocus SHDSL 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 6.2.4 - EOC retrieved information on page 84.

inventory

info

alarmConfiguration Also in this case the Crocus SHDSL "scans" the SHDSL line, adds the objects to the containment tree and retrieves information from the devices. Refer to 6.2.3 - Discovering devices on the SHDSL line on page 84 and 6.2.4 - EOC retrieved information on page 84.

Additionally, the central1 SHDSL device forces the remote2 SHDSL device and any intermediary repeater to use the link alarm thresholds lineAttenuation and signal-Noise 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 crocusShdsl<Tt|Cv>/line/linkAlarmThresholds on page 176 for more information.

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.

Default:noneRange: enumerated, see below

Page 98: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

84

6.2.3 Discovering devices on the SHDSL line

When you change the eocHandling attribute from none to any other value, the Crocus SHDSL starts "scan-ning" the SHDSL line in order to determine which devices are present between itself and its remote coun-terpart. 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 as central device, a Telindus 1421 SHDSL Router as remote device and one Crocus SHDSL 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.

6.2.4 EOC retrieved information

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.

Page 99: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

85

3.R

efer

to 6

.2.2

- Th

e E

OC

han

dlin

g at

tribu

te o

n pa

ge83

for m

ore

info

rmat

ion

on th

e ala

rmCo

nfigu

ratio

n va

lue.

EOC status information

EOC

sta

tus

info

rmat

ion

Doe

s th

e at

trib

ute

or e

lem

ent d

ispl

ay re

leva

nt in

form

atio

n in

cas

e eo

cHan

dlin

g is

set

to �

?

Obj

ect

croc

usSh

-ds

l<Tt|C

v>/�

Attr

ibut

e(E

lem

ent)

none

disc

over

yin

vent

ory

info

alarm

Conf

igur

atio

n

line

eocA

larmT

hres

holds

(lineA

ttenu

ation

, sign

al-No

ise)

No.

The

val

ue is

al

way

s 0.

0.�

On

the

cent

ral1 : y

es. T

he v

alue

s ar

e th

ose

as s

et in

the

linkA

-lar

mThr

esho

lds a

ttrib

ute.

�O

n th

e re

mot

e2 : n

o. T

he v

alue

is a

lway

s 0.

0.

1.Th

e ce

ntra

l dev

ice

is th

e de

vice

on

whi

ch th

e ch

anne

l attr

ibut

e is

set

to ce

ntral.

2.Th

e re

mot

e de

vice

is th

e de

vice

on

whi

ch th

e ch

anne

l attr

ibut

e is

set

to re

mote.

Yes

. The

val

ues

are

thos

e as

set

in th

e lin

kA-

larmT

hres

holds

attr

ibut

e on

the

cent

ral d

evic

e.3

numD

iscov

ered

Repe

aters

Yes

.

repe

ater[

]or en

d

vend

orId

(coun

tryCo

de, p

rovid

er-

Code

, ven

dorS

pecif

ic)

No

repe

ater[

] or

end

obje

ct is

cre

-at

ed.

Yes

.

vend

orMo

del

No.

Yes

.

vend

orSe

rial

No.

Yes

.

vend

orSo

ftVer

sion

No.

Yes

.

eocS

oftVe

rsion

Yes

.

shds

lVer

sion

Yes

.

eocS

tate

Yes

.

eocA

larmT

hres

holds

(lineA

ttenu

ation

, sign

al-No

ise)

No.

The

val

ue is

alw

ays

0.0.

Yes

. The

val

ues

are

thos

e as

set

in th

e lin

kA-

larmT

hres

holds

attr

ibut

e on

the

rem

ote

devi

ce.

Yes

. The

val

ues

are

thos

e as

set

in th

e lin

kA-

larmT

hres

holds

attr

ibut

e on

the

cent

ral d

evic

e.

repe

ater[

]/line

Pair[

]or en

d/line

Pair[

]

lineA

ttenu

ation

No

repe

ater[

] or

end

obje

ct is

cre

-at

ed.

No.

The

val

ue is

alw

ays

0.0.

Yes

. The

val

ues

are

the

actu

al li

ne a

ttenu

atio

n an

d si

gnal

noi

se a

s m

easu

red

on th

e re

mot

e de

vice

.sig

nalN

oise

Page 100: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

86

EOC performance information

EOC

per

form

ance

info

rmat

ion

Doe

s th

e at

trib

ute

or e

lem

ent d

ispl

ay re

leva

nt in

form

atio

n in

cas

e eo

cHan

dlin

g is

set

to �

?

Obj

ect

croc

usSh

-ds

l<Tt|C

v>/�

Attr

ibut

eno

nedi

scov

ery

inve

ntor

yin

foala

rmCo

nfig

urat

ion

repe

ater[

]/line

Pair[

]or en

d/line

Pair[

]

lineP

aram

eters

No

repe

ater[

] or

end

obje

ct is

cre

-at

ed.

No.

The

val

ue is

alw

ays

0.0.

Yes

. The

val

ues

are

the

sam

e as

thos

e on

the

rem

ote

devi

ce.

Not

e th

at in

this

cas

e th

e sy

sUpT

ime

is n

ot th

e el

apse

d tim

e si

nce

the

last

col

d bo

ot, b

ut th

e el

apse

d tim

e si

nce

the

crea

tion

of th

e re

peate

r[ ] o

r en

d ob

ject

.

perfo

rman

ce

h2Lin

ePar

amete

rs

h2Pe

rform

ance

h24L

inePa

rame

ters

h24P

erfor

manc

e

d7Lin

ePar

amete

rs

d7Pe

rform

ance

Page 101: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

87

EOC alarm information

EOC

ala

rm in

form

atio

nD

oes

the

attr

ibut

e or

ele

men

t dis

play

rele

vant

info

rmat

ion

in c

ase

eocH

andl

ing

is s

et to

� ?

Obj

ect

croc

usSh

-ds

l<Tt|C

v>/�

Attr

ibut

eno

nedi

scov

ery

inve

ntor

yin

foala

rmCo

nfig

urat

ion

line/l

inePa

ir[ ]

lineA

ttenu

ation

The

thre

shol

ds a

s co

nfig

ured

in th

e lin

kAlar

mThr

esho

lds a

ttrib

ute

on th

e lo

cal d

evic

e ar

e us

ed to

gen

erat

e th

e al

arm

s.Th

e th

resh

olds

as

con-

figur

ed in

the

linkA

larm-

Thre

shold

s attr

ibut

e on

th

e ce

ntra

l1 dev

ice

are

used

to g

ener

ate

the

alar

ms2 .

1.Th

e ce

ntra

l dev

ice

is th

e de

vice

on

whi

ch th

e ch

anne

l attr

ibut

e is

set

to ce

ntral.

2.R

efer

to 6

.2.2

- Th

e E

OC

han

dlin

g at

tribu

te o

n pa

ge83

for m

ore

info

rmat

ion

on th

e ala

rmCo

nfigu

ratio

n va

lue.

signa

lNois

e

repe

ater[

]/line

Pair[

]or en

d/line

Pair[

]

lineA

ttenu

ation

No

repe

ater[

] or

end

obje

ct is

cre

-at

ed.

No

alar

ms

are

gene

rate

d.Th

e th

resh

olds

as

con-

figur

ed in

the

linkA

larm-

Thre

shold

s attr

ibut

e on

th

e lo

cal d

evic

e ar

e us

ed to

gen

erat

e th

e al

arm

s.

The

thre

shol

ds a

s co

n-fig

ured

in th

e lin

kAlar

m-Th

resh

olds a

ttrib

ute

on

the

cent

ral d

evic

e ar

e us

ed to

gen

erat

e th

e al

arm

s.

signa

lNois

e

errS

ecEx

ceed

edTh

e th

resh

olds

as

con-

figur

ed in

the

linkA

larm-

Thre

shold

s attr

ibut

e on

th

e lo

cal d

evic

e ar

e us

ed to

gen

erat

e th

e al

arm

s.

sevE

rrSec

Exce

eded

Page 102: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

88

6.3 Configuring the timing mode

crocusShdsl<Tt|Cv>/line/timingMode

Use the timingMode attribute to set the timing mode.

The Crocus SHDSL 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:

� In case of a G703 Nx64k interface, if you set the framing attribute to framed, then the Crocus SHDSL 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 essen-tial. Refer to 6.16 - Crocus SHDSL compatibility with other SHDSL devices on page 154.

Value Description

plesiochronous In this mode each SHDSL frame has 0 or 4 stuffing bits to compensate clock devi-ations towards the user interface clock. In this mode, all possible clocking modes can be selected.

synchronous 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.

Default:plesiochronousRange: synchronous / plesiochronous

Page 103: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

89

6.4 Configuring the clocking mode

This section explains how to configure the clocking mode on the Crocus SHDSL. It also explains how the auto clocking mechanism works. The following gives an overview of this section.

� 6.4.1 - The clocking attribute on page 90� 6.4.2 - Possible clocking modes versus DTE interface on page 91� 6.4.3 - Fixed clocking modes on page 92� 6.4.4 - Preferred and alternative clocking on page 93� 6.4.5 - Schematic overview of the different clocking modes on page 94� 6.4.6 - Special points of interest concerning clocking on some interfaces on page 95� 6.4.7 - Clocking decision sequenceson the Crocus SHDSL on page 97� 6.4.8 - The presence of the external clock signalon the Crocus SHDSL on page 99� 6.4.9 - Auto-sensingon the Crocus SHDSL on page 100� 6.4.10 - Auto clocking for RS530, V35 and V36 interfaces on page 101� 6.4.11 - Auto clocking for Bridge and Router interfaces on page 103� 6.4.12 - Auto clocking for the X21 interface on page 104� 6.4.13 - Some examples of auto clocking on page 106

Page 104: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

90

6.4.1 The clocking attribute

The location of the clocking attribute in the Crocus SHDSL containment tree is:

crocusShdsl<Tt|Cv>/<dteInterface>/clocking

Use the clocking attribute to select a clocking mode. The available clocking modes depend on which DTE interface is used. Also the default clocking mode is interface dependent.

All possible clocking modes and their exact notation (important if you work with CLI!) are given in the table of 6.4.2 - Possible clocking modes versus DTE interface on page 91.

Default:<interface dependent>Range: enumerated, see below

Page 105: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

91

6.4.2 Possible clocking modes versus DTE interface

The available clocking modes depend on which DTE interface is used in the Crocus SHDSL. The follow-ing table gives an overview:

The default clocking mode is indicated in bold.

Clocking mode V35, V36, RS530

X211

1. Refer to 6.4.6 - Special points of interest concerning clocking on some interfaces on page 95 for some specific remarks concerning clocking on these interfaces.

Bridge, Router

G7031 DP G703-Serial1

auto X X X

internal X X X

internalPreferred X X

internalAlternative X X

slaveRcv X

slaveRcvPreferred X X

slaveRcvAlternative X X

external X X X X

externalLoopback X X

station(CV only)

X X

Page 106: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

92

6.4.3 Fixed clocking modes

This section explains the fixed clocking modes. The following table gives an overview:

Clocking mode Description

internal The Crocus SHDSL generates the transmit clock signal and sends it to the appli-cation via the TxClk circuit (circuit 114).

Internal clocking can be selected in combination with preferred or alternative clock-ing. This is explained in the following section.

slave receive The transmit clock signal is derived from the received line data. This reconstructed clock signal is sent to the application via the TxClk circuit (circuit 114).

Slave receive clocking can be selected in combination with preferred or alternative clocking. This is explained in the following section.

external The application generates the transmit clock signal and sends it to the Crocus SHDSL via the ExtTxClk circuit (circuit 113).

external loop-back

The receive clock signal (RxClk) is the same as the external transmit clock signal (ExtTxClk).

The external and external loop-back differenceThe following explains the difference between external and external loop-back clocking mode:

� external clocking mode: the receive data is sampled by the DTE with the RxClk signal. In this case, the RxClk does not have to be in phase with the ExtTxClk signal (i.e. no re-timing required on the receive data).

� external loop-back clocking mode: the receive data is sampled by the DTE with the ExtTxClk signal. In this case, the RxClk signal has to be in phase with the ExtTxClk signal (i.e. re-timing on the receive data).

station Remark

Station clocking can only be selected when you use a Crocus SHDSL CV with a G703 interface.

The station clock signal is applied to a connector located on the back of the CN4 card nest. This clock signal is then routed to the Crocus SHDSL via the backplane of the nest. The Crocus SHDSL then uses the station clock as reference clock for the receive data.

Page 107: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

93

6.4.4 Preferred and alternative clocking

Internal and slave receive clocking can be selected in combination with preferred or alternative clocking:

The switch-over time between alternative and preferred clocking is about 100ms.

Clocking mode Description

preferred The application loops back the output of the TxClk circuit (circuit 114) to the Ext-TxClk circuit (circuit 113). This guarantees an optimal phase relationship between the transmitted data and the transmitted clock. This because the transmission delays of the TxD circuit (circuit 103) and the ExtTxClk circuit are exactly the same, since the outputs of both circuits originate in the application and are fed into the Crocus SHDSL.

alternative The application does not loop back the output of the TxClk (circuit 114) to the Ext-TxClk (circuit 113). In this case the clock is looped back within the Crocus SHDSL itself.

Remark

In case you select an alternative clocking mode, be aware that the transmission delays between the TxD circuit and the ExtTxClk circuit can become significant. Especially when you use high speeds, long cables interconnecting the Crocus SHDSL and application or interface converters. As a result transmit clock and transmit data can become out of phase, which results in errors.In case transmit clock and transmit data are out of phase, you could try to adjust this by inverting the transmit sample clock. Do this using the transmitSampleClock attribute.

Page 108: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

94

6.4.5 Schematic overview of the different clocking modes

The following figures give a schematic overview of all the clocking possibilities:

Page 109: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

95

6.4.6 Special points of interest concerning clocking on some interfaces

This section gives a few special points of interest concerning clocking on some interfaces.

X21 interface clocking

For the X21 interface the special points of interest are:

Special point of interest

Description

external loop-back

S and X clock

Normal X.21 operation only provides the S clock (DCE originated), which is used for both transmit and receive clocking. Therefore, the normal clock configuration would be internal alternative at one side, and slave receive alternative at the other.If the X clock circuit is present, external clocking is also possible. In that case, the S clock is only used to clock out the receive data.

External loop-back

Many applications on X.21 deny the S clock signal and sample the receive data with their X clock. However, in case the S and X clock are not in phase, bit errors may occur. This is especially so when there is some jitter on the receive data sig-nal. To solve this problem you can use the external loop-back clocking mode. In this clocking mode the receive clock is the same as the external transmit clock.

Remark

A set-up using external loop-back clocking can only work when the remote Crocus SHDSL is in slave receive clocking mode.

ignoring the X clock

In case you have a set-up in which you do not use the X clock and if you want to avoid that the (possible) presence of an X clock signal negatively influences the clocking, then you can choose to ignore the X clock signal completely. Do this by setting the xSignal attribute to ignore (refer to 7.6.2 - X21 interface configuration attributes on page 188).

extended X21 link

When connecting two X21 interfaces back-to-back for an extended X21 link, use the external clocking mode. In that case, the receive data is sent to the DTE with the S clock, independently of the X clock.

Page 110: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

96

G703 interface clocking

In internal clocking mode it is the Crocus SHDSL who generates the reference clock signal to sample the receive data. In station clocking mode the station clock on the CN4 card nest is used as reference clock.

Both internal and station clocking mode imply 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.

Dual Port G703-Serial interface clocking

The available clocking modes on the Dual Port G703-Serial interface are actually those of the G703 interface (internal, external and station). The serial interface always slaves on the clock of the G703 interface. The only clocking modes that you can select on the serial interface are preferred or alternative clocking.

Page 111: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

97

6.4.7 Clocking decision sequenceson the Crocus SHDSL

This section gives an introduction to clocking decision sequences on the Crocus SHDSL.

Clocking decision sequences

Clocking decisions are not only made in auto clocking mode, but also in fixed clocking mode. For instance when the Crocus SHDSL is configured in external clocking mode and the external clock signal is lost, then the Crocus SHDSL decides to go to internal alternative clocking mode in order to continue operation.

Page 112: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

98

Which factors influence the clocking decision sequence?

The following table lists all the factors that influence the clocking decision sequence. They are listed from the highest to the lowest priority.

Priority Influencing factor

1 Initiation of a test

Depending on which type of diagnostic test is started, the Crocus SHDSL selects a new clocking mode in order to continue correct operation.

2 The local / remote interface combination

Not only the local, but also the remote interface type has an impact on the clocking deci-sion sequence. Especially X21 and G703 interfaces require special attention, because they have limited clocking possibilities.

3 The local configured clocking mode

The clocking mode that you configure is not necessarily the clocking mode that will be used.

E.g. if you configured the Crocus SHDSL in internal preferred clocking mode, but no clock signal is detected on the ExtTxClk pin of the interface, then the Crocus SHDSL will select internal alternative clocking mode.

4a1

1. These three items are on the same priority level.

The actual remote clocking mode

This information in combination with the remote interface type information as described under priority 2 has a certain impact on the clocking mode that will actually be chosen by the Crocus SHDSL.

4b1 The presence of an external clock signal

The presence or absence of the external clock signal also plays its role in the clocking decision sequence.

4c1 For X21: the master / slave selection and remote auto or fixed clocking mode

This information is useful when both local and remote Crocus SHDSL are equipped with an X21 interface. If both X21 interfaces are in auto clocking mode, one has to act as mas-ter and the other as slave in the clocking decision sequence. They mutually decide who will be the master and who the slave.

5 The line synchronisation

Some applications require that a clock signal is always present on the RxClk circuit. If a Crocus SHDSL is in slave receive clocking mode and the local and remote Crocus SHDSL are not synchronised, then the RxClk is derived �·

� from the ExtTxClk in case an external clock signal is detected·

or

� from a clock signal generated internally in the Crocus SHDSL.

Page 113: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

99

6.4.8 The presence of the external clock signalon the Crocus SHDSL

The presence or absence of an external clock signal may influence the clocking mode that is actually chosen by the Crocus SHDSL. This section explains how.

All interfaces supporting the external clock signal, regularly check the presence of this external clock sig-nal. The following table clarifies what happens when no external clock signal is present or when it is lost:

If the Crocus SHDSL is con-figured in �

and if the external clock signal is not present or if it is lost,

a preferred clocking mode,

then the Crocus SHDSL automatically switches to alternative clocking mode.

If at a certain moment the external clock signal (re)appears, the Crocus SHDSL switches (back) to the preferred clocking mode.

external, exter-nal loop-back or station clocking mode,

then the Crocus SHDSL automatically switches to internal alternative clocking mode.

If at a certain moment the external clock signal (re)appears, the Crocus SHDSL switches (back) to external, external loop-back or station clocking mode.

Page 114: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

100

6.4.9 Auto-sensingon the Crocus SHDSL

This section explains what auto-sensing is.

What is auto-sensing?

Auto-sensing is a part of the clocking decision process. As already explained in 6.4.7 - Clocking decision sequenceson the Crocus SHDSL on page 97 and 6.4.8 - The presence of the external clock signalon the Crocus SHDSL on page 99, the presence of an external clock signal has an impact on the clocking decision sequence. This is shown in the following table:

If the external clock signal �

then the Crocus SHDSL selects �

is present, external clocking mode.In this case, the auto clock selection sequence ends here.

is not present, internal or slave receive clocking mode. In this case, the auto clock selection sequence continues:

� If the external clock signal appears (i.e. the DTE loops back the clock signal to the ExtTxClk pin of the interface), then the Crocus SHDSL selects internal or slave receive preferred clocking mode.

� If the external clock signal does not appear(i.e. the DTE does not loop back the clock signal to the ExtTxClk pin of the interface), then the Crocus SHDSL selects internal or slave receive alternative clocking mode.

Remark

The selection between internal or slave receive clocking mode depends on the remote interface type / remote clocking combination.

Page 115: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

101

6.4.10 Auto clocking for RS530, V35 and V36 interfaces

In case of auto clocking, initially the Crocus SHDSL selects a clocking mode depending on the interface and clocking mode used by the remote Crocus SHDSL. After that also other factors may influence the clocking decision sequence as explained in 6.4.7 - Clocking decision sequenceson the Crocus SHDSL on page 97.

This section explains the auto clocking decision for a local RS530, V35 and V36 interface in function of the remote interface and clocking mode.

Remote inter-face

Remote clock-ing mode

Clocking mode selected by the local Crocus SHDSL

G703 internal � slave receive preferred� slave receive alternative

The decision between these clocking modes is made by the auto-sensing mechanism. Refer to 6.4.9 - Auto-sensingon the Crocus SHDSL on page 100

station

external � external� slave receive preferred� slave receive alternative

The decision between these clocking modes is made by the auto-sensing mechanism. Refer to 6.4.9 - Auto-sensingon the Crocus SHDSL on page 100

X21 internal � external� slave receive preferred� slave receive alternative

The decision between these clocking modes is made by the auto-sensing mechanism. Refer to 6.4.9 - Auto-sensingon the Crocus SHDSL on page 100

Remark

The combination X21 + internal clock and RS530, V35 or V36 + external clock is not advisable because in X21 systems only one clock source may be present. However, the local Crocus SHDSL selects this external clocking mode to indicate that the application generates a clock signal.

external

slave receive � external loop-back� internal preferred� internal alternative

The decision between these clocking modes is made by the auto-sensing mechanism. Refer to 6.4.9 - Auto-sensingon the Crocus SHDSL on page 100

Page 116: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

102

other any � external� external loop-back

(in case the remote interface is in slave receive clocking mode)

� internal preferred� internal alternative

The decision between these clocking modes is made by the auto-sensing mechanism. Refer to 6.4.9 - Auto-sensingon the Crocus SHDSL on page 100

Remote inter-face

Remote clock-ing mode

Clocking mode selected by the local Crocus SHDSL

Page 117: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

103

6.4.11 Auto clocking for Bridge and Router interfaces

In case of auto clocking, initially the Crocus SHDSL selects a clocking mode depending on the interface and clocking mode used by the remote Crocus SHDSL. After that also other factors may influence the clocking decision sequence as explained in 6.4.7 - Clocking decision sequenceson the Crocus SHDSL on page 97.

This section explains the auto clocking decision for a local Bridge and Router interfaces in function of the remote interface and clocking mode.

Remote inter-face

Remote clocking mode

Clocking mode selected by the local Crocus SHDSL

G703 any slave receive

X21 any slave receive

other any internal

Page 118: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

104

6.4.12 Auto clocking for the X21 interface

In case of auto clocking, initially the Crocus SHDSL selects a clocking mode depending on the interface and clocking mode used by the remote Crocus SHDSL. After that also other factors may influence the clocking decision sequence as explained in 6.4.7 - Clocking decision sequenceson the Crocus SHDSL on page 97.

This section explains the auto clocking decision for a local X21 interface in function of the remote inter-face and clocking mode.

Local interface: X21 - remote interface: X21

When both local and remote Crocus SHDSL are equipped with an X21 interface and at least one of them is in auto clocking mode, then one interface is chosen as master and the other as slave:

� If only one X21 interface is in auto clocking mode, then this interface is the master.� If both X21 interfaces are in auto clocking mode, they mutually decide who will be the master and

who the slave.

First the auto clocking decision of the X21 master is explained, then that of the X21 slave.

X21 master

External clock signal present?

Remote clock-ing mode

Clocking mode selected by the local Crocus SHDSL

yes slave receive external loop-back

anything else external

no slave receive � internal preferred� internal alternative

The decision between these clocking modes is made by the auto-sensing mechanism. 6.4.9 - Auto-sensingon the Crocus SHDSL on page 100.

internal or exter-nal

� slave receive preferred� slave receive alternative

The decision between these clocking modes is made by the auto-sensing mechanism. 6.4.9 - Auto-sensingon the Crocus SHDSL on page 100

Page 119: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

105

X21 slave

Is the remote clocking mode fixed slave receive?

Clocking mode selected by the local Crocus SHDSL

yes � external loop-back� internal preferred� internal alternative

The decision between these clocking modes is made by the auto-sensing mechanism. Refer to 6.4.9 - Auto-sensingon the Crocus SHDSL on page 100.

no � external� external loop-back� slave receive preferred� slave receive alternative

The decision between these clocking modes is made by the auto-sensing mechanism. Refer to 6.4.9 - Auto-sensingon the Crocus SHDSL on page 100.

Page 120: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

106

6.4.13 Some examples of auto clocking

This section gives some examples of decision sequences made by the Crocus SHDSL when it is con-figured in auto clocking mode.

The following figures and corresponding text display the auto clocking decision. Normally only the clock-ing decision of the local Crocus SHDSL is described, unless the decision of the remote Crocus SHDSL has an impact on the decision of the local Crocus SHDSL. In that case, both auto clocking decision sequences are given.

Auto clocking example: V35 and auto clocking - V35 and auto clocking

Page 121: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

107

Auto clocking example: X21 and auto clocking - X21 and auto clocking

When both local and remote Crocus SHDSL are equipped with an X21 interface and when both are con-figured for auto clocking mode, they mutually decide who will be the auto clocking master and who the slave.

Page 122: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

108

6.5 Configuring the user speed

This section explains how to configure the user speed. It also explains how the auto speed mechanism works. The following gives an overview of this section:

� 6.5.1 - The speed attribute on page 109� 6.5.2 - Using odd speeds on the Crocus SHDSL 2P when using serial interfaces on page 110� 6.5.3 - How does the auto speed mode work? on page 111� 6.5.4 - Clocking and speed combinations on page 112

In case of a G703 interface, skip this section and go to 6.7 - Configuring framing and time slots on page 118 for the time slot configuration.

Page 123: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

109

6.5.1 The speed attribute

The location of the speed attribute in the Crocus SHDSL containment tree is:

crocusShdsl<Tt|Cv>/<dteInterface>/speed

Use the speed attribute to select a user speed. The user speeds can be set either to a fixed speed or to auto speed. The user speed ranges from 64 kbps up to 2304 kbps in steps of 64 kbps.

The exact notation of the user speed (important if you work with CLI) is: <speed>kbps. For example 64kbps, 2048kbps, 2304kbps, �

crocusShdsl<Tt|Cv>/<dteInterface>/speed2P

This attribute is only present on a Crocus SHDSL 2P (2 pair) version.

Use the speed2P attribute to select a user speed in case of a Crocus SHDSL 2P (if it is truly in 2 pair oper-ation, see below). The user speeds can be set either to a fixed speed or to auto speed. The user speed ranges from 128 kbps up to 4096 kbps in steps of 128 kbps.

In case of the serial interfaces, it is possible to select the user speed in steps of 64 kbps or 128 kbps. Refer to 6.5.2 - Using odd speeds on the Crocus SHDSL 2P when using serial interfaces on page 110.

The exact notation of the user speed (important if you work with CLI) is: <speed>kbps. For example 128kbps, 1024kbps, 4608kbps, �

When you change the line/mode attribute, then make sure that you use the correct speed attribute to set the user speed:

Important remark

� In case of a Crocus SHDSL 2P (2 pair) version, set the speed2P attribute of either the central or remote Crocus SHDSL to auto, but not of both. Else the 2 line pairs could train at a different speed which is not allowed.

� In case you use a G703 interface in one Crocus SHDSL and a serial interface in 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.

� If both the central1 and remote2 Crocus SHDSL are configured in external clocking mode and an external clock signal is present, then it is the central Crocus SHDSL modem who determines the speed on which the line trains.

If the mode attribute is set to � then use the attribute �

singlePair, speed to configure the user speed.

dualPair, speed2P to configure the user speed.

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.

Default:autoRange: enumerated, see below

Default:autoRange: enumerated, see below

Page 124: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

110

6.5.2 Using odd speeds on the Crocus SHDSL 2P when using serial interfaces

When using serial interfaces (RS530, V35, V36 X21) in the Crocus SHDSL 2P, odd speeds can be used.

With PCB version 1.2 and lower, the user speed could only be adjusted in steps of 128 kbps. As of PCB version 2.0, user speeds between 64kbps and 2048 kbps can be selected in steps of 64kbps; once above 2048 kbps, steps of 128 kbps are possible. All speeds that are a variation of 64 kbps (so 32 kbps per line pair) are called odd speeds. Refer to the following table:

Refer to 6.5.1 - The speed attribute on page 109 for more information about the speed2P attribute.

Important remarks

� When using odd speeds, the interface works in slotted E1 mode. This means that only one clock source is allowed. If more than one clock source is available, communication will fail.

� The line speed will always be a multiple of 128 kbps. The following example illustrates this:When a user speed of 192 kbps is selected, 3 timeslots with data will have to be sent over the line. One timeslot with dummy data will be sent together with the three data timeslots. This results in a line speed of 256 kbps (multiple of 128 kbps).

� When using auto speed on one of two interfaces, the resulting line speed will always be a multiple of 128 kbps.The following example illustrates this:- central modem: user speed = 320 kbps (5 timeslots)- remote modem: user speed = auto speed; This results in 5 timeslots of 64 kbps and one dummy timeslot. So the resulting line speed will be 384 kbps (multiple of 128 kbps). When a line speed of 320 kbps is required, the user must set the speed to 320 kbps manually on the remote side.

PCB version Possible user speed �

1.2 and lower can vary between 128 kbps and 4096 kbps in steps of 128kbps.

As of 2.0 can vary between 64 kbps and 4096 kbps, in steps of:

� 64 kbps up to 2048 kbps� 128 kbps from 2176 kbps up to 4608 kbps

Page 125: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

111

6.5.3 How does the auto speed mode work?

The following table explains how the auto speed mode works:

Important remark

� In case of a Crocus SHDSL 2P (2 pair) version, set the speed2P attribute of either the central or remote Crocus SHDSL to auto, but not of both. Else the 2 line pairs could train at a different speed which is not allowed.

� 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.

� If both the central1 and remote2 Crocus SHDSL are configured in external clocking mode and an external clock signal is present, then it is the central Crocus SHDSL modem who determines the speed on which the line trains.

If the Crocus SHDSL is con-figured in �

then the Crocus SHDSL�

external clocking mode and an external clock signal is present,

measures the frequency of the external clock signal and automati-cally adapts the user speed.

The user speed (and ditto external clock) can range from 64 kbps up to 2304 kbps in steps of 64 kbps.

any other clocking mode, adopts the speed as selected on the remote Crocus SHDSL.

When both local and remote Crocus SHDSL are configured in auto speed mode, the user speed is set to the maximum common user speed on both sides.

Special case - G703

In case the interface used in the remote Crocus SHDSL is a G703 interface configured in �

� framed mode, then the user speed is calculated as the sum of the selected G.704 time slots.

� unframed (transparent) mode, then the user speed is set to 2 Mbps.

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.

Page 126: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

112

6.5.4 Clocking and speed combinations

The following table shows which user speed the local Crocus SHDSL will adopt when it is set to auto speed and this in function of the local clocking and remote user speed and clocking combination.

Remote Crocus SHDSL(speed / clock)

Local Crocus SHDSL

(speed / clock)

auto / external auto / internal or slave receive

fixed / external fixed / internal or slave receive

auto / external The local user speed equals the local external clock.

The local user speed equals the local external clock.

The local user speed equals the local external clock.

The local user speed equals the local external clock.

auto / internal or slave receive

The local user speed equals the remote external clock.

The local user speed equals the maximum com-mon user speed.

The local user speed equals the remote fixed speed. (Speed should match external clock!)

The local user speed equals the remote fixed speed.

Page 127: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

113

6.6 Configuring the minimum line speed

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:

� 6.6.1 - Important remark on the minimum line pair speed on page 114� 6.6.2 - The minimum line pair speed attribute on page 115� 6.6.3 - Purpose of the minimum line pair speed on page 117

Page 128: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

114

6.6.1 Important remark on the minimum line pair speed

If you configure the minimum line pair speed (i.e. you set the minLinePairSpeed attribute to any value dif-ferent from <opt>), then only one master clock is allowed in the system.

In other words, only the following clocking combinations are allowed:

Executing an ET test on both sides will not work in case both sides change their clocking modes to inter-nal!

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:

One side Other side

internal always slave receive

external slave receive

external external (provided the application on both sides use the same network clock)

station station or slave receive

� clocking = internalPreferred� speed = 640kbps� minLinePairSpeed = <opt>

� clocking = internalPreferred� speed = 640kbps� minLinePairSpeed = <opt>

� clocking = internalPreferred� speed = 640kbps� minLinePairSpeed = 1024kbps

� clocking = slaveRcvPreferred� speed = 640kbps� minLinePairSpeed = 1024kbps

Page 129: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

115

6.6.2 The minimum line pair speed attribute

Also see 6.6.1 - Important remark on the minimum line pair speed on page 114.

The location of the minimum line pair speed attribute in the Crocus SHDSL containment tree is:

crocusShdsl<Tt|Cv>/line/minLinePairSpeed

Use the minLinePairSpeed attribute to determine what the minimum speed on the line pair has to be when the Crocus SHDSL 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 a G703 Nx64k interface in the Crocus SHDSL with less than 3 time slots configured (or 6 time slots on a 2 pair version) or a serial interface in the Crocus SHDSL with speeds lower than 192 kbps.

Default:<opt>Range: 192kbps up to

2048kbps (in steps of 64kbps)

Page 130: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

116

The minLinePairSpeed attribute has the following values:

� 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.

Value Description

<opt> 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 �

� 640 kbps in case of a Crocus SHDSL 1P (1 pair) version.� 320 kbps on each line pair in case of a Crocus SHDSL 2P (2 pair) version.

192kbps up to 2048kbps (in steps of 64kbps)

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 min-imum line speed is set to 1024 kbps (minLinePairSpeed = 1024kbps), then the speed on the line pair(s) equals 1024 kbps. (On a Crocus SHDSL 1P (1 pair) version this is also the total line speed. On a Crocus SHDSL 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 minLinePair-Speed attribute is 2048 kbps. So for a Crocus SHDSL 1P (1 pair) version you can set the minLinePairSpeed attribute to its maximum value (being 2048 kbps). For a Crocus SHDSL 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 minLinePa-irSpeed attribute to a value higher than 1024 kbps, then a message is displayed in the messages table and the Crocus SHDSL 2P continues to operate with a total line speed of 2048 kbps.

Page 131: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

117

6.6.3 Purpose of the minimum line pair speed

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 a G703 Nx64k interface in the Crocus SHDSL with only 1 or 2 time slots configured (or 2 or 4 time slots in case of a 2 pair version) or a serial interface in the Crocus SHDSL with speeds lower than 192 kbps, 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 a G703 Nx64k interface in the Crocus SHDSL with only 2 time slots configured (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 crocusShdsl<Tt|Cv>/line/framerType on page 222 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 impos-sible 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 crocusShdsl<Tt|Cv>/line/framerType on page 222 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.

Page 132: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

118

6.7 Configuring framing and time slots

This section explains how to select the framing mode and how to allocate time slots on a G703 Nx64k interface. The following gives an overview of this section:

� 6.7.1 - Selecting unframed or framed mode on page 119� 6.7.2 - Selecting the time slots on page 120� 6.7.3 - Time slot transposition on page 121

Page 133: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

119

6.7.1 Selecting unframed or framed mode

crocusShdsl<Tt|Cv>/g703/framing

Use the framing attribute to select between unframed or framed mode:

Value Description

unframed 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 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 dis-abled.

� Crocus SHDSL 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 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 times-lots configured in the timeslot attribute:- If the line speed is lower than the configured timeslots, then the correspond-

ing 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 2P (2 pair) version, set the framing attribute of either the central or remote Crocus SHDSL 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.

Default:unframedRange: framed / auto /

unframed

Page 134: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

120

6.7.2 Selecting the time slots

crocusShdsl<Tt|Cv>/g703/timeSlots

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 when using a G703 Nx64k interface in the local Crocus SHDSL and a non-G703 interface in the remote Crocus SHDSL.

� ·In case you use a G703 interface in one Crocus SHDSL and a serial interface in 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.

� 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.

Local G703 Nx64k versus remote interface

The following table shows you what to do or what happens on the remote Crocus SHDSL (depending on the used interface), when the local Crocus SHDSL is equipped with a G703 Nx64k interface in framed mode:

Example

If the remote Crocus SHDSL is equipped with �

set to � then �

an RS530, V35, V36, X21, Bridge or Router

a fixed speed, this fixed speed has to be configured by the user and should equal Nx64 kbps (with N = number of allocated time slots on the local G703 Nx64k interface).

auto speed, its speed is adapted automatically to Nx64 kbps (with N = number of allocated time slots on the local G703 Nx64k interface).

a G703 Nx64k interface the same amount of time slots should be config-ured by the user as on the local Crocus SHDSL.

� framed mode� TS6, TS12, TS25 = 1� all other time slots = 0

� auto speed, slave receive clock⇒the DTE interface speed

changes to 192 kbps (3x64 kbps)

Default:ts0=1, other ts=0Range: enumerated, see below

Page 135: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

121

6.7.3 Time slot transposition

If at both sides of the link a G703 Nx64k interface is used, it is possible to perform a time slot transposi-tion. 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 is put in TS10 of the remote Crocus SHDSL, TS12 in TS16 and TS25 in TS26. A similar mechanism exists in the receive direction.

The following figure shows the time slot transposition mechanism:

� framed mode� TS6, TS12, TS25 = 1� all other time slots = 0

� framed mode� TS10, TS16, TS26 = 1� all other time slots = 0

Page 136: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

122

6.8 Configuring the user speed and time slots on the Dual Port G703-Serial interface

Because on the Dual Port G703-Serial interface you can configure both a user speed and time slots, this section highlights some special points of interest concerning this configuration.

The following gives an overview of this section:

� 6.8.1 - Selecting unframed or framed mode on page 123� 6.8.2 - Configuring the user speed and time slots on page 123� 6.8.3 - How is the serial and G703 data ordered? on page 124

Page 137: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

123

6.8.1 Selecting unframed or framed mode

On the G703 interface of the Dual Port G703-Serial interface you can select between unframed or framed mode as described in 6.7.1 - Selecting unframed or framed mode on page 119.

Unframed mode can only work when the Dual Port G703-Serial interface is used as G703 interface only. So if you set the framing attribute to unframed, then the Dual Port G703-Serial interface always works in G703 only mode, independently of the setting of the multiplexingMode attribute. Also refer to 6.10.3 - Configuring the Dual Port G703-Serial interface on page 130.

6.8.2 Configuring the user speed and time slots

On the �

� serial interface of the Dual Port G703-Serial interface you can configure a user speed in the same way as on the other serial interfaces (RS530, V35, V36, etc.). Refer to 5.8 - Configuring the user speed.

� G703 interface of the Dual Port G703-Serial interface you can configure the time slots in the same way as on a regular G703 Nx64k interface. Refer to 5.10 - Configuring framing and time slots. How-ever, note that if you use �- both the serial and the G703 interface, then at least one time slot has to be set. Else the serial

interface does not work (you can not use the serial interface only).- the G703 interface only, then you can set the time slots as on a regular G703 Nx64k interface.

When using both the serial and the G703 interface care has to be taken that the sum of the user speed and the time slots does not exceed the maximum possible line speed. If it does, a warning is logged in the status message table.

Page 138: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

124

6.8.3 How is the serial and G703 data ordered?

When using both the serial and the G703 interface, the data coming from the G703 interface is put on the line first followed by the data coming from the serial interface. This is shown in the following two examples.

Example

As you can see in this example, the first time slots on the remote G703 interface (TS 7, 8, 9) match the time slots of the central G703 interface (TS 1, 3, 7). The time slots do not necessarily have to be the same on both sides (time slot transposition). The remaining time slots on the remote G703 interface are filled with the data from the central serial interface.

Example

As you can see in this example, the time slots on the remote G703 interface (TS 7, 8, 9) match the time slots of the central G703 interface (TS 1, 3, 7). The time slots do not necessarily have to be the same on both sides (time slot transposition), but the order remains the same.

Page 139: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

125

6.9 Low speed limitations on the G703 Nx64k interfaces

When configuring low speed on the G703 Nx64k interfaces, there are some limitations regarding time slot configuration (and in some cases a workaround to overcome these limitations). The following tables give an overview of these limitations when using different interfaces in the Crocus SHDSL and connect-ing the Crocus SHDSL to other Telindus SHDSL devices. The table below shows the different combina-tions of possible user speeds for central and remote units. The user speeds are indicated with value N. N is a 64kbit/s multiple (e.g. N = 32 = 2048kbit/s). The first table gives all the combinations for 1 pair SHDSL devices, while the second table gives the combinations for 2 pair SHDSL devices. The cells in grey have few practical use. This does not mean the devices cannot operate in this way as central or remote units.

1 Pair versions:

Remote device

Central device

Crocus SHDSL + serial/router if

Crocus SHDSL + G703 Nx64K

Crocus SHDSL G703 (RP)

Crocus SHDSL + Dual Port if

Telindus 1421 in Pleisio-chronous mode

Crocus SHDSL + serial/router if

N = 1 � 36 N = 1 � 32 N = 1 � 32 N = 1 � 32

Crocus SHDSL + G703 Nx64K

N = 1 � 32 N = 1 � 32 N = 1 � 32 N = 3 � 321

1. N = 1�31 on serial interface. The time slots on the central G703 destined for the G703 on the remote DP interface have the lowest time slot values.

N = 1 � 32

Crocus SHDSL G703 (RP)

N = 1 � 32 N = 1 � 32 N = 1 � 32 N = 3 � 321 N = 1 � 32

Crocus SHDSL + G703-Serial DP

N = 3 � 321

Crocus SHDSL Quad

N = 1 � 32 N = 1 � 32 N = 1 � 32 N = 3 � 321 N = 1 � 32

Telindus 2300 SHDSL

N = 1 � 32 N = 1 � 32 N = 1 � 32 N = 3 � 321 N = 1 � 32

Page 140: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

126

2 Pair versions:

Remote device

Central device

Crocus SHDSL + serial/router if

Crocus SHDSL + G703 Nx64K

Crocus SHDSL G703 (RP)

Crocus SHDSL + Dual Port if

Telindus 1421 in Pleisio-chronous mode

Crocus SHDSL + serial/router if

N = 2 � 72 (N=even)

N = 2 � 32 (N=even)

N = 1�32 N = 2,4,6 � 32 (N=even)

Crocus SHDSL + G703 Nx64K

N = 2 � 32 (N=even)

N = 1�32 N = 1�32 N = 6 � 321 (N=even)

1. N = 1�31 on serial interface. The time slots on the central G703 destined for the G703 on the remote DP interface have the lowest time slot values.

N = 2,4,6 � 32 (N=even)

Crocus SHDSL G703 (RP)

N = 2 � 32 (N=even)

N = 1�32 N = 1�32 N = 6 � 321 (N=even)

N = 2,4,6 � 32 (N=even)

Crocus SHDSL + G703-Serial DP

N = 6 � 321 (N=even)

Crocus SHDSL Quad

N = 2 � 32 (N=even)

N = 1�32 N = 1�32 N = 6 � 321 (N=even)

N = 2,4,6 � 32 (N=even)

Telindus 2300 SHDSL

N = 2 � 32 (N=even)

N = 1�32 N = 1�32 N = 6 � 321 (N=even)

N = 2,4,6 � 32 (N=even)

Page 141: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

127

6.10 Configuring the interface specific attributes

This section explains the most important interface specific attributes. The following gives an overview of this section:

� 6.10.1 - Configuring the RS530, V35 and V36 interfaces on page 128� 6.10.2 - Configuring the G703 interface on page 129� 6.10.3 - Configuring the Dual Port G703-Serial interface on page 130� 6.10.4 - Configuring the Bridge interface on page 132

Page 142: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

128

6.10.1 Configuring the RS530, V35 and V36 interfaces

crocusShdsl<Tt|Cv>/<dteInterface>/rtsControl

Use the rtsControl attribute to define which device will activate the RTS sig-nal.

Normal operation requires the RTS signal (circuit 105) to be active before the Crocus SHDSL activates its data transfer state, as indicated by the CTS signal (circuit 106). Therefore, make sure the RTS signal is activated either by the application or by the Crocus SHDSL.

If RTS control is set to � the RTS signal is activated by �

Use this setting in case �

external the application. the application has to be in com-mand of the RTS signal.

internal the Crocus SHDSL. the application is not able to activate the RTS signal.

Default:internalRange: external / internal

Page 143: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

129

6.10.2 Configuring the G703 interface

crocusShdsl<Tt|Cv>/g703/coding

Use the coding attribute to set the G703 interface encoding mode. Possible values are:

crocusShdsl<Tt|Cv>/g703/crc4Insertion

This attribute is only present on a G703 Nx64k interface in framed mode.

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:

crocusShdsl<Tt|Cv>/g703/jitterAttenuation

Use the jitterAttenuation attribute to set the buffer depth of the jitter attenuator. The jitter attenuator of the Crocus SHDSL attenuates the clock and data jitter.

The values of the jitterAttenuation attribute are 32 bits and 128 bits. You may wish to limit the buffer size to 32 bits in applications where throughput delay is critical.

Value Description

ami Alternate Mark Inversion is selected. This is a bipolar code with no zero substitu-tion.

hdb3 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.

Value Description

auto In auto mode, CRC-4 insertion is �·

� disabled if the data is unframed,·� enabled if the data is G.704 framed.

disabled CRC-4 insertion is disabled.

enabled CRC-4 insertion is enabled.

Default:hdb3Range: ami / hdb3

Default:autoRange: enumerated, see below

Default:32bitsRange:

Page 144: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

130

6.10.3 Configuring the Dual Port G703-Serial interface

crocusShdsl<Tt|Cv>/dualPort/multiplexingMode

Use the multiplexingMode attribute to determine whether you use both the G703 and serial interface or the G703 interface only.

The multiplexingMode attribute has the following possible values:

crocusShdsl<Tt|Cv>/dualPort/g703/stationClockFallback

Use the stationClockFallback attribute to determine to which clocking mode the Crocus SHDSL has to fall back in case you configured the Crocus SHDSL in station clock mode but the station clock signal is no longer present. You can use this attribute to insure that even when the station clock signal drops, only one master clock is present in the set-up.

The stationClockFallback attribute has the following possible values:

Value Description

multiplexed The Dual Port G703-Serial interface multiplexes two data streams using Time Divi-sion Multiplexing:·

� one stream form the G703 interface,·� one stream from the serial interface.

g703Only Only the data stream from the G703 interface is taken. In this case, the Dual Port G703-Serial interface acts as a regular G703 Nx64k interface. The opposite, i.e. the serial interface only, is not possible.

Remark

If on the G703 part of the Dual Port G703-Serial interface you set the framing attribute to unframed, then the Dual Port G703-Serial interface always works in G703 only mode, independently of the setting of the multiplexingMode attribute.

Value Description

internal The clocking mode falls back to internal clock mode in case the station clock signal is no longer present.

external The clocking mode falls back to external clock mode in case the station clock sig-nal is no longer present.

Default:multiplexedRange: g703Only / multiplexed

Default:internalRange: external / internal

Page 145: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

131

crocusShdsl<Tt|Cv>/dualPort/g703/fallbackClocking

Use the fallbackClocking attribute to determine to which clocking mode the Crocus SHDSL has to fall back in case you configured the Crocus SHDSL in external clock mode but the external clock signal is no longer present. You can use this attribute to insure that even when the external clock signal drops, only one master clock is present in the set-up.

The fallbackClocking attribute has the following possible values:

The external clock mentioned here is the external clock on the G703 interface.

crocusShdsl<Tt|Cv>/dualPort/rs530/x21Conversion

Use the x21Conversion attribute to determine whether you use the Dual Port G703-Serial interface as X.21 interface (enabled) or not (disabled).

You can set the straps of the Dual Port G703-Serial interface in such a way that it operates in RS-530, RS-530A, V.35, V.36 or X.21 mode. When you select another operation mode, you also have to use the correct interface conversion cable. What is more, in case you set the Dual Port G703-Serial interface to X.21 mode you also have to set the x21Conversion attribute enabled. This to insure correct operation when using the Dual Port G703-Serial interface as X.21 interface.

For more information on setting the Dual Port G703-Serial interface in an other mode and for more infor-mation on the interface conversion cables, refer to the manual of the Dual Port G703-Serial interface.

Value Description

internal The clocking mode falls back to internal clock mode in case the external clock sig-nal is no longer present.

slaveReceive The clocking mode falls back to slave receive clock mode in case the external clock signal is no longer present.

Default:internalRange: slaveReceive / internal

Default:disabledRange: enabled / disabled

Page 146: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

132

6.10.4 Configuring the Bridge interface

crocusShdsl<Tt|Cv>/bridge/IanFilter

Use the lanFilter attribute to enable or disable the filter functionality of the bridge. The lanFilter attribute can be set to:

Example of a bridge set-up

The following figure depicts a bridge set-up:

Value Description

enabled The bridge acts as a filter.

Refer to Example of a bridge set-up. Data coming from network 1, will only be let through by the bridge if this data has a destination outside network 1 or if it has a broadcast or multicast address. This means the bridge filters the data and decreases the traffic on the serial line.

disabled The bridge acts as a repeater.

Refer to Example of a bridge set-up. All the data which originates from network 1 will be let through to network 2. Even if the data is not destined for that network.

Default:enabledRange: disabled / enabled

Page 147: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

133

6.11 Configuring the management attributes

This section explains the management attributes of the Crocus SHDSL. 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 in a network. Then it explains the attributes that have an impact on the management of the Cro-cus SHDSL. Finally, it gives some examples of networks and how to configure the Crocus SHDSL to make it accessible for the central management system.

The following gives an overview of this section:

� 6.11.1 - Rules of thumb and remarks concerning management on page 134� 6.11.2 - Using relative or absolute addressing on page 135� 6.11.3 - Selecting the purpose of the control connector on page 136� 6.11.4 - Forwarding management data to the line and control connector on page 137� 6.11.5 - Configuring the management data on the line on page 139� 6.11.6 - Configuring the management data on a G703 interface on page 140� 6.11.7 - Configuring the internal DMM function on page 141� 6.11.8 - Example - management over the line and the control port on page 142� 6.11.9 - Example - management over the line and the E1 interface on page 144

Page 148: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

134

6.11.1 Rules of thumb and remarks concerning management

The following lists some rules of thumb concerning the management of Telindus devices in a network:

� Make sure there is only one path towards the management system. Else you might get unexpected results (e.g. devices that do not answer to polling, answer of several devices at once when polling one device, etc.).

� Once your network starts to become complex on management level (i.e. more than just in-line con-nections as depicted in Relative addressing on page 135), you are advised to use absolute address-ing instead of relative addressing (refer to Absolute addressing on page 135). In practice, it is best to use absolute addressing when you configure one of the attributes listed below as follows:- ctrlPortProtocol attribute to management,- internalDmm attribute to enabled,- g703/saBits to anything else than transparent.

� On a Crocus SHDSL CV, the control port is linked to modem A on management level. This means that when you use the control port to create an extended management link, the management data passes through modem A to the control port.

� On a Crocus SHDSL CV, the attributes ctrlPortProtocol and internalDmm are present in both the contain-ment tree of modem A and modem B. However, changing these attributes on modem B has no effect! You have to change them on modem A in order to have an effect.

� If you use a router interface in the Crocus SHDSL and you want to manage it through the control con-nector or over the line, then you are advised to set the ctrlPortProtocol attribute to management. Else you might be unable to manage the router interface. However, if you use a router interface in a Crocus SHDSL CV and you want to manage it through the high-speed bus of the CN4 card nest (using a management concentrator), then the ctrlPortProtocol attribute may be set to any value.

� If you use a router interface in modem B of a Crocus SHDSL CV and you set the ctrlPortProtocol attribute to management, then the router interface is linked to modem A instead of modem B on man-agement level. In practice, this means that when using e.g. a management concentrator you have to specify modem A instead of modem B in your exit port settings.

� When 10M Router interfaces are inserted in a Crocus SHDSL CV in modem A and B, the ctrlPortPro-tocol attribute should be set to Console, and not to Management.

� Changing the ctrlPortProtocol and internalDmm attribute causes the Crocus SHDSL to reboot.

Page 149: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

135

6.11.2 Using relative or absolute addressing

In order to connect with TMA to the Crocus SHDSL (refer to 4.1 - Starting TMA on the Crocus SHDSL on page 58), you can use two addressing schemes:

Address type Description

relative This type of addressing is meant for a network topology where the devices are con-nected in-line on management level. I.e. with extended management connections* between two devices.

To enable relative addressing, no address has to be specified in the device. In other words, you can leave the cms2Address attribute at its default value, being 0.

Relative addressing

Remark

* An extended management connection is realised with a crossed cable between the control connectors of the two Telindus devices. You also have to set the ctrl-PortProtocol 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 crocusShdsl<Tt|Cv>/management/cms2Address.

Absolute addressing

Page 150: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

136

6.11.3 Selecting the purpose of the control connector

crocusShdsl<Tt|Cv>/management/ctrlPortProtocol

The setting of the ctrlPortProtocol attribute depends on what you connect to the control connector of the Crocus SHDSL. This is explained in the following table:

Pay attention:

� When managing a remote Crocus Router Interface (2M or 10M) module with a Crocus SHDSL CV, following settings can be used:- console: can be used in any case- management: can only be used when the Crocus Router Interface (2M or 10M) module has an abso-

lute address.� When managing a remote Crocus Router Interface (2M or 10M) module with a Crocus SHDSL TT,

the ctrlPortProtocol attribute must always be set to management.

Value Description

management Select this value if you want to connect the control connector of the Crocus SHDSL to �·

� a management concentrator (e.g. the Orchid 1003 LAN or Telindus 1035 Orchid) for management purposes.·

� the control connector of another Telindus device using a crossed cable (i.e. back-to-back) in order to create an extended management link. For more infor-mation on extended management links, refer to Relative addressing on page 135 and Forwarding management information on page 137).

When connecting the control connector of the Crocus SHDSL to a COM port of your computer, you can still open a TMA session on the Crocus SHDSL. 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 to a COM port of your computer in order to manage the Crocus SHDSL locally using TMA, CLI or ATWIN.

Default:consoleRange: management / console

Page 151: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

137

6.11.4 Forwarding management data to the line and control connector

crocusShdsl<Tt|Cv>/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 Tel-indus device.

The forwardTmaToCtrlPort attribute is only present on the TT.

crocusShdsl<Tt|Cv>/forwardTmaToLine

Enables or disables propagation of management information to the line. If forwardTmaToLine is enabled, management information is sent over the line via a dedicated management channel towards the remote Crocus SHDSL.

Forwarding management information

The management system has been designed to provide access not only to the local Crocus SHDSL, but also to all remote Crocus SHDSLs or other Telindus devices in a network.

Default:enabledRange: disabled / enabled

Default:enabledRange: disabled / enabled

Page 152: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

138

� If the attribute forwardTmaToLine is enabled on Crocus SHDSL 1, then management information can be propagated over the line (via a dedicated management channel) from Crocus SHDSL 1 in site A to Crocus SHDSL 2 in site B.

� If the attribute forwardTmaToCtrlPort is enabled on Crocus SHDSL 2 and if the control connector of Cro-cus SHDSL 2 is connected with a crossed cable (i.e. back-to-back) to the control connector of Crocus SHDSL 3, then the management information can also be propagated to Crocus SHDSL 3.

� If the attribute forwardTmaToLine is enabled on Crocus SHDSL 3, then the management information can even be propagated to the remote of Crocus SHDSL 3.

� Etceteras.

Page 153: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

139

6.11.5 Configuring the management data on the line

crocusShdsl<Tt|Cv>/line/management

Use the management attribute to determine whether and which management data is forwarded over the line.

The management attribute has the following possible values:

Value Description

transparent No management data is forwarded over the SHDSL line. The data is passed trans-parently over the line.

o10Management This forwards the proprietary Telindus O10 protocol over the SHDSL line. This allows you to manage the remote SHDSL device (and possibly other Telindus devices connected to the SHDSL device).

pathManagement This forwards path management information over the SHDSL line. This allows you to manage complete paths instead of managing individual devices (i.e. ele-ments).For more information on path management, refer to the TMA Path Man-agement manual.

o10-PathManage-ment

This forwards both the proprietary Telindus O10 protocol as the path management information over the SHDSL line.

Default:o10-PathManagementRange: enumerated, see below

Page 154: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

140

6.11.6 Configuring the management data on a G703 interface

crocusShdsl<Tt|Cv>/g703/saBits

This attribute is only present on a G703 Nx64k interface.

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:

Note that forwarding management data over the G703 interface can be very slow. The speed lies between 200 and 2400 bps.

Value Description

transparent No management data is inserted in the SA-bits. The SA-bits are passed transpar-ently.

o10Management This inserts the proprietary Telindus 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 net-work of Telindus devices.

pathManagement This inserts path management information in the SA-bits. This allows you to man-age complete paths instead of managing individual devices (i.e. elements).

For more information on path management, refer to the Path Management man-ual.

o10-PathManage-ment

This insert both the proprietary Telindus O10 protocol as the path management information in the SA-bits.

Default:PathManagementRange: enumerated, see below

Page 155: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

141

6.11.7 Configuring the internal DMM function

crocusShdslCv/management/internalDmm

This attribute is only present on a CV.

Use the internalDmm attribute on the Card Version to enable or disable the flow of management data between modem A and modem B. The following example tries to clarify this.

Example

The following table shows how the internalDmm attribute influences the accessibility of the Telindus devices in the set-up above:

internalDmm Description

disabled The PC running TMA can only reach Crocus SHDSL TT 1, Crocus SHDSL CV modem A and router interface A.

enabled The PC running TMA can reach any device through the control port of Crocus SHDSL TT 1. You can even reach modem B of the Crocus SHDSL CV, including its router interface and remote counterpart.

Note again that it is best to �·

� set the ctrlPortProtocol attribute to management.·� use absolute addressing.

Default:disabledRange: enabled / disabled

Page 156: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

142

6.11.8 Example - management over the line and the control port

Page 157: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

143

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!

Page 158: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

144

6.11.9 Example - management over the line and the E1 interface

Page 159: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

145

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 sys-tem!

� 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 man-agement system for CV 3. E.g. if you would enable internalDmm, then modem A could contact the man-agement 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.

Page 160: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

146

6.12 Configuring remote power operation

If you want to use remote power operation, then this has to be enabled on the Crocus SHDSL itself. Refer to 2.8 - Remote power operation on page 33.

In order to enable remote power operation on the Crocus SHDSL itself, proceed as follows:

Step Action

1 In the Crocus SHDSL containment tree, select the linePair[ ] object and click on the right mouse button.

⇒A pop-up window appears.

2 In the pop-up window, select Add Child → pwrSource.

⇒The pwrSource object is added under the linePair[ ] object.

Remark

In case of a Crocus SHDSL 2P (2 pair) version, you can add the pwrSource object under the object linePair[1], linePair[2] or both. Remote power is only enabled on those line pairs for which you added an object.

3 In the pwrSource object, the pwrSource attribute is set to enabled by default. If you want to disable remote power operation, then set this attribute to disabled.

Page 161: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

147

6.13 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 pass-word. Furthermore, this section shows you how to enter the passwords in the different maintenance tools.

The following gives an overview of this section:

� 6.13.1 - Adding passwords to the security table on page 148� 6.13.2 - Entering passwords in the different management tools on page 148

Page 162: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

148

6.13.1 Adding passwords to the security table

In order to avoid unauthorised access to the Crocus SHDSL and the network you can create a list of passwords with associated access levels in the security table. Do this using the security attribute. Refer to crocusShdsl<Tt|Cv>/security on page 164.

6.13.2 Entering passwords in the different management tools

Now that you created a (list of) password(s) in the Crocus SHDSL, you have to enter these passwords every time you want to access the Crocus SHDSL with one of the maintenance or management tools.

The following table explains how to enter passwords in the different maintenance or management tools:

� If no passwords are created, everybody has complete access.� If you define at least one password, it is impossible to access the Crocus SHDSL 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 configu-ration.

Maintenance or man-agement tool

How to enter the password?

TMA Enter the password in the Connect� window.

TMA CLI, TMA Ele-ment Management1 and TMA for HP OpenView1

1. Only possible through a management concentrator.

Use the application TmaUserConf.exe to create a TMA user and assign a password to this user. The password should correspond with a password configured in the device.

Refer to the manual of TMA CLI, TMA Element Management or TMA for HP OpenView for more information.

CLI You are prompted to enter the password when the session starts.

ATWIN You are prompted to enter the password when the CLI session starts. Then you can start an ATWIN session.

Web Interface You are prompted to enter the password when the session starts.

SNMP1 Define the password as community string. If no passwords are defined, then you can use any string as community string.

TML Enter the password after the destination file name. Separate password and file name by a �?�.

Example: tml �fsourcefile@destinationfile?pwd

(T)FTP1 Enter the password after the destination file name. Separate password and file name by a �?�.

Example: put sourcefile destinationfile?pwd

Page 163: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

149

6.14 Executing configuration actions

This section shows you how to execute actions on the configuration. The following gives an overview of this section:

� 6.14.1 - What are the different configuration types? on page 150� 6.14.2 - Activating the configuration on page 151� 6.14.3 - Loading the default configuration on page 151� 6.14.4 - Loading the default configuration using a DIP switch on page 152

Page 164: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

150

6.14.1 What are the different configuration types?

This section explains the different configuration types that are present in the Crocus SHDSL.

Which are the configuration types?

Three types of configuration are present in the Crocus SHDSL:

� the non-active configuration� the active configuration� the default configuration.

Explaining the configuration types

When you configure the Crocus SHDSL, the following happens:

Which are the configuration actions?

You can execute the following actions on the configuration:

� crocusShdsl<Tt|Cv>/Activate Configuration on page 166� crocusShdsl<Tt|Cv>/Load Default Configuration on page 166� crocusShdsl<Tt|Cv>/Load Saved Configuration on page 167� crocusShdsl<Tt|Cv>/Cold Boot on page 167

Phase Action Result

1 Connect the computer running the mainte-nance tool to the Crocus SHDSL.

The non-active configuration is displayed on the screen.

2 Modify the non-active configuration. The modifications have no immediate influ-ence on the active configuration currently used by the Crocus SHDSL.

3 Complete the modifications on the non-active configuration.

The non-active configuration has to be acti-vated.

4 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, Easy-Connect terminal, TMA CLI), then exe-cute the Activate Configuration action.

The non-active configuration becomes the active configuration.

Page 165: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

151

6.14.2 Activating the configuration

As explained in section 6.14.1 - What are the different configuration types? on page 150, when you fin-ished configuring the Crocus SHDSL you have to activate the configuration changes you made.

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.

6.14.3 Loading the default configuration

If you install the Crocus SHDSL for the first time, all configuration attributes have their default values. If the Crocus SHDSL has already been configured but you want to start from scratch, then you can revert to the default configuration.

You can load the default configuration using the Load Default Configuration �

� action. Refer to crocusShdsl<Tt|Cv>/Load Default Configuration on page 166. � DIP switch. Refer to 6.14.4 - Loading the default configuration using a DIP switch on page 152.

Page 166: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

152

6.14.4 Loading the default configuration using a DIP switch

The following procedure shows how to load the default configuration using the Load Default Configura-tion DIP switch on the Crocus SHDSL PCB:

Step Action

1 Disconnect the Crocus SHDSL from the power supply. In case of a Crocus SHDSL TT, open the housing as described in 3.1 - DIP switches and straps on page 46.

2 In case of a Crocus SHDSL �

� TT: set DIP switch bank DS1 position 3 to off.� CV modem A: set DIP switch bank DS1 position 3 to off.� CV modem B: set DIP switch bank DS1 position 4 to off.

To locate this DIP switch bank and for the DIP switch setting procedure, refer to Chapter 3 - DIP switches and straps of the Crocus SHDSL on page 45

3 Reconnect the power supply to the Crocus SHDSL.

⇒The Crocus SHDSL 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. Refer to 4.1 - Starting TMA on the Crocus SHDSL on page 58.

2. Execute the Activate Configuration action.

5 Again, disconnect the Crocus SHDSL from the power supply.

6 Reset the appropriate DIP switch to on (see step 2).

7 In case of a Crocus SHDSL TT, properly replace the cover as described in 3.1.4 - Chang-ing DIP switch and strap settings of the TT on page 50 and reconnect the power supply. In case of a Crocus SHDSL CV, gently slide the CV into the CN4 card nest again as described in 3.2.4 - Changing DIP switch and strap settings of the CV on page 56

⇒The Crocus SHDSL reboots in normal operation mode.

Page 167: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

153

6.15 Troubleshooting the Crocus SHDSL

If you experience trouble when installing, configuring or operating the Crocus SHDSL, then check the following:

Check Description

power Is the Crocus SHDSL powered properly?

connections Are all the necessary cables connected to the Crocus SHDSL? Are they connected to the correct connectors of the Crocus SHDSL? Are they connected properly? Did you use the correct cables (straight, crossed, �)?

Refer to 2.6 - Connecting the Crocus SHDSL TT on page 20 and 2.7 - Connecting the Crocus SHDSL Card Version on page 26.

other devices Are the devices that are connected to the Crocus SHDSL working properly (are they powered, are they operational, �)?

LEDs What indicate the LEDs of the Crocus SHDSL? Do they indicate a fault condition?

Refer to 2.10 - Front panel LED indicators on page 40.

messages What messages are displayed in the messages table? This table displays informa-tive and error messages.

Refer to crocusShdsl<Tt|Cv>/messages on page 216

status What do the status attributes of the Crocus SHDSL indicate? What is the status of the different interfaces (up, down, testing, �)?

Refer to 8 - Status attributes on page 209.

performance What do the performance attributes of the Crocus SHDSL 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 9 - Performance attributes on page 259.

alarms What do the alarm attributes of the Crocus SHDSL indicate? What is the alarm sta-tus of the different interfaces (link down, errors, �)?

Refer to 10 - Alarm attributes on page 281.

Page 168: m Crocus SHDSL

Crocus SHDSL Chapter 6

User manual Step-by-step configuration

154

6.16 Crocus SHDSL compatibility with other SHDSL devices

The Crocus SHDSL can be used in combination with other (Telindus) SHDSL devices. The document �Interoperability for Telindus SHDSL products� (PDF) gives an overview of the interoperability.

Page 169: m Crocus SHDSL

Crocus SHDSL

Reference manual

155

Reference manual

Page 170: m Crocus SHDSL

Crocus SHDSL

Reference manual

156

Page 171: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

157

7 Configuration attributes

This chapter discusses the configuration attributes of the Crocus SHDSL. The following gives an over-view of this chapter.

� 7.1 - Configuration attribute overview on page 158� 7.2 - General configuration attributes on page 163� 7.3 - Line configuration attributes on page 168� 7.4 - Line pair configuration attributes on page 179� 7.5 - Remote power configuration attributes on page 181� 7.6 - DTE Interface configuration attributes on page 183� 7.7 - Management configuration attributes on page 205

Page 172: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

158

7.1 Configuration attribute overview

> crocusShdsl<Tt|Cv>sysNamesysContactsysLocationsecurityforwardTmaToCtrlPort1

forwardTmaToLinealarmMaskalarmLevelremoteAlarmMask1

alarmContactHighMask2

alarmContactLowMask2

Action: Activate ConfigurationAction: Load Saved ConfigurationAction: Load Default ConfigurationAction: Cold Boot

1. TT only2. CV only

Page 173: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

159

>> linechannelregiontimingModemode3

minLinePairSpeedretrainstartupMargintestDurationasymmetricPsdeocChanneltxEocMessages3

eocHandlingnumExpectedRepeaterslinkAlarmThresholdsmanagementnamealarmMaskalarmLevelremoteAlarmMask1

alarmContactHighMask2

alarmContactLowMask2

repeaterAlarmMaskrepeaterAlarmLevelrepeaterLinePairAlarmMaskrepeaterLinePairAlarmLevelendAlarmMaskendAlarmLevelendLinePairAlarmMaskendLinePairAlarmLevel

>>> linePair[ ]4

alarmMaskalarmLevelremoteAlarmMask1

alarmContactHighMask2

alarmContactLowMask2

>>>> pwrSource2+5

pwrSourcealarmMaskalarmLevelalarmContactHighMask2

alarmContactLowMask2

3. 2P version only4. in case of a 2P version, two linePair objects are present: linePair[1] and linePair[2]5. not present by default, has to be added

Page 174: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

160

>> rs530, v35, v366

rtscontrolctsdelaynametestsspeedrdlDetectclockingtransmitSampleClockalarmMaskalarmLevelremoteAlarmMask1

speed2P3

serialModealarmContactHighMask2

alarmContactLowMask2

>> x216

namespeedspeed2P3

clockingtransmitSampleClockxSignalrdlDetectalarmMaskalarmLevelremoteAlarmMask1

alarmContactHighMask2

alarmContactLowMask2

6. only present when the corresponding interface is used

Page 175: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

161

>> g7036

nameframing7

timeSlots7

clockingcodingcrc4Insertion7

aisDetectionsqThresholdsqTimejitterAttenuationsaBits7

rdlDetecttests7

alarmMaskalarmLevelremoteAlarmMask1

alarmContactHighMask2

alarmContactLowMask2

>> dualPort6

namerdlDetectmultiplexingMode

>>> g703nameframingtimeSlotsclockingstationClockFallBackfallbackClockingcodingcrc4InsertionaisDetectionsqThresholdsqTimejitterAttenuationsaBitstestsalarmMaskalarmLevelremoteAlarmMask1

alarmContactHighMask2

alarmContactLowMask2

7. G703 Nx64 only

Page 176: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

162

>>> rs530namespeedspeed2P3

clockingtransmitSampleClockrtsControlctsDelayx21ConversiontestsalarmMaskalarmLevelremoteAlarmMask1

alarmContactHighMask2

alarmContactLowMask2

>> bridge6

namespeedspeed2P3

clockingtransmitSampleClocklanFilterrdlDetectalarmMaskalarmLevelremoteAlarmMask1

alarmContactHighMask2

alarmContactLowMask2

>> router6

namespeedspeed2P3

clockingtransmitSampleClockrdlDetectalarmMaskalarmLevelremoteAlarmMask1

alarmContactHighMask2

alarmContactLowMask2

>> managementcms2AddressconsoleNoTrafficTimeOutctrlPortProtocolinternalDmm

Page 177: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

163

7.2 General configuration attributes

This section describes the following configuration attributes:

� crocusShdsl<Tt|Cv>/sysName on page 164� crocusShdsl<Tt|Cv>/sysContact on page 164� crocusShdsl<Tt|Cv>/sysLocation on page 164� crocusShdsl<Tt|Cv>/security on page 164� crocusShdsl<Tt|Cv>/forwardTmaToCtrlPort on page 165� crocusShdsl<Tt|Cv>/forwardTmaToLine on page 165� crocusShdsl<Tt|Cv>/<configurationAlarmAttributes> on page 165

This section describes the following actions:

� crocusShdsl<Tt|Cv>/Activate Configuration on page 166� crocusShdsl<Tt|Cv>/Load Default Configuration on page 166� crocusShdsl<Tt|Cv>/Load Saved Configuration on page 167� crocusShdsl<Tt|Cv>/Cold Boot on page 167

Page 178: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

164

crocusShdsl<Tt|Cv>/sysName

This is a field where you can assign a name to the Crocus SHDSL. The field has a limit of 64 characters.

This is a SNMP MIB2 parameter.

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/sysLocation

This is a field where you can fill in the physical location of the Crocus SHDSL. The field has a limit of 64 characters.

This is a SNMP MIB2 parameter.

crocusShdsl<Tt|Cv>/security

In order to avoid unauthorised access to the network and the Crocus SHDSL, you can create a list of passwords with associated access levels. The security attribute contains the following elements:

Element Description

password The password is a string of maximum 10 characters.

accessRights This attribute represents the access levels assigned to a password. It is a bit string whereof each bit corre-sponds to an access level. The different access levels are:·

� readAccess� writeAccess·� securityAccess

Default:<empty>Range: 0 � 64 characters

Default:<empty>Range: 0 � 64 characters

Default:<empty>Range: 0 � 64 characters

Default:<empty>Range: table, see below

Default:<empty>Range: 0 � 10 characters

Default:11111Range: bit string, see below

Page 179: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

165

The following table shows, for each access level, what you can or can not do:

crocusShdsl<Tt|Cv>/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 Tel-indus device.

The forwardTmaToCtrlPort attribute is only present on the TT.

crocusShdsl<Tt|Cv>/forwardTmaToLine

Enables or disables propagation of management information to the line. If forwardTmaToLine is enabled, management information is sent over the line via a dedicated management channel towards the remote Crocus SHDSL.

For more information, refer to 6.11.4 - Forwarding management data to the line and control connector on page 137.

crocusShdsl<Tt|Cv>/<configurationAlarmAttributes>

For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask, alarmCon-tactHighMask, alarmContactLowMask and on the alarms in general, refer to 10.2 - Introducing the alarm attributes on page 285.

For more information on the alarms of the crocusShdsl<Tt|Cv> object, refer to 10.3 - General alarms on page 292.

Access level Read attributes

Change attributes

Read security attributes1

1. The Crocus SHDSLhas the following security attributes:crocusShdsl<Tt|Cv>/sysNamecrocusShdsl<Tt|Cv>/security

Change secu-rity attributes1

Execute actions2

2. Actions are e.g. Cold Boot, testActivation, retrain, etc.

readAccess yes no no no no

writeAccess yes yes no no yes

securityAccess yes yes yes yes yes

Default:enabledRange: enabled / disabled

Default:enabledRange: enabled / disabled

Page 180: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

166

crocusShdsl<Tt|Cv>/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 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 acti-vate the configuration after you finished configuring the Crocus SHDSL 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 fin-ished configuring the Crocus SHDSL, 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.

crocusShdsl<Tt|Cv>/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 for the first time, all configuration attributes have their default values. If the Crocus SHDSL 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 after executing the Load Default Configuration action to see the new non-active configuration.

Page 181: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

167

crocusShdsl<Tt|Cv>/Load Saved Configuration

If you execute this action, the non-active configuration is overwritten by the active configuration currently used by the Crocus SHDSL.

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 after executing the Load Default Configuration action to see the new non-active configuration.

crocusShdsl<Tt|Cv>/Cold Boot

If you execute this action, the Crocus SHDSL reboots. As a result, the Crocus SHDSL �

� performs a self-test.� checks the software.� reads the saved configuration and restarts program execution.

When use this action?

Use this action, for instance, to activate new application software.

If a Cold Boot is performed on a Crocus SHDSL CV Twin, both modem A and B reboot.

Page 182: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

168

7.3 Line configuration attributes

This section describes the following configuration attributes:

� crocusShdsl<Tt|Cv>/line/channel on page 169� crocusShdsl<Tt|Cv>/line/region on page 169� crocusShdsl<Tt|Cv>/line/timingMode on page 170� crocusShdsl<Tt|Cv>/line/mode on page 171� crocusShdsl<Tt|Cv>/line/minLinePairSpeed on page 171� crocusShdsl<Tt|Cv>/line/retrain on page 171� crocusShdsl<Tt|Cv>/line/startupMargin on page 174� crocusShdsl<Tt|Cv>/line/testDuration on page 174� crocusShdsl<Tt|Cv>/line/asymmetricPsd on page 174� crocusShdsl<Tt|Cv>/line/eocChannel on page 175� crocusShdsl<Tt|Cv>/line/txEocMessages on page 175� crocusShdsl<Tt|Cv>/line/eocHandling on page 175� crocusShdsl<Tt|Cv>/line/numExpectedRepeaters on page 175� crocusShdsl<Tt|Cv>/line/linkAlarmThresholds on page 176� crocusShdsl<Tt|Cv>/line/management on page 178� crocusShdsl<Tt|Cv>/line/name on page 178� crocusShdsl<Tt|Cv>/line/<configurationAlarmAttributes> on page 178

Page 183: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

169

crocusShdsl<Tt|Cv>/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 Crocus SHDSL TT is remote, while that of a Crocus SHDSL CV is cen-tral. 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.

crocusShdsl<Tt|Cv>/line/region

Use the region attribute to set the S-HDSL standard. The region attribute has the following values:

Value Description

annexA The American S-HDSL standard is used.

annexB The European S-HDSL standard is used.

auto The S-HDSL standard is selected automatically.

Default:remote for TT / central for CV

Range: remote / central

Default:autoRange: enumerated, see below

Page 184: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

170

crocusShdsl<Tt|Cv>/line/timingMode

Use the timingMode attribute to set the timing mode. It influences the relation-ship between the line clock and the user interface clock.

Use the timingMode attribute to set the timing mode.

The Crocus SHDSL 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:

� In case of a G703 Nx64k interface, if you set the framing attribute to framed, then the Crocus SHDSL 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 essen-tial. Refer to 6.16 - Crocus SHDSL compatibility with other SHDSL devices on page 154

Value Description

plesiochronous In this mode each SHDSL frame has 0 or 4 stuffing bits to compensate clock devi-ations towards the user interface clock. In this mode, all possible clocking modes can be selected.

synchronous 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.

Default:pleisiochronousRange: pleisiochronous / syn-

chronous

Page 185: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

171

crocusShdsl<Tt|Cv>/line/mode

This attribute is only present on a Crocus SHDSL 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:

crocusShdsl<Tt|Cv>/line/minLinePairSpeed

Use the minLinePairSpeed attribute to determine what the minimum speed on the line pair has to be when the Crocus SHDSL trains.

For more information on the minimum line pair speed, refer to 6.6 - Config-uring the minimum line speed on page 113.

crocusShdsl<Tt|Cv>/line/retrain

Use the retrain attribute to determine when the Crocus SHDSL should retrain.

The retrain criteria

The following criteria determine when to retrain:

If the mode attribute is set to � then use the attribute �

singlePair, speed to configure the user speed.

dualPair, speed2P to configure the user speed.

Criterion Description

no SHDSL frame synchronisation

When the Crocus SHDSL cannot synchronise on the SHDSL framing, it retrains.

SHDSL frame CRC error threshold exceeded

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 retrains.

signal to noise too low

When the signal to noise ratio becomes too low during a certain period of time, the Crocus SHDSL retrains.

Default:dualPairRange: singlePair / dualPair

Default:<opt>Range: 192kbps up to

2048kbps (in steps of 64kbps)

Default:-Range: structure, see below

Page 186: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

172

Configuring the retrain criteria

The retrain structure contains the following elements:

Element Description

enabled Use this element to enable (yes) or disable (no) retraining. So when selecting no, the Crocus SHDSL will never retrain (even not when the line is discon-nected).

errorPersistence-Time

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 retrains.

errorThreshold Use this element to set the amount of CRC errors, per mille, at which the Crocus SHDSL should retrain. If the amount of CRC errors exceeds this value, then the Crocus SHDSL retrains

Remark

The errored SHDSL frames can be monitored using the performance attribute cro-cusShdsl<Tt|Cv>/line/linePair[ ]/performance/codeViolations.

snrThreshold Use this element to set the signal to noise ratio, in dB, which has to be maintained. If the measured signal to noise ratio drops below this value, then the Crocus SHDSL retrains.

If you configured the Crocus SHDSL in �

� a fixed speed, then the Crocus SHDSL tries to retrain again at this fixed speed. If the retrain is successful, then the Crocus SHDSL operates at this fixed speed again. If the retrain is not successful, then the Crocus SHDSL retrains again. If the line conditions are so bad that the fixed speed can no longer be attained, then the Crocus SHDSL keeps retraining.

� auto speed, then the Crocus SHDSL 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.

Default:yesRange: -

Default:10Range: -1 � 30

Default:10Range: 1 � 1000

Default:23Range: 20 � 25

Page 187: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

173

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 retrains at a lower speed (because of the deteriorated line conditions).

� exceeds 27 dB (i.e. the stepupThreshold value), then the Crocus SHDSL retrains at a higher speed (because of the improved line conditions).

stepupMargin Use this element to enable or disable the step-up retrain mechanism.

If you set the stepupMargin to a value other than disabled, then the Crocus SHDSL retrains at a higher speed (because of the improved line conditions) when the cur-rent signal to noise ratio of the line exceeds the sum of �

� the signal to noise ratio at the moment the line entered the data state (i.e. shortly after a successful training cycle)

+

� the stepupMargin value.

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 are in auto speed mode.

Element Description

Default:disabledRange: 3 � 15

Page 188: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

174

crocusShdsl<Tt|Cv>/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 rel-evant in case both central and remote Crocus SHDSL 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.

crocusShdsl<Tt|Cv>/line/testDuration

Use the testDuration attribute to set the time-out period of diagnostic tests.

It is possible to perform diagnostic tests on the Crocus SHDSL (refer to Chapter 13 - Diagnostic tests on page 325). 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. 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).

crocusShdsl<Tt|Cv>/line/asymmetricPsd

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:

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.

Step Action

1 Select the speed for which you want to enable asymmetrical PSD using the speed(2P) attribute:·

� 768 kbps or 1536 kbps in case of Annex A.·� 2048 kbps or 2304 kbps in case of Annex B.

2 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.

3 Enable asymmetrical PSD by setting the asymmetricPsd attribute to enabled.

Default:2dBRange: enumerated, see below

Default:00000d 00h 03m 00sRange: 00000d 00h 00m 01s-

00000d 18h 12m 15s

Default:disabledRange: enabled / disabled

Page 189: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

175

crocusShdsl<Tt|Cv>/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:

crocusShdsl<Tt|Cv>/line/txEocMessages

This attribute is only present on a Crocus SHDSL 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).

crocusShdsl<Tt|Cv>/line/eocHandling

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 6.2 - Configuring EOC handling on page 82.

crocusShdsl<Tt|Cv>/line/numExpectedRepeaters

Use the numExpectedRepeaters attribute to set the number of Crocus SHDSL Repeaters that the Crocus SHDSL can expect to find on the SHDSL line. If the actual number of repeat-ers does not match the number you entered in the numExpectedRepeaters attribute, then the invalidNumRe-peaters alarm is raised.

Value Description

proprietary The checksum is calculated using a proprietary method.

itu-G.991.2 The checksum is calculated using the G.SHDSL standard method.

Default:itu-G.991.2Range: proprietary / itu-

G.991.2

Default:bothPairsRange: pair1 / bothPairs

Default:noneRange: enumerated, see below

Default:0Range: 0 � 8

Page 190: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

176

crocusShdsl<Tt|Cv>/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 Description

lineAttenuation 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 cen-tral 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.

Default:-Range: structure, see below

Page 191: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

177

errSecRatio-Exceeded

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 2 hour time interval. So if the errored seconds ratio �

� exceeds this value within a 2 hour period3, then the errSecRatioExceeded alarm is raised.

� drops below this value within a 2 hour period, then the errSecRatioExceeded alarm is cleared.

sevErrSecRatio-Exceeded

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 2 hour time interval. So if the severely errored seconds ratio �

� exceeds this value within a 2 hour period4, then the sevErrSecRatioExceeded alarm is raised.

� drops below this value within a 2 hour period, then the sevErrSecRatioExceeded alarm is cleared.

bBErrRatio-Exceeded

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 2 hour 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 2 hour period4, then the bBErrRatioExceeded alarm is raised.

� drops below this value within a 2 hour 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 2 hour periods run synchronous with the 2 hour periods of the line/h2Line performance

attribute. Because alarms are raised or cleared within 2 hour periods, there is a delay in the alarm status. For example, suppose that in the first minute of a 2 hour period the errSecRatioEx-ceeded value is exceeded, then the errSecRatioExceeded alarm is raised. The alarm stays on for the remainder of the 2 hour period. The alarm is only cleared if also in the next 2 hour period the errSecRatioExceeded value is not exceeded.

Element Description

Page 192: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

178

crocusShdsl<Tt|Cv>/line/management

Use the management attribute to determine whether and which management data is forwarded over the line.

The management attribute has the following possible values:

crocusShdsl<Tt|Cv>/line/name

Use the name attribute to assign a name to the line.

crocusShdsl<Tt|Cv>/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 repeaterLinePa-

irAlarmLevel).� 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 10.2 - Introducing the alarm attributes on page 285.

� the alarms of the line object, refer to 10.4 - Line alarms on page 295.� the alarms of the repeater object, refer to 10.7 - Repeater and end alarms on page 302.� the alarms of the end object, refer to 10.7 - Repeater and end alarms on page 302.

Value Description

transparent No management data is forwarded over the SHDSL line. The data is passed trans-parently over the line.

o10Management This forwards the proprietary Telindus O10 protocol over the SHDSL line. This allows you to manage the remote SHDSL device (and possibly other Telindus devices connected to the SHDSL device).

pathManagement This forwards path management information over the SHDSL line. This allows you to manage complete paths instead of managing individual devices (i.e. ele-ments).For more information on path management, refer to the TMA Path Man-agement manual.

o10-PathManage-ment

This forwards both the proprietary Telindus O10 protocol as the path management information over the SHDSL line.

Default:o10-PathManagementRange: enumerated, see below

Default:<empty>Range: 0 ... 24 characters

Page 193: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

179

7.4 Line pair configuration attributes

This section describes the following configuration attributes:

� crocusShdsl<Tt|Cv>/line/linePair[ ]/<configurationAlarmAttributes> on page 180

In case of a Crocus SHDSL 2P, two linePair objects are present: linePair [1] and linePair [2].

Page 194: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

180

crocusShdsl<Tt|Cv>/line/linePair[ ]/<configurationAlarmAttributes>

For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask, alarmCon-tactHighMask, alarmContactLowMask and on the alarms in general, refer to 10.2 - Introducing the alarm attributes on page 285.

For more information on the alarms of the linePair[ ] object, refer to 10.5 - Line pair alarms on page 297.

Page 195: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

181

7.5 Remote power configuration attributes

This describes the following configuration attributes:

� crocusShdsl<Tt|Cv>/line/linePair[ ]/pwrSource/pwrSource on page 182� crocusShdsl<Tt|Cv>/line/linePair[ ]/pwrSource/<configurationAlarmAttributes> on page 182

Page 196: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

182

crocusShdsl<Tt|Cv>/line/linePair[ ]/pwrSource/pwrSource

Use the pwrSource attribute to disable or enable remote power operation.

For more information on remote powering, refer to 2.8 - Remote power operation on page 33.

crocusShdsl<Tt|Cv>/line/linePair[ ]/pwrSource/<configurationAlarmAttributes>

For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask, alarmCon-tactHighMask, alarmContactLowMask and on the alarms in general, refer to 10.2 - Introducing the alarm attributes on page 285.

For more information on the alarms of the pwrSource object, refer to 10.6 - Remote power alarms on page 300.

Default:enabledRange: disabled / enabled

Page 197: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

183

7.6 DTE Interface configuration attributes

This section discusses the configuration attributes of the different DTE interfaces. Because some of the interface configuration attributes are present on every interface, they are discussed in a general section. All other sections discuss the interface specific attributes.

The following gives an overview of this section.

� 7.6.1 - RS530, V35 and V36 interface configuration attributes on page 184� 7.6.2 - X21 interface configuration attributes on page 188� 7.6.3 - G703 interface configuration attributes on page 191� 7.6.4 - Dual Port G703-Serial interface configuration attributes on page 196� 7.6.5 - Bridge interface configuration attributes on page 199� 7.6.6 - Router interface configuration attributes on page 202

Page 198: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

184

7.6.1 RS530, V35 and V36 interface configuration attributes

This section describes the following configuration attributes:

� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/rtsControl on page 185� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ctsDelay on page 185� -crocusShdsl<Tt|Cv>/<rs530/v35/v36>/tests on page 186� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/name on page 186� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/speed on page 186� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/speed2P on page 186� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/clocking on page 187� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/transmitSampleClock on page 187� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/rdlDetect on page 187� crocusShdsl<Tt|Cv>/<rs530/v35/v36>serialMode on page 187� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/<configurationAlarmAttributes> on page 187

Page 199: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

185

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/rtsControl

Use the rtsControl attribute to define which device will activate the RTS signal.

Normal operation requires the RTS signal (circuit 105) to be active before the Crocus SHDSL activates its data transfer state, as indicated by the CTS signal (circuit 106). Therefore, make sure the RTS signal is activated either by the application or by the Crocus SHDSL.

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ctsDelay

Use the cTSDelay attribute to define the delay between the active edge of the incoming RTS signal and the active edge of the outgoing CTS signal.

The delays that can be selected are: 0 ms, 4 ms, 16 ms and 64 ms.

Between the moment the RTS signal drops and the moment the CTS signal drops, no delay is provided.

If RTS control is set to� the RTS signal is activated by�

Use this setting in case�

external the application. the application has to be in com-mand of the RTS signal.

internal the Crocus SHDSL. the application is not able to activate the RTS signal.

If RTS control is set to�

then�

external a delay is provided between:

� the moment the active edge of the RTS signal comes in� the moment the active edge of the outgoing CTS signal is generated.

internal no delay is provided. The CTS signal is always on.

Default:internalRange: external/internal

Default:0 msRange: enumerated, see below

Page 200: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

186

-crocusShdsl<Tt|Cv>/<rs530/v35/v36>/tests

Use the tests attribute to enable or disable the interface tests.

The interface tests of the Crocus SHDSL are useful to trace possible problems. These interface tests are initiated by the application via the interface. If these tests are not supported by the application, it is possible that an undesired test is activated resulting in a disturbance of the data transfer. Therefore, they are disabled by default.

The available interface tests are:

� interfaceAl: interface Analogue Loop� interfaceRdl: interface Remote Digital Loop

For more information on these tests, refer to Chapter 13 - Diagnostic tests on page 325.

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/name

Use the name attribute to assign an administrative name to the DTE inter-face.

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/speed

Use the speed attribute to set the speed of the DTE interface.

For more information, refer to 6.5 - Configuring the user speed on page 108.

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/speed2P

This attribute is only present on a Crocus SHDSL 2P (2 pair) version. Use the speed2P attribute to set the speed of the DTE interface in case of a Crocus SHDSL 2P (if it is truly in 2 pair operation).

Important remark

� In case of a Crocus SHDSL 2P (2 pair) version, set the speed2P attribute of either the central or remote Crocus SHDSL to auto, but not of both. Else the 2 line pairs could train at a different speed which is not allowed.

� In case you use a G703 interface in one Crocus SHDSL and a serial interface in 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.

� If both the central8 and remote9 Crocus SHDSL are configured in external clocking mode and an external clock signal is present, then it is the central Crocus SHDSL modem who determines the speed on which the line trains.

For more information, refer to 6.5 - Configuring the user speed on page 108.

8. The central device is the device on which the channel attribute is set to central.9. The remote device is the device on which the channel attribute is set to remote.

Default:disabledRange: enabled / disabled

Default:<empty>Range: 0 � 64 characters

Default:autoRange: enumerated, see below

Default:autoRange: enumerated, see below

Page 201: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

187

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/clocking

Use the clocking attribute to select a clocking mode.

For more information, refer to 6.4 - Configuring the clocking mode on page 89.

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/transmitSampleClock

Use the transmitSampleClock attribute to set the transmit sample clock to normal or invert.

In case the clocking mode is set to an alternative mode, then inverting the sample clock may solve the possible problem of too long delays on the transmit data in comparison to the transmit clock.

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/rdlDetect

When set to disabled, this attribute prevents that a digital loop can be per-formed by a remote Crocus SHDSL on the local Crocus SHDSL.

When rdlDetect is disabled, and a remote Crocus SHDSL initiates an RDL test, the local Crocus SHDSL will not go in digital loop. However, the DTE interface of the remote Crocus SHDSL will be clamped and data transfer is interrupted.

crocusShdsl<Tt|Cv>/<rs530/v35/v36>serialMode

The serial interface signals support different serial interface types.

Use the serialMode attribute to select the serial interface type. Possible values are:

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/<configurationAlarmAttributes>

For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask, alarmCon-tactHighMask, alarmContactLowMask and on the alarms in general, refer to 10.2 - Introducing the alarm attributes on page 285.

For more information on the alarms of the <dteInterface> object, refer to 10.8 - Interface alarms on page 306.

Value Description

rs530 The serial interface type is rs530.

rs530a The serial interface type is rs530a.

v35 The serial interface type is v35.

v35Interim The serial interface type is v35Interim.

v36-v10 The serial interface type is v36-v10.

v36-v11 The serial interface type is v36-v11.

x21 The serial interface type is x21.

x21NotTerminated The serial interface type is x21NotTerminated.

rs232 The serial interface type is rs232.

Default:autoRange: enumerated, see below

Default:normalRange: invert / normal

Default:enabledRange: disabled / enabled

Default:rs530Range: enumerated, see below

Page 202: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

188

7.6.2 X21 interface configuration attributes

This section describes the following configuration attributes:

� crocusShdsl<Tt|Cv>/x21/xSignal on page 189� crocusShdsl<Tt|Cv>/x21/name on page 189� crocusShdsl<Tt|Cv>/x21/speed on page 189� crocusShdsl<Tt|Cv>/x21/speed2P on page 190� crocusShdsl<Tt|Cv>/x21/clocking on page 190� crocusShdsl<Tt|Cv>/x21/transmitSampleClock on page 190� crocusShdsl<Tt|Cv>/x21/rdlDetect on page 190� crocusShdsl<Tt|Cv>/x21/<configurationAlarmAttributes> on page 190

Page 203: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

189

crocusShdsl<Tt|Cv>/x21/xSignal

Use this attribute to determine whether the X clock is taken into account or not.

crocusShdsl<Tt|Cv>/x21/name

Use the name attribute to assign an administrative name to the DTE inter-face.

crocusShdsl<Tt|Cv>/x21/speed

Use the speed attribute to set the speed of the DTE interface.

For more information, refer to 6.5 - Configuring the user speed on page 108.

If the X clock is � and it is � in your set-up, then set the xSignal attribute to �

present, used (i.e. the clocking mode is set to external or external loop-back)

inUse.

present, not used (i.e. the clocking mode is set to internal or slave receive)

ignore to make sure that the X clock signal is not used.

not present, ignore to make sure that possible interference does not give the false impression that an X clock signal is present.

Default:inUseRange: ignore / inUse

Default:<empty>Range: 0 � 64 characters

Default:autoRange: enumerated, see below

Page 204: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

190

crocusShdsl<Tt|Cv>/x21/speed2P

This attribute is only present on a Crocus SHDSL 2P (2 pair) version. Use the speed2P attribute to set the speed of the DTE interface in case of a Crocus SHDSL 2P (if it is truly in 2 pair operation).

Important remark

� In case of a Crocus SHDSL 2P (2 pair) version, set the speed2P attribute of either the central or remote Crocus SHDSL to auto, but not of both. Else the 2 line pairs could train at a different speed which is not allowed.

� 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.

� If both the central10 and remote11 Crocus SHDSL are configured in external clocking mode and an external clock signal is present, then it is the central Crocus SHDSL modem who determines the speed on which the line trains.

For more information, refer to 6.5 - Configuring the user speed on page 108.

crocusShdsl<Tt|Cv>/x21/clocking

Use the clocking attribute to select a clocking mode.

For more information, refer to 6.4 - Configuring the clocking mode on page 89.

crocusShdsl<Tt|Cv>/x21/transmitSampleClock

Use the transmitSampleClock attribute to set the transmit sample clock to normal or invert.

In case the clocking mode is set to an alternative mode, then inverting the sample clock may solve the possible problem of too long delays on the transmit data in comparison to the transmit clock.

crocusShdsl<Tt|Cv>/x21/rdlDetect

When set to disabled, this attribute prevents that a digital loop can be per-formed by a remote Crocus SHDSL on the local Crocus SHDSL.

When rdlDetect is disabled, and a remote Crocus SHDSL initiates an RDL test, the local Crocus SHDSL will not go in digital loop. However, the DTE interface of the remote Crocus SHDSL will be clamped and data transfer is interrupted.

crocusShdsl<Tt|Cv>/x21/<configurationAlarmAttributes>

For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask, alarmCon-tactHighMask, alarmContactLowMask and on the alarms in general, refer to 10.2 - Introducing the alarm attributes on page 285.

For more information on the alarms of the <dteInterface> object, refer to 10.8 - Interface alarms on page 306.

10.The central device is the device on which the channel attribute is set to central.11.The remote device is the device on which the channel attribute is set to remote.

Default:autoRange: enumerated, see below

Default:autoRange: enumerated, see below

Default:normalRange: invert / normal

Default:enabledRange: disabled / enabled

Page 205: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

191

7.6.3 G703 interface configuration attributes

This section describes the following configuration attributes:

� crocusShdsl<Tt|Cv>/g703/framing on page 192� crocusShdsl<Tt|Cv>/g703/timeSlots on page 192� crocusShdsl<Tt|Cv>/g703/coding on page 192� crocusShdsl<Tt|Cv>/g703/crc4Insertion on page 193� crocusShdsl<Tt|Cv>/g703/aisDetection on page 193� crocusShdsl<Tt|Cv>/g703/sqThreshold on page 193� crocusShdsl<Tt|Cv>/g703/sqTime on page 193� crocusShdsl<Tt|Cv>/g703/jitterAttenuation on page 193� crocusShdsl<Tt|Cv>/g703/saBits on page 194� crocusShdsl<Tt|Cv>/g703/tests on page 194� crocusShdsl<Tt|Cv>/g703/name on page 194� crocusShdsl<Tt|Cv>/g703/clocking on page 195� crocusShdsl<Tt|Cv>/g703/rdlDetect on page 195� crocusShdsl<Tt|Cv>/g703/<configurationAlarmAttributes> on page 195

Page 206: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

192

crocusShdsl<Tt|Cv>/g703/framing

This attribute is only present on a G703 Nx64k interface.

Use the framing attribute to select between unframed or framed mode:

For more information, refer to 6.7 - Configuring framing and time slots on page 118.

crocusShdsl<Tt|Cv>/g703/timeSlots

This attribute is only present on a G703 Nx64k interface.

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 when using a G703 Nx64k interface in the local Crocus SHDSL and a non-G703 interface in the remote Crocus SHDSL.

� 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 6.7 - Configuring framing and time slots on page 118.

crocusShdsl<Tt|Cv>/g703/coding

Use the coding attribute to set the G703 interface encoding mode. Possible values are:

Value Description

unframed In unframed (or transparent) mode, a 2 Mbps data stream is sent transparently over the line.

framed In framed (G.704 framing) mode, 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.

Value Description

ami Alternate Mark Inversion is selected. This is a bipolar code with no zero substitu-tion.

hdb3 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:unframedRange: framed / unframed

Default:ts0=1, other ts=0Range: enumerated, see below

Default:hdb3Range: ami / hdb3

Page 207: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

193

crocusShdsl<Tt|Cv>/g703/crc4Insertion

This attribute is only present on a G703 Nx64k interface.

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:

crocusShdsl<Tt|Cv>/g703/aisDetection

Use this attribute to enable or disable the detection of the Alarm Indication Sig-nal.

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/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.

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.

crocusShdsl<Tt|Cv>/g703/jitterAttenuation

Use the jitterAttenuation attribute to set the buffer depth of the jitter attenuator. The jitter attenuator of the Crocus SHDSL attenuates the clock and data jitter.

The values of the jitterAttenuation attribute are 32 bits and 128 bits. You may wish to limit the buffer size to 32 bits in applications where throughput delay is critical.

Value Description

auto In auto mode, CRC-4 insertion is �

� disabled if the data is unframed,� enabled if the data is G.704 framed.

disabled CRC-4 insertion is disabled.

enabled CRC-4 insertion is enabled.

Default:autoRange: enumerated, see below

Default:enabledRange: enabled / disabled

Default:10Range: 0 � 65535

Default:00000d 00h 01m 00sRange: 00000d 00h 00m 00s -

24855d 03h 14m 07s

Default:32 bitsRange: 128 bits / 32 bits

Page 208: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

194

crocusShdsl<Tt|Cv>/g703/saBits

This attribute is only present on a G703 Nx64k interface.

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:

Note that forwarding management data over the G703 interface can be very slow. The speed lies between 200 and 2400 bps.

crocusShdsl<Tt|Cv>/g703/tests

This attribute is only present on a G703 Nx64k interface.

Use the tests attribute to enable or disable the interface tests.

The interface tests of the Crocus SHDSL are useful to trace possible problems. These interface tests are initiated by the application via the interface. If these tests are not supported by the application, it is possible that an undesired test is activated resulting in a disturbance of the data transfer. Therefore, they are disabled by default.

The available interface tests are:

� interfaceAl: interface Analogue Loop� interfaceRdl: interface Remote Digital Loop

For more information on these tests, refer to Chapter 13 - Diagnostic tests on page 325.

crocusShdsl<Tt|Cv>/g703/name

Use the name attribute to assign an administrative name to the DTE inter-face.

Value Description

transparent No management data is inserted in the SA-bits. The SA-bits are passed transpar-ently.

o10Management This inserts the proprietary Telindus 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 net-work of Telindus devices.

pathManagement This inserts path management information in the SA-bits. This allows you to man-age complete paths instead of managing individual devices (i.e. elements).For more information on path management, refer to the Path Management manual.

o10-PathManage-ment

This insert both the proprietary Telindus O10 protocol as the path management information in the SA-bits.

Default:pathManagementRange: enumerated, see below

Default:disabledRange: enabled / disabled

Default:<empty>Range: 0 � 64 characters

Page 209: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

195

crocusShdsl<Tt|Cv>/g703/clocking

Use the clocking attribute to select a clocking mode.

For more information, refer to 6.4 - Configuring the clocking mode on page 89.

crocusShdsl<Tt|Cv>/g703/rdlDetect

When set to disabled, this attribute prevents that a digital loop can be per-formed by a remote Crocus SHDSL on the local Crocus SHDSL.

When rdlDetect is disabled, and a remote Crocus SHDSL initiates an RDL test, the local Crocus SHDSL will not go in digital loop. However, the DTE interface of the remote Crocus SHDSL will be clamped and data transfer is interrupted.

crocusShdsl<Tt|Cv>/g703/<configurationAlarmAttributes>

For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask, alarmCon-tactHighMask, alarmContactLowMask and on the alarms in general, refer to 10.2 - Introducing the alarm attributes on page 285.

For more information on the alarms of the <dteInterface> object, refer to 10.8 - Interface alarms on page 306.

Default:autoRange: enumerated, see below

Default:enabledRange: disabled / enabled

Page 210: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

196

7.6.4 Dual Port G703-Serial interface configuration attributes

This section describes the following configuration attributes:

� crocusShdsl<Tt|Cv>/dualPort/multiplexingMode on page 197� crocusShdsl<Tt|Cv>/dualPort/g703/stationClockFallback on page 197� crocusShdsl<Tt|Cv>/dualPort/g703/fallbackClocking on page 197� crocusShdsl<Tt|Cv>/dualPort/rs530/x21Conversion on page 198

This section lists the configuration attributes that are specific for the Dual Port G703-Serial interface. All other attributes of the Dual Port G703-Serial interface are the same as those of the G703 (Nx64k) and RS530 interface. Therefore, for more information on these attributes, refer to �

� 7.6.1 - RS530, V35 and V36 interface configuration attributes on page 184� 7.6.3 - G703 interface configuration attributes on page 191.

There are also some specific remarks concerning clocking, framing, speed and time slot selection on the Dual Port G703-Serial interface. For more information on �

� clocking, refer to 6.4.6 - Special points of interest concerning clocking on some interfaces on page 95.� framing, refer to 6.8 - Configuring the user speed and time slots on the Dual Port G703-Serial inter-

face on page 122.� speed and time slot selection, refer to 6.8 - Configuring the user speed and time slots on the Dual

Port G703-Serial interface on page 122.

Page 211: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

197

crocusShdsl<Tt|Cv>/dualPort/multiplexingMode

Use the multiplexingMode attribute to determine whether you use both the G703 and serial interface or the G703 interface only.

The multiplexingMode attribute has the following possible values:

crocusShdsl<Tt|Cv>/dualPort/g703/stationClockFallback

Use the stationClockFallback attribute to determine to which clocking mode the Crocus SHDSL has to fall back in case you configured the Crocus SHDSL in station clock mode but the station clock signal is no longer present. You can use this attribute to insure that even when the station clock signal drops, only one master clock is present in the set-up.

The stationClockFallback attribute has the following possible values:

crocusShdsl<Tt|Cv>/dualPort/g703/fallbackClocking

Use the fallbackClocking attribute to determine to which clocking mode the Crocus SHDSL has to fall back in case you configured the Crocus SHDSL in external clock mode but the external clock signal is no longer present. You can use this attribute to insure that even when the external clock signal drops, only one master clock is present in the set-up.

Value Description

multiplexed The Dual Port G703-Serial interface multiplexes two data streams using Time Divi-sion Multiplexing:

� one stream form the G703 interface,� one stream from the serial interface.

g703Only Only the data stream from the G703 interface is taken. In this case, the Dual Port G703-Serial interface acts as a regular G703 Nx64k interface. The opposite, i.e. the serial interface only, is not possible.

Remark

If on the G703 part of the Dual Port G703-Serial interface you set the framing attribute to unframed, then the Dual Port G703-Serial interface always works in G703 only mode, independently of the setting of the multiplexingMode attribute.

Value Description

internal The clocking mode falls back to internal clock mode in case the station clock signal is no longer present.

external The clocking mode falls back to external clock mode in case the station clock sig-nal is no longer present.

Default:multiplexedRange: enumerated, see below

Default:internalRange: external / internal

Default:internalRange: slaveReceive / internal

Page 212: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

198

The fallbackClocking attribute has the following possible values:

crocusShdsl<Tt|Cv>/dualPort/rs530/x21Conversion

Use the x21Conversion attribute to determine whether you use the Dual Port G703-Serial interface as X.21 interface (enabled) or not (disabled).

You can set the straps of the Dual Port G703-Serial interface in such a way that it operates in RS-530, RS-530A, V.35, V.36 or X.21 mode. When you select another operation mode, you also have to use the correct interface conversion cable. What is more, in case you set the Dual Port G703-Serial interface to X.21 mode you also have to set the x21Conversion attribute enabled. This to insure correct operation when using the Dual Port G703-Serial interface as X.21 interface.

For more information on setting the Dual Port G703-Serial interface in an other mode and for more infor-mation on the interface conversion cables, refer to the manual of the Dual Port G703-Serial interface.

Value Description

internal The clocking mode falls back to internal clock mode in case the external clock sig-nal is no longer present.

slaveReceive The clocking mode falls back to slave receive clock mode in case the external clock signal is no longer present.

Default:disabledRange: enabled / disabled

Page 213: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

199

7.6.5 Bridge interface configuration attributes

This describes the following configuration attributes:

� crocusShdsl<Tt|Cv>/bridge/IanFilter on page 200� crocusShdsl<Tt|Cv>/router/name on page 203� crocusShdsl<Tt|Cv>/router/speed on page 203� crocusShdsl<Tt|Cv>/router/speed2P on page 203� crocusShdsl<Tt|Cv>>/router/clocking on page 203� crocusShdsl<Tt|Cv>/router/transmitSampleClock on page 203� crocusShdsl<Tt|Cv>/router/rdlDetect on page 204� crocusShdsl<Tt|Cv>/router/<configurationAlarmAttributes> on page 204

Page 214: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

200

crocusShdsl<Tt|Cv>/bridge/IanFilter

Use the lanFilter attribute to enable or disable the filter functionality of the bridge. The lanFilter attribute can be set to:

crocusShdsl<Tt|Cv>/bridge/name

Use the name attribute to assign an administrative name to the DTE inter-face.

crocusShdsl<Tt|Cv>/bridge/speed

Use the speed attribute to set the speed of the DTE interface.

For more information, refer to 6.5 - Configuring the user speed on page 108.

crocusShdsl<Tt|Cv>/bridge/speed2P

This attribute is only present on a Crocus SHDSL 2P (2 pair) version. Use the speed2P attribute to set the speed of the DTE interface in case of a Crocus SHDSL 2P (if it is truly in 2 pair operation).

Important remark

� In case of a Crocus SHDSL 2P (2 pair) version, set the speed2P attribute of either the central or remote Crocus SHDSL to auto, but not of both. Else the 2 line pairs could train at a different speed which is not allowed.

� 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.

� If both the central12 and remote13 Crocus SHDSL are configured in external clocking mode and an external clock signal is present, then it is the central Crocus SHDSL modem who determines the speed on which the line trains.

For more information, refer to 6.5 - Configuring the user speed on page 108.

Value Description

enabled The bridge acts as a filter.

Refer to Example of a bridge set-up on page 132. Data coming from network 1, will only be let through by the bridge if this data has a destination outside network 1 or if it has a broadcast or multicast address. This means the bridge filters the data and decreases the traffic on the serial line.

disabled The bridge acts as a repeater.

Refer to Example of a bridge set-up on page 132. All the data which originates from network 1 will be let through to network 2. Even if the data is not destined for that network.

12.The central device is the device on which the channel attribute is set to central.13.The remote device is the device on which the channel attribute is set to remote.

Default:enabledRange: disabled / enabled

Default:<empty>Range: 0 � 64 characters

Default:autoRange: enumerated, see below

Default:autoRange: enumerated, see below

Page 215: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

201

crocusShdsl<Tt|Cv>>/bridge/clocking

Use the clocking attribute to select a clocking mode.

For more information, refer to 6.4 - Configuring the clocking mode on page 89.

crocusShdsl<Tt|Cv>/bridge/transmitSampleClock

Use the transmitSampleClock attribute to set the transmit sample clock to normal or invert.

In case the clocking mode is set to an alternative mode, then inverting the sample clock may solve the possible problem of too long delays on the transmit data in comparison to the transmit clock.

crocusShdsl<Tt|Cv>/bridge/rdlDetect

When set to disabled, this attribute prevents that a digital loop can be per-formed by a remote Crocus SHDSL on the local Crocus SHDSL.

When rdlDetect is disabled, and a remote Crocus SHDSL initiates an RDL test, the local Crocus SHDSL will not go in digital loop. However, the DTE interface of the remote Crocus SHDSL will be clamped and data transfer is interrupted.

crocusShdsl<Tt|Cv>/bridge/<configurationAlarmAttributes>

For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask, alarmCon-tactHighMask, alarmContactLowMask and on the alarms in general, refer to 10.2 - Introducing the alarm attributes on page 285.

For more information on the alarms of the <dteInterface> object, refer to 10.8 - Interface alarms on page 306.

Default:autoRange: enumerated, see below

Default:normalRange: invert / normal

Default:enabledRange: disabled / enabled

Page 216: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

202

7.6.6 Router interface configuration attributes

This describes the following configuration attributes:

� crocusShdsl<Tt|Cv>/router/name on page 203� crocusShdsl<Tt|Cv>/router/speed on page 203� crocusShdsl<Tt|Cv>/router/speed2P on page 203� crocusShdsl<Tt|Cv>>/router/clocking on page 203� crocusShdsl<Tt|Cv>/router/transmitSampleClock on page 203� crocusShdsl<Tt|Cv>/router/rdlDetect on page 204� crocusShdsl<Tt|Cv>/router/<configurationAlarmAttributes> on page 204

Page 217: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

203

crocusShdsl<Tt|Cv>/router/name

Use the name attribute to assign an administrative name to the DTE inter-face.

crocusShdsl<Tt|Cv>/router/speed

Use the speed attribute to set the speed of the DTE interface.

For more information, refer to 6.5 - Configuring the user speed on page 108.

crocusShdsl<Tt|Cv>/router/speed2P

This attribute is only present on a Crocus SHDSL 2P (2 pair) version. Use the speed2P attribute to set the speed of the DTE interface in case of a Crocus SHDSL 2P (if it is truly in 2 pair operation).

Important remark

� In case of a Crocus SHDSL 2P (2 pair) version, set the speed2P attribute of either the central or remote Crocus SHDSL to auto, but not of both. Else the 2 line pairs could train at a different speed which is not allowed.

� 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.

� If both the central14 and remote15 Crocus SHDSL are configured in external clocking mode and an external clock signal is present, then it is the central Crocus SHDSL modem who determines the speed on which the line trains.

For more information, refer to 6.5 - Configuring the user speed on page 108.

crocusShdsl<Tt|Cv>>/router/clocking

Use the clocking attribute to select a clocking mode.

For more information, refer to 6.4 - Configuring the clocking mode on page 89.

crocusShdsl<Tt|Cv>/router/transmitSampleClock

Use the transmitSampleClock attribute to set the transmit sample clock to normal or invert.

In case the clocking mode is set to an alternative mode, then inverting the sample clock may solve the possible problem of too long delays on the transmit data in comparison to the transmit clock.

14.The central device is the device on which the channel attribute is set to central.15.The remote device is the device on which the channel attribute is set to remote.

Default:<empty>Range: 0 � 64 characters

Default:autoRange: enumerated, see below

Default:autoRange: enumerated, see below

Default:autoRange: enumerated, see below

Default:normalRange: invert / normal

Page 218: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

204

crocusShdsl<Tt|Cv>/router/rdlDetect

When set to disabled, this attribute prevents that a digital loop can be per-formed by a remote Crocus SHDSL on the local Crocus SHDSL.

When rdlDetect is disabled, and a remote Crocus SHDSL initiates an RDL test, the local Crocus SHDSL will not go in digital loop. However, the DTE interface of the remote Crocus SHDSL will be clamped and data transfer is interrupted.

crocusShdsl<Tt|Cv>/router/<configurationAlarmAttributes>

For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask, alarmCon-tactHighMask, alarmContactLowMask and on the alarms in general, refer to 10.2 - Introducing the alarm attributes on page 285.

For more information on the alarms of the <dteInterface> object, refer to 10.8 - Interface alarms on page 306.

Default:enabledRange: disabled / enabled

Page 219: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

205

7.7 Management configuration attributes

This section describes the following configuration attributes:

� crocusShdsl<Tt|Cv>/management/cms2Address on page 206� crocusShdsl<Tt|Cv>/management/consoleNoTrafficTimeOut on page 206� crocusShdsl<Tt|Cv>/management/ctrlPortProtocol on page 207� crocusShdsl<Tt|Cv>/management/internalDmm on page 208

Page 220: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

206

crocusShdsl<Tt|Cv>/management/cms2Address

Use the cms2Address attribute to configure an absolute address in the Crocus SHDSL. The absolute addressing range goes from 1 up to 65535. This address can then be used to con-nect with TMA. Refer to 4.1 - Starting TMA on the Crocus SHDSL on page 58.

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 6.11.2 - Using relative or absolute addressing on page 135 for more information on relative and absolute addressing.

crocusShdsl<Tt|Cv>/management/consoleNoTrafficTimeOut

You can open a TMA, CLI or ATWIN session on the Crocus SHDSL 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 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.

Default:0Range: 1 � 65535

Default:00000d 00h 30m00sRange: 00000d 00h 30m �

24855d 03h 14m 07s

Page 221: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

207

crocusShdsl<Tt|Cv>/management/ctrlPortProtocol

The setting of the ctrlPortProtocol attribute depends on what you connect to the control connector of the Crocus SHDSL. This is explained in the following table:

Pay attention:

� When managing a remote Crocus Router Interface (2M or 10M) module with a Crocus SHDSL CV, following settings can be used:- console: can be used in any case- management: can only be used when the Crocus Router Interface (2M or 10M) module has an abso-

lute address.� When managing a remote Crocus Router Interface (2M or 10M) module with a Crocus SHDSL TT,

the ctrlPortProtocol attribute must always be set to management.

Value Description

management Select this value if you want to connect the control connector of the Crocus SHDSL to �

� a management concentrator (e.g. the Orchid 1003 LAN or Telindus 1035 Orchid) for management purposes.

� the control connector of another Telindus device using a crossed cable (i.e. back-to-back) in order to create an extended management link. For more infor-mation on extended management links, refer to Relative addressing on page 135 and Forwarding management information on page 137).

When connecting the control connector of the Crocus SHDSL to a COM port of your computer, you can still open a TMA session on the Crocus SHDSL. 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 to a COM port of your computer in order to manage the Crocus SHDSL locally using TMA, CLI or ATWIN.

Default:consoleRange: management / console

Page 222: m Crocus SHDSL

Crocus SHDSL Chapter 7

Reference manual Configuration attributes

208

crocusShdsl<Tt|Cv>/management/internalDmm

This attribute is only present on a CV.

Use the internalDmm attribute on the Card Version to enable or disable the flow of management data between modem A and modem B. The following example tries to clarify this.

Example

The following table shows how the internalDmm attribute influences the accessibility of the Telindus devices in the set-up above:

internalDmm Description

disabled The PC running TMA can only reach Crocus SHDSL TT 1, Crocus SHDSL CV modem A and router interface A.

enabled The PC running TMA can reach any device through the control port of Crocus SHDSL TT 1. You can even reach modem B of the Crocus SHDSL CV, including its router interface and remote counterpart.

Note again that it is best to �

� set the ctrlPortProtocol attribute to management.� use absolute addressing.

Default:disabledRange: enabled / disabled

Page 223: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

209

8 Status attributes

This chapter discusses the status attributes of the Crocus SHDSL. The following gives an overview of this chapter.

� 8.1 - Status attribute overview on page 210� 8.2 - General status attributes on page 215� 8.3 - Line status attributes on page 219� 8.4 - Line pair status attributes on page 227� 8.5 - Remote power status attributes on page 230� 8.6 - Repeater and end status attributes on page 232� 8.7 - DTE Interface status attributes on page 237� 8.8 - Management status attributes on page 255� 8.9 - Operating system status on page 257

Page 224: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

210

8.1 Status attribute overview

> crocusShdsl<Tt|Cv>sysDescrsysObjectIDsysUpTimesysServicesmessagesdeviceIdconfigurationSavingbootVersionloaderVersionflash1VersionAction: Cold Boot

>> lineifDescrifTypeifSpeedifOperStatusminLinePairSpeedmaxLinePairSpeedframerTypetestTypetestOriginatortestStatusmaxSpeedSearchmaxSpeedResulterrorCountregionasymmetricPsdlinePairsSwapped1

numDiscoveredRepeaterseocAlarmThresholdsAction: testActivationAction: clearErrorCounterAction: maximumSpeedSearch

1. 2P version only

Page 225: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

211

>>> linePair[ ]2

ifSpeedifOperStatusstatustimeSinceLastRetraintransmitPowerlineAttenuationsignalNoisestepupThresholdactualBitRate

>>>> remPowerSource[ ]3

versionstatus

>> repeater[ ]4

vendorIdvendorModelvendorSerialvendorSoftVersioneocSoftVersionshdslVersioneocStateeocAlarmThresholdsAction: loopbackActivation

>>> networkLinePair[ ]2

lineAttenuationsignalNoise

>>> customerLinePair[ ]2

lineAttenuationsignalNoise

>> end4

vendorIdvendorModelvendorSerialvendorSoftVersioneocSoftVersionshdslVersioneocStateeocAlarmThresholds

2. in case of a 2P version, two linePair objects are present: linePair[1] and linePair[2].3. not present by default, has to be added (CV only).4. not present by default, is added automatically when setting the line/eocHandling attribute.

Page 226: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

212

>>> linePair[ ]2

lineAttenuationsignalNoise

>> rs530, v35, v365

txdItu103rxdItu104rtsItu105ctsItu106dsrItuT107dcdItu109rdlItu140alItu141tiItu142ifDescrifTypeifSpeedifClockingremIfClockingextClockSourceifOperStatus

>> x215

txdItu103rxdItu104indicatorifDescrifTypeifSpeedifClockingremIfClockingextClockSourceifOperStatus

>> g7035

timeslots6

txdItu103rxdItu104losaislfa6

rai6

ifDescrifTypeifSpeedifClockingifOperStatus

5. only present when the corresponding interface is used6. G703 Nx64 only

Page 227: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

213

>> dualPort5

>>> g703timeSlotstxdItu103rxdItu104losaislfa6

rai6

ifDescrifTypeifSpeedifClockingifOperStatus

>>> rs530txdItu103rxdItu104rtsItu105ctsItu106dsrItuT107dcdItu109rdlItu140alItu141tiItu142ifDescrifTypeifSpeedifClockingifOperStatus

>> bridge5

wanTxdwanRxdifDescrifTypeifSpeedifClockingremIfClockingifOperStatus

Page 228: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

214

>> router5

wanTxdwanRxdifDescrifTypeifSpeedifClockingremIfClockingifOperStatus

>> managementcardSlotNumber7

cardNestNumber7

modemPosition7

>> operatingSystemtaskInfo

7. CV only

Page 229: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

215

8.2 General status attributes

This section describes the following status attributes:

� crocusShdsl<Tt|Cv>/sysDescr on page 216� crocusShdsl<Tt|Cv>/sysObjectID on page 216� crocusShdsl<Tt|Cv>/sysUpTime on page 216� crocusShdsl<Tt|Cv>/sysServices on page 216� crocusShdsl<Tt|Cv>/messages on page 216� crocusShdsl<Tt|Cv>/deviceId on page 217� crocusShdsl<Tt|Cv>/configurationSaving on page 217� crocusShdsl<Tt|Cv>/bootVersion on page 217� crocusShdsl<Tt|Cv>/loaderVersion on page 217� crocusShdsl<Tt|Cv>/flash1Version on page 218

This section describes the following actions:

� crocusShdsl<Tt|Cv>/Cold Boot on page 218

Page 230: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

216

crocusShdsl<Tt|Cv>/sysDescr

This is a textual description of the device. This is an SNMP MIB2 parameter.

Example: Telindus Crocus SHDSL TT V35 T1234/00100 01/01/00 12:00. In this example the following parameters are visible:

� Telindus 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.

crocusShdsl<Tt|Cv>/sysObjectID

This is the SNMP identification string. It is an SNMP MIB2 parameter.

Example: 1.3.6.1.4.1.776.22.

crocusShdsl<Tt|Cv>/sysUpTime

This is the elapsed time since last power-on or cold boot of the Crocus SHDSL.

Example: 00005d 02h 42m 15s, which means 5 days, 2 hours, 42 minutes and 15 seconds.

crocusShdsl<Tt|Cv>/sysServices

This is the SNMP service identification. It is an SNMP MIB2 parameter.

crocusShdsl<Tt|Cv>/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 con-trol connector, you can monitor these messages. If you hit the ENTER key, the messages stop and you get a password prompt (CLI mode).

Page 231: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

217

crocusShdsl<Tt|Cv>/deviceId

This displays a unique code. This code is programmed into the Crocus SHDSLbefore it leaves the fac-tory. You can use this code for inventory purposes.

crocusShdsl<Tt|Cv>/configurationSaving

This attribute indicates when the Crocus SHDSL is writing its (new) configuration to the flash memory.

crocusShdsl<Tt|Cv>/bootVersion

This displays the code and version of the boot software currently used in the Crocus SHDSL. For more information on boot software, refer to 12.1 - What is boot, loader and application software? on page 314.

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.

crocusShdsl<Tt|Cv>/loaderVersion

This displays the code and version of the loader software currently used in the Crocus SHDSL. For more information on loader software, refer to 12.1 - What is boot, loader and application software? on page 314.

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.

Value Description

busy The Crocus SHDSL is busy writing its configuration to the flash memory. During this state, do not power-down or reboot the Crocus SHDSL else the new configu-ration will be lost.

done The Crocus SHDSL has finished writing its configuration to the flash memory.

Page 232: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

218

crocusShdsl<Tt|Cv>/flash1Version

This displays the code and version of the application software, also called firmware, currently used in the Crocus SHDSL. For more information on application software, refer to 12.1 - What is boot, loader and application software? on page 314.

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.

crocusShdsl<Tt|Cv>/Cold Boot

This action will reboot the Crocus SHDSL while the power stays up (the Crocus SHDSL also reboots if it is powered down and up again).

Page 233: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

219

8.3 Line status attributes

This section describes the following status attributes:

� crocusShdsl<Tt|Cv>/line/ifDescr on page 220� crocusShdsl<Tt|Cv>/line/ifType on page 220� crocusShdsl<Tt|Cv>/line/ifSpeed on page 220� crocusShdsl<Tt|Cv>/line/ifOperStatus on page 220� crocusShdsl<Tt|Cv>/line/minLinePairSpeed on page 220� crocusShdsl<Tt|Cv>/line/maxLinePairSpeed on page 221� crocusShdsl<Tt|Cv>/line/framerType on page 222� crocusShdsl<Tt|Cv>/line/testType on page 222� crocusShdsl<Tt|Cv>/line/testOriginator on page 223� crocusShdsl<Tt|Cv>/line/testStatus on page 223� crocusShdsl<Tt|Cv>/line/maxSpeedSearch on page 223� crocusShdsl<Tt|Cv>/line/maxSpeedResult on page 223� crocusShdsl<Tt|Cv>/line/errorCount on page 224� crocusShdsl<Tt|Cv>/line/region on page 224� crocusShdsl<Tt|Cv>/line/asymmetricPsd on page 224� crocusShdsl<Tt|Cv>/line/linePairsSwapped on page 224� crocusShdsl<Tt|Cv>/line/numDiscoveredRepeaters on page 224� crocusShdsl<Tt|Cv>/line/eocAlarmThresholds on page 225

This section describes the following actions:

� crocusShdsl<Tt|Cv>/line/testActivation on page 225� crocusShdsl<Tt|Cv>/line/clearErrorCounter on page 225� crocusShdsl<Tt|Cv>/line/maximumSpeedSearch on page 226

Page 234: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

220

crocusShdsl<Tt|Cv>/line/ifDescr

This attribute displays the interface description. It is an SNMP MIB2 parameter.

The ifDescr value for the line object is line.

crocusShdsl<Tt|Cv>/line/ifType

This attribute displays the interface type. It is an SNMP MIB2 parameter.

The ifType value for the line object is other.

crocusShdsl<Tt|Cv>/line/ifSpeed

This attribute displays the current line speed in bits per second (bps), e.g. 2048000.

crocusShdsl<Tt|Cv>/line/ifOperStatus

This attribute displays the current operation status of the line. Possible operation status values are:

crocusShdsl<Tt|Cv>/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 221 for more information.

Value Description

up The line is up, data transfer is possible.

down The line is down, data transfer is not possible.

testing 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.

Page 235: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

221

crocusShdsl<Tt|Cv>/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 config-ured?

Description

user speed (fixed)

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.

user speed (auto)

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 dis-plays the lowest possible speed that could be achieved on the line pair(s) during the training cycle. The status attribute maxLinePairSpeed displays the highest possi-ble speed that could be achieved on the line pair(s) during the training cycle.

user speed (fixed) + line speed

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 min-LinePairSpeed displays a speed that is equal to the configured minimum line pair speed. What is more, the status attributes minLinePairSpeed and maxLinePairSpeed dis-play the same speed.

Remark

Note that this only applies when the configured user speed is lower than the con-figured 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.

Page 236: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

222

crocusShdsl<Tt|Cv>/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 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 depend-ing on which interface is used, which user/line speed is chosen, etc. the Crocus SHDSL will select one of these modes.

crocusShdsl<Tt|Cv>/line/testType

This attribute displays which test is currently active. The possible indications are:

Mode Description

Nx64 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 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 2 pair version).

slotted E1 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 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 2 pair version).

Value Description

no No test is active.

al An analogue loop is active.

dl A digital loop is active.

rdl A remote digital loop is active.

et The error test pattern generator / detector is active.

alEt An analogue loop in combination with an error test is active.

rdlEt A remote digital loop in combination with an error test is active.

Page 237: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

223

crocusShdsl<Tt|Cv>/line/testOriginator

This attribute displays the origin of the active test. The possible indications are:

crocusShdsl<Tt|Cv>/line/testStatus

This attribute displays the status of the active test. The possible indications are:

crocusShdsl<Tt|Cv>/line/maxSpeedSearch

This attribute shows the status of the maximumSpeedSearch action. The possible indications are:

crocusShdsl<Tt|Cv>/line/maxSpeedResult

This attribute displays the maximum speed that was achieved during the execution of the maximumSpeed-Search action.

Value Description

nms The test is initiated by the management system (e.g. TMA).

keyboard The test is initiated by the keyboard or the EasyConnect via the test "window" of the Crocus SHDSL. Refer to 5.5 - The test window on page 77.

interface The test is initiated by the application, via the interface.

remote The test is initiated by the remote Crocus SHDSL.

unknown There are two possibilities:

� No test is running.� For some reason it is not possible to define the origin of the test.

Value Description

progressing The test is starting.

running The test is running.

ending The test is ending.

unknown There are two possibilities:

� No test is running.� For some reason it is not possible to retrieve the status of the test.

Value Description

idle No maximumSpeedSearch action has been performed.

progressing The maximumSpeedSearch action is running.

aborted The maximumSpeedSearch action stopped without result.

completed The maximumSpeedSearch action is finished. The result is displayed in the maxSpeed-Result attribute.

Page 238: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

224

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/line/region

This attribute displays how you configured the region configuration attribute (annexA, annexB or auto).

crocusShdsl<Tt|Cv>/line/asymmetricPsd

This attribute displays whether asymmetric PSD is currently active or not.

crocusShdsl<Tt|Cv>/line/linePairsSwapped

This attribute is only present on the Crocus SHDSL 2P version.

This attribute indicates whether the 2 line pairs have been swapped when connecting the central with the remote device. Possible values are:

crocusShdsl<Tt|Cv>/line/numDiscoveredRepeaters

This attribute displays the number of Crocus SHDSL Repeaters that the Crocus SHDSL discovered on the SHDSL line.

Value Description

yes The line pairs are swapped.

no The line pairs are not swapped.

unknown The Crocus SHDSL is unable to determine whether the line pairs have been swapped (e.g. because it is still training).

Page 239: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

225

crocusShdsl<Tt|Cv>/line/eocAlarmThresholds

What this attribute displays depends on the setting of the line/eocHandling attribute:

The eocAlarmThresholds structure contains the following elements:

� lineAttenuation� signalNoise

crocusShdsl<Tt|Cv>/line/testActivation

Use this action to perform a test on the Crocus SHDSL. These tests are useful to trace possible prob-lems. Possible tests are: no, al, dl, rdl, et, alEt, rdlEt.

To execute a test, proceed as follows:

For more information on these tests, refer to Chapter 13 - Diagnostic tests on page 325.

crocusShdsl<Tt|Cv>/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.

If eocHandling is set to �

then �

none the eocAlarmThresholds attribute does not display relevant information. It always dis-plays 0.0.

discovery � on the central device, the eocAlarmThresholds attribute displays the values as set in the line/linkAlarmThresholds attribute.·

� on the remote device, the eocAlarmThresholds attribute does not display relevant information. It always displays 0.0.

inventory

info

alarmConfiguration the eocAlarmThresholds attribute displays the values as set in the line/linkAlarmThresh-olds attribute on the central device.

Step Action

1 In the TMA window, select the object line and the group Performance or Status.

2 In the action window of TMA, click the left mouse button on the field under the heading Argument Value.

⇒A drop down box appears.

3 In the drop down box, select the test you want to execute.

4 Press the right mouse button and select Execute.

Page 240: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

226

crocusShdsl<Tt|Cv>/line/maximumSpeedSearch

Use this action to determine the highest possible line speed that can be achieved between the central and remote Crocus SHDSL. Double click on the maximumSpeedSearch string to execute the action.

When you execute this test, the following happens:

� The Crocus SHDSL 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.

Phase Action

1 The Crocus SHDSL interrupts the normal data transfer.

2 Both local and remote Crocus SHDSL 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.

3 When the test ends, the result is displayed by the maxSpeedResult attribute.

4 The Crocus SHDSL resumes normal data transfer at the speed that was selected before the test.

Page 241: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

227

8.4 Line pair status attributes

This section describes the following status attributes:

� crocusShdsl<Tt|Cv>/line/linePair[ ]/ifSpeed on page 228� crocusShdsl<Tt|Cv>/line/linePair[ ]/ifOperStatus on page 228� crocusShdsl<Tt|Cv>/line/linePair[ ]/status on page 228� crocusShdsl<Tt|Cv>/line/linePair[ ]/timeSinceLastRetrain on page 228� crocusShdsl<Tt|Cv>/line/linePair[ ]/transmitPower on page 229� crocusShdsl<Tt|Cv>/line/linePair[ ]/lineAttenuation on page 229� crocusShdsl<Tt|Cv>/line/linePair[ ]/signalNoise on page 229� crocusShdsl<Tt|Cv>/line/linePair[ ]/stepupThreshold on page 229� crocusShdsl<Tt|Cv>/line/linePair[ ]/actualBitRate on page 229

In case of a Crocus SHDSL 2P, two linePair objects are present: linePair [1] and linePair [2].

Page 242: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

228

crocusShdsl<Tt|Cv>/line/linePair[ ]/ifSpeed

This attribute displays the line pair speed, in bits per second (bps), when the line pair is in data state.

crocusShdsl<Tt|Cv>/line/linePair[ ]/ifOperStatus

This attribute displays the current operation status of the line. The possible indications are:

crocusShdsl<Tt|Cv>/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:

crocusShdsl<Tt|Cv>/line/linePair[ ]/timeSinceLastRetrain

This attribute displays the time the line is in data state since the last retrain cycle.

Value Description

up The line is up, data transfer is possible.

down The line is down, data transfer is not possible.

testing 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.

Value Description

idle No data connection is present. This is the initial state.

dataState A data connection is present. The training sequence was successful and the bit-pumps are ready to transmit data.

Page 243: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

229

crocusShdsl<Tt|Cv>/line/linePair[ ]/transmitPower

This attribute displays the current transmit power in dB, e.g. 7.5.

crocusShdsl<Tt|Cv>/line/linePair[ ]/lineAttenuation

This attribute displays the current line attenuation in dB, e.g. 11.0.

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/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 will retrain at a higher speed if the measured signal to noise ratio exceeds the step-up threshold value.

The stepupThreshold value =

� the signal to noise ratio at the moment the line entered the data state (i.e. shortly after a successful training cycle)

+

� the stepupMargin value.

Refer to crocusShdsl<Tt|Cv>/line/retrain on page 171 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).

crocusShdsl<Tt|Cv>/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.

Page 244: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

230

8.5 Remote power status attributes

This section describes the following status attributes:

� crocusShdsl<Tt|Cv>/line/linePair[ ]/pwrSource/status on page 231� crocusShdsl<Tt|Cv>/line/linePair[ ]/pwrSource/version on page 231

Page 245: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

231

crocusShdsl<Tt|Cv>/line/linePair[ ]/pwrSource/status

This attribute displays the status of the Remote Power Source module. The possible indications are:

crocusShdsl<Tt|Cv>/line/linePair[ ]/pwrSource/version

This attribute displays the version of the Remote Power source module its software.

Value The Remote Power source module �

active is active and operates normal.

hwFailed is defective.

hwDisabled has been disabled by the dedicated hardware strap on the Remote Power source module. In this case it is not possible to enable remote powering via a manage-ment tool.

mgtDisabled has been disabled using the configuration attribute pwrSource. Refer to 7.5 - Remote power configuration attributes on page 181.

noCurrent only has to deliver a current smaller than 15 mA. This might indicate that:

� the remote modem is fed by a power supply and therefore does not require remote power over the line.

� the remote modem is defective and therefore does not longer require supply current.

� the Remote Power source module is defective.� the line is interrupted.

overCurrent has to deliver a current higher than 60 mA. This might indicate that:

� the remote modem is defective and a short circuit has occurred.� the Remote Power source module is defective.� the line is short circuited.

Page 246: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

232

8.6 Repeater and end status attributes

This section describes the following status attributes:

� crocusShdsl<Tt|Cv>/end/vendorId on page 233� crocusShdsl<Tt|Cv>/end/vendorModel on page 233� crocusShdsl<Tt|Cv>/end/vendorSerial on page 233� crocusShdsl<Tt|Cv>/end/vendorSoftVersion on page 233� crocusShdsl<Tt|Cv>/end/eocSoftVersion on page 234� crocusShdsl<Tt|Cv>/end/shdslVersion on page 234� crocusShdsl<Tt|Cv>/end/eocState on page 234� crocusShdsl<Tt|Cv>/end/eocAlarmThresholds on page 234� crocusShdsl<Tt|Cv>/end/linePair[ ]/lineAttenuation on page 236� crocusShdsl<Tt|Cv>/end/linePair[ ]/signalNoise on page 236

This section describes the following actions:

� crocusShdsl<Tt|Cv>/repeater/loopbackActivation on page 236

� 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 6.2 - Configuring EOC handling on page 82.

� 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 6.2.4 - EOC retrieved information on page 84.

� The repeater[ ] and end objects contain the same attributes, therefore only the attributes of the end object are listed here.

� When the Crocus SHDSL is configured for 1 pair operation, the repeater[ ] and end[ ] objects networ-kLinePair[2] and customerLinePair[2] still appear in the containment tree (although 1 pair operation has been configured).

Page 247: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

233

crocusShdsl<Tt|Cv>/end/vendorId

This attribute is only retrieved in case the eocHandling attribute is set to discovery, inventory, info or alarmCon-figuration.

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 Telindus.� vendorSpecific

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/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 Telindus devices this is the deviceId attribute.

crocusShdsl<Tt|Cv>/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 Telindus device this is the part after "/" of the T-code string displayed in the flashVersion attribute.

Page 248: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

234

crocusShdsl<Tt|Cv>/end/eocSoftVersion

This attribute is only retrieved in case the eocHandling attribute is set to discovery, inventory, info or alarmCon-figuration.

This attribute displays the EOC software version used on the repeater or end device.

crocusShdsl<Tt|Cv>/end/shdslVersion

This attribute is only retrieved in case the eocHandling attribute is set to discovery, inventory, info or alarmCon-figuration.

This attribute displays the SHDSL version used on the repeater or end device.

crocusShdsl<Tt|Cv>/end/eocState

This attribute is only retrieved in case the eocHandling attribute is set to discovery, inventory, info or alarmCon-figuration.

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 mes-sages.

crocusShdsl<Tt|Cv>/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:

The eocAlarmThresholds structure contains the following elements:

� lineAttenuation

If eocHandling is set to �

then �

info the eocAlarmThresholds attribute displays the values as set in the line/linkAlarmThresh-olds attribute on the remote1 device or repeater.

1. The remote device is the device on which the channel attribute is set to remote.

alarmConfiguration the eocAlarmThresholds attribute displays the values as set in the line/linkAlarmThresh-olds attribute on the central2 device.

Remark

Note that the values are rounded off. E.g. when 28.6 dB is configured on the cen-tral modem, then 28 dB is shown on the remote device or repeater.

2. The central device is the device on which the channel attribute is set to central.

Page 249: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

235

� signalNoise

Page 250: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

236

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/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 (dou-ble-click the loopbackActivation string). Stop the loop by selecting the action argument value clearAllMainte-nanceStates 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 alarmConfig-

uration.� The loopbackActivation action argument value noAction does nothing. It is only present to have a default

value.

Page 251: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

237

8.7 DTE Interface status attributes

This section discusses the status attributes of the different DTE interfaces. Because some of the inter-face status attributes are present on every interface, they are discussed in a general. All other sections discuss the interface specific attributes.

The following gives an overview of this section.

� 8.7.1 - RS530, V35 and V36 interface status attributes on page 238� 8.7.2 - X21 interface status attributes on page 243� 8.7.3 - G703 interface status attributes on page 247� 8.7.4 - Dual Port G703-Serial interface status attributes on page 251� 8.7.5 - Bridge and Router interface status attributes on page 252

Page 252: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

238

8.7.1 RS530, V35 and V36 interface status attributes

This section describes the following status attributes:

� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/txdItu103 on page 239� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/rxdItu104 on page 239� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/rtsItu105 on page 239� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ctsItu106 on page 239� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/dsrItu107 on page 239� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/dcdItu109 on page 239� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/rdlItu140 on page 239� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/alItu141 on page 239� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/tiItu142 on page 239� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/remIfClocking on page 240� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/extClockSource on page 240� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ifDescr on page 240� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ifType on page 241� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ifSpeed on page 241� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ifClocking on page 241� crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ifOperStatus on page 242

Page 253: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

239

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/txdItu103

This attribute displays the status (on / off) of the transmit data signal (circuit 103). The txdItu103 attribute only indicates the presence of the TxD signal, it does not monitor the real data signal.

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/rxdItu104

This attribute displays the status (on / off) of the receive data signal (circuit 104). The rxdItu104 attribute only indicates the presence of the RxD signal, it does not monitor the real data signal.

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/rtsItu105

This attribute displays the status (on / off) of the request to send signal (circuit 105).

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ctsItu106

This attribute displays the status (on / off) of the clear to send signal (circuit 106).

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/dsrItu107

This attribute displays the status (on / off) of the data set ready signal (circuit 107).

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/dcdItu109

This attribute displays the status (on / off) of the data carrier detect signal (circuit 109).

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/rdlItu140

This attribute displays the status (on / off) of the remote digital loop signal (circuit 140).

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/alItu141

This attribute displays the status (on / off) of the analogue loop signal (circuit 141).

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/tiItu142

This attribute displays the status (on / off) of the test indication signal (circuit 142).

Page 254: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

240

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/remIfClocking

This attribute displays the clocking mode which is actually used by the remote Crocus SHDSL, e.g. inter-nalPreferred.

This is not necessarily the clocking mode you configured. It can be a clocking mode that is selected by the remote Crocus SHDSL because it was not possible to select the clocking mode of your choice (for example, because the external clock signal is lost).

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/extClockSource

This attribute displays the external clock source. Note that this attribute only displays meaningful infor-mation when the clocking mode is set to auto mode.

The possible indications are:

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ifDescr

This attribute displays the DTE interface description. It is an SNMP MIB2 parameter.

Value Description

none No external clock signal was detected.

txClock The external clock signal is a transmit clock signal generated by the Crocus SHDSL and looped back by the DTE.

rxClock The external clock signal is a transmit clock signal derived from the received line data by the Crocus SHDSL and looped back by the DTE.

dte The external clock signal is an external transmit clock signal generated by the DTE.

notDetected The external clock source can not be determined. This value is also shown when the clocking mode is set to a fixed mode instead of auto mode.

Page 255: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

241

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ifType

This attribute displays the DTE interface type. It is an SNMP MIB2 parameter.

The following table shows the ifDescr and ifType attribute for each DTE interface.

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/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.

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ifClocking

This attribute displays the clocking mode which is actually used by the Crocus SHDSL, e.g. internalPre-ferred.

This is not necessarily the clocking mode you configured. It can be a clocking mode that is selected by the Crocus SHDSLbecause it was not possible to select the clocking mode of your choice (for example, because the external clock signal is lost).

DTE interface ifDescr value ifType value

RS530 rs530 other

V35 v35 other

V36 v36 other

X21 x21 other

G703 g703 � other when the G703 inter-face is used in unframed mode

� e1 when the G703 interface is used in framed mode

Bridge bridge ethernet-csmacd

Router router other

Page 256: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

242

crocusShdsl<Tt|Cv>/<rs530/v35/v36>/ifOperStatus

This attribute displays the current operational status of the DTE interface. This matches the unavailability condition as defined in ITU-T recommendation G.826 (Annex A). The possible indications are:

Remarks

� In case of an RS530, V35 or V36 interface the ifOperStatus attribute behaviour is influenced by the set-ting of the rtsControl attribute. In case the rtsControl attribute is set to �- internal, then the ifOperStatus attribute value is always up.- external, then the ifOperStatus attribute follows the RTS signal coming from the application.

� In case of a G703 interface the ifOperStatus attribute value is down if a Loss Of Signal (LOS) is detected on the incoming signal (transmit data or TxD) or on the outgoing signal (receive data or RxD).

� In case of a Bridge interface the ifSpeed attribute displays the speed on the LAN interface. In other words, when a LAN is connected (i.e. ifOperStatus = up) then the ifSpeed is always 10000000 bps, disregarding of the setting of the configuration attribute speed.

� In case of a Router interface the ifSpeed and ifOperStatus attributes display the speed and operational status between the Router interface and the Crocus SHDSL. This implies that as soon as you insert a Router interface in the Crocus SHDSL the crocusShdsl<Tt|Cv>/router/ifOperStatus value becomes up, dis-regarding of the operational status of the Router interface itself. For that information you have to con-nect to the Router interface.

Value Description

up The DTE interface is up, data transfer is possible.

down The DTE interface is down, data transfer is not possible. For example, because there is no connection between the interface and the DTE.

Page 257: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

243

8.7.2 X21 interface status attributes

This section describes the following status attributes:

� crocusShdsl<Tt|Cv>/x21/txdItu103 on page 244� crocusShdsl<Tt|Cv>/x21/rxdItu104 on page 244� crocusShdsl<Tt|Cv>/x21/indicator on page 244� crocusShdsl<Tt|Cv>/x21/remIfClocking on page 244� crocusShdsl<Tt|Cv>/x21/extClockSource on page 244� crocusShdsl<Tt|Cv>/X21/ifDescr on page 245� crocusShdsl<Tt|Cv>/X21/ifType on page 245� crocusShdsl<Tt|Cv>/X21/ifSpeed on page 245� crocusShdsl<Tt|Cv>/X21/ifClocking on page 245� crocusShdsl<Tt|Cv>/X21/ifOperStatus on page 246

Page 258: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

244

crocusShdsl<Tt|Cv>/x21/txdItu103

This attribute displays the status (on / off) of the transmit data signal (circuit 103). The txdItu103 attribute only indicates the presence of the TxD signal, it does not monitor the real data signal.

crocusShdsl<Tt|Cv>/x21/rxdItu104

This attribute displays the status (on / off) of the receive data signal (circuit 104). The rxdItu104 attribute only indicates the presence of the RxD signal, it does not monitor the real data signal.

crocusShdsl<Tt|Cv>/x21/indicator

This attribute displays the status (on / off) of the indicator signal.

crocusShdsl<Tt|Cv>/x21/remIfClocking

This attribute displays the clocking mode which is actually used by the remote Crocus SHDSL, e.g. inter-nalPreferred.

This is not necessarily the clocking mode you configured. It can be a clocking mode that is selected by the remote Crocus SHDSL because it was not possible to select the clocking mode of your choice (for example, because the external clock signal is lost).

crocusShdsl<Tt|Cv>/x21/extClockSource

This attribute displays the external clock source. Note that this attribute only displays meaningful infor-mation when the clocking mode is set to auto mode.

The possible indications are:

Value Description

none No external clock signal was detected.

txClock The external clock signal is a transmit clock signal generated by the Crocus SHDSL and looped back by the DTE.

rxClock The external clock signal is a transmit clock signal derived from the received line data by the Crocus SHDSL and looped back by the DTE.

dte The external clock signal is an external transmit clock signal generated by the DTE.

notDetected The external clock source can not be determined. This value is also shown when the clocking mode is set to a fixed mode instead of auto mode.

Page 259: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

245

crocusShdsl<Tt|Cv>/X21/ifDescr

This attribute displays the DTE interface description. It is an SNMP MIB2 parameter.

crocusShdsl<Tt|Cv>/X21/ifType

This attribute displays the DTE interface type. It is an SNMP MIB2 parameter.

The following table shows the ifDescr and ifType attribute for the X21 interface.

crocusShdsl<Tt|Cv>/X21/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.

crocusShdsl<Tt|Cv>/X21/ifClocking

This attribute displays the clocking mode which is actually used by the Crocus SHDSL, e.g. internalPre-ferred.

This is not necessarily the clocking mode you configured. It can be a clocking mode that is selected by the Crocus SHDSL because it was not possible to select the clocking mode of your choice (for example, because the external clock signal is lost).

DTE interface ifDescr value ifType value

X21 x21 other

Page 260: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

246

crocusShdsl<Tt|Cv>/X21/ifOperStatus

This attribute displays the current operational status of the DTE interface. The possible indications are:

Remarks

� In case of an RS530, V35 or V36 interfaces the ifOperStatus attribute behaviour is influenced by the setting of the rtsControl attribute. In case the rtsControl attribute is set to �- internal, then the ifOperStatus attribute value is always up.- external, then the ifOperStatus attribute follows the RTS signal coming from the application.

� In case of a G703 interface the ifOperStatus attribute value is down if a Loss Of Signal (LOS) is detected on the incoming signal (transmit data or TxD) or on the outgoing signal (receive data or RxD).

� In case of a Bridge interface the ifSpeed attribute displays the speed on the LAN interface. In other words, when a LAN is connected (i.e. ifOperStatus = up) then the ifSpeed is always 10000000 bps, disregarding of the setting of the configuration attribute speed.

� In case of a Router interface the ifSpeed and ifOperStatus attributes display the speed and operational status between the Router interface and the Crocus SHDSL. This implies that as soon as you insert a Router interface in the Crocus SHDSL the crocusShdsl<Tt|Cv>/router/ifOperStatus value becomes up, dis-regarding of the operational status of the Router interface itself. For that information you have to con-nect to the Router interface.

Value Description

up The DTE interface is up, data transfer is possible.

down The DTE interface is down, data transfer is not possible. For example, because there is no connection between the interface and the DTE.

Page 261: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

247

8.7.3 G703 interface status attributes

This section describes the following status attributes:

� crocusShdsl<Tt|Cv>/g703/timeSlots on page 248� crocusShdsl<Tt|Cv>/g703/txdItu103 on page 248� crocusShdsl<Tt|Cv>/g703/rxdItu104 on page 248� crocusShdsl<Tt|Cv>/g703/los on page 248� crocusShdsl<Tt|Cv>/g703/ais on page 248� crocusShdsl<Tt|Cv>/g703/lfa on page 248� crocusShdsl<Tt|Cv>/g703/rai on page 248� crocusShdsl<Tt|Cv>/g703/ifDescr on page 248� crocusShdsl<Tt|Cv>/g703/ifType on page 249� crocusShdsl<Tt|Cv>/g703/ifSpeed on page 249� crocusShdsl<Tt|Cv>/g703/ifClocking on page 249� crocusShdsl<Tt|Cv>/g703/ifOperStatus on page 250

Page 262: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

248

crocusShdsl<Tt|Cv>/g703/timeSlots

This attribute is only present on the G703 Nx64k interface.

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 6.7.1 - Selecting unframed or framed mode on page 119.

crocusShdsl<Tt|Cv>/g703/txdItu103

This attribute displays the status (on / off) of the transmit data signal. The txdItu103 attribute only indicates the presence of the TxD signal, it does not monitor the real data signal.

crocusShdsl<Tt|Cv>/g703/rxdItu104

This attribute displays the status (on / off) of the receive data signal. The rxdItu104 attribute only indicates the presence of the RxD signal, it does not monitor the real data signal.

crocusShdsl<Tt|Cv>/g703/los

This attribute displays (on / off) whether a Loss Of Signal has been detected. LOS is on when the incom-ing data is no longer present. E.g. the connection from the application towards the Crocus SHDSLis interrupted.

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/g703/lfa

This attribute is only present on the G703 Nx64k interface.

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.

crocusShdsl<Tt|Cv>/g703/rai

This attribute is only present on the G703 Nx64k interface.

This attribute displays (on / off) whether a Remote Alarm Indication signal has been detected. RAI is on when the RAI signal is detected on the incoming data. RAI means the far-end equipment has a problem with the signal it is receiving from the local equipment.

crocusShdsl<Tt|Cv>/g703/ifDescr

This attribute displays the DTE interface description. It is an SNMP MIB2 parameter.

Page 263: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

249

crocusShdsl<Tt|Cv>/g703/ifType

This attribute displays the DTE interface type. It is an SNMP MIB2 parameter.

The following table shows the ifDescr and ifType attribute for each DTE interface.

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/g703/ifClocking

This attribute displays the clocking mode which is actually used by the Crocus SHDSL, e.g. internalPre-ferred.

This is not necessarily the clocking mode you configured. It can be a clocking mode that is selected by the Crocus SHDSL because it was not possible to select the clocking mode of your choice (for example, because the external clock signal is lost).

DTE interface ifDescr value ifType value

RS530 rs530 other

V35 v35 other

V36 v36 other

X21 x21 other

Bridge bridge ethernet-csmacd

Router router other

Page 264: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

250

crocusShdsl<Tt|Cv>/g703/ifOperStatus

This attribute displays the current operational status of the DTE interface. The possible indications are:

Remarks

� In case of an RS530, V35 or V36 interfaces the ifOperStatus attribute behaviour is influenced by the setting of the rtsControl attribute. In case the rtsControl attribute is set to �- internal, then the ifOperStatus attribute value is always up.- external, then the ifOperStatus attribute follows the RTS signal coming from the application.

� In case of a G703 interface the ifOperStatus attribute value is down if a Loss Of Signal (LOS) is detected on the incoming signal (transmit data or TxD) or on the outgoing signal (receive data or RxD).

� In case of a Bridge interface the ifSpeed attribute displays the speed on the LAN interface. In other words, when a LAN is connected (i.e. ifOperStatus = up) then the ifSpeed is always 10000000 bps, disregarding of the setting of the configuration attribute speed.

� In case of a Router interface the ifSpeed and ifOperStatus attributes display the speed and operational status between the Router interface and the Crocus SHDSL. This implies that as soon as you insert a Router interface in the Crocus SHDSL the crocusShdsl<Tt|Cv>/router/ifOperStatus value becomes up, dis-regarding of the operational status of the Router interface itself. For that information you have to con-nect to the Router interface.

Value Description

up The DTE interface is up, data transfer is possible.

down The DTE interface is down, data transfer is not possible. For example, because there is no connection between the interface and the DTE.

Page 265: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

251

8.7.4 Dual Port G703-Serial interface status attributes

The status attributes of the Dual Port G703-Serial interface are the same those of the G703 (Nx64k) and RS530 interface. Therefore, for more information on these attributes, refer to �

� 8.7.1 - RS530, V35 and V36 interface status attributes on page 238,� 8.7.3 - G703 interface status attributes on page 247.

Page 266: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

252

8.7.5 Bridge and Router interface status attributes

This section describes the following status attributes:

� crocusShdsl<Tt|Cv>/<dteInterface>/wanTxd on page 253� crocusShdsl<Tt|Cv>/<dteInterface>/wanRxd on page 253� crocusShdsl<Tt|Cv>/<dteInterface>/remIfClocking on page 253� crocusShdsl<Tt|Cv>/<dteInterface>/ifDescr on page 253� crocusShdsl<Tt|Cv>/<dteInterface>/ifType on page 253� crocusShdsl<Tt|Cv>/<dteInterface>/ifSpeed on page 254� crocusShdsl<Tt|Cv>/<dteInterface>/ifClocking on page 254� crocusShdsl<Tt|Cv>/<dteInterface>/ifOperStatus on page 254

Page 267: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

253

crocusShdsl<Tt|Cv>/<dteInterface>/wanTxd

This attribute displays the status (on / off) of the WAN TxD (wide area network transmit data) signal, after encapsulation of the user data on the Bridge or Router interface.

crocusShdsl<Tt|Cv>/<dteInterface>/wanRxd

This attribute displays the status (on / off) of the WAN RxD (wide area network receive data) signal, before extraction of the user data on the Bridge or Router interface.

crocusShdsl<Tt|Cv>/<dteInterface>/remIfClocking

This attribute displays the clocking mode which is actually used by the remote Crocus SHDSL, e.g. inter-nalPreferred.

This is not necessarily the clocking mode you configured. It can be a clocking mode that is selected by the remote Crocus SHDSL because it was not possible to select the clocking mode of your choice (for example, because the external clock signal is lost).

crocusShdsl<Tt|Cv>/<dteInterface>/ifDescr

This attribute displays the DTE interface description. It is an SNMP MIB2 parameter.

crocusShdsl<Tt|Cv>/<dteInterface>/ifType

This attribute displays the DTE interface type. It is an SNMP MIB2 parameter.

The following table shows the ifDescr and ifType attribute for each DTE interface.

DTE interface ifDescr value ifType value

RS530 rs530 other

V35 v35 other

V36 v36 other

X21 x21 other

G703 g703 � other when the G703 inter-face is used in unframed mode

� e1 when the G703 interface is used in framed mode

Bridge bridge ethernet-csmacd

Router router other

Page 268: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

254

crocusShdsl<Tt|Cv>/<dteInterface>/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.

crocusShdsl<Tt|Cv>/<dteInterface>/ifClocking

This attribute displays the clocking mode which is actually used by the Crocus SHDSL, e.g. internalPre-ferred.

This is not necessarily the clocking mode you configured. It can be a clocking mode that is selected by the Crocus SHDSL because it was not possible to select the clocking mode of your choice (for example, because the external clock signal is lost).

crocusShdsl<Tt|Cv>/<dteInterface>/ifOperStatus

This attribute displays the current operational status of the DTE interface. The possible indications are:

Remarks

� In case of an RS530, V35 or V36 interfaces the ifOperStatus attribute behaviour is influenced by the setting of the rtsControl attribute. In case the rtsControl attribute is set to �- internal, then the ifOperStatus attribute value is always up.- external, then the ifOperStatus attribute follows the RTS signal coming from the application.

� In case of a G703 interface the ifOperStatus attribute value is down if a Loss Of Signal (LOS) is detected on the incoming signal (transmit data or TxD) or on the outgoing signal (receive data or RxD).

� In case of a Bridge interface the ifSpeed attribute displays the speed on the LAN interface. In other words, when a LAN is connected (i.e. ifOperStatus = up) then the ifSpeed is always 10000000 bps, disregarding of the setting of the configuration attribute speed.

� In case of a Router interface the ifSpeed and ifOperStatus attributes display the speed and operational status between the Router interface and the Crocus SHDSL. This implies that as soon as you insert a Router interface in the Crocus SHDSL the crocusShdsl<Tt|Cv>/router/ifOperStatus value becomes up, dis-regarding of the operational status of the Router interface itself. For that information you have to con-nect to the Router interface.

Value Description

up The DTE interface is up, data transfer is possible.

down The DTE interface is down, data transfer is not possible. For example, because there is no connection between the interface and the DTE.

Page 269: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

255

8.8 Management status attributes

This section describes the following status attributes:

� crocusShdsl<Tt|Cv>/management/cardSlotNumber on page 256� crocusShdsl<Tt|Cv>/management/cardNestNumber on page 256� crocusShdsl<Tt|Cv>/management/modemPosition on page 256

The following attributes are only present on a Crocus SHDSL Card Version, not on a Table Top.

Page 270: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

256

crocusShdsl<Tt|Cv>/management/cardSlotNumber

This attribute displays in which slot of the CN4 card nest the Crocus SHDSL is situated.

It is possible to manage the Crocus SHDSL with a management concentrator (e.g. the Orchid 1003 LAN or Telindus 1035 Orchid). In that case, the Crocus SHDSL its position in the CN4 card nest has to be known so that the management concentrator can address the Crocus SHDSL.

crocusShdsl<Tt|Cv>/management/cardNestNumber

This attribute displays the CN4 card nest address.

It is possible to manage the Crocus SHDSL with a management concentrator (e.g. the Orchid 1003 LAN or Telindus 1035 Orchid). In that case, the address of the CN4 card nest has to be known so that the management concentrator can address the Crocus SHDSL.

The CN4 card nest address can be set with DIP switches at the back of the card nest. For more infor-mation, refer to the CN4 manual.

crocusShdsl<Tt|Cv>/management/modemPosition

This attribute displays the position of the modem (A or B) on the Card Version.

It is possible to manage the Crocus SHDSL with a management concentrator (e.g. the Orchid 1003 LAN or Telindus 1035 Orchid). In that case, the position of the modem on the card has to be known so that the management concentrator can address that particular modem.

Page 271: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

257

8.9 Operating system status

This section describes the following status attributes:

� crocusShdsl<Tt|Cv>/operatingSystem/taskInfo on page 258

Page 272: m Crocus SHDSL

Crocus SHDSL Chapter 8

Reference manual Status attributes

258

crocusShdsl<Tt|Cv>/operatingSystem/taskInfo

The taskInfo table displays status information about the operating system. The table contains the following attributes:

Attribute Description

taskName Name of the task.

taskStatus Current status. The task can have the following status values:

� 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.

load30s (%) This is the load on the processor during the last 30 seconds.

load5m (%) This is the load on the processor during the last 5 minutes.

runningInMedium (%)

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.

runningInHigh (%) 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 sec-onds. The percentage of time this task is running with low priority can be calculated using the following formula:100% - runningInMedium (%) - runningInHigh (%).

programCounter This is the current value of the program counter. The program counter is the mem-ory address for the current instruction of this task.

Page 273: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

259

9 Performance attributes

This chapter discusses the performance attributes of the Crocus SHDSL. The following gives an over-view of this chapter.

� 9.1 - Performance attribute overview on page 260� 9.2 - Introducing the performance attributes on page 263� 9.3 - Line performance attributes on page 266� 9.4 - Line pair performance attributes on page 268� 9.5 - Repeater and end performance attributes on page 271� 9.6 - G703 interface performance attributes on page 272� 9.7 - Dual Port G703-Serial interface performance attributes on page 276� 9.8 - Operating system performance attributes on page 277

Page 274: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

260

9.1 Performance attribute overview

> crocusShdsl<Tt|Cv>Action: Cold Boot

>> lineh2Lineh24Lined7LinelineerrorCountAction: retrainAction: testActivationAction: clearErrorCounter

>>> linePair[ ]1

h2LineParametersh2Performanceh24LineParametersh24Performanced7LineParametersd7PerformancelineParametersperformance

>> repeater[ ]2

h2Lineh24Lined7Lineline

>>> networkLinePair[ ]1

h2LineParametersh2Performanceh24LineParametersh24Performanced7LineParametersd7PerformancelineParametersperformance

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

Page 275: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

261

>>> customerLinePair[ ]1

h2LineParametersh2Performanceh24LineParametersh24Performanced7LineParametersd7PerformancelineParametersperformance

>> end2

h2Lineh24Lined7Lineline

>>> linePair[ ]1

h2LineParametersh2Performanceh24LineParametersh24Performanced7LineParametersd7PerformancelineParametersperformance

>> g7033

h2G703Performanceh24G703Performanced7G703Performanceg703Performanceh2G826Performanceh24G826Performanced7G826Performanceg826Performance

>> dualPort3

>>> g703h2G703Performanceh24G703Performanced7G703Performanceg703Performanceh2G826Performanceh24G826Performanced7G826Performanceg826Performance

3. only present when the corresponding interface is used

Page 276: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

262

>> operatingSytemcurrUsedProcPowerfreeDataBufferstotalDataBufferslargestFreeBlockSizefreeBlockCountfreeMemorytotalMemoryusedProcPowertaskInfo

Page 277: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

263

9.2 Introducing the performance attributes

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 in detail, some general information on the performance attributes of the Crocus SHDSL is given.

The following gives an overview of this section.

� 9.2.1 - Introducing the performance timing on page 264� 9.2.2 - Introducing the performance terms on page 265

Page 278: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

264

9.2.1 Introducing the performance timing

The following table explains the performance information timing.

The Crocus SHDSL 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.

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.

Performance timing

Description

2 hours,24 hours,7 days

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. This can be considered as a performance information summary.

Page 279: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

265

9.2.2 Introducing the performance terms

The following table explains the performance information terms.

Term Description

sysUpTime Reflects the time since the latest cold boot of the Crocus SHDSL.

min, max, avrg Display the minimum, maximum and average values calculated for the corre-sponding period.E.g. min-max-avrg value of the noise margin.

count Counts the number of times an event occurred during the corresponding period.E.g. the number of retrains.

time Indicates the duration of an event during the corresponding period.E.g. the time during which the line is up.

Page 280: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

266

9.3 Line performance attributes

This section describes the following performance attributes:

� crocusShdsl<Tt|Cv>/line/<h2/h24/d7>Line on page 267� crocusShdsl<Tt|Cv>/line/line on page 267� crocusShdsl<Tt|Cv>/line/errorCount on page 267

This section describes the following actions:

� crocusShdsl<Tt|Cv>/line/retrain on page 267� crocusShdsl<Tt|Cv>/line/testActivation on page 267� crocusShdsl<Tt|Cv>/line/clearErrorCounter on page 267

Page 281: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

267

crocusShdsl<Tt|Cv>/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:

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/line/retrain

Use this action to initiate a retrain cycle. Double click on the retrain string to execute the action.

crocusShdsl<Tt|Cv>/line/testActivation

Use this action to perform a test on the Crocus SHDSL. These tests are useful to trace possible prob-lems. Possible tests are: no, al, dl, rdl, et, alEt, rdlEt.

To execute a test, proceed as follows:

For more information on these tests, refer to Chapter 13 - Diagnostic tests on page 325.

crocusShdsl<Tt|Cv>/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.

Element For the corresponding period, this value displays �

sysUpTime the elapsed time since the last cold boot.

linkDownCount the number of times the link went down.

linkDownTime the total amount of time the link was down.

Step Action

1 In the TMA window, select the object line and the group Performance or Status.

2 In the action window of TMA, click the left mouse button on the field under the heading Argument Value.

⇒A drop down box appears.

3 In the drop down box, select the test you want to execute.

4 Press the right mouse button and select Execute.

Page 282: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

268

9.4 Line pair performance attributes

This section describes the following performance attributes:

� crocusShdsl<Tt|Cv>/line/linePair[ ]/<h2/h24/d7>LineParameters on page 269� crocusShdsl<Tt|Cv>/line/linePair[ ]/lineParameters on page 269� crocusShdsl<Tt|Cv>/line/linePair[ ]/<h2/h24/d7>Performance on page 270� crocusShdsl<Tt|Cv>/line/linePair[ ]/performance on page 270

In case of a Crocus SHDSL 2P, two linePair objects are present: linePair [1] and linePair [2].

Page 283: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

269

crocusShdsl<Tt|Cv>/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:

crocusShdsl<Tt|Cv>/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.

Element For the corresponding period, this value displays �

sysUpTime the elapsed time since the last cold boot.

lineAttenuationMin (dB) the minimum line attenuation that was measured.

lineAttenuationMax (dB) the maximum line attenuation that was measured.

lineAttenuationAvrg (dB) the average line attenuation that was calculated.

signalNoiseMin (dB) the minimum signal to noise ratio that was measured.

signalNoiseMax (dB) the maximum signal to noise ratio that was measured.

signalNoiseAvrg (dB) the average signal to noise ratio that was calculated.

Page 284: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

270

crocusShdsl<Tt|Cv>/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>Per-formance structured value elements are the following:

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.

crocusShdsl<Tt|Cv>/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.

Attribute For the corresponding period, this attribute displays �

sysUpTime the time since the latest cold boot.

codeViolations the number of errored SHDSL frames that was counted.

errSec the number of errored seconds that was counted.

sevErrSec the number of severely errored seconds that was counted.

unavailableSec the number of unavailable seconds that was counted.

loswSec the number of lost synchronisation words that was counted.

moniSec the number of monitored seconds.

Page 285: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

271

9.5 Repeater and end performance attributes

� 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 6.2 - Configuring EOC handling on page 82.

� 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 6.2.4 - EOC retrieved information on page 84.

� 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 �- 9.3 - Line performance attributes on page 266 for more information on the line attributes.- 9.4 - Line pair performance attributes on page 268 for more information on the line pair attributes.

� When the Crocus SHDSL is configured for 1 pair operation, the repeater[ ] and end[ ] objects networ-kLinePair[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.

Page 286: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

272

9.6 G703 interface performance attributes

This section describes the following performance attributes:

� crocusShdsl<Tt|Cv>/g703/<h2/h24/d7>G703Performance on page 273� crocusShdsl<Tt|Cv>/g703/g703Performance on page 273� crocusShdsl<Tt|Cv>/g703/<h2/h24/d7>G826Performance on page 274� crocusShdsl<Tt|Cv>/g703/g826Performance on page 274

Page 287: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

273

crocusShdsl<Tt|Cv>/g703/<h2/h24/d7>G703Performance

This structured value displays the 2 hours, 24 hours and 7 days performance summary of the G703 inter-face. The <h2/h24/d7>G703Performance structured value elements are the following:

Also see G703 interface performance definitions.

crocusShdsl<Tt|Cv>/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.

Element For the corresponding period, this value displays �

sysUpTime the elapsed time since the last cold boot.

losCount the number of times a Loss Of Signal condition occurred.

losTime the amount of time a Loss Of Signal condition was active.

aisCount the number of times an Alarm Indication Signal condition occurred.

aisTime the amount of time an Alarm Indication Signal condition was active.

lfaCount the number of times a Loss of Frame Alignment condition occurred. This is only present on the G703 Nx64k interface.

lfaTime the amount of time a Loss of Frame Alignment condition was active. This is only present on the G703 Nx64k interface.

Page 288: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

274

crocusShdsl<Tt|Cv>/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:

Also see G703 interface performance definitions.

crocusShdsl<Tt|Cv>/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.

Element For the corresponding period, this value displays �

sysUpTime the elapsed time since the last cold boot.

errBlocks the number of errored blocks that was counted.

errSec the number of errored seconds that was counted.

sevErrSec the number of severely errored seconds that was counted.

unavailCount the number of times the interface was down (i.e. unavailable, as defined in ITU-T recommendation G.826 Annex A).

unavailTime the amount of time the interface was down.

bBErrors the number of background block errors that was counted.

Page 289: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

275

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 Definition

defect A defect is one of the following conditions:

� Loss Of Signal (LOS, defined in G.775).� Alarm Indication Signal (AIS, defined in G.775).� Loss of Frame Alignment (LFA, defined in G.706).

Errored Block (EB)

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.

Errored Second (ES)

A 1 second period where at least 1 EB or defect occurred.

Severely Errored Second (SES)

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.

Page 290: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

276

9.7 Dual Port G703-Serial interface performance attributes

The status attributes of the Dual Port G703-Serial interface are the same those of the G703 (Nx64k) interface. Refer to 9.6 - G703 interface performance attributes on page 272.

Page 291: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

277

9.8 Operating system performance attributes

This section describes the following performance attributes:

� crocusShdsl<Tt|Cv>/operatingSystem/currUsedProcPower on page 278� crocusShdsl<Tt|Cv>/operatingSystem/freeDataBuffers on page 278� crocusShdsl<Tt|Cv>/operatingSystem/totalDataBuffers on page 278� crocusShdsl<Tt|Cv>/operatingSystem/largestFreeBlockSize on page 278� crocusShdsl<Tt|Cv>/operatingSystem/freeBlockCount on page 278� crocusShdsl<Tt|Cv>/operatingSystem/freeMemory on page 278� crocusShdsl<Tt|Cv>/operatingSystem/totalMemory on page 278� crocusShdsl<Tt|Cv>/operatingSystem/usedProcPower on page 279� crocusShdsl<Tt|Cv>/operatingSystem/taskInfo on page 279

Page 292: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

278

crocusShdsl<Tt|Cv>/operatingSystem/currUsedProcPower

This is the amount of processing power used during the last 650 milliseconds, expressed as a percent-age of the total available processing power.

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/operatingSystem/totalDataBuffers

This is the total number of available data buffers.

crocusShdsl<Tt|Cv>/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.

crocusShdsl<Tt|Cv>/operatingSystem/freeBlockCount

This is the number of free contiguous memory blocks.

crocusShdsl<Tt|Cv>/operatingSystem/freeMemory

This is the total free memory expressed in bytes.

crocusShdsl<Tt|Cv>/operatingSystem/totalMemory

This is the total RAM memory expressed in bytes.

Page 293: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

279

crocusShdsl<Tt|Cv>/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 used-ProcPower is composed of the following attributes:

crocusShdsl<Tt|Cv>/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 proc-essor's operating system.

This attribute contains the same information as taskInfo in the status group (refer to 8.9 - Operating sys-tem status on page 257).

Value Description

sysUpTime Displays the elapsed time since the last cold boot. The next values are for the 30 seconds period before this relative time stamp.

minimumPP (%) This is the minimum percentage of processing power in use during the last 30 seconds.

averagePP (%) This is the average percentage of processing power in use during the last 30 seconds.

maximumPP (%) This is the maximum percentage of processing power in use during the last 30 seconds.

Page 294: m Crocus SHDSL

Crocus SHDSL Chapter 9

Reference manual Performance attributes

280

Page 295: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

281

10 Alarm attributes

This chapter discusses the alarm attributes of the Crocus SHDSL. The following gives an overview of this chapter.

� 10.1 - Alarm attribute overview on page 282� 10.2 - Introducing the alarm attributes on page 285� 10.3 - General alarms on page 292� 10.4 - Line alarms on page 295� 10.5 - Line pair alarms on page 297� 10.6 - Remote power alarms on page 300� 10.7 - Repeater and end alarms on page 302� 10.8 - Interface alarms on page 306

Page 296: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

282

10.1 Alarm attribute overview

> crocusShdsl<Tt|Cv>totalAlarmLevelalarmInfo

notRespondingalarmSyncLossconfigChangedaccessremoteAlarmunknownStatepowerSupply1CvFail1

powerSupply2CvFail1

powerSupply48VFail1

remotePowerFail1

coldBootwarmBootlocalPowerFailcodeConsistencyFailconfigConsistencyFail

Action: Cold Boot

>> linealarmInfo

linkDowntestActiveinvalidNumRepeatersremotePowerFail

>>> linePair[ ]2

alarmInfolinkDownlineAttenuationsignalNoiseerrSecRatioExceededsevErrSecRatioExceededbBErrRatioExceeded

>>>> pwrSource3

alarmInfoharwareFailmanuallyDisabledmanagementDisablednoCurrentoverCurrent

1. CV only2. in case of a 2P version, two linePair objects are present: linePair [1] and linePair [2]3. not present by default, has to be added

Page 297: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

283

>> repeater[ ]4

alarmInfolinkDown

>>> networkLinePair[ ]2

alarmInfolinkDownlineAttenuationsignalNoiseerrSecRatioExceededsevErrSecRatioExceededbBErrRatioExceeded

>>> customerLinePair[ ]2

alarmInfolinkDownlineAttenuationsignalNoiseerrSecRatioExceededsevErrSecRatioExceededbBErrRatioExceeded

>> end4

alarmInfolinkDown

>>> linePair[ ]2

alarmInfolinkDownlineAttenuationsignalNoiseerrSecRatioExceededsevErrSecRatioExceededbBErrRatioExceeded

>> rs530, v35, v365

alarmInfolinkDownlossOfTimingbackupTiming

4. not present by default, is added automatically when setting the line/eocHandling attribute5. only present when the corresponding interface is used

Page 298: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

284

>> g7035

alarmInfolinkDownaislfa6

rai6

sqlossOfTiming

>> dualPort5

>>> g703alarmInfo

linkDownaislfaraisqlossOfTiming

>>> rs530alarmInfo

linkDownlossOfTimingbackupTiming

>> bridge, router5

alarmInfolinkDown

6. G703 Nx64 only

Page 299: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

285

10.2 Introducing the alarm attributes

Before discussing the alarm attributes of the Crocus SHDSL in detail, some general information on the alarm attributes of the Crocus SHDSL is given.

The following gives an overview of this section.

� 10.2.1 - Configuration alarm attributes on page 286� 10.2.2 - General alarm attributes on page 289� 10.2.3 - Alarm signalling on page 291

Page 300: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

286

10.2.1 Configuration alarm attributes

This section describes the following alarm attributes:

� crocusShdsl<Tt|Cv>/�/alarmMask on page 287� crocusShdsl<Tt|Cv>/�/alarmLevel on page 287� crocusShdsl<Tt|Cv>/�/remoteAlarmMask on page 288� crocusShdsl<Tt|Cv>/�/alarmContactHighMask on page 288� crocusShdsl<Tt|Cv>/�/alarmContactLowMask on page 288

Page 301: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

287

This section explains the attributes that allow you to configure the alarm behaviour of the Crocus SHDSL. These configuration alarm attributes are:

crocusShdsl<Tt|Cv>/�/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 11 - TMA subsystem picture of the Crocus SHDSL on page 309).

The alarms in the alarmMask attribute have the following values:

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).

crocusShdsl<Tt|Cv>/�/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 crocusSh-dsl<Tt|Cv>.

Value Is the active alarm being forwarded to the central management system? Does the active alarm cause a change of colour in the subsystem picture?

enabled Yes. So the alarm is unmasked.

disabled No. So the alarm is masked.

Page 302: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

288

crocusShdsl<Tt|Cv>/�/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.

By default, all the alarms in the remoteAlarmMask are set to disabled.

crocusShdsl<Tt|Cv>/�/alarmContactHighMask

This attribute is present on the CV only.

The alarmContactHighMask 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.� the high alarm contacts of the CN4 card nest are driven.

By default, all the alarms in the alarmContactHighMask are set to disabled.

crocusShdsl<Tt|Cv>/�/alarmContactLowMask

This attribute is present on the CV only.

The alarmContactLowMask 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.� the low alarm contacts of the CN4 card nest are driven.

By default, all the alarms in the alarmContactLowMask are set to disabled.

Using the remote alarm and the high and low alarm contacts of the CN4 card nest, you could perform alarm signalling. For more information, refer to 10.2.3 - Alarm signalling on page 291.

Page 303: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

289

10.2.2 General alarm attributes

This section describes the following alarm attributes:

� crocusShdsl<Tt|Cv>/totalAlarmLevel on page 290� crocusShdsl<Tt|Cv>/�/alarmInfo on page 290

Page 304: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

290

This section explains the general alarm attributes. These are:

crocusShdsl<Tt|Cv>/totalAlarmLevel

This attribute is only present in the top object of the containment tree of the Crocus SHDSL, crocusSh-dsl<Tt|Cv>.

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.

crocusShdsl<Tt|Cv>/�/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 Displays for the corresponding object �

discriminator the total number of alarm status changes in this object since the last cold boot.

currentAlarms the current alarm status of this object.

previousAlarms the previous alarm status of this object.

alarmMask the alarmMask as configured in the Configuration group.

alarmLevel the alarmLevel as configured in the Configuration group.

Page 305: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

291

10.2.3 Alarm signalling

If you do not have a central management system, you could perform alarm signalling with the alarm con-tacts of the CN4 card nest.

Example

Suppose the following situation:

� On a remote Crocus SHDSL TT the configChanged alarm of the Crocus SHDSL object is set to enabled in the remoteAlarmMask. In other words: crocusShdsl<Tt|Cv>/remoteAlarmMask/configChanged = enabled.

� On a central Crocus SHDSL CV the remoteAlarm of the top object is set to enabled in the alarmCon-tactHighMask. In other words: crocusShdsl<Tt|Cv>/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 Situation Result

1 Someone changes the configuration of the Crocus SHDSL TT.

On the Crocus SHDSL TT the configChanged alarm becomes active.

2 On the Crocus SHDSL TT the configChanged alarm is enabled in the remoteAlarmMask.

A remote alarm is sent to the Crocus SHDSL CV.

3 On the Crocus SHDSL CV the remoteAlarm is enabled in the alarmContactHighMask.

The high alarm contacts of the CN4 card nest close.

4 The high alarm contacts of the CN4 card nest close.

The light bulb lights up.

Page 306: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

292

10.3 General alarms

This section describes the following alarm attributes:

� crocusShdsl<Tt|Cv>/alarmInfo on page 293

This section describes the following action:

� crocusShdsl<Tt|Cv>/Cold Boot on page 294

Refer to 10.2 - Introducing the alarm attributes on page 285 for the general alarm attributes.

Page 307: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

293

crocusShdsl<Tt|Cv>/alarmInfo

The different alarms related to the crocusShdsl<Tt|Cv> 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 alarmLevel

notResponding when the Crocus SHDSL does not respond on the polling session of the management concentrator.

enabled 4

alarmSyncLoss when the internal alarm buffer overflows. enabled 4

configChanged when the configuration of the Crocus SHDSL is changed.

disabled 1

access when a management session is started on the Crocus SHDSL itself. This alarm is not activated when the management session is established through a management con-centrator.

Example

The alarm �

� is activated in case of a TMA, TMA CLI, terminal (CLI or ATWIN) or EasyCon-nect session via the control connector of the Crocus SHDSL.

� is not activated in case of any manage-ment session (TMA, terminal, Telnet, HTTP, etc.) established through a man-agement concentrator on the Crocus SHDSL.

disabled 1

remoteAlarm when the remote Crocus SHDSL is in alarm condition.

disabled 0

unknownState each time a new Crocus SHDSL is added to the network and before the management concentrator has completed a first suc-cessful polling session.

disabled 0

powerSupply1CvFail(CV only)

when the upper power supply in the CN4 card nest is not present or fails.This alarm exists on the CV only.

disabled 3

powerSupply2CvFail(CV only)

when the lower power supply in the CN4 card nest is not present or fails.

This alarm exists on the CV only.

disabled 3

Page 308: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

294

crocusShdsl<Tt|Cv>/Cold Boot

This action will reboot the Crocus SHDSL while the power stays up (the Crocus SHDSL also reboots if it is powered down and up again).

powerSupply48VFail(CV only)

when the directly connected -48 Vdc on the CN4 card nest is no longer present. This means that the 115/230 Vac back-up power supply has taken over.

This alarm exists on the CV only.

disabled 3

remotePowerFail(CV only)

when the remote Crocus SHDSL is no longer powered. The remote power fail mechanism on the Crocus SHDSL com-plies with the G.SHDSL standard.

This alarm exists on the CV only.

disabled 3

coldBoot when the Crocus SHDSL performs a cold boot.

disabled 1

warmBoot when the Crocus SHDSL performs a warm boot.

disabled 1

codeConsistencyFail when the software consistency imposed by the management concentrator on the Cro-cus SHDSL fails. For example, because of a loss of contact.

On the management concentrator, check the status attribute nmsgroup/softConsisten-cyStatus to determine the problem.

disabled 1

configConsistencyFail when the configuration consistency imposed by the management concentrator on the Crocus SHDSL fails. For example, because of a loss of contact.On the man-agement concentrator, check the status attributes nmsgroup/objectTable/configState and configDiag to determine the problem.

disabled 1

The alarm � is generated � Default value

alarmMask alarmLevel

Page 309: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

295

10.4 Line alarms

This section describes the following alarm attribute:

� crocusShdsl<Tt|Cv>/line/alarmInfo on page 296

Refer to 10.2 - Introducing the alarm attributes on page 285 for the general alarm attributes.

Page 310: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

296

crocusShdsl<Tt|Cv>/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 alarmLevel

linkDown when no data link towards the remote Cro-cus SHDSL is present.It does not neces-sarily 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.

enabled 3

invalidNumRepeaters 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.The actual number of repeaters discovered by the Crocus SHDSL can be seen in the line/numDiscoveredRepeaters status attribute.

disabled 1

testActive when a test is active. disabled 1

remotePowerFail(CV only)

when the remote Crocus SHDSL is no longer powered. The remote power fail mechanism on the Crocus SHDSL com-plies with the G.SHDSL standard.This alarm exists on the CV only.

disabled 3

Page 311: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

297

10.5 Line pair alarms

This section describes the following alarm attributes:

� crocusShdsl<Tt|Cv>/line/linePair[ ]/alarmInfo on page 298

In case of a Crocus SHDSL 2P, two linePair objects are present: linePair [1] and linePair [2].

Refer to 10.2 - Introducing the alarm attributes on page 285 for the general alarm attributes.

Page 312: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

298

crocusShdsl<Tt|Cv>/line/linePair[ ]/alarmInfo

The different alarms related to the linePair[ ] object together with their explanation and their default alarm-Mask and alarmLevel value are given in the following table:

The alarm � is generated � Default value

alarmMask alarmLevel

linkDown when no data link towards the remote Cro-cus SHDSL 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 link-Down alarm is generated.

enabled 3

lineAttenuation when the line attenuation exceeds the value configured in the line/linkAlarmThresh-olds 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/eocHan-dling configuration attribute is set to alarm-Configuration, the central SHDSL device forces the remote SHDSL device to use the linkAlarmThresholds/lineAttenuation as config-ured on the central device.

For more information, refer to �

� 6.2.2 - The EOC handling attribute on page 83

� 6.2.4 - EOC retrieved information on page 84

disabled 1

Page 313: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

299

signalNoise when the signal noise exceeds the value configured in the line/linkAlarmThresholds con-figuration attribute for at least 10 seconds. The alarm is cleared when the signal noise drops below this value for at least 10 sec-onds.

Note however that in case the line/eocHan-dling configuration attribute is set to alarm-Configuration, 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 �

� 6.2.2 - The EOC handling attribute on page 83

� 6.2.4 - EOC retrieved information on page 84

disabled 1

errSecRatioExceeded when the errored seconds ratio exceeds the value configured in the line/linkAlarm-Thresholds configuration attribute within a 2 hour period1. The alarm is cleared when the errored seconds ratio drops below this value within a 2 hour period.

disabled 1

sevErrSecRatioExceeded when the severely errored seconds ratio exceeds the value configured in the line/linkAlarmThresholds configuration attribute within a 2 hour period1. The alarm is cleared when the severely errored seconds ratio drops below this value within a 2 hour period.

disabled 2

bBErrRatioExceeded when the background block error ratio exceeds the value configured in the line/linkAlarmThresholds configuration attribute within a 2 hour period1. The alarm is cleared when the background block error ratio drops below this value within a 2 hour period.

disabled 1

1. The 2 hour periods run synchronous with the 2 hour periods of the line/h2Line performance attribute. Because alarms are raised or cleared within 2 hour periods, there is a delay in the alarm status. For example, suppose that in the first minute of a 2 hour period the errSecRatioEx-ceeded value is exceeded, then the errSecRatioExceeded alarm is raised. The alarm stays on for the remainder of the 2 hour period. The alarm is only cleared if also in the next 2 hour period the errSecRatioExceeded value is not exceeded.

The alarm � is generated � Default value

alarmMask alarmLevel

Page 314: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

300

10.6 Remote power alarms

This section describes the following alarm attributes:

- crocusShdsl<Tt|Cv>/line/linePair[ ]/pwrSource/alarmInfo on page 301

See 10.3 - General alarms on page 292 for the general alarm attributes.

Page 315: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

301

crocusShdsl<Tt|Cv>/line/linePair[ ]/pwrSource/alarmInfo

The different alarms related to the pwrSource objects together with their explanation and their default alarm-Mask and alarmLevel value are given in the following table:

The alarm� is generated� Default value

alarmMask alarmLevel

hardwareFail when the Remote Power source module is defective.

enabled 3

manuallyDisabled when the Remote Power source module has been disabled by the dedicated hard-ware strap on the Remote Power source module PCB. In this case it is not possible to enable remote powering via a manage-ment tool.

disabled 1

managementDisabled when the Remote Power source module has been disabled using the configuration attribute pwrSource. Refer to 7.5 - Remote power configuration attributes on page 181

disabled 1

noCurrent only has to deliver a current smaller than 15 mA. This might indicate that:

� the remote modem is fed by a power � supply and therefore does not require

remote power over the line.� the remote modem is defective and

therefore does not longer require supply current.

� the Remote Power source module is defective.

� the line is interrupted.

disabled 1

overCurrent has to deliver a current higher than 60 mA. This might indicate that:

� the remote modem is defective and a short circuit has occurred.

� the Remote Power source module is defective.

� the line is short circuited.

enabled 2

Page 316: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

302

10.7 Repeater and end alarms

This section describes the following alarm attributes:

� crocusShdsl<Tt|Cv>/end/linePair[ ]/alarmInfo on page 303

� 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 6.2 - Configuring EOC handling on page 82

� 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 6.2.4 - EOC retrieved information on page 84.

� The repeater[ ] and end objects contain the same attributes, therefore only the attributes of the end object are listed here.

� When the Crocus SHDSL is configured for 1 pair operation, the repeater[ ] and end[ ] objects networ-kLinePair[2] and customerLinePair[2] still appear in the containment tree (although 1 pair operation has been configured).

Page 317: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

303

crocusShdsl<Tt|Cv>/end/linePair[ ]/alarmInfo

The different alarms related to the linePair[ ] object together with their explanation and their default alarm-Mask and alarmLevel value are given in the following table:l

The alarm � is generated � Default value

alarmMask alarmLevel

linkDown when no data link towards the remote Cro-cus SHDSL 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 link-Down alarm is generated.

enabled 3

lineAttenuation when the line attenuation exceeds the value configured in the line/linkAlarmThresh-olds 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/eocHan-dling configuration attribute is set to alarm-Configuration, the central SHDSL device forces the remote SHDSL device and any intermediary repeater to use the linkAlarm-Thresholds/lineAttenuation as configured on the central device.

For more information, refer to �

� 6.2.2 - The EOC handling attribute on page 83

� 6.2.4 - EOC retrieved information on page 84

disabled 1

Page 318: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

304

signalNoise when the signal noise exceeds the value configured in the line/linkAlarmThresholds con-figuration 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/eocHan-dling configuration attribute is set to alarm-Configuration, the central SHDSL device forces the remote SHDSL device and any intermediary repeater to use the linkAlarm-Thresholds/signalNoise as configured on the central device.

For more information, refer to �

� 6.2.2 - The EOC handling attribute on page 83

� 6.2.4 - EOC retrieved information on page 84

disabled 1

errSecRatioExceeded when the errored seconds ratio exceeds the value configured in the line/linkAlarm-Thresholds configuration attribute of the local device within a 2 hour period1. The alarm is cleared when the errored seconds ratio drops below this value within a 2 hour period.

disabled 1

sevErrSecRatio-Exceeded when the severely errored seconds ratio exceeds the value configured in the line/linkAlarmThresholds configuration attribute of the local device within a 2 hour period1. The alarm is cleared when the severely errored seconds ratio drops below this value within a 2 hour period.

disabled 2

bBErrRatioExceeded when the background block error ratio exceeds the value configured in the line/linkAlarmThresholds configuration attribute of the local device within a 2 hour period1. The alarm is cleared when the background block error ratio drops below this value within a 2 hour period.

disabled 1

The alarm � is generated � Default value

alarmMask alarmLevel

Page 319: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

305

1. The 2 hour periods run synchronous with the 2 hour periods of the line/h2Line performance attribute. Because alarms are raised or cleared within 2 hour periods, there is a delay in the alarm status. For example, suppose that in the first minute of a 2 hour period the errSecRatioEx-ceeded value is exceeded, then the errSecRatioExceeded alarm is raised. The alarm stays on for the remainder of the 2 hour period. The alarm is only cleared if also in the next 2 hour period the errSecRatioExceeded value is not exceeded.

Page 320: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

306

10.8 Interface alarms

This section describes the following alarm attributes:

� crocusShdsl<Tt|Cv>/<dteInterface>/alarmInfo on page 307

Refer to 10.2 - Introducing the alarm attributes on page 285 for the general alarm attributes.

Page 321: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

307

crocusShdsl<Tt|Cv>/<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 alarmLevel

linkDown(for RS530, V35, V36)

when no RTS signal is detected. I.e. the connection between the Crocus SHDSL and the DTE is down.The linkDown alarm is only generated if the attribute rtsControl is set to external. If the attribute rtsControl is set to internal, the linkDown alarm will never be generated.

enabled 3

linkDown(for X21)

when no valid C signal is detected. I.e. the connection between the Crocus SHDSL and the DTE is down.

enabled 3

linkDown(for G703 and G703 Nx64k)

when there is a loss of signal. I.e. the trans-mit data is no longer present.

enabled 3

linkDown(for Bridge)

when there is no connection with the LAN. I.e. the LAN is not connected or no valid LAN signals are present.

enabled 3

linkDown(for Router)

when there is no connection between the router and the Crocus SHDSL. Because this connection is made by the interface connector, it is highly unlikely that this alarm will be generated. However, when it does occur it might indicate that the router interface is faulty.

enabled 3

ais(G703 and G703 Nx64k only)

when an Alarm Indication Signal (AIS) has been detected in the incoming G703 trans-mit data. It means the application has detected an error.

disabled 2

lfa(G703 Nx64k only)

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.)

disabled 2

Page 322: m Crocus SHDSL

Crocus SHDSL Chapter 10

Reference manual Alarm attributes

308

rai(G703 Nx64k only)

when a Remote Alarm Indication signal (RAI) has been detected in the incoming receive data. RAI means the far-end equip-ment has a problem with the signal it is receiving from the local equipment.

disabled 2

sq(G703 and G703 Nx64k only)

when the sqThreshold value, i.e. the number 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 gen-erated.Refer to the configuration attributes sqThreshold and sqTime for more information.

disabled 2

lossOfTiming(not for Bridge and Router)

when an external clocking mode is config-ured but the external clock signal is not present. In that case the Crocus SHDSL switches to internal clocking mode.

enabled 3

backupTiming(RS530, V35, V36, X21 only)

when a preferred clocking mode is config-ured but the external clock signal is not present. In that case the Crocus SHDSL switches to alternative clocking mode.

disabled 2

The alarm � is generated � Default value

alarmMask alarmLevel

Page 323: m Crocus SHDSL

Crocus SHDSL Chapter 11

User manual TMA subsystem picture of the Crocus SHDSL

309

11 TMA subsystem picture of the Crocus SHDSL

The subsystem picture is a TMA tool which visualises the status information of the Crocus SHDSL. This chapter explains how to display the subsystem picture, and how to interpret the visual indications. The following gives an overview of this chapter.

� 11.1 - Displaying the subsystem picture on page 310� 11.2 - Subsystem picture elements on page 311

Note that the figures in this chapter are those of a Crocus SHDSL. Although the subsystem picture of the CV has a different layout, the interpretation of the visual indications is the same.

Page 324: m Crocus SHDSL

Crocus SHDSL Chapter 11

User manual TMA subsystem picture of the Crocus SHDSL

310

11.1 Displaying the subsystem picture

To display the subsystem picture of the Crocus SHDSL, proceed as follows:

Step Action

1 Open a TMA session on the Crocus SHDSL. Refer to 4.1 - Starting TMA on the Crocus SHDSL on page 58.

2 In the TMA window, press on the subsystem picture button: .

The subsystem picture is displayed:

3 To close the subsystem picture, press .

Page 325: m Crocus SHDSL

Crocus SHDSL Chapter 11

User manual TMA subsystem picture of the Crocus SHDSL

311

11.2 Subsystem picture elements

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 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.

Page 326: m Crocus SHDSL

Crocus SHDSL Chapter 11

User manual TMA subsystem picture of the Crocus SHDSL

312

The table below gives an overview of the subsystem picture elements and what they indicate.

Element Description

LED indicators They reflect the actual status of the Crocus SHDSL. The LED indication on the subsystem picture corresponds with the LED indication on the Crocus SHDSL itself. For more information on the interpretation of the LEDs, refer to 2.10 - Front panel LED indicators on page 40.

DTE interface This reflects the status of the DTE interface. The possible indications are:

� none: If the DTE interface slot in the subsystem picture is blank, it means that no DTE interface module was present at power-up.

� 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.

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 10.2.1 - Configuration alarm attributes on page 286.

� In case of a Router interface the LAN interface connector displays the opera-tional status between the Router interface and the Crocus SHDSL. This implies that as soon as you insert a Router interface in the Crocus SHDSL the LAN interface colours green, disregarding of the operational status of the Router interface itself. For that information you have to connect to the Router interface.

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 10.2.1 - Configuration alarm attributes on page 286.

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).

Page 327: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

313

12 Software download

This chapter explains how to download new loader and application software (also called firmware) into the flash memory of the Crocus SHDSL. The following gives an overview of this chapter.

� 12.1 - What is boot, loader and application software? on page 314� 12.2 - Important download issues on page 318� 12.3 - Downloading with TMA on page 319� 12.4 - Downloading with TML on page 320� 12.5 - Downloading in loader mode on page 321� 12.6 - Downloading in boot mode on page 322� 12.7 - Downloading via a management concentrator on page 323

Page 328: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

314

12.1 What is boot, loader and application software?

This section explains the difference between boot, loader and application software. The following gives an overview of this section.

� 12.1.1 - What is boot software? on page 315� 12.1.2 - What is loader software? on page 316� 12.1.3 - What is application software? on page 317

Page 329: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

315

12.1.1 What is boot software?

What is boot software?

The boot software takes care of the start-up of the Crocus SHDSL. It is located on the lowest software level.

Functionality in boot mode

In boot mode you can only download loader software to the Crocus SHDSL.

The boot mode DIP switch

You can force the Crocus SHDSL in boot mode using a DIP switch. This is necessary in case you want to download new loader software.

How to identify the Crocus SHDSL runs in boot mode?

When the Crocus SHDSL runs in boot mode �

� the PWR LED is on� the RXD and TXD LED are in a random state� all other LEDs are off.

Page 330: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

316

12.1.2 What is loader software?

What is loader software?

The loader software takes care of the download of application software to the Crocus SHDSL. It is located on the middle software level.

When you start a download of application software while in application mode, the Crocus SHDSL auto-matically falls back to loader mode.

Functionality in loader mode

In loader mode the Crocus SHDSL has limited functionality. In loader mode you can �

� download application software to the local Crocus SHDSL� download application software over the line to a remote Crocus SHDSL.

However, while in loader mode the Crocus SHDSL can not �

� transfer data� be accessed with TMA� be configured.

The loader mode DIP switch

You can force the Crocus SHDSL 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 runs in loader mode?

When the Crocus SHDSL runs in loader mode �

� the PWR LED is on� the TST LED is on.

When the Crocus SHDSL switches from loader mode to application mode, the TST LED flashes 5 times.

Page 331: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

317

12.1.3 What is application software?

What is application software?

The application software, also called firmware, completely controls the Crocus SHDSL. It is located on the highest software level.

Functionality in application mode

In application mode the Crocus SHDSL has full functionality.

Page 332: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

318

12.2 Important download issues

� When downloading new application software, there is a software / hardware combination that has a long service down time and one that has a short service down time (less than 3 minutes). To find out which is which, refer to 1.4 - Application software overview on page 7.

� When you upgrade the application software of a à, do not power off the Crocus SHDSL until the TST LED stops blinking. Else the application software upgrade will fail.

� When a Crocus SHDSL is managed by a management concentrator (i.e. it is present in the manage-ment concentrator its objectTable and being polled), it is no longer possible to download software through the Crocus SHDSL its control connector using TMA or TML. Instead, use the software distri-bution 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.

� When you download new loader software, you also have to download the application software again.

� It is not possible to explicitly download software to modem B of a Crocus SHDSL CV Twin. This because a Crocus SHDSL CV Twin uses the same software for both modem A and B. However, it is possible to download software to a router interface inserted in modem B or to modem B its remote counterpart.

� You can not download application code to a Crocus SHDSL through a G703 interface (using the SA-bits, refer to 6.11.6 - Configuring the management data on a G703 interface on page 140). This because when you start the download, the Crocus SHDSL falls into loader mode. In this mode, the DTE interface is not supported (i.e. it is not running).

Page 333: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

319

12.3 Downloading with TMA

To download application software with TMA, proceed as follows:

Step Action

1 Establish a link between TMA and the Crocus SHDSL through the control connector. Refer to 4.1 - Starting TMA on the Crocus SHDSL on page 58.

2 In the TMA window select Tools → Download�

3 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 and will be between 9600 bps and 115200 bps.

4 In the TMA - Download window, select the Configuration tab, and press Add�

5 In the Remote filename window:

1. Select the filename you want 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 falls back to loader mode, then a DOS window opens and shows the download progress.

Page 334: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

320

12.4 Downloading with TML

When downloading with TMA (as explained in the previous section), you actually evoke TML (Telindus Memory Loader) through TMA. You can also use TML without opening TMA.

To download application software with TML, proceed as follows:

Step Action

1 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 as shown in the following figure:

2 Open a DOS window on your computer.

3 Go to the directory where the TML executable is located. Typically this isC:\Program Files\TMA.

4 Place the software file you want to download in this directory.

5 Type the following command to download:

� application software: tml -c1 -v -f<Txxxxxxx.00>@CONTROL

where �

� tml is the executable (Telindus Memory Loader) to download files to the Telindus devices through their control port

� -c1 specifies the COM port of the computer connected to the Crocus SHDSL (in this example COM1)

� -v returns graphical information on the download status� -f<Txxxxxxx.00> is the software file you want to download (e.g. T1212001.00)� CONTROL (in capitals!) specifies that the destination is a flash bank of the Crocus

SHDSL.

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.

Page 335: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

321

12.5 Downloading in loader mode

When a download of application software has failed or when a flash memory error occurs, the Crocus SHDSL 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 inoperative and inaccessible to TMA. In that case, new application software can still be downloaded by forcing the Crocus SHDSL in loader mode. This is done by means of the loader mode DIP switch (refer to3.1.2 - DIP switches of the TT on page 48 and 3.2.2 - DIP switches of the CV on page 53.

To download application software to a Crocus SHDSL in loader mode, proceed as follows:

Step Action

1 Disconnect the Crocus SHDSL from the power supply.

2 Set DIP switch bank DS1 position 1 to off.

To locate this DIP switch bank and for the DIP switch setting procedure, refer to Chapter 3 - DIP switches and straps of the Crocus SHDSL on page 45.

3 Reconnect the power supply to the Crocus SHDSL.

⇒The Crocus SHDSL is now in loader mode.

4 Now proceed as explained in 12.4 - Downloading with TML on page 320.

5 When the download is finished, disconnect the Crocus SHDSL from the power supply again.

6 Reset DIP switch bank DS1 position 1 to on.

7 Reconnect the power supply to the Crocus SHDSL.

Page 336: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

322

12.6 Downloading in boot mode

When a download of loader software has failed or when a flash memory error occurs, it may be possible that the loader software becomes corrupt making the Crocus SHDSL inoperative and inaccessible to TMA. In that case, new loader software can still be downloaded by forcing the Crocus SHDSL in boot mode. This is done by means of the boot mode DIP switch:

To download loader software to a Crocus SHDSL in boot mode, proceed as follows:

DIP switch name DS1 no. Setting Function

boot mode 1 (TT & CV) on Normal operation.

off Start up in boot mode.

Step Action

1 Disconnect the Crocus SHDSL from the power supply.

2 Set DIP switch bank DS1 position 1 to off.

To locate this DIP switch bank and for the DIP switch setting procedure, refer to Chapter 3 - DIP switches and straps of the Crocus SHDSL on page 45.

3 Reconnect the power supply to the Crocus SHDSL.

⇒The Crocus SHDSL is now in boot mode.

4 Now proceed as explained in 12.4 - Downloading with TML on page 320.

5 When the download is finished, disconnect the Crocus SHDSL from the power supply again.

6 Reset DIP switch bank DS1 position 1 to on.

7 Reconnect the power supply to the Crocus SHDSL.

Page 337: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

323

12.7 Downloading via a management concentrator

If many Crocus SHDSL Card Version modems need a software update, it is more efficient to use the software distribution feature of the management concentrator (e.g. Orchid 1003 LAN or Telindus 1035 Orchid). In that case, the software file that is present on the file system of the management concentrator is downloaded over the high speed bus to the Crocus SHDSL CV.

Also the Crocus SHDSL CVs their remote counterparts (which are often Table Tops) can get a software update using the management concentrator its software distribution feature.

For more information, refer to the manual of the management concentrator.

Page 338: m Crocus SHDSL

Crocus SHDSL Chapter 12

User manual Software download

324

Page 339: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

325

13 Diagnostic tests

This chapter describes the diagnostic tests of the Crocus SHDSL. The following gives an overview of this chapter.

� 13.1 - Introducing the diagnostic tests on page 326� 13.2 - Line tests on page 327� 13.3 - Interface tests on page 335� 13.4 - Repeater tests on page 336

Page 340: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

326

13.1 Introducing the diagnostic tests

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.

Example

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.

� Depending how you start a test using the keyboard or the EasyConnect, the originator (and hence the priority level) differs. If you start a test using the keyboard or the EasyConnect �- via the test "window" of the Crocus SHDSL (refer to 5.5 - The test window on page 77), then the

originator is called keyboard.- by browsing the model using the testActivation action in the line object / status group (refer to 5.6 -

The model browsing window on page 78), then the originator is called nms (network management system).

� 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 7.3 - Line configuration attributes on page 168). This attribute determines how long a test lasts.

Diagnostic tests can be generated by � with the priority level �

the management system, high.

the keyboard, medium.

the application via the interface, low.

the remote Crocus SHDSL,(RDL test only) low.

Phase Action Result

1 Start an interface test, for example AL. The AL test is started.

2 Start a test in TMA, for example RDL. The AL test stops, and the RDL test starts. This because the interface test has a lower priority than the TMA test.

3 Stop the TMA test. The interface test, in this case AL, is restarted.

Page 341: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

327

13.2 Line tests

This section describes the diagnostic tests you can start on the line of the Crocus SHDSL. The following gives an overview of this section.

� 13.2.1 - The line test action on page 328� 13.2.2 - Error test on page 330� 13.2.3 - Analogue loop on page 331� 13.2.4 - Remote digital loop on page 332� 13.2.5 - Digital loop on page 334

Page 342: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

328

13.2.1 The line test action

This section describes the following test attributes:

� crocusShdsl<Tt|Cv>/line/testActivation on page 329� crocusShdsl<Tt|Cv>/line/testDuration on page 329

Page 343: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

329

The location of the testActivation attribute in the Crocus SHDSL containment tree is:

crocusShdsl<Tt|Cv>/line/testActivation

Use this action to perform a test on the Crocus SHDSL. These tests are use-ful to trace possible problems. Possible tests are: no, al, dl, rdl, et, alEt, rdlEt.

To execute a test, proceed as follows:

crocusShdsl<Tt|Cv>/line/testDuration

Use the testDuration attribute to set the time-out period of diagnostic tests. Tests are automatically terminated after this time-out period.

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).

Step Action

1 In the TMA window, select the object line and the group Performance or Status.

2 In the action window of TMA, click the left mouse button on the field under the heading Argument Value.

⇒A drop down box appears.

3 In the drop down box, select the test you want to execute.

4 Press the right mouse button and select Execute.

(Status + Performance group)

Default:00000d 00h 03m 00sRange: 00000d 00h 00m 01s -

00000d 18h 12m 15s

Page 344: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

330

13.2.2 Error test

Initiating the ET test activates the internal error test pattern generator and detector. Possible errors which are received by the detector are accumulated in an internal register. The amount of errors can be seen with TMA, namely in the status attribute errorCount of the line object. The error LED on the front panel will also light.

When the central modem uses a Dual Port G703-Serial interface and the remote modem uses a different interface, then starting an ET test on the remote modem only gives erroneous results.

How to use this test?

Example:

Clocking during an ET test

When an ET test is activated, the Crocus SHDSL switches to internal clocking mode.

Phase Description

1 Start an ET test on the local Crocus SHDSL.

⇒A test pattern is sent down the line.

2 Start an ET test on the remote Crocus SHDSL.

⇒The detector of the remote Crocus SHDSL receives this test pattern, and looks for possible errors in the pattern. The quantity of errors could be an indication of the line quality.

Page 345: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

331

13.2.3 Analogue loop

Initiating the AL test establishes an analogue loop on the local Crocus SHDSL. This loop is compliant to loop 3 as described in the ITU-T recommendation V.54.

The loop is situated immediately behind the analogue part of the local Crocus SHDSL, schematically rep-resented as follows:

How to use this test?

Example:

In combination with the ET test, the AL test can also be used as a self-test of the Crocus SHDSL.

Clocking during an AL test

The following table shows what happens with the clocking on the Crocus SHDSL when an AL test is acti-vated:

Phase Description

1 Start an AL test on the local Crocus SHDSL.

⇒An analogue loop is established on the local Crocus SHDSL.

2 Send data with the application.

⇒If this data is received again by the application, the connection between the DTE and the Crocus SHDSL is OK. If not, it is possible that there is a bad connection between the DTE and the Crocus SHDSL.

If the Crocus SHDSL is in � and an AL test is activated, then it �

internal clocking mode remains in internal clocking mode.

external clocking mode remains in external clocking mode.

slave receive clocking mode switches to internal clocking mode.

Page 346: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

332

13.2.4 Remote digital loop

Initiating the RDL test establishes a digital loop on the remote Crocus SHDSL. This loop is compliant to loop 2 as described in the ITU-T recommendation V.54.

The loop is situated immediately behind the digital part of the remote Crocus SHDSL, schematically rep-resented as follows:

Make sure that on the remote Crocus SHDSL the rdlDetect attribute is set to enabled (refer to 7.6 - DTE Interface configuration attributes on page 183). Else it is not possible to initiate an RDL test on the remote.

How to use this test?

Example:

Phase Description

1 Start an RDL-ET test on the local Crocus SHDSL.

⇒A digital loop is established on the remote Crocus SHDSL and a test pattern is sent down the line.

2 Because the remote side is in a digital loop, the test pattern returns to the local Crocus SHDSL.

3 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.

Page 347: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

333

Clocking during an RDL test

The following table shows what happens with the clocking on the Crocus SHDSL when an RDL test is activated:

If the � Crocus SHDSL is in � and an RDL test is activated, then it �.

local internal clocking mode remains in internal clocking mode.

external clocking mode remains in external clocking mode.

slave receive clocking mode switches to internal clocking mode.

remote any clocking mode switches to slave receive clock-ing mode.

Page 348: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

334

13.2.5 Digital loop

Initiating the DL test also establishes a digital loop, but on the local Crocus SHDSL itself. This loop is compliant to loop 2 as described in the ITU-T recommendation V.54.

The loop is situated immediately behind the digital part of the remote Crocus SHDSL, schematically rep-resented as follows:

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 (as with RDL), but on the local Crocus SHDSL. This can be necessary when, for example, the remote Crocus SHDSL is unable to initiate a remote digital loop test.

Clocking during a DL test

When a DL test is activated, the Crocus SHDSL switches to slave receive clocking mode.

Page 349: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

335

13.3 Interface tests

For some DTE interfaces it is possible that the application (the DTE) initiates a test on the Crocus SHDSL 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.

� Note that also these tests are automatically terminated after the time-out period as set using the test-Duration attribute.

� The interface tests can be disabled via the tests attribute.

Available tests Description

Analog loop (AL) For �

� RS530, V35 and V36 the activation of the AL test signal (circuit 141)� G703 Nx64k the sending of the Sa6 bit sequence 1111

� initiates an analogue loop (loop 3) on the local Crocus SHDSL, in compliance with ITU-T recommendation V.54. Refer to 13.2.3 - Analogue loop on page 331.

Remote Digital Loop (RDL)

For �

� RS530, V35 and V36 the activation of the RDL test signal (circuit 140)� G703 Nx64k the sending of the Sa6 bit sequence 1010

� initiates a digital loop (loop 2) on the remote Crocus SHDSL, in compliance with ITU-T recommendation V.54. Refer to 13.2.4 - Remote digital loop on page 332.

Page 350: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

336

13.4 Repeater tests

This section describes the following test attributes:

� crocusShdsl<Tt|Cv>/repeater/loopbackActivation on page 337� crocusShdsl<Tt|Cv>/line/testDuration on page 337

Page 351: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

337

The location of the loopbackActivation attribute in the Crocus SHDSL containment tree is:

crocusShdsl<Tt|Cv>/repeater/loopbackActivation

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 (dou-ble-click the loopbackActivation string). Stop the loop by selecting the action argument value clearAllMainte-nanceStates 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 alarmConfig-

uration.� The loopbackActivation action argument value noAction does nothing. It is only present to have a default

value.

crocusShdsl<Tt|Cv>/line/testDuration

Use the testDuration attribute to set the time-out period of diagnostic tests. Tests are automatically terminated after this time-out period.

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).

Note that the Crocus SHDSL Repeater rounds off these values. If you set the testDuration attribute to a value under 1 minute, then this becomes 1 minute on the Crocus SHDSL Repeater. A value between 1 and 2 minutes becomes 2 minutes on the Crocus SHDSL Repeater. Etc.

(Status group)

Default:00000d 00h 03m 00sRange: 00000d 00h 00m 01s -

00000d 18h 12m 15s

Page 352: m Crocus SHDSL

Crocus SHDSL Chapter 13

User manual Diagnostic tests

338

Page 353: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

339

14 Technical specifications

This chapter gives the technical specifications of the Crocus SHDSL. The following gives an overview of this chapter.

� 14.1 - Crocus SHDSL types on page 340� 14.2 - Line specifications on page 340� 14.3 - RJ45 - RJ12 adapter specifications on page 342� 14.4 - Maximum covered distance on a noise free line on page 343� 14.5 - G703 interface specifications on page 344� 14.6 - RS530 interface specifications on page 345� 14.7 - Management interface connectors on page 347� 14.8 - Control connector on page 348� 14.9 - Diagnostic tests on page 349� 14.10 - Power requirements on page 349� 14.11 - Environmental compliance on page 350� 14.12 - Safety compliance on page 351� 14.13 - Over-voltage and over-current protection compliance on page 351� 14.14 - EMC compliance on page 351� 14.15 - Mechanical dimensions on page 351

Page 354: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

340

14.1 Crocus SHDSL types

The following Crocus SHDSL types exist:

� desktop units (Table Top or TT):- separate 115/230Vac and -48Vdc versions- separate 1 pair and 2 pair versions

� rack-mount units (Card Version or CV):- 1 pair version: 2 modems per card- 2 pair version: 1 modem per card

14.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, unavaila-

bility 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).

Page 355: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

341

� The following table shows the connector layout of the RJ45 line connector.

Pin Signal Figure

1 not used

2 not used

3 line 21

1. For a Crocus SHDSL 2P (2 pair) version only

4 line 1

5 line 1

6 line 21

7 not used

8 not used

Page 356: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

342

14.3 RJ45 - RJ12 adapter specifications

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.

The following table shows the connector layout of the RJ12 adapter connector.

Pin Signal Figure

1 not used

2 line 21

1. For a Crocus SHDSL 2P (2 pair) version only

3 line 1

4 line 1

5 line 21

6 not used

Page 357: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

343

14.4 Maximum covered distance on a noise free line

These values are valid starting from Crocus SHDSL PCB revision 1.2 and firmware revision T2141/00800, T2145/00600 and T2136/01300 and higher.

SHDSL signal to noise ratio values for error free transmission:

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 perform-ance tests with noise, a noise margin of 6dB is usually taken (matching S/N ratio 29dB). From experi-ence, it can be concluded that a 27dB S/N ratio gives no errors, at 25dB errors are rare.

Covered distance (km)

Line speed (kbps) Wire diameter (mm)

1P 2P 0.4 0.5 0.6 0.7 0.8 0.9 1,1

64 128 11,0 15,1 21,5 22,5 27,2 34,6 39,3

128 256 8,0 11,0 15,6 16,4 19,8 25,2 28,6

256 512 8,2 11,3 16,0 16,8 20,3 25,8 29,3

512 1024 7,2 9,9 14,0 14,7 17,8 22,7 25,7

1024 2048 5,5 7,6 10,7 11,3 13,6 17,3 19,6

1536 3072 4,0 5,5 7,8 8,2 9,9 12,6 14,3

2048 4096 4,2 5,8 8,2 8,6 10,4 13,2 15

2304 4608 4,0 5,5 7,8 8,2 9,9 12,6 14,3

Page 358: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

344

14.5 G703 interface specifications

Some of the G703 interface specifications are related to the device it is used in (in this case the Crocus SHDSL). Therefore the G703 interface specifications are listed below:

� 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 align-ment 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 Signal DCE Figure

1 receive A (+) output

2 receive B (-) output

3 signal ground -

4 transmit A (+) input

5 transmit B (-) input

6 signal ground -

7 not used -

8 not used -

Page 359: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

345

14.6 RS530 interface specifications

� Connector: 25 pins subD, female (DCE). The following figure shows the connector layout:

� Connector compliance: - directly compliant with RS530, RS530A- compliant through adapter cable with V.35, V.36, (RS449), X.21, V.24 (RS232)

� Applicable standards ITU-T V.10, V.11� Cable to be used: shielded twisted pair� Operation modes: RS-530, RS-530A, V.35 Interim, V.36, X.21 or V.24 (configurable)� Speed:

- 1 pair: up to 2304 kbps- 2 pair: up to 4608 kbps

� Clocking: internal, external, slave receive, auto.

Page 360: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

346

� The following table shows the connector layout of the RS530 connector:

Pin Signal Abbreviation DCE V10/V11/V28 operation

1 Shield - - -

2 Transmit Data A TXD A In V.11/V.28

3 Received Data A RXD A Out V.11/V.28

5 Clear to Send A CTS A Out V.10/V.11/V.28

6 DCE Ready A DSR A Out V.10/V.11/V.28

7 Signal Ground SGND - -

8 Received Line Signal Detector A DCD A Out V.10/V.11/V.28

9 Received Signal Element Timing B RXCLK B Out V.11

10 Received Line Signal Detector B DCD B Out V.10/V.11

11 External Signal Element Timing B EXTCLK B In V.11

12 Transmit Signal Element Timing B TXCLK B Out V.11

13 Clear To Send B CTS B Out V.10/V.11

14 Transmit Data B TXD B In V.11

15 Transmitted Signal Element Timing A TXCLK A Out V.11/V.28

16 Received Data B RXD B Out V.11

17 Received Signal Element Timing A RXCLK A Out V.11/V.28

18 Local Loopback AL In V.10/V.28

20 Data terminal Ready A DTR A In V.10/V.11/V.28

21 Remote Loopback RDL In V.10/V.28

22 DCE Ready B DSR B Out V.10/V.11

23 Data terminal Ready B DTR B In V.10/V.11

24 External Signal Element Timing A EXTCLK A In V.11/V.28

25 Test Indicator TI Out V.10/V.28

Page 361: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

347

14.7 Management interface connectors

The possible management interface connectors are:

For all available management tools, refer to 1.7 - Management overview on page 9.

Management interface con-nector

Connector type Speed

asynchronous through the con-trol connector

9 pins subD (on the Crocus SHDSL)

9600 bps, 8+N

synchronous through a man-agement concentrator and the high speed bus

backplane DIN (on the CN4 card nest)

800 kbps

Page 362: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

348

14.8 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:

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 Orchid 1003 LAN management concentrator can be ordered at the distributor (code 149220).

Card Version

� 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 connection to the Orchid 1003 LAN management concentrator is made through the high speed bus of the CN4 card nest. Refer to the CN4 manual for more information.

Pin Signal DCE Figure

1 not used -

2 NMS RxD output

3 NMS TxD input

4 not used -

5 GND -

6 not used -

7 not used -

8 not used -

9 not used -

Page 363: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

349

14.9 Diagnostic tests

The following diagnostic test are available on the Crocus SHDSL:

� Analogue Loop (AL)� Digital Loop (DL)� Remote Digital Loop (RDL)� Error Test (ET) (test pattern ITU 2E15-1)

14.10 Power requirements

The power requirements for the different Crocus SHDSL types are as follows:

Type Voltage Frequency Maximum power

Table Top 1P 230 Vac (85 à 265 Vac) 45 - 60 Hz 9 W

-48 Vdc (-36 Vdc à -72 Vdc) - 4 W

Table Top 2P 230 Vac (85 à 265 Vac) 45 - 60 Hz 15 W

-48 Vdc (-36 Vdc à -72 Vdc) - 8 W

Card Version 1P -48 Vdc (-36 Vdc à -72 Vdc) - 8 W

Card Version 2P -48 Vdc (-36 Vdc à -72 Vdc) - 16 W

Page 364: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

350

14.11 Environmental compliance

� Storage conditions: ETSI ETS 300 019-1-1 Class 1.1. In addition, the storage temperature has to be between -25 to +70°C

� Transport conditions: ETSI ETS 300 019-1-2 Class 2.3� Stationary use conditions: ETSI ETS 300 019-1-3 Class 3.2. In addition, the requirements below

apply:- relative humidity 5 to 95% non-condensing and ambient operational temperature -5 to 45°C

or- relative humidity 0 to 95% non-condensing and ambient operational temperature -10 to 50°C

� Maximum altitude: 3000m� International protection (IP) class of protection against solid and liquids: IP40

Page 365: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

351

14.12 Safety compliance

� EN60950� Class 1 equipment for Table Tops with 115/230 Vac internal power supply.� Class 3 equipment for �

- Table Tops with 115/230 Vac external power supply adapter- Table Tops with -48 Vdc internal power supply- Card Versions.

14.13 Over-voltage and over-current protection compliance

The over-voltage and over-current protection complies with ITU-T K.44 and ETSI ETS 300 386-2 recom-mendations.

14.14 EMC compliance

� EN55022 B Emissions� EN55024 Immunity� EN61000-3-2 Harmonics� EN61000-3-3 Voltage fluctuations and flicker� EN61000-4-2 ESD� EN61000-4-3 Radiated immunity� EN61000-4-4 EFT/burst� EN61000-4-5 Surge� EN61000-4-6 Conducted immunity� EN61000-4-8 Power magnetic field immunity� EN61000-4-11 Voltage dips & drops� ENV50204 Radiated immunity against digital radio telephone

14.15 Mechanical dimensions

The mechanical dimensions are as follows:

Dimensions Table Top

height (mm) 45

width (mm) 220

depth (mm) 215 excl. interface

235 incl. interface

weight (kg) 0.75 (excl. interface)

Page 366: m Crocus SHDSL

Crocus SHDSL Chapter 14

User manual Technical specifications

352

Page 367: m Crocus SHDSL

Crocus SHDSL

Annex

353

Annex

Page 368: m Crocus SHDSL

Crocus SHDSL

Annex

354

Page 369: m Crocus SHDSL

Crocus SHDSL Annex A:

Annex product information

355

Annex A: product information

The following table displays the product information of the Crocus SHDSL basic units.

Sales code Product name Description

180055 Crocus SHDSL RJ45 TT BU VAC 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)

180056 Crocus SHDSL RJ45 TT BU 48VDC 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)

180054 Crocus SHDSL +LCD RJ45 TT BU VAC 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)

180053 Crocus SHDSL 2P RJ45 TT BU VAC 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)

171976 Crocus SHDSL 2P TT BU 48VDC 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

177938 Crocus SHDSL 2P +LCD TT BU VAC 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!)

177939 Crocus SHDSL 2P +LCD TT BU 48VDC 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 !)

182598 Crocus SHDSL TT BU 24VDC Crocus SHDSL table top on 1 line pair, Basic Unit, no interface provided. Interface module available as separate sales item. 24Vdc powered. On request-check production. New product. Check release and availability date.

182599 Crocus SHDSL 2P TT BU 24VDC Crocus SHDSL table top on 1 line pair, Basic Unit, no interface provided. Interface module available as separate sales item. 24Vdc powered. On request-check production. New product. Check release and availability date.

180057 Crocus SHDSL 2 TWIN-CV BU 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: 171285)

171977 Crocus SHDSL 2P TWIN-CV BU 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.

Page 370: m Crocus SHDSL

Crocus SHDSL Annex A:

Annex product information

356

181080 CROCUS SHDSL TT G703 230VAC Crocus SHDSL table top on 1 line pair with fixed G703 onboard interface. Includes European 230VAC external power adapter

178713 CROCUS SHDSL 2P TT G703 RP 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)

178715 CROCUS SHDSL TT G703 RP 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)

181082 CROCUS SHDSL TT RS530 230VAC 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

181083 CROCUS SHDSL TT RS530 NPWR 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

178716 CROCUS SHDSL TT RS530 RP 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.

178714 CROCUS SHDSL 2P TT RS530 RP 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.

Sales code Product name Description

Page 371: m Crocus SHDSL

Crocus SHDSL Annex A:

Annex product information

357

The following table displays the product information of the Crocus SHDSL DTE interfaces.

Sales code Product name Description

143666 V35 INTF. CROCUS Plug-in modular interface V.35 transparent.

142199 V36 INTF.CROCUS Plug-in modular interface V.36 transparent.

161611 RS-530 INTF.CROCUS Plug-in modular interface RS-530 transparent.

142200 X21 INTF.CROCUS Plug-in modular interface X.21 transparent.

175253 G703 INTF 2M CROCUS G.703 interface module for the Crocus SHDSL. Can only work with line speed 2Mbit/s. BNC connectors.

175254 G703 INTF NX64K CROCUS G.703 interface module for the Crocus SHDSL. Can work with line speeds below 2Mbit/s. BNC connectors.

150466 BRIDGE INTF.CROCUS Plug-in modular interface Ethernet Bridge for direct UTP LAN connection. IEEE 802.3 compliant.

161613 ROUTER 2M INTF.CROCUS Plug-in modular interface Ethernet Router for direct UTP LAN connection. IEEE 802.3 compliant. Limited to 2M.

177455 ROUTER 10M INTF.CROCUS Plug-in modular interface Ethernet Router for direct UTP LAN connection. IEEE 802.3 compliant. Up to 10M.

Page 372: m Crocus SHDSL

Crocus SHDSL Annex A:

Annex product information

358

The following table displays cables to be used in combination with the Crocus SHDSL RS530:

Sales code Product name Description

182968 CBL DCE RS530 (DB25M) - DTE V36M SH 2M Data-Cabling for TOP items: Serial CBL. See doc Telindus Access Product Quick Reference. For application, details and pin layout see document: -Data cables- on the Telindus Product dBase. -> Cable layout-19

182969 CBL DCE RS530 (DB25M) - DTE V36M SH 5M Data-Cabling for TOP items: Serial CBL. See doc Telindus Access Product Quick Reference. For application, details and pin layout see document: -Data cables- on the Telindus Product dBase. -> Cable layout-19

182970 CBL DCE RS530 (DB25M) - DTE X21M SH 2M Data-Cabling for TOP items: Serial CBL. See doc Telindus Access Product Quick Reference. For application, details and pin layout see document: -Data cables- on the Telindus Product dBase. -> Cable layout-20

182971 CBL DCE RS530 (DB25M) - DTE X21M SH 5M Data-Cabling for TOP items: Serial CBL. See doc Telindus Access Product Quick Reference. For application, details and pin layout see document: -Data cables- on the Telindus Product dBase. -> Cable layout-20

Page 373: m Crocus SHDSL

Crocus SHDSL Index

Annex

1

Index

Numerics1 pair operation

Crocus SHDSL 1P CV Twin 32

2 pair operationCrocus SHDSL 1P CV Twin 32

Aabsolute addressing

use 135

action, what is 67

activatingconfiguration 151remote power source operation 36

alarm attributes 281configuration 286general 289introduction 285overview 282

alarm signalling 291

alarmsend 302general 292interface 306line 295line pair 297repeater 302

alternative clocking 93

analogue loop 331

application softwareoverview 7what is 314, 317

attribute - actionactivate configuration 166clearErrorCounter 225Cold Boot 218cold boot 167load default configuration 166load saved configuration 167loopbackActivation 236, 337maximumSpeedSearch 226testActivation 225

attribute - alarmalarmContactHighMask 288alarmContactLowMask 288alarmInfo 290, 293, 296, 298, 303, 307alarmLevel 287alarmMask 287Cold Boot 294remoteAlarmMask 288totalAlarmLevel 290

attribute - configurationaisDetection 193alarmContactHighMask

top object 165alarmContactLowMask

top object 165alarmLevel

dteInterface object 187, 190, 195, 201, 204

line object 178linePair object 180, 182top object 165

alarmMaskdteInterface object 187, 190, 195, 201,

204line object 178linePair object 180, 182top object 165

asymmetricPsd 174channel 80, 169clocking 90, 187, 190, 195, 201, 203cms2Address 206coding 129, 192consoleNoTrafficTimeOut 206crc4Insertion 129, 193ctrlPortProtocol 136, 207ctsDelay 185eocChannel 81, 175eocHandling 83, 175fallbackClocking 131, 197forwardTmaToCtrlPort 137, 165forwardTmaToLine 137, 165framing 119, 192IanFilter 200internalDmm 141, 208jitterAttenuation 129, 193lanFilter 132linkAlarmThresholds 176management 139, 178minLinePairSpeed 115, 171mode 80, 171multiplexingMode 130, 197name 178, 186, 189, 194, 200, 203numExpectedRepeaters 175pwrSource 182rdlDetect 187, 190, 195, 201, 204region 80, 169remoteAlarmMask

linePair object 182top object 165

retrain 171rtsControl 128, 185saBits 140, 194security 164serialMode 187speed 109, 186, 189, 200, 203speed2P 109, 186, 190, 200, 203sqThreshold 193sqTime 193

Page 374: m Crocus SHDSL

Crocus SHDSL Index

Annex

2

startupMargin 174stationClockFallback 130, 197sysContact 164sysLocation 164sysName 164testDuration 174, 329, 337tests 186, 194timeSlots 120, 192timingMode 88, 170transmitSampleClock 187, 190, 201, 203txEocMessages 175x21Conversion 131, 198xSignal 189

attribute - performance<h2/h24/d7>G703Performance 273<h2/h24/d7>G826Performance 274<h2/h24/d7>Line 267<h2/h24/d7>LineParameters 269<h2/h24/d7>Performance 270clearErrorCounter 267currUsedProcPower 278errorCount 267freeBlockCount 278freeDataBuffers 278freeMemory 278g703Performance 273g826Performance 274largestFreeBlockSize 278line 267lineParameters 269performance 270retrain 267taskInfo 279testActivation 267, 329totalDataBuffers 278totalMemory 278usedProcPower 279

attribute - statusactualBitRate 229ais 248alItu141 239asymmetricPsd 224bootVersion 217cardNestNumber 256cardSlotNumber 256configurationSaving 217ctsItu106 239dcdItu109 239deviceId 217dsrItu107 239eocAlarmThresholds 225, 234eocSoftVersion 234eocState 234errorCount 224extClockSource 240, 244flash1Version 218framerType 222ifClocking 241, 245, 249, 254

ifDescr 220, 240, 245, 248, 253ifOperStatus 220, 228, 242, 246, 250, 254ifSpeed 220, 228, 241, 245, 249, 254ifType 220, 241, 245, 249, 253indicator 244lfa 248lineAttenuation 229, 236linePairsSwapped 224loaderVersion 217los 248maxLinePairSpeed 221maxSpeedResult 223maxSpeedSearch 223messages 216minLinePairSpeed 220modemPosition 256numDiscoveredRepeaters 224rai 248rdlItu140 239region 224remIfClocking 240, 244, 253rtsItu105 239rxdItu104 239, 244, 248shdslVersion 234signalNoise 229, 236status 228, 231stepupThreshold 229sysDescr 216sysObjectID 216sysServices 216sysUpTime 216taskInfo 258testOriginator 223testStatus 223testType 222tiItu142 239timeSinceLastRetrain 228timeSlots 248transmitPower 229txdItu103 239, 244, 248vendorId 233vendorModel 233vendorSerial 233vendorSoftVersion 233version 231wanRxd 253wanTxd 253

attribute string, reading vii

attribute, what is 67

auto clockingbridge and router interfaces 103examples 106RS530, V35 and V36 interfaces 101X21 interface 104

auto speed mode, how works 111

auto-sensing 100

Page 375: m Crocus SHDSL

Crocus SHDSL Index

Annex

3

Bbasic configuration

passwords 147

basic line parametersconfiguring 80

boot softwarewhat is 314, 315

bridge interfaceauto clocking 103configuring 132interface configuration attributes 199interface status attributes 252

Ccard version

connecting the line 30inserting in the CN4 card nest 27inserting the DTE interface 31motherboard 52

changing DIP switch settingsof the CV 56of the TT 50

changing strap settingsof the CV 56of the TT 50

clockingalternative 93attribute 90preferred 93special points of interest on some interfaces

95

clocking and speed combinations 112

clocking decision sequences 97

clocking modeconfiguring 89

CN4 card nest 8filling 28inserting the card version 27line connector 29

compatibility with other SHDSL devices 154

configurationactivating 151alarm attributes 286

configuration actionsexecuting 149what is 150

configuration attributes 157general 163interface 183line 168line pair 179management 205

overview 158

configuration types 150

configuringbasic line parameters 80bridge interface 132clocking mode 89Dual Port G703-Serial interface 130EOC handling 82framing 118G703 interface 129interface specific attributes 127internal DMM function 141management attributes 133management data on a G703 interface 140management data on the line 139minimum line speed 113remote power 146RS530, V35 and V36 interfaces 128time slots 118timing mode 88user speed 108user speed and time slots 123user speed and time slots on the Dual Port

G703-Serial interface 122

connectingCrocus SHDSL CV 26Crocus SHDSL TT 20line to card version 30line to Table Top 24power supply 22

containment tree 68terminology 66what is 67

control connectorforwarding management data 137selecting the purpose 136specifications 348

conventions in this manualgraphical vtypographical iv

copyright notice iiCrocus SHDSL

attribute overview 69connecting the CV 26connecting the TT 20DIP switches 45features 4introduction 3managing 57product overview 5straps 45types 340

Crocus SHDSL 1P CV Twinchoosing 1 pair or 2 pair operation 32straps 55

Page 376: m Crocus SHDSL

Crocus SHDSL Index

Annex

4

Ddata carrier detect LED (DCD/109) 44

diagnostic tests 325introduction 326specifications 349

different clocking modesschematic overview 94

digital loop 334

DIP switch table, reading vi

DIP switches 45changing settings of the CV 56changing settings of the TT 50of the CV 51, 53of the TT 46, 48

displaying the subsystem picture 310

documentconventions

graphical vtypographical iv

copyright notice iifirmware version described in this viiiintended audience viiiorganisation ivproperties iistatements iiiyour feedback viii

downloadingin boot mode 322in loader mode 321via a management concentrator 323with TMA 319with TML 320

DTE interface overview 6Dual Port G703-Serial interface

configuring 130configuring the user speed and time slots 122interface clocking 96interface configuration attributes 196interface performance attributes 276interface status attributes 251

EEMC compliance

specifications 351

endalarms 302performance attributes 271status attributes 232

environmental compliancespecifications 350

EOCconfiguring handling 82discovering devices on the SHDSL line 84

EOC handling attribute 83retrieved information 84what is 83

error LED (AIS/ERR) 43

error test 330

exampleauto clocking 106management over the line and the control

port 142management over the line and the E1 inter-

face 144

executing configuration actions 149

external clock signalpresence 99

Ffeedback viii

filling an entire CN4 card nest 28

firmwareversion viii

fixed clocking modes 92

forwarding management data to the line and control connector 137

framed modeselecting 119, 123

framingconfiguring 118

front panel display 71"windows" 72connect remote window 78DTE window 76line window 75main window 73model browsing window 78test window 77version window 78

front panel LEDsindicators 40introduction 41

GG703 data

ordering 124

G703 interfaceconfiguring 129configuring management data 140interface clocking 96interface configuration attributes 191interface performance attributes 272interface status attributes 247specifications 344

general

Page 377: m Crocus SHDSL

Crocus SHDSL Index

Annex

5

alarm attributes 289alarms 292configuration attributes 163status attributes 215

group, what is 67

IIdentification viii

important download issues 318

important remarkon starting a TMA session 63on the minimum line pair speed 114

inserting the DTE interfacein the Card Version 31in the Table Top 25

installation and connection precautions 19

installingoptional remote power module 37

Installing and connecting 13

interfacealarms 306configuration attributes 183status attributes 237tests 335

interface clockingDual Port G703-Serial interface 96G703 interface 96X21 interface 95

interface configuration attributesbridge 199dual Port G703-Serial interface 196G703 interface 191router interface 202RS530, V35 and V36 184X21 interface 188

interface performance attributesDual Port G703-Serial interface 276G703 interface 272

interface specific attributesconfiguring 127

interface status attributesbridge interface 252dual Port G703-Serial interface 251G703 interface 247router interface 252RS530, V35 and V36 238X21 interface 243

internal DMM functionconfiguring 141

introductionalarm attributes 285Crocus SHDSL 3

diagnostic tests 326front panel LEDs 41management attributes 65performance terms 265performance timing 264TMA 59

Kkeyboard management

starting 64

LLED

data carrier detect (DCD/109) 44error(AIS/ERR) 43power (PWR) 42receive data (RXD/104) 44request to send (RTS/105) 43test(TST/142) 42transmit data (TXD/103) 44

LED indicatorsfront panel 40

linealarms 295configuration attributes 168configuring management data 139forwarding management data 137performance attributes 266specifications 340status attributes 219tests 327

line pairalarms 297configuration attributes 179performance attributes 268status attributes 227

line test action 328

load default configuration 151using a DIP switch 152

loader softwarewhat is 314, 316

low speed limitations on the G703 Nx64k inter-faces 125

Mmanagement

configuration attributes 205overview 9rules of thumb and remarks 134status attributes 255

management attributesconfiguring 133

management interface connectorsspecifications 347

Page 378: m Crocus SHDSL

Crocus SHDSL Index

Annex

6

management toolsentering passwords 148

managing the Crocus SHDSL 57

maximum covered distance on a noise free linespecifications 343

mechanical dimensionsspecifications 351

minimum line pair speedattribute 115important remark 114purpose 117

minimum line speedconfiguring 113

motherboardcard version 52Table Top 47

Oobject, what is 67

odd speeds, using 110

operating systemperformance attributes 277status 257

optional remote power moduleinstalling 37

orderingG703 data 124serial data 124

organisation of this manual ivover-current protection compliance

specifications 351

overviewalarm attributes 282application software 7configuration attributes 158DTE interface 6management 9performance attributes 260remote power operation 35status attributes 210

over-voltage protection compliancespecifications 351

Ppasswords

adding to the security table 148basic configuration 147entering in the different management tools

148

performance attributes 259end 271line 266

line pair 268operating system 277overview 260repeater 271

performance termsintroduction 265

performance timingintroduction 264

possible clocking modes versus DTE interface 91

Power back-off 8power LED (PWR) 42

power requirementsspecifications 349

power supplyconnecting 22

preferred clocking 93

presence of external clock signal 99

product information 355DTE interfaces 357

product overviewCrocus SHDSL 5

purpose of the minimum line pair speed 117

Rreading

a DIP switch table vian attribute string vii

receive data LED (RXD/104) 44

relative addressinguse 135

remarks onDIP switch for RP source operation 37, 54opening the housing 46remote power source operation 36selecting a site 16

remote digital loop 332

remote powerconfiguring 146status attributes 230what is 34

remote power operation 33overview 35

remote power source operationactivating 36

repeateralarms 302performance attributes 271status attributes 232tests 336

Page 379: m Crocus SHDSL

Crocus SHDSL Index

Annex

7

use 39

request to send LED (RTS/105) 43

RJ45 - RJ12 adapterspecifications 342

router interfaceauto clocking 103interface configuration attributes 202interface status attributes 252

RS530 interfaceautoclocking 101configuring 128interface configuration attributes 184interface status attributes 238

rules of thumb and remarks concerning manage-ment 134

Ssafety

instructions 14requirements iisafety compliance specifications 351

schematic overview of the different clocking modes 94

security tableadding passwords 148

selectinga site 16purpose of the control connector 136time slots 120unframed or framed mode 119, 123

serial dataordering 124

signal and protective ground interconnection 23

software download 313

special points of interest concerning clocking on some interfaces 95

specificationscontrol connector 348Crocus SHDSL types 340diagnostic tests 349EMC compliance 351environmental compliance 350G703 interface 344line 340management interface connectors 347maximum covered distance on a noise free

line 343mechanical dimensions 351over-current protection compliance 351over-voltage protection compliance 351power requirements 349RJ45 - RJ12 adapter 342safety compliance 351

speed attribute 109

starting a TMA sessionthrough a management concentrator 62through the control connector 60

starting keyboard management 64

starting TMA on the Crocus SHDSL 58

statements iiistatus attributes 209

end 232general 215interfaces 237line 219line pair 227managemant 255overview 210remote power 230repeater 232

step-by-step configuration 79

straps 45changing settings of the CV 56changing settings of the TT 50of the Crocus SHDSL 1P CV Twin 55of the CV 51of the TT 46, 49

structured value, what is 67

subsystem picturedisplay 310elements 311

TTable Top

connections 21inserting the DTE interface 25motherboard 47

technical specifications 339

test LED (TST/142) 42

time slotsconfiguring 118, 123selecting 120transposition 121

timing modeconfiguring 88

TMA subsystem picture 309

transmit data LED (TXD/103) 44

transpositiontime slots 121

troubleshooting 153

Uunframed mode

selecting 119, 123

Page 380: m Crocus SHDSL

Crocus SHDSL Index

Annex

8

unpacking 15

user speedauto speed mode, how works 111configuring 108, 123odd speeds, using 110speed attribute 109

usinga repeater 39relative or absolute addressing 135

VV35 interface

autoclocking 101configuring 128interface configuration attributes 184interface status attributes 238

V36 interfaceautoclocking 101configuring 128interface configuration attributes 184interface status attributes 238

value, what is 67

Wwall mounting 17

warningEMC 19ESD 19important safety instructions 14safety warning 14

what isapplication software 314, 317boot software 314, 315containment tree 67EOC 83loader software 314, 316remote power 34

XX21 interface

auto clocking 104interface clocking 95interface configuration attributes 188interface status attributes 243