M SHDSL

Crocus SHDSL
Crocus SHDSL
USER and REFERENCE MANUAL
Version: 1.5 181598
Telindus Technical Publications Geldenaaksebaan 335 B-3001 Leuven Belgium tel. +32 16 382011
Copyright, safety and statements Crocus SHDSL
Copyright notice
The information and descriptions contained in this publication are the property of Telindus. Such
information 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
The interfaces on the Crocus SHDSL should only be connected to circuit types as listed below.
Interface Connector Circuit
line RJ12 TNV-1
management subD SELV
Carefully read the safety instructions at the beginning of Chapter 2 - Installing and connecting the Crocus
SHDSL, page 11.
Version 1.5 03 December 2002

MRP 181598 TELiNDUS
ii
Crocus SHDSL Copyright, safety and statements
Statements
http://www.telindusproducts.com ! Products ! Choose a product ! Download certificates
Hereby, TELINDUS declares that this Crocus SHDSL is in compliance with the essential requirements
and other relevant provisions of Directive 1999/5/EC.
Bij deze verklaart TELINDUS dat deze Crocus SHDSL in overeenstemming is met de essentile
vereisten en andere relevante bepalingen van Richtlijn 1999/5/EC.
Par la prsente, TELINDUS dclare que ce Crocus SHDSL est en conformit avec les exigences
essentielles et autres articles applicables de la Directive 1999/5/EC.
Hiermit, TELINDUS erklrt da dieser Crocus SHDSL in Fgsamkeit ist mit den wesentlichen
Anforderungen 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 dems prescripciones relevantes de la Directiva 1999/5/CE.
A TELINDUS declara que o Crocus SHDSL cumpre os principais requisitos e outras disposies da
Directiva 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.
iii
Preface Crocus SHDSL
Preface
Organisation of this manual

This manual contains three main parts.
Part This part
User manual shows you how to install and connect the Crocus SHDSL.
Reference manual gives more detailed information on the Crocus SHDSL. It contains a complete
description for lookup purposes.
Annexes gives additional information.
The following table gives an overview of the chapters in the user manual.
Chapter This chapter
1 introduces the Crocus SHDSL.
2 explains how to install and connect the Crocus SHDSL. It also describes the front panel
LED indicators.
3 shows the position of the DIP switches and straps on the Crocus SHDSL motherboard. It
also reveals their function.
4 introduces the Telindus Maintenance Application (TMA) and keyboard management. It

also shows how to start a TMA or keyboard management session on the Crocus
SHDSL. Furthermore, it introduces the management attributes of the Crocus SHDSL.
5 teaches you the basics to configure the Crocus SHDSL, in a step-by-step manner.
6 describes the information that can be seen on the front panel display, in case your
Crocus SHDSL is equipped with a display and keyboard.
The following table gives an overview of the chapters in the reference manual.
Chapter This chapter
7, 8, 9, 10 describes the configuration, status, performance and alarm attributes, respectively.
11 displays and labels the different elements of the Telindus Maintenance Application
subsystem picture.
12 gives a software download procedure.
13 uncovers the available diagnostic test functions.
14 summarises the technical specifications of the Crocus SHDSL.
The following table gives an overview of the annexes.
Annex This annex
Annex A gives a list of abbreviations.
Annex B shows ordering information.
iv
Crocus SHDSL Preface
Conventions used in this manual

Typographical conventions
The following typographical conventions are used in this manual.
The format is used to indicate
Normal normal text.
Italic new or emphasised words

file names and directory paths, e.g. C:\Program Files\TMA\bin\Tma.exe
Computer computer output and code examples, e.g. NOK,1,1,Invalid command.

Computer Bold text you have to enter at the prompt, e.g. Get sysName.
Narrow objects and attributes in the containment tree of a device when they are
mentioned in the normal text. I.e. when they are not a part of computer input or
output.
Blue references to other parts in the manual, e.g. refer to Chapter xx - Technical
specifications.
Blue underlined a hyperlink to a web site, e.g. http://www.telindus.com
Icons
The following icons are used throughout the manual.
Icon Name Description
Remark Useful information or tips.
Caution Read the text that follows carefully in order to avoid damage to the
device.
Warning Read the text that follows carefully in order to avoid injury.
DIP switch A configuration attribute of the Crocus SHDSL which can be set with the
DIP switches.
Basic TMA A basic attribute of the Crocus SHDSL which can be set with the
parameter Telindus Maintenance Application (TMA).
Advanced TMA An advanced attribute of the Crocus SHDSL which can be set with the
parameter Telindus Maintenance Application (TMA).
Action An action which can be executed on the Crocus SHDSL with the
Telindus Maintenance Application (TMA).
v
Preface Crocus SHDSL
Hardware version
This manual describes the hardware of the Crocus SHDSL PCB version 1.2 and higher.
Application software version

This manual describes the features, containment tree and attributes of the Crocus SHDSL application
software version T2136/01200, T2145/00400 and T2141/00500. For more information on these different
application software types, refer to Section 1.4 - Application software overview.
Your feedback
Your satisfaction about this purchase is an extremely important priority to all of us at Telindus.
Accordingly, all electronic, functional and cosmetic aspects of this new unit have been carefully and
thoroughly tested and inspected. If any fault is found with this unit or should you have any other quality-
related comment concerning this delivery, please submit the Quality Comment Form on our web page at
http://www.telindusproducts.com/quality.
vi
Crocus SHDSL Table of contents
Table of contents
User manual................................................................................................1
1. Introducing the Crocus SHDSL.............................................................................. 3
1.1 Crocus SHDSL features ..................................................................................................4
1.2 Crocus SHDSL product overview ....................................................................................5
1.3 DTE interface overview ...................................................................................................6
1.4 Application software overview .........................................................................................7
1.5 Power back-off ................................................................................................................8
1.6 CN4 card nest .................................................................................................................8
1.7 Management overview ....................................................................................................9
2. Installing and connecting the Crocus SHDSL .................................................... 11

2.1 Safety instructions .........................................................................................................12
2.2 Unpacking .....................................................................................................................13
2.3 Selecting a site ..............................................................................................................14
2.4 Installation and connection precautions ........................................................................15
2.5 Connecting the Crocus SHDSL Table Top....................................................................16
2.6 Connecting the Crocus SHDSL Card Version ...............................................................22
2.7 Front panel LED indicators............................................................................................31
3. DIP switches and straps of the Crocus SHDSL.................................................. 37

3.1 DIP switches and straps of the Crocus SHDSL Table Top ...........................................38
3.2 DIP switches and straps of the Crocus SHDSL Card Version.......................................43
4. Managing the Crocus SHDSL............................................................................... 48

4.1 Starting TMA on the Crocus SHDSL .............................................................................49
4.2 Starting keyboard management on the Crocus SHDSL ................................................55
4.3 Introducing the management attributes of the Crocus SHDSL......................................56
5. Step-by-step configuration................................................................................... 61
5.1 Reading the configuration settings ................................................................................62
5.2 Loading the default configuration ..................................................................................64
5.3 Crocus SHDSL compatibility with other Telindus devices .............................................67
5.4 Configuring the line .......................................................................................................68
5.5 Selecting the timing mode .............................................................................................70
5.6 Configuring the clocking mode ......................................................................................71
5.7 Configuring the user speed ...........................................................................................89
5.8 Configuring the G703 time slots ....................................................................................93
5.9 Configuring the user speed and G703 time slots on the Dual Port G703-Serial
interface ..................................................................................................................................97
5.10 Configuring the interface specific attributes ................................................................100
5.11 Configuring the management attributes ......................................................................105
5.12 Activating the configuration .........................................................................................109
Continued on next page
vii
Table of contents Crocus SHDSL
Table of contents (continued)
6. The front panel display .......................................................................................110

6.1 The windows of the front panel display..................................................................... 111
6.2 The main window ........................................................................................................ 112
6.3 The line window .......................................................................................................... 113
6.4 The DTE window......................................................................................................... 114
6.5 The test window .......................................................................................................... 115
6.6 The model browsing window....................................................................................... 116
6.7 The connect remote window ....................................................................................... 116
6.8 The version window .................................................................................................... 116
Reference manual .................................................................................. 117

7. Configuration attributes......................................................................................119
7.1 Configuration attribute overview.................................................................................. 120
7.2 General configuration attributes .................................................................................. 122
7.3 Line configuration attributes ........................................................................................ 130
7.4 Line pair configuration attributes ................................................................................. 133
7.5 Interface configuration attributes................................................................................. 134
7.6 Management configuration attributes.......................................................................... 142
8. Status attributes ..................................................................................................144

8.1 Status attribute overview............................................................................................. 145
8.2 General status attributes ............................................................................................. 147
8.3 Line status attributes ................................................................................................... 150
8.4 Line pair status attributes ............................................................................................ 154
8.5 Interface status attributes............................................................................................ 155
8.6 Management status attributes..................................................................................... 163
8.7 Operating system status ............................................................................................. 164
9. Performance attributes .......................................................................................165

9.1 Performance attribute overview .................................................................................. 166
9.2 Introducing the performance attributes ....................................................................... 167
9.3 Line performance attributes ........................................................................................ 170
9.4 Line pair performance attributes ................................................................................. 171
9.5 G703 interface performance attributes........................................................................ 172
9.6 Dual Port G703-Serial interface performance attributes ............................................. 173
9.7 Operating system performance attributes ................................................................... 174
10. Alarm attributes ...................................................................................................176

10.1 Alarm attribute overview.............................................................................................. 177
10.2 Introducing the alarm attributes .................................................................................. 178
10.3 General alarms............................................................................................................ 183
10.4 Line alarms ................................................................................................................. 185
10.5 Line pair alarms .......................................................................................................... 186
10.6 Interface alarms .......................................................................................................... 187
viii
Crocus SHDSL Table of contents
Table of contents (continued)
11. TMA subsystem picture of the Crocus SHDSL................................................. 189

11.1 Displaying the subsystem picture................................................................................190
11.2 Subsystem picture elements .......................................................................................191
12. Software download ............................................................................................. 193

12.1 What is boot, loader and application software?...........................................................194
12.2 Important download issues..........................................................................................198
12.3 Downloading with TMA................................................................................................199
12.4 Downloading with TML ................................................................................................200
12.5 Downloading in loader mode.......................................................................................201
12.6 Downloading in boot mode..........................................................................................202
12.7 Downloading via the Orchid 1003 LAN .......................................................................203
13. Diagnostic tests .................................................................................................. 204

13.1 Introducing the diagnostic tests...................................................................................205
13.2 Error test......................................................................................................................206
13.3 Analogue loop .............................................................................................................207
13.4 Remote digital loop......................................................................................................208
13.5 Digital loop...................................................................................................................209
13.6 Interface tests..............................................................................................................210
14. Technical specifications..................................................................................... 211

14.1 Crocus SHDSL types ..................................................................................................212
14.2 Line specifications .......................................................................................................212
14.3 RJ45 RJ12 adapter specifications............................................................................213
14.4 Maximum covered distance on a noise free line .........................................................214
14.5 G703 interface specifications ......................................................................................215
14.6 Management interface connectors ..............................................................................216
14.7 Control connector ........................................................................................................216
14.8 Diagnostic tests ...........................................................................................................217
14.9 Power requirements ....................................................................................................217
14.10Environmental compliance ..........................................................................................217
14.11Safety compliance .......................................................................................................218
14.12Over-voltage and over-current protection compliance.................................................218
14.13EMC compliance .........................................................................................................218
14.14Mechanical dimensions ...............................................................................................218
Annexes ..................................................................................................219
Annex A: abbreviations............................................................................................. 221
Annex B: product information.................................................................................. 223
ix
List of figures Crocus SHDSL
List of figures
Figure 2.1: Rear view of the Crocus SHDSL TT 115/230 Vac model ......................................................17
Figure 2.2: Rear view of the Crocus SHDSL TT 48V model ....................................................................17
Figure 2.3: Front panel LED indicators of the Crocus SHDSL ....................................................................32
Figure 3.1: Position of the DIP switches and straps on the TT motherboard..............................................39
Figure 3.2: Position of the DIP switches and straps on the CV motherboard .............................................44
Figure 4.1: TMA window containing the Crocus SHDSL containment tree.................................................57
Figure 5.1: Internal preferred clocking.........................................................................................................76
Figure 5.2: Internal alternative clocking.......................................................................................................76
Figure 5.3: Slave receive preferred clocking ...............................................................................................76
Figure 5.4: Slave receive alternative clocking .............................................................................................76
Figure 5.5: External clocking .......................................................................................................................76
Figure 5.6: External loop-back clocking ......................................................................................................76
Figure 5.7: V35 and auto clocking V35 and auto clocking .......................................................................86
Figure 5.8: V35 and auto clocking X21 and auto clocking .......................................................................87
Figure 5.9: X21 and auto clocking X21 and auto clocking .......................................................................88
Figure 5.10: Bridge functionality ............................................................................................................... 104
Figure 7.1: Forwarding TMA management information............................................................................ 125
Figure 7.2: Relative addressing................................................................................................................ 142
Figure 7.3: Absolute addressing............................................................................................................... 142
x
Crocus SHDSL List of tables
List of tables
Table 2.1: Rear view of the Crocus SHDSL TT parts table .....................................................................17
Table 2.2: Connecting the power supply.....................................................................................................18
Table 2.3: Connecting the line to the TT .....................................................................................................20
Table 2.4: Inserting the DTE interface in the TT .........................................................................................21
Table 2.5: Inserting the CV in the CN4 card nest........................................................................................23
Table 2.6: Filling an entire CN4 card nest...................................................................................................24
Table 2.7: Parts of the CN4 line connector .................................................................................................25
Table 2.8: Connecting the line to the CV ....................................................................................................26
Table 2.9: Inserting the DTE interface in the CV.........................................................................................27
Table 2.10: Installing the optional wetting current module on the CV.........................................................30
Table 3.1: Overview of DIP switch bank DS1 of the TT ..............................................................................40
Table 3.2: Overview of strap ST9 of the TT ................................................................................................41
Table 3.3: Changing DIP switch and strap settings of the TT.....................................................................42
Table 3.4: Overview of DIP switch bank DS1 of the CV .............................................................................45
Table 3.5: Overview of DIP switch bank #ADS1 and #CDS1 of the CV .....................................................45
Table 3.6: Overview of straps ST2, ST4 and ST6 of the Crocus SHDSL 1P CV .......................................46
Table 3.7: Changing DIP switch and strap settings of the CV ....................................................................47
Table 4.1: Starting a TMA session through the control connector ..............................................................52
Table 4.2: Starting keyboard management .................................................................................................55
Table 4.3: Containment tree terminology ....................................................................................................58
Table 4.4: Objects of the Crocus SHDSL containment tree........................................................................59
Table 7.1: Entering passwords in the different management systems .....................................................123
Table 7.2: Correcting the security table ....................................................................................................124
Table 7.3: The non-active, active and default configuration .....................................................................127
Table 7.4: Activating a configuration .........................................................................................................127
Table 7.5: Loading the active configuration ..............................................................................................128
Table 7.6: Loading the default configuration .............................................................................................128
Table 7.7: Performing a cold boot .............................................................................................................129
Table 7.8: Relative and absolute addressing ............................................................................................142
Table 8.1: Executing a test........................................................................................................................152
Table 13.1: Diagnostic test originators......................................................................................................205
xi
Crocus SHDSL
User manual
User manual 1
Crocus SHDSL
2 User manual
Crocus SHDSL Introducing the Crocus SHDSL
1. Introducing the Crocus SHDSL

This chapter introduces the Crocus SHDSL. The following table gives an overview of this chapter.
Section Title Page
1.1 Crocus SHDSL features 4
1.2 Crocus SHDSL product overview 5
1.3 DTE interface overview 6
1.4 Application software overview 7
1.5 Power back-off 8
1.6 CN4 card nest 8
1.7 Management overview 9
User manual 3
Introducing the Crocus SHDSL Crocus SHDSL
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 two-wire 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 new 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 systems 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 10BaseT
connections with integrated bridge or 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 115/230 Vac and direct 48 Vdc powering can be used.
With TMA, 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 or by connecting an external LCD hand 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 application 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 information), 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.
4 User manual
1.2 Crocus SHDSL product overview

The following Crocus SHDSL types exist:
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
The following table gives a description of the used abbreviations:
Abbreviation In full Explanation
TT Table Top This is a stand-alone version of the Crocus SHDSL. It is

