Crocus Inverse Multiplexer - Route 66 Communications

Crocus Inverse Multiplexer 


USER and REFERENCE MANUAL 

Version: 2.2 191971 

Telindus Technical Publications – Geldenaaksebaan 335 ⋅ B-3001 Leuven ⋅ Belgium – tel. +32 16 382011

Copyright, safety and statements 


Document properties 

Subject 

Manual type 


USER and REFERENCE MANUAL 

Version 2.2 

Code 191971 

Modification date 02 August 2004 ©Telindus 

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. 

ii



Safety requirements 

Carefully read the safety instructions at the beginning of Chapter 2 - Installing and connecting the Crocus 

Inverse Multiplexer, page 14. 

The interfaces on the Crocus Inverse Multiplexer should only be connected to circuit types as listed 

below. 

Connector Interface Circuit 

RJ45 

COAX 

RJ45 

COAX 

COAX 

RJ45 

COAX 

COAX 

RJ45 

COAX 

COAX 

RJ45 

COAX 

COAX 

station clock 

link 1 

link 1 Tx-in 

link 1 Tx-out 

link 2 

link 2 Tx-in 

link 2 Tx-out 

link 3 

link 3 Tx-in 

link 3 Tx-out 

link 4 

link 4 Tx-in 

link 4 Tx-out 

SELV 

SELV 

SELV 

SELV 

SELV 

SubD9 management SELV 

RJ45 LAN SELV 

• SELV (Safety Extra Low Voltage): local connection (e.g. PC to Crocus Inverse Multiplexer) or leased 

line inside the building 

iii



Statements 

http://www.telindusproducts.com ! Telindus Access Solutions ! Products ! Choose a product ! 

Downloads ! Certificates 

Hereby, TELINDUS declares that this Crocus Inverse Multiplexer is in compliance with the essential 

requirements and other relevant provisions of Directive 1999/5/EC. 

Bij deze verklaart TELINDUS dat deze Crocus Inverse Multiplexer in overeenstemming is met de 

essentiële vereisten en andere relevante bepalingen van Richtlijn 1999/5/EC. 

Par la présente, TELINDUS déclare que ce Crocus Inverse Multiplexer est en conformité avec les 

exigences essentielles et autres articles applicables de la Directive 1999/5/EC. 

Hiermit, TELINDUS erklärt daß dieser Crocus Inverse Multiplexer in Fügsamkeit ist mit den wesentlichen 

Anforderungen und anderen relevanten Bereitstellungen von Direktive 1999/5/EC. 

Mediante la presente, TELINDUS declara que el Crocus Inverse Multiplexer cumple con los requisitos 

esenciales y las demás prescripciones relevantes de la Directiva 1999/5/CE. 

A TELINDUS declara que o Crocus Inverse Multiplexer cumpre os principais requisitos e outras 

disposições da Directiva 1999/5/EC. 

Col presente, TELINDUS dichiara che questo Crocus Inverse Multiplexer è in acquiescenza coi requisiti 

essenziali e stipulazioni attinenti ed altre di Direttivo 1999/5/EC. 

Με το παρόν, η TELINDUS δηλώνει ότι αυτό το Crocus Inverse Multiplexer είναι συµµορφούµενο µε τις 

βασικές απαιτήσεις και µε τις υπόλοιπες σχετικές διατάξεις της οδηγίας 1999/5/EC. 

iv


Preface 

Organisation of this manual 

This manual contains three main parts. 

Part 

User manual 

Reference manual 

Annexes 

This part … 

shows you how to install and connect the Crocus Inverse Multiplexer. 

gives more detailed information on the Crocus Inverse Multiplexer. It contains a 

complete description for lookup purposes. 

gives additional information. 

The following table gives an overview of the chapters in the user manual. 

Chapter 

This chapter … 

1 introduces the Crocus Inverse Multiplexer. 

2 explains how to install and connect the Crocus Inverse Multiplexer. It also describes the 

front panel LED indicators. 

3 locates the DIP switches of the Crocus Inverse Multiplexer on the motherboard. It also 

gives a procedure to change the DIP switch settings. 

4 introduces and describes the tools with which the Crocus Inverse Multiplexer can be 

managed. It is in this chapter that the attributes of the Crocus Inverse Multiplexer are 

introduced. It also shows how to connect the Crocus Inverse Multiplexer to the Telindus 

Maintenance Application. 

5 teaches you the basics to configure the Crocus Inverse Multiplexer, in a step-by-step 

manner. 

The following table gives an overview of the chapters in the reference manual. 

Chapter 

This chapter … 

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

10 displays and labels the different elements of the Telindus Maintenance Application 

subsystem picture. 

11 gives a firmware download procedure. 

12 uncovers the available diagnostic test functions. 

13 summarises the technical specifications of the Crocus Inverse Multiplexer. 

14 explains how to replace the fuses. 

v

Preface 


The following table gives an overview of the annexes. 

Annex 

Annex A 

This annex … 

shows ordering information. 

vi


Preface 

Conventions used in this manual 

Typographical conventions 

The following typographical conventions are used in this manual. 

The format … 

Normal 

Italic 

Computer 

Computer Bold 

Narrow 

Blue 

Blue underlined 

is used to indicate … 

normal text. 

• new or emphasised words 

• file names and directory paths, e.g. C:\Program Files\TMA\bin\Tma.exe 

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

text you have to enter at the prompt, e.g. Get sysName. 

objects and attributes in the containment tree of a device when they are 

mentioned in the normal text. I.e. when they are not a part of computer input or 

output. 

references to other parts in the manual, e.g. refer to Chapter xx - Technical 

specifications. 

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 

Warning 

Read the text that follows carefully in order to avoid damage to the 

device. 

Read the text that follows carefully in order to avoid injury. 

DIP switch 

Basic TMA 

parameter 

Advanced TMA 

parameter 

Action 

A configuration attribute of the Crocus Inverse Multiplexer which can be 

set with the DIP switches. 

A basic attribute of the Crocus Inverse Multiplexer which can be set with 

the Telindus Maintenance Application (TMA). 

An advanced attribute of the Crocus Inverse Multiplexer which can be 

set with the Telindus Maintenance Application (TMA). 

An action which can be executed on the Crocus Inverse Multiplexer with 

the Telindus Maintenance Application (TMA). 

vii

Preface 


Firmware version 

This manual describes the features, containment tree and attributes of the Crocus Inverse Multiplexer 

firmware version T2701/00700. 

Audience 

This manual is intended for computer-literate people, who have a working knowledge of computing and 

networking principles. 

Related documentation 

This manual describes the hardware and features of the Crocus Inverse Multiplexer. This manual also 

often refers to manuals of other Telindus products. As the manual of this product, also these manuals can 

be found on the Telindus Access Products distribution CD that is delivered with the Telindus products. 

This CD not only contains all the Telindus product manuals, but also the free maintenance tool TMA and 

the firmware of the Telindus devices. 

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 qualityrelated 

comment concerning this delivery, please submit the Quality Comment Form on our web page at 

http://www.telindusproducts.com/quality. 

viii


Table of contents 


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

1. Introduction to the Crocus Inverse Multiplexer....................................................3 

1.1 Introducing the Crocus Inverse Multiplexer .....................................................................4 

1.2 What is inverse multiplexing..........................................................................................5 

1.3 Fall-back operation........................................................................................................10 

1.4 Link synchronisation......................................................................................................11 

1.5 E1 line interfaces...........................................................................................................12 

1.6 DCE interfaces ..............................................................................................................12 

1.7 Local Area Network interface ........................................................................................12 

1.8 Clocking.........................................................................................................................12 

1.9 Management .................................................................................................................13 

2. Installing and connecting the Crocus Inverse Multiplexer ................................14 

2.1 Safety instructions .........................................................................................................15 

2.2 Unpacking .....................................................................................................................16 

2.3 Selecting a site ..............................................................................................................17 

2.4 Installation and connection precautions ........................................................................18 

2.5 Connecting the Crocus Inverse Multiplexer...................................................................19 

2.6 Front panel LED indicators............................................................................................26 

3. DIP switches of the Crocus Inverse Multiplexer.................................................31 

3.1 Location of the DIP switches .........................................................................................32 

3.2 Overview of the DIP switches........................................................................................33 

3.3 Changing the DIP switch settings..................................................................................34 

4. Maintenance of the Crocus Inverse Multiplexer .................................................35 

4.1 Introduction to TMA .......................................................................................................36 

4.2 Connecting to a Crocus Inverse Multiplexer with TMA..................................................37 

4.3 Introduction to the attributes of the Crocus Inverse Multiplexer ....................................41 

5. Step-by-step configuration...................................................................................44 

5.1 Reading the configuration settings ................................................................................45 

5.2 Loading the default configuration ..................................................................................47 

5.3 Clocking.........................................................................................................................48 

5.4 Link and station clock impedance selection ..................................................................55 

5.5 Fall-back operation........................................................................................................56 

5.6 Link activation................................................................................................................57 

5.7 Basic LAN interface configuration .................................................................................57 

5.8 Basic DCE interface configuration.................................................................................58 

5.9 Configuring the management attributes ........................................................................60 

5.10 Activating the configuration ...........................................................................................66 

ix



Reference manual .................................................................................... 67 

6. Configuration attributes........................................................................................69 

6.1 Configuration attribute overview....................................................................................70 

6.2 Crocus Inverse Multiplexer configuration attributes ......................................................71 

6.3 LAN interface configuration attributes...........................................................................81 

6.4 DCE interface configuration attributes ..........................................................................82 

6.5 Link configuration attributes ..........................................................................................88 

6.6 SNMP proxy configuration attributes.............................................................................90 

6.7 Management configuration attributes............................................................................91 

7. Status attributes ....................................................................................................94 

7.1 Status attribute overview...............................................................................................95 

7.2 Crocus Inverse Multiplexer status attributes .................................................................97 

7.3 LAN interface status attributes....................................................................................101 

7.4 DCE interface status attributes ...................................................................................104 

7.5 Link status attributes ...................................................................................................109 

7.6 Management status attributes.....................................................................................112 

7.7 Operating system status attributes..............................................................................112 

8. Performance attributes .......................................................................................113 

8.1 Performance attribute overview ..................................................................................114 

8.2 Introduction to the performance attributes ..................................................................115 

8.3 Crocus Inverse Multiplexer performance attributes.....................................................117 

8.4 LAN interface performance attributes .........................................................................122 

8.5 Link performance attributes ........................................................................................123 

8.6 Operating system performance attributes...................................................................126 

9. Alarm attributes...................................................................................................128 

9.1 Alarm attribute overview..............................................................................................129 

9.2 Introduction to the alarm attributes .............................................................................130 

9.3 Crocus Inverse Multiplexer alarms..............................................................................132 

9.4 LAN interface alarms...................................................................................................134 

9.5 DCE interface alarms..................................................................................................135 

9.6 Link alarms..................................................................................................................136 

10. TMA subsystem picture of the Crocus Inverse Multiplexer.............................137 

10.1 Displaying the subsystem picture................................................................................138 

10.2 Structure of the subsystem picture..............................................................................139 

11. Firmware download.............................................................................................141 

11.1 Downloading with TMA ...............................................................................................142 

11.2 Downloading with TML................................................................................................143 

11.3 Downloading with TML in boot mode..........................................................................144 

11.4 Downloading with TFTP..............................................................................................145 

x



12. Diagnostic tests ..................................................................................................146 

12.1 Introduction to the diagnostic tests..............................................................................147 

12.2 Error test......................................................................................................................148 

12.3 Local link loop-back test ..............................................................................................149 

12.4 Reverse link / DCE loop-back test...............................................................................150 

12.5 Remote DCE loop-back test........................................................................................151 

12.6 DCE interface tests .....................................................................................................152 

13. Technical specifications.....................................................................................153 

13.1 Inverse multiplexing.....................................................................................................154 

13.2 E1 link interface...........................................................................................................154 

13.3 Station clock interface .................................................................................................155 

13.4 DCE interface ..............................................................................................................155 

13.5 LAN interface...............................................................................................................155 

13.6 Console port ................................................................................................................156 

13.7 Power requirements ....................................................................................................157 

13.8 Mechanical dimensions ...............................................................................................157 

13.9 Environmental requirements .......................................................................................157 

14. Fuse replacement................................................................................................158 

Annexes ..................................................................................................159 

Annex A: product information..................................................................................161 

xi


User manual 

User manual 1


2 User manual


Introduction to the Crocus Inverse Multiplexer 

1. Introduction to the Crocus Inverse Multiplexer 

This chapter gives an introduction to the Crocus Inverse Multiplexer. The following table gives an 

overview of this chapter. 

Section Title Page 

1.1 Introducing the Crocus Inverse Multiplexer 4 

1.2 What is inverse multiplexing 5 

1.3 Fall-back operation 10 

1.4 Link synchronisation 11 

1.5 E1 line interfaces 12 

1.6 DCE interfaces 12 

1.7 Local Area Network interface 12 

1.8 Clocking 12 

1.9 Management 13 

User manual 3



1.1 Introducing the Crocus Inverse Multiplexer 

The Crocus Inverse Multiplexer allows transparent transmission of high-speed synchronous data and this 

… 

• over an E1 network 

• at speeds up to 7808 kbps 

• using up to four standard E1 lines. 

This technology, called inverse multiplexing, provides a cost effective and high speed transmission 

medium for the interconnection of bridges, routers, etc. 

The following figure shows a basic application of the Crocus Inverse Multiplexer. Here, four HDSL E1 

modems are used to interconnect two Crocus Inverse Multiplexer units. 

HDSL 

HDSL 

INV 

HDSL 

HDSL 

INV 

MUX 

HDSL 

HDSL 

MUX 

HDSL 

HDSL 

4 User manual



1.2 What is inverse multiplexing 

This section gives a definition of inverse multiplexing. It also gives some information on compliance of the 

Crocus Inverse Multiplexer and E1 line interface, the framing structure and speeds. The following table 

gives an overview of this section. 


1.2.1 Definition 6 

1.2.2 Inverse multiplexing compliance 6 

1.2.3 E1 line interface compliance 6 

1.2.4 Inverse multiplexing E1 framing structure 7 

1.2.5 Cyclic Redundancy Check – CRC4 8 

1.2.6 Speeds 9 

User manual 5



1.2.1 Definition 

Inverse multiplexing is a technique that splits a high-speed data stream for parallel transmission over 

several lower-speed transmission paths. 

1.2.2 Inverse multiplexing compliance 

The Crocus Inverse Multiplexer implements this technique following the ISO/IEC 13871 (1995) 

specification. 

This is an ISO standard on Digital Channel Aggregation for 64 kbps channels. It is based on the industry 

bonding specification version 1.1. In the Crocus Inverse Multiplexer, this standard has been adapted: 

• The standard is adapted for E1 lines using mode 2 only. Mode 2 is a framed mode (248 octets per 

frame, 128 frames per multi-frame) with continuous line monitoring. 

• All operations related to call set-up / disconnect and bandwidth negotiation, as described in the 

standard, are not relevant in this inverse multiplexing application. 

• CRC4 on end-to-end basis is always in use. 

1.2.3 E1 line interface compliance 

Each E1 line interface of the Crocus Inverse Multiplexer complies with the ITU Recommendation G.703, 

G.704 and G.823. They operate at a nominal rate of 2048 kbps. The data transferred over the E1 lines is 

organised in frames. 

6 User manual



1.2.4 Inverse multiplexing E1 framing structure 

How is an inverse multiplexing E1 frame structured 

The standard 8-byte synchronisation header of each G.704/G.703 2048 kbps channel is stripped. This 

leaves 1984 kbps which is organised in a sequence of frames. Each frame is composed of 248 octets. 

Four of these octets (see below) are used to establish the framing structure and for the exchange of 

information with the far end. This leaves a total of 1952 kbps for the user. 

The four framing octets 

The four octets which are used to establish the framing structure and for the exchange of information with 

the far end are: 

Octet name Abbreviation Description 

Frame Alignment Word FAW This is monitored continuously in each channel. It is 

used to determine whether the inter-channel frame 

alignment has been lost and if so, to recover the frame 

alignment. 

Information Channel IC This provides in-band information exchange with the far 

end device. It offers a 6 kbps Network Management 

System (NMS) communication channel on each E1 link. 

However, only one of these four channels is really used. 

You could consider the other three channels to be backup 

channels. 

Frame Count FC This is used to measure the relative delay variance 

between the E1 channels. 

Cyclic Redundancy 

Check 

CRC 

This octet carries the CRC4 check. It is computed over 

the whole 1984 kbps channel available in G.704 and it 

provides an end-to-end quality monitoring of each 

individual E1 link. 

What is bonding 

Bonding is the restructuring of user data to include the additional information (as described above) 

required for multiplexing and de-multiplexing. 

The following figure shows an inverse multiplexing E1 framing structure: 

msb 

lsb 

D7 D6 D5 D4 D3 D2 D1 D0 

1 2 62 63 124 125 186 187 248 

D D FAW D IC D FC D CRC 

F1 F2 F127 F128 

FAW: Frame Alignment Word 

IC: Information Channel 

FC: Frame Count 

CRC: Cyclic Redundancy Check 

D: Data octet (D7...D0) 

F1…F128: Frames 

User manual 7



1.2.5 Cyclic Redundancy Check – CRC4 

The CRC4 check provides an end-to-end quality monitoring of each individual E1 link. Two types of 

CRC4 checks can be run over a specific link: 

• CRC4 link check (can be enabled or disabled by the user) 

• CRC4 bonding check (is always enabled). 

The following figure displays the two types of CRC4 checks: 

HDSL 

HDSL 

HDSL 

HDSL 

INV 

HDSL 

HDSL 

HDSL 

HDSL 

INV 

MUX 

HDSL 

HDSL 

HDSL 

HDSL 

MUX 

HDSL 

HDSL 

HDSL 

HDSL 

CRC4 link check 

CRC4 bonding check 

8 User manual



1.2.6 Speeds 

The Crocus Inverse Multiplexer uses up to four E1 lines for data transmission. This means it can transmit 

data at a rate of 1952, 3904, 5856 and 7808 kbps, depending on how many E1 lines are used. 1952 kbps 

is also supported as a fall-back rate. 

The user can activate or deactivate each E1 line. 

The throughput delay of the Crocus Inverse Multiplexer is kept to an absolute minimum. It adds only 50µs 

to the differential delay of the E1 lines. 

The following figure gives an overview of the speeds in a Crocus Inverse Multiplexer set-up: 

1952Kbps 1984Kbps 2048Kbps 

2048Kbps 

1984Kbps 

1952Kbps 

1952 kbps, 

3904 kbps, 

5856 kbps, 

7808 kbps 

V.35, 

V.36, 

X.21, 

RS-530, 

Bridge 

MUX 

bonding 

bonding 

bonding 

bonding 

G.704 framing 

G.704 framing 

G.704 framing 

G.704 framing 

G.704 framing 

G.704 framing 

G.704 framing 

G.704 framing 

bonding 

bonding 

bonding 

bonding 

MUX 

1952 kbps, 

3904 kbps, 

5856 kbps, 

7808 kbps 

V.35, 

V.36, 

X.21, 

RS-530, 

Bridge 

G.703 

G.703 



User manual 9



1.3 Fall-back operation 

What is fall-back operation 

If one of the E1 lines fails, then the Crocus Inverse Multiplexer automatically selects the following lower 

available speed and continues data transmission at this fall-back rate. 

If the E1 recovers, then the Crocus Inverse Multiplexer automatically returns to the original rate selected 

by the user. 

Before enabling the fall-back feature, make sure your data terminal equipment tolerates changes in the 

data rate. 

How does fall-back operation work 

Fall-back is based on a permanent line quality monitoring of each E1 line. The line quality … 

• is determined by the CRC4 bonding errors, Loss Of Frame alignment (LOF) and Alarm Indication 

Signal (AIS) errors 

• is monitored on both ends of the link 

• information is exchanged between the Crocus Inverse Multiplexers at both ends of the link. 

If the Crocus Inverse Multiplexer detects an unacceptable line quality at one side of the link, then the line 