available with or without an LCD display and keyboard.
CV Card Version This card 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 card 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 The line connection is made over 1 line pair.
2P 2 pair The line connection is made over 2 line pairs.
Vac Volts - Alternate The modem has to be powered with 115 or 230 Vac.
Current
-48Vdc Volts - Direct The modem has to be powered with -48 Vdc.
Current
User manual 5
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.
V35 V.35 is only specified up to 2 Mbps. V35 interfaces with PCB version
0.2 or lower only support speeds up to 2 Mbps.
0.3 or higher support all user and corresponding line speeds, provided
short cables are used.
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.
10baseT Bridge All user and corresponding line speeds are supported.
10baseT Router 2M All user and corresponding line speeds up to 2304 kbps (hardware limitation).
10baseT Router 10M All user and corresponding line speeds are supported.
6 User manual
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:
Software PCB 0.x & long PCB 0.x & short PCB 1.x (3)
service down time (1) service down time (2)
boot T2135xxx T2135xxx T2140xxx
loader T2137003 T2137004 T2142xxx
application T2136xxx T2145xxx T2141xxx
(1)
With this boot, loader, application software and hardware combination the data traffic is interrupted
when downloading new application software into the Crocus SHDSL.
(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.
(3)
All revisions of this boot, loader, application software and hardware combination support non-
interrupted data traffic when downloading new application software.
For more information on downloading software, refer to Section 12 - Software download.
User manual 7
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
recommendation. It reduces the maximum transmit power level if the line conditions are sufficiently good
to operate at a lower transmit level.
Power back-off is performed by default (no configuration attribute). During the ITU-T G.994.1 handshake,
the two sides of the line mutually agree on the transmit level. The transmit level is lowered between 0 and
6 dB in steps of 1dB.
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.
8 User manual
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.
EasyConnect terminal
Connecting the Telindus EasyConnect hand-held terminal over a serial connection (i.e. through the
control connector) to the Crocus SHDSL, allows you to manage the Crocus SHDSL in the same way as
with keyboard management.
CLI and ATWIN

Connecting a VT100 terminal (emulation program) over a serial connection (i.e. through the control
connector) 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.
The Orchid 1003 LAN management concentrator

Connecting the Crocus SHDSL to the Orchid 1003 LAN management concentrator offers the following
possibilities:
Using the Orchid 1003 LAN as an IP proxy agent, you have the possibility to connect to the Crocus
SHDSL over an IP network. In that case you can establish an IP connection with the Crocus SHDSL
and 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 Orchid 1003 LAN as an IP proxy agent, refer to the Orchid
1003 LAN manual.
Using the Orchid 1003 LAN as an SNMP proxy agent, you can manage the Crocus SHDSL through
SNMP.
For more information on how to use the Orchid 1003 LAN as an SNMP proxy agent, refer to the
Orchid 1003 LAN manual.
The Orchid 1003 LAN allows you to manage the Crocus SHDSL with TMA for HP OpenView, the
Telindus integrated management application that runs on the HP OpenView platform.
To find out more about TMA for HP OpenView, refer to the TMA for HP OpenView manual.
User manual 9
Management overview (continued)
Management overview
The following table gives an overview of all the management possibilities and how you can connect them:
Management PC Crocus SHDSL connection PC Orchid connection

tool (Orchid 1003 LAN as proxy)
Serial IP Serial IP
Keyboard (1)
EasyConnect X X
CLI X (2) X (2) X (3)
ATWIN X (2) X (2) X (3)
TMA X X X
TMA CLI X X X
TMA for HPOV X
SNMP (4) X
Web Interface (5) X

(1)
Connection with the Crocus SHDSL is internal. Keyboard and LCD are not available on all models.
(2)
Using a VT100 terminal (emulation program).
(3)
Using Telnet.
(4)
Using any SNMP browser.
(5)
Using a web browser.
10 User manual
Crocus SHDSL Installing and connecting the Crocus SHDSL
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
skipping 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 table gives an overview of this chapter.
Section Title Page
2.1 Safety instructions 12
2.2 Unpacking 13
2.3 Selecting a site 14
2.4 Installation and connection precautions 15
2.5 Connecting the Crocus SHDSL Table Top 16
2.6 Connecting the Crocus SHDSL Card Version 22
2.7 Front panel LED indicators 31
User manual 11
Installing and connecting the Crocus SHDSL Crocus SHDSL
2.1 Safety instructions
IMPORTANT SAFETY INSTRUCTIONS

Unplug the unit from the wall power outlet or remove it from the card nest before installing, adjusting or
servicing.
The safety of this unit depends upon the third pin (ground pin) of the 3-wire grounding type plug. Do not
defeat this safety feature. If the power outlet at your site only has 2 pins, please consult a qualified
electrician.
ACHTUNG! WICHTIGE SICHERHEITSINSTRUKTIONEN

Vor smtlichen Arbeiten am Gert (Installation, Einstellungen, Reparaturen etc.) sollten Sie den
Netzstecker aus der Steckdose ziehen.
Die Sicherheit dieses Gertes ist abhngig von dem dritten Kontakt (dem Erdungspin) des 3-poligen
Steckers. Beachten Sie unbedingt diese Sicherheitsstandard. Sollten Sie nur eine ltere 2-polige
Steckdose zur Verfgung haben, lassen Sie diese von einem Elektriker gegen eine 3-polige Steckdose
auswechseln.
SAFETY WARNING
To avoid damage to the unit, please observe all procedures described in this chapter.
SICHERHEITSBESTIMMUNGEN
Um eine Beschdigung des Gertes zu verhindern, beachten Sie bitte unbedingt die
Sicherheitsbestimmungen, die in diesem Abschnitt beschrieben werden.
Ensure that the unit and its connected equipment all use the same AC power and ground, to reduce
noise interference and possible safety hazards caused by differences in ground or earth potentials.
12 User manual
2.2 Unpacking
Checking the shipping carton
Rough handling during shipping causes most early failures. Before installation, check the shipping carton
for signs of damage:
If the carton box is damaged, please place a claim with the carrier company immediately.
If the carton box 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
RJ45 to RJ12 adapter
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)
User manual 13
2.3 Selecting a site
WARNING
Always place the unit on its feet without blocking the air vents.
Do not stack multiple units directly onto each other, as stacking can cause heat build-up that could
damage the equipment.
ACHTUNG
Stellen Sie das Gert niemals seitlich, sondern nur auf den Fen auf und achten Sie darauf, da die
Lftungsschlitze an der Seitenverkleidung frei bleiben.
Stapeln Sie nicht mehrere Gerte direkt bereinander, dies kann zu einem Hitzestau fhren.
Install the unit in an area free of extreme temperatures, humidity, shock and vibration. Position it so that
you can easily see and access the front panel and its control indicators. Leave enough clearance at the
back for cables and wires. Position the unit within the correct distances for the different accesses and
within 2m of a power outlet.
14 User manual
2.4 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 Gert kann gespeist wurden durch ein IT Power System.
User manual 15
2.5 Connecting the Crocus SHDSL Table Top

This section explains how to connect the Crocus SHDSL TT. The following table gives an overview of this
section.
Section Title Page
2.5.1 Table Top connections 17
2.5.2 Connecting the power supply 18
2.5.3 Signal and protective ground interconnection 19
2.5.4 Connecting the line to the Table Top 20
2.5.5 Inserting the DTE interface in the Table Top 21
16 User manual
2.5.1 Table Top connections

All the connections have to be made at the back of the Crocus SHDSL Table Top. The following figure
gives a rear view of the Crocus SHDSL TT.
ON OFF
PWR WARNING! SEE BOTTOM CTRL LINE
1 2 3 4 5
Figure 2.1: Rear view of the Crocus SHDSL TT 115/230 Vac model
ON OFF
- 48V +
PWR CTRL LINE
1 2 3 4 5
Figure 2.2: Rear view of the Crocus SHDSL TT 48V model
The following table labels the different parts located at the back of the Crocus SHDSL TT.
Number Part
1 power switch
2 power inlet
3 DTE interface slot
4 DB9 control connector (sometimes also called auxiliary or NMS connector)
5 RJ45 line connector
Table 2.1: Rear view of the Crocus SHDSL TT parts table
User manual 17
2.5.2 Connecting the power supply

The following table explains how to connect the power supply. The Crocus SHDSL TT exists in two
different models:
TT model Connector type Connecting the power supply
115/230 Vac standard IEC For a 115/230 Vac model, connect the standard IEC power
power supply supply connector to the power inlet. Refer to Figure 2.1:
connector Rear view of the Crocus SHDSL TT 115/230 Vac model.
-48 Vdc 48 V power supply For a -48 Vdc model, a power supply connector is delivered
connector 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 connected to +, while the
negative voltage has to be connected to the -.
When the -48 Vdc power supply connector is wired,
connect it to the power inlet. Refer to Figure 2.2: Rear view
of the Crocus SHDSL TT 48V model.
Table 2.2: Connecting the power supply
18 User manual
2.5.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 Crocus SHDSL TT motherboard. For more information,
refer to Section 3.1.3 - Straps of the TT.
User manual 19
2.5.4 Connecting the line to the Table Top

In order to connect the line to the Table Top, proceed as follows:
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 Section 14.2 -
Line specifications and 14.3 - RJ45 RJ12 adapter specifications.
2 Plug the other end of the cable in the DSL outlet.

Crocus SHDSL TT DSL line outlet
line cable
Table 2.3: Connecting the line to the TT
For optimum performance, the used line pairs have to be properly twisted pairs.
20 User manual
2.5.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.
Table 2.4: Inserting the DTE interface in the TT
User manual 21
2.6 Connecting the Crocus SHDSL Card Version

This section explains how to connect the Crocus SHDSL CV. The following table gives an overview of
this section.
Section Title Page
2.6.1 Inserting the Card Version in the CN4 card nest 23
2.6.2 Filling an entire CN4 card nest 24
2.6.3 The CN4 card nest line connector 25
2.6.4 Connecting the line to the Card Version 26
2.6.5 Inserting the DTE interface in the Card Version 27
2.6.6 Choosing 1 pair or 2 pair operation on the Crocus SHDSL 1P CV Twin 28
2.6.7 Enabling wetting current operation 29
2.6.8 Installing the optional wetting current module 30
22 User manual
2.6.1 Inserting the Card Version in the CN4 card nest

The Crocus SHDSL 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:
15 slots
3 Fasten the two screws located at the front of the CV.
Table 2.5: Inserting the CV in the CN4 card nest
User manual 23
2.6.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.
Table 2.6: Filling an entire CN4 card nest
24 User manual
2.6.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:
Indication What to connect Figure
L1 1P CV Twin: line pair of modem A

1P CV Twin as 2P(): line pair 1 of modem A
2P CV Twin: line pair 1 of modem A L1
L2
L2 2P CV Twin: line pair 2 of modem A
L3
L3 1P CV Twin: line pair of modem B L4

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
Table 2.7: Parts of the CN4 line connector
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 positions L1 and L3 are
used to connect respectively line pair 1 and 2 of modem A. For more information, refer to Section 3.2.3 -
Straps of the Crocus SHDSL 1P CV Twin.
For optimum performance, the used line pairs have to be properly twisted pairs.
User manual 25
2.6.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:
Step Action
1 Slide the wires of the line pair in the connector positions as indicated in Section 2.6.3 -
The CN4 card nest line connector.
2 Fasten the line connector screws.
Table 2.8: Connecting the line to the CV
For more information on how to connect the line pairs to the CN4 card nest, refer to the manual of the
CN4 card nest.
26 User manual
2.6.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:
3 Fasten the two screws of the DTE interface.
4 When the DTE interface is present, connect the application.
Table 2.9: Inserting the DTE interface in the CV
User manual 27
2.6.6 Choosing 1 pair or 2 pair operation on the Crocus SHDSL 1P CV Twin

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
Section 3.2.3 - Straps of the Crocus SHDSL 1P CV Twin.
28 User manual
2.6.7 Enabling wetting current operation

The Crocus SHDSL CV can be equipped with an optional wetting current module. This allows wetting
current operation on the Crocus SHDSL CV.
What is wetting current?

Wetting current is a small DC current (5 10 mA) which is injected on the line to prevent contact
oxidation.
Only a Crocus SHDSL CV can act as a wetting current source. A standard Crocus SHDSL TT acts as
wetting current sink.
How to enable wetting current?

In order to activate wetting current on the Crocus SHDSL CV
install the optional wetting current module. Refer to 2.6.8 - Installing the optional wetting current
module.
set the appropriate DIP switches located on the Crocus SHDSL CV motherboard. Refer to 3.2.2 - DIP
switches of the CV.
User manual 29
2.6.8 Installing the optional wetting current module

To enable wetting current operation on the Crocus SHDSL CV, you have to install the optional wetting
current module on the CV motherboard. 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 wetting current module and position the connectors of the module over
the pin headers ST8 and ST9 of the CV motherboard. Make sure the component side of
the module is facing down.
3 Push the module down so that the pin headers slide in the connectors.
4 Turn the CV around, i.e. with the DIP switches, straps, etc. facing down.
5 Fasten the screw of the module through the hole in the CV motherboard.
The optional wetting current module is installed.
Table 2.10: Installing the optional wetting current module on the CV
#ADS1
ST9
#CDS1
VIEW
ST8
position module above pin

headers and push down
wetting current module
component side
down ST9 ST8
Crocus SHDSL CV
motherboard
fasten screw
30 User manual
2.7 Front panel LED indicators

This section gives an overview of the front panel LEDs and what they indicate. The following table gives
an overview of this section.
Section Title Page
2.7.1 Introducing the front panel LEDs 32
2.7.2 Power LED (PWR) 33
2.7.3 Test LED (TST/142) 33
2.7.4 Error LED (AIS/ERR) 34
2.7.5 Request to send LED (RTS/105) 35
2.7.6 Transmit data LED (TXD/103) 36
2.7.7 Receive data LED (RXD/104) 36
2.7.8 Data carrier detect LED (DCD/109) 36
User manual 31
2.7.1 Introducing the front panel LEDs

When all the connections are made and the Crocus SHDSL is 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 TT and CV:
Figure 2.3: 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.
32 User manual
2.7.2 Power LED (PWR)

This LED indicates that the Crocus SHDSL is connected to the power supply and is switched on.
2.7.3 Test LED (TST/142)

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:
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 Section 12.1.2 - What is loader software?.
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.
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.
User manual 33
2.7.4 Error LED (AIS/ERR)

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:
LED status Description Error priority
off No error has occurred. -
monitoring The Crocus SHDSL its internal error test pattern generator / high
detector (ET) is active and received bit errors.
continuously on In case a G703 interface is used, it indicates an Alarm Indication medium

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).
flashing Alarm signalling is active and an alarm has been detected. low
(CV only) For more information on alarm signalling, refer to Section 10.2.3
- Alarm signalling.
34 User manual
2.7.5 Request to send LED (RTS/105)

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
following:
Interface What the RTS LED indicates
RS530, V35, The LED is on when an RTS signal is detected. I.e. the connection between the
V36, HSSI 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 Both interfaces have to be up (as defined above), before the RTS LED lights up.
interfaces
User manual 35
2.7.6 Transmit data LED (TXD/103)

This LED monitors the data sent by the application (Data Terminal Equipment) to the DTE interface
module 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.7.7 Receive data LED (RXD/104)

This LED monitors the data sent to the application (Data Terminal Equipment) by the DTE interface
module 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.7.8 Data carrier detect LED (DCD/109)

This LED indicates whether the central Crocus SHDSL is in synchronisation with the remote Crocus
SHDSL. Three different modes can be distinguished:
LED status Description
off No signal is detected on the line.
blinking A training cycle between central and remote Crocus SHDSL is in progress.
on The central and remote Crocus SHDSL are synchronised. A data link is present.
In case of a Crocus SHDSL 2P two DCD LEDs are present, one for each line pair.
36 User manual
Crocus SHDSL DIP switches and straps of the Crocus SHDSL
3. DIP switches and straps of the Crocus SHDSL

This chapter locates the DIP switches and straps on the Crocus SHDSL Table Top and Card Version
motherboard. It gives an overview of their function and it explains how to change their settings.
Section Title Page
3.1 DIP switches and straps of the Crocus SHDSL Table Top 38
3.2 DIP switches and straps of the Crocus SHDSL Card Version 43
Default settings are printed in bold.
User manual 37
DIP switches and straps of the Crocus SHDSL Crocus SHDSL
3.1 DIP switches and straps of the Crocus SHDSL Table Top
This section locates the DIP switches and straps on the Crocus SHDSL Table Top motherboard. It gives
an overview of their function and it explains how to change their settings.
Section Title Page
3.1.1 The TT motherboard 39
3.1.2 DIP switches of the TT 40
3.1.3 Straps of the TT 41
3.1.4 Changing DIP switch and strap settings of the TT 42
Disconnect the Crocus SHDSL Table Top from the mains before you open the housing to change DIP
switch and/or strap settings.
38 User manual
3.1.1 The TT motherboard

The figure below shows the position of the DIP switches and straps on the Crocus SHDSL TT
motherboard.
ON
DS1
1 2
3
4
3 2 1
ST9
1. NOT CON
2. CON 100
3. CON
DANGEROUS VOLTAGE AREA!
Figure 3.1: Position of the DIP switches and straps on the TT motherboard
User manual 39
3.1.2 DIP switches of the TT

The following table gives an overview of DIP switch bank DS1 of the TT:
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 3 on Normal operation.

configuration
off Load default configuration.
- 4 - - not used -
Table 3.1: Overview of DIP switch bank DS1 of the TT
For more information on

DIP switch and strap location on the TT motherboard, refer to Section 3.1.1 - The TT motherboard.
changing DIP switch and strap settings on the TT, refer to Section 3.1.4 - Changing DIP switch and
strap settings of the TT.
40 User manual
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:
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
3 2 1 application is not the same. In such a situation earth current
loops may induce distortion on the transmitted data,
resulting in transmission errors.
connected through Sometimes you might want to connect the Crocus SHDSL
100 ohms resistor earth to the application earth although both earth potentials
are not the same. (E.g. to avoid a big difference between
3 2 1 both earth potentials.) To avoid that high earth currents are
generated, you can make this connection through a 100
ohms resistor.
directly connected Sometimes it is not possible to connect the application

directly to the earth. In that case you can earth the
application through the Crocus SHDSL by connecting the
3 2 1 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 application by connecting the
application to the earth and setting strap ST9 in position 3.
Table 3.2: Overview of strap ST9 of the TT

DIP switch and strap location on the TT motherboard, refer to Section 3.1.1 - The TT motherboard.
changing DIP switch and strap settings on the TT, refer to Section 3.1.4 - Changing DIP switch and
strap settings of the TT.
User manual 41
3.1.4 Changing DIP switch and strap settings of the TT

To change the DIP switch settings of the TT, proceed as follows:
Step Action
1 Switch the Crocus SHDSL TT off.
2 Disconnect the Crocus SHDSL TT from the mains.
3 Unscrew the two screws located at the back of the Crocus SHDSL TT.
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 TT.
2
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 TT.
8 Reconnect the Crocus SHDSL TT to the mains.
9 Switch the Crocus SHDSL TT on.
Table 3.3: Changing DIP switch and strap settings of the TT
42 User manual
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.
Section Title Page
3.2.1 The CV motherboard 44
3.2.2 DIP switches of the CV 45
3.2.3 Straps of the Crocus SHDSL 1P CV Twin 46
3.2.4 Changing DIP switch and strap settings of the CV 47
User manual 43
3.2.1 The CV motherboard

The figure below shows the position of the DIP switches and straps on the Crocus SHDSL CV
motherboard.
ON
1 2 3 4 5 6 7 8
DS1
ON
1 2 3 4
#ADS1
ST2
ST4 1x2P
2x1P ST9
PLACE WITH COMPONENT SIDE DOWN

WETTING CURRENT OPTION
ON
1 2 3 4
#CDS1
ST8
ST6
2W 4W Optional wetting current module.
Place the module on pin headers
with component side down.
Figure 3.2: Position of the DIP switches and straps on the CV motherboard
44 User manual
3.2.2 DIP switches of the CV

The following table gives an overview of DIP switch bank DS1 of the Crocus SHDSL CV:
boot mode 1 on Normal operation.
loader mode 2 on Normal operation.

configuration
modem A

configuration
modem B
wetting current 5 on Normal operation.
off Wetting current operation.
- 6 - - not used -
- 7 - - not used -
- 8 - - not used -
Table 3.4: Overview of DIP switch bank DS1 of the CV
If your Crocus SHDSL CV is equipped with the optional wetting current module, then besides setting DIP
switch bank DS1 position 5 to off, also use DIP switch banks #ADS1 and #CDS1 to activate the wetting
current operation:
DIP switch name #ADS1 and #CDS1 Setting Function

no.
wetting current 1, 2, 3 and 4 on Normal operation.
off Wetting current operation.
Table 3.5: Overview of DIP switch bank #ADS1 and #CDS1 of the CV

DIP switch and strap location on the CV motherboard, refer to Section 3.2.1 - The CV motherboard.
changing DIP switch and strap settings on the CV, refer to Section 3.2.4 - Changing DIP switch and
strap settings of the CV.
User manual 45
3.2.3 Straps of the Crocus SHDSL 1P CV Twin

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:
Strap settings Function
The Crocus SHDSL CV operates as a 1P CV Twin, i.e.

2x1P 1x2P
ST2 ST6 two modems (A and B) on one card each with 1 line pair.
ST4 2W 4W
(default) (default)
The Crocus SHDSL CV operates as a 2P CV Single, i.e.

2x1P 1x2P
ST2 ST6 one modem (A) on one card with 2 line pairs.
ST4 2W 4W In this case, modem B can not be used.
Table 3.6: Overview of straps ST2, ST4 and ST6 of the Crocus SHDSL 1P CV

DIP switch and strap location on the CV motherboard, refer to Section 3.2.1 - The CV motherboard.
changing DIP switch and strap settings on the CV, refer to Section 3.2.4 - Changing DIP switch and
strap settings of the CV.
46 User manual
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.
3 Gently slide the CV on the two inner slides into the CN4 card nest again.
The following figure
shows this procedure:
15 slots
5 Fasten the two screws located at the front of the CV.
Table 3.7: Changing DIP switch and strap settings of the CV
User manual 47
Managing the Crocus SHDSL Crocus SHDSL
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 Section 1.7 - Management overview.
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
management of a Telindus device.
Section Title Page
4.1 Starting TMA on the Crocus SHDSL 49
4.2 Starting keyboard management on the Crocus SHDSL 55
4.3 Introducing the management attributes of the Crocus SHDSL 56
48 User manual
Crocus SHDSL Managing the Crocus SHDSL
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 table gives an overview of this section.
Section Title Page
4.1.1 Introducing TMA 50
4.1.2 Starting a TMA session through the control connector 51
4.1.3 Starting a TMA session through the Orchid 1003 LAN 53
4.1.4 Important remarks on starting a TMA session 54
User manual 49
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 the Orchid 1003 LAN.
50 User manual
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
control connector, proceed as follows:
Step Action
1 Connect the COM port of your PC through

a straight DB9 male-female cable with the
control 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.
User manual 51
Starting a TMA session through the control connector (continued)
Step Action
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
relative 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.
Table 4.1: Starting a TMA session through the control connector
52 User manual
4.1.3 Starting a TMA session through the Orchid 1003 LAN