is deactivated in both directions. Data transfer stops temporarily and the lines resynchronise. Then the 

Crocus Inverse Multiplexer continues data transmission in fall-back mode. 

If during data transfer the deactivated line is found to be OK again in both directions, then the line is 

reactivated. Data transfer stops temporarily and the lines resynchronise. Then the Crocus Inverse 

Multiplexer continues data transmission over the originally selected number of lines. 

10 User manual



1.4 Link synchronisation 

The Crocus Inverse Multiplexer can compensate for a differential delay of up to 64 ms between the four 

E1 lines. I.e. if the differential delay is not higher than 64 ms, the Crocus Inverse Multiplexer is able to 

reconstruct the original data at the remote side. 

The Crocus Inverse Multiplexer can also detect the interchanging of the E1 lines. What is more, it can 

correctly re-assembly the E1 lines should they be interchanged. 

These two capabilities allows routing over different paths or different facilities for increased flexibility and 

reliability. 

Take care when you activate less E1 lines than the total available number of E1 lines. In that case, the 

unused lines should be connected directly to the same line numbers on both units. This to enable 

automatic line change-over. The Crocus Inverse Multiplexer will generate a warning in case of incorrect 

connection of unused lines. 

On the other hand, when activating the automatic fall-back feature, this cross connect correction operates 

automatically again. 

User manual 11



1.5 E1 line interfaces 

The Crocus Inverse Multiplexer provides four E1 line interfaces. Each E1 line interface of the Crocus 

Inverse Multiplexer … 

• has one 120 ohm RJ45 connector and two 75 ohm coaxial BNC connectors 

• operates at a nominal rate of 2048 kbps 

• complies with the ITU Recommendation G.703 and G.704 

• its jitter performance complies with the ITU Recommendation G.823 

• supports the CRC4 option as specified in the ITU Recommendation G.704 

• enables the activation or deactivation of the CRC4 insertion. 

1.6 DCE interfaces 

A complete range of plug-in DCE interface modules makes the Crocus Inverse Multiplexer ideal for 

interfacing with almost any application. The DCE interface modules are: 

• RS-530 

• V35 

• V36 

• X21 

• Router 10M 

All these DCE interface modules can be exchanged in only a few seconds. They are also are 

interchangeable between the different members of the Telindus Crocus family. 

1.7 Local Area Network interface 

The Crocus Inverse Multiplexer offers a 10Base-T Ethernet interface for management purposes over an 

IP network. 

1.8 Clocking 

All clock signals on the Crocus Inverse Multiplexer are conform to the … 

• ITU Recommendation G.732. I.e. the characteristics of primary PCM multiplex equipment operating at 

2048 kbps. 

• ITU Recommendation G.823. I.e. the control of jitter and wander within digital networks based on the 

2048 kbps hierarchy. 

12 User manual



1.9 Management 

The Crocus Inverse Multiplexer is manageable in many different ways: 

• You can connect the Telindus Maintenance Application (TMA) to the Crocus Inverse Multiplexer both 

over a serial connection (through the auxiliary connector) or over IP. 

• Using any terminal emulation program, you can establish a serial connection with the Crocus Inverse 

Multiplexer (through the auxiliary connector). Then you can choose between a windows-driven menu 

for occasional users (ATWIN) and a command line user interface for experienced users (CLI). 

• Alternatively, you can make a Telnet connection to the Crocus Inverse Multiplexer. Again you can 

choose between ATWIN or CLI. 

• You can manage it with TMA CLI, an advanced Command Line Interface with extra scripting 

capabilities. Contact your distributor for more information on this product. 

• You can manage it with TMA for HP OpenView, the Telindus integrated management application that 

runs on the HP OpenView platform. Contact your distributor for more information on this product. 

• You can manage the Crocus Inverse Multiplexer through SNMP. The Crocus Inverse Multiplexer 

supports MIB2 and a private MIB, including traps. The private MIB comes with your copy of TMA. After 

installation of the TMA data files, the private MIB file is available in directory C:\Program 

Files\TMA\snmp with the name e3mux.mib. The first part of the directory path may be different if you 

did not choose the default path during the installation of the TMA data files. 

• Using the Orchid 1003 LAN management concentrator in combination with the Crocus Inverse 

Multiplexer also offers extra management features (software distribution and consistency, 

configuration distribution and consistency, etc.). 

User manual 13

Installing and connecting the Crocus Inverse Multiplexer 


2. Installing and connecting the Crocus Inverse Multiplexer 

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

Crocus Inverse Multiplexer. 

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 Inverse Multiplexer 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. 


2.1 Safety instructions 15 

2.2 Unpacking 16 

2.3 Selecting a site 17 

2.4 Installation and connection precautions 18 

2.5 Connecting the Crocus Inverse Multiplexer 19 

2.6 Front panel LED indicators 26 

14 User manual



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 product 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 sämtlichen Arbeiten am Gerät (Installation, Einstellungen, Reparaturen etc.) sollten Sie den 

Netzstecker aus der Steckdose ziehen. 

Die Sicherheit dieses Gerätes ist abhängig von dem dritten Kontakt (dem Erdungspin) des 3-poligen 

Steckers. Beachten Sie unbedingt diese Sicherheitsstandard. Sollten Sie nur eine ältere 2-polige 

Steckdose zur Verfügung haben, lassen Sie diese von einem Elektriker gegen eine 3-polige Steckdose 

auswechseln. 

SAFETY WARNING 

To avoid damage to the equipment, please observe all procedures described in this chapter. 

SICHERHEITSBESTIMMUNGEN 

Um eine Beschädigung des Gerätes 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. 

User manual 15



2.2 Unpacking 

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. 

The Crocus Inverse Multiplexer comes with the following items: 

• a 2m power cord 

• rack mounting material 

• desktop mounting material 

• CD-ROM containing the TMA program, the TMA model files and this manual. 

16 User manual



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 Gerät niemals seitlich, sondern nur auf den Füßen auf und achten Sie darauf, daß die 

Lüftungsschlitze an der Seitenverkleidung frei bleiben. 

Stapeln Sie nicht mehrere Geräte direkt übereinander, dies kann zu einem Hitzestau führen. 

Install the unit in an area free of extreme temperatures, humidity, shock and vibration. Position it so that 

you can easily see and access the front panel and its control indicators. Leave enough clearance at the 

back for cables and wires. Position the unit within the correct distances for the different accesses and 

within 2m of a power outlet. 

User manual 17



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 is fully EMC compliant. To ensure compliance with EMC directive 

89/336/EEC, shielded cables or ferrite beads have to be used. 

NOTE 

This equipment may be powered by an IT power system. 

ANMERKUNG 

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

18 User manual



2.5 Connecting the Crocus Inverse Multiplexer 

This section explains how to connect the Crocus Inverse Multiplexer. The following table gives an 

overview of this section. 


2.5.1 Mounting desktop or rack parts on the Crocus Inverse Multiplexer 20 

2.5.2 Crocus Inverse Multiplexer connections 21 

2.5.3 Connecting the power supply 22 

2.5.4 Voltage selection – 230/115 Vac 22 

2.5.5 Signal and protective ground interconnection 23 

2.5.6 Connecting the station clock 24 

2.5.7 Connecting the links 24 

2.5.8 Connecting a LAN 24 

2.5.9 Inserting the DCE interface 25 

User manual 19



2.5.1 Mounting desktop or rack parts on the Crocus Inverse Multiplexer 

The Crocus Inverse Multiplexer can be mounted as a rack or desktop model. The following figure shows 

you which parts to mount for which model: 

rack 

mount 

model 

desktop 

model 

After you mounted the rack model parts, you can directly install the Crocus Inverse Multiplexer into an 

industry standard 19” rack. The Crocus Inverse Multiplexer only occupies 1 unit (44.4 mm) of space in the 

rack. 

20 User manual



2.5.2 Crocus Inverse Multiplexer connections 

Most connections have to be made at the back of the Crocus Inverse Multiplexer. The following figure 

gives a rear view of the Crocus Inverse Multiplexer. 

PWR 

TO DTE 

STATION CLOCK LINK4 LINK3 LINK2 LINK1 

TPI 

TX-OUT TX-IN TX-OUT TX-IN TX-OUT TX-IN TX-OUT 

1 2 3 4 5 6 7 8 

The following table labels the different parts located at the rear of the Crocus Inverse Multiplexer. 

TX-IN 

Number 

Part 

1 power inlet 

2 station clock connectors (1 RJ45; 1 BNC) 

3 link 4 connectors (1 RJ45, 2 BNC) 




7 DCE interface 

8 TPI connector (RJ45) 

User manual 21



2.5.3 Connecting the power supply 

The following table explains how to connect the power supply. The Crocus Inverse Multiplexer exists in 

two different models: 

model Connector type Connecting the power supply 

230/115 Vac standard IEC 

power supply 

connector 

For a 230/115 Vac model, connect the standard IEC power 

supply connector to the power inlet. Refer to Section 2.5.2 - 

Crocus Inverse Multiplexer connections 

24 Vdc or 48 Vdc 3 pin power supply 

connector 

For a 24/48 Vdc model, a 3 pin power supply connector is 

delivered with the Crocus Inverse Multiplexer. 

The + and – indications are with respect to each other, not 

to ground level. This means that for a … 

• –24/48 Vdc connection: the ground has to be connected 

to +, while the negative voltage has to be connected to 

the –. 

• 24/48 Vdc connection: the ground has to be connected 

to the –, while the positive voltage has to be connected 

to the +. 

2.5.4 Voltage selection – 230/115 Vac 

The 230/115 Vac model of the Crocus Inverse Multiplexer can be supplied with either 230 Vac or 115 

Vac. The Crocus Inverse Multiplexer detects automatically which voltage is used, and adapts its power 

supply accordingly. Therefore, no manual selection has to be made. 

22 User manual



2.5.5 Signal and protective ground interconnection 

With strap ST18, you can configure the interconnection between signal ground and protective ground 

(earth). The following figure shows the position of ST18 on the Crocus Inverse Multiplexer motherboard: 

ST18 

3 

2 

1 

Strap settings Connection Description 

1 2 3 

1 2 3 

1 2 3 

disconnected 

connected through 

100 ohms resistor 

directly connected 

As default, the signal ground is disconnected from the earth. 

This avoids problems which might occur when the earth 

potential of the Crocus Inverse Multiplexer and the connected 

application is not the same. In such a situation earth current 

loops may induce distortion on the transmitted data, resulting 

in transmission errors. 

Sometimes you might want to connect the Crocus Inverse 

Multiplexer earth to the application earth although both earth 

potentials are not the same. (E.g. to avoid a big difference 

between both earth potentials.) To avoid that high earth 

currents are generated, you can make this connection through 

a 100 ohms resistor. 

Sometimes it is not possible to connect the application directly 

to the earth. In that case you can earth the application through 

the Crocus Inverse Multiplexer by connecting the Crocus 

Inverse Multiplexer to the earth and setting strap ST18 in 

position 3. 

Also the opposite situation might occur: it is not possible to 

earth the Crocus Inverse Multiplexer. In that case you can 

earth the Crocus Inverse Multiplexer through the application by 

connecting the application to the earth and setting strap ST18 

in position 3. 

Make sure that the Crocus Inverse Multiplexer and its network units all use the same earth. This avoids 

noise interference. 

User manual 23



2.5.6 Connecting the station clock 

The E1 transmit clocks and DCE interface clock can be derived from the 

station clock. At the back of the Crocus Inverse Multiplexer, two station 

clock connectors are provided: 

STATION CLOCK 

• a 75 ohm coaxial BNC connector 

• a 120 ohm RJ45 connector. 

Refer to Section 2.5.2 - Crocus Inverse Multiplexer connections for the position of the station clock 

connectors. 

Connect the station clock either to the BNC connector or the RJ45 connector. 

Using one of these two connector types also involves configuring the correct termination resistance. 

Refer to Section 5.4 - Link and station clock impedance selection. 

2.5.7 Connecting the links 

The Crocus Inverse Multiplexer can multiplex / de-multiplex a DTE 

data stream in up to four E1 links. At the back of the Crocus Inverse 

Multiplexer, the four links can be connected. Each link has … 

LINK1 

• two 75 ohm coaxial BNC connectors 

• one 120 ohm RJ45 connector. 

TX-OUT 

TX-IN 

Refer to Section 2.5.2 - Crocus Inverse Multiplexer connections for the position of the link connectors. 

Connect a link either to the BNC connectors or the RJ45 connector. 

Using one of these two connector types also involves configuring the correct termination resistance. 

Refer to Section 5.4 - Link and station clock impedance selection. 

2.5.8 Connecting a LAN 

You can connect the Crocus Inverse Multiplexer to a Local Area Network (LAN) for management 

purposes. For instance to open a TMA session over an IP network or for management solutions with the 

Orchid 1003 LAN in combination with e.g. HP OpenView. 

At the back of the Crocus Inverse Multiplexer, a 120 ohm RJ45 TPI port is provided. 

Refer to Section 2.5.2 - Crocus Inverse Multiplexer connections for the position of the 

TPI port. 

TPI 

24 User manual



2.5.9 Inserting the DCE interface 

At the back of the Crocus Inverse Multiplexer, an empty slot is provided in which you can insert the 

desired DCE interface module without opening the housing. 

To insert the DCE interface in the Crocus Inverse Multiplexer, proceed as follows: 

Step 

Action 

1 Gently slide the DCE 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 DCE interface is present, connect the application. 

User manual 25



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


2.6.1 Introduction to the front panel LEDs 27 

2.6.2 Power LED 28 

2.6.3 LAN interface LEDs 28 

2.6.4 Test LED 28 

2.6.5 Link LEDs 29 

2.6.6 DCE interface LEDs 30 

26 User manual



2.6.1 Introduction to the front panel LEDs 

When all the connections are made and the Crocus Inverse Multiplexer is powered, the LEDs on the front 

panel reflect the actual status. The following figure shows the front panel of the Crocus Inverse 

Multiplexer. 

LINK ALARM 

2 

3 

4 

LAN LOS AIS LOS AIS LOS AIS LOS AIS 

DTE CONSOLE 

LOF ERR LOF ERR LOF ERR LOF ERR 

PWR LNK COL TXD RXD TST 

The following table lists the front panel LED indicators with their corresponding label and colour. 

Front panel LED indicator Label Colour Assignment 

power LED PWR green The complete device. 

link LED LNK green The LAN interface. 

collision LED COL red 

transmit LED TXD green 

receive LED RXD green 

test LED TST red The four links and DCE interface. 

loss of signal / 

loss of frame alignment LED 

LOS / LOF red The four links. 

alarm indication signal / 

CRC4 error LED 

AIS / ERR 

red 

transmit LED TXD yellow The DCE interface. 

receive LED RXD green 

User manual 27



2.6.2 Power LED 

This LED indicates that the Crocus Inverse Multiplexer is connected to the power supply and is switched 

on. 

2.6.3 LAN interface LEDs 

The LAN interface LEDs reflect the actual status of the Crocus Inverse Multiplexer its LAN interface. 

There are four LAN interface LEDs: 

LAN interface LED 

LNK 

COL 

TXD 

RXD 

Description 

This LED indicates there is a good link integrity on the TPI port. 

This LED indicates there are collisions on the LAN. 

This LED indicates the LAN transmits data. 

This LED indicates the LAN receives data. 

2.6.4 Test LED 

This LED indicates whether the Crocus Inverse Multiplexer is in normal operation or in test condition. 

Three different status modes can be distinguished: 

LED status 

Description 

off 

continuously on 

blinking 

No test is active. 

A DCE interface test is active. 

A link test is active. 

28 User manual



2.6.5 Link LEDs 

The link LEDs reflect the actual status of the Crocus Inverse Multiplexer its links. For each link, there are 

two link LEDs: 

• LOS / LOF 

• AIS / ERR 

LOS / LOF LED 

For the LOS / LOF LED, three different status modes can be distinguished: 

off 

LED status 


Description 

No Loss Of Signal (LOS) or Loss Of Frame alignment (LOF) is detected or the link 

has been disabled. 

This indicates a Loss Of Signal (LOS). 

This means the particular link no longer receives data. 

blinking 

This indicates a Loss of Frame Alignment (LFA). 

This means that the particular link received three consecutive erroneous … 

• Frame Alignment Words (FAW) 

or 

• Frame Counts (FC) 

In the G.704 link framing … 

• a Frame Alignment Word is used to synchronise the sequence of frames in the 

data stream of a specific link 

• Frame Count is used to measure the relative delay variance between the 

individual channels of the Nx2.048 Mbps stream. 

AIS / ERR LED 

For the AIS / ERR LED, three different status modes can be distinguished: 

off 

LED status 


Description 

No Alarm Indication Signal (AIS) or BER error (ERR) is detected or the link has 

been disabled. 

This indicates an Alarm Indication Signal (AIS) is detected on the particular link. 

An AIS means that all data bits are set to 1. 

blinking 

This indicates that the BER errors which are received on the particular link, exceed 

the configured onThreshold in the errorAlarmThreshold. 

User manual 29



2.6.6 DCE interface LEDs 

The DCE interface LEDs reflect the actual status of the Crocus Inverse Multiplexer its DCE interface. 

There are two DCE interface LEDs: 

DCE interface LED 

TXD 

Description 

This LED monitors the data sent by the application (Data Terminal 

Equipment) to the DCE interface module of the Crocus Inverse Multiplexer. 

Note that the data is monitored after it went through the DCE interface 

circuitry. 

RXD 

This LED monitors the data sent to the application (Data Terminal 

Equipment) by the DCE interface module of the Crocus Inverse Multiplexer. 

Note that the data is monitored before it went through the DCE interface 

circuitry. 

30 User manual


DIP switches of the Crocus Inverse Multiplexer 

3. DIP switches of the Crocus Inverse Multiplexer 

This chapter locates the DIP switches on the Crocus Inverse Multiplexer motherboard. It also gives an 

overview of their function and it explains how to change their settings. 



3.1 Location of the DIP switches 32 

3.2 Overview of the DIP switches 33 

3.3 Changing the DIP switch settings 34 

User manual 31



3.1 Location of the DIP switches 

The figure below shows the position of the DIP switches on the Crocus Inverse Multiplexer motherboard. 

DS1 

1 4 

32 User manual



3.2 Overview of the DIP switches 

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

DIP switch name DS1 no. Setting Function 

- 1 - Reserved. 

- 2 - Reserved. 

start-up mode 3 on Start up from flash memory. 

off 

Start up in boot mode. 

load default 4 on Normal operation. 

configuration off Load default configuration. 

User manual 33



3.3 Changing the DIP switch settings 

To change the DIP switch settings of the Crocus Inverse Multiplexer, proceed as follows: 

Step 

Action 

1 Switch the Crocus Inverse Multiplexer off. 

2 Disconnect the Crocus Inverse Multiplexer from the mains. 

3 Unscrew the following screw on the Crocus Inverse Multiplexer … 

• the four top screws 

• the four upper front panel screws 

• the four upper back panel screws 

This is shown in the following picture: 

4 Lift the cover from the Crocus Inverse Multiplexer. 

5 Change the DIP switch settings. 

6 Replace the cover and close tight. 

7 Fasten the screws you loosened in step 3. 

8 Reconnect the Crocus Inverse Multiplexer to the mains. 

9 Switch the Crocus Inverse Multiplexer on. 

34 User manual


Maintenance of the Crocus Inverse Multiplexer 

4. Maintenance of the Crocus Inverse Multiplexer 

Once you installed the Crocus Inverse Multiplexer, you can proceed with the configuration of the Crocus 

Inverse Multiplexer. You can do this using … 

• the Telindus Maintenance Application (TMA) 

• ATWIN over a terminal emulation or a Telnet session 

• Command Line Interface (CLI) over a terminal emulation or a Telnet session. 

This chapter introduces TMA and it describes how to start a session on the Crocus Inverse Multiplexer. 

Furthermore, this chapter gives an introduction to the attributes of the Crocus Inverse Multiplexer. 

To find out more about ATWIN and CLI, refer to the ATWIN and CLI manual. 



4.1 Introduction to TMA 36 

4.2 Connecting to a Crocus Inverse Multiplexer with TMA 37 