On central locations with many access devices, the Crocus SHDSL can be connected to an Orchid 1003
LAN concentrator device. In this case the Orchid 1003 LAN is a proxy device for the Crocus SHDSL. In
that case you can connect TMA to the Crocus SHDSL through the Orchid 1003 LAN.
What is more, the Orchid 1003 LAN can act as an IP proxy device for the Crocus SHDSL. The IP address
related to the Crocus SHDSL is defined in the Orchid 1003 LAN.
Refer to the manual of the Orchid 1003 LAN for more information on the configuration and management
capabilities of this device.
User manual 53
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 Table 4.1: Starting a TMA
session through the control connector, step 3).
then enter the password of modem B in the Select device window (refer to Table 4.1: Starting a TMA
session through the control connector, 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:
If you want to open a TMA then set the attribute

session on a remote
Crocus SHDSL TT, ctrlPortProtocol to management.

What is more, if the remote Crocus SHDSL TT contains a router
interface and you want to manage this remote interface, then also
the ctrlPortProtocol of the remote Crocus SHDSL TT has to be set to
management.
Telindus 1420 SHDSL Router, eocChannel to itu-G.991.2.
Obviously, you can only start a TMA session on the remote device if the data link is up.
54 User manual
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:
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.
In order to exit keyboard management, repeatedly press the Esc key until the main
display window appears again.
To find out more about keyboard management, refer to the Telindus EasyConnect
manual.
Table 4.2: Starting keyboard management
Status information on the display

When you are not busy managing the Crocus SHDSL with the keyboard, the display shows status
information. For more information, refer to Chapter 6 - The front panel display.
User manual 55
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.
Section Title Page
4.3.1 Containment tree terminology 57
4.3.2 The Crocus SHDSL containment tree 59
4.3.3 Crocus SHDSL attribute overview 60
56 User manual
4.3.1 Containment tree terminology

The following figure depicts the TMA window containing the Crocus SHDSL containment tree.
Groups
Attributes
Containment tree
Attribute values
Objects
Actions
Structured values
Figure 4.1: TMA window containing the Crocus SHDSL containment tree
User manual 57
Containment tree terminology (continued)

The following table explains the terminology associated with the containment tree.
Term Description
containment The containment tree represents the hierarchical structure of the Crocus SHDSL. It
tree is composed of a number of objects that are ordered in a tree. This tree resembles
a Windows 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
corresponding priority level.
group Groups assemble a set of attributes related by functionality. There are four groups
in TMA, which correspond with the four tabs in the attribute window:
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.
Table 4.3: Containment tree terminology
58 User manual
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 (%).
Table 4.4: Objects of the Crocus SHDSL containment tree
User manual 59
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.
60 User manual
Crocus SHDSL Step-by-step configuration
5. Step-by-step configuration
This chapter describes in a step-by-step manner how to perform a basic configuration on Crocus SHDSL.
It also explains how DIP switch configuration tables and TMA attribute strings should be interpreted.
You are advised to read this chapter in a sequential manner, from the beginning to the end, without
skipping any part. By doing so, your Crocus SHDSL will be completely configured and ready for use
when you reach the end of this chapter.
Section Title Page
5.1 Reading the configuration settings 62
5.2 Loading the default configuration 64
5.3 Crocus SHDSL compatibility with other Telindus devices 67
5.4 Configuring the line 68
5.5 Selecting the timing mode 70
5.6 Configuring the clocking mode 71
5.7 Configuring the user speed 89
5.8 Configuring the G703 time slots 93
5.9 Configuring the user speed and G703 time slots on the Dual Port G703- 97
Serial interface
5.10 Configuring the interface specific attributes 100
5.11 Configuring the management attributes 105
5.12 Activating the configuration 109
For a complete overview of the attributes of the Crocus SHDSL, refer to the reference manual.
User manual 61
Step-by-step configuration Crocus SHDSL
5.1 Reading the configuration settings

As this chapter explains the basic configuration of the Crocus SHDSL, a lot of DIP switch configuration
tables and TMA attribute strings are displayed in it. To enable you to read this information in a correct
way, this section explains the structure of such tables and strings.
Reading a DIP switch configuration table

A DIP switch configuration table has the following layout:
Load default 3 (TT & CV-A) on Normal operation.

configuration 4 (CV-B)
1 2 3 4 5
The following table explains the DIP switch configuration table layout.
Number This position displays
1 the DIP switch icon. It indicates that the table which follows is a DIP switch configuration
table.
2 the DIP switch name.
3 for each Crocus SHDSL version:

on which DIP switch bank the switch can be found
the position of the switch on this DIP switch bank.
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
Version 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.
62 User manual
Reading the configuration settings (continued)
Reading a TMA attribute string

A TMA attribute string has the following layout:
crocusShdsl<Tt/Cv>/line/channel default: central
1 2 3
The following table explains the TMA attribute string layout.
Number This position displays
1 the TMA attribute icon. It indicates that the string which follows is a TMA attribute string.
Two different TMA attribute icons exist:
a basic attribute icon
an advanced attribute icon
For more information refer to Preface Conventions used in this manual.
2 the attribute name and its position in the containment tree.

In the figure above, the string crocusShdsl<Tt/Cv>/line/channel means the following:
the attribute name is channel
this attribute is located in the sub-object line
this sub object is located in the top object crocusShdsl<Tt/Cv>. The top object name is
crocusShdslTt in case of a TT
crocusShdslCv in case of a CV.
3 the default value of a configuration attribute.
User manual 63
5.2 Loading the default configuration

If you install the Crocus SHDSL for the first time, all configuration attributes are set to their default value.
If the Crocus SHDSL has already been configured a number of times and you want to reconfigure it
starting from scratch, it might be best to load the default configuration.
Also, when you accidentally made a configuration error which, for some reason, makes the Crocus
SHDSL inaccessible for TMA, you can load the default configuration using the appropriate DIP switch.
For instance: you defined a password in the Crocus SHDSL but you can not remember it. In that case
you can not access the Crocus SHDSL with TMA if you do not supply the correct password.
You can load the default configuration For more information, refer to Section
by means of
a DIP switch. 5.2.1 - The load default configuration DIP switch
an action in TMA. 5.2.2 - The load default configuration action in TMA
64 User manual
5.2.1 The load default configuration DIP switch

The location of the load default configuration DIP switch is:
load default 3 (TT & CV-A) on Normal operation.

configuration 4 (CV-B)
To load the default configuration using the appropriate DIP switch, proceed as follows:
Step Action
1 Disconnect the Crocus SHDSL from the power supply.
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.
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 TMA session on the Crocus SHDSL (refer to Section 4.1 - Starting TMA on
the Crocus SHDSL). ()
2. Execute the Activate Configuration command.
( )
If you are performing this load default configuration procedure because you
accidentally made a configuration error, you have the possibility to retrieve this
erroneous configuration before executing the Activate Configuration command. In that case
you do not have to reconfigure the complete device again, but you only have to correct
the error in question. Retrieve the erroneous configuration by executing the Load saved
configuration command.
5 Again, disconnect the Crocus SHDSL from the power supply.
6 Reset the appropriate DIP switch to on (see step 2).
The Crocus SHDSL reboots in normal operation mode.
User manual 65
5.2.2 The load default configuration action in TMA

The location of the Load Default Configuration action in the Crocus SHDSL containment tree is:
crocusShdsl<Tt/Cv>/Load Default Configuration

To load the default configuration, proceed as follows:
Step Action
1 In the TMA window, select the top object crocusShdsl<Tt/Cv> and the group Configuration.
2 In the action window of TMA, click the left mouse button on Load Default Configuration so
that this action is selected.
3 Press the right mouse button and select Execute.
4 To see the default configuration, press the Retrieve all attributes from device button
5 In the action window of TMA, click the left mouse button on Activate Configuration so that
this action is selected.
66 User manual
5.3 Crocus SHDSL compatibility with other Telindus devices

The Crocus SHDSL can be used in combination with other Telindus SHDSL devices. This section gives
an overview of the interoperability.
The following table shows the possible combinations of SHDSL products on a link. The drawings always
show a Crocus SHDSL (2P) TT. However, unless explicitly mentioned, this may equally be a Crocus
SHDSL (2P) CV Twin.
Set-up Interoperability issues
On the Crocus SHDSL, set the

crocusShdsl<Tt/Cv>/line/region attribute to annexA
crocusShdsl<Tt/Cv>/line/timingMode attribute to
synchronous
crocusShdsl<Tt/Cv>/line/eocChannel attribute to itu-
G.991.2
No further restrictions.
Exception: you can not use a Crocus Router
Interface when using ATM encapsulation.
This combination is only possible on DSLAMs

with PPP or Frame Relay encapsulation instead
of ATM encapsulation. Most DSLAMs support
only ATM encapsulation.
User manual 67
5.4 Configuring the line

crocusShdsl<Tt/Cv>/line/channel default: remote for TT / central for CV
The channel attribute defines which modem is the central and which the remote modem. I.e. it determines
which modem acts as master and which as slave during the synchronisation procedure of the modem.
The default channel setting of a Crocus SHDSL TT 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 default: annexB

The region attribute defines which S-HDSL standard is used:
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.
crocusShdsl<Tt/Cv>/line/mode default: dualPair

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:
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.
68 User manual
Configuring the line (continued)
crocusShdsl<Tt/Cv>/line/eocChannel default: proprietary

Use the eocChannel attribute to determine how the checksum of Embedded Operations Channel (EOC)
messages is calculated. Make sure that on both the central and the remote device the eocChannel attribute
is set to the same value.
The eocChannel attribute has the following values:
Value Description
proprietary The checksum is calculated using a proprietary method.
itu-G.991.2 The checksum is calculated using the G.SHDSL standard method.
User manual 69
5.5 Selecting the timing mode

crocusShdsl<Tt/Cv>/line/timingMode default: plesiochronous
Use this attribute to set the timing mode. The timingMode attribute has the following values:
Value Description
synchronous In this case the central Crocus SHDSL uses its internally generated clock as master
clock (internal clocking) and the remote Crocus SHDSL slaves on this clock (slave
receive clocking). This means that if you set the timingMode attribute to synchronous,
then the clocking attribute is ignored.
plesiochronous In this case each SHDSL frame has 0 or 4 stuffing bits to compensate for the clock
deviations towards the internal clock. In this mode, all possible clocking modes can
be selected.
In case of a G703 Nx64 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.
70 User manual
5.6 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 table gives an overview of this section.
Section Title Page
5.6.1 The clocking attribute 72
5.6.2 Possible clocking modes versus DTE interface 73
5.6.3 Fixed clocking modes 74
5.6.4 Preferred and alternative clocking 75
5.6.5 Schematic overview of the different clocking modes 76
5.6.6 Special points of interest concerning clocking on some interfaces 77
5.6.7 Clocking decision sequences 78
5.6.8 The presence of the external clock signal 80
5.6.9 Auto-sensing 81
5.6.10 Auto clocking for RS530, V35 and V36 interfaces 82
5.6.11 Auto clocking for Bridge and Router interfaces 83
5.6.12 Auto clocking for the X21 interface 84
5.6.13 Some examples of auto clocking 86
User manual 71
5.6.1 The clocking attribute

The location of the clocking attribute in the Crocus SHDSL containment tree is:
crocusShdsl<Tt/Cv>/<dteInterface>/clocking default: <interface dependent>

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 Section 5.6.2 - Possible clocking modes versus DTE interface.
72 User manual
5.6.2 Possible clocking modes versus DTE interface

The available clocking modes depend on which DTE interface is used in the Crocus SHDSL. The
following table gives an overview:
Clocking mode V35, V36, X21 () Bridge, G703 () DP G703-

RS530 Router Serial ()
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 X X
(CV only)
( )
Refer to Section 5.6.6 - Special points of interest concerning clocking on some interfaces for some
specific remarks concerning clocking on these interfaces.
The default clocking mode is indicated in bold.
User manual 73
5.6.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
application via the TxClk circuit (circuit 114).
Internal clocking can be selected in combination with preferred or alternative
clocking. 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 difference

The following table explains the difference between external and external loop-
back clocking mode:
external 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 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
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.
74 User manual
5.6.4 Preferred and alternative clocking

Internal and slave receive clocking can be selected in combination with preferred or alternative clocking:
preferred The application loops back the output of the TxClk circuit (circuit 114) to the
ExtTxClk 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 This does not require the TxClk (circuit 114) to ExtTxClk (circuit 113) loop-back.
In this case the clock is looped back within the Crocus SHDSL itself.
It may be necessary to use preferred clocking when delays are introduced in the communication between
the DTE and the Crocus SHDSL. Delays may occur in case of long interconnection cables or interface
converters.
User manual 75
5.6.5 Schematic overview of the different clocking modes

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

TxD TxD
Tx Tx
ExtTxClk ExtTxClk
TxClk clock TxClk clock

generation generation
RxClk RxClk
RxD Rx RxD Rx
Figure 5.1: Internal preferred clocking Figure 5.2: Internal alternative clocking

TxD TxD
Tx Tx
ExtTxClk ExtTxClk
TxClk TxClk
RxClk RxClk
RxD Rx RxD Rx
Figure 5.3: Slave receive preferred clocking Figure 5.4: Slave receive alternative clocking

TxD TxD
Tx Tx
ExtTxClk ExtTxClk
TxClk TxClk
RxClk RxClk
RxD Rx RxD Rx
Retiming buffer
Figure 5.5: External clocking Figure 5.6: External loop-back clocking
76 User manual
5.6.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 Description

interest
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 signal. 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.
A set-up using external loop-back clocking can only work when the remote
Crocus SHDSL is in slave receive clocking mode.
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.
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.
User manual 77
5.6.7 Clocking decision sequences

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.
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
decision sequence. Especially X21 and G703 interfaces require special attention:
Since X21 interfaces in general only have one clock circuit (the S clock), there may be
only one clock source in the X21 system. It is only when both X21 interfaces have an X
clock circuit that there may be two (external) clock sources in the X21 system.
Also in a G703 system one clock source is allowed. This means that when a G703
interface is in internal or station clocking mode, the applications on both sides of the
link have to be in slave receive clocking mode.
3 The local configured clocking mode

The clocking mode that you configure on the local Crocus SHDSL determines the actual
clocking mode that will be used. This is not necessarily the clocking mode that you
configured.
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.
78 User manual
Which factors influence the clocking decision sequence? (continued)
Priority Influencing factor
4a (1) 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.
4b (1) 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.
4c (1) 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 and at least one of them is in auto clocking mode. In this case one
interface is chosen as master, 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.
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.
(1)
These three items are on the same priority level.
User manual 79
5.6.8 The presence of the external clock signal

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
signal. The following table clarifies what happens when no external clock signal is present or when it is
lost:
If the Crocus SHDSL is and if the external clock signal is not present or if it is lost,
configured in
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, external loop-back then the Crocus SHDSL automatically switches to internal alternative
or station clocking mode, clocking mode.
If at a certain moment the external clock signal (re)appears, the Crocus
SHDSL switches (back) to external / external loop-back / station clocking
mode.
80 User manual
5.6.9 Auto-sensing
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 Section 5.6.7 - Clocking
decision sequences and Section 5.6.8 - The presence of the external clock signal, 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 then the Crocus SHDSL selects

signal
is present, external clocking mode.

In this case, the auto clock selection sequence ends here.
is not present, internal or slave receive clocking mode. (1)

In this case, the auto clock selection sequence continues:
If the external clock signal then the Crocus SHDSL selects

appears internal or slave receive preferred

(i.e. the DTE loops back the clock clocking mode.
signal to the ExtTxClk pin of the
interface),
does not appear internal or slave receive alternative

(i.e. the DTE does not loop back clocking mode.
the clock signal to the ExtTxClk pin
of the interface),
(1)
The selection between internal or slave receive clocking mode depends on
the remote interface type / remote clocking combination.
User manual 81
5.6.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 Section 5.6.7 - Clocking decision sequences.
This section explains the auto clocking decision for a local RS530, V35 and V36 interfaces in function of
the remote interface and clocking mode.
Remote Remote Clocking mode selected by the local Crocus SHDSL

interface clocking mode
G703 internal slave receive preferred

station slave receive alternative
The decision between these clocking modes is made by the

auto-sensing mechanism. Refer to Section 5.6.9 - Auto-sensing.
external external
slave receive preferred
slave receive alternative

X21 internal external

external slave receive preferred

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.
slave receive external loop-back

internal preferred
internal alternative

other any external

external loop-back
(in case the remote interface is in slave receive clocking
mode)
internal preferred

82 User manual
5.6.11 Auto clocking for Bridge and Router interfaces

This section explains the auto clocking decision for a local Bridge and Router interfaces in function of the
remote interface and clocking mode.
Remote Remote Clocking mode selected by the local Crocus SHDSL

interface clocking mode
G703 any slave receive
X21 any slave receive
other any internal
User manual 83
5.6.12 Auto clocking for the X21 interface

This section explains the auto clocking decision for a local X21 interface in function of the remote
interface 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 Remote Clocking mode selected by the local Crocus SHDSL
signal present? clocking mode
yes any external
slave receive external loop-back
no any internal preferred


internal slave receive preferred


84 User manual
Auto clocking for the X21 interface (continued)
X21 slave
Is the remote clocking mode Clocking mode selected by the local Crocus SHDSL
fixed slave receive?
yes external loop-back

internal preferred

no external
external loop-back
slave receive preferred

Local interface: X21 remote interface: other
The local X21 interface behaves as in case the remote interface is a
master, RS530, V35, V36, Bridge or Router interface.
slave, G703 or 4E1 interface.
User manual 85
5.6.13 Some examples of auto clocking

This section gives some examples of decision sequences made by the Crocus SHDSL when it is
configured in auto clocking mode.
The following figures and corresponding text display the auto clocking decision. Normally only the
clocking 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
local Crocus SHDSL remote Crocus SHDSL
AUTO V35 V35 AUTO
Figure 5.7: V35 and auto clocking V35 and auto clocking
START
The remote interface is a V35 interface in auto clocking mode.

Is an external clock signal present on the local V35 interface?
Yes external clocking mode is selected. END
No internal clocking mode is selected.

Does the DTE loop back the clock signal to the ExtTXClk pin of the V35 interface?
Yes internal preferred clocking mode is selected. END
No internal alternative clocking mode is selected. END
86 User manual
Some examples of auto clocking (continued)
Auto clocking example: V35 and auto clocking X21 and auto clocking
AUTO V35 X21 AUTO
Figure 5.8: V35 and auto clocking X21 and auto clocking
START
The remote interface is an X21 interface in auto clocking mode.

Is an external clock signal present on the remote X21 interface?
Yes the remote Crocus SHDSL selects external clocking mode.

Yes the local Crocus SHDSL selects external clocking mode. END
No the local Crocus SHDSL selects slave receive clocking mode.

Does the DTE loop back the clock signal to the ExtTXClk pin of the local
V35 interface?
Yes the local Crocus SHDSL selects slave receive preferred

clocking mode. END
No the local Crocus SHDSL selects slave receive alternative

clocking mode. END
No the remote Crocus SHDSL selects slave receive alternative clocking mode.
Yes the local Crocus SHDSL selects external clocking mode. END
No the local Crocus SHDSL selects internal clocking mode.

Does the DTE loop back the clock signal to the ExtTXClk pin of the local
V35 interface?
Yes the local Crocus SHDSL selects internal preferred clocking

mode. END
No the local Crocus SHDSL selects internal alternative clocking

mode. END
User manual 87
Some examples of auto clocking (continued)
Auto clocking example: X21 and auto clocking X21 and auto clocking
AUTO X21 X21 AUTO
Figure 5.9: 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
configured for auto clocking mode, they mutually decide who will be the auto clocking master and who
the slave.
START
The remote interface is an X21 interface in auto clocking mode.

Is an external clock signal present on the local X21 interface?
Yes external clocking mode is selected.

Yes the remote Crocus SHDSL selects external clocking mode. This means
the local Crocus SHDSL can stay in external clocking mode. END
No the remote Crocus SHDSL selects slave receive alternative clocking

mode. As a consequence, the local Crocus SHDSL switches to external
loop-back clocking mode. END
No
Yes the remote Crocus SHDSL selects external clocking mode. In this case
the local Crocus SHDSL selects slave receive alternative clocking
mode. END
No the remote Crocus SHDSL selects slave receive alternative clocking

mode. In this case the local Crocus SHDSL selects internal alternative
clocking mode. END
88 User manual
5.7 Configuring the user speed

This section explains how to configure the user speed. It also explains how the auto speed mechanism
works. The following table gives an overview of this section:
Section Title Page
5.7.1 The speed attribute 90
5.7.2 How does the auto speed mode work? 91
5.7.3 Clocking and speed combinations 92
In case of a G703 interface, skip this section and go to Section 5.8 - Configuring the G703 time slots for
the time slot configuration.
User manual 89
5.7.1 The speed attribute

The location of the speed attribute in the Crocus SHDSL containment tree is:
crocusShdsl<Tt/Cv>/<dteInterface>/speed default: auto

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 default: auto

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
operation, 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 4608 kbps in steps of 128 kbps.
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:
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.
90 User manual
5.7.2 How does the auto speed mode work?

The following table explains how the auto speed mode works:
If the Crocus SHDSL is configured then the Crocus SHDSL

in
external clocking mode and an measures the frequency of the external clock signal and
external clock signal is present, automatically 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.
allowed.
User manual 91
5.7.3 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 auto / external auto / internal or fixed / external fixed / internal or
SHDSL slave receive slave receive
(speed / clock)
auto / external The local user The local user The local user The local user
speed equals the speed equals the speed equals the speed equals the
local external local external local external local external
clock. clock. clock. clock.
auto / internal or The local user The local user The local user The local user
slave receive speed equals the speed equals the speed equals the speed equals the
remote external maximum remote fixed remote fixed
clock. common user speed. (Speed speed.
speed. should match
external clock!)
92 User manual
5.8 Configuring the G703 time slots

This section explains how to select the framing mode and how to allocate time slots on a G703 Nx64
interface. The following table gives an overview of this section:
Section Title Page
5.8.1 Selecting unframed or framed mode 94
5.8.2 Selecting the time slots 95
5.8.3 Time slot transposition 96
User manual 93
5.8.1 Selecting unframed or framed mode
crocusShdsl<Tt/Cv>/g703/framing default: unframed

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
disabled.
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.
In case of a G703 Nx64 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.
94 User manual
5.8.2 Selecting the time slots
crocusShdsl<Tt/Cv>/g703/timeSlots default: ts0=1, other ts=0

Use this attribute to enable or disable the individual 64 kbps time slots in the framed data stream.
Important remarks
Do not enable time slot 0 when using a G703 Nx64 interface in the local Crocus SHDSL and a non-
G703 interface in the remote Crocus SHDSL.
When using two G703 Nx64 interfaces and when enabling time slot 0, a DL test might not be
completely errorless.
Local G703 Nx64 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 Nx64 interface in framed
mode:
If the remote Crocus set to then

SHDSL is equipped
with
an RS530, V35, V36, a fixed speed, this fixed speed has to be configured by the user and
X21, Bridge or Router should equal Nx64 kbps (with N = number of allocated
time slots on the local G703 Nx64 interface).
auto speed, its speed is adapted automatically to Nx64 kbps (with N =

number of allocated time slots on the local G703 Nx64
interface).
a G703 Nx64 interface the same amount of time slots should be configured by
the user as on the local Crocus SHDSL.
Example:
G703 V35
framed mode auto speed, slave receive

TS6, TS12, TS25 = 1 clock
all other time slots = 0 the DTE interface speed
changes to 192 kbps (3x64
kbps)
User manual 95
5.8.3 Time slot transposition

If at both sides of the link a G703 Nx64 interface is used, it is possible to perform a time slot transposition
with TMA. Such a transposition is realised by setting the G703 Nx64 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:
G703 G703
framed mode framed mode

TS6, TS12, TS25 = 1 TS10, TS16, TS26 = 1
all other time slots = 0 all other time slots = 0
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:
Transmit
local side
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
remote side
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Receive
local side
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
remote side
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
96 User manual
5.9 Configuring the user speed and G703 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 G703 time
slots, this section highlights some special points of interest concerning this configuration.
The following table gives an overview of this section:
Section Title Page
5.9.1 Selecting unframed or framed mode 98
5.9.2 Configuring the user speed and the G703 time slots 98
5.9.3 How is the serial and G703 data ordered? 99
User manual 97
5.9.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 Section 5.8.1 - Selecting unframed or framed mode. However, this is only possible
if you use the Dual Port G703-Serial interface as G703 interface only. In other words when the
multiplexingMode attribute is set to g703Only (refer to Section 5.10.5 - Configuring the multiplexing mode
(Dual Port G703-Serial)).
5.9.2 Configuring the user speed and the G703 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 Section 5.7 - 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 Nx64 interface. Refer to Section 5.8 - Configuring the G703 time slots.
However, 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 Nx64 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.
98 User manual
5.9.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
Configuration (central modem): Configuration (remote modem):

G703 time slots : TS 1, 3, 7 G703 time slots : TS 7, 8, 9,
serial user speed : 256 kbps 10, 11, 12, 13
G703
G703
serial
G703 time slots : TS 1, 3, 7 TS 7, 8, 9

serial user speed : 256 kbps TS 10, 11, 12, 13
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
Configuration (central modem): Configuration (remote modem):

G703 time slots : TS 1, 3, 7 G703 time slots : TS 7, 8, 9
serial user speed : 256 kbps serial user speed : 256 kbps
G703 G703
serial serial
G703 time slots : TS 1, 3, 7 G703 time slots : TS 7, 8, 9

serial user speed : 256 kbps serial user speed : 256 kbps
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.
User manual 99
5.10 Configuring the interface specific attributes

This section explains the most important interface specific attributes. The following table gives an
overview of this section:
Section Title Page
5.10.1 Configuring the RTS control (RS530, V35, V36) 101
5.10.2 Configuring the CRC4 insertion (G703 Nx64) 101
5.10.3 Configuring the jitter attenuation (G703) 101
5.10.4 Configuring the SA bits (G703 Nx64) 102
5.10.5 Configuring the multiplexing mode (Dual Port G703-Serial) 103
5.10.6 Configuring the LAN filter (Bridge) 104
100 User manual

5.10.1 Configuring the RTS control (RS530, V35, V36)
crocusShdsl<Tt/Cv>/<dteInterface>/rtsControl default: internal

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.
If RTS control is the RTS signal is Use this setting in case

set to activated by
external the application. the application has to be in command of the RTS signal.
internal the Crocus SHDSL. the application is not able to activate the RTS signal.
5.10.2 Configuring the CRC4 insertion (G703 Nx64)
crocusShdsl<Tt/Cv>/g703/crc4Insertion default: auto

Use the crc4Insertion attribute to determine whether the CRC-4 (cyclic redundancy check) is recalculated
before sending it to the interface. The CRC is used to check the data integrity on the G.703 connection.
The crc4Insertion attribute has the following possible values:
Value Description
auto In auto mode, CRC-4 insertion is

disabled if the total line speed matches 2 Mbps,
enabled if the total line speed differs from 2 Mbps.
disabled CRC-4 insertion is disabled.
enabled CRC-4 insertion is enabled.
5.10.3 Configuring the jitter attenuation (G703)
crocusShdsl<Tt/Cv>/g703/jitterAttenuation default: 32 bits

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.
User manual 101

5.10.4 Configuring the SA bits (G703 Nx64)
crocusShdsl<Tt/Cv>/g703/saBits default: pathManagement

Use the saBits attribute to determine whether and which management data is inserted in the SA bits. If
selected, the management data is inserted in the SA registers SA5, SA7 and SA8. SA4 is used as a
control register and contains bandwidth information.
The saBits attribute has the following possible values:
Value Description
transparent No management data is inserted in the SA bits. The SA bits are passed
transparently.
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
forward management data over the line. As a result, you can e.g. open a TMA
session through the G703 interface on the Telindus device connected to the G703
interface.
pathManagement This inserts path management information in the SA bits. This allows you to
manage complete paths instead of managing individual devices (i.e. elements).
For more information on the differences between path management and element
management and for more information on path management in general, refer to
the Path management manual.
In the current application software release (T2136/01200, T2145/00400 or

T2141/00500), path management is not supported yet. This means that the option
pathManagement and o10-PathManagement does the same as the option transparent.
o10-PathManagement This insert both the proprietary Telindus O10 protocol as the path management
information in the SA bits.
102 User manual

5.10.5 Configuring the multiplexing mode (Dual Port G703-Serial)
crocusShdsl<Tt/Cv>/dualPort/multiplexingMode default: multiplexed

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:
Value Description
multiplexed The Dual Port G703-Serial interface multiplexes two data streams using Time
Division 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.
User manual 103

5.10.6 Configuring the LAN filter (Bridge)
crocusShdsl<Tt/Cv>/bridge/IanFilter default: enabled

Use the lanFilter attribute to enable or disable the filter functionality of the bridge. The lanFilter attribute can
be set to:
Value Description
enabled The bridge acts as a filter.

Refer to Figure 5.10: Bridge functionality. 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 Figure 5.10: Bridge functionality. 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.
The following figure depicts a bridge set-up:
PC1
modem + modem +
bridge bridge
PC2
network 1 network 2
Figure 5.10: Bridge functionality
104 User manual

5.11 Configuring the management attributes

This section explains the attributes that influence the management of the Crocus SHDSL. The following
table gives an overview of this section:
Section Title Page
5.11.1 Selecting the purpose of the control connector 106
5.11.2 Configuring the internal DMM function 107
5.11.3 Important remarks on the ctrlPortProtocol and internalDmm attribute 108
User manual 105

5.11.1 Selecting the purpose of the control connector
crocusShdsl<Tt/Cv>/management/ctrlPortProtocol default: console

The setting of the ctrlPortProtocol attribute depends on what purpose the control connector of the Crocus
SHDSL has to serve. This is explained in the following table:
Value Description
management Select this value if you want to connect the control connector of the Crocus SHDSL
to
the Orchid 1003 LAN for management purposes.
the control connector of another Crocus SHDSL using a crossed cable (i.e. they
are connected back-to-back) in order to create an extended management link.
For more information on extended management links, refer to Figure 7.1:
Forwarding TMA management information and Table 7.8: Relative and absolute
addressing.
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. You can
however 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 using TMA,
CLI or ATWIN.
Also refer to Section 5.11.3 - Important remarks on the ctrlPortProtocol and internalDmm attribute.
106 User manual

5.11.2 Configuring the internal DMM function
crocusShdslCv/management/internalDmm default: disabled

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
router PC running
modem A interface A TMA
(abs 11) (abs 12)
Crocus SHDSL TT 1
(abs 33)
internalDmm = CTRL port

enabled Crocus SHDSL TT 2
(abs 44)
router
modem B interface B
(abs 21) (abs 22) For Crocus SHDSL CV :
internalDmm = enabled
Crocus SHDSL CV For all Crocus SHDSL modems :
ctrlPortProtocol = management
In the set-up above, you are able to 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.
Also refer to Section 5.11.3 - Important remarks on the ctrlPortProtocol and internalDmm attribute.
User manual 107

5.11.3 Important remarks on the ctrlPortProtocol and internalDmm attribute
Changing the ctrlPortProtocol and internalDmm attribute causes the Crocus SHDSL to reboot.
In case of a Crocus SHDSL CV, the ctrlPortProtocol and internalDmm attributes are present in both the
containment 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 set the ctrlPortProtocol attribute to management, then you are advised to use absolute addressing
instead of relative addressing. Else you might be unable to address some devices in the network.
If you set the internalDmm attribute to enabled, then you are advised to use absolute addressing instead
of relative addressing. Else you might be unable to address some devices in the network.
If you use router interfaces in the Crocus SHDSL, then you are advised to set the ctrlPortProtocol
attribute to management. Else you might be unable to address the router interfaces.
108 User manual

5.12 Activating the configuration

Once the basic configuration of the Crocus SHDSL is made, it has to be activated. Do this by pressing
the Send all attributes to device button in TMA:
Repeat the installation for the remote Crocus SHDSL.

When both local and remote Crocus SHDSL are configured, try sending data to check whether the data
link is established. If any problems occur, the status, performance and alarm attributes of the Crocus
SHDSL can be checked. Refer to the reference manual for more information on these attributes.
User manual 109

The front panel display Crocus SHDSL
6. 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
similar way.
When you are not busy managing the Crocus SHDSL with the keyboard, the display shows status
information. This chapter describes the information that can be seen on the display.
Section Title Page
6.1 The windows of the front panel display 111
6.2 The main window 112
6.3 The line window 113
6.4 The DTE window 114
6.5 The test window 115
6.6 The model browsing window 116
6.7 The connect remote window 116
6.8 The version window 116
110 User manual

Crocus SHDSL The front panel display
6.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
windows. The following gives an overview of the different front panel display windows:
main window
line window
DTE window
test window
model browsing window
connect remote window
version window
Pressing the Esc key in any window returns you to the main window.
User manual 111

6.2 The main window

The main window displays general status information. The structure of the window is as follows:
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
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
The following table clarifies the main window display structure:
Display position Field Description
row 1 column 2 consistency Displays whether the Crocus SHDSL is under

consistency of the Orchid 1003 LAN 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.
row 2 column 8 11 line speed Displays the line speed currently in use: from 64 up to
(kbps) 2304.
row 2 column 13 16 DTE speed Displays the DTE interface speed currently in use: from
(kbps) 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.
112 User manual

6.3 The line window

The line window displays status information of the line. The structure of the window is as follows:
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
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
The following table clarifies the line window display structure:
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
displayed,
l2: status information of line pair 2 is being
displayed.
row 1 column 7 10 line status Displays the state of the line: up, down, test.
row 1 column 12 15 line speed Displays the line speed currently in use: from 64 up to
(kbps) 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.
User manual 113

6.4 The DTE window

The DTE window displays status information of the DTE interface. The structure of the window is as
follows:
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
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
The following table clarifies the DTE window display structure:
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 Displays the DTE interface speed currently in use: from
(kbps) 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
114 User manual

6.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:
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
1 r l + e t
2 e t a l r l d l c l r
The following table clarifies the test window display structure:
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 Briefly displays the status of the test currently in use:
originator progress or ending,
and then displays the originator of the test currently 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:
row 2 column 7 & 8 analogue loop
1. Move the cursor with the # and $ keys underneath
row 2 column 11 & 12 remote digital the string of the test you want to start.
loop 2. Press the Enter key.
row 2 column 15 & 16 digital loop 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 20 21 clear error Using this action you can clear the error counter. Move
counter the cursor with the # and $ keys underneath the clr
string and press the Enter key.
User manual 115

6.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 Section 4.2 - Starting keyboard management on the Crocus SHDSL.
6.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 management
on the remote Crocus SHDSL using the local keyboard and display.
6.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:
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
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
The following table clarifies the line window display structure:
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.
116 User manual

Crocus SHDSL
Reference manual
Reference manual 117

Crocus SHDSL
118 Reference manual

Crocus SHDSL Configuration attributes
7. Configuration attributes
This chapter discusses the configuration attributes of the Crocus SHDSL. The following table gives an
overview of this chapter.
Section Title Page
7.1 Configuration attribute overview 120
7.2 General configuration attributes 122
7.3 Line configuration attributes 130
7.4 Line pair configuration attributes 133
7.5 Interface configuration attributes 134
7.6 Management configuration attributes 142

Configuration attributes Crocus SHDSL
7.1 Configuration attribute overview
> crocusShdsl<Tt/Cv> (continued)

sysName >> rs530, v35, v36 (5)
sysContact
speed
sysLocation
speed2P (3)
security
clocking
forwardTmaToCtrlPort (1)
rtsControl
forwardTmaToLine
ctsDelay
alarmMask
rdlDetect
alarmLevel
tests
remoteAlarmMask (1)
alarmMask
alarmContactHighMask (2)
alarmLevel
alarmContactLowMask (2)
remoteAlarmMask (1)
Action: Activate Configuration
Action: Load Saved Configuration
Action: Load Default Configuration
Action: Cold Boot >> x21 (5)
(1)
TT only speed
(2)
CV only speed2P (3)
clocking
rdlDetect
>> line alarmMask
channel alarmLevel
region remoteAlarmMask (1)
timingMode alarmContactHighMask (2)
mode (3) alarmContactLowMask (2)
retrain
startupMargin >> g703 (5)
eocChannel framing (6)
testDuration timeSlots (6)
alarmMask clocking
alarmLevel coding
remoteAlarmMask (1) crc4Insertion (6)
alarmContactHighMask (2) jitterAttenuation
alarmContactLowMask (2) saBits (6)
(3)
2P version only alarmMask
alarmLevel
remoteAlarmMask (1)
>>> linePair [ ] (4) alarmContactHighMask (2)
alarmMask (6)
alarmLevel G703 Nx64 only
remoteAlarmMask (1) Continued on next page
(4)
in case of a 2P version, two linePair objects are
present: linePair[1] and linePair[2]
Continued in next column

Configuration attribute overview (continued) (continued)
>> dualPort (5) >> router (5)

rdlDetect speed
multiplexingMode speed2P (3)
>>> g703 clocking
rdlDetect
framing
alarmMask
timeSlots
alarmLevel
clocking
remoteAlarmMask (1)
coding
crc4Insertion
jitterAttenuation
(5)
saBits only present when the corresponding
alarmMask interface is used
alarmLevel
remoteAlarmMask (1)
alarmContactHighMask (2) >> management
alarmContactLowMask (2) cms2Address
>>> rs530 consoleNoTrafficTimeOut
speed ctrlPortProtocol
speed2P (3) internalDmm (2)
clocking
rtsControl
ctsDelay
tests
alarmMask
alarmLevel
remoteAlarmMask (1)
>> bridge (5)

speed
speed2P (3)
clocking
lanFilter
rdlDetect
alarmMask
alarmLevel
remoteAlarmMask (1)

7.2 General configuration attributes

crocusShdsl<Tt/Cv>/sysName default: <empty>
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 default: <empty>

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.
crocusShdsl<Tt/Cv>/sysLocation default: <empty>

This is a field where you can fill in the physical location of the Crocus SHDSL. The field has a limit of 64
characters.
crocusShdsl<Tt/Cv>/security default: <empty>

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 Default value
password The password is a string of maximum 10 characters. <empty>
accessRights This attribute represents the access levels assigned to a 111

password. It is a bit string whereof each bit corresponds to an
access level. The different access levels are:
readAccess
writeAccess
securityAccess
The following table shows, for each access level, what you can or can not do:
Access level Read Change Read security Change security Execute

attributes attributes attributes (1) attributes (1) actions (2)
readAccess yes no no no no
writeAccess yes yes no no yes
securityAccess yes yes yes yes yes
(1)
The Crocus SHDSL has the following security attributes:
crocusShdsl<Tt/Cv>/sysName
crocusShdsl<Tt/Cv>/security
(2)
Actions are e.g. Cold Boot, testActivation, retrain, etc.

crocusShdsl<Tt/Cv>/security (continued)
Entering passwords
The table below explains how to enter passwords in the different management systems.
Management system How to enter the password?
TMA You can enter the password in the connect windows.
Telnet You are prompted to enter the password when the session starts.
SNMP You should use the defined passwords as community strings. If no

passwords are defined then you can use any string as community strings.
TML Similar to TFTP you can send the password after the destination file name,
separated by a ?.
Example: tml fsourcefile@destinationfile?pwd
TMA CLI and TMA for Use the application TmaUserConf.exe to create a TMA user and assign a
HP OpenView password to this user. The password should correspond with a password
configured in the device.
Table 7.1: Entering passwords in the different management systems
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 configuration.

crocusShdsl<Tt/Cv>/security (continued)
Correcting the security table

If you forgot your password or you forgot to create one with write and security access, then you can set
the Load Default Configuration DIP switch. As a result, the Crocus SHDSL reboots in its default
configuration. You can then retrieve the erroneous configuration and correct it.
To correct the security table, proceed as follows:
Step Action
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.
The Crocus SHDSL reboots and loads the default configuration.
4 Retrieve the erroneous configuration:

1. Open a TMA session on the Crocus SHDSL (refer to Section 4.1 - Starting TMA on
the Crocus SHDSL).
2. Execute the Load saved configuration command.
3. Correct the error in the security table.
4. Execute the Activate Configuration command.
5 Again, disconnect the Crocus SHDSL from the power supply.
6 Reset the appropriate DIP switch to on (see step 2).
The Crocus SHDSL reboots in normal operation mode.
Table 7.2: Correcting the security table

General configuration attributes (continued)
crocusShdslTt/forwardTmaToCtrlPort default: enabled

Enables or disables propagation of TMA management information to the NMS port. This allows you to
cascade management information through the NMS port towards another Telindus device.
The forwardTmaToCtrlPort attribute is only present on the TT.
crocusShdsl<Tt/Cv>/forwardTmaToLine default: enabled

Enables or disables propagation of TMA 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 TMA 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 in a network.
forwardTmaToCtrlPort
line connection
Site A
Crocus SHDSL 1 forwardTmaToCtrlPort

forwardTmaToLine
Crocus SHDSL 2
Site B
extended link
forwardTmaToCtrlPort forwardTmaToLine
Crocus SHDSL 3
forwardTMAToLine
Figure 7.1: Forwarding TMA management information
If the attribute forwardTmaToLine is enabled on Crocus SHDSL 1, then management commands and
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 Crocus
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.

crocusShdsl<Tt/Cv>/<configurationAlarmAttributes>
For more information on the configuration alarm attributes alarmMask, alarmLevel, remoteAlarmMask,
alarmContactHighMask, alarmContactLowMask and on the alarms in general, refer to Section 10.2 - Introducing
the alarm attributes.
For more information on the alarms of the crocusShdsl<Tt/Cv> object, refer to Section 10.3 - General alarms.

Configuration actions
Three types of configuration are present in the Crocus SHDSL:
the non-active configuration
the active configuration
the default configuration.
When configuring the Crocus SHDSL with TMA, as in Chapter 5 - Step-by-step configuration, the
following happens:
Phase Action Result
1 The computer running TMA is connected The non-active configuration is displayed

to the Crocus SHDSL. on the screen.
2 Modifications are made on the non-active These modifications have no immediate

configuration. influence on the active configuration
currently used by the Crocus SHDSL.
3 All necessary modifications are carried out Now, the non-active configuration has to
on the non-active configuration. be made active.
4 Execute the Activate Configuration action. The non-active configuration becomes the
active configuration.
Table 7.3: The non-active, active and default configuration
crocusShdsl<Tt/Cv>/Activate Configuration
If you execute this action, the editable non-active configuration becomes the active configuration.
To activate a configuration, proceed as follows:
Step Action

Alternatively, you can just double click on the Activate Configuration string.
Table 7.4: Activating a configuration
The Activate Configuration action can also be performed with the Send all attributes to device button: .

crocusShdsl<Tt/Cv>/Load Saved Configuration

If you are in the progress of modifying the non-active configuration but made some mistakes, you might
want to revert to the active configuration. If you execute the Load Saved Configuration action, the non-active
configuration is overwritten by the active configuration currently used by the Crocus SHDSL.
To reload the active configuration, proceed as follows:
Step Action
2 In the action window of TMA, click the left mouse button on Load Saved Configuration so that

Alternatively, you can just double click on the Load Saved Configuration string.
4 To see the active configuration, press the Retrieve all attributes from device button:
Table 7.5: Loading the active configuration
crocusShdsl<Tt/Cv>/Load Default Configuration

If you install the Crocus SHDSL for the first time, all configuration attributes are set to their default value.
If the Crocus SHDSL has already been configured a number of times and you want to reconfigure it
starting from scratch, you can load the default configuration.
To load the default configuration, proceed as follows:
Step Action
2 In the action window of TMA, click the left mouse button on Load Default Configuration so
that this action is selected.

Alternatively, you can just double click on the Load Default Configuration string.
4 To see the default configuration, press the Retrieve all attributes from device button

Alternatively, you can just double click on the Activate Configuration string.
Table 7.6: Loading the default configuration

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).
This implies that:
it checks which application software to use
it reads the saved configuration and restarts program execution.
You can use this action, for instance, to activate new application software.
To perform a cold boot, proceed as follows:
Step Action
2 In the action window of TMA, click the left mouse button on Cold Boot so that this action is
selected.
3 Press the right mouse button and select Execute. Alternatively, you can just double click
on the Cold Boot string.
The session between TMA and the Crocus SHDSL is interrupted.
4 Re-establish a TMA session on the Crocus SHDSL.
The Crocus SHDSL attributes reappear on your screen.
Table 7.7: Performing a cold boot
If a Cold Boot is performed on a Crocus SHDSL CV Twin, both modem A and B reboot.