4.3 Introduction to the attributes of the Crocus Inverse Multiplexer 41 

User manual 35



4.1 Introduction to TMA 

TMA is a free Windows ® software package that enables you to maintain the Crocus Inverse Multiplexer, 

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 Inverse Multiplexer. The most recent model files and TMA engine can always be downloaded 

from the Telindus web site. Go to http://www.telindus.com/accessproducts and select Products ! 

Maintenance & Management ! TMA Maintenance ! Download TMA software. 

36 User manual



4.2 Connecting to a Crocus Inverse Multiplexer with TMA 

This section explains how you can connect to the Crocus Inverse Multiplexer using TMA. 

There are two ways to establish a connection with TMA to the Crocus Inverse Multiplexer: 

• over a serial connection, through the auxiliary connector 

• over an IP connection, through the LAN connector. 

Connecting through the auxiliary connector 

To established a link between TMA and the Crocus Inverse Multiplexer through the auxiliary connector, 

proceed as follows: 

Step 

Action 

1 Connect the COM port of your 

computer through a straight DB9 

male-female cable with the 

auxiliary connector of the Crocus 

Inverse Multiplexer 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 

Inverse Multiplexer is connected to. 

• If a password has previously been configured in the Crocus Inverse Multiplexer then 

also fill in the password field. 

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

User manual 37



Step 

Action 



Select device… 

• or press the shortcut key: Ctrl+D 

• or press on the Select device button: 

The Connect (select a device) window is being 


7 Two situations can be distinguished depending on establishing a connection to the local 

or remote Crocus Inverse Multiplexer: 

• In order to connect to the local Crocus Inverse Multiplexer TT, choose On device. 

• In order to connect to the remote Crocus Inverse Multiplexer, choose After device 

and enter relative NMS address 1 or higher. 

You can connect to a remote Crocus Inverse Multiplexer only if the data link is up. 

If a password has previously been configured in the Crocus Inverse Multiplexer then 


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

9 After a couple of seconds, the attributes of the selected Crocus Inverse Multiplexer 

appear in the TMA window. 

38 User manual



Connecting over an IP network 

To established a link between TMA and the Crocus Inverse Multiplexer over an IP network, proceed as 

follows: 

Step 

Action 

1 Connect the IP network to … 

• the network port of your PC 

• the LAN connector of the 

Crocus Inverse Multiplexer. 

IP 

2 Start TMA. 



Device… 

• or press the shortcut key: Ctrl+N 

• or press on the Connect to device 

button: 

The Connect (to a device) window is being 


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

• Select the option IP address, and enter the IP address of the Crocus Inverse 


• If a password has previously been configured in the Crocus Inverse Multiplexer then 


Before you are able to establish a connection over an IP network, you have to configure 

an IP address and a default gateway in the Crocus Inverse Multiplexer. 

You can do this by first connecting TMA to the Crocus Inverse Multiplexer through the 

auxiliary connector, and then configuring an IP address and a default gateway (refer to 

Section 5.7 - Basic LAN interface configuration). 

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

User manual 39



Step 

Action 



Select device… 

• or press the shortcut key: Ctrl+D 

• or press on the Select device button: 

The Connect (select a device) window is being 


7 Two situations can be distinguished depending on establishing a connection to the local 

or remote Crocus Inverse Multiplexer: 

• In order to connect to the local Crocus Inverse Multiplexer TT, choose On device. 

• In order to connect to the remote Crocus Inverse Multiplexer, choose After device 

and enter relative NMS address 1 or higher. 

You can connect to a remote Crocus Inverse Multiplexer only if the data link is up. 

If a password has previously been configured in the Crocus Inverse Multiplexer then 


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

9 After a couple of seconds, the attributes of the selected Crocus Inverse Multiplexer 

appear in the TMA window. 

40 User manual



4.3 Introduction to the attributes of the Crocus Inverse Multiplexer 

This section gives an introduction to the attributes of the Crocus Inverse Multiplexer. It introduces terms 

such as containment tree, group, object, attribute, value and action. 

Containment tree terminology 

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

Groups 

Containment tree 

Attributes 

Attribute values 

Objects 

Actions 

Structured values 

User manual 41



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

Term 

containment 

tree 

Description 

The containment tree represents the hierarchical structure of the Crocus Inverse 

Multiplexer. It 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 crocusInvMux contains the sub-object lanInterface. This object contains 

all the attributes concerning the LAN interface. E.g. the configuration attribute 

ipAddress. 

attribute 

An attribute is a parameter related to a certain object. It has a certain value. 

Example: 

The object lanInterface contains the status attribute ifOperStatus, which has as possible 

values up and down. 

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 fallback can be set to the value enabled or disabled. 

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, or 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 Activate Configuration action only appears when the object crocusInvMux is selected 

in combination with the group Configuration. 

42 User manual



The Crocus Inverse Multiplexer containment tree 

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

Object 

crocusInvMux 

lanInterface 

 

This object contains … 

the general system attributes. It is the top object in the containment tree. 

E.g. the configuration attributes sysName, sysContact and sysLocation. 

the attributes concerning the LAN interface. 

E.g. the configuration attributes ipAddress, ipNetMask and defaultRoute. 

the DCE interface attributes. 

E.g. the configuration attribute clocking. 

The name of this attribute depends on the type of DCE interface. 

E.g. v35 in case of a V35 interface, rs530 in case of a RS530 interface, etc. 

link[ ] 

snmpProxy 

management 

operatingSystem 

the attributes related to the link. 

E.g. the status attribute errorCount. 

the attributes concerning SNMP traps. 

E.g. the configuration attribute trapDestinations. 

the attributes concerned with the management of the Crocus Inverse 


E.g. the configuration attribute cms2Address. 

the operating system attributes. 

E.g. the performance attribute freeDataBuffers. 

Where can you find an overview of all the attributes 

The reference part of this manual explains all the attributes of the Crocus Inverse Multiplexer. One 

chapter describes one group of attributes: 

• chapter 6 describes the configuration attributes 

• chapter 7 describes the status attributes 

• chapter 8 describes the performance attributes 

• chapter 9 describes the alarm attributes. 

Within a chapter, the objects and their underlying attributes are discussed in a sequential manner. I.e. 

from top to bottom, as they appear in the attribute window. 

User manual 43

Step-by-step configuration 


5. Step-by-step configuration 

This chapter describes in a step-by-step method how to perform a basic configuration on Crocus Inverse 

Multiplexer. 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 Inverse Multiplexer will be completely configured and ready 

for use when you reach the end of this chapter. 



5.1 Reading the configuration settings 45 

5.2 Loading the default configuration 47 

5.3 Clocking 48 

5.4 Link and station clock impedance selection 55 

5.5 Fall-back operation 56 

5.6 Link activation 57 

5.7 Basic LAN interface configuration 57 

5.8 Basic DCE interface configuration 58 

5.9 Configuring the management attributes 60 

5.10 Activating the configuration 66 

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

44 User manual



5.1 Reading the configuration settings 

As this chapter explains the basic configuration of the Crocus Inverse Multiplexer, 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. 

DIP switch configuration table 

A DIP switch configuration table has the following layout: 

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 • 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: DIP switch bank number 1, switch position number 3 

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. 

User manual 45



TMA attribute string 

A TMA attribute string has the following layout: 

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 crocusInvMux/link[ ]/physicalInterface means the following: 

• the attribute name is physicalInterface 

• this attribute is located in the sub object link[ ] 

• this sub object is located in the top object crocusInvMux. 

3 the default value of a configuration attribute. 

46 User manual



5.2 Loading the default configuration 

If you install the Crocus Inverse Multiplexer for the first time, all configuration attributes are set to their 

default value. If the Crocus Inverse Multiplexer 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. 

You can do this by means of … 

• the load default configuration DIP switch 

• the Load Default Configuration action in TMA. 

The location of the load default configuration DIP switch is: 


load default 4 on Normal operation. 

configuration off Load default configuration. 

To locate this DIP switch bank and for the DIP switch setting procedure, refer to Chapter 3 - DIP switches 

of the Crocus Inverse Multiplexer. 

The location of the Load Default Configuration action in the Crocus Inverse Multiplexer containment tree is: 

crocusInvMux/Load Default Configuration 

To load the default configuration, proceed as follows: 

Step 

Action 

1 In the TMA window, select the top object crocusInvMux 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. 


User manual 47



5.3 Clocking 

This section describes the clocking principles of the Crocus Inverse Multiplexer. 



5.3.1 System clock 49 

5.3.2 E1 link clocking principles 50 

5.3.3 DCE clocking principles 52 

5.3.4 End-to-end clocking principles 53 

48 User manual



5.3.1 System clock 

The system clock is used to generate timings for: 

• the transmit clock of the DCE interface 

• the transmit clock of the E1 links. 

The system clock can be derived from: 

• the receive clock of one of the four E1 links 

• the external applied station clock 

• the internal clock generating circuit of the Crocus Inverse Multiplexer. 

crocusInvMux/clockSelection 

default: rxClockLink1 

Use the clockSelection attribute to select a system clock. The clockSelection attribute has the following values: 

Value 

The system clock is derived from … 

rxClockLink1 the receive clock on E1 link number 1. 




stationClock 

internal 

the external applied station clock. 

the internal clock circuit of the Crocus Inverse Multiplexer. 

crocusInvMux/alternateClockSelection 

default: autoRxClockLink 

Should the clock you selected with the clockSelection attribute fail, then the Crocus Inverse Multiplexer 

takes the clock as set with the alternateClockSelection attribute. 

The alternateClockSelection attribute has the following values: 

Value 

autoRxClockLink 

internal 

Description 

If the earlier selected clock fails, then the four link receive clocks are scanned 

starting with link 1 up to link 4. The first valid clock which is encountered becomes 

the new system clock. If no valid link receive clock is detected, then the inverse 

multiplexing is stopped in the receive direction. 

If the earlier selected clock fails, then the internal clock becomes the new system 

clock. 

User manual 49



5.3.2 E1 link clocking principles 

The transmit clock of all the E1 links is based on the system clock. The receive clock of an E1 link, on the 

other hand, is always derived from the incoming E1 data. 

Link receive clocking 

If you set the clockSelection attribute to rxClockLink, the transmit clock of the E1 links is derived from the 

receive clock of one of the E1 links. The following figure clarifies this: 

System Clock 

Tx Clk 1 

Rx Clk 1 

E1 

Tx Clk 2 

Tx Clk 

Tx Clk 

Rx Clk 2 

E1 

Rx Clk 

DCE interface 

Rx Clk 

Tx Clk 3 

Rx Clk 3 

E1 

Tx Clk 4 

Rx Clk 4 

E1 

Station clocking 

If you set the clockSelection attribute to stationClock, the transmit clock of the E1 links is derived from the 

external applied station clock. The following figure clarifies this: 

System Clock 

Tx Clk 1 

Rx Clk 1 

E1 

Tx Clk 

Tx Clk 

Tx Clk 2 

Rx Clk 2 

E1 

Rx Clk 

DCE interface 

Rx Clk 

Tx Clk 3 

Rx Clk 3 

E1 

Tx Clk 4 

Rx Clk 4 

E1 

Station 

Clock 

50 User manual



Internal clocking 

If you set the clockSelection attribute to internal, the transmit clock of the E1 links is derived from the internal 

clock circuit of the Crocus Inverse Multiplexer. The following figure clarifies this: 

Internal 

Clock 

Generator 

System Clock 

Tx Clk 1 

Rx Clk 1 

E1 

Tx Clk 2 

Tx Clk 

Tx Clk 

Rx Clk 2 

E1 

Rx Clk 

DCE interface 

Rx Clk 

Tx Clk 3 

Rx Clk 3 

E1 

Tx Clk 4 

Rx Clk 4 

E1 

User manual 51



5.3.3 DCE clocking principles 

The receive clock of the modular DCE interface is always generated by the Crocus Inverse Multiplexer 

(DCE). However, the Crocus Inverse Multiplexer generates this clock based on the receive clock of one 

of the E1 links. This means that … 

• if receive link clocking is selected as system clock, the modular DCE interface receive clock is derived 

from the selected E1 link. 

• although internal or station clocking is selected as system clock, the modular DCE interface receive 

clock is derived from the first available receive clock of an enabled E1 link. 

The transmit clock of the modular DCE interface can … 

• either come from the Crocus Inverse Multiplexer (DCE) 

• or from the user application (DTE). 

crocusInvMux/< dceInterface >/dTESignalTiming 

default: disabled 

Use this attribute to select between DTE or DCE timing. 

This attribute only applies to the DCE interfaces RS530, V35, V36 and X21. 

DCE timing 

If you set the dTESignalTiming attribute to disabled, the Crocus Inverse Multiplexer generates both transmit 

and receive clock towards the modular DCE interface. The following figure clarifies this: 

Internal 

Clock 

Generator 

System Clock 

Tx Clk 1 

Rx Clk 1 

Tx Clk 2 

E1 

Tx Clk 

Tx Clk 

Rx Clk 2 

E1 

Rx Clk 

DCE interface 

Rx Clk 

Tx Clk 3 

Rx Clk 3 

E1 

Tx Clk 4 

Rx Clk 4 

E1 

DTE timing 

If you set the dTESignalTiming attribute to enabled, the DTE uses the transmit clock it receives from the 

Crocus Inverse Multiplexer to generate an external clock. The DTE then uses this external clock to send 

its transmit data. The DTE also applies this external clock to the external clock pin of the modular DCE 

interface. The modular DCE interface then clocks in the transmit data with this external clock. The 

following figure clarifies this: 

Internal 

Clock 

Generator 

System Clock 

Tx Clk 1 

Rx Clk 1 

Tx Clk 2 

E1 

Tx Clk 

Tx Clk 

Rx Clk 2 

E1 

Rx Clk 

Ext Clk 

DCE interface 

Rx Clk 

Tx Clk 3 

Rx Clk 3 

E1 

Tx Clk 4 

Rx Clk 4 

E1 

52 User manual



5.3.4 End-to-end clocking principles 

Transmit and receive paths can be clocked independently from each other. The following figures show 

some clocking examples. 

Internal – internal clocking 

Internal 

Clock 

Generator 

Internal 

Clock 

Generator 

System Clock 

Tx Clk 1 

Tx Clk 1 

System Clock 

Rx Clk 1 

E1 

E1 

Rx Clk 1 

Tx Clk 2 

Tx Clk 2 

Tx Clk 

Rx Clk 2 

E1 

E1 

Rx Clk 2 

Tx Clk 

Rx Clk 

DCE interface 

Tx Clk 3 

Rx Clk 3 

E1 

E1 

Tx Clk 3 

Rx Clk 3 

DCE interface 

Rx Clk 

Tx Clk 4 

Tx Clk 4 

Rx Clk 4 

E1 

E1 

Rx Clk 4 

Internal – link receive clocking 

Internal 

Clock 

Generator 

System Clock 

Tx Clk 1 

Tx Clk 1 

System Clock 

Rx Clk 1 

E1 

E1 

Rx Clk 1 

Tx Clk 2 

Tx Clk 2 

Tx Clk 

Rx Clk 2 

E1 

E1 

Rx Clk 2 

Tx Clk 

Rx Clk 

DCE interface 

Tx Clk 3 

Rx Clk 3 

E1 

E1 

Tx Clk 3 

Rx Clk 3 

DCE interface 

Rx Clk 

Tx Clk 4 

Rx Clk 4 

E1 

E1 

Tx Clk 4 

Rx Clk 4 

External – internal clocking 

Internal 

Clock 

Generator 

System Clock 

Tx Clk 1 

Rx Clk 1 

E1 

E1 

Tx Clk 1 

Rx Clk 1 

System Clock 

Tx Clk 2 

Tx Clk 2 

Tx Clk 

Rx Clk 2 

E1 

E1 

Rx Clk 2 

Tx Clk 

Rx Clk 

DCE interface 

Tx Clk 3 

Rx Clk 3 

E1 

E1 

Tx Clk 3 

Rx Clk 3 

DCE interface 

Rx Clk 

Tx Clk 4 

Tx Clk 4 

Rx Clk 4 

E1 

E1 

Rx Clk 4 

Station 

Clock 

User manual 53



External – link receive clocking 

System Clock 

Tx Clk 1 

Rx Clk 1 

E1 

E1 

Tx Clk 1 

Rx Clk 1 

System Clock 

Tx Clk 

Rx Clk 

DCE interface 

Tx Clk 2 

Rx Clk 2 

Tx Clk 3 

Rx Clk 3 

E1 

E1 

E1 

E1 

Tx Clk 2 

Rx Clk 2 

Tx Clk 3 

Rx Clk 3 

DCE interface 

Tx Clk 

Rx Clk 

Tx Clk 4 

Rx Clk 4 

E1 

E1 

Tx Clk 4 

Rx Clk 4 

Station 

Clock 

External – external clocking 

System Clock 

Tx Clk 1 

Rx Clk 1 

E1 

E1 

Tx Clk 1 

Rx Clk 1 

System Clock 

Tx Clk 

Rx Clk 

DCE interface 

Tx Clk 2 

Rx Clk 2 

Tx Clk 3 

Rx Clk 3 

E1 

E1 

E1 

E1 

Tx Clk 2 

Rx Clk 2 

Tx Clk 3 

Rx Clk 3 

DCE interface 

Tx Clk 

Rx Clk 

Tx Clk 4 

Rx Clk 4 

E1 

E1 

Tx Clk 4 

Rx Clk 4 

Station 

Clock 

Station 

Clock 

54 User manual



5.4 Link and station clock impedance selection 

For both the link and station clock connections, two types of connectors are provided: 

• 75 ohm coaxial BNC 

• 120 ohm RJ45. 

Connect the links or station clock either to the BNC connector or the RJ45 connector. Using one of these 

two connector types also involves configuring the correct termination resistance. 

crocusInvMux/stationClockPhysicalInterface 

default: 75 Ohm 

The stationClockPhysicalInterface attribute allows you to make a double selection: 

• the selection between one of the two station clock connectors on the one hand 

• the selection between the correct impedance on the other hand. 

These two selections are inevitably linked with each other. 

The stationClockPhysicalInterface attribute has the following values: 

Value 

Description 

75 Ohm This selects the coaxial BNC connector as station clock connector, with an 

impedance of 75 ohm. 

120 Ohm This selects the twisted pair RJ45 connector as station clock connector, with an 


crocusInvMux/link[ ]/physicalInterface 


The physicalInterface attribute allows you to make a double selection: 

• the selection between one of the two link connectors on the one hand 



The physicalInterface attribute has the following values: 

Value 

Description 

75 Ohm This selects the coaxial BNC connectors as link connector, with an impedance of 75 

ohm. 

120 Ohm This selects the twisted pair RJ45 connector as link connector, with an impedance 

of 120 ohm. 

User manual 55



5.5 Fall-back operation 

crocusInvMux/fallback 

default: enabled 

Use the fallback attribute to enable or disable the fall-back mechanism. 


available speed and continues data transmission at this fall-back rate. If the E1 recovers, then the Crocus 

Inverse Multiplexer automatically returns to the original rate selected by the user. 


data rate. 

Normal operation, i.e. over all 4 E1 links, is at a DCE interface speed of 7808 kbps. The fall-back speeds 

on the DCE interface are: 

• 5856 kbps ! fall back to 3 E1 links 


• 1952 kbps ! fall back to 1 E1 link. 

crocusInvMux/minimumLinks default: 1 

This attribute sets the minimum number of E1 links to be used in the bonding process. This parameter is 

important for the fall-back mechanism. 

crocusInvMux/maximumLinks default: 4 

This attribute sets the maximum number of E1 links to be used in the bonding process. This parameter is 

important for the step-up mechanism. 

56 User manual



5.6 Link activation 

crocusInvMux/link[ ]/ifAdminStatus 

default: up 

The ifAdminStatus attribute determines the link activation. By setting this attribute to down: 

• you can disable unused links on the Crocus Inverse Multiplexer 

• alarms are reset on the corresponding link. 

5.7 Basic LAN interface configuration 

crocusInvMux/lanInterface/ipAddress default: 0.0.0.0 

This attribute defines the IP address for the LAN interface. The address should belong to the subnet the 

interface is connected to. 

crocusInvMux/lanInterface/ipNetMask default: 255.255.255.0 

This attribute defines the IP subnet mask for the LAN interface. This parameter defines the number of IP 

devices that may be present on the corresponding IP segment. 

crocusInvMux/lanInterface/defaultRoute 

default: empty 

The defaultRoute attribute is the IP address of the first router on the path to the destination network. 

User manual 57



5.8 Basic DCE interface configuration 

crocusInvMux//rTSControl 

default: external 

This attribute only applies to the DCE interfaces RS530, V35 and V36. 

Use the rTScontrol attribute to define which device will activate the RTS signal. Following settings are 

possible: 

If RTS control 

is set to … 

the RTS signal is activated 

by … 

This attribute setting is used when … 

external the application. the application has to be in command of the RTS 

signal. 

internal 

the Crocus Inverse 


the application is not able to activate the RTS 

signal. 

Normal operation requires the RTS signal (circuit 105) to be active before the Crocus Inverse Multiplexer 

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 Inverse Multiplexer. 

crocusInvMux/< dceInterface >/cTSDelay 

default: 0 ms 

This attribute only applies on the DCE interfaces RS530, V35 and V36. 

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. 

Following delays can be selected: 

• 0 ms 

• 4 ms 

• 16 ms 

• 64 ms 

If RTS control is set to … 

external 

then … 

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. 

58 User manual



crocusInvMux/< dceInterface >/dTESignalTiming 


This attribute only applies to the DCE interfaces RS530, V35, V36 and X21. 


If the dTESignalTiming 

is set to … 

then … 

I.e. the transmit clock of the modular DCE 

interface is generated by the … 

disabled DCE timing is selected. Crocus Inverse Multiplexer (DCE). 

enabled DTE timing is selected. user application (DTE). 

For more information on DTE and DCE timing, Section 5.3.3 - DCE clocking principles. 

User manual 59



5.9 Configuring the management attributes 

This section explains the management attributes of the Crocus Inverse Multiplexer. These attributes allow 

you to make all the devices in your network accessible for management from one central location. 

First this section gives you some rules of thumb and remarks concerning the management of the Crocus 

Inverse Multiplexer in a network. Then it explains the attributes that have an impact on the management 

of the Crocus Inverse Multiplexer. 

The following table gives an overview of this section: 


5.9.1 Rules of thumb and remarks concerning management 61 

5.9.2 Using relative or absolute addressing 62 

5.9.3 Selecting the purpose of the control connector 63 

5.9.4 Forwarding management data to the links 64 

5.9.5 Addressing the Crocus Router Interface 10M 65 

60 User manual



5.9.1 Rules of thumb and remarks concerning management 

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

• Make sure there is only one path towards the management system. Else you might get unexpected 

results (e.g. devices that do not answer to polling, answer of several devices at once when polling one 

device, etc.). 

• Once your network starts to become complex on management level (i.e. more than just in-line 

connections as depicted in Relative addressing on page 62), you are advised to use absolute 

addressing instead of relative addressing (refer to Absolute addressing on page 62). 

In practice, it is best to use absolute addressing when you configure consoleSelection attribute to nms. 

• If you use a Crocus Router Interface 10M in the Crocus Inverse Multiplexer and you want to manage it 

through the control connector or the LAN of the Crocus Inverse Multiplexer, then you are advised to 

set the consoleSelection attribute to nms. Else you might not be able to manage the router interface. Refer 

to Section 5.9.3 - Selecting the purpose of the control connector for more information. 

• If you use a Crocus Router Interface 10M in the Crocus Inverse Multiplexer, then absolute addressing 

must be used in the Crocus Router Interface 10M as well as in the Crocus Inverse Multiplexer, to gain 

access to the Crocus Router Interface 10M. Moreover, you not only have to configure the absolute 

address in the Crocus Router Interface 10M itself, but also in the router object of the Crocus Inverse 

Multiplexer its containment tree. Refer to Section 5.9.5 Addressing the Crocus Router Interface 10M 

for more information. 

User manual 61



5.9.2 Using relative or absolute addressing 

In order to connect with TMA to the Crocus Inverse Multiplexer (refer to Section 4.2 - Connecting to a 

Crocus Inverse Multiplexer with TMA), you can use two addressing schemes: 

Address type 

relative 

Description 

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 

connections ∗ between two devices. 

To enable relative addressing, no address has to be specified in the device. In other 

words, you can leave the cms2Address attribute at its default value, being 0. 

Relative addressing 

∗ An extended management connection is realised with a crossed cable between 

the control connectors of the two Telindus devices. You also have to set the 

consoleSelection attribute to the value nms. 

absolute 

This type of addressing is meant for a network topology where the devices are not 

connected in-line on management level. I.e. when there is a digital multipoint device 

present (e.g. the Orchid DM). 

To enable absolute addressing, an address has to be specified in the device. Do 

this using the cms2Address attribute. The absolute addressing range goes from 1 up 

to 65535. Refer to Section 6.7 - Management configuration attributes. 

Absolute addressing 

62 User manual



5.9.3 Selecting the purpose of the control connector 

crocusInvMux/management/consoleSelection 

default: console 

Use the consoleSelection attribute to define which kind of application runs over the auxiliary connection. 

Value 

Description 

nms 

Select this value if you want to connect the control connector of the Crocus 

Inverse Multiplexer to … 

• a management concentrator (e.g. the Orchid 1003 LAN or Telindus 1035 

Orchid) for management purposes. 

• the control connector of another Telindus device using a crossed cable (i.e. 

back-to-back) in order to create an extended management link. For more 

information on extended management links, refer to Section 5.9.2 - Using 

relative or absolute addressing. 

When connecting the control connector of the Crocus Inverse Multiplexer to a 

COM port of your computer, you can still open a TMA session on the Crocus 

Inverse Multiplexer. However, you can not open a CLI or ATWIN session. 

console 

Select this value if you want to connect the control connector of the Crocus 

Inverse Multiplexer to a COM port of your computer in order to manage the 

Crocus Inverse Multiplexer locally using TMA, CLI or ATWIN. 

User manual 63



5.9.4 Forwarding management data to the links 

crocusInvMux/forwardTMAToLinks 


Disables or enables propagation of TMA management information to the link. If forwardTMAToLinks is 

enabled, management information is sent over the link via a dedicated management channel towards the 

remote Crocus Inverse Multiplexer. 

forwardTMAToLinks 

Site A 

link connection 

Site B 


64 User manual



5.9.5 Addressing the Crocus Router Interface 10M 

crocusInvMux/router/cms2Address default: 0 

Use this attribute to define an absolute address in the Crocus Router Interface 10M. Refer to Section 

5.9.2 - Using relative or absolute addressing for more information on absolute addressing. 

It is necessary that the absolute address in the router object of the Crocus Inverse Multiplexer and in the 

management object of the Crocus Router Interface 10M itself, are identical. Refer to the following examples. 

Window 1 shows the router object of the Crocus Inverse Multiplexer, window 2 shows the management 

object of the Crocus Router Interface 10M itself. 

Crocus Inverse Multiplexer : 

Crocus Router Interface 10M : 

User manual 65



5.10 Activating the configuration 

Once the basic configuration of the Crocus Inverse Multiplexer is made, it has to be activated. To activate 

the new configuration, press in TMA on the Send all attributes to device button: 

Now set the basic configuration attributes of the remote Crocus Inverse Multiplexer and activate this 

configuration. 

When both Crocus Inverse Multiplexers are set, try sending data to check whether the data link is 

established. If any problems occur, the status, performance and alarm attributes of the Crocus Inverse 

Multiplexer can be checked. Refer to the reference manual for more information on these attributes. 

66 User manual


Reference manual 

Reference manual 67


68 Reference manual


Configuration attributes 

6. Configuration attributes 

This chapter discusses the configuration attributes of the Crocus Inverse Multiplexer. The following table 

gives an overview of this chapter. 


6.1 Configuration attribute overview 70 

6.2 Crocus Inverse Multiplexer configuration attributes 71 

6.3 LAN interface configuration attributes 81 

6.4 DCE interface configuration attributes 82 

6.5 Link configuration attributes 88 

6.6 SNMP proxy configuration attributes 90 

6.7 Management configuration attributes 91 

Reference manual 69



6.1 Configuration attribute overview 

> crocusInvMux 

sysName 

sysContact 

sysLocation 

clockSelection 

alternateClockSelection 

stationClockPhysicalInterface 

fallback 

fallbackBER 

minimumLinks 

maximumLinks 

maximumDelayDifference 

synchronisationPeriod 

linkDeactivationPeriod 

linkReactivationPeriod 

security 

testDuration 

remoteDTELoopbackDetect 


bootFromFlash 

errorAlarmThreshold 

alarmMask 

alarmLevels 

Action: Activate Configuration 

Action: Load Saved Configuration 

Action: Load Default Configuration 

Action: Cold Boot 

Action: Resynchronise 

>> 

>> rs530, v35, v36 

rTSControl 

cTSDelay 

dTESignalTiming 

tests 

alarmMask 

alarmLevels 

>> x21 

dTESignalTiming 

alarmMask 

alarmLevels 

>> router 

cms2Address 

alarmMask 

alarmLevels 

>> link[1], link[2], link[3], link[4] 

ifAdminStatus 

physicalInterface 

cRC4Generation 

errorAlarmThreshold 

alarmMask 

alarmLevels 

>> lanInterface 

ipAddress 

ipNetMask 

alarmMask 

alarmLevels 

arpTimeout 

defaultRoute 

>> snmpProxy 

trapDestinations 

mib2Traps 

>> management 

cms2Address 

accessList 

snmp 

telnet 

tftp 

consoleNoTrafficTimeout 

alarmFilter 

consoleSelection 

70 Reference manual



6.2 Crocus Inverse Multiplexer configuration attributes 

crocusInvMux/sysName 


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

characters. 

This is a SNMP MIB2 parameter. 

crocusInvMux/sysContact 


This is a field where you can fill in the name of a contact person together with information on how to 

contact this person. The field has a limit of 64 characters. 


crocusInvMux/sysLocation 


This is a field where you can fill in the physical location of the Crocus Inverse Multiplexer. The field has a 

limit of 64 characters. 


crocusInvMux/clockSelection 

default: rxClockLink1 

Use the clockSelection attribute to select a system clock. The system clock is used to generate timings for 

the DCE interface and the transmit information on the E1 links. 

The clockSelection attribute has the following values: 

Value 

The system clock is derived from … 





stationClock 

internal 

the external applied station clock. 

the internal clock circuit of the Crocus Inverse Multiplexer. 

For more information on clocking, refer to Section 5.3 - Clocking. 

Reference manual 71



crocusInvMux/alternateClockSelection 

default: autoRxClockLink 

Should the clock you selected with the clockSelection attribute fail, then the Crocus Inverse Multiplexer 

takes the clock as set with the alternateClockSelection attribute. 

The alternateClockSelection attribute has the following values: 

Value 

autoRxClockLink 

internal 

Description 

If the earlier selected clock fails, then the four link receive clocks are scanned 

starting with link 1 up to link 4. The first valid clock which is encountered becomes 

the new system clock. If no valid link receive clock is detected, then the inverse 

multiplexing is stopped in the receive direction. 

If the earlier selected clock fails, then the internal clock becomes the new system 

clock. 

crocusInvMux/stationClockPhysicalInterface 


The stationClockPhysicalInterface attribute allows you to make a double selection: 

• the selection between one of the two station clock connectors on the one hand 



The stationClockPhysicalInterface attribute has the following values: 

Value 

Description 

75 Ohm This selects the coaxial BNC connector as station clock connector, with an 


120 Ohm This selects the twisted pair RJ45 connector as station clock connector, with an 


crocusInvMux/fallback 


Use the fallback attribute to enable or disable the fall-back mechanism. 


available speed and continues data transmission at this fall-back rate. If the E1 recovers, then the Crocus 

Inverse Multiplexer automatically returns to the original rate selected by the user. 


data rate. 

Normal operation, i.e. over all 4 E1 links, is at a DCE interface speed of 7808 kbps. The fall-back speeds 

on the DCE interface are: 



• 1952 kbps ! fall back to 1 E1 link. 

72 Reference manual



crocusInvMux/fallbackBER 

Use the fallbackBER attribute to determine when Crocus Inverse Multiplexer should fall-back or step-up. 

Fall-back is based on a permanent line quality monitoring of each E1 line. The line quality is determined 

by the CRC4 error rate, Loss Of Frame alignment (LOF) and Alarm Indication Signal (AIS) errors. Using 

the fallbackBER attribute, a CRC4 error rate threshold can be configured which determines when the 

Crocus Inverse Multiplexer should fall-back or step-up. 

The fallbackBER attribute contains a table with the following three attributes: 

Attribute Description Range Default 

averagingPeriod 

(minutes) 

fallbackThreshold 

stepupThreshold 

Period, in minutes, over which the average BER value is 

calculated. 

If within the averagingPeriod the average BER value equals 

or exceeds the value entered in the fallbackThreshold 

attribute, then the Crocus Inverse Multiplexer will fall 

back. 

If the Crocus Inverse Multiplexer operates in fall back, 

and if within the averagingPeriod the average BER value 

equals or exceeds the value entered in the 

stepupThreshold attribute, then the Crocus Inverse 

Multiplexer will step up. 

1 … 60 2 

10 -3 … 10 -8 10 -5 

10 -3 … 10 -8 10 -7 

The Crocus Inverse Multiplexer will only fall back if the fallback attribute is set to enabled. 

crocusInvMux/minimumLinks default: 1 

This attribute sets the minimum number of E1 links to be used in the bonding process. This parameter is 

important for the fall-back mechanism. 

crocusInvMux/maximumLinks default: 4 

This attribute sets the maximum number of E1 links to be used in the bonding process. This parameter is 

important for the step-up mechanism. 

crocusInvMux/maximumDelayDifference default: 63 

Use this attribute to set the maximum allowed delay difference between the links. 

crocusInvMux/synchronisationPeriod default: 10 

Use this attribute to define how long the Crocus Inverse Multiplexer should try to synchronise on a link 

before disabling the link. 

crocusInvMux/linkDeactivationPeriod default: 10 

Use this attribute to define after how much time a link is deactivated, in case of loss of signal, loss of 

framing and AIS signals. 

crocusInvMux/linkReactivationPeriod default: 10 

Use this attribute to define how long a disabled link has to be free from loss of signal, loss of framing and 

AIS signals before it is reactivated. 

Reference manual 73



crocusInvMux/security 


In order to avoid unauthorised access to the network and the Crocus Inverse Multiplexer, you can create 

a list of passwords with associated access levels. 

Attribute Description Default value 

password 

The password is a string of maximum 10 characters. 

A maximum of 5 passwords can be defined. 

empty 

accessRights This is a bit string. Each bit corresponds with an access level. 111 

The access levels which you can associate with a password are the following: 


ReadAccess 

WriteAccess 

The user is allowed to read all the attributes except the security 

attributes. 

The user can modify all the attributes except the security 

attributes. Moreover, the security attributes cannot be read. 

enabled 

enabled 

SecurityAccess The user can read and modify the security attributes. enabled 

Entering passwords 

The table below explains how to enter passwords in the different management systems. 

Management system 

TMA 

Telnet 

SNMP 

TML 

TMA CLI and TMA for 

HP OpenView 

How to enter the password 

You can enter the password in the connect windows. 

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

You should use the defined passwords as community strings. If no 

passwords are defined then you can use any string as community strings. 

Similar to TFTP you can send the password after the destination file name, 

separated by a ‘’. 

Example: tml –fsourcefile@destinationfilepwd 

Use the application TmaUserConf.exe to create a TMA user and assign a 

password to this user. The password should correspond with a password 

configured in the device. 

If no passwords are created, everybody has complete access. 

If you define at least one password, it is impossible to access the Crocus Inverse Multiplexer 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. 

74 Reference manual



Clearing the security table 

If you forgot your password or you forgot to create one with write and security access then load the 

default configuration. As a result, the configuration attributes are reset to their default values. Hence, the 

security table is cleared. 

To clear the security table, proceed as follows: 

Step 

Action 

1 Execute steps 1, 2, 3 and 4 of the procedure described in Section 3.3 - Changing the 

DIP switch settings. 

2 Set DIP switch bank DS1 position 4 to off. 

To locate this DIP switch bank, refer to Section 3.1 - Location of the DIP switches. 

3 Place the cover on the Crocus Inverse Multiplexer, without fastening the screws. Then 

power the Crocus Inverse Multiplexer. 

⇒ The Crocus Inverse Multiplexer reboots and loads the default configuration. 

4 After the Crocus Inverse Multiplexer has finished its boot cycle, remove the cover from 

the Crocus Inverse Multiplexer again. 

5 Reset DIP switch bank DS1 position 4 to on. 



⇒ The Crocus Inverse Multiplexer reboots in normal operation mode. 

7 Because the configuration attributes have been reset to their default values, you 

probably will have to reconfigure the Crocus Inverse Multiplexer. Refer to Chapter 5 - 

Step-by-step configuration. 

crocusInvMux/testDuration 

default: 00000d 00h 01m 00s 

Tests initiated with TMA or the network management system are automatically terminated after a timeout 

period as set with the testDuration attribute. This prevents hang-up situations which make normal data 

transfer impossible. 

The time-out range goes from 00000d 00h 00m 01s up to 00049d 17h 00m 00s. When entering 00000d 00h 00m 00s 

the test duration is zero seconds, so no tests are possible. 

crocusInvMux/remoteDTELoopbackDetect 


When set to disabled, this attribute prevents that a remote DCE loop-back test initiated by the remote 

DCE can be executed on the local Crocus Inverse Multiplexer. This prevents the disturbance of the 

normal data transfer by accidental initiation of a remote DCE loop-back test. 

Reference manual 75



crocusInvMux/forwardTMAToLinks 


Disables or enables propagation of TMA management information to the link. If forwardTMAToLinks is 

enabled, management information is sent over the link via a dedicated management channel towards the 

remote Crocus Inverse Multiplexer. 


Site A 

link connection 

Site B 


crocusInvMux/bootFromFlash 

default: Auto 

The Crocus Inverse Multiplexer has two flash memory banks. Each flash memory can contain a complete 

software version, but only one can be active. You can choose from the following settings: 

Value 

Flash 1 

Flash 2 

Auto 

If you boot the Crocus Inverse Multiplexer then … 

the first flash memory bank is activated. 

the second flash memory bank is activated. 

the Crocus Inverse Multiplexer automatically chooses the flash memory bank 

containing the most recent software, by comparing the version numbers of the 

software. 

76 Reference manual



crocusInvMux/errorAlarmThreshold 

The Crocus Inverse Multiplexer permanently monitors the link quality. When certain BER values are 

exceeded, the Crocus Inverse Multiplexer generates an errors alarm. Use the errorAlarmThreshold attribute 

to define at what BER an alarm will be generated in case the link quality deteriorates. 

The errorAlarmThreshold attribute contains a table with the following three attributes: 



(minutes) 

onThreshold 

offThreshold 


calculated. 


or exceeds the value entered in the onThreshold attribute, 

then the Crocus Inverse Multiplexer will generate an 

errors alarm. 

If an errors alarm is active, and within the averagingPeriod 

the average BER value equals or drops below the value 

entered in the offThreshold attribute, then the Crocus 

Inverse Multiplexer will clear the errors alarm. 

1 … 60 2 

10 -3 … 10 -8 10 -6 

10 -3 … 10 -8 10 -7 

The errorAlarmThreshold attribute in the crocusInvMux object applies on all the links which are bonded. The 

errorAlarmThreshold attribute in the link[ ] object only applies on the specific link. 

Avoid setting the averaging period too short. The shorter this period, the faster an alarm will be 

generated. As transmissions errors are statistically spread, a short averaging period could result in 

spurious alarms. 

crocusInvMux/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. 

crocusInvMux/alarmLevel 

With the alarmLevel attribute, a priority level can be assigned to each alarm of the corresponding object. 