7.3 Line configuration attributes

crocusShdsl<Tt/Cv>/line/channel default: remote for TT / central for CV
The channel attribute defines which modem is the central and which the remote modem. I.e. it determines
which modem acts as master and which as slave during the synchronisation procedure of the modem.
The default channel setting of a Crocus SHDSL TT 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 default: auto

The region attribute defines which S-HDSL standard is used:
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.
crocusShdsl<Tt/Cv>/line/timingMode default: plesiochronous

Use this attribute to set the timing mode. The timingMode attribute has the following values:
Value Description
synchronous In this case the central Crocus SHDSL uses its internally generated clock as master
clock (internal clocking) and the remote Crocus SHDSL slaves on this clock (slave
receive clocking). This means that if you set the timingMode attribute to synchronous,
then the clocking attribute is ignored.
plesiochronous In this case each SHDSL frame has 0 or 4 stuffing bits to compensate for the clock
deviations towards the internal clock. In this mode, all possible clocking modes can
be selected.
In case of a G703 Nx64 interface, if you set the framing attribute to framed, then the Crocus SHDSL always
operates in plesiochronous mode regardless of the timingMode attribute setting.

Line configuration attributes (continued)
crocusShdsl<Tt/Cv>/line/mode default: dualPair

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/retrain
Use this attribute to determine when the Crocus SHDSL should retrain.
The retrain criteria