The alarm level range goes from 0 to 254, where 0 is the lowest and 254 is the highest priority level. 

For more information on alarms in general, refer to Chapter 9 - Alarm attributes. 

For more information on the alarms of the crocusInvMux object, refer to Section 9.3 - Crocus Inverse 

Multiplexer alarms. 

Reference manual 77



Crocus Inverse Multiplexer – configuration actions 

The following actions are visible when selecting the crocusInvMux object in combination with the Configuration 

tab. 

Configuration actions 

The following three actions are related to the configuration of the Crocus Inverse Multiplexer. Three types 

of configurations are present in the Crocus Inverse Multiplexer: 

• the non-active configuration 

• the active configuration 

• the default configuration. 

When configuring the Crocus Inverse Multiplexer with TMA, as in Chapter 5 - Step-by-step configuration, 

the following happens: 

Phase Action Result 

1 The computer running TMA is connected 

to the Crocus Inverse Multiplexer. 

2 Modifications are made on the non-active 

configuration. 

3 All necessary modifications are carried out 

on the non-active configuration. 

The non-active configuration is displayed 

on the screen. 

These modifications have no immediate 

influence on the active configuration 

currently used by the Crocus Inverse 


Now, the non-active configuration has to 

be made active. 

4 Execute the Activate Configuration action. The non-active configuration becomes the 

active configuration. 

crocusInvMux/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 





Table 6.1: Activating a configuration 

The Activate Configuration action can also be performed with the Send all attributes to device button: . 

78 Reference manual



crocusInvMux/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 Inverse Multiplexer. 

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 



4 

To see the active configuration, press the Retrieve all attributes from device button: . 

crocusInvMux/Load Default Configuration 

If you install the Crocus Inverse Multiplexer for the first time, all configuration attributes are set to their 

default value. If the Crocus Inverse Multiplexer 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. 

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. 


4 To see the default configuration, press the Retrieve all attributes from device button 

. 




Reference manual 79



crocusInvMux/Cold Boot 

This action will reboot the Crocus Inverse Multiplexer while the power stays up (the Crocus Inverse 

Multiplexer also reboots if it is powered down and up again). 

This implies that: 

• it checks which firmware to use 

• it reads the saved configuration and restarts program execution. 

You can use this action, for instance, to activate new firmware. 

To perform a cold boot, proceed as follows: 

Step 

Action 

1 In the TMA window, select the top object crocusInvMux and the group Configuration, Status, 

Performance or Alarms. 

2 In the action window of TMA, click the left mouse button on Cold Boot so that this action is 

selected. 


⇒ The Crocus Inverse Multiplexer boots. The session between TMA and the Crocus 

Inverse Multiplexer is (temporarily) interrupted. 

crocusInvMux/Resynchronise 

Use this action to force a resynchronisation. 

To perform a resynchronisation, proceed as follows: 

Step 

Action 


2 In the action window of TMA, click the left mouse button on Resynchronise so that this 

action is selected. 


80 Reference manual



6.3 LAN interface configuration attributes 

crocusInvMux/lanInterface/ipAddress default: 0.0.0.0 

This attribute defines the IP address for the LAN interface. The address should belong to the subnet the 

interface is connected to. 

crocusInvMux/lanInterface/ipNetMask default: 255.255.255.0 

This attribute defines the IP subnet mask for the LAN interface. This parameter defines the number of IP 

devices that may be present on the corresponding IP segment. 

crocusInvMux/lanInterface/alarmMask 



crocusInvMux/lanInterface/alarmLevel 




For more information on the alarms of the lanInterface object, refer to Section 9.4 - LAN interface alarms. 

crocusInvMux/lanInterface/arpTimeout 

default: 00000d 02h 00m 00s 

The arpTimeout attribute is used for the ageing mechanism of the ARP (Address Resolution Protocol) 

cache. 

The LAN interface has been allocated a fixed Ethernet address, also called MAC (Medium Access 

Control) address. This MAC address is not user configurable. The IP address of the LAN interface, on the 

other hand, is user configurable (refer to the ipAddress attribute). This means that the user associates an 

IP address with the predefined MAC address. The MAC address – IP address pairs are kept in a table, 

called the ARP cache (refer to Section 7.3 - LAN interface status attributes for an example of such a 

table). 

Before the Crocus Inverse Multiplexer sends an IP packet on the LAN interface, it has to know the MAC 

address of the destination device. If it is not known yet, the Crocus Inverse Multiplexer sends an ARP 

request on the Ethernet to learn the MAC address and associated IP address of the destination device. 

This address pair is then written in the ARP cache. 

Summarised, all the MAC address – IP address pairs from ARP requests and replies received on the 

LAN interface are kept in the ARP cache. However, if devices on the network are reconfigured then this 

MAC address – IP address relation may change. Therefore, the ARP cache entries are automatically 

removed from the cache after a fixed timeout. 

This timeout period can be set with arpTimeout attribute. 

crocusInvMux/lanInterface/defaultRoute 


The defaultRoute attribute is the IP address of the first router on the path to the destination network. 

Reference manual 81



6.4 DCE interface configuration attributes 

This section discusses the configuration attributes of the different DCE interfaces. This interface 

configuration attribute overview can be split in several sections: 

• One section discussing the general interface configuration attributes. These are applicable on all 

interfaces. 

• Two sections discussing the specific interface configuration attributes. 

The following table gives an overview of this section. 


6.4.1 General DCE interface configuration attributes 83 

6.4.2 RS530, V35 and V36 interface configuration attributes 84 

6.4.3 X21 interface configuration attributes 86 

6.4.4 Crocus Router Interface 10M configuration attributes 87 

82 Reference manual



6.4.1 General DCE interface configuration attributes 

crocusInvMux/< dceInterface >/alarmMask 



crocusInvMux/< dceInterface >/alarmLevel 




For more information on the alarms of the object, refer to Section 9.5 - DCE interface 

alarms. 

Note that the underlying alarms may differ for each interface. 

Reference manual 83



6.4.2 RS530, V35 and V36 interface configuration attributes 

crocusInvMux/< dceInterface >/rTSControl 

default: external 

Use the rTScontrol attribute to define which device will activate the RTS signal. Following settings are 

possible: 

If RTS control 

is set to … 

the RTS signal is activated 

by … 

This attribute setting is used when … 

external the application. the application has to be in command of the RTS 

signal. 

internal 

the Crocus Inverse 


the application is not able to activate the RTS 

signal. 

Normal operation requires the RTS signal (circuit 105) to be active before the Crocus Inverse Multiplexer 

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 Inverse Multiplexer. 

crocusInvMux/< dceInterface >/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. 

Following delays can be selected: 

• 0 ms 

• 4 ms 

• 16 ms 

• 64 ms 

If RTS control is set to … 

external 

then … 

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. 

crocusInvMux//dTESignalTiming 



If the dTESignalTiming 

is set to … 

then … 

I.e. the transmit clock of the modular DCE 

interface is generated by the … 

disabled DCE timing is selected. Crocus Inverse Multiplexer (DCE). 

enabled DTE timing is selected. user application (DTE). 

For more information on DTE and DCE timing, refer to Section 5.3.3 - DCE clocking principles. 

84 Reference manual


crocusInvMux//tests 



Use the tests attribute to disable or enable the interface tests. 

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

Test 

interfaceAL 

interfaceRDL 

Description 

Local link loop-back (or Analogue Loop) which can be initiated by the DCE via the 

interface. 

Remote DCE loop-back (or Remote Digital Loop) which can be initiated by the DCE 

via the interface. 

Reference manual 85



6.4.3 X21 interface configuration attributes 

crocusInvMux/x21/DCESignalTiming 



The normal clock configuration for an X21 interface is DCE timing, and this on both sides. In exceptional 

cases however, the X21 interface can also be configured for DTE timing provided the X circuit is used. 

86 Reference manual



6.4.4 Crocus Router Interface 10M configuration attributes 

crocusInvMux/router/cms2Address 


Use this attribute to define an absolute address in the Crocus Router Interface 10M. Refer to Section 

5.9.2 - Using relative or absolute addressing for more information on absolute addressing. Also refer to 

Section 5.9.5 - Addressing the Crocus Router Interface 10M for more information about addressing the 

Crocus Router interface 10M. 

Reference manual 87



6.5 Link configuration attributes 

crocusInvMux/link[ ]/ifAdminStatus 

default: up 

The ifAdminStatus attribute determines the link activation. By setting this attribute to down: 

• you can disable unused links on the Crocus Inverse Multiplexer 

• alarms are reset on the corresponding link. 

crocusInvMux/link[ ]/physicalInterface 


The physicalInterface attribute allows you to make a double selection: 

• the selection between one of the two link connectors on the one hand 



The physicalInterface attribute has the following values: 

Value 

Description 

75 Ohm This selects the coaxial BNC connectors as link connector, with an impedance of 75 

ohm. 

120 Ohm This selects the twisted pair RJ45 connector as link connector, with an impedance 

of 120 ohm. 

crocusInvMux/link[ ]/cRC4Generation 


The CRC4 check provides an end-to-end quality monitoring of each individual E1 link. Two types of 

CRC4 checks can be run over a specific link: 

• CRC4 link check (can be enabled or disabled by the user) 

• CRC4 bonding check (is always enabled). 

It is the CRC4 link check which can be enabled or disabled with the cRC4Generation attribute. This attribute 

is only present to provide compatibility with intermediate equipment. The actual CRC4 error detection as 

used on the Crocus Inverse Multiplexer is always on the CRC4 bonding level and is always enabled. 

For a visual interpretation of CRC4 link and bonding check, refer to Section 1.2.5 - Cyclic Redundancy 

Check – CRC4. 

88 Reference manual



crocusInvMux/link[ ]/errorAlarmThreshold 

The Crocus Inverse Multiplexer permanently monitors the link quality. When certain BER values are 

exceeded, the Crocus Inverse Multiplexer generates an errors alarm. Use the errorAlarmThreshold attribute 

to define at what BER an alarm will be generated in case the link quality deteriorates. 

The errorAlarmThreshold attribute contains a table with the following three attributes: 



(minutes) 

onThreshold 

offThreshold 


calculated. 


or exceeds the value entered in the onThreshold attribute, 

then the Crocus Inverse Multiplexer will generate an 

errors alarm. 

If an errors alarm is active, and within the averagingPeriod 

the average BER value equals or drops below the value 

entered in the offThreshold attribute, then the Crocus 

Inverse Multiplexer will clear the errors alarm. 

1 … 60 2 

10 -3 … 10 -8 10 -6 

10 -3 … 10 -8 10 -7 

The errorAlarmThreshold attribute in the crocusInvMux object applies on all the links which are bonded. The 

errorAlarmThreshold attribute in the link[ ] object only applies on the specific link. 

Avoid setting the averaging period too short. The shorter this period, the faster an alarm will be 

generated. As transmissions errors are statistically spread, a short averaging period could result in 

spurious alarms. 

crocusInvMux/link[ ]/alarmMask 



crocusInvMux/link[ ]/alarmLevel 




For more information on the alarms of the link[ ] object, refer to Section 9.6 - Link alarms. 

Reference manual 89



6.6 SNMP proxy configuration attributes 

crocusInvMux/snmpProxy/trapDestinations 


The Crocus Inverse Multiplexer translates all alarm status changes into SNMP traps. These traps can 

then be sent to a management system. To enable this, configure in the trapDestinations table the IP 

addresses to which the traps have to be sent. If the trapDestinations table is empty then no traps are sent. 

The trapDestinations table contains the following attributes: 


address 

community 

This is the IP address of the management station to which the SNMP 

trap messages have to be sent. 

This is the community string which is included in the SNMP traps 

which are sent to the management station. It is used as a password 

in the SNMP communication. Give it the same value as on your 

SNMP management station. 

0.0.0.0 

public 

crocusInvMux/snmpProxy/mib2Traps 

default: off 

Use this attribute if you want to send the SNMP traps as MIB2 traps or as enterprise specific (private) 

MIB traps. 

Proceed as follows: 

Step 

Action 

1 Select the trapDestinations attribute. Add an entry to this table for each network management 

station that should receive SNMP traps. 

2 First define the IP address of the management stations that should receive the SNMP traps. 

3 Set the community attribute associated with each trap destination. 

4 Configure the mib2Traps attribute. 

Value 

on 

off 

Description 

Select this value if the management station is any SNMP station 

(without the TMA for HP OpenView application). In that case, the 

Crocus Inverse Multiplexer sends the alarms coldBoot, warmBoot and 

linkDown as MIB2 traps instead of enterprise specific (private) MIB 

traps. 

Select this value if the management system is the TMA for HP 

OpenView application. In that case the Crocus Inverse Multiplexer 

sends all alarms as enterprise specific (private) MIB traps. 

5 Set for each object of the Crocus Inverse Multiplexer: 

• the alarms that you want to send using the attribute alarmMask 

• the importance of each alarm using the attribute alarmLevel. 

By default only the most important alarms are enabled. 

90 Reference manual



6.7 Management configuration attributes 

crocusInvMux/management/cms2Address default: 0 

Use this attribute to define an absolute address in the Crocus Inverse Multiplexer. Refer to Section 5.9.2 - 

Using relative or absolute addressing for more information on absolute addressing. 

crocusInvMux/management/accessList 


In order to control the access from certain hosts or networks, you can define an access list. This list filters 

incoming traffic for the Crocus Inverse Multiplexer, based on the source IP address. 

Every entry in the access list contains the following elements: 


sourceAddress 

mask 

This is the IP source address of the packet. The address may be 

a (sub)network address. 

This is the IP subnetmask for the sourceAddress. By combining an 

IP address with a mask you can uniquely identify a range of 

addresses. Before comparing IP addresses, a logical “AND” 

function is made between both addresses and the mask. 

0.0.0.0 

255.255.255.255 

action The action to be taken on the above specified range can be: deny 

Value 

deny 

allow 

Description 

The packets will be dropped. 

The packets will be forwarded. 

You can specify multiple entries within the access list. When more than one entry applies to the same 

packet, then only the most specific one is taken in consideration. I.e. the entry covering the smallest 

range. If not one entry matches, then the packet is dropped. If the access list is empty, then all packets 

are forwarded. 

Example 1 

This example shows an access list that only forwards 

traffic from subnet 192.168.48.0 to the LAN interface, 

except for packets from station 192.168.48.10. All 

other traffic for the LAN interface is dropped. 

Example 2 

The next example shows an access list to forward all 

traffic, except the traffic from subnet 192.168.48.0. The 

second entry is the rule to add if you want all packets 

that do not match the previous entries to be forwarded. 

Reference manual 91



crocusInvMux/management/snmp 


It is possible to discard all SNMP requests in order to protect the Crocus Inverse Multiplexer against any 

SNMP requests. Possible values for this attribute are: 

Value 

Description 

enabled 

disabled 

SNMP requests are accepted. 

All SNMP requests are discarded. 

You need security access to read and change this attribute. 

crocusInvMux/management/telnet 


Similar to SNMP, you can also protect the Crocus Inverse Multiplexer against any telnet sessions. 

Possible values for this attribute are: 

Value 

Description 

enabled 

disabled 

Telnet sessions are accepted. 

All telnet session requests are discarded. 


crocusInvMux/management/tftp 


Similar to SNMP and telnet, you can also protect the Crocus Inverse Multiplexer against any TFTP 

sessions. Possible values for this attribute are: 

Value 

Description 

enabled 

disabled 

TFTP sessions are accepted. 

All TFTP session requests are discarded. 


92 Reference manual



crocusInvMux/management/consoleNoTrafficTimeout 

default: 00000d 00h 30m 00s 

You can open a TMA, TMA CLI or ATWIN session on the Crocus Inverse Multiplexer through the auxiliary 

connector. These sessions close automatically if there is no user interaction during a certain timeout 

period. This timeout period can be set with the consoleNoTrafficTimeout attribute. 

The purpose of such a timer is to protect the Crocus Inverse Multiplexer against unauthorised access in 

case the last user did not close his session. 

The range of the timeout period goes from 00000d 00h 00m 00s up to 24855d 03h 14m 07s. 

The consoleNoTrafficTimeout attribute is only effective when the consoleSelection attribute is set to console, not 

when it is set to nms. 

crocusInvMux/management/alarmFilter default: 0 

The alarmFilter makes it possible to selectively ignore / drop alarms below a certain level in TMA for HP 

OpenView. This filter number corresponds with a certain filter which is defined in the Alarm Manager of 

TMA for HP OpenView. 

The Alarm Manager makes it possible to specify a minimum alarm level that is needed before alarms are 

logged in HP OpenView. This can be specified for each filter number. 

The alarmFilter value ranges from 0 up to 50000. 

crocusInvMux/management/consoleSelection 

default: console 

Use the consoleSelection attribute to define which kind of application runs over the auxiliary connection. 

Value 

Description 

nms 

Select this option if you want to … 

• connect the auxiliary connector to a port of the Orchid 1003 LAN for 

management purposes 

• open a TMA session on the Crocus Inverse Multiplexer through the auxiliary 

connector. 

console 

Select this option if you want to … 

• open a TMA session 

• open a TMA CLI session 

• open an ATWIN session 

… on the Crocus Inverse Multiplexer through the auxiliary connector. 

Reference manual 93

Status attributes 


7. Status attributes 

This chapter discusses the status attributes of the Crocus Inverse Multiplexer. The following table gives 

an overview of this chapter. 


7.1 Status attribute overview 95 

7.2 Crocus Inverse Multiplexer status attributes 97 

7.3 LAN interface status attributes 101 

7.4 DCE interface status attributes 104 

7.5 Link status attributes 109 

7.6 Management status attributes 112 

7.7 Operating system status attributes 112 

94 Reference manual



7.1 Status attribute overview 


sysDesc 

sysObjectID 

sysServices 

sysUpTime 

flash1Version 

flash2Version 

bootVersion 

activeFlash 

clockInUse 

linksInUse 

timeSinceLastSync 

localBondingSyncLoss 

remoteBondingSyncLoss 

testType 

testOriginator 

testStatus 

errorCount 

deciveID 

messages 


Action: clearErrorCount 


ipAddress 

ipNetMask 

ifDescr 

ifType 

ifMtu 

ifOperStatus 

ifLastChange 

ifSpeed 

arpCache 

macAddress 

ipAdEntBcastAddr 

ipAdEntReasmMaxSize 

>> 

>> rs530, v35, v36 

ifDescr 

ifType 

ifSpeed 

ifOperStatus 

dTEExtClock 

dTEClockSlips 

tXDCCT103 

rXDCCT104 

rTSCCT105 

cTSCCT106 

dSRCCT107 

dCDCCT109 

rDLCCT140 

aLCCT141 

tICCT142 

>> x21 

ifDescr 

ifType 

ifSpeed 

ifOperStatus 

dTEExtClock 

dTEClockSlips 

tXDCCT103 

rXDCCT104 

indicator 

control 

>> router 

ifDescr 

ifType 

ifSpeed 

ifOperStatus 

wANTXD 

wANRXD 

Reference manual 95




linkNumber 

ifDescr 

ifType 

ifSpeed 

ifOperStatus 

linkStatus 

linkFrameType 

linkTestType 

testOriginator 

testStatus 

errorCount 

>> management 

cms2Address 

>> operatingSystem 

taskInfo 

96 Reference manual



7.2 Crocus Inverse Multiplexer status attributes 

crocusInvMux/sysDesc 

This is a textual description of the device. It is a SNMP MIB2 parameter. 

Example: Telindus Crocus Inverse Mux Txxxx/xxxx 01/01/00 12:00. In this example the following parameters are 

visible: 

• Telindus is the manufacturer name 

• Crocus Inverse Mux is the device name 

• Txxxx/xxxx is the firmware code and version 

• 01/01/00 12:00 is the firmware release date and time. 

crocusInvMux/sysObjectID 

This is the SNMP identification string. It is a SNMP MIB2 parameter. 

Example: 1.3.6.1.4.1.776.14. 

crocusInvMux/sysServices 

This is the SNMP service identification. It is a SNMP MIB2 parameter. 

Example: 1, which indicates that the Crocus Inverse Multiplexer is a layer 1 device type. I.e. it has a 

physical functionality. 

crocusInvMux/sysUpTime 

This is the time since last power-on or cold boot of the Crocus Inverse Multiplexer. 

Example: 00005d 02h 42m 15s, which means 5 days, 2 hours, 42 minutes and 15 seconds. 

crocusInvMux/flash1Version 

crocusInvMux/flash2Version 

This displays the code and version of the firmware currently stored in flash bank 1 and 2, respectively. If a 

flash bank does not contain firmware then the value is left empty. 

Example: Txxxx/xxxx 01/01/00 12:00. In this example the following parameters are visible: 

• Txxxx is the firmware code for this device 

• /xxxx is the firmware version 

• 01/01/00 is the firmware release date 

• 12:00 is the firmware release time. 

crocusInvMux/bootVersion 

This displays the code and version of the boot software currently used in the Crocus Inverse Multiplexer. 

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. 

crocusInvMux/activeFlash 

This displays which flash bank is currently active. 

Example: Flash2, which means the firmware stored in flash bank 2 currently controls the device. 

Reference manual 97



crocusInvMux/clockInUse 

This is the clocking mode which is effectively used by the Crocus Inverse Multiplexer. This is not 

necessarily the clocking mode you selected with the configuration attribute clockSelection. It can be a 

clocking mode which is selected by the Crocus Inverse Multiplexer in case the clocking mode of your 

choice fails. 

crocusInvMux/linksInUse 

This attribute shows the amount of links which are actually transferring data. I.e. the links of which the 

configuration attribute ifAdminStatus and status attribute ifOperStatus are up. 

crocusInvMux/timeSinceLastSync 

This is the elapsed time since the last synchronisation, whether successful or not, occurred. 

crocusInvMux/localBondingSyncLoss 

Indicates that the synchronisation between the E1 links on the local Crocus Inverse Multiplexer is lost. 

crocusInvMux/remoteBondingSyncLoss 

Indicates that the synchronisation between the E1 links on the remote Crocus Inverse Multiplexer is lost. 

crocusInvMux/testType 

This attribute displays the type of test which is running. The possible indications are: 

Value 

Description 

NO test 

reverse DCE loopback 

remote DCE loopback 

reverse Link loopback 

eT test 

remote DCE loopback + ET 

local Link loopback + ET 

local Link loopback 


A reverse DCE loop-back test is active. 

A remote DCE loop-back test is active. 

A reverse link loop-back test is active. 

The error test pattern generator / detector is active. 

A remote DCE loop-back test is active in combination with the error test 

pattern generator / detector. 

A local link loop-back test is active in combination with the error test pattern 

generator / detector. 

A local link loop-back test is active. 

For more information on diagnostic tests, refer to Chapter 12 - Diagnostic tests. 

The attributes concerning diagnostic tests (testType, testOriginator, testStatus and errrorCount) which are 

located in the object … 

• crocusInvMux, apply on all the active links 

• link[ ], only apply on that specific link. 

98 Reference manual



crocusInvMux/testOriginator 

This attribute displays the origin of the test which is running. The possible indications are: 

Value 

Description 

nmstst 

interfacetst 

remotetst 

unknown 

The test is initiated by the Telindus Maintenance Application or the central 

management system (e.g. HP OpenView). 

The test is initiated by the DCE through the DCE interface. 

The test is initiated by the remote Crocus Inverse Multiplexer. 

There are two possibilities: 

• No test is running. 

• For some reason it is not possible to define the origin of the test. 

crocusInvMux/testStatus 

This attribute displays the status of the test which is running. The possible indications are: 

Value 

Description 

progressing 

running 

ending 

unknown 

The test is starting. 

The test is running. 

The test is ending. 



• For some reason it is not possible to retrieve the status of the test. 

Reference manual 99



crocusInvMux/errorCount 

This attribute displays the amount of detected errors since the start of an eT test or a test in combination 

with an eT test. Every time such a new test is started, the errorCount attribute is reset to 0. 

crocusInvMux/deviceID 

This displays a unique code. This code is programmed into the Crocus Inverse Multiplexer before it 

leaves the factory. You can use this code for inventory purposes. 

crocusInvMux/messages 

This table displays informative and error messages, e.g. Reconfigured, Cold Boot, … The messages table 

displays maximum 20 messages. 




For more information, refer to Section 6.2 - Crocus Inverse Multiplexer configuration attributes. 

crocusInvMux/clearErroCount 

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. 

100 Reference manual



7.3 LAN interface status attributes 

crocusInvMux/lanInterface/ipAddress 

This is the IP address of the LAN interface as you configured it with the configuration attribute ipAddress. 

crocusInvMux/lanInterface/ipNetMask 

This is the IP subnet mask of the LAN interface as you configured it with the configuration attribute 

ipNetMask. 

crocusInvMux/lanInterface/ifDescr 

This attribute displays the interface description. It is a SNMP MIB2 parameter. 

The ifDescr value for the lanInterface object is lan. 

crocusInvMux/lanInterface/ifType 

This attribute displays the interface type. It is a SNMP MIB2 parameter. 

The ifType value for the lanInterface object is ethernet-csmacd. 

crocusInvMux/lanInterface/ifMtu 

This is the interface Maximum Transfer Unit, i.e. the maximum number of bytes that one packet can 

contain on this interface. It is a SNMP MIB2 parameter. 

crocusInvMux/lanInterface/ifOperStatus 

This attribute displays the current operation status of the LAN interface. Possible operation status values 

are: 

Value 

Description 

up 

down 

The LAN interface is up, data transfer is possible. 

The LAN interface is down, data transfer is not possible. 

crocusInvMux/lanInterface/ifLastChange 

This is the system-up time when the interface entered its current operational state. I.e. the moment the 

value of the ifOperStatus status attribute changes (from up to down or vice versa), the system-up time value 

is written into the ifLastChange status attribute. 

It is a SNMP MIB2 parameter. 

crocusInvMux/lanInterface/ifSpeed 

This attribute displays the current LAN interface speed in bits per second (bps), e.g. 10000000. 

Reference manual 101



crocusInvMux/lanInterface/arpCache 

This table displays all the MAC address – IP address pairs from ARP requests and replies received on 

the LAN interface. 

Every entry in the ARP cache table contains the following elements: 

Attribute 

macAddress 

ipAddress 

type 

Description 

The corresponding MAC address, e.g. 00:C0:89:00:0F:ED. 

The IP address. 

ARP cache entries can be one of the following types. 

Value 

dynamic 

static 

Description 

The match is retrieved from an ARP request or reply message. 

The match has been configured before. 

There is only one static entry, i.e. the Crocus Inverse Multiplexer 

its own IP and MAC address. 

timeout 

This is the time this entry still will remain in the ARP cache. For the static entry, this 

value is 0. 

The following figure shows part of an ARP cache table as an example: 

crocusInvMux/lanInterface/macAddress 

The LAN interface has been allocated a fixed Ethernet address, also called MAC (Medium Access 

Control) address. The MAC address is globally unique and can not be modified. It is a 6 byte code, 

represented in hexadecimal format. Each byte in the code is separated by a colon. 

This attribute displays the MAC address of the Crocus Inverse Multiplexer: 00:C0:89:00:0F:ED. 




crocusInvMux/lanInterface/ipAdEntBcastAddr 

This attribute displays the value of the least-significant bit in the IP broadcast address. This address is 

used for sending packets on the interface which is associated with the IP address of this entry. The value 

applies to both the general broadcast, the subnet and network broadcasts. 


crocusInvMux/lanInterface/ipAdEntReasmMaxSize 

This attribute displays the size of the largest IP packet which this entity can re-assemble from incoming IP 

fragmented packets received on this interface. Value 0 means there is no re-assembly. 





7.4 DCE interface status attributes 

This section discusses the status attributes of the different DCE interfaces. The following table gives an 

overview of this section. 


7.4.1 General interface status attributes 105 

7.4.2 RS530, V35 and V36 interface status attributes 106 

7.4.3 X21 interface status attributes 107 

7.4.4 Crocus Router interface 10M status attributes 108 

The following interface status attribute overview can be split in several sections: 

• One section discussing the general interface status attributes. These are applicable on all interfaces. 

• Three sections discussing the specific interface status attributes. 




7.4.1 General interface status attributes 

crocusInvMux//ifDescr 


crocusInvMux//ifType 


The following table shows the ifDescr and ifType attribute values for each DCE interface. 

ifDescr value 

RS530 

V35 

V36 

X21 

router 

ifType value 

other 

other 

other 

other 

other 

crocusInvMux//ifSpeed 

This attribute displays the current DCE interface speed in bits per second (bps), e.g. 7808000. 

crocusInvMux//ifOperStatus 

This attribute displays the current operation status of the DCE interface. The possible indications are: 

Value 

Description 

up 

down 

testing 

The DCE interface is up, data transfer is possible. 

The DCE interface is down, data transfer is not possible. 

An interface test is active. 

For more information on type, originator and status of the test refer to the status 

attributes (link)TestType, testOriginator and testStatus. 






crocusInvMux//dTEClockSlips 

This attribute shows how many times the deviation between the DCE clock and the system clock becomes 

unacceptable. A dTEClockSlips value of 1 is normal. This usually occurs when the Crocus Inverse 

Multiplexer boots. 




7.4.2 RS530, V35 and V36 interface status attributes 

crocusInvMux//dTEExtClock 

This attribute displays whether the DCE applies an external clock to the external clock pin of the modular 

DCE interface or not. 

crocusInvMux//tXDCCT103 

This attribute displays the status (on / off) of the transmit data signal (circuit 103). 

crocusInvMux//rXDCCT104 

This attribute displays the status (on / off) of the receive data signal (circuit 104). 

crocusInvMux//rTSCCT105 

This attribute displays the status (on / off) of the request to send signal (circuit 105). 

crocusInvMux//cTSCCT106 

This attribute displays the status (on / off) of the clear to send signal (circuit 106). 

crocusInvMux//dSRCCT107 

This attribute displays the status (on / off) of the data set ready signal (circuit 107). 

crocusInvMux//dCDCCT109 

This attribute displays the status (on / off) of the data carrier detect signal (circuit 109). 

crocusInvMux//rDLCCT140 

This attribute displays the status (on / off) of the remote digital loop signal (circuit 140). 

crocusInvMux//aLCCT141 

This attribute displays the status (on / off) of the analogue loop signal (circuit 141). 

crocusInvMux//tICCT142 

This attribute displays the status (on / off) of the test indication signal (circuit 142). 




7.4.3 X21 interface status attributes 

crocusInvMux/x21/dTEExtClock 

This attribute displays whether the DCE applies an external clock to the external clock pin of the modular 

DCE interface or not. 

crocusInvMux/x21/tXDCCT103 

This attribute displays the status (on / off) of the transmit data signal (circuit 103). 

crocusInvMux/x21/rXDCCT104 

This attribute displays the status (on / off) of the receive data signal (circuit 104). 

crocusInvMux/x21/indicator 

This attribute displays the status (on / off) of the indicator signal. 

crocusInvMux/x21/control 

This attribute displays the status (on / off) of the control signal. 




7.4.4 Crocus Router interface 10M status attributes 

crocusInvMux/router/wanTxd 

This attribute displays the status (on / off) of the WANTXD (wide area network transmit data) signal, after 

encapsulation of the user data on the router interface. 

crocusInvMux/router/wanRxd 

This attribute displays the status (on / off) of the WANRXD (wide area network receive data) signal, 

before extraction of the user data on the router interface. 




7.5 Link status attributes 

crocusInvMux/link[ ]/linkNumber 

This attribute displays the link number of the link currently selected in TMA: 1, 2, 3 or 4. 

crocusInvMux/link[ ]/ifDescr 


The ifDescr value for the link[ ] object is link. 

crocusInvMux/link[ ]/ifType 


The ifType value for the link[ ] object is e1. 

crocusInvMux/link[ ]/ifSpeed 

This attribute displays the current link speed in bits per second (bps), e.g. 2048000. 

crocusInvMux/link[ ]/ifOperStatus 

This attribute displays the current operation status of the link. The possible indications are: 

Value 

Description 

up 

down 

testing 

The link is up, data transfer is possible. 

The link is down, data transfer is not possible. 

A link test is active. 

For more information on type, originator and status of the test refer to the link 

status attributes linkTestType, testOriginator and testStatus. 

crocusInvMux/link[ ]/linkStatus 

This attribute displays the current status of the link. Possible indications are: 

Value 

Description 

normal 

LOS 

LOF 

AIS 

The current status of the link is normal. Non of the possible problems as listed 

below have been detected. 

A Loss Of Signal is detected. 

A Loss Of Frame alignment is detected. 

An Alarm Indication Signal is detected. 




crocusInvMux/link[ ]/linkFrameType 

This attribute displays the type of framing detected by the receiver. Possible indications are: 

Value 

Description 

unknown 

doubleFraming 

crc4MultiFrame 

No framing has been found. 

G.704 framing is detected. 

G.704 + CRC4 framing is detected. 

crocusInvMux/link[ ]/linkTestType 

This attribute displays the type of test which is running. The possible indications are: 

Value 

Description 

NO test 

reverse Link loopback 

eT test 

local Link loopback + ET 


A reverse link loop-back test is active. 

The error test pattern generator / detector is active. 

A local link loop-back test is active in combination with the error test pattern 

generator / detector. 






crocusInvMux/link[ ]/testOriginator 

This attribute displays the origin of the test which is running. The possible indications are: 

Value 

Description 

nmstst 

interfacetst 

remotetst 

unknown 

The test is initiated by the Telindus Maintenance Application or the central 

management system (e.g. HP OpenView). 

The test is initiated by the DCE through the DCE interface. 

The test is initiated by the remote Crocus Inverse Multiplexer. 



• For some reason it is not possible to define the origin of the test. 




crocusInvMux/link[ ]/testStatus 

This attribute displays the status of the test which is running. The possible indications are: 

Value 

Description 

progressing 

running 

ending 

unknown 

The test is starting. 

The test is running. 

The test is ending. 



• For some reason it is not possible to retrieve the status of the test. 

crocusInvMux/link[ ]/errorCount 






7.6 Management status attributes 

crocusInvMux/management/cms2Address 

This is the CMS2 address as you configured it with the configuration attribute cms2Address. 

7.7 Operating system status attributes 

crocusInvMux/operatingSystem/taskInfo 

The taskInfo table displays status information about the operating system. The table contains the following 

attributes: 

Attribute 

Description 

taskName 

taskStatus 

Name of the task. 

Current status. The task can have the following status values: 

• awake: this task is actually running. 

• asleep: this task is waiting on an event. 

• inactive: this task slot is not active, i.e. no task has been assigned to this slot. 

RelLoad30s (%) 

RelLoad5min (%) 

RunningInMedium (%) 

RunningInHigh (%) 

ProgramCounter 

This is the relative load on the processor during the last 30 seconds. 

This is the relative load on the processor during the last 5 minutes. 

Each task can be running with a low, medium or high priority. This element gives 

the percentage of time this task is running with medium priority during the last 30 

seconds. 

Each task can be running with a low, medium or high priority. This element gives 

the percentage of time this task is running with high priority during the last 30 

seconds. The percentage of time this task is running with low priority can be 

calculated using the following formula: 

100% - RunningInMedium (%) - RunningInHigh (%). 

This is the current value of the program counter. The program counter is the 

memory address for the current instruction of this task. 



Performance attributes 

8. Performance attributes 

This chapter discusses the performance attributes of the Crocus Inverse Multiplexer. The following table 



8.1 Performance attribute overview 114 

8.2 Introduction to the performance attributes 115 

8.3 Crocus Inverse Multiplexer performance attributes 117 

8.4 LAN interface performance attributes 122 

8.5 Link performance attributes 123 

8.6 Operating system performance attributes 126 




8.1 Performance attribute overview 


errorCount 

resynchronisations 

fallbackCount 

fallbackTime 

diffDelay (ms) 

bitErrorRate 

errorAlarmCount 

errorAlarmTime 

unavailableCount 

unavailableTime 

errSeconds 

burstErrSeconds 

sevErrSeconds 

h2Parameters 

h2BitErrors 

h2Performance 

h24Parameters 

h24BitErrors 

h24Performance 


Action: Activate Test 


ifInOctets 

ifInUcastPkts 

ifInNUcastPkts 

ifInDiscards 

ifInErrors 

ifInUnknownProtos 

ifOutOctets 

ifOutUcastPkts 

ifOutNUcastPkts 

ifOutDiscards 

ifOutErrors 

ifOutQLen 


errorCount 

lOSCount 

lOSTime 

lOFCount 

lOFTime 

aISCount 

aISTime 

bitErrorRate 

errorAlarmCount 

errorAlarmTime 

errSeconds 

sevErrSeconds 




h2Parameters 

h2BitErrors 

h2Performance 

h24Parameters 

h24BitErrors 

h24Performance 

Action: Activate Test 

>> operatingSystem 

currUsedProcPower (%) 

usedProcPower 

freeDataBuffers 

totalDataBuffers 

largestFreeBlockSize 

freeBlockCount 

freeMemory 

totalMemory 

taskInfo 




8.2 Introduction to 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 Inverse Multiplexer in detail, some general 

information on the performance attributes of the Crocus Inverse Multiplexer is given. 

This section can be broken up into two parts: 

• First, the timing of the performance information is explained. 

• Secondly, frequently used terms such as min – max – average, count and time are explained. 

The following table explains the performance information timing. 

Interval 

Description 

2 hours The performance information is accumulated during a 15 minutes time span, 

called a period. After a period, the accumulated performance information is 

written into a buffer. Then a new period starts. To cover a 2 hours interval, 8 

periods are kept. 

The buffer in which the information is stored, is a circular buffer. I.e. every 15 

minutes the most recent measured and calculated values are added, and the 

oldest values are lost. 

24 hours The performance information is accumulated during a 2 hours time span, called 

a period. After a period, the accumulated performance information is written into 

a buffer. Then a new period starts. To cover a 24 hours interval, 12 periods are 

kept. 

The buffer in which the information is stored, is a circular buffer. I.e. every 2 

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 Inverse Multiplexer. This can be considered as a performance 

information summary. 

The Crocus Inverse Multiplexer 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. 

Only the available performance information is displayed. If the interrogation happens shortly after boot, no 

values are displayed. For example for the 2 hours and 24 hours intervals, the new performance 

information is available only when a complete time span (15 minutes, 2 hours) has elapsed. 




The following table explains the performance information terms. 

Term 

min, max, avrg 

count 

time 

Description 

Display the minimum, maximum and average values calculated for the 

corresponding period. 

E.g. min-max-avrg value of the bit error rate. 

Counts the number of times an event occurred during the corresponding period. 

E.g. the number of times an alarm was active. 

Indicates the time duration of an event during the corresponding period. 

E.g. the time during which an alarm was active. 




8.3 Crocus Inverse Multiplexer performance attributes 

Several performance attributes are present in both the crocusInvMux object as in the link[ ] object. 

• The crocusInvMux object performance attributes apply on the bonding; i.e. all the active, bonded links 

(bonding level). 

• The link[ ] object performance attributes apply on the particular link (link level). 

crocusInvMux/errorCount 



crocusInvMux/resynchronisations 

This attribute displays how many resynchronisations occurred since the last cold boot. 

crocusInvMux/fallbackCount 

This attribute displays how many times a fall-back occurred since the last cold boot. 

crocusInvMux/fallbackTime 

This attribute displays the total fall-back time since the last cold boot. 

crocusInvMux/diffDelay 

This attribute displays the relative time difference between the data on the link that arrives with the 

smallest delay and the data on the link that arrives with the largest delay. 

crocusInvMux/bitErrorRate 

This attribute displays the bit error rate for the elapsed time since the last cold boot. 

crocusInvMux/errorAlarmCount 

This attribute displays the number of error alarms which was counted since the last cold boot. The alarms 

are counted during the synchronised bonding state. 

crocusInvMux/errorAlarmTime 

This attribute displays the time during which an error alarm was active since the last cold boot. The time 

is measured during the synchronised bonding state. 

crocusInvMux/unavailableCount 