The following criteria determine when to retrain:
Criterion Description
SHDSL frame CRC error SHDSL framing sends 166 blocks per second over the line, independently
threshold exceeded of the speed. Each block has a CRC check. When a certain percentage of
frames has a CRC error, the Crocus SHDSL retrains.
no SHDSL frame When the Crocus SHDSL cannot synchronise on the SHDSL framing, it
synchronisation retrains.
signal to noise margin too When the S/N margin becomes too low during a certain period of time, the
low Crocus SHDSL retrains.
When start a retrain?

The retrain attributes are:
Attribute Description Range Default
enabled Use this attribute to enable (yes) or disable (no) - yes

retraining. So when selecting no, the Crocus SHDSL
will never retrain.
errorPersistenceTime Use this attribute to set the period, in seconds, during 1 30 10

which each criterion is measured. If within this period
the predefined criterion value is equalled or exceeded,
the Crocus SHDSL retrains.
errorThreshold Use this attribute to set the CRC errors, per mille, at 10 1000 10
which the Crocus SHDSL should retrain.
The erroneous SHDSL frames can be monitored using the performance attribute
crocusShdsl<Tt/Cv>/line/linePair [ ]/performance/codeViolations.

Line configuration attributes (continued)
crocusShdsl<Tt/Cv>/line/startupMargin default: 2dB
Use this attribute to define for which signal to noise margin a line speed is selected during the ITU-T
G.994.1 auto speed negotiation. The startupMargin attribute is only relevant in case both central and remote
Crocus SHDSL 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.
In case of a Crocus SHDSL 2P (2 pair) version, the startupMargin attribute does not function because you
can not set both the central and remote Crocus SHDSL 2P in auto speed mode.
crocusShdsl<Tt/Cv>/line/eocChannel default: proprietary

Use this attribute to determine how the checksum of Embedded Operations Channel (EOC) messages is
calculated. Make sure that on both the central and the remote device the eocChannel attribute is set to the
same value.
The eocChannel attribute has the following values:
Value Description
proprietary The checksum is calculated using a proprietary method.
itu-G.991.2 The checksum is calculated using the G.SHDSL standard method.
crocusShdsl<Tt/Cv>/line/testDuration default: 00000d 00h 03m 00s

It is possible to perform diagnostic tests on the Crocus SHDSL (refer to Chapter 13 - Diagnostic tests).
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.
crocusShdsl<Tt/Cv>/line/<configurationAlarmAttributes>
For more information on the alarms of the line object, refer to Section 10.4 - Line alarms.

7.4 Line pair configuration attributes
In case of a Crocus SHDSL 2P, two linePair objects are present: linePair [1] and linePair [2].
crocusShdsl<Tt/Cv>/linePair [ ]/<configurationAlarmAttributes>
For more information on the alarms of the linePair [ ] object, refer to Section 10.5 - Line pair alarms.

7.5 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.
Section Title Page
7.5.1 General interface configuration attributes 135
7.5.2 RS530, V35 and V36 interface configuration attributes 136
7.5.3 G703 interface configuration attributes 137
7.5.4 Dual Port G703-Serial interface configuration attributes 140
7.5.5 Bridge interface configuration attributes 141

7.5.1 General interface configuration attributes
crocusShdsl<Tt/Cv>/<dteInterface>/speed default: auto

Use the speed attribute to set the speed of the DTE interface.
For more information, refer to Section 5.7 - Configuring the user speed.
crocusShdsl<Tt/Cv>/<dteInterface>/speed2P default: auto

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).
allowed.
For more information, refer to Section 5.7 - Configuring the user speed.
crocusShdsl<Tt/Cv>/<dteInterface>/clocking default: auto

Use the clocking attribute to select a clocking mode.
For more information, refer to Section 5.6 - Configuring the clocking mode.
crocusShdsl<Tt/Cv>/<dteInterface>/rdlDetect default: enabled

When set to disabled, this attribute prevents that a digital loop can be performed 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>/<dteInterface>/<configurationAlarmAttributes>
For more information on the alarms of the <dteInterface> object, refer to Section 10.6 - Interface alarms.

7.5.2 RS530, V35 and V36 interface configuration attributes
crocusShdsl<Tt/Cv>/<rs530/v35/v36>/rtsControl default: internal

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.
If RTS control is the RTS signal is Use this setting in case

set to activated by
external the application. the application has to be in command of the RTS signal.
internal the Crocus SHDSL. the application is not able to activate the RTS signal.
crocusShdsl<Tt/Cv>/<rs530/v35/v36>/ctsDelay default: 0 ms
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.
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.
Between the moment the RTS signal drops and the moment the CTS signal drops, no delay is provided.
crocusShdsl<Tt/Cv>/<rs530/v35/v36>/tests default: disabled

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.

7.5.3 G703 interface configuration attributes
crocusShdsl<Tt/Cv>/g703/framing default: unframed

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.
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.
For more information, refer to Section 5.8 - Configuring the G703 time slots.
crocusShdsl<Tt/Cv>/g703/timeSlots default: ts0=1, other ts=0

Use this attribute to enable or disable the individual 64 kbps time slots in the framed data stream.
Important remarks
Do not enable time slot 0 when using a G703 Nx64 interface in the local Crocus SHDSL and a non-
G703 interface in the remote Crocus SHDSL.
When using two G703 Nx64 interfaces and when enabling time slot 0, a DL test causes errors.
For more information, refer to Section 5.8 - Configuring the G703 time slots.
crocusShdsl<Tt/Cv>/g703/coding default: hdb3

Use the coding attribute to set the G703 interface encoding mode. Possible values are:
Value Description
ami Alternate Mark Inversion is selected. This is a bipolar code with no zero
substitution.
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.

G703 interface configuration attributes (continued)
crocusShdsl<Tt/Cv>/g703/crc4Insertion default: auto

Use the crc4Insertion attribute to determine whether the CRC-4 (cyclic redundancy check) is recalculated
before sending it to the interface. The CRC is used to check the data integrity on the G.703 connection.
The crc4Insertion attribute has the following possible values:
Value Description
auto In auto mode, CRC-4 insertion is

disabled if the total line speed matches 2 Mbps,
enabled if the total line speed differs from 2 Mbps.
disabled CRC-4 insertion is disabled.
enabled CRC-4 insertion is enabled.
crocusShdsl<Tt/Cv>/g703/jitterAttenuation default: 32 bits

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.

G703 interface configuration attributes (continued)
crocusShdsl<Tt/Cv>/g703/saBits default: pathManagement

Use the saBits attribute to determine whether and which management data is inserted in the SA bits. If
selected, the management data is inserted in the SA registers SA5, SA7 and SA8. SA4 is used as a
control register and contains bandwidth information.
The saBits attribute has the following possible values:
Value Description
transparent No management data is inserted in the SA bits. The SA bits are passed
transparently.
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
forward management data over the line. As a result, you can e.g. open a TMA
session through the G703 interface on the Telindus device connected to the G703
interface.
pathManagement This inserts path management information in the SA bits. This allows you to
manage complete paths instead of managing individual devices (i.e. elements).
For more information on the differences between path management and element
management and for more information on path management in general, refer to
the Path management manual.
In the current application software release (T2136/01200, T2145/00400 or

T2141/00500), path management is not supported yet. This means that the option
pathManagement and o10-PathManagement does the same as the option transparent.
o10-PathManagement This insert both the proprietary Telindus O10 protocol as the path management
information in the SA bits.

7.5.4 Dual Port G703-Serial interface configuration attributes
crocusShdsl<Tt/Cv>/dualPort/multiplexingMode default: multiplexed

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:
Value Description
multiplexed The Dual Port G703-Serial interface multiplexes two data streams using Time
Division 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.
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
Section 7.5.1 - General interface configuration attributes,
Section 7.5.2 - RS530, V35 and V36 interface configuration attributes,
Section 7.5.3 - G703 interface configuration attributes.
However, there are 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 Section 5.6.6 - Special points of interest concerning clocking on some interfaces.
framing, refer to Section 5.9 - Configuring the user speed and G703 time slots on the Dual Port G703-
Serial interface.
speed and time slot selection, refer to Section 5.9 - Configuring the user speed and G703 time slots
on the Dual Port G703-Serial interface.

7.5.5 Bridge interface configuration attributes
crocusShdsl<Tt/Cv>/bridge/IanFilter default: enabled

Use the lanFilter attribute to enable or disable the filter functionality of the bridge. The lanFilter attribute can
be set to:
Value Description
enabled The bridge acts as a filter.

Refer to Figure 5.10: Bridge functionality. 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 Figure 5.10: Bridge functionality. 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.

7.6 Management configuration attributes

crocusShdsl<Tt/Cv>/management/cms2Address default: 0
If you want to connect to a Crocus SHDSL with TMA, you have to specify the address of the Crocus
SHDSL. Refer to Section 4.1 - Starting TMA on the Crocus SHDSL.
There are two different types of addresses:
Address type Description
relative This type of addressing is meant for a network topology where the devices are
connected in-line on management level. I.e. with extended management links (1)
between two devices. Refer to Figure 7.2: Relative addressing.
To enable relative addressing, no address has to be specified in the device.
(1)
An extended management link is realised with a crossed cable between the
control connectors of the two devices. You also have to set the ctrlPortProtocol
attribute to the value management.
absolute This type of addressing is meant for a network topology where the devices are not
connected in-line on management level. I.e. when there is a digital multipoint device
present (e.g. the Orchid DM). Refer to Figure 7.3: Absolute addressing.
To enable absolute addressing, an address has to be specified in the device. This
is done with the attribute cms2Address. The absolute addressing range goes from 0
up to 65535.
Table 7.8: Relative and absolute addressing
extended
link
PC running relative 0 relative 1 relative 2 relative 3

TMA
Figure 7.2: Relative addressing
digital
multipoint
example:
absolute 10
example:
PC running example: absolute 20
example:
TMA absolute 0 absolute 1 example:
absolute 30
Figure 7.3: Absolute addressing

Management configuration attributes (continued)
crocusShdsl<Tt/Cv>/management/consoleNoTrafficTimeOut default: 00000d 00h 30m 00s

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.
crocusShdsl<Tt/Cv>/management/ctrlPortProtocol default: console

The setting of the ctrlPortProtocol attribute depends on what purpose the control connector of the Crocus
SHDSL has to serve.
For more information, refer to Section 5.11 - Configuring the management attributes.
crocusShdslCv/management/internalDmm default: disabled

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.
For more information, refer to Section 5.11 - Configuring the management attributes.

Status attributes Crocus SHDSL
8. Status attributes
This chapter discusses the status attributes of the Crocus SHDSL. The following table gives an overview
of this chapter.
Section Title Page
8.1 Status attribute overview 145
8.2 General status attributes 147
8.3 Line status attributes 150
8.4 Line pair status attributes 154
8.5 Interface status attributes 155
8.6 Management status attributes 163
8.7 Operating system status 164

Crocus SHDSL Status attributes
8.1 Status attribute overview

sysDescr >> rs530, v35, v36 (2)
sysObjectID
txdItu103
sysUpTime
rxdItu104
sysServices
rtsItu105
messages
ctsItu106
deviceId
dsrItuT107
configurationSaving
dcdItu109
bootVersion
rdlItu140
loaderVersion
alItu141
flash1Version
tiItu142
Action: Cold Boot
ifDescr
ifType
>> line ifSpeed
ifClocking
ifDescr
ifOperStatus
ifType
ifSpeed >> x21 (2)
ifOperStatus
txdItu103
testType
rxdItu104
testOriginator
indicator
testStatus
ifDescr
maxSpeedSearch
ifType
maxSpeedResult
ifSpeed
errorCount
ifClocking
Action: testActivation
ifOperStatus
Action: clearErrorCounter
Action: maximumSpeedSearch >> g703 (2)
txdItu103
rxdItu104
>>> linePair [ ] (1)
ais
ifSpeed lfa (3)
ifOperStatus los
status openCircuit
timeSinceLastRetrain receiveLevel
lineAttenuation ifDescr
signalNoise ifType
actualBitRate ifSpeed
(1)
in case of a Crocus SHDSL 2P, two linePair ifClocking
objects are present ifOperStatus
(3)
Continued in next column G703 Nx64 only

Status attribute overview (continued) (continued)
>> dualPort (2) >> bridge (2)
>>> g703 wanTxd

wanRxd
txdItu103
ifDescr
rxdItu104
ifType
ais
ifSpeed
lfa (3)
ifClocking
los
ifOperStatus
openCircuit
receiveLevel >> router (2)
ifDescr
wanTxd
ifType
wanRxd
ifSpeed
ifDescr
ifClocking
ifType
ifOperStatus
ifSpeed
>>> rs530 ifClocking
txdItu103 ifOperStatus
rxdItu104 (2)
only present when the corresponding
rtsItu105
interface is used
ctsItu106
dsrItuT107
dcdItu109
>> management
rdlItu140
alItu141 cardSlotNumber (4)
tiItu142 cardNestNumber (4)
ifDescr modemPosition (4)
(4)
ifType CV only
ifSpeed
ifClocking
ifOperStatus >> operatingSystem
Continued in next column taskInfo

8.2 General status attributes

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.
Example: 1, which indicates that the Crocus SHDSL is a modem.

General status attributes (continued)
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
control connector, you can monitor these messages. If you hit the ENTER key, the messages stop and
you get a password prompt (CLI mode).
crocusShdsl<Tt/Cv>/deviceId
This displays a unique code. This code is programmed into the Crocus SHDSL before it leaves the
factory. 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.
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 configuration
will be lost.
done The Crocus SHDSL has finished writing its configuration to the flash memory.

General status attributes (continued)
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 Section 12.1 - What is boot, loader and application software?.
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 Section 12.1 - What is boot, loader and application software?.
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.
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 Section 12.1 - What is boot, loader
and application software?.
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.

8.3 Line status attributes

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

Line status attributes (continued)
crocusShdsl<Tt/Cv>/line/testType
This attribute displays which test is currently active. The possible indications are:
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.
crocusShdsl<Tt/Cv>/line/testOriginator
This attribute displays the origin of the active test. The possible indications are:
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 Section 6.5 - The test window.
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.
crocusShdsl<Tt/Cv>/line/testStatus
This attribute displays the status of the active test. The possible indications are:
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.

crocusShdsl<Tt/Cv>/line/maxSpeedSearch
This attribute shows the status of the maximumSpeedSearch action. The possible indications are:
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

maxSpeedResult attribute.
crocusShdsl<Tt/Cv>/line/maxSpeedResult
This attribute displays the maximum speed that was achieved during the execution of the
maximumSpeedSearch action.
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/testActivation
Use this action to perform a test on the Crocus SHDSL. These tests are useful to trace possible
problems. Possible tests are: no, al, dl, rdl, et, alEt, rdlEt.
To execute a test, proceed as follows:
Step 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.
Table 8.1: Executing a test
For more information on these tests, refer to Chapter 13 - Diagnostic tests.


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.
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:
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.
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.
In case of a Crocus SHDSL 2P (2 pair) version, you can not execute the maximumSpeedSearch action
because you can not set both the central and remote Crocus SHDSL in auto speed mode.

8.4 Line pair status attributes
crocusShdsl<Tt/Cv>/line/linePair [ ]/ifSpeed
This attribute displays the current line speed in bits per second (bps), e.g. 2048000.
crocusShdsl<Tt/Cv>/line/linePair [ ]/ifOperStatus
This attribute displays the current operation status of the line. The possible indications are:
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.
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:
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.
crocusShdsl<Tt/Cv>/line/linePair [ ]/timeSinceLastRetrain
This attribute displays the time the line is in data state since the last retrain cycle.
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 lineAttenuation and signalNoise do not display meaningful information when the line is
not trained or in analogue loop (AL). These attributes are only relevant for a trained line.
crocusShdsl<Tt/Cv>/line/linePair [ ]/actualBitRate
This attribute displays the bit rate as you wanted it (i.e. the speed as you configured it using the speed or
timeSlots attribute).

8.5 Interface status attributes

This section discusses the status attributes of the different DTE interfaces. Because some of the interface
status attributes are present on every interface, they are discussed in a general section. All other sections
discuss the interface specific attributes.
Section Title Page
8.5.1 General interface status attributes 156
8.5.2 RS530, V35 and V36 interface status attributes 158
8.5.3 X21 interface status attributes 159
8.5.4 G703 interface status attributes 160
8.5.5 Dual Port G703-Serial interface status attributes 161
8.5.6 Bridge and Router interface status attributes 162

8.5.1 General interface status attributes
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 interface

is used in unframed mode
e1 when the G703 interface
is used in framed mode
Bridge bridge ethernet-csmacd
Router router other

General interface status attributes (continued)
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.
internalPreferred.
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:
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.
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,
disregarding of the operational status of the Router interface itself. For that information you have to
connect to the Router interface.

8.5.2 RS530, V35 and V36 interface status attributes
crocusShdsl<Tt/Cv>/<dteInterface>/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>/<dteInterface>/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>/<dteInterface>/rtsItu105
This attribute displays the status (on / off) of the request to send signal (circuit 105).
crocusShdsl<Tt/Cv>/<dteInterface>/ctsItu106
This attribute displays the status (on / off) of the clear to send signal (circuit 106).
crocusShdsl<Tt/Cv>/<dteInterface>/dsrItu107
This attribute displays the status (on / off) of the data set ready signal (circuit 107).
crocusShdsl<Tt/Cv>/<dteInterface>/dcdItu109
This attribute displays the status (on / off) of the data carrier detect signal (circuit 109).
crocusShdsl<Tt/Cv>/<dteInterface>/rdlItu140
This attribute displays the status (on / off) of the remote digital loop signal (circuit 140).
crocusShdsl<Tt/Cv>/<dteInterface>/alItu141
This attribute displays the status (on / off) of the analogue loop signal (circuit 141).
crocusShdsl<Tt/Cv>/<dteInterface>/tiItu142
This attribute displays the status (on / off) of the test indication signal (circuit 142).

8.5.3 X21 interface status attributes
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.

8.5.4 G703 interface status attributes
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/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 Nx64 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/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 SHDSL is
interrupted.
crocusShdsl<Tt/Cv>/g703/openCircuit
This attribute displays (on / off) whether the transmit side is connected or not. Open circuit is on when e.g.
the connection from the Telindus 1030 Router towards the WAN is interrupted.
crocusShdsl<Tt/Cv>/g703/rxLevel
This attribute displays the signal level, in dB, of the incoming data.

8.5.5 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
Section 8.5.1 - General interface status attributes,
Section 8.5.2 - RS530, V35 and V36 interface status attributes,
Section 8.5.4 - G703 interface status attributes.

8.5.6 Bridge and Router interface status attributes
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.

8.6 Management status attributes
The following attributes are only present on a Crocus SHDSL Card Version, not on a Table Top.
crocusShdslCv/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 the Orchid 1003 LAN management concentrator. In that
case, the Crocus SHDSL its position in the CN4 card nest has to be known so that the Orchid can
address the Crocus SHDSL.
crocusShdslCv/management/cardNestNumber
This attribute displays the CN4 card nest address.
case, the address of the CN4 card nest has to be known so that the Orchid 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
information, refer to the CN4 manual.
crocusShdslCv/management/modemPosition
This attribute displays the position of the modem (A or B) on the Card Version.
case, the position of the modem on the card has to be known so that the Orchid can address that
particular modem.

8.7 Operating system status

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:
Value Description
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
seconds. 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
memory address for the current instruction of this task.

Crocus SHDSL Performance attributes
9. Performance attributes
This chapter discusses the performance attributes of the Crocus SHDSL. The following table gives an
Section Title Page
9.1 Performance attribute overview 166
9.2 Introducing the performance attributes 167
9.3 Line performance attributes 170
9.4 Line pair performance attributes 171
9.5 G703 interface performance attributes 172
9.6 Dual Port G703-Serial interface performance attributes 173
9.7 Operating system performance attributes 174

Performance attributes Crocus SHDSL
9.1 Performance attribute overview

Action: Cold Boot >> dualPort (2)
>>> g703
>> line h2G703Performance
h2Line h24G703Performance
h24Line d7G703Performance
d7Line g703Performance
line (2)
errorCount interface is used
Action: retrain
Action: testActivation
Action: clearErrorCounter >> operatingSytem
currUsedProcPower
freeDataBuffers
>>> linePair [ ] (1)
totalDataBuffers
h2LineParameters
largestFreeBlockSize
h2Performance
freeBlockCount
h24LineParameters
freeMemory
h24Performance
totalMemory
d7LineParameters
usedProcPower
d7Performance
taskInfo
lineParameters
performance
(1)
in case of a Crocus SHDSL 2P, two linePair
objects are present: linePair [1] and linePair [2]
>> g703 (2)

h2G703Performance
h24G703Performance
d7G703Performance
g703Performance

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.
Section Title Page
9.2.1 Performance timing 168
9.2.2 Performance terms 169

9.2.1 Performance timing

The following table explains the performance information timing.
Performance timing Description
2 hours, The performance information is accumulated during a certain time span,

24 hours, called a period. After a period, the accumulated performance information is
7 days 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.
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.

9.2.2 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
corresponding 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.

9.3 Line performance attributes

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:
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.
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
problems. Possible tests are: no, al, dl, rdl, et, alEt, rdlEt.
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.

9.4 Line pair performance attributes
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:
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.
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.
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>Performance structured value elements are the following:
Attribute For the corresponding period, this attribute displays
sysUpTime the time since the latest cold boot.
codeViolations the number of erroneous SHDSL frames that was counted.
errSec the number of erroneous seconds that was counted.
sevErrSec the number of severely erroneous seconds that was counted.
unavailableSec the number of unavailable seconds that was counted.
loswSec the number of lost synchronisation words that was counted.
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.

9.5 G703 interface performance attributes

crocusShdsl<Tt/Cv>/g703/<h2/h24/d7>G703Performance
This structured value displays the 2 hours, 24 hours and 7 days G703 interface performance summary.
The <h2/h24/d7>G703Performance structured value elements are the following:
crc4ErrorCount the number of CRC4 errors that was counted in case CRC4 insertion is enabled.
aisCount the number of alarm indication signal alarms that was counted.
aisTime the time during which an alarm indication signal alarm was active.
lfaCount the number of loss of frame alignment alarms which was counted. This is only
present on the G703 Nx64 interface.
lfaTime the time during which a loss of frame alignment alarm was active. This is only
present on the G703 Nx64 interface.
losCount the number of loss of signal alarms that was counted.
losTime the time during which a loss of signal alarm was active.
crocusShdsl<Tt/Cv>/g703/g703Performance
This structured value displays the G703 interface performance summary since the last cold boot. Except
for sysUpTime, the structured value elements are the same as for the <h2/h24/d7>G703Performance attribute.

9.6 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 Section 9.5 - G703 interface performance attributes.

9.7 Operating system performance attributes

crocusShdsl<Tt/Cv>/operatingSystem/currUsedProcPower
This is the amount of processing power used during the last 650 milliseconds, expressed as a
percentage of the total available processing power.
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.

Operating system performance attributes (continued)
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
usedProcPower is composed of the following attributes:
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.
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
processors operating system.
This attribute contains the same information as taskInfo in the status group (refer to Section 8.7 -
Operating system status).

Alarm attributes Crocus SHDSL
10. Alarm attributes

This chapter discusses the alarm attributes of the Crocus SHDSL. The following table gives an overview
of this chapter.
Section Title Page
10.1 Alarm attribute overview 177
10.2 Introducing the alarm attributes 178
10.3 General alarms 183
10.4 Line alarms 185
10.5 Line pair alarms 186
10.6 Interface alarms 187

Crocus SHDSL Alarm attributes
10.1 Alarm attribute overview

totalAlarmLevel >> rs530, v35, v36, x21 (3)
alarmInfo
alarmInfo
notResponding
linkDown
alarmSyncLoss
lossOfTiming
configChanged
backupTiming
access
remoteAlarm >> g703 (3)
unknownState
alarmInfo
powerSupply1CvFail (1)
linkDown
powerSupply2CvFail (1)
ais
powerSupply48VFail (1)
lfa (4)
coldBoot
lossOfTiming
warmBoot (4
) G703 Nx64 only
codeConsistencyFail
configConsistencyFail
>> dualPort (3)
Action: Cold Boot
(1)
CV only >>> g703
alarmInfo
linkDown
>> line ais
alarmInfo lfa
linkDown lossOfTiming
testActive >>> rs530
alarmInfo
>>> linePair [ ] (2) linkDown
lossOfTiming
alarmInfo
backupTiming
linkDown
(2)
in case of a Crocus SHDSL 2P, two linePair >> bridge, router (3)
objects are present: linePair [1] and linePair [2] alarmInfo
Continued in next column linkDown
(3)
interface is used

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.
Section Title Page
10.2.1 Configuration alarm attributes 179
10.2.2 General alarm attributes 181
10.2.3 Alarm signalling 182

10.2.1 Configuration alarm attributes

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
crocusShdsl<Tt/Cv>//alarmLevel
crocusShdslTt//remoteAlarmMask
crocusShdslCv//alarmContactHighMask
crocusShdslCv//alarmContactLowMask
The following table explains the configuration alarm attributes.
alarmMask The alarmMask attribute enables or disables for each alarm of the corresponding
object, whether it is communicated to the central management system (e.g. HP
OpenView) or not.
Alarms are always seen in the alarmInfo 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. Also the alarm count and time in the performance information will
increment.
However, because this alarm is disabled:
it will not be sent to the central management system (e.g. HP OpenView)
it will not cause a change of colour in the subsystem picture (refer to Chapter
11 - TMA subsystem picture of the Crocus SHDSL).
alarmLevel With this attribute, a priority level can be assigned to each alarm of the
corresponding object. The alarm level ranges 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 crocusShdsl<Tt/Cv>.

Configuration alarm attributes (continued)
remoteAlarmMask The remoteAlarmMask attribute enables or disables for each alarm of the
corresponding object, whether:
(TT only)
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.

The remoteAlarmMask attribute is only present on the TT.
alarmContactHighMask The alarmContactHighMask attribute enables or disables for each alarm of the
(CV only)
the high alarm contacts of the CN4 card nest are driven.
By default, all the alarms in the alarmContactHighMask are set to disabled.

The alarmContactHighMask attribute is only present on the CV.
alarmContactLowMask The alarmContactLowMask attribute enables or disables for each alarm of the
(CV only)
the low alarm contacts of the CN4 card nest are driven.
By default, all the alarms in the alarmContactLowMask are set to disabled.

The alarmContactLowMask attribute is only present on the CV.
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 Section 10.2.3 - Alarm signalling.

10.2.2 General alarm attributes

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,
crocusShdsl<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. 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.

10.2.3 Alarm signalling

If you do not have a central management system, you could perform alarm signalling with the alarm
contacts of the CN4 card nest.
Example
Suppose the following situation:
On a remote Crocus SHDSL TT the configChanged alarm of the crocusShdslTt object is set to enabled in
the remoteAlarmMask. In other words: crocusShdslTt/remoteAlarmMask/configChanged = enabled.
On a central Crocus SHDSL CV the remoteAlarm of the top object is set to enabled in the
alarmContactHighMask. In other words: crocusShdslTt/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 On the Crocus SHDSL TT the configChanged
Crocus SHDSL TT. alarm becomes active.
2 On the Crocus SHDSL TT the configChanged A remote alarm is sent to the Crocus
alarm is enabled in the remoteAlarmMask. SHDSL CV.
3 On the Crocus SHDSL CV the remoteAlarm The high alarm contacts of the CN4 card
is enabled in the alarmContactHighMask. nest close.
4 The high alarm contacts of the CN4 card The light bulb lights up.
nest close.

10.3 General alarms

Refer to Section 10.2 - Introducing the alarm attributes for the general alarm attributes.
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 enabled 4
polling session of the Orchid 1003 LAN.
alarmSyncLoss when the internal alarm buffer overflows. enabled 4
configChanged when the configuration of the Crocus SHDSL is disabled 1

changed.
access when a TMA connection is made through the disabled 1

control connector of the Crocus SHDSL (not when
a TMA connection is made via the Orchid 1003
LAN).
remoteAlarm when the remote Crocus SHDSL is in alarm disabled 0

condition.
unknownState each time a new Crocus SHDSL is added to the disabled 0

network and before the Orchid 1003 LAN has
completed a first successful polling session.
remotePowerFail when the remote Crocus SHDSL experiences a disabled 3

power fail.
powerSupply1CvFail when the upper power supply in the CN4 card nest disabled 3
is not present or fails.
This alarm exists on the CV only.
powerSupply2CvFail when the lower power supply in the CN4 card nest disabled 3
is not present or fails.
powerSupply48VFail when the directly connected -48 Vdc on the CN4 disabled 3
card nest is no longer present. This means that the
115/230 Vac back-up power supply has taken over.
coldBoot when the Crocus SHDSL performs a cold boot. disabled 1
warmBoot when the Crocus SHDSL performs a warm boot. disabled 1

General alarms (continued)
codeConsistencyFail when the software consistency imposed by the disabled 1

Orchid 1003 LAN on the Crocus SHDSL fails. For
example, because of a loss of contact.
Check the status attribute o1003/nmsgroup/
softConsistencyStatus to determine the problem.
configConsistencyFail when the configuration consistency imposed by the disabled 1

Orchid 1003 LAN on the Crocus SHDSL fails. For
example, because of a loss of contact.
Check the status attributes o1003/nmsgroup/objectTable/
configState and configDiag to determine the problem.

10.4 Line alarms

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:
linkDown when no data link towards the remote Crocus enabled 3

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 linkDown alarm is
generated.
testActive when a test is active. disabled 1

10.5 Line pair alarms
crocusShdsl<Tt/Cv>/line/linePair [ ]/alarmInfo
The linePair [ ] object alarm, together with its explanation and its default alarmMask and alarmLevel value is
given in the following table:
linkDown when no data link towards the remote Crocus enabled 3

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 linkDown alarm is
generated.

10.6 Interface alarms

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:
linkDown when no RTS signal is detected. I.e. the connection enabled 3

between the Crocus SHDSL and the DTE is down.
(for RS530, V35,
V36) 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.
linkDown when no valid C signal is detected. I.e. the enabled 3

connection between the Crocus SHDSL and the
(for X21)
DTE is down.
linkDown when there is a loss of signal. I.e. the transmit data enabled 3
is no longer present.
(for G703 and
G703 Nx64)
linkDown when there is no connection with the LAN. I.e. the enabled 3
LAN is not connected or no valid LAN signals are
(for Bridge)
present.
linkDown when there is no connection between the router enabled 3

and the Crocus SHDSL. Because this connection is
(for Router)
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.
ais when an alarm indication signal has been detected disabled 2

on the incoming G703 transmit data. It means the
(G703 and G703
application has detected an error.
Nx64 only)
lfa when the frame alignment signal (FAS), which is disabled 2

present in time slot 0 of the G.704 framed data, is
(G703 Nx64 only)
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.)

Interface alarms (continued)
lossOfTiming when an external clocking mode is configured but enabled 3

the external clock signal is not present. In that case
(not for Bridge and
the Crocus SHDSL switches to internal clocking
Router)
mode.
backupTiming when a preferred clocking mode is configured but disabled 2

the external clock signal is not present. In that case
(RS530, V35, V36,
the Crocus SHDSL switches to alternative clocking
X21 only)
mode.

Crocus SHDSL TMA subsystem picture of the Crocus SHDSL
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 table gives an overview of this chapter.
Section Title Page
11.1 Displaying the subsystem picture 190
11.2 Subsystem picture elements 191
Note that the figures in this chapter are those of a Crocus SHDSL TT. Although the subsystem picture of
the CV has a different layout, the interpretation of the visual indications is the same.

TMA subsystem picture of the Crocus SHDSL Crocus SHDSL
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 Section 4.1 - Starting TMA on the
Crocus SHDSL.
2
In the TMA window, press on the subsystem picture button: .
The subsystem picture is
displayed:
3 To close the subsystem picture, press .

Crocus SHDSL TMA subsystem picture of the Crocus SHDSL
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 TT subsystem picture is displayed.
LED status
line status line pair status