This attribute displays the number of unavailability alarms which was counted since the last cold boot. 

The alarms are counted during the synchronised bonding state. 

crocusInvMux/unavailableTime 

This attribute displays the time during which an unavailability alarm was active since the last cold boot. 

The time is measured during the synchronised bonding state. 




crocusInvMux/errSeconds 

This attribute displays the number of seconds for which the summation of the CRC4 errors of the links 

that are bonded is not zero. The seconds are counted during the synchronised bonding state, and this 

since the last cold boot. 

errSeconds is also counted when the link is in unavailable state. This is not in conformity with G.826. 

crocusInvMux/burstErrSeconds 

This attribute displays the number of seconds for which the BER of the links that are bonded is between 

10 -5 and 10 -4 . The seconds are counted during the synchronised bonding state, and this since the last 

cold boot. 

crocusInvMux/sevErrSeconds 

This attribute displays the number of seconds for which the BER of the links that are bonded is higher 

than 10 -4 . The seconds are counted during the synchronised bonding state, and this since the last cold 

boot. 

sevErrSeconds is also counted when the link is in unavailable state. This is not in conformity with G.826. 

crocusInvMux/h2Parameters 

This structured value displays the 2 hours performance summary of the parameters resynchronisations, 

fallbackCount, fallbackTime and diffDelay. The h2Parameters attributes are: 

Attribute 

sysUpTime 

resynchronisations 

fallbackCount 

fallbackTime 

diffDelayMin (ms) 

diffDelayMax (ms) 

diffDelayAvrg (ms) 

For the corresponding period, this value displays … 

the elapsed time since the last cold boot. 

how many resynchronisations occurred. 

how many times a fall-back occurred. 

the fall-back time. 

the minimum differential delay between the active E1 links which was measured. 

the maximum differential delay between the active E1 links which was 

measured. 

the average differential delay between the active E1 links which was calculated. 




crocusInvMux/h2BitErrors 

This structured value displays the 2 hours performance summary related to the bit error rate. The 

h2BitErrors attributes are: 

Attributes 

sysUpTime 

bERMin 

bERMax 

bERAvrg 

alarmCount 

alarmTime 



the minimum bit error rate which was measured. 

the maximum bit error rate which was measured. 

the average bit error rate which was calculated. 

the number of bit error rate alarms which was counted. 

the time during which a bit error rate alarm was active. 




crocusInvMux/h2Performance 

This structured value displays the 2 hours performance summary related to the performance. The 

h2Performance attributes are: 

Attribute 

sysUpTime 

errSeconds 

sevErrSeconds 






the number of erroneous seconds which was counted. 

the number of severely erroneous seconds which was counted. 

the number of error burst seconds which was counted. 

the number of unavailability alarms which was counted. 

the time during which an unavailability alarm was active. 

crocusInvMux/h24Parameters 

This structured value displays the 24 hours performance summary of the parameters resynchronisations, 

fallbackCount, fallbackTime and diffDelay. The h24LineParameters attributes are the same as the h2LineParameters 

attributes. 

crocusInvMux/h24BitErrors 


h24BitError attributes are the same as the h2BitError attributes. 

crocusInvMux/h24Performance 


h24Performance attributes are the same as the h2Performance attributes. 







For more information, refer to Section 6.2 - Crocus Inverse Multiplexer configuration attributes. 

crocusInvMux/Activate Test 

Use this action to perform a test on the Crocus Inverse Multiplexer. These tests are useful to trace 

possible problems. 

To execute a test, proceed as follows: 

Step 

Action 

1 In the TMA window, select the object crocusInvMux and the group Performance. 

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 action you want to execute. 


For more information on these tests, refer to Chapter 12 - Diagnostic tests. 




8.4 LAN interface performance attributes 

crocusInvMux/lanInterface/ifInOctets 

This is the number of octets (bytes) received on this interface. 

crocusInvMux/lanInterface/ifInUcastPkts 

This is the number of unicast packets received on this interface and delivered to a higher-layer protocol. 

Unicast packets are all non-multicast and non-broadcast packets. 

crocusInvMux/lanInterface/ifInNUcastPkts 

This is the number of non-unicast packets received on this interface and delivered to a higher-layer 

protocol. Non-unicast packets are all the multicast and broadcast packets. 

crocusInvMux/lanInterface/ifInDiscards 

This is the number of incoming packets that were discarded, to prevent their deliverance to a higher-layer 

protocol. This even though no errors were detected in these packets. 

crocusInvMux/lanInterface/ifInErrors 

This is the number of incoming packets that could not be delivered to a higher-layer protocol because 

they contained errors. 

crocusInvMux/lanInterface/ifInUnknownProtos 

This is the number of incoming packets that were discarded because they contained an unknown or 

unsupported protocol. 

crocusInvMux/lanInterface/ifOutOctets 

This is the total number of octets (bytes) transmitted by the interface, including framing characters. 

crocusInvMux/lanInterface/ifOutUcastPkts 

This is the total number of packets that higher-level protocols requested to be transmitted to a unicast 

address, including those that were discarded or not sent. 

crocusInvMux/lanInterface/ifOutNUcastPkts 

This is the number of non-unicast packets that higher-level protocols requested to be transmitted to a 

non-unicast (i.e. a broadcast or multicast) address, including those that were discarded or not sent. 

crocusInvMux/lanInterface/ifOutDiscards 

This is the number of outgoing packets that were discarded, to prevent they were transmitted by the 

interface. This could be due to, for instance, the presence of an access list. 

crocusInvMux/lanInterface/ifOutErrors 

This is the number of outgoing packets that could not be transmitted by the interface because they 

contained errors. 

crocusInvMux/lanInterface/ifOutQLen 

This is the length of the output packet queue, expressed in packets, on the interface. 

All these attributes are SNMP MIB2 parameters. 




8.5 Link performance attributes 

crocusInvMux/link[ ]/errorCount 



crocusInvMux/link[ ]/lOSCount 

This attribute displays how many times a Loss Of Signal occurred since the last cold boot. 

crocusInvMux/link[ ]/lOSTime 

This attribute displays the total Loss Of Signal time since the last cold boot. 

crocusInvMux/link[ ]/lOFCount 

This attribute displays how many times a Loss Of Frame alignment occurred since the last cold boot. 

crocusInvMux/link[ ]/lOFTime 

This attribute displays the total Loss Of Frame alignment time since the last cold boot. 

crocusInvMux/link[ ]/aISCount 

This attribute displays how many times an Alarm Indication Signal occurred since the last cold boot. 

crocusInvMux/link[ ]/aISTime 

This attribute displays the total Alarm Indication Signal time since the last cold boot. 

crocusInvMux/link[ ]/bitErrorRate 

This attribute displays the bit error rate for the elapsed time since the last cold boot. 

crocusInvMux/link[ ]/errorAlarmCount 

This attribute displays the number of error alarms which was counted since the last cold boot. The alarms 

are counted during normal link state. 

crocusInvMux/link[ ]/errorAlarmTime 

This attribute displays the time during which an error alarm was active since the last cold boot. The time 

is measured during normal link state. 

crocusInvMux/link[ ]/errSeconds 

This attribute displays the number of seconds for which the summation of the CRC4 errors of the link is 

not zero. The seconds are counted during normal link state, and this since the last cold boot. 

errSeconds is also counted when the link is in unavailable state. This is not in conformity with G.826. 

crocusInvMux/link[ ]/sevErrSeconds 

This attribute displays the number of seconds for which the BER of the link is higher than 10 -4 . The 

seconds are counted during normal link state, and this since the last cold boot. 

sevErrSeconds is also counted when the link is in unavailable state. This is not in conformity with G.826. 




crocusInvMux/link[ ]/burstErrSeconds 

This attribute displays the number of seconds for which the BER of the link is between 10 -5 and 10 -4 . The 

seconds are counted during normal link state, and this since the last cold boot. 

crocusInvMux/link[ ]/unavailableCount 

This attribute displays the number of unavailability alarms which was counted since the last cold boot. 

The alarms are counted during normal link state. 

crocusInvMux/link[ ]/unavailableTime 

This attribute displays the time during which an unavailability alarm was active since the last cold boot. 

The time is measured during normal link state. 

crocusInvMux/link[ ]/h2Parameters 

This structured value displays the 2 hours performance summary related to the LOS, LOF and AIS 

alarms. The h2Parameters attributes are: 

Attribute 

sysUpTime 

lOSCount 

lOSTime 

lOFCount 

lOFTime 

aISCount 

aISTime 



how many times a Loss Of Signal occurred. 

the Loss Of Signal time. 

how many times a Loss Of Frame alignment occurred. 

the Loss Of Frame alignment time. 

how many times an Alarm Indication Signal occurred. 

the Alarm Indication Signal time. 

crocusInvMux/link[ ]/h2BitErrors 


h2BitErrors attributes are: 

Attributes 

sysUpTime 

bERMin 

bERMax 

bERAvrg 

alarmCount 

alarmTime 



the minimum bit error rate which was measured. 

the maximum bit error rate which was measured. 

the average bit error rate which was calculated. 

the number of bit error rate alarms which was counted. 

the time during which a bit error rate alarm was active. 




crocusInvMux/link[ ]/h2Performance 


h2Performance attributes are: 

Attribute 

sysUpTime 

errSeconds 

sevErrSeconds 






the number of erroneous seconds which was counted. 

the number of severely erroneous seconds which was counted. 

the number of error burst seconds which was counted. 

the number of unavailability alarms which was counted. 

the time during which an unavailability alarm was active. 

crocusInvMux/link[ ]/h24Parameters 

This structured value displays the 24 hours performance summary related to the LOS, LOF and AIS 

alarms. The h24LineParameters attributes are the same as the h2LineParameters attributes. 

crocusInvMux/link[ ]/h24BitErrors 


h24BitError attributes are the same as the h2BitError attributes. 

crocusInvMux/link[ ]/h24Performance 


h24Performance attributes are the same as the h2Performance attributes. 

crocusInvMux/link[ ]/Activate Test 

Use this action to perform a test on the Crocus Inverse Multiplexer. These tests are useful to trace 

possible problems. 

To execute a test, proceed as follows: 

Step 

Action 

1 In the TMA window, select the object link[ ] and the group Performance. 

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 action you want to execute. 


For more information on these tests, refer to Chapter 12 - Diagnostic tests. 




8.6 Operating system performance attributes 

crocusInvMux/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. 

crocusInvMux/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: 

Attribute 

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. 

crocusInvMux/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 parameter is the number of data buffers currently not in use and 

available for e.g. incoming data. 

crocusInvMux/operatingSystem/totalDataBuffers 

This is the total number of available data buffers. 

crocusInvMux/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. 

crocusInvMux/operatingSystem/freeBlockCount 

This is the number of free contiguous memory blocks. 

crocusInvMux/operatingSystem/freeMemory 

This is the total free memory expressed in bytes. 

crocusInvMux/operatingSystem/totalMemory 

This is the total RAM memory expressed in bytes. 




crocusInvMux/operatingSystem/taskInfo 

This attribute contains status information concerning the different tasks running on the processor. It is a 

table grouping up to 31 task slots, which is the maximum number of parallel tasks running on the 

processor’s operating system. 

This attribute contains the same information as taskInfo in the status group (refer to Section 7.7 - 

Operating system status attributes). 


Alarm attributes 


9. Alarm attributes 

This chapter discusses the alarm attributes of the Crocus Inverse Multiplexer. The following table gives 



9.1 Alarm attribute overview 129 

9.2 Introduction to the alarm attributes 130 

9.3 Crocus Inverse Multiplexer alarms 132 

9.4 LAN interface alarms 134 

9.5 DCE interface alarms 135 

9.6 Link alarms 136 




9.1 Alarm attribute overview 


totalAlarmLevel 

alarmInfo 

NotResponding 

AlarmSyncLoss 

StrapChanged 

LocalAccess 

TestActive 

SevErrSecond 

Unavailability 

ErrorsAlarm 

UnknownState 

ColdBoot 

WarmBoot 

Fallback 

ClockFailed 



alarmInfo 

LinkDown 

>> rs530, v35, v36, x21, router 

alarmInfo 

LinkDown 


alarmInfo 

LinkDown 

TestActive 

SevErrSecond 

LOSAlarm 

LOFAlarm 

AISAlarm 

ErrorsAlarm 




9.2 Introduction to the alarm attributes 

Before discussing the alarm attributes of the Crocus Inverse Multiplexer in detail, some general 

information on the alarm attributes of the Crocus Inverse Multiplexer is given. 

This section can be broken up into two parts: 

• First, the configuration alarm attributes are explained. 

• Secondly, the general alarm attributes such as totalAlarmLevel and alarmInfo are explained. 

Configuration alarm attributes 

The following four configuration alarm attributes are already explained in Chapter 6 - Configuration 

attributes, but are explained more thoroughly below. 

crocusInvMux/…/alarmMask 



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. 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 10 - TMA subsystem 

picture of the Crocus Inverse Multiplexer) 

it will not be shifted towards the value previousAlarms of the alarmInfo attribute (refer to Section 9.2 - 

Introduction to the alarm attributes). 

crocusInvMux/…/alarmLevel 

With this attribute, a priority level can be assigned to each alarm of the corresponding object. The alarm 

level range goes from 0 to 254, where 0 is the lowest and 254 is the highest priority level. 

The alarmLevel of an unmasked, active alarm is sent to the totalAlarmLevel of the top object crocusInvMux. 




General alarm attributes 

The general alarm attributes totalAlarmLevel and alarmInfo are explained below. 

crocusInvMux/totalAlarmLevel 

This attribute is only present in the top object of the containment tree of the Crocus Inverse Multiplexer, 

crocusInvMux. 

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. 

crocusInvMux/…/alarmInfo 

The alarmInfo contains the actual alarm information of the corresponding object. The alarmInfo attributes 

are: 

Attribute 

discriminator 

currentAlarms 

previousAlarms 

Displays for the corresponding object … 

the total alarm count since the last cold boot. 

the current alarms. 

the second most recent alarms. 

alarmMask the alarmMask as configured in the Configuration group. Refer to Chapter 6 - 

Configuration attributes. 

alarmLevel the alarmLevel as configured in the Configuration group. Refer to Chapter 6 - 

Configuration attributes. 




9.3 Crocus Inverse Multiplexer alarms 

Refer to Section 9.2 - Introduction to the alarm attributes for the general alarm attributes. 

crocusInvMux/alarmInfo 

The different alarms related to the object crocusInvMux 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 Inverse Multiplexer can not 

respond on the polling sessions of the Orchid 1003 

LAN. 

enabled 4 

AlarmSyncLoss when the internal alarm buffer overflows. enabled 4 

StrapChanged when the local configuration has been changed. disabled 1 

LocalAccess 

when TMA is connected locally via the auxiliary 

connector to the Crocus Inverse Multiplexer. 

disabled 1 

TestActive when a test is running on bonding level. disabled 0 

SevErrSecond 

Unavailability 

ErrorsAlarm 

UnknownState 

when during a one second period the bit error rate 

of the bonded links equals or exceeds 10 -4 . 

For each second the alarm condition is true, the 

alarm is activated. If a non-severely erroneous 

second occurs, the alarm is cleared. 

when a period of unavailable time is detected on 

bonding level. 

A period of unavailable time begins when the bit 

error rate in each second is worse than 10 -4 for a 

period of ten consecutive seconds. These ten 

seconds are considered to be unavailable time. 

A new period of available time begins with the first 

second of a period of ten consecutive seconds 

each of which has a bit error rate better than 10 -4 . 

when the bit error rate of the bonded links equals or 

exceeds the predefined value entered in onThreshold 

of the errorAlarmThreshold attribute. Refer to Section 

6.2 - Crocus Inverse Multiplexer configuration 

attributes. 

each time a new Crocus Inverse Multiplexer is 

added to the network, and before the Orchid 1003 

LAN has completed a first successful polling 

session. 

disabled 2 

disabled 2 

disabled 2 

disabled 0 




The alarm … 


Default value 

alarmMask 

alarmLevel 

ColdBoot 

WarmBoot 

Fallback 

each time the Crocus Inverse Multiplexer performs 

a cold boot. 

each time the Crocus Inverse Multiplexer performs 

a warm boot. 

when the Crocus Inverse Multiplexer operates in 

fall-back mode. 

disabled 1 

disabled 1 

disabled 2 

ClockFailed when the clocking mode you initially selected fails. disabled 1 




For more information, refer to Section 6.2 - Crocus Inverse Multiplexer configuration attributes 




9.4 LAN interface alarms 


crocusInvMux/lanInterface/alarmInfo 

The alarm related to the object lanInterface together with its explanation and its default alarmMask and 

alarmLevel value is given in the following table: 

The alarm … 


Default value 

alarmMask 

alarmLevel 

LinkDown 

when no valid LAN data is detected. I.e. the 

connection between the LAN and the interface is 

down. 

enabled 3 




9.5 DCE interface alarms 


crocusInvMux//alarmInfo 

The different alarms related to the object together with their explanation and their default 

alarmMask and alarmLevel value are given in the following table: 

The alarm … 


Default value 

alarmMask 

alarmLevel 

LinkDown 

(for RS530, V35 

and V36) 

LinkDown 

(for X21) 

LinkDown 

(for Router 

Interface 10M) 

when no RTS signal is detected. I.e. the connection 

between the Crocus Inverse Multiplexer and the 

DCE is down. 

The LinkDown alarm is only generated if the attribute 

rTSControl is set to external. If the attribute rTSControl 

is set to internal, the LinkDown alarm will never be 

generated. 

when no valid C signal is detected. I.e. the 

connection between the Crocus Inverse Multiplexer 

and the DCE is down. 

when there is no connection between the router 

and the Crocus Inverse Multiplexer. Because this 

connection is made by the interface connector, it is 

highly unlikely that this alarm will be generated. 

However, when it does occur it might indicate that 

the router interface is faulty. 

enabled 3 

enabled 3 

enabled 3 




9.6 Link alarms 


crocusInvMux/link[ ]/alarmInfo 

The different alarms related to the object link[ ] together with their explanation and their default alarmMask 

and alarmLevel value are given in the following table: 

The alarm … 


Default value 

alarmMask 

alarmLevel 

LinkDown 

when no data link towards the remote is present. 

It does not necessarily mean that the link is 

disconnected. If the link quality is so bad that data 

transfer is not possible, a LinkDown alarm is 

generated. 

enabled 3 

TestActive when a test is running on link level. disabled 1 

SevErrSecond 

when during a one second period the bit error rate 

of the link equals or exceeds 10 -4 . 

For each second the alarm condition is true, the 

alarm is activated. If a non-severely erroneous 

second occurs, the alarm is cleared. 

disabled 1 

LOSAlarm when the incoming E1 data is no longer present. disabled 1 

LOFAlarm 

AISAlarm 

ErrorsAlarm 

when the Frame Alignment Signal (FAS), which is 

present in time slot 0 of the incoming E1 data, is not 

detected after a certain period. 

when an Alarm Indication Signal is detected on the 

incoming E1 data. It means an error has been 

detected by a device along the transmission path. 

when the bit error rate of the link equals or exceeds 

the predefined value entered in onThreshold of the 

errorAlarmThreshold attribute. Refer to Section 6.5 - 

Link configuration attributes. 

disabled 1 

disabled 1 

disabled 1 



TMA subsystem picture of the Crocus Inverse Multiplexer 

10. TMA subsystem picture of the Crocus Inverse Multiplexer 

The subsystem picture is a TMA tool which visualises the status information of the Crocus Inverse 

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


10.1 Displaying the subsystem picture 138 

10.2 Structure of the subsystem picture 139 




10.1 Displaying the subsystem picture 

To display the subsystem picture of the Crocus Inverse Multiplexer, proceed as follows: 

Step 

Action 

1 Establish a link between TMA and the Crocus Inverse Multiplexer. Refer to Section 4.2 - 

Connecting to a Crocus Inverse Multiplexer with TMA. 

2 

In the TMA window, press on the subsystem picture button: . 

The subsystem picture is 

displayed: 

3 To close the subsystem picture, press . 




10.2 Structure of the subsystem picture 

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 Inverse Multiplexer subsystem picture is 