DTE interface status
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 Section 2.7
- Front panel LED indicators.

TMA subsystem picture of the Crocus SHDSL Crocus SHDSL
Subsystem picture elements (continued)
Element Description
DTE interface This reflects the status of the DTE interface. The possible indications are:
Colour Explanation
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.
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 Section 10.2.1 - Configuration alarm attributes.
In case of a Router interface the LAN interface connector displays the
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 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:
Colour Explanation
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
Section 10.2.1 - Configuration alarm attributes.
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).
When TMA fails to upload the sub-system picture info (e.g. because TMA is disconnected), then the
LEDs and connectors are greyed-out.

Crocus SHDSL Software download
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 table gives an overview of this chapter.
Section Title Page
12.1 What is boot, loader and application software? 194
12.2 Important download issues 198
12.3 Downloading with TMA 199
12.4 Downloading with TML 200
12.5 Downloading in loader mode 201
12.6 Downloading in boot mode 202
12.7 Downloading via the Orchid 1003 LAN 203

Software download Crocus SHDSL
12.1 What is boot, loader and application software?

This section explains the difference between boot, loader and application software. The following table
gives an overview of this section.
Section Title Page
12.1.1 What is boot software? 195
12.1.2 What is loader software? 196
12.1.3 What is application software? 197

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.

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

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.

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 Section 1.4 - Application software overview.
When you upgrade the application software of a Crocus SHDSL which contains the loader software
T2137004 or T2142xxx, then 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 an Orchid 1003 LAN (i.e. it is present in the Orchid 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 distribution feature of the Orchid
1003 LAN.
It is not possible to use the software distribution feature of the Orchid 1003 LAN 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.

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 Section 4.1 - Starting TMA on the Crocus SHDSL.
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.

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 is

C:\Program Files\TMA.
4 Place the software file you want to download in this directory.
5 Type the following command: 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.

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:
loader mode 2 (TT & CV) on Normal operation.
To download application software to a Crocus SHDSL in loader mode, proceed as follows:
Step Action
2 Set DIP switch bank DS1 position 2 to off.

The Crocus SHDSL is now in loader mode.
4 Now proceed as explained in Section 12.4 - Downloading with TML.
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.

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:
boot mode 1 (TT & CV) on Normal operation.
To download loader software to a Crocus SHDSL in boot mode, proceed as follows:
Step Action
2 Set DIP switch bank DS1 position 1 to off.

The Crocus SHDSL is now in boot mode.
4 Now proceed as explained in Section 12.4 - Downloading with TML.
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.

12.7 Downloading via the Orchid 1003 LAN

If many Crocus SHDSL Card Version modems need a software update, it is more efficient to use the
software distribution feature of the Orchid 1003 LAN management concentrator. In that case, the
software file that is present on the file system of the Orchid 1003 LAN 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 Orchid its software distribution feature.
For more information, refer to the Orchid 1003 LAN manual.

Diagnostic tests Crocus SHDSL
13. Diagnostic tests

This chapter describes the diagnostic tests of the Crocus SHDSL. The following table gives an overview
of this chapter.
Section Title Page
13.1 Introducing the diagnostic tests 205
13.2 Error test 206
13.3 Analogue loop 207
13.4 Remote digital loop 208
13.5 Digital loop 209
13.6 Interface tests 210

Crocus SHDSL Diagnostic tests
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.
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, low.

(RDL test only)
Table 13.1: Diagnostic test originators
Example
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.
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 Section 6.5 - The test window), then the
originator is called keyboard.
by browsing the model using the testActivation action in the line object / status group (refer to Section
6.6 - The model browsing window), 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 Section 7.3 - Line configuration attributes). This attribute
determines how long a test lasts.

13.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:
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.
Clocking during an ET test

When an ET test is activated, the Crocus SHDSL switches to internal clocking mode.

13.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
represented as follows:
modulator
demodulator

Example:
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.
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
activated:
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.

13.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
modulator demodulator
demodulator modulator
Make sure that on the remote Crocus SHDSL the rdlDetect attribute is set to enabled (refer to Section 7.5.1 -
General interface configuration attributes). Else it is not possible to initiate an RDL test on the remote.

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.
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 clocking mode.

13.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
local Crocus SHDSL
modulator
demodulator

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.

13.6 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.
Available tests Description
interfaceAl For
RS530, V35 and V36 the activation of the AL test signal (circuit 141)
G703 Nx64 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 Section 13.3 - Analogue loop.
interfaceRdl For
RS530, V35 and V36 the activation of the RDL test signal (circuit 140)
G703 Nx64 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 Section 13.4 - Remote digital loop.

Crocus SHDSL Technical specifications
14. Technical specifications

This chapter gives the technical specifications of the Crocus SHDSL. The following table gives an
Section Title Page
14.1 Crocus SHDSL types 212
14.2 Line specifications 212
14.3 RJ45 RJ12 adapter specifications 213
14.4 Maximum covered distance on a noise free line 214
14.5 G703 interface specifications 215
14.6 Management interface 216
14.7 Control connector 216
14.8 Diagnostic tests 217
14.9 Power requirements 217
14.10 Environmental compliance 217
14.11 Safety compliance 218
14.12 Over-voltage and over-current protection compliance 218
14.13 EMC compliance 218
14.14 Mechanical dimensions 218

Technical specifications Crocus SHDSL
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: RJ12
Impedance: 135 ohm
Coding: TC PAM, compliant to ITU-T G.991.2 (G.SHDSL)
Line speeds:
1 pair: N x 64 kbps (N = 1 36)
2 pair: N x 128 kbps (N = 1 36)
Handshaking: compliant to G.994.1 (automatic speed negotiation) or fixed speed
Performance monitoring: compliant to G.826 (errored seconds, severely errored seconds,
unavailability seconds)
Round trip delay: 0.6 ms
In case of a G.703 Nx64 interface, the round trip delay ranges from 0.6 ms (unframed) over 0.8 ms
(framed, all timeslots on) up to 3.1 ms (framed, 3 timeslots on).
The line connector lay-out

The following table shows the connector layout of the RJ45 line connector.
Pin Signal Figure
1 not used
2 not used
3 line 2 (1) 1 8
4 line 1
5 line 1
6 line 2 (1)
7 not used
8 not used
(1)
For a Crocus SHDSL 2P (2 pair) version only.

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 2 (1)
3 line 1
1 6
4 line 1
5 line 2 (1)
6 not used
(1)
For a Crocus SHDSL 2P (2 pair) version only.

14.4 Maximum covered distance on a noise free line
Speed 0.4 mm 0.5 mm 0.6 mm 0.8 mm 1.0 mm 1.2 mm

(kbps) 26 AWG 24 AWG 22 AWG 20 AWG 18 AWG 16 AWG
(km) (km) (km) (km) (km) (km)
64 10,2 13,5 16,8 23,5 30,6 37,7

128 8,5 11,2 13,9 19,4 25,4 31,3
192 7,3 9,6 12,0 16,8 21,9 27,0
256 7,0 9,2 11,6 16,1 21,0 25,9
320 7,0 9,2 11,6 16,1 21,0 25,9
384 6,8 8,9 11,1 15,5 20,3 25,0
448 6,7 8,8 11,1 15,4 20,1 24,8
512 6,5 8,5 10,6 14,8 19,4 23,9
576 6,4 8,4 10,5 14,6 19,1 23,5
640 6,2 8,2 10,2 14,3 18,6 22,9
704 6,1 8,1 10,1 14,0 18,3 22,6
768 5,0 6,6 8,3 11,5 15,0 18,5
832 5,8 7,6 9,5 13,2 17,3 21,3
896 5,6 7,3 9,2 12,8 16,7 20,5
960 5,2 6,8 8,5 11,8 15,5 19,1
1024 5,4 7,1 8,9 12,4 16,2 20,0
1088 5,3 6,9 8,7 12,1 15,8 19,4
1152 5,0 6,6 8,3 11,5 15,0 18,5
1216 5,0 6,6 8,3 11,5 15,0 18,5
1280 4,5 5,9 7,4 10,4 13,5 16,7
1344 4,3 5,7 7,1 9,9 12,9 15,9
1408 4,6 6,1 7,6 10,6 13,8 17,0
1472 4,6 6,1 7,6 10,6 13,8 17,0
1536 4,5 5,9 7,3 10,2 13,4 16,5
1600 4,6 6,1 7,6 10,6 13,8 17,0
1664 4,6 6,1 7,6 10,6 13,8 17,0
1728 4,4 5,7 7,2 10,0 13,1 16,1
1792 4,4 5,7 7,2 10,0 13,1 16,1
1856 4,3 5,7 7,1 9,9 12,9 15,9
1920 4,3 5,7 7,1 9,9 12,9 15,9
1984 4,2 5,5 6,8 9,5 12,5 15,4
2048 3,9 5,1 6,4 8,9 11,6 14,2
2304 3,9 5,1 6,4 8,9 11,6 14,2

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 Nx64
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 Nx64): 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 Nx64): framed or unframed (configurable), framing compliant to G.704
Time slots (G703 Nx64):
1 pair: N x 64 kbps (N = 1 32)
2 pair: N x 128 kbps (N = 1 16)
CRC4 insertion (G703 Nx64): enabled, disabled or automatic detection (configurable)

14.6 Management interface connectors

The possible management interface connectors are:
Management interface connector Connector type Speed
asynchronous through the control connector 9 pins subD 9600 bps, 8+N
(on the Crocus SHDSL)
synchronous through the Orchid 1003 LAN backplane DIN 800 kbps
and the high speed bus
(on the CN4 card nest)
For all available management tools, refer to Section 1.7 - Management overview.
14.7 Control connector

The control connector (sometimes also called control port) is a 9 pins subD connector that is labelled
CTRL. The signals on this connector are V.24 / V.28 signals.
The control connector layout

The control connector has the following pin layout:
Pin Signal DCE Figure
1 not used -
2 NMS RxD output
3 NMS TxD input 1

6
4 not used - 2
7
5 GND - 3
8
6 not used - 4
9
5
7 not used -
8 not used -
9 not used -
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.

14.8 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.9 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 9W
-48 Vdc (-36 Vdc ! -72 Vdc) - 4W
Table Top 2P 230 Vac (85 ! 265 Vac) 45 60 Hz 15 W
-48 Vdc (-36 Vdc ! -72 Vdc) - 8W
Card Version 1P -48 Vdc (-36 Vdc ! -72 Vdc) - 8W
Card Version 2P -48 Vdc (-36 Vdc ! -72 Vdc) - 16 W
14.10 Environmental compliance

Storage conditions: ETSI ETS 300 019-1-1 Class 1.1. In addition, the storage temperature has to be
between -25 to +70C
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 45C
or
relative humidity 0 to 95% non-condensing and ambient operational temperature -10 to 50C
Maximum altitude: 3000m
International protection (IP) class of protection against solid and liquids: IP40

14.11 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.12 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
recommendations.
14.13 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.14 Mechanical dimensions

The mechanical dimensions are as follows:
Dimensions Table Top Card Version CN4 Card Nest
height (mm) 45 20 270
width (mm) 220 235 445 without rackmounts
depth (mm) 215 excl. interface 300 330 excl. interface

235 incl. interface 350 incl. interface
weight (kg) 0.75 (excl. interface) 1 6.1 (excl. cards)

Crocus SHDSL
Annexes
Annexes 219
Crocus SHDSL
220 Annexes
Crocus SHDSL Annex A: abbreviations
Annex A: abbreviations
The following table gives a list of abbreviations and their description.
Abbreviation Description
AIS Alarm Indication Signal
AL Analogue Loop
AMI Alternate Mark Inversion
BER Bit Error Rate
bps bits per second
CN4 Card Nest 4
CRC Cyclic Redundancy Check
CTRL ConTRoL
CTS Clear To Send
CV Card Version
CV-A Card Version modem A
CV-B Card Version modem B
DCE Data Communications Equipment
DIP Dual In line Pin
DL Digital Loop
DS Dip Switch bank
DTE Data Terminal Equipment
ERR Error
ET Error Test
ExtTxClk External Transmit Clock
FAS Frame Alignment Signal
HDB3 High Density Bipolar 3
HDSL High bit rate Digital Subscriber Line
SHDSL Single pair HDSL
if interface
IP Internet Protocol
LAN Local Area Network
LED Light Emitting Diode
LFA Loss of Frame Alignment
LOS Loss Of Signal
Annexes 221
Annex A: abbreviations Crocus SHDSL
Annex A: abbreviations (continued)
Abbreviation Description
MIB Management Information Base
NMS Network Management System
PWR Power
RDL Remote Digital Loop
RTS Request To Send
Rx Receive
RxClk Receive Clock
RxD Receive Data
SDSL Symmetric Digital Subscriber Line
SELV Safety Extra Low Voltage
SNMP Simple Network Management Protocol
SSR Solid State Relay
TMA Telindus Maintenance Application
TML Telindus Memory Loader
TNV Telecom Network Voltage
TST Test
TT Table Top
Tx Transmit
TxClk Transmit Clock
TxD Transmit Data
WAN Wide Area Network
222 Annexes
Crocus SHDSL Annex B: product information
Annex B: product information

The following table displays the product information of the Crocus SHDSL basic units.
Sales code Product name Description

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 !)
171975 CROCUS SHDSL 2P 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
177936 CROCUS SHDSL + LCD 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 (Only manufactured after order !)
170814 CROCUS SHDSL 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
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 !)
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
177937 CROCUS SHDSL + LCD TT BU 48VDC Crocus SHDSL table top on 1 line pair, Basic Unit, Keyboard
and LCD for local programming, no interface provided.
Interface module available as separate sales item. 48 Vdc
(Only manufactured after order !)
171284 CROCUS SHDSL 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
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.
171285 CROCUS SHDSL TWIN-CV BU Crocus SHDSL twin CV on 1 line pair, suitable for CN4. Basic
Unit, no interfaces provided. Interface modules (2 modules
required) available as separate sales items.
Annexes 223
Annex B: product information Crocus SHDSL
Annex B: product information (continued)

The following table displays the product information of the Crocus SHDSL DTE interfaces.

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.
The following table displays the product information of the Crocus SHDSL documentation.

171971 MANUAL CROCUS SHDSL (E) Manuals are delivered with the product in electronic format
(CD-ROM) for environmental reasons. If however a hardcopy
(print-out) of the manual is required, this sales item can be
used. Between brackets an indication of the language.
224 Annexes

M SHDSL

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M SHDSL

Uploaded by

Copyright:

Available Formats

Crocus SHDSL

Interface Connector Circuit

line RJ12 TNV-1

management subD SELV

Version 1.5 03 December 2002

http://www.telindusproducts.com ! Products ! Choose a product ! Download certificates

, TELINDUS Crocus SHDSL

Organisation of this manual

Part This part

Annexes gives additional information.

Chapter This chapter

1 introduces the Crocus SHDSL.

4 introduces the Telindus Maintenance Application (TMA) and keyboard management. It

Chapter This chapter

7, 8, 9, 10 describes the configuration, status, performance and alarm attributes, respectively.

12 gives a software download procedure.

13 uncovers the available diagnostic test functions.

14 summarises the technical specifications of the Crocus SHDSL.

The following table gives an overview of the annexes.

Annex This annex

Annex A gives a list of abbreviations.

Annex B shows ordering information.

Conventions used in this manual

The format is used to indicate

Normal normal text.

Italic new or emphasised words

Computer computer output and code examples, e.g. NOK,1,1,Invalid command.

Blue underlined a hyperlink to a web site, e.g. http://www.telindus.com

Icon Name Description

Remark Useful information or tips.

Application software version

2. Installing and connecting the Crocus SHDSL .................................................... 11

3. DIP switches and straps of the Crocus SHDSL.................................................. 37

4. Managing the Crocus SHDSL............................................................................... 48

Continued on next page

Table of contents (continued)

6. The front panel display .......................................................................................110

Reference manual .................................................................................. 117

8. Status attributes ..................................................................................................144

9. Performance attributes .......................................................................................165

10. Alarm attributes ...................................................................................................176

Continued on next page

Table of contents (continued)

11. TMA subsystem picture of the Crocus SHDSL................................................. 189

12. Software download ............................................................................................. 193

13. Diagnostic tests .................................................................................................. 204

14. Technical specifications..................................................................................... 211

Annex B: product information.................................................................................. 223

1. Introducing the Crocus SHDSL

Section Title Page

1.1 Crocus SHDSL features 4

1.2 Crocus SHDSL product overview 5

1.3 DTE interface overview 6

1.4 Application software overview 7

1.5 Power back-off 8

1.6 CN4 card nest 8

1.7 Management overview 9

1.1 Crocus SHDSL features

1.2 Crocus SHDSL product overview

The following table gives a description of the used abbreviations:

Abbreviation In full Explanation

TT Table Top This is a stand-alone version of the Crocus SHDSL. It is

1P 1 pair The line connection is made over 1 line pair.