displayed. 

power LED 

LAN interface LEDs 

link LEDs 

DTE interface LEDs 

station clock connectors 

link connectors 

DTE interface connector 

TPI connector 

The table below gives an overview of the subsystem picture elements and what they indicate. 

Element 

LED indicators 

station clock 

connectors 

link connectors 

Description 

They reflect the actual status of the Crocus Inverse Multiplexer. The LED 

indication on the subsystem picture always corresponds with the LED indication 

on the Crocus Inverse Multiplexer itself. For more information on the 

interpretation of the LEDs, refer to Section 2.6 - Front panel LED indicators. 

If station clocking is selected, the station clock connectors reflect the status of 

the station clock signal. 

They reflect the status of the links. The possible indications are: 

Colour 

green 

red 

Explanation 

No alarm of the link[ ] object is active. 

An (unmasked) alarm of the link[ ] object is active. 

The colours of the link connectors only change if the alarms related to the link[ ] 

object are set to enabled in the alarmMask. Refer to Section 9.2 - Introduction to 

the alarm attributes. 

Example: 

If you want to avoid that the link connectors turn red when you activate a link 

test, set the alarm TestActive in the alarmMask of the link[ ] 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). 




Element 

DCE interface 

Description 

This reflects the status of the DCE interface. The possible indications are: 

Colour 

none 

green 

red 

Explanation 

If the DCE interface slot in the subsystem picture is blank, it 

means that no DCE interface module was present at power-up. 

No alarm of the object is active. 

An (unmasked) alarm of the object is active. 

The layout of the connector also gives an indication of the type of DCE interface 

which is currently used in the Crocus Inverse Multiplexer. 

The colours of the DCE interface only change if the alarms related to the 

object are set to enabled in the alarmMask. Refer to Section 6.4 - 

DCE interface configuration attributes. 

TPI connector 

This reflects the status of the LAN interface. 



Firmware download 

11. Firmware download 

This chapter explains how to download new firmware into the flash memory of the Crocus Inverse 

Multiplexer. The following table gives an overview of this chapter. 


11.1 Downloading with TMA 142 

11.2 Downloading with TML 143 

11.3 Downloading with TML in boot mode 144 

11.4 Downloading with TFTP 145 




11.1 Downloading with TMA 

To download firmware with TMA, proceed as follows: 

Step 

Action 

1 Establish a link between TMA and the Crocus Inverse Multiplexer either over a serial or 

an IP link. Refer to Section 4.2 - Connecting to a Crocus Inverse Multiplexer with TMA. 

2 In the TMA window select Tools ! Download… 

3 In case you made … 

• an IP connection, skip this step. 

• a serial connection, select the Options tab in 

the TMA – Download window. 

Here it is a good practice to 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 Inverse Multiplexer 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 (e.g. Txxxxxxx.00) 

2. Type CONTROL in the Remote file 

field. 

3. Press Open. 

6 If you are currently connected to the Crocus Inverse Multiplexer without write access, 

then you can enter a password which gives you write access in the Password tab. Else 

leave the Password tab blank. 

7 When the TMA – Download window reappears, 

press OK. 

⇒ A window opens and shows the download 

progress. 




11.2 Downloading with TML 

When downloading with TMA over a serial link, you actually evoke TML (Telindus Memory Loader) 

through TMA. You can also use TML without opening TMA. 

To download firmware 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 auxiliary connector of 

your Crocus Inverse Multiplexer 

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 firmware file you want to download in this directory. 

5 Type the following command: tml -c1 –v -f@CONTROLmy_pwd 

where … 

• tml is the executable (Telindus Memory Loader) to download files to the Telindus 

devices through their auxiliary port 

• -c1 specifies the COM port of the computer connected to the Crocus Inverse 

Multiplexer (in this example COM1) 

• -v returns graphical information on the download status 

• -f is the firmware file you want to download (e.g. T1212001.00) 

• CONTROL (in capitals!) specifies that the destination is a flash bank of the Crocus 

Inverse Multiplexer. 

• my_pwd is the write access password as configured in the Crocus Inverse 

Multiplexer. If no password has been configured, you may omit the and the 

password. 

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 firmware download begins. 

If you used the –v option together with the TML command, a graphical bar shows the 

download progress. 




11.3 Downloading with TML in boot mode 

When a flash memory software download has failed or when a flash memory error occurs, it may be 

possible that the Crocus Inverse Multiplexer becomes inaccessible to TMA. In that case, new software 

can still be downloaded by setting the Crocus Inverse Multiplexer in boot mode. This is done by means of 

the start-up mode DIP switch: 


start-up mode 3 on Start up from flash memory. 

off 

Start up in boot mode. 

The Crocus Inverse Multiplexer can be forced in boot mode by setting DIP switch bank DS1 position 1 to 

off. If a new software download is successfully completed, the DIP switch must be reset to on in order to 

restart operation from flash memory. 

To download firmware to a Crocus Inverse Multiplexer in boot mode, proceed as follows: 

Step 

Action 



2 Set DIP switch bank DS1 position 3 to off. 

To locate this DIP switch bank, refer to Section 3.1 - Location of the DIP switches. 

3 Replace the cover, without fastening the screws. Reconnect the external power supply 

to the Crocus Inverse Multiplexer. 

⇒ The Crocus Inverse Multiplexer is now in boot mode. 

4 Now proceed as explained in the previous section, Section 11.2 - Downloading with 

TML. 

5 When the download is finished, disconnect the Crocus Inverse Multiplexer from the 

power supply again. 

6 Reset DIP switch bank DS1 position 3 to on. 






11.4 Downloading with TFTP 

When downloading with TMA over an IP link, you actually evoke TFTP (Trivial File Transfer Protocol) 

through TMA. You can also use TFTP without opening TMA. 

To download firmware with TFTP, proceed as follows: 

Step 

Description 

1 Start a TFTP session on the Crocus Inverse Multiplexer. 

For example by typing tftp 10.0.11.1 at the command prompt of your UNIX station, 

where 10.0.11.1 is the LAN IP address of the Crocus Inverse Multiplexer. 

2 Set the following TFTP parameters: 

• Set the retransmission time-out to at least 20 seconds. 

The syntax is typically rexmt 20. 

• Set the total TFTP timeout sufficiently large (e.g. 40 seconds). 

The syntax is typically timeout 40. 

• Set the transfer mode to binary (octet) format. 

The syntax is typically binary or octet. 

3 Send the new firmware file to the Crocus Inverse Multiplexer. 

Example: 

tftp> put T1042018.00@CONTROLmy_pwd 

Where … 

• put is the TFTP command to send a file 

• T1042018.00 is the Crocus Inverse Multiplexer firmware file 

• CONTROL is the destination (flash memory) 

• my_pwd is the write access password as configured in the Crocus Inverse 

Multiplexer. If no password has been configured, you may omit the and the 

password. 

7 When the file transfer is finished, close the TFTP session. 


Diagnostic tests 


12. Diagnostic tests 

This chapter describes the diagnostic tests of the Crocus Inverse Multiplexer. The following table gives 



12.1 Introduction to the diagnostic tests 147 

12.2 Error test 148 

12.3 Local link loop-back test 149 

12.4 Reverse link / DCE loop-back test 150 

12.5 Remote DCE loop-back test 151 

12.6 DCE interface tests 152 




12.1 Introduction to the diagnostic tests 

Once installed and operational, the Crocus Inverse Multiplexer offer the network manager and/or the user 

the possibility to carry out diagnostic tests. They are a helpful tool to locate a problem, should one occur. 

Diagnostic test originators 

The following table shows the possible test originators and their priority level. 

Diagnostic tests can be generated by … 

TMA 

the DCE via the interface 

(RS530, V35 and V36 only) 

the remote Crocus Inverse Multiplexer 

(remote DCE loop-back) 

with the priority level … 

high. 

low. 

low. 

Within the same priority level the rule first come, first served applies. 

Note that TMA can inhibit all tests, disregarding the originator. 


The following table shows the test which can be executed on bonding and link level. 

Diagnostic tests on bonding level 

reverse DCE loop-back 

Diagnostic tests on link level 

reverse link loop-back 

remote DCE loop-back 

ET test 

ET test 

remote DCE loop-back + ET test 

local link loop-back + ET test 

local link loop-back + ET test 

local link loop-back 




12.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 in the status and performance attribute errorCount of the crocusInvMux and link[ ] object. 

Injecting a test pattern on link level will cause a Loss Of Frame alignment. 

How to use this test 

Example: 

Phase 

Description 

1 Start an ET test on bonding or link level on the local Crocus Inverse Multiplexer. 

⇒ A test pattern is sent down the link. 

2 Start an ET test on bonding or link level on the remote Crocus Inverse Multiplexer. 

⇒ The detector of the remote Crocus Inverse Multiplexer receives this test pattern, and 

looks for possible errors in the pattern. The quantity of errors could be an indication of 

the link quality. 

The following figure shows the different ET tests: 

local 

remote 

ET 

ET 

ET test on bonding level 

local 

remote 

ET 

ET 

ET test on link level 




12.3 Local link loop-back test 

Initiating a local link loop-back test establishes a loop just before the links. I.e. the data is looped back 

before it can enter the links. 

During the execution of a local link loop-back test, no normal data communication is possible. In order to 

avoid that this test would stay active for an indefinite time, and thus disturbing the normal data transfer, a 

testDuration attribute is linked with the test (refer to Section 6.2 - Crocus Inverse Multiplexer configuration 

attributes). This attribute determines how long a test lasts. 


Example: 

Phase 

Description 

1 Start a local link loop-back test on the local Crocus Inverse Multiplexer. 

⇒ A local link loop-back is established on the local Crocus Inverse Multiplexer. 

2 Send data with the DCE. 

⇒ If this data is received again by the DCE, it indicates the connection between the DCE 

and the Crocus Inverse Multiplexer is OK. If this data is not received again by the DCE, it 

is possible that there is a bad connection between the DCE and the Crocus Inverse 


In combination with the ET test, the local link loop-back test can also be used as a self-test of the Crocus 

Inverse Multiplexer. 

The following figure shows the different local link loop-back tests: 

local 

remote 

local link loop-back on bonding level 

or 

interface test I141 (AL) 

local 

remote 

ET 

local link loop-back + ET test on bonding level 

local 

remote 

ET 

local link loop-back + ET test on link level 

Note that an AL interface test (I141) has the same effect as a local link loop-back on bonding level test. 




12.4 Reverse link / DCE loop-back test 

There are two different reverse loop-back tests: 

• a reverse link loop-back test. Initiating this test establishes a loop just after the links. I.e. the data is 

looped back on the links before it can enter the Crocus Inverse Multiplexer. 

• a reverse DCE loop-back test. Initiating this test establishes a loop just after the DCE interface. I.e. the 

data is looped back before it can enter the DCE. 


Example: 

Phase 

Description 

1 Start a reverse DCE loop-back test on the local Crocus Inverse Multiplexer. 

⇒ A reverse DCE loop-back is established on the local Crocus Inverse Multiplexer. 

2 Start an ET test on the remote Crocus Inverse Multiplexer. 

⇒ A test pattern is sent down the link. 

3 Because the local Crocus Inverse Multiplexer is in a reverse DCE loop-back, the test 

pattern returns to the remote Crocus Inverse Multiplexer. 

4 The remote Crocus Inverse Multiplexer its 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 quality of the data path. 

The following figure shows reverse link and DCE loop-back test: 

local 

remote 

reverse link loop-back on link level 

local 

remote 

reverse DTE loop-back 




12.5 Remote DCE loop-back test 

Initiating a remote DCE loop-back test establishes a loop just after the DCE interface of the remote 

Crocus Inverse Multiplexer. I.e. the data is looped back before it can enter the remote DCE. 

Before you can initiate a remote DCE loop-back test on a remote Crocus Inverse Multiplexer, it has to 

allow this test. You can change this with the attribute remoteDTELoopbackDetect (refer to Section 6.2 - 

Crocus Inverse Multiplexer configuration attributes). 


With this test, you can verify the same things as with the remote digital loop (refer to Section 12.4 - 

Reverse link / DCE loop-back test). The only difference is that the loop is not made on the local Crocus 

Inverse Multiplexer (as with a reverse DCE loop-back test), but on the remote Crocus Inverse Multiplexer. 

The following figure shows the different remote DCE loop-back tests: 

local 

remote 

remote DTE loop-back 

local 

remote 

ET 

remote DTE loop-back + ET test 

Note that an RDL interface test (I140) has the same effect as a remote DCE loop-back test. 




12.6 DCE interface tests 

If you use the RS530, V35 and V36 DCE interfaces it is possible that the DCE initiates a test on the 

Crocus Inverse Multiplexer via the DCE interface. This because the circuits I140 and I141 are present on 

these interfaces. 

The following interface tests are available: 

• interface RDL. This is a Remote Digital Loop (circuit I140), the equivalent of a remote DCE loop-back 

test. Refer to Section 12.5 - Remote DCE loop-back test. 

• interface AL. This is a Analogue Loop (circuit 141), the equivalent of a local link loop-back test on 

bonding level. Refer to Section 12.3 - Local link loop-back test. 

The DCE interface tests can be individually enabled or disabled using the tests attribute. Refer to Section 

6.4.2 - RS530, V35 and V36 interface configuration attributes. 

A DCE interface test is activated on all enabled links and interrupts the user data. A link test is only 

activated on an individual link. The user data is redistributed on the links which are not under test. 



Technical specifications 

13. Technical specifications 

This chapter gives the technical specifications of the Crocus Inverse Multiplexer. The following table 



13.1 Inverse multiplexing 154 

13.2 E1 link interface 154 

13.3 Station clock interface 155 

13.4 DCE interface 155 

13.5 LAN interface 155 

13.6 Console port 156 

13.7 Power requirements 157 

13.8 Mechanical dimensions 157 

13.9 Environmental requirements 157 




13.1 Inverse multiplexing 

The inverse multiplexing characteristics are as follows: 

Parameter 

Description 

number of E1 links 4 

maximum delay variance between the links 

64 ms 

throughput delay 50 µs 

13.2 E1 link interface 

The E1 link interface characteristics are as follows: 

Parameter 

Description 

applicable standards CCITT Recommendation G.703, G.704, G.732 

connectors 

balanced interface: 8 pins RJ45 female connector 

unbalanced interface: 2 BNC coaxial connectors 

impedance 

(software selectable) 

nominal line speed 

balanced interface: 120 Ohm 

unbalanced interface: 75 Ohm 

2048 kbps 

transmit level balanced interface: ± 3V ± 10% 

unbalanced interface: ± 2.7V ± 10% 

receiver sensitivity 

line code 

framing 

0 to -10 dB 

AMI 

with CRC4: 

• time slot 0 multi-frame for CRC4 protection 

• no multi-frame (G.732N) intended for use with CCS 

without CRC4: no multi-frame (G.732N) intended for use with CCS 

jitter performance CCITT Recommendation G.823 




13.3 Station clock interface 

The station clock interface characteristics are as follows: 

connectors 

Parameter 

Description 

balanced interface: 8 pins RJ45 female connector 

unbalanced interface: 2 BNC coaxial connectors 

impedance 

(software selectable) 

nominal frequency 

line code 

balanced interface: 120 Ohm 

unbalanced interface: 75 Ohm 

2048 kHz (± 100 ppm) 

AMI 

13.4 DCE interface 

The DCE interface characteristics are as follows: 

data rate 

Parameter 

Description 

1952, 3904, 5856, 7808 kbps depending on the number of E1 links in use. 

automatic fall-back to next lower rate when an E1 link fails. 

timing modes 

DCE: transmit and receive clocks supplied by the application 

DCE: 

• receive and transmit clock supplied to the application 

• external transmit clock accepted from the application 

13.5 LAN interface 

The LAN interface characteristics are as follows: 

Parameter 

Description 

connector 

operation 

8-pins RJ45 female connector 

10BaseT Ethernet 




13.6 Console port 

The console port (sometimes also called control port or auxiliary connector) is a 9 pins subD connector 

with the following pin layout: 

Pin Signal DCE Figure 

1 - - 

2 NMS RxD output 

3 NMS TxD input 

4 not used - 

5 GND - 

6 not used - 

7 NMS RTS input 

8 NMS CTS output 

9 - - 

1 

2 

3 

4 

5 

6 

7 

8 

9 

Note: 

• 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 Crocus Inverse Multiplexer with the Orchid 1003 LAN 

management concentrator can be ordered at the distributor (code 149.220). 




13.7 Power requirements 

The power requirements are as follows: 

Parameter 

supply voltage 

Description 

100 – 240 Vac nominal (90 ! 246 Vac), 47 – 63 Hz 

24 – 48 Vdc nominal (20 ! 70 Vdc) 

power consumption 

25 Watts maximum 

13.8 Mechanical dimensions 

The mechanical dimensions are as follows: 

Dimensions Desktop model Rackmount model 

height (mm) 50 43 

width (mm) 430 482 

depth (mm) 270 270 

weight (kg) 4.3 4.6 

13.9 Environmental requirements 

The environmental requirements are as follows: 

Parameter 

Description 

ambient operational temperature 0°C to 50°C 

storage temperature 

maximum altitude 

relative humidity 

statutory requirement 

safety regulations 

-25°C to +70°C 

3000 m 

0% to 95% non-condensing 

EN60950, class I equipment 

EN55022B, IEC 1000-4-2, IEC 1000-4-3, IEC1000-4-4 

EN60950, class I equipment 

EN41003 


Fuse replacement 


14. Fuse replacement 

This chapter gives a fuse replacement procedure for the Crocus Inverse Multiplexer. 

FUSE REPLACEMENT 

For continued protection against the possibility of fire, replace fuses only with the specified voltage, 

current and type ratings. 

The figure below shows the position of the fuses on the Crocus Inverse Multiplexer motherboard: 

F1 

To replace a fuse on the Crocus Inverse Multiplexer, proceed as follows: 

Step 

Action 



2 Locate the blown fuse on the power module PCB and remove it. 

3 Verify the specifications of the fuse about to be replaced. 

The fuse value of the Crocus Inverse Multiplexer is: 

F1: 250V T3.15A 

4 Place the new fuse. 





Annexes 

Annexes 159


160 Annexes


Annex A: product information 

Annex A: product information 

The following table displays the product information of the Crocus Inverse Multiplexer basic units. 

Sales code Product name Description 

153862 CROCUS 4E1 INV MUX BU 230VAC Crocus Inverse Multiplexer allows transmission of transparent 

synchronous data up to 8 Mbps over up to 4 E1 lines using an 

efficient bonding mechanism. Basic Unit, no interfaces 

provided. Interface module available as separate sales items. 

230 / 115 Vac 

156363 CROCUS 4E1 INV MUX BU 48VDC Crocus Inverse Multiplexer allows transmission of transparent 

synchronous data up to 8 Mbps over up to 4 E1 lines using an 

efficient bonding mechanism. Basic Unit, no interfaces 

provided. Interface module available as separate sales items. 

48 Vdc 

The following table displays the product information of the Crocus Inverse Multiplexer DCE interfaces. 

Sales code Product name Description 

143666 V35 INTF. CROCUS Plug-in modular interface V.35 transparent. Suitable for Crocus 

HS / SDSL-F/ HDSL / HDSL-F / FO10M / INV-MUX. 

142199 V36 INTF.CROCUS Plug-in modular interface V.36 transparent. Suitable for Crocus 


142200 X21 INTF.CROCUS Plug-in modular interface X.21 transparent. Suitable for Crocus 


161611 RS-530 INTF.CROCUS Plug-in modular interface RS-530 for Crocus HS / SDSL-F/ 

HDSL / HDSL-F / FO10M / INV-MUX. 

177455 ROUTER INTF.10M CROCUS Plug-in modular IP router / bridge interface. 10/100Mbit/s autosense 

Ethernet interface & VLAN interconnect support. 

Encapsulation ATM, Frame Relay and PPP. 10Mbit/s serial 

throughput. 

Annexes 161

Crocus Inverse Multiplexer - Route 66 Communications

Create successful ePaper yourself

Delete template?

Save as template?