cfm-m m4-mux_td_en_v 2 1

CFM-M-MUX / CFM-M4-MUX Indoor Units

Indoor Unit Management System Technical Description and Configuration

Guide

© SAF Tehnika A/S 2009

Table of Contents

1 CFM Multiplexer Indoor Unit Overview..................................................... 4 2 Indoor Unit Appearance ........................................................................ 5

2.1 Installation Notes ........................................................................... 5 2.2 Ports ............................................................................................ 6 2.3 LEDs............................................................................................. 7 2.4 Interface Modules........................................................................... 8

2.4.1 V.35 Interface Module ................................................................. 8 2.4.2 E1 Interface Module .................................................................... 8 2.4.3 4xE1 Interface Module................................................................. 9 2.4.4 100Base-T Ethernet Bridge Modules ............................................ 10 2.4.5 E3 Interface modules (only for CFM-M-MUX with FEC).................... 12

2.5 FEC Coding (only for CFM-M-MUX with FEC) ..................................... 12 2.6 Labelling ..................................................................................... 13

3 Configuration and Management............................................................ 14 3.1 LCD/Keypad ................................................................................ 14

3.1.1 “Status Display” Mode of the IDU LCD Management Interface ......... 14 3.1.2 “Setup” Mode of IDU LCD Management Interface .......................... 15 3.1.3 Interface Module LEDs............................................................... 19

3.2 Resetting the IDU......................................................................... 20 3.3 RS-232 Serial Management Port ..................................................... 20 3.4 Ethernet Port ............................................................................... 22

3.4.1 Web Management..................................................................... 23 3.4.2 Telnet management .................................................................. 26 3.4.3 SNMP Management ................................................................... 26

3.5 Command Interface ...................................................................... 27 3.5.1 Working with configuration script ................................................ 37 3.5.2 File system .............................................................................. 37 3.5.3 Storage of radio parameters....................................................... 39 3.5.4 Security commands .................................................................. 39

3.6 Updating management software ..................................................... 40 3.6.1 Uploading file via Ethernet management port (TFTP) ..................... 41 3.6.2 Uploading file via Ethernet management port (FTP) ....................... 42 3.6.3 Uploading file via serial port (Xmodem) ....................................... 42

3.7 Alarms........................................................................................ 43 3.7.1 Alarm (I/O) port (DB-25 connector) ............................................ 44 3.7.2 E1 module alarms..................................................................... 44

3.8 Configuring Management Service Channel........................................ 47 3.9 Algorithm of LCD Operation ........................................................... 53 3.10 Replacing the Indoor Unit .............................................................. 53 3.11 Default Settings ........................................................................... 54 3.12 Automatic Transmit Power Control (ATPC)........................................ 55

3.12.1 ATPC Algorithm ........................................................................ 55 3.12.2 ATPC commands....................................................................... 55

3.13 Configuring Radio Parameters ........................................................ 56 3.13.1 Default ODU Settings ................................................................ 56 3.13.2 Configuring Tx Frequency .......................................................... 56 3.13.3 Configuring Tx Power ................................................................ 56 3.13.4 Evaluating RSL from RSSI signal................................................. 56

3.14 Performing Loop-back Tests ........................................................... 57 3.14.1 Setting Loop Tests from IDU LCD/Keypad .................................... 57 3.14.2 Setting Loop Tests from Telnet/serial terminal .............................. 58 3.14.3 Radio loopback......................................................................... 58 3.14.4 Base-band loopbacks ................................................................ 58

3.14.5 V.35 Interface Module Loopback ................................................. 59 3.14.6 E1 Interface Module Loopbacks................................................... 59

4 1+1 Configuration.............................................................................. 61 4.1 1+1 Protection Modes ................................................................... 62

4.1.1 FD (Frequency diversity)............................................................ 62 4.1.2 HSB (Hot-standby) ................................................................... 62

4.2 Traffic switching ........................................................................... 62 4.3 Switching time ............................................................................. 63 4.4 E1 traffic switching ....................................................................... 63 4.5 Ethernet traffic switching............................................................... 63 4.6 V.35 traffic switching .................................................................... 64 4.7 Management Ethernet traffic switching ............................................ 64 4.8 Ethernet traffic switching............................................................... 64 4.9 Commands for Telnet/serial terminal............................................... 64 4.10 IP configuration for 1+1 link .......................................................... 64 4.11 Hardware Installation.................................................................... 65 4.12 Replacing faulty 1+1 CFM-M-MUX IDU............................................. 65

5 Pinouts............................................................................................. 66 5.1 Management port pinouts .............................................................. 66

5.1.1 RS232..................................................................................... 66 5.1.2 Ethernet.................................................................................. 66

5.2 Alarm interface (I/O Port) pinouts................................................... 66 5.2.1 Alarm port specification for CFM-M-MUX (1+0) (DB-25 connector)... 66 5.2.2 Alarm port specification for CFM-M-MUX (1+1) (DB-44 connector)... 67

5.3 Traffic port pinouts ....................................................................... 68 5.3.1 V.35 traffic port pinouts............................................................. 68 5.3.2 E1 port pinouts ........................................................................ 68

6 Mechanical data................................................................................. 70 7 SAF Tehnika A/S Contacts ................................................................... 71 8 References........................................................................................ 72

The CFM-M-MUX/CFM-M4-MUX IDU Management System Technical Description and Configuration Guide Rev. 2.1 © SAF Tehnika A/S 2009

4

1 CFM Multiplexer Indoor Unit Overview

Proprietary notice

The specifications or information contained in this document are subject to change without notice due to continuing introduction of design improvements. If there is any conflict between this document and compliance statements, the latter will supersede this document.

This document describes the CFM modular multiplexer Indoor Unit, CFM-M-MUX and CFM-M4-MUX, covering hardware features, built-in management system, configuration functionality, etc.

The CFM series multiplexer IDUs are parts of SAF Tehnika’s CFM series digital microwave radio product family. The multiplexer IDUs provide:

- Means of interconnecting the user equipment with the Radio (ODU) at each site of the 1+0 (unprotected) radiolink; The CFM-M-MUX Indoor Unit is intended for use with the CFM-LM radios; the maximum WAN capacity of the CFM-M-MUX (without FEC) is 34.368 Mbps.

The CFM-M4-MUX Indoor Unit is intended for use with the CFM-L4 radios; the maximum WAN capacity of the CFM-M4-MUX IDU is 4 Mbps.

Note: 1+1 solution is described in chapter 4.

The modularity of the CFM-M-MUX IDU allows to install various CFM series traffic interface modules, which include 1xE1; 4xE1; E3 (only with FEC version); V.35 and 10/100Base-T interfaces (for more information please refer to chapter 2.4).

- Local and remote management (incl. Web, Telnet, SNMP, serial console).

- TCP/IP service channel between sites over the radiolink.

- Alarm interface (optional).

The CFM-M-MUX IDU supports various link capacities: 8 Mbps, 16 Mbps and 34 Mbps; the CFM-M4-MUX IDU operates with 2 Mbps or 4 Mbps speeds. The capacity is software selectable. Any capacity can be selected for any frequency band.

The CFM-M-MUX IDU supports 1+0 and 1+1 link configurations, CFM-M4-MUX IDU supports 1+0 configuration only. CFM-M-MUX 1+1 link configuration is available only with 1+1 I/O port (DB-44 connector).

The IDU is frequency-independent; the operating frequency is determined by the ODU only.

Revision history

Revision Date Comments

1.0 January, 2005

1.1 February, 2005

1.2 June, 2005 For M-MUX SW ver. 4.09 (2005.05.31)

1.3 September, 2005 Chapter “Labeling” revised

1.4 October 6, 2005 Information about 1-port 100Base-T interface module added

1.5 January 24, 2006 Information about SNMP traps added; command ‘beralarmlevel’ added

1.6 February 24, 2006 Information about M-MUX 1+1 configuration added

1.7 March 15, 2006 Chapters 3, 4, 5 revised.

1.8 June 13, 2006 Chapters 3.5, 3.8 revised due to IDU software release, version 4.20.

1.9 September 13, 2006 Information about CFM-M4-MUX and 1+1 I/O port added

2.0 November 6, 2006 Information about ATPC function added

2.1 February 17, 2009 Miscellaneous corrections made


5

2 Indoor Unit Appearance

2.1 Installation Notes

The CFM-M, M4 IDUs are 19” wide, rack mountable 1U high units, aluminium chassis, the depth of the unit is 230 mm without front panel handles and 270 mm with handles. Some space should be reserved for interface cables in front of the IDU and RF cable behind the IDU, see Figure 2.1.

8 cm10 cm

V.35 E1

4 cm

23 cm(9.10 ")

(3.15 ")(3.94 ")(1.57 ")

(16.93 ")42.6 cm

(19.29 ")48.6 cm

12 cm(4.72 ")

Figure 2.1

The CFM-M-MUX IDU provides four sockets – module slots, for installation of interface modules. The CFM-M4-MUX IDU provides two sockets for installation of interface modules. For information about what data rate each multiplexer slot supports, please see Table 3.2 in chapter 3.1.2.

The CFM-M-MUX IDU contains:

- Multiplexer board;

- Management controller board;

- Power Supply module;

- LCD and Keypad module;

- Traffic interface modules.

All the aforementioned boards and modules are interconnected with flat ribbon cables and snap-on connectors.

- 48V + CFM-M-MUXCLEAR

ENTER

OUT INE1

TX AIS

LB RX

TX

V.35

SYNC

RADIO

REMOTE

ALARM

SL

LB RX

Figure 2.2. The CFM-M-MUX IDU, equipped with, E1 and V.35 interface modules (front

panel)

The numbering of multiplexer module slots is depicted in the following picture.

- 48V +SYNC

RADIO

CLEAR

ENTER Slot 1 Slot 2 Slot 3 Slot 4REMOTE

ALARM

Figure 2.3. Numbering of module slots


6

2.2 Ports

The IDU provides:

- Interfaces:

- Radio Unit (ODU), N-type Female connector;

- The M-MUX IDU provides 1 up to 4 slots for traffic port modules (1 module per slot), the CFM-M4-MUX provides two traffic module slots; for information about modules see chapter 2.4;

- RS-232 serial management port;

- 10\100Base-T Ethernet management ports.

- DB-25 female connector (optional) shares the following ports:

- Alarm port, for more information please refer to chapter 3.7.1.

- Four user input ports, for more information please refer to chapter 3.7.1.

- DB-44 HD female connector (optional) shares the following ports :

- Alarm port, for more information please refer to chapter 3.7.1.

- Four user input ports, for more information please refer to chapter 3.7.1.

- 1+1 I/O port, for more information see chapter 4.

- LCD display and keypad buttons on the front panel of the IDU, to configure and monitor the CFM site;

- Port activity LEDs;

- Power connector.

Table 2.1. Connectors

Port/connector Front panel connectors

+-48V (power socket)

Power connector, IDU should be powered from 20V – 60V DC power source. Both “+” or “–” poles of the power source could be grounded, one should make sure if the chosen grounding wire is connected to ground on IDU power connector.

Port/connector Rear panel connectors

RF (N-type connector)

N-type Female connector, the cable should be connected to the Radio Unit (ODU);

RS-232 (DB-9 connector)

RS232 management port for connection of serial console (or analog line modem for the remote connection of serial console). This port is also used to update management software.

2x10\100Base-T Ethernet ports (RJ-45 socket)

Ethernet switch management ports, for Web or Telnet management; the ports have bridging function. The ports are numbered from left to right when facing the IDU rear panel, thus port 1 is located next to serial management port and port 2 – next to port 1.

DB-25 connector Alarm port. This feature is optional.

DB-44 connector I/O (alarm) port for 1+1 configuration. This feature is optional.


7

2.3 LEDs

Table 2.2. Front panel LEDs Label Color Description

Sync Red Red Signal Lost LED indicates the loss of Multiplexer synchronization; If not lit – operating properly;

The SL LED is updated one time per second.

Radio Red Radio Alarm LED indicates problems with radio unit and IDU-ODU cable.

The following problems cause the Radio Alarm to turn on: − Rx signal level is lower the predefined value, - the

corresponding parameter is RxAlarmLev on the LCD or RxAlarmLevel using Telnet/serial console. For more details refer to Chapter 3.11;

− The humidity within the radio is too high (possibly ODU is opened);

− Transmitter malfunction (TxOut=Error) − RF Cable=Short – cable is faulty, RF Cable=Off – cable or

Radio is faulty; − Tx and Rx synthesizer loops are not locked (TxPLL=Error,

RxPLL=Error)

If not lit – operating properly (Rx=OK & TxOut=OK & Humidity=Low & RF Cable – OK & TxPLL=OK & RxPLL=OK).

The RA LED is updated one time per second.

(!) The RA LED will also switch on if the Radio loopback is active and/or if the transmitter power is switched off.

Remote Red Remote Alarm Indicator (RAI alarm), - indicates that the far-end site has the SL alarm switched on.

Alarm Yellow BER alarm (YELLOW) – indicates that the BER is equal or higher the BER level, specified with BerAlarmLevel command from Telnet or serial terminal. The BER margin can be changed form Telnet or serial console, for information see chapter 3.5.

(!) The LEDs located on interface modules are described in Chapter 3.1.3.

Table 2.3.

Other front panel LED signals

Alarm Description

Wrong Capacity

In case if due to wrong MUX slot speed configuration

− the WAN capacity is lower than sum of MUX slot speeds (LAN speed higher than WAN speed), or

− one or more MUX slot speed settings does not support the selected WAN capacity (for example, slot 1 configured with RMN capacity while WAN capacity is 16 Mbps).

SYNC, RADIO, REMOTE and ALARM LEDs switch on and off alternatively in the following combination:

(RADIO, REMOTE) <-> (SYNC, ALARM)

IDU HARDWARE

If IDU hardware failure occurs, SYNC, RADIO, REMOTE and ALARM LEDs simultaneously will be switching on and off.


8

FAILURE

Rear panel LEDs and connectors are shown in Figure 2.4.

Ethernet link\activityLED

100 Mbps speedLED

Hidden resetbutton

Ethernetmanagement ports

ODUportSerial management

port

Indicates operation of themanagement module CPU

Groundingscrew

Figure 2.4. Rear panel LEDs and connectors

2.4 Interface Modules

2.4.1 V.35 Interface Module

The V.35 interface module is provided with M34 standard connector. The V.35 module terminates 2, 4, 6, or 8 Mbps from modular multiplexer (from modular Ethernet bridge multiplexer only 2 Mbps) and provides user selectable data rates of 64 kbps, 128 kbps, 256 kbps, 512 kbps, 1024 kbps, 2048 kbps, 4096 kbps, 6144 kbps or 8192 kbps to V.35 interface port on M34 connector.

If multiplexer slot capacity is set to 2 Mbps, the V.35 module also supports fractional E1 mode, - up to thirty one 64 kbps channels can be selected from E1 stream from WAN side (timeslots 2. – 32. in PCM31 mode).

For description of V.35 interface module LEDs, see Table 3.3.

Figure 2.5. V.35 module (front)

2.4.2 E1 Interface Module

The E1 interface module is a single port module provided with two types of interfaces:

• 120 Ω balanced interface, connector type: RJ-45;

• 75 Ω unbalanced interface, connector type: BNC, - requires a pair of coaxial cables with BNC type connectors.

Both interfaces are provided for termination of 2 Mbps (G.703) streams.


9

Table 2.4. E1 Interface module ports

Out, In

Two BNC connectors of the 75 Ω unbalanced port provide means to connect the customer equipment to the IDU;

Tx data stream is transmitted over OUT (output) port;

Rx data is to be received through IN (input) port.

RJ-45 RJ-45 connector for balanced 120 Ω E1 interface.

Table 2.5. 1xE1 module LEDs

Label Color Description

Tx Green Steady green light indicates the E1 module is ready to transmit data to CPE connected to E1 port.

In case if Multiplexer synchronization is lost (S.L. LED is lit), Tx LED goes off and AIS signal is transmitted from E1 port to user equipment.

Rx Green Steady green light indicates the data signal from E1 input.

AIS Red Steady red LED indicates the AIS signal from E1 input.

LB Red “Loopback” LED (red) indicates loopback mode is activated in the module.

OUT INE1

TX AIS

LB RX

Figure 2.6. 1xE1 module (front)

2.4.3 4xE1 Interface Module

The 4xE1 module provides four E1 ports with RJ-45 connectors (120 Ω balanced interfaces) or with DB-25 connector (120 Ω balanced or 75 Ω unbalanced interface); the ports can be separately switched on/off, the speed of the module changes according to the following table:

Active E1 ports Module speed

4 (all ports active) 8 Mbps

3 6 Mbps

2 4 Mbps

1 2 Mbps

0 0 Mbps

(!) Use either IDU keypad or console to switch between BNC and RJ-45 ports. This operations are described in chapters 3.1.2 and 3.5, respectively.


10

Each port has two LEDs indicating operations status of the port:

• One of both LEDs for each port is loop-back LED, it has yellow colour; if loop-back is set for the port, the LED is switched on; if switched off, no loop-back is active.

• Other LED indicates transmission status of the port and has either green or red colour; for details see Table 2.6.

Table 2.6. Description of RJ-45 connector interface LEDs

E1 port LED (highlighted)

Color Description

Green (loop-back LED yellow or off)

Indicates normal operation of the channel, no problems with signal reception.

Red (loop-back LED yellow or off)

Constant red indicates that E1 signal is lost. If red flashes momentarily, the bipolar violation (line code error) was received from user equipment.

Blinking green and red (loop-back LED yellow or off)

AIS signal is being received from user equipment.

Yellow loop-back LED (loop-back switched on)

When loopback LED is switched on, analog, digital or remote loop-back mode is active for that channel.

No LED is lit Channel is switched off.

(1) (2)

2 4E1

1 3

Figure 2.7. 4xE1 modules: (1) with DB-25 port; (2) with RJ-45 ports

2.4.4 100Base-T Ethernet Bridge Modules

The 1-port FREB module and low capacity 2-port REB module (FREB - Fast Remote Ethernet Bridge) performs bridging between LAN ports and WAN port, and between both LAN ports.

The 1-port module terminates any capacity up to 34 Mbps from the multiplexer on 100Base-T ports (RJ-45 sockets); 1-port module has one 100-Base-T port;

The 2-port module terminates any capacity up to 12 Mbps from the multiplexer on 100Base-T ports (RJ-45 sockets); 2-port module has two 100-Base-T ports.

Feature summary:


11

1-port 100Base-T Fast Ethernet Bridge Module

Low capacity 2-port 100Base-T Ethernet Bridge Module

• 10M/100M Half/Full duplex auto-detect

• TP auto MDIX TX/RX swap

• 10.000 or (optionally unlimited) MAC addresses table

• Store and forward architecture

• Aging function

• Supports up to 1760 (optionally up to 2000) byte packets

• Supports 802.1Q VLAN;

• Optional support for 1+1 protection.

• 10M/100M Half/Full duplex auto-detect

• TP auto MDIX TX/RX swap

• 2048 MAC addresses table

• Store and forward architecture

• Aging function

• Supports up to 1522 byte packets

• Supports 802.1Q VLAN.

For more information about 1-port module throughput, see Table 2.7.

Table 2.7. 1-port 100Base-T Ethernet module throughput for various frame sizes

Frame Size, Total Throughput,

[bytes] [Mbit/sec] 64 30.260

128 31.722

256 32.549

512 33.161

1024 33.522

1280 34.017

1518 34.210

1600 34.291

The maximum available WAN traffic capacity of the bridge is possible if 1-port module is used in slot 1 of the CFM-M-MUX IDU, and slot 1 is configured as ‘RMN’; following this, the maximum WAN traffic capacity (payload) is 34.21 Mbps (total capacities including service channel, framing, etc. are 34.368 Mbps, 16.384 Mbps, 8.192 Mbps, 4.096 Mbps).

100 Mbps speed LED(yellow), -if this LED is switched on,the port speed is 100 Mbps

Ethernet link/activity LED(green), if flickers, indicatesdata transmission,

Figure 2.8. 2-port FREB module LEDs


12

100Base-T modules comply with:

• IEEE Std. 802.1D Media Access Control (MAC) Bridging capabilities (without the spanning tree algorithm),

• IEEE Std.802.1Q (without prioritization),

• IEEE 802.3.

2.4.5 E3 Interface modules (only for CFM-M-MUX with FEC)

The E3 interface module is a single port module provided with 75 ohm unbalanced interface (G.703) with BNC connectors. The E3 interface module is compatible with M-MUX with FEC (software version 5.xx).

Table 2.8 E3 module LEDs


LOS Red Steady red light indicates the loss of incoming E3 signals.

LB Yellow “Loopback” LED (yellow) indicates loopback mode is activated in the module.

Figure 2.9 E3 Interface module

2.5 FEC Coding (only for CFM-M-MUX with FEC)

The CFM-M-MUX IDUs with FEC use RS (255, 223) FEC (Forward Error Correction) coding (Reed Solomon algorithm). The CFM-M-MUX with FEC can operate in one of three modes:

- as normal 34 Mbps M-MUX IDU;

- in a mode that improves receiver sensitivity by 4 dB;

- Or with an increased data rate, which enables to use E3 module + 1xE1 module.

For IDUs with FEC the available service channel is 160 kbps.

Maximum bandwidth of the Ethernet interface module in Slot 1 is 36.1 Mbps. The available Ethernet interface module bandwidth in Slots 2, 3, 4 is from 0 Mbps to 18, 12 and 8 Mbps respectively with a step of 2 Mbps.

The E1 and 4xE1 interface modules can be used only in Slots 2, 3, 4.

The FEC feature is available for M-MUX IDUs with software versions 5.xx.


13

2.6 Labelling

The IDU label is found at the rear panel.

The IDU and ODU label contains the following information:

− Product model name. − Product number (P/N): product number contains information of subband (A, B or C)

and band side (L, H). − Serial number (S/N); the Serial Number has the following information:

− 4-digit product code,

− Consecutive number of the product; the 5-digit consecutive numbering for IDU label is separate for each IDU type (e.g. MUX IDU, REB IDU, E1 IDU, etc.), for ODU label – separate for each frequency band.

− Product type and hardware version.

The Serial Number uniquely identifies the unit (IDU or ODU).

Figure 2.10. IDU label

Product number Consecutive number

Product type (internal use only) Hardware version\ specification

4-digit Product code assigned to Product Number

Product model name


14

3 Configuration and Management

3.1 LCD/Keypad

LCD and keypad provides most basic method to locally configure and monitor the local CFM terminal (IDU+ODU).

LCD display is constantly backlight and is able to display 2 lines of 16 symbols each line.

LCD operates in two modes, “Status display” and “Setup”, please refer to Flow Chart 1 in Chapter 3.9.

Keypad consists of 4 buttons:

Button Description

ENTER ‘ENTER’ button is used

- to switch from “status display” to “setup” mode.

- to confirm the choice of selected value or parameter, or to enter submenu;

CLEAR ‘CLEAR’ button is used

- to cancel the choice and to move to previous (upper) menu level;

- to switch from the root menu of the “setup” to “status display” mode.

↑ ↓ Up/Down buttons are used:

- To scroll through menu;

- To choose parameter, and its value.

3.1.1 “Status Display” Mode of the IDU LCD Management Interface

Once the IDU is powered up, it automatically enters “Manual Display” mode, displaying two parameters at a time statically (use up/down arrow buttons to scroll through parameters). These parameters are listed in the Table 3.1.

Table 3.1. Parameters displayed in “Status Display” mode

Parameter Description

Tx=14518.500MHz Parameter indicates Tx frequency of the Radio. Rx=15246.500MHz Parameter indicates Rx frequency of the Radio. TxPower=+20dBm Indicates current output power, see Chapter 3.13.3 for more

information. Rx=OK Indicates various conditions of Rx signal from ODU:

“OK” - IDU receives acceptable signal from ODU; “Low” - received signal level at IDU is too low for proper operation; “Error” - indicates internal fault in ODU receiver; “Loopback” - radio loopback mode is switched on.

RxLev=-66dBm Indicates the level of the received signal. Cable=–5 dB Indicates signal attenuation in IDU-ODU cable, values of 0 … -20 dB

provide proper operation of IDU. TxOut=Ok Indicates operation status of ODU transmitter:

“Ok” indicated proper operation; “Error” indicates internal fault in ODU transmitter, please contact sales representative or manufacturer.

TxPLL=Ok Indicates operation status of ODU Tx Synthesizer Loop (PLL lock): “Ok” indicates proper operation; “Error” indicates internal fault in ODU transmitter.

RxPLL=Ok Indicates operation status of ODU Rx Synthesizer Loop (PLL lock): “Ok” indicated proper operation; “Error” indicates internal fault in ODU receiver.

ODU t=23C Indicates ODU internal temperature. Humidity=Low Indicates humidity level inside ODU,

“Low” indicate acceptable moisture levels; “High” indicate too high level of humidity, condensing.

Restart= 99 Indicates number of ODU management controller restarts since


15


counter was reset on power up. PW max = 20 Indicates maximum transmitter power (dBm). RxAlarmLev =-77 Indicates the Rx level (in dBm) at which the Radio Alarm is switched

on. No data from ODU RF Cable – OFF

Indicates connectivity status between IDU and ODU: “OK” - indicates acceptable level; “Short” - indicates short circuit in cable; “Off” - indicates too low power consumption by ODU. This is most likely due to the brake in the cable. If the cable is intact, the ODU is faulty. While ‘RF Cable = Off’, the IDU does not receive any data from ODU and will not display any information related with ODU.

IDU t= 31C Indicates temperature within the IDU. BlkErr=0 Block Error counter; Errored block is WAN frame with one or more bit

errors. Errored blocks are not counted while Sync lost (SL) alarm is switched on.

BBlkErr=0 Background Block Error counter: the background block errors are counted while BER < 10-3, and are not counted while Sync lost (SL) alarm is switched on.

StatTime=12107 Time, during which all error measurements are performed. ErrSec=12194 Errored seconds; errored second is a one-second period in which one

or more bits are in error or during which SL alarm is switched on.

SErrSec=12214 Severely errored seconds. Severely errored second is a one-second period which has a bit-error ratio ≥ 1·10-3 or during which SL alarm is switched on.

SLTime=12236 Synch Lost time, - time, during which SL alarm is switched on. AvTime=12306 Availability time. Please refer to ITU-T recommendation G.826 (Annex

A) for definition of availability of the path or connection. UnAvTime=9 Unavailability time. BER= 4.8e-12 Bit Error Ratio. This indication is correct assuming, that each block

(WAN frame) may have maximum one errored bit. BBER= 2.9e-10 Background Bit Error Ratio. BBLoop=OFF Indicates if the base-band loopback is switched on or off.

3.1.2 “Setup” Mode of IDU LCD Management Interface

The following table describes parameters available for change from IDU in Setup mode.

Algorithm of LCD operation is shown on Flow Chart 1 in Chapter 3.9. Table 3.2


Access code Specify the panel access code (a number from 0 – 200) to enable configuration of the CFM site from IDU using keypad. The panel access security feature can be enabled by setting the panel access code as a number from 1 to 200, either from serial or Telnet terminal. If panel access code is set as 0 (zero), the panel access security feature is disabled.

Restart CPU Reboots management controller; this will reset all management counters.

Reset counters Reset BlkErr, BBlkErr, StatTime, ErrSec, SErrSec, SLTime, AvTime and UnAvTime counters. Counters are also cleared when management controller is rebooted. For more information about counters, see Table 3.1.

Write config Saves current settings in EEPROM of management controller, these settings will take effect the next time when IDU will be restarted.

Loopback - RF loop OFF – switch off the radio loopback (local), - RF loop ON – switch on the radio loopback (local), - BB loopback OFF - switch off the baseband loopback (any), - BB loopback analog – switch on the analog baseband loop,


16

Parameter Description - BB loop ON - switch on the digital baseband loopback. For more details on radio and baseband loopbacks refer to Chapter 3.13.

Outdoor Unit - Tx Power - adjust the radio output power; the default setting is “OFF”.

- Tx frequency – set the radio transmit frequency (kHz). Frequencies can be set only according to the corresponding channel plan (depends on the part number). After manual setting of Tx frequency, Rx frequency and Channel number will be changed automatically.

- Change Chan – change Tx/Rx frequency channel. When choosing frequency channel, the LCD will display only Tx frequencies, but when channel is changed, the appropriate Rx frequency is also changed. Channel numbers and corresponding Tx/Rx frequency values are found in tables in the document ‘Channel plans’.

Modules This item contains all the commands for configuration of the installed modules. See Setup Mode Menu Tree below for all commands available from ‘Modules’ menu for 100Base-T, 1xE1, V.35, and 4xE1 modules.

Capacity Set the maximum capacity of the multiplexer (WAN speed): 8 Mbps, 16 Mbps or 34 Mbps. Once the capacity is changed, the IDU will configure the software for various IDU components, this will take a few minutes. Once the configuration is complete, the IDU will automatically restart. After the capacity change, the user must manually reconfigure all MUX slot speeds from LCD or from Telnet or serial terminal using ‘muxspeeds’ command; the new configuration must be saved using ‘write’ command.

MUX speeds Sets the data rate for each multiplexer slot; use 1E1…4E1 modes for E1 modules, and 2M…34M modes for Ethernet and V.35 modules; supported speeds for each slot are the following: • CFM-M-MUX with the maximum capacity of 8 Mbps: all slots support

speeds 0…8 Mbps with 2 Mbps step. In case the opposite site has the CFM series 4E1 FODU installed, and link operates with 8 Mbps capacity, the CFM-M-MUX must have one of the following configurations:

In case if FODU and CFM-M-MUX operates with 8 Mbps capacity

Slot 1 Slot 2 Slot 3 Slot 4

1E1 1E1 1E1 1E1

4E1 0M 0M 0M

• CFM-M-MUX with the maximum capacity of 16 Mbps: slot 1 and slot 2

supports speeds 0…16 Mbps with 2 Mbps step; slot 3 and slot 4 supports speeds 0…8 Mbps with 2 Mbps step.

• CFM-M-MUX with the maximum capacity of 34 Mbps: slot 2 and slot 3 supports speeds 0…16 Mbps with 2 Mbps step; slot 4 supports speeds 0…8 Mbps with 2 Mbps step; slot 1 supports speeds 0…8 Mbps with 2 Mbps step and RMN (remaining capacity) and FOD modes. In RMN mode the slot operates with any capacity equal to (34 – C2,3,4) Mbps, where C2,3,4 – the sum of capacities of slots 2, 3 and 4. The slot 1 is the only slot which supports capacity above 16 Mbps, including the maximum capacity of 34 Mbps. The FOD mode should be used for compatibility with the CFM Full Outdoor Unit, operating with WAN capacity of 34 Mbps. In case if the opposite site has the CFM series FODU installed, and link operates with 34 Mbps capacity, the CFM-M-MUX must have one of the following configurations:

In case if FODU and CFM-M-MUX operates with 34 Mbps capacity Slot 1 Slot 2 Slot 3 Slot 4 FOD 1E1 1E1 0M FOD 0M 0M 0M FOD 1E1 0M 0M


17


FOD 0M 1E1 0M

• CFM-M4-MUX with the maximum capacity of 4 Mbps, the following configurations are supported (0M+0M), (1E1+0M), (1E1+0M), (2M+0M), (2E1+0M), (4M+0M), (0M+1E1), (0M+2M), (0M+2E1), (0M+4M), (1E1+1E1), (1E1+2M), (2M+1E1), (2M+2M):

The numbering of slots is shown in Figure 2.3. Service line - Select local IP - Sets the IP address of the serial port of the local

IDU (local SLIP port IP address). - Select remote IP - Sets the IP address of the serial port of the

remote IDU (far-end SLIP port IP address). - Sel. remote MASK - Sets the IP netmask for the serial port of the

remote IDU (far-end SLIP port netmask). - Ping remote – pings the far-end IDU SLIP port, and displays packet

travel time in milliseconds. Ethernet - Select IP - specify IP address of the Ethernet management port of

the IDU management controller; default value 192.168.205.010 or 192.168.206.010;

- Select NETMASK – specify netmask for Ethernet management port; default value - 255.255.255.000

- Select Gateway – specify gateway for the IDU Ethernet management controller; default value - 255.255.255.255 (no gateway specified)

IP, Netmask, and Gateway parameters provide the means of addressing management board of IDU in order to control and manage the CFM site locally and remotely via service channel.

(!) It is necessary to restart the management CPU for any changes in IP settings to take effect.


18

Setup mode menu tree

Access code ChangeRestart CPU * - current channel numberReset Counters ** - number of corresponding portW rite ConfigLoopbacks RF loop ON

RF loop OFFBB loopback Change BBloop OFF

Change BBloop analogChange BBloop ON

Outdoor unit ODU Chan ##* Change Chan ##ODU Tx Power Change Tx PowerTx Frequency Change

Modules Module 1 Bridge Connection ChangeFlow Cntrl. Change

Module 2 1xE1 loopbacks Remote loop Change RloopAnalog loop Change AloopDigital loop Change Dloop

Module 3 V35 V.35 Speed Change SpeedV.35 Loopback Change Loopback

V.35 Clock Change ModeModule 4 4xE1 P#** rloop

P#** aloopP#** dloop

Capacity Change capacity16M MUX speeds ChangeService line Select local IP Change

Select remote IP ChangeSel. remote MASK Change

Ping remote PingEthernet Select IP Change

Select NETMASK ChangeSelect Gateway Change


19

3.1.3 Interface Module LEDs

V.35 Interface Module LEDs

Table 3.3. V.35 Module LEDs (see Figure 2.5)

LED Color Name Function Direction

TX Green Data Transmitting

Active

Data activity - data is being transferred from module's front port to multiplexer.

V.35 MUX*

SL Red Signal Loss V.35 port failure.

LB Red Loopback Active

Loopback on V.35 module is switched on, informing that the connection between V.35 port and MUX board is interrupted.

Dual loopback, please refer to chapter 3.14.5 for more information about V.35 module loopback.

RX Green Data Receiving

Active

Data activity - data is being received from multiplexer board and transmitted to module front port

MUX V.35*

E1 Interface Module LEDs


Tx Green

Steady green light indicates the E1 module is ready to transmit data to the user equipment (DTE – Data Terminal Equipment) connected to E1 port.

Normally Tx LED is switched on all the time.

In case if Multiplexer synchronization is lost (S.L. LED is lit), Tx LED goes off and AIS signal is transmitted from E1 port to CPE.

Rx Green Steady green light indicates that E1 port receives data from DTE.

AIS Red Steady red light indicates that E1 port receives AIS (Alarm Indication Signal) from DTE.

LB Red “Loopback” LED (red) indicates loopback mode is activated in the module.

Ethernet Interface Module LEDs

Color Description

Green Flickering Ethernet Link/Activity LED indicates data transmission

Yellow If this LED is switched on, the port speed is 100 mbps


20

3.2 Resetting the IDU

Depending on the method used, the user may reset

− the whole terminal (IDU+ODU) which will disturb the traffic, or

− the management controller individually, this will disturb the traffic for about a second, see table below for details.

Type of IDU reset Result

Reset through the LCD menu system using “Restart CPU” option or from the Telnet/serial console using “restartcpu” command

Restarts the management module. Resets all management counters.

Reset using hidden button at the rear side of the IDU (see Figure 2.4)

Restarts both the multiplexer module and the management module. Resets all management counters.

(!) This may require a pin, at least 15 mm long, approx. 1.5 mm in diameter.

Unplugging power supply Restarts the multiplexer module and the management module. Resets all management counters.

3.3 RS-232 Serial Management Port

RS-232 serial management port provides terminal management via connected PC or other terminal device, using command interface. The terminal connected to the serial management port (serial console) provides the same management functionality as Telnet terminal, for complete description of command interface please refer to chapter 3.5.

Modem PC/TerminalModem

IDU

PC/Terminal

IDU RS-232

RS-232

Figure 3.1. RS-232 serial connection

In order to interconnect the IDU and the management terminal directly through serial ports, a straight through modem cable is needed. The serial port of the management terminal should be configured with the following settings:

− Bits per second: 19200

− Data bits: 8

− Parity: none

− Stop bits: 1

− Flow control: none.

The serial console can be connected to the IDU remotely through a telephone line, using modems. In this case the modem, which is connected with the IDU, should be configured as stated below:

- Auto answer on first ring ON

- Echo offline commands OFF

- Suppress result codes


21

- DTR override

The modem configuration then should be saved (typically with AT&W string).

Figure 3.2. Command prompt

In order to connect the PC to the RS232 management port using Hyper Terminal program (this program is included in any Windows version), proceed as described below.

1. Connect PC to the RS232 serial port by means of ‘straight through’ serial cable (modem cable).

2. Run “Hyper Terminal” program. 3. Make a New connection, enter connection name.

Figure 3.3. Entering connection name

4. Choose port (COM1 or COM2).

Figure 3.4. Choosing COM port


22

5. Set port settings (bits per second: 19200, data bits: 8, parity: none, stop bits: 1, no data flow control).

Figure 3.5. COM port settings

6. Press OK 7. Press Enter. Password is disabled by default.

If successfully connected, the prompt should appear as in the picture below; see Chapter 3.5 for available commands.

Figure 3.6. Command prompt in ‘Hyper Terminal’

3.4 Ethernet Port

The 10/100Base-T Ethernet management port provides:

• Web management via integrated Web server;

• Telnet server, accessible using command interface;

• SNMP management via integrated SNMP agent.

The IDU can be connected

− directly to PC/Laptop,

− to LAN via router or other TCP/IP packet network termination unit to have IDU as part of network for transmission of management information.


23

3.4.1 Web Management

The CFM-M-MUX management system is running a Web server; the user can connect to Web server via Ethernet management port. Using Web interface it is possible to remotely configure and monitor the CFM site (counters, radio parameters, configuration etc.) from Web page via HTTP.

The IDU management system supports up to 2 Web clients.

Web interface is accessible by any standards based Web browser.

Before connecting to Web server, it is necessary to specify User Name and Password, using ‘wwwuser <username> <password>’ command, from Telnet or serial terminal. If User Name and Password is not specified, the user will not be able to open configuration pages (configure settings).

Figure 3.7. Main Web management window

To check the status of each module, click on a Status link to open the module status window.

(!) Entries, which are highlighted in red, indicate that specific parameters do not comply with the norms of normal operation; all other parameters are satisfactory.


24

Figure 3.8. Module Status window

In order to save the configuration, change multiplexer slot speeds, restart the CPU or change the Web page refresh time, go to the Main Configuration window (see the Figure below). When clicked on the Configure link for the first time since connected to Web server, you will be prompted to enter User Name and Password.

Figure 3.9. Main Configuration window (Configuration of radio parameters is disabled)


25

By default, the Main Configuration window does not allow configuring ODU parameters (frequency channel and output power); the radio parameter configuration from Web page is factory-set as disabled. It can be enabled with ‘enable rfweb yes’ command from Telnet or serial console.

Figure 3.10. The CFM IDU Main Configuration window extended with the ODU parameter configuration

To configure each interface module (speed, loopbacks, etc.), open the Modules Configuration window via Modules Configuration link.

Figure 3.11. Modules Configuration window


26

Command interface from Web

The Web interface allows using commands just like from Telnet or serial console. The commands are discussed in chapter 3.5.

To use commands, proceed as follows:

- Open Web browser;

- In navigation toolbar type “http://<ip_address>/configL.htm”, where <ip_address> is IP address of the IDU; see example in the following screenshot;

- Enter Username and Password when prompted;

- Type the command in the “Command” box and press Enter.

3.4.2 Telnet management

The user can connect to Telnet server via Ethernet management port (1 client is supported).

In order to connect to IDU via Telnet, the user will be prompted for login name and password. The default (factory preset) Telnet login-name\password is not specified; in order to connect to IDU via Telnet, the user must specify Telnet login-name and password using ‘Telnetuser <username> <password>’ command; information about command interface is given in chapter 3.5.

3.4.3 SNMP Management

The SNMP management allows to: − Read and configure parameters of IDU and ODU via SNMP; − Receive SNMP traps from IDU. In order to use the SNMP management facilities, it is necessary to configure: − the IP address of the management PC with the installed SNMP Trap Manager

program; the IP address can be specified from a Telnet or serial console using “SNMP trap <IPaddress>” command, or from IDU front panel. The default value is 255.255.255.255 (no SNMP Trap Manager specified). The Trap Manager address should be configured for each IDU, from which it is necessary to receive information on parameters, counters and alarms. The information is sent as SNMP Trap packets through the mediation of UDP protocol.

− host PC IP addresses. If the SNMP host connected to the IDU is not added to the IDU SNMP host table, the IDU will not respond to the SNMP requests from that host.

− SNMP read and write community names (passwords); there are no default read and write community names specified, - while SNMP community names are not specified, accordingly it will not be possible to read and write parameters via SNMP.

SNMP management functionality is available from any SNMP browser, by means of compiling SAF MIB to browser’s MIB base.

SAF MIB is available from:

- SAF Tehnika Web site, www.saftehnika.com,

- From SAF Tehnika tech support, email: [email protected],


27

- Contacting SAF Tehnika or distributors. ***** SNMP QUERY STARTED ***** sysDescr.0 (octets) SAF SNMP and WWW management sysObjectID.0 (oid) saf sysUpTime.0 (timeticks) 0 days 00h:33m:34s.90th (201490) productDescr.0 (octets) SAF CFM-M-UX description.0 (octets) SAF 23GHz microwave radio version.0 (octets) V2.16 2000.09.05 radioAlarm.0 (int32) on(1) signalAlarm.0 (int32) none(0) v_01.0 (octets) Tx=23362.5MHz v_02.0 (octets) Rx=22354.5MHz v_03.0 (octets) TxPower=+20dBm v_04.0 (octets) Rx=OK v_05.0 (octets) RxLev=-109dBm v_06.0 (octets) Cable=- 26dB v_07.0 (octets) TxOut=Ok v_08.0 (octets) TxPLL=Ok v_09.0 (octets) RxPLL=Ok v_10.0 (octets) t= 23C v_11.0 (octets) Humidity=Low v_12.0 (octets) Restart= 99 v_13.0 (octets) IDU t= 27C v_14.0 (octets) RF Cable - OFF v_15.0 (octets) MUX 6M+0M+0M+2M ***** SNMP QUERY FINISHED *****

Sample of SNMP query

SNMP traps

SNMP traps are SNMP packets sent by IDU to PC with installed SNMP trap managing software; the IP address of the trap Manager PC is specified with “SNMP trap <IPaddress>” command from Telnet or serial terminal.

The IDU sends the following SNMP trap packets to the SNMP Trap Manager:

SNMP trap Description

Alarm The trap is sent each time the changes with one of alarms occur (alarm switches on or off), the following alarms are included in Alarm trap:

- Radio alarm

- Sync lost alarm

- BER alarm (triggers when BER exceeds specified value, which is 10-6

by default)

- Remote alarm (RAI)

- System alarm: this alarm is switched on in case of hardware failures.

For more information about alarms, see Table 2.2 and Table 2.3.

Cold-start The trap is sent each time the IDU is started.

Authentication failure The trap is sent each time the attempt occurs to read or write the variable with incorrect community name.

3.5 Command Interface

The CFM equipment (IDU and ODU) can be monitored and configured using command interface described in this chapter, connecting with

- serial console to RS232 port, or

- Telnet terminal via Ethernet management port; the Telnet management supports only one client.

The command line management interface offers the widest configuration and monitoring functionality. The following tables in this chapter summarize all available commands for Telnet and serial management.

Tips:


28

− To end Telnet or serial session press Ctrl+D, then, to open session again, the prompt will appear to enter username and password.

− For default (factory) usernames and passwords please refer to chapter 3.5.4.

Common commands

Command Description Time Show current date and time. Time <YYYY-MM-DD HH:mm:ss>

Set the date and time. The clock is not available on the IDU LCD.

Name <deviceName> Assigns a name to the IDU; The default name is “SAF”. The IDU name appears in the prompt string of the Telnet/serial terminal management windows, it can also be seen on the IDU LCD by pressing clear button while in status display mode as well as on the Web browser window. The name can be a maximum of 16 symbols long. If using space(s), the argument should be in double quotes, Example: name “SAFterm2 14 7”

Lcd <1…255> Adjust LCD contrast (values 0…255), default value is 165. Write Save all settings in the EEPROM. This command saves all current

settings in EEPROM, including those in the script. Ping <IPaddress> This command is for troubleshooting purposes to verify the service

channel connectivity, - sends a special packet to the remote IDU and then waits for a reply.

BBloop on | analog | off [duration]

Set baseband loopback, “on” – set digital loopback (dual), “analog” – set analog loopback (non-dual), “off” – suspend baseband loopback. Without setting duration parameter, by default loopback will be active for 1 min. Example: BBloop on 3

RFloop on | off [duration]

Set RF loopback, - “on” – set loopback, “off” – suspend loopback. Without setting duration parameter, by default loopback will be active for 1 min. Example: Rfloop on 3

Webrefresh <refreshperiod>

Refreshes the contents of WEB interface with a period specified with refreshperiod parameter. The period is given in seconds; the minimum period is 2 seconds.

Example: webrefresh 5 – the web page will be updated after every 5 seconds.

RxAlarmLevel Displays Rx signal level (if set or obtained from ODU) at which the Radio Alarm is switched on. In case no value is set or obtained from ODU, then shows RxAlarmLevel= NoData

Rxalarmlevel <rx> | auto

Sets Rx Alarm Level value. “Auto” – value is obtained from ODU. “rx” – value should be entered manually. Example: rxalarmlevel –55

ResetWDT The management module has a watchdog timer (WDT), which manages the automatic restart of the management system if it “freezes” for about 2 seconds. Resetwdt command will reset watchdog timer causing the management system to restart, this will also reset all management counters.

ClearCounters Reset all counters, - BlkErr, BBlkErr, StatTime, ErrSec, SErrSec, SLTime, AvTime and UnAvTime counters. Counters are also cleared when IDU is rebooted. For more information about counters see Table 3.1.

Disable telnet | www | snmp | rip

“telnet” – Disable Telnet interface; “www” – Disable Web interface; “snmp” – Disable SNMP interface; “rip” – Disable RIP; (!) - After the command is entered, it is necessary to save the configuration in EEPROM (use “write” command) and restart the IDU for changes to take effect.

- RIP must be enabled for 1+1 configuration (with optional alarm port).


29

Common commands

Command Description BERAlarmLevel <BERlevel>

Specify BER level which, when exceeded, will trigger BER alarm to switch on, and will switch off BER alarm once the BER will get below the alarm level. Default value is 10-6 (1e-6), see the following example. Example: beralarmlevel 1e-7 - sets 10-7 BER alarm margin.

telnet <IP_address> Open Telnet session with the IDU, IP_address – IP address of the IDU management Ethernet port.

Configuring ODU parameters

Command Description Chan <channel#> Set the ODU Tx/Rx channel. Channel numbers and

corresponding Tx/Rx frequency values are found in tables in the document ‘Channel plans’.

Txpower Set the ODU Transmitter power [dBm]. The default setting is “OFF”.

Txfreq <frequency-kHz> Set the ODU Tx/Rx channel by specifying Tx frequency as integer in [kHz] units. Example: txfreq 14711000

Configuring security parameters

Command Description Enable password <password> Specify a password to prevent unauthorized access from

serial console (PC connected to IDU via serial port). Panel access <accesscode> Specify a password to prevent unauthorized configuration

from IDU front panel (LCD\keypad). The password can be a number from 0 – 200. By default the panel access code is set to “0” (there is no code specified).

WWWuser <username> <password>

Specify username and password (1 - 31 symbols) to prevent unauthorized access from Web terminal. By default there is no Web username and password specified, which means that access to the Web interface is prohibited.

FTPuser <username> <password>

Specify username and password (1 - 31 symbols) to prevent unauthorized connection to FTP server. By default there is no FTP username and password specified, which means that access to the FTP server is prohibited. When specifying FTP username and password, do not forget to start FTP server with command “start ftp” in order to get access to the FTP server.

Telnetuser <username> <password>

Specify username and password (1 - 23 symbols) to prevent unauthorized access from Telnet terminal. By default there is no Telnet username and password specified, which means that access to the Telnet interface is prohibited.

Enable rfweb yes | AnyString Enables configuration of ODU parameters (frequency, Tx power) from the Web terminal. In order to enable it, use “yes” with small caps; to disable use any string instead of “yes” argument except the empty string ( “” ). By default, the ODU configuration from Web is disabled.

Configuring IDU parameters

Command Description RestartCPU Restart CPU of the management controller for the new IP

settings to take effect. Resets all management counters. Muxspeeds slt1+slt2+slt3+slt4

Set the data rate for each multiplexer slot. See Table 3.2 for more information about speeds supported by each slot. Example: muxspeeds rmn+2E1+2E1+2M – configures the multiplexer slots.

Muxcapacity 8M|16M|34M Change the multiplexer maximum WAN capacity. After the


30


Command Description capacity change, the user must manually reconfigure all MUX slot speeds using ‘muxspeeds’ command; for CFM-M4-MUX the syntax of this command is: “Muxspeeds slt1+slt2”; the new configuration must be saved using ‘write’ command.

Mod 1|2|3|4 stat Show parameters, - lists all parameters and input/output status that refer to the specific module. Example for E1 interface module: SAF>mod 1 stat Module Fast Bridge vers. 1 software vers. 1 Configuration Eth. Port Link: Enabled Speed: Auto Duplex: Auto Flow cntrl: Enabled Actual status Link: Off Speed: 100Mb Duplex: Full Flow cntrl: On

Mod detect Detects and displays a list of currently installed modules. This detection procedure is carried out each time when management controller boots up.

IP addr <IPaddress> Set the IP address of Ethernet management port (requires to restart the management module CPU).

IP mask <IPnetmask> Set the IP netmask of Ethernet management port (requires to restart the management module CPU).

IP gw <IPaddress> Set the IP address of the default gateway to the service channel (requires to restart the management module CPU).

IP seraddr <IPaddress> Set the IP address of the serial port of service channel for the local (near-end) IDU management module (requires to restart the management module CPU).

IP remaddr <IPaddress> Set the IP address of the serial port of service channel for the remote (far-end) IDU management module (requires to restart the management module CPU).

IP remmask <IPnetmask> Set the netmask of the serial port for the remote (far-end) IDU management module (requires to restart the management module CPU).

IP sideaddr <IPaddress> For 1+1 configuration only (option with alarm port only)! Set the IP address of the alternate link.

Route add <destinationIPaddr> Mask [netmask] <gateway> [metric]

Add a static route to the routing table. The variable “metric” is set to 1 by default. Example: Route add 192.168.205.010 Mask 255.255.255.0 155.13.79.13 5

Route delete <destinationIPaddr> [netmask]

Delete a static route from the routing table.

Route print [all] Display the list of the existing routes. SNMP community read <communityname>

Specify the SNMP community name of the agent to enable parameters to be read (not configured). The default read community name is saf-public.

SNMP community write <communityname>

Specify the SNMP community name of the agent to enable parameters to be written (configured). The default write community name is saf-private.

SNMP host add <IPaddress> Adds the host IP address to the IDU SNMP host table. If the SNMP host connected to the IDU is not added to the IDU SNMP host table, the IDU will not respond to the SNMP requests from that host.

SNMP trap <IPaddress> Set the IP address of the management terminal with the installed software for SNMP trap management (requires to restart the management module CPU).


31


Command Description Start ftp Runs the FTP server on the IDU. By default it is switched off.

In order to use FTP server, it is required to: 1) Start FTP server using ‘start ftp’ command; 2) Specify username and password using ‘ftpuser’ command.

Start tftp Runs the TFTP server on the IDU, by default it is switched off.

Configuring E1 Interface Module parameters

Command Description

Mod 1|2|3|4 setE1 loop off | analog | digital | remote

Set the analog, digital or remote loopback in the module or switch the loopback off.

Example: Mod 3 setE1 loop analog

Mod 1|2|3|4 setE1 TxAIS on | off

Switch transmitting AIS signal on or off.

Mod 1|2|3|4 setE1 on | off Switch the module on or off.

Configuring 4xE1 Interface Module parameters

Command Description

Mod 1|2|3|4 setE1 port1 | port2 | port3 | port4 loop off | analog | digital | remote

Set the analog, digital or remote loopback in the module or switch the loopback off.

Example: Mod 3 setE1 port2 loop analog

Mod 1|2|3|4 setE1 port1 | port2 | port3 | port4 TxAIS on | off

Switch transmitting AIS signal on or off.

Mod 1|2|3|4 setE1 port1 | port2 | port3 | port4 on | off

Switch the module on or off.

Configuring V.35 Interface Module parameters (incl. fractional mode)

Command Description Mod 1|2|3|4 setV35 speed 64 | 128 | 256 | 512 | 1024 | 2048 | 4096 | 6144 | 8192

Set the speed of V.35 interface (in kbps). Actual number of options depends on “muxspeeds” command setting for the module.

Mod 1|2|3|4 setV35 phase normal | inverse

Invert the RxC clock signal (it is transmitted from V.35 module to user equipment)

Mod 1|2|3|4 setV35 polarity normal | inverse

Invert the incoming and outgoing data signals (RxD – outgoing, TxD – incoming) between DCE (module) and DTE (user equipment).

Mod 1|2|3|4 setV35 loop on | off Set the loopback mode of V.35 interface module. Mod 1|2|3|4 setV35 TxC Master | Slave Set the sync status of V.35 interface module, ie.

master or slave. Example: Mod 2 setV35 txc slave

Mod 1|2|3|4 setV35 fr ON | PCM31 | PCM30 | OFF

ON – switches on fractional mode, fractional mode can be switched on only if slot speed is 2 Mbps; OFF – switches off fractional mode (uses all available bandwidth).

Mod 1|2|3|4 setV35 TSC <count of time slots>

Specify count of timeslots (up to 31). The default TSC value depends on mode, - if mode is PCM30, default value is 30, if mode is PCM31, - 31. The count of timeslots must be equal to “ones” in TSM parameter.


32

Configuring V.35 Interface Module parameters (incl. fractional mode)

Command Description Mod 1|2|3|4 setV35 TSM <time slot select mask>

Specify time slot selection mask. The length of the mask must be 32 symbols, with “1” and “0” only. For example, if all available timeslots are selected in mode PCM31, the command is: Mod 1 setv35 tsm 11111111111111111111111111111110 In PCM30 mode Mod 1 setv35 tsm 11111111111111101111111111111110

Configuring Low capacity 2-port 100Base-T Ethernet Bridge Module Command Description

Mod 1|2|3|4 setf2bridge port1 | port2 connection auto | 10hdx | 10fdx | 100hdx | 100fdx

Configure port speed and duplex, 10hdx – 10 Mbps half duplex, 10fdx - 10 Mbps full duplex, etc. Example: Mod 3 setf2bridge port1 connection 100fdx The factory setting for both ports is auto.

Mod 1|2|3|4 setf2bridge port1 | port2 priority low | high

Configure port priority. The factory setting for both ports is low.

Mod 1|2|3|4 setf2bridge port1 | port2 flowcntrl enable | disable

Enable or disable flow control for the specified port.

Mod 1|2|3|4 statistics [reset] Displays statistical information: − Received packets and bytes, transmitted packets and

bytes, errors for port 1, port 2 and WAN port; − Collisions for port 1 and port 2. The subcommand for resetting these counters is: mod 1|2|3|4 statistics reset

Mod 1|2|3|4 resetf2bridge Restart Ethernet bridge module.

Configuring 1-port 100Base-T Ethernet Bridge Module

Command Description Mod 1|2|3|4 setbridge connection auto | 10hdx | 10fdx | 100hdx | 100fdx

Configure port speed and duplex, 100hdx – 100 Mbps half duplex, 100fdx - 100 Mbps full duplex etc. Example: Mod 3 setbridge connection 100fdx The factory setting is auto.

Mod 1|2|3|4 setbridge flowcntrl enable | disable

Enable or disable flow control.

Mod 1|2|3|4 statistics Displays statistical information: − received packets and bytes from LAN and WAN, − transmitted packets and bytes from LAN and WAN, − count of FCS errors for LAN and WAN port, − collisions for LAN side. The subcommand for resetting these counters is: mod 1|2|3|4 statistics reset “Mod 1|2|3|4 stat” command will display Eth link status (on/off), mode (FDx/Dx), speed.

Mod 1|2|3|4 resetbridge Restart Ethernet bridge module.

Configuring Ethernet management ports (located on IDU rear panel, see Figure 2.4)

Command Description

ethernet stat Displays the Ethernet statistics for port1 and port2. Example: SAF>ethernet stat Fast 2 Chan. Ethernet interface. Configuration


33

Configuring Ethernet management ports (located on IDU rear panel, see Figure 2.4)

Command Description Port 1 Speed: Auto Duplex: Auto Flow cntrl: Enabled Port 2 Speed: Auto Duplex: Auto Flow cntrl: Enabled Actual status Port 1 Link: Off Speed: 10Mb Duplex: Half Flow cntrl: Rx:Off Tx:Off Port 2 Link: On Speed: 10Mb Duplex: Half Flow cntrl: Rx:On Tx:On

(!) In case statistics display that Link is Off, the rest of Actual Status data is not credible.

ethernet port1 | port2 connection auto | 10fdx | 10hdx | 100fdx | 100hdx

Configure port speed and duplex, 10hdx – 10 Mbps half duplex, 10fdx - 10 Mbps full duplex, etc. Example: ethernet port1 connection 10fdx

The factory setting for both ports is auto.

ethernet port1 | port2 flowcntrl enable | disable

Enable or disable flow control for the specified port.

Example: ethernet port1 flowcntrl enable

Configuring ATPC settings

Command Description ATPC enable Enable ATPC feature ATPC disable Disable ATPC feature ATPC delay <seconds> Specify minimum time delay (in seconds) between Tx power

adjustments; default value 1 second. ATPC delta <Tx[dB]> Specify step for Tx power adjustments; default value is 1 dB,

changing of this value is not recommended. ATPC TXmin 1|2 <Tx[dBm]> Specify minimum Tx level (dBm), for link 1 or link 2. ATPC TXmax 1|2 <Tx[dBm]> Specify maximum Tx level (dBm), for link 1 or link 2. ATPC RXmin 1|2 <Rx[dBm]> Specify minimum Rx level (dBm), at which the Tx power will

not be changed for link 1 or link 2. ATPC RXmax 1|2 <Rx[dBm]> Specify maximum Rx level (dBm), at which the Tx power will

not be changed for link 1 or link 2. ATPC stat Display ATPC related parameters.

Commands for script editing Command Description

Cfg show Show the configuration script stored in RAM. Cfg load Load the configuration script from EEPROM into RAM. Cfg run Execute configuration script stored in RAM. Cfg clear Clear the script stored in RAM. Cfg delete <stringNumber> Clear a single string in the configuration script. This command is

useful for script editing. Cfg write Save current script in EEPROM. This command saves in EEPROM the

current script as well as settings that are specified in it.


34

Commands for script editing Command Description

cfg backup <filename> Save current configuration script in text file on the Flash disk, with the specified filename.

cfg restore <filename> Load the configuration script (specified text file) in RAM, but does not execute the script. Further, − to apply the script (execute commands), use ‘cfg run’

command. − to store the script in EEPROM, use ‘write’ command.

Cfg factory yes Reset the configuration by loading in EEPROM the script with default settings. This command performs the following actions (in the following order): 1. clears the current script from EEPROM, 2. creates and stores in EEPROM the new script with the following

settings: - IP addr 192.168.205.010 or 192.168.206.010 - IP mask 255.255.255.000 - IP gw – 255.255.255.255 (default gateway - none) - IP seraddr 192.168.0.10 – (SLIP configuration, - IP address

of the local serial port) - IP remaddr 192.168.0.11 – (SLIP configuration, - IP

address of the remote serial port) - Enable rfweb yes (enable configuration from Web terminal) - SNMP trap 255.255.255.255 (none) - RxAlarmLevel auto (parameter value is obtained from ODU) - muxspeeds 0M+0M+0M+0M

3. restarts the management controller log show [start_num] The management controller maintains event log, - events include

configuration changes, management controller restarts, local site alarm changes (RA, SL, RAI alarms). The maximum count of log entries is approximately 1000, the events are written in EEPROM cyclically, overwriting older entries. The “log show” or “log” commands display latest 20 log entries, the log entries are numbered, - entry with the largest number is the latest event. The “log show” command can be followed up with an entry number to display latest 20 entries beginning from the entry specified by the number, e.g., “log show 100” will display entries 100…120.

log filter <group_ID> [num]

List specific group ID alarm entries. [num] parameter defines the starting number of the entries.

log file <file_name> Saves the log into a file and saves it in the Flash memory. Commands for operations with files and file system Please refer to chapter ‘Working with files’, Chapter 3.5.2. Syntax notes: − Commands are in bold font. − All arguments (variables) are in italic font. − Subcommands and keywords are in regular font. − Arguments in square brackets ([ ]) are optional but required arguments are in angle brackets

(<>). − Alternative keywords are grouped in braces ( ) and separated by vertical bars (| ). − For the CFM-M4-MUX, only arguments “1” and “2” are used from 1|2|3|4.

Verification commands (read-only)

Command Description

Stat Show parameters, - lists all the parameters that are displayed in the status display mode of the IDU LCD.


35

Verification commands (read-only)

Command Description

Diag power Display power supply voltages supplied to PCBs and ODU power. Example: SAF local>diag power Power supply: U +3.3V = 3.36V U +5V = 5.12V U -5V = -5.16V U ODU = 23.64V I ODU = 0.00A P ODU = 0.00W Iodu max= 0.75A

Mac Display MAC address of the Ethernet management port. Ver Display hardware and software version of the IDU and ODU, and IDU serial

number. ODU Display ODU software version. sernum Display IDU serial number. ustat Display inputs and outputs of the alarm port.

Alarm and performance management commands

Command Description

Alarm stat Lists alarm groups currently set. Alarm groups Displays the list of all alarms and their group IDs. Alarm cfg <group ID> [<global> <first> <logging> <snmp>]

Allows defining detailed alarm representation settings. [<global> <first> <logging> <snmp>] must be defined in a row of ‘1’s or ‘0’s of 5 values for specified group ID with <group ID>. ‘1’ means the values are ‘on’ and ‘0’ – ‘off’.

pm log <interval> <last rec count> | <start date> | <start time> | <end date> | <end time>

Lists performance management log with selected <interval> of 1min, 15min or 1hr. Allows choosing the number of last records to be shown (<last rec count>) or to define start and end time and date.

(!) End time and date values must be entered after entering start time or date, respectively.

pm select RX_LEVEL | TX_LEVEL | ODU_TEMP | RF_CABLE | ND_ODU | IDU_TEMP | BER ALARMS | ALL|NOT

Allows selecting the system parameters to be monitored and shown in the performance management log.

pm logclear Clears performance log.

pm threshold stat | auto | RX_LEVEL | TX_LEVEL | ODU_TEMP | RF_CABLE | IDU_TEMP | BER min|max <value>|auto

Sets threshold levels for parameters outside which TS (Threshold Seconds) are counted and shown in the performance log.

Alarmio on | off Turns the alarm port (optional) on or off.

Switch commands for 1+1 configuration (with optional alarm port only)

Command Description

Switch enable | disable Enable/Disable switching function in 1+1 site. Switch stat Display switchover status information. Switch active Set as Active if it is in normal operation condition Switch standby Set the IDU to Standby, allowing the other IDU in 1+1 site to

become Active.


36

Switch commands for 1+1 configuration (with optional alarm port only)

Command Description

Switch force active | standby | off

• ‘active’, ‘standby’ - Switch to the selected mode, ignoring any conditions;

• ‘off’ – disable forced mode resuming normal switching. Switch mode HSB | FD [ primary]

Set the switching mode: HSB – hot-standby.

FD – frequency diversity ‘FD primary’ – sets the FD mode and if both links operate normally, the M-MUX will be set as Active.

(!) For switching to work properly in HSB mode, all four IDUs of the radiolink must be set as HSB.

(!) For switching to work properly in FD mode, all four IDUs must be set to FD mode, and only one of them can be set as ‘FD primary’ option.

Switch delay <time_seconds>

Specifies the minimum delay (in seconds) between consecutive switchover attempts for the IDU. This value must be less or equal to “switch try delay”; the default value is 2 seconds.

(!) This setting must be different for each of four IDUs of each hop.

Switch try delay <time_seconds>

Specifies the exact time interval between switchover attempts, must be less than “Switch delay” value. Default value is 5 seconds.

Switch show on | off Allow (on) or disallow (off) displaying switching information in command interface. Off by default.

Time

Active

Standby

Active

Standby

How Delay parameters work

OFF

ON

IDU

1S

YN

CLO

SS

ALA

RM

M-MUXIDU 1

IDU

2S

YN

CLO

SS

ALA

RM

M-MUXIDU 2

OFF

ON

IDU

stat

eID

Ust

ate

Switch Try Delay, - the IDU 2 will notswitch from Active to Standby unlessSwitch Try Delay interval expires, even ifSL alarm switches on during that time

Switch Delay, - the IDU will not switchfrom Standby to Active state, until theSwitch Delay has not expired

Power Off

Switch delaySwitch delay

Switch try delay

Switch try delaySwitch delay

Figure 3.12


37

3.5.1 Working with configuration script

The management module has RAM and EEPROM chips onboard. When IDU is booted up, bootstrap is loaded from the EEPROM into RAM. The bootstrap contains the parameters that were previously stored in EEPROM using write and/or cfg write commands. These parameters are stored in EEPROM in the form of script and when booting up, the script parameters are loaded into RAM. These parameters can be freely changed in run-time, - changing the data in RAM. If the IDU is shut down without saving the current configuration (script) in EEPROM, the original configuration will be restored from EEPROM on the next boot-up.

Here is an example of script: SAF>cfg show 01: ip remaddr 192.168.0.11 02: ip seraddr 192.168.0.10 03: Chan 144 04: muxspeeds rmn+8M+8M+4E1 05: snmp community read safpub 06: snmp trap 255.255.255.255 07: route add 62.85.14.0 MASK 255.255.255.0 192.168.12.22

The script can be edited:

- string can be added by simply entering the required command (the script will be supplemented with the new string or the instant string entry will be updated)

- string can be deleted using “cfg delete <string#>” command line.

- the changes can be saved in EEPROM using cfg write command line.

3.5.2 File system

The software used by the IDU management controller is organised in files, which are stored in Flash disk.

Firmware and boot configuration files

The following files are needed for the IDU to start:

- ‘Boot.ini’ file, - device boot configuration file. This file is text file and contains the name of the firmware file which must be executed at startup. The file name can be freely changed, but its default name is ‘boot.ini’, hereinafter it is assumed, that this file has default filename. The most important factor about this file is that it must be uploaded with ‘B’ and ‘e’ attribute flags (flags are case sensitive!), only then it will be treated as executive script.

Attribute flags for ‘boot.ini’ file:

B – query run at boot; e – executive script

For information how to upload files in the Flash disk, please refer to chapter 3.6.

- Firmware file, - this file is the main firmware executable for the appropriate IDU model. The file name can be freely changed, but its default name will contain the version and IDU model, e.g., ‘mmux428.elf.ezip’. The most important factor about this file is that it must be uploaded with ‘E’ and ‘c’ attribute flags, otherwise this file will not be used as the firmware.

Attribute flags for firmware file:

E – executable binary; c - compressed

(!) The parameters that are not specified in the configuration script will have their default values when the IDU is restarted.


38

Configuration backup files

Using ‘cfg backup <filename>’ command, the user can create the backup file of the current CFM site configuration. The configuration backup file is text file and, when created, contains the current configuration script, - the same configuration script that are stored in EEPROM. Please refer to chapter 0 for more information about configuration script.

The configuration backup files are stored in Flash disk, where they can be edited or downloaded to PC. The backup configuration file can be applied in run-time, by consecutively entering ‘cfg restore <filename>’ and ‘cfg run’ commands.

The user can create and store several configuration files to quickly revert to other CFM site configurations.

Working with files

The following commands are intended to operate with files, stored in the Flash disk on the management controller.

edit <filename> Edits the specified file. This command is intended for editing configuration backup files and boot configuration file (boot.ini). For example,

edit boot.ini,Be

– file ‘boot.ini’ will be opened for editing. ‘Be’ specifies that this file will be saved with attributes ‘B’ and ‘e’. If boot.ini file is intended to be modified, it should always be opened specifying ‘B’ and ‘e’ flags as in example above, this will ensure that file will be saved with these attributes (flags).

To close the file and save changes press Ctrl+Z, to close the file without saving changes press Ctrl+Q.

The configuration backup files do not require specific attributes.

Boot.ini file in Flash memory can be edited from serial console only, not via Telnet.

tfs ls Displays a list of files stored in the Flash disk, and how many bytes are used by these files and how many bytes are free.

‘tfs dir’ can also be used.

tfs cat <filename> Displays the contents of a text file.

‘tfs type’ can also be used.

tfs del <filename> Deletes the specified file from Flash disk.

‘tfs rm’ can also be used.

tfs check Checks the files and file system consistency; this command is for diagnostic purposes. For example:

SAF>tfs check

TFS device //FLASH/ check:

(!) - The files are uploaded from PC to Flash disk using TFTP (via Ethernet management port) or using Xmodem protocol (via RS232 serial port). For more information about file upload please refer to chapter 3.6; configuration backup files are created by IDU management system.

- The flash disk may store other files as well, for example, previous firmware versions, configuration backup files, - up to 3.5 Mb (3 or 4 firmware files).

- The attribute flags for files are case sensitive.

- The file names can be changed, but it is very important that the file has the necessary attribute flags. Otherwise, the file will be used neither as firmware, nor as ‘boot.ini’ type file.

- There are no file extensions in the file system; either file, when edited, is treated as ASCII text file.

- When uploading the file, if the Flash disk stores the file with the same filename as for uploadable file, it will be overwritten with the new file.

(!) The configuration restored from file is not stored in EEPROM and therefore will be lost when IDU is restarted, to save it in EEPROM use ‘write’ command.


39

mainappb.elf.ezip... ok

mmux400.elf.ezip... ok

cfg1.txt... ok

boot.ini... ok

PASSED

TFS checked ...

In this example no files are corrupted.

tfs clean Defragments the Flash disk. It is recommended to perform the defragmentation if larger files (like firmware files) are uploaded or deleted.

3.5.3 Storage of radio parameters

The radio parameter values (transmit frequency and power) are stored internally in Flash memory of the Radio unit, the Radio operates exactly with those values stored in its Flash memory. When the radio parameter is modified while the equipment is in operation, the corresponding radio parameter value in the Radio Flash memory is overwritten with the new one and applied in operation. Since the radio parameters are stored in ODU in Flash memory, it is not necessary for the IDU configuration script (bootstrap) to contain strings that configure radio parameters. In case if the configuration script stored in IDU EEPROM contains strings that configure radio parameter(s), each time the equipment is booted, the radio parameter values written in the IDU bootstrap are uploaded to the Radio and the previously stored radio parameter values in Flash memory are overwritten with those in the IDU bootstrap. Hence the radio parameter configuration in the IDU bootstrap has a higher priority as they will override the values stored in the Radio Flash memory when the equipment is rebooted.

It is useful to write the radio parameter configuration in the IDU configuration script for the purpose to be able to quickly replace the ODU later.

3.5.4 Security commands

General tips

Telnet server supports one user only. The default username and password for Telnet terminal is not specified.

Web server supports two users. By deault the Web server is disabled, because the username and password for Web terminal is not specified; the username and password to connect to Web server from Web terminal can be specified, using

‘WWWuser <username> <password>’ command.

The passwords may contain spaces, if using space(s) the password should be entered in quote marks.

For serial, Telnet and Web terminals the password can be changed by simply re-entering the appropriate security command while logged on, and then saving the configuration in EEPROM using ‘write’ command.

To terminate Telnet session press Ctrl+D.

To disable username and/or password, enter the password configuration command with empty string in argument: − for serial console: enable password “”

− for Telnet terminal: telnetuser “” “”

− for Web access: wwwuser “” “”

In case if user has forgotten username and password for Telnet access and password for access from serial console, it is possible to restart the IDU without applying settings stored in EEPROM, and then find out the Username and Password using ‘cfg show’ command. Proceed as follows:

(!) Take note of upper case and lower case type, it should be taken into account for both username and password!


40

− connect to IDU with serial console (via serial port); − Enter ‘restartcpu’ command and follow the strings displayed on serial console

window; as soon as ‘Press <Esc> twice to stop initialisation’ string appears (see Figure 3.13), press Esc key twice.

Figure 3.13. Startup screen

− Enter ‘cfg show’ command to display boot configuration script, which will also include security commands with Usernames and Passwords.

By default there are no password specified for access from serial console, - when user connects to IDU from serial console, no prompt is displayed to enter password.

Panel access code

The panel access code for the access from IDU panel can be specified from the Telnet and serial terminals only. When the access code is specified, the adjustment and configuration of any IDU/ODU parameters and loopbacks from IDU LCD is not available, unless the correct access code is specified at IDU using keypad (refer to chapter “Setup” Mode of IDU LCD Management Interface). The specification of access code should also be followed by saving the configuration script otherwise the access code value will be set to default (none) on the IDU restart. The panel access code can be changed simply entering the new access code (number from 0 – 200) using panel access command.

To disable the panel access code feature, enter value “0”, which means that this feature is disabled (default setting).

3.6 Updating management software

Generally the user can update the IDU management software by uploading the appropriate firmware file to IDU Flash disk, and then edit boot configuration file if necessary. The file upload can be performed

- via Ethernet management port using FTP (recommended),

- via Ethernet management port using TFTP, or

- via RS232 serial port using Xmodem protocol.

To simplify the software update process, SAF Tehnika provides special update package as new version is available. This update pack is available as archive (e.g. zip), which includes firmware file, boot configuration file and other files needed for update process. To receive update pack, please contact Your SAF Tehnika distributor.

To update IDU software by using the update pack, proceed as follows:

- uncompress the package;

(!) Important!

The specification of username and password (or access code) should always be followed by saving the configuration script (using “write” or “cfg write” commands). Otherwise, the password request will be ignored after the restart of the IDU.


41

- change the IDU IP address to 192.168.205.10, or edit ‘send_boot_ini.cmd’ and ‘send_ttftp.cmd’ files by replacing “192.168.205.10” with actual IDU IP address;

- run ‘sw_update.cmd’ to perform update. In case if the memory is full, the upload will halt and error message will be displayed, in this case user must first delete some files to free enough memory on IDU Flash disk.

Chapters 3.6.1 and 3.6.2 describe other methods how to update the software without using update pack.

3.6.1 Uploading file via Ethernet management port (TFTP)

Assuming that the IDU IP settings are properly configured, proceed as follows:

1) Connect the IDU to network or directly to PC,

2) Make sure TFTP is running on IDU (by default, the TFTP is switched off); to run the TFTP on IDU, connect to IDU with Telnet client and enter the following command: ‘start tftp’.

3) Run the program that enables to use TFTP service, for example command interpreter (cmd.exe) if using Windows, see Figure 3.14.

4) For example, to upload the firmware file ‘mmux400.elf.ezip’ with attribute flags ‘E’ and ‘c’, enter command:

tftp –i 192.168.205.11 put C:\files\mmux400.elf.ezip,Ec

where:

‘-i’ – key which specifies that file must be transferred in binary image transfer mode;

‘192.168.205.11’ – IDU Ethernet management port IP address (host);

‘C:\files\mmux400.elf.ezip’ – firmware file (source);

‘Ec’ – file attribute flags ‘E’ and ‘c’; the attribute flags are separated from file name or source with comma (only comma and no space) and there are no commas or spaces between flags;

Figure 3.14. Firmware upload via TFTP

5) If uploaded file is large (like firmware file), it is recommended to defragment Flash disk. Use ‘tfs clean’ command from Telnet or serial terminal to perform defragmentation.

6) If the uploaded file is firmware file which should be used by IDU, it is necessary to edit ‘boot.ini’ file by deleting the entry with old file name and writing file name of the new firmware file; the ‘boot.ini’ file must be saved with ‘B’ and ‘e’ flags (file attributes), for more information how to edit files, please refer to chapter ‘Working with files’, Chapter 3.5.2.

(!) To copy file from IDU Flash disk to PC hard disk via TFTP, use the following command:

tftp -i 192.168.205.11 get filename C:\destination

where

‘192.168.205.11’ – IDU port IP address (host);

‘filename’ – file to be copied from IDU to PC; ‘C:\destination’ – destination path where the file will be saved on PC hard disk.


42

3.6.2 Uploading file via Ethernet management port (FTP)

Before uploading file via FTP, make sure IDU FTP server is running and username and password are specified, using commands “Start ftp” and “FTPuser <username> <password>” accordingly.

- Open command window. - Start FTP client by entering “ftp” command (“ftp>” prompt will appear). - Connect to IDU FTP server using command “open <IDU_IP_address>”. Type in

username and password when prompted. - Enter command “type binary’ to make sure the binary transfer mode is selected. - Use command “send <local file> <remote file>,<flags>” to upload files to IDU Falsh

disk. For example:

send c:\boot.ini boot.ini,Be

Use flags ‘E’ and ‘c’ if the file is firmware file; if the file is boot configuration file (boot.ini), the flags must be ‘B’ and ‘e’ (‘Be’); the flags for configuration backup files may not be specified.

Use command “ls” to list files on IDU flash disk.

Use command “delete <filename>” to delete the fale from IDU Flash disk.

3.6.3 Uploading file via serial port (Xmodem)

File upload via serial port takes much longer time compared to using TFTP and should be used only in case if Ethernet connection with IDU management system is not available, or does not start normally.

1) Connect the serial console to IDU RS232 port, make connection with the following properties: Bits per second: 19200; Data bits: 8; Parity: none; Stop bits: 1; Flow control: none; if using ‘Hyper Terminal’ program, please refer to chapter 3.3 for information how to make a connection.

2) Type ‘restartcpu’ and, while IDU is booting, press any key when ‘boot.ini?’ prompt appears. This will stop executing script in ‘boot.ini’ file and the IDU will remain in MicroMonitor mode, this is system startup mode which loads the management system firmware;

3) In MicroMonitor mode enter the following command:

xmodem –cd –F <filename-no_flags> -f Ec

where

<filename-no_flags> - file name with no flags specified

‘Ec’ – file flags, in case the file is firmware file - ‘E’ and ‘c’ flags must be used; if the file is boot configuration file (boot.ini), the flags must be ‘Be’ (‘B’ and ‘e’); the flags for configuration backup files may not be specified, in that case the command will be

xmodem –cd –F < filename-no_flags >

4) Use terminal emulation software with file upload function, such as Hyper Terminal (in Windows) to upload the firmware file to IDU as binary image (use binary transfer mode), using Xmodem protocol.

If using Hyper Terminal, proceed as follows: from menu select ‘Transfer’ ’Send File…’, then select file and in ‘protocol’ box select Xmodem protocol and press ‘Send’ button, the following box should appear

(!) While in MicroMonitor mode, the ‘uMON>’ prompt will be displayed, instead of normal prompt with IDU name (default ‘SAF>’).


43

When upload is complete, the following information will be displayed (Figure 3.15):

Figure 3.15

5) Enter ‘reset’ command to exit from MicroMonitor mode and restart the IDU.

6) Proceed with steps 5) and 6) in chapter 3.6.1.

3.7 Alarms

The following types of alarms

• Radio alarm (RA): when active, indicates problems with ODU or IDU-ODU cable, for more information see Table 2.2.2. The state of RA can be verified from

− RA LED on the IDU front panel,

− Web page,

− Telnet or serial console.

• Sync Lost alarm (SL): when active, indicates failure of Multiplexer frame synchronization, when switched off – the frame synchronisation is established. The state of SL can be verified from


44

− SL LED on the IDU front panel,

− Web page,


• Remote Alarm Indicator (RAI): this alarm signal is received from the far-end site (WAN side), indicating that the far-end site has the SL alarm switched on. The state of RAI can be verified from

− RAI LED on the IDU front panel,

− Web page,


3.7.1 Alarm (I/O) port (DB-25 connector)

The Alarm port is an optional feature.

The Alarm port shares the set of outputs of relay switches intended for the CFM site supervision and the user inputs to connect an external device that requires to be supervised. Each output of the port can be used either as NO type (normally open) or NC type (normally closed).

The following alarms are available through the alarm port as parallel relay outputs:

• A: Power on\off relay. If power is on, the relay is closed (normal relay state); if power is off – relay is open.

• B: SL – Synch Lost alarm, ON - relay is closed, OFF – relay is opened (normal operation).

• C: RAI – Remote Alarm Indicator, ON - relay is closed, OFF – relay is opened (normal operation).

• D: RA – Radio Alarm, ON - relay is closed, OFF – relay is opened (normal operation).

Each output is available as normally opened and normally closed.

There are four parallel inputs of the alarm port available: input A, input B, input C, input D. These inputs are used for connection of an external device which supplies DC voltage on input, - “0” or “1”; the changes of inputs (triggering between “0” and “1”), can be monitored from management terminal; refer to Chapter 5 for electrical specifications.

The alarm port outputs can be supervised via SNMP manager and/or Web console.

For information on Alarm port pinouts and electrical specifications, please refer to Chapter 5.

3.7.2 E1 module alarms

In this chapter 4 different situations will be examined to help identify the cause of particular alarms.


45

1)

In the first situation there are no problems with the link – cable is properly connected to E1 module; synchronization between modems at both link sides is successful, but the E1 module is receiving alarm indication signal (AIS) from user equipment side, which indicates channel failure at logical or physical level on user equipment.

In this case “mod # stat” (where # - number of E1 module installed) will show “AIS – On”, “TxAIS – Off” and “LOS – Off” and “log show” command will indicate two entries – “Slot[#]-Mod[#xE1] Ch[#] LOS[Off] AIS[On]” and “Slot[4]-Mod[#xE1] Ch[#] TxAIS[Off]”.

2)

In the second situation there is synchronization loss between modems, but connection between PBX (user equipment) and E1 module is operating well.

In this case “mod # stat” will show “AIS – Off”, “TxAIS – On” and “LOS – Off” and “log show” command will indicate two entries – “Slot[#]-Mod[#xE1] Ch[#] LOS[Off] AIS[Off]” and “Slot[4]-Mod[1xE1] Ch[#] TxAIS[On]”.

Module port will generate AIS signal.


46

3)

In the third situation there is no connection between PBX (user equipment) and E1 module, but synchronization between modems at both link sides is successful.

In this case “mod # stat” will show “AIS – On”, “TxAIS – Off” and “LOS – On” and “log show” command will indicate two entries – “Slot[#]-Mod[#xE1] Ch[#] LOS[On] AIS[On]” and “Slot[4]-Mod[1xE1] Ch[#] TxAIS[Off]”.

4)

In the last situation there is synchronization loss between modems and no connection between PBX (user equipment) and E1 module.

In this case “mod # stat” (where # - number of E1 module installed) will show “AIS – On”, “TxAIS – On” and “LOS – On” and “log show” command will indicate two entries – “Slot[#]-Mod[#xE1] Ch[#] LOS[On] AIS[On]” and “Slot[4]-Mod[#xE1] Ch[#] TxAIS[On]”.


47

3.8 Configuring Management Service Channel

The service channel capacity varies depending on the configured WAN capacity:

Maximum IDU capacity Service channel capacity

8 Mbps 40 kbps 16 Mbps 80 kbps 34 Mbps 160 kbps

Before using the Management Service Channel, the mandatory precondition is to properly configure the following parameters:

– IP addresses of the local and remote serial port (also referred as SLIP addresses): the IDU Management Module has a virtual serial port onboard that is used to receive/transmit the management information from/to the other virtual serial port on the far-side via service channel; both ports use SLIP.

– IP netmask of the remote serial port.

– IP address and net-mask of the Management Module.

– IP address of the gateway or host that is locally connected to the IDU.

The console is connected to the IDU via Ethernet console port located on the Management Module. The console should be configured so as to have routing information to the serial port (SLIP port) of the local IDU, - it should either run the RIP thereby automatically obtaining the routing information, or a static route(s) should be added.

The routing requires determining IP addresses of service channels (virtual serial port IP addresses). Since the Management Module operates as a router between two subnets running the RIP 2, normally it is not necessary to configure the routing by adding static routes.

Virtual serial port IP addresses can be picked from the “private internet” addresses, e.g., 10.X.X.X or 192.168.X.X. Both of these addresses should be different from those used for addressing the IDU, the principle is shown in the picture below, here each cloud depicts a subnet.

Eth

(RJ-

45) 2-port

Router Ser

ial

Por

t

Ser

ial

Por

t

ManagementModule

Servicechannel

The configuration of local and remote SLIP port addresses should conform the following principle.

Terminal A Terminal B

Local serial port IP address IP 1 IP 2

Remote serial port IP address IP 2 IP 1


48

Local Site (Terminal A’)

service channel

Eth

VirtualSerialPort

ManagementModule(router)

Eth

VirtualSerialPort


Remote virtual serialport IP address

Remote virtual serialport IP address

Local virtual serial portIP address

Local virtual serial portIP address

ManagementConsole

Required to specify:IP address/Net Mask,Default Gateway

Local Site(Terminal A)

Required to specify:Local serial port IP addr.,Remote serial port IP addr.Remote serial port netmask

Required to specify:Local serial port IP addr.,Remote serial port IP addr.Remote serial port netmask

Side IP address

Eth

VirtualSerialPort


Side IP address

Local Site (Terminal B’)

Side IP address

Local Site(Terminal B)

Eth

VirtualSerialPort


Required to specify:IP address/Net Mask,Default Gateway

Side IP address

for 1+1 onlyfor 1+0 and 1+1

IP parameters required to specify, for 1+0 and 1+1 link (terminals A’ and B’)

See examples below:

Examples of service channel configuration in 1+0 mode

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON

Eth

VirtualSerialPort

ManagementModule

RIP = ON

Telnet console/Web client

IP Addr 192.168.205.10IP mask 255.255.255.0IP GW 192.168.205.1

Local Site (Terminal A) Remote Site (Terminal B)

IP seraddr 192.168.0.1IP remaddr 192.168.0.2IP remmask 255.255.255.252


IP Addr 192.168.206.10IP mask 255.255.255.0

Console IP address: 192.168.205.1, 255.255.255.0Route Add 192.168.206.0 Mask 255.255.255.0 192.168.205.10

Figure 3.16

(!) It is recommended to use configuration where SLIP port net masks are 255.255.255.255 or 255.255.255.252.


49

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON

Eth

VirtualSerialPort

ManagementModule

RIP = ON



Local Site (Terminal A) Remote Site (Terminal B)




Router port IP address: 192.168.205.1, 255.255.255.0Route Add 192.168.206.0 Mask 255.255.255.0 192.168.205.10

Router(RIP=OFF)

Ethernet

Figure 3.17

Ethernet

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON

Telnet console/Web clientIP address: 192.168.204.2





Port IP address: 192.168.204.1

Router(RIP = OFF)

Eth

VirtualSerialPort

ManagementModule

RIP = ON

Eth

VirtualSerialPort

ManagementModule

RIP = ON



service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON



Hop 1

Hop 2

Port IP address: 192.168.205.1Route Add 192.168.205.0 Mask 255.255.255.240 192.168.205.2

Eth

VirtualSerialPort

ManagementModule

RIP = ON



service channel

Eth

VirtualSerialPort



Hop 3

ManagementModule

RIP = ON

Route Add 192.168.205.0 Mask 255.255.255.240 192.168.204.1

Figure 3.18. The IP configuration of the management channel via three 1+0 hops with the RIP II switched on in each IDU; since the management controllers are running RIP II, there is no necessary to specify gateway (see configuration strings in grey)


50

Ethernet

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = OFF


IP Addr 192.168.205.2IP mask 255.255.255.252



IP Addr 192.168.205.5IP mask 255.255.255.252


Router(RIP = OFF)

Eth

VirtualSerialPort

ManagementModule

RIP = OFF

Eth

VirtualSerialPort

ManagementModule

RIP = OFF

IP Addr 192.168.205.6IP mask 255.255.255.252


service channel

Eth

VirtualSerialPort

ManagementModule

RIP = OFF


IP Addr 192.168.205.9IP mask 255.255.255.252

Hop 1

Hop 2


Eth

VirtualSerialPort

ManagementModule

RIP = OFF

IP Addr 192.168.205.13IP mask 255.255.255.252


service channel

Eth

VirtualSerialPort


IP Addr 192.168.205.10IP mask 255.255.255.252

Hop 3

ManagementModule

RIP = OFF

IP GW 192.168.205.1Route add 192.168.205.4 Mask 255.255.255.252 192.168.0.2Route add 192.168.205.8 Mask 255.255.255.248 192.168.0.2

IP GW 192.168.0.1Route add 192.168.205.8 Mask 255.255.255.248 192.168.205.6




Route add 192.168.205.0 Mask 255.255.255.240 192.168.204.1

IP GW 192.168.0.9

Figure 3.19. The IP configuration of the management channel via three 1+0 hops with the RIP II switched off in each IDU; for proper routing between IDU management modules, the default gateway and static routes must be set for each module


51

Examples of service channel configuration in 1+1 mode

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON

Eth

VirtualSerialPort

ManagementModule

RIP = ON





IP Addr 192.168.206.10IP mask 255.255.255.0

Console IP address: 192.168.205.1, 255.255.255.0Route Add 192.168.206.0 Mask 255.255.255.0 192.168.205.10

IP sideaddr 192.168.205.11 IP sideaddr 192.168.206.11

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON

Eth

VirtualSerialPort

ManagementModule

RIP = ON

IP Addr 192.168.205.11IP mask 255.255.255.0



IP Addr 192.168.206.11IP mask 255.255.255.0

IP sideaddr 192.168.205.10 IP sideaddr 192.168.206.10

Figure 3.20


52

Ethernet

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON

Telnet console/Web clientIP address: 192.168.204.2




IP Addr 192.168.205.9IP mask 255.255.255.248


Router(RIP = OFF)

Eth

VirtualSerialPort

ManagementModule

RIP = ON

Hop 1


Route Add 192.168.205.0 Mask 255.255.255.240 192.168.204.1

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON

IP Addr 192.168.205.3IP mask 255.255.255.248



IP Addr 192.168.205.10IP mask 255.255.255.248

Eth

VirtualSerialPort

ManagementModule

RIP = ON

IP sideaddr 192.168.205.2



IP sideaddr 192.168.205.10

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON

IP Addr 192.168.205.17IP mask 255.255.255.248



IP Addr 192.168.205.11IP mask 255.255.255.248

Eth

VirtualSerialPort

ManagementModule

RIP = ON

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON




IP Addr 192.168.205.12IP mask 255.255.255.248

Eth

VirtualSerialPort

ManagementModule

RIP = ON

IP sideaddr 192.168.205.17

IP sideaddr 192.168.205.13

IP sideaddr 192.168.205.11

IP sideaddr 192.168.205.12Hop 2

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON

IP Addr 192.168.205.6IP mask 255.255.255.248



IP Addr 192.168.205.14IP mask 255.255.255.248

Eth

VirtualSerialPort

ManagementModule

RIP = ON

service channel

Eth

VirtualSerialPort

ManagementModule

RIP = ON

IP Addr 192.168.205.26IP mask 255.255.255.248



IP Addr 192.168.205.25IP mask 255.255.255.248

Eth

VirtualSerialPort

ManagementModule

RIP = ON


IP sideaddr 192.168.205.26

IP sideaddr 192.168.205.14

IP sideaddr 192.168.205.25Hop 3

Figure 3.21. The IP configuration of the management channel via three 1+1 hops; Note: the RIP II must be switched on in each CFM-M-MUX IDU with alarm (I/O) ports (DB-44 connectors) for 1+1 configurations.


53

3.9 Algorithm of LCD Operation

Management ControllerBoot-up

Enter ispressed

Status Displaymode

IDU is powered on Hardware resetbutton is pressed

Perform RestartCPU from menu

Setup mode

NO

YES

YES

NO

Jump 1 level up on theSetup mode menu tree

Clear is pressed, - in the Setup modemenu tree level lower than the top level

YES

Clear is pressed,- at the top level

of the Setupmode menu tree

Idle for about 10seconds ?

NO

Flow Chart 1. LCD operation

3.10 Replacing the Indoor Unit

Before replacing the IDU, verify the configuration of Radio if possible, - inspect the channel and transmit power settings. Then configure the new IDU in one of the following ways:

− delete the bootstrap via Telnet or serial console using cfg clear command, or − configure Radio channel and transmit frequency as needed (from LCD or via

management console);


54

In order to replace the faulty IDU while in operation, take the following steps:

− Disconnect the faulty IDU from the Radio: disconnect the N-type female connector; unplugging of power is optional;

− Connect the new IDU: if the new IDU is previously configured (the transmit power and channel

settings are made and the configuration is saved), the Radio will apply these settings after the management controller will be restarted,

if configuration script (bootstrap) is empty or does not contain entries on channel and transmit power, the Radio will keep the configuration that was last received from IDU;

− Restart the management controller, for instance, using RestartCPU option on the LCD.

3.11 Default Settings

Parameter name or command line Parameter/description

Telnet / serial LCD Default value/setting

Tx/Rx channel Chan Chan

In the middle of the band covered by Radio

Transmitter power TxPower Tx Power Off Rx signal level by which the Radio Alarm is turned on RxAlarmLevel RxAlarmLev

Auto Parameter value is obtained from ODU.

Fdx/Hdx port mode and speed for Ethernet bridges

Bridge Bridge Auto

Management controller IP address

IP addr IP 192.168.205.10 or 192.168.206.10

Management controller IP address netmask

IP mask Netmask 255.255.255.0

IP address of the gateway to the service channel

IP gw Gateway 255.255.255.255

IP address of the local virtual serial port of service channel

IP seraddr Local IP 192.168.0.10

IP address of the remote virtual serial port of service channel

IP remaddr Remote IP 192.168.0.11

IDU name Name - SAF IDU capacity capacity Capacity (customer specified) Multiplexer slot speed settings

muxspeeds MUX speeds All slots 0 Mbps (for all IDU capacities)

SNMP read community name SNMP community read

- Not specified

SNMP write community name SNMP community write

- Not specified

IP address of the SNMP trap manager

SNMP trap - 255.255.255.255 -> trap manager not specified

Web page refresh time Webrefresh - 5 seconds Username and password for serial console Enable password -

(password disabled, - no password required to connect via serial port)

Access number for LCD/Keypad

Panel access Access code 0 (disabled)

Username and password for Web management

WWWuser - Username and password not specified

Username and password for Telnet terminal

Telnetuser - Not specified

Configuration of Radio parameters from the Web terminal

Enable rfweb - (disabled)


55

3.12 Automatic Transmit Power Control (ATPC)

The ATPC feature is disabled by default. To enable it, use ‘ATPC enable’ command.

3.12.1 ATPC Algorithm

The local IDU receives from the far-end IDU information (each second) about Rx level through the service channel; depending on the received Rx level parameter, the local IDU adjusts the transmitter power according to the algorithm shown below.

Rx level - the the Rx level figure received from the far-endRx max - maximum permissible Rx level at the far-endRx min - minimum permissible Rx level at the far-endBER min - minimum permissible BER level at the far-endTx level - current transmitter power at the local site (Tx power)Tx max - maximum permissible Tx power at the local siteTx min - minimum permissible Tx power at the local siteDelta - the value by which the Tx power is increased or decreasedaccording to far-end Rx level indication (1 dBm by default)

Rx level indication received from far end

Rx level < Rx min ?

Rx level > Rx max ?

Tx level = Tx max ?

Tx level = Tx min ?

NO

YES Increase Tx level by ‘Delta’NO

END

YES

YES Decrease Tx level by ‘Delta’NO

YES

NO

END

BER level > BER min ? Tx level = Tx max ?YES NO

YES END

Increase Tx level by ‘Delta’

BER level received from far end

Check info from far end

Far end info OK

Link failure - Sync Loss and/or RAIalarm is switched on. Tx level is setto maximum.

Tx level = Tx max

END

NO

YES

NO

Figure 3.22. ATPC algorithm

3.12.2 ATPC commands

Please refer to chapter 3.5.


56

3.13 Configuring Radio Parameters

3.13.1 Default ODU Settings

The Outdoor Units are shipped with disabled Transmitter (TxPower OFF) and channel is set to one in the middle of respective A or B side of the Low or High subband (Radio types: LA, HA, LB, HB), or in the middle of the whole Low or High subband (Radio types: L and H).

3.13.2 Configuring Tx Frequency

The Tx frequency of the CFM LM and the CFM L4 type ODUs can be adjusted in the following ways:

1) It can be set through “ODU Chan” item of IDU LCD menu system.

If this item is chosen, display indicates:

where “Odu Chan” corresponds to Tx channel number and “Tx” indicates appropriate frequency in MHz.

Operator sets desired channel number scrolling through values with “Up” or “Down” buttons and confirming the choice with “Enter” button.

2) The Tx frequency can be set using “Chan” command from serial or Telnet management terminal, example: Chan 22

22 – channel number.

Since the telemetry data is transmitted between the ODU and the IDU, the concordance of Tx frequency to Low or High band side is detected automatically, and when the Tx channel is configured from the IDU LCD, the LCD displays frequencies within the subband (Low or High) that is covered by the Radio. However, if the ODU covers only a half of the subband (e.g., LA, HA, LB or HB, - depends on the duplexer filter within the ODU), the user should only choose from those Tx frequencies (channels) that are covered by the half of the subband specific to the Radio.

If a fault occurs in the ODU that prevents the transmission of telemetry data, the IDU LCD shows “No data from ODU”.

The Rx frequency is set automatically by Tx frequency.

3.13.3 Configuring Tx Power

The Tx Power level of the CFM series ODU can be adjusted in the following ways:

1) It can be set through “ODU Tx Power” item of IDU LCD menu system.

2) The Tx Power can be adjusted using Txpower command from Telnet or serial terminal, example: Txpower +10

The Tx power range depends on radio frequency used and on particular model. Tx power can be adjusted in steps of 1 dBm as well as turned off (Txpower off).

To avoid possible interference with other radio equipment, the default setting is “OFF”.

3.13.4 Evaluating RSL from RSSI signal

The following chart and table shows typical relationship of the received signal level (Rx level) displayed by IDU vs. RSSI port output voltage (RSSI – Received Signal Strength Indicator). The RSSI port is located on ODU. The evaluated Rx level has the error +/-2 dBm.

ODU Chan = xxx Tx = xxxxx.x MHz


57

-90 0-85 0,1-80 0,2-75 0,3-70 0,4-65 0,5-60 0,6-55 0,7-50 0,8-45 0,9-40 1-35 1,1-30 1,2-25 1,3-20 1,4-15 1,5-10 1,6

Displayed RSL, dBm

RSSI,V

Typical RSSI=f(RSL) chart

0,00,10,20,30,40,50,60,70,80,91,01,11,21,31,41,51,61,7

-90 -85 -80 -75 -70 -65 -60 -55 -50 -45 -40 -35 -30 -25 -20 -15 -10 -5

Displayed RSL, dBm

RSS

I por

t out

put,

V

3.14 Performing Loop-back Tests

Loopback tests are accessible using local or remote management methods.

All baseband and RF loopbacks (local and remote) for safety purposes can be set on a fixed time interval only. The interface loopbacks (E1, V.35) do not have time limit and must be switched off manually.

3.14.1 Setting Loop Tests from IDU LCD/Keypad

From the IDU LCD all loop tests are set on 1 minute time interval. • Baseband loopback:

From status display mode do the following: Press “ENTER” to enter setup mode → select “Loopbacks” → select “BB loopback” → “Change BBloop” → “ON” to set the digital baseband loops or “analog“ to set the analog baseband loop → select “Yes”.

• RF loopback: From status display mode do the following: Press “ENTER” to enter setup mode → select “Loopbacks” → select “RF loop ON” → select “Yes”.

• V.35 interface loopback: From status display mode do the following: Press “ENTER” to enter setup mode → select “Modules” → select “Module # V35” → select “V.35 Loopback” → “Change Loopback”, switch over to ON and confirm.

• E1 interface loopback: From status display mode do the following: Press “ENTER” to enter setup mode → select “Modules” → select “Module # 1E1” → “loopbacks” → select “Analog loop” for analog loopback (non-dual), “Digital loop” for digital loopback or “Remote loop” for remote loopback → “Change”, switch over to ON and confirm.

• Ethernet interface loopback: not available.

(!) The RSSI port is typically labelled with RSSI . The ODUs which does not have such label (ODU v2.22 and lower & ODU processor board rev. 083 and lower) do not correspond to the table and graph given above; the maximum level of RSSI voltage (at peak RSL) for these ODUs may vary from 1.2 up to 2 volts.


58

3.14.2 Setting Loop Tests from Telnet/serial terminal

From the remote management terminal, the loopbacks can be activated using the following commands:

• V.35 interface module loopback:

Use command “Mod # setV35 loop on|off”, # - MUX slot number

Example: mod 3 setv35 loop on (see also syntax notes in Chapter 3.5).

• E1 interface module loopback: “Mod # setE1 loop off|analog|digital|remote”, if argument is “analog” - analog loopback is activated, “digital” activates digital loopback, “remote” – remote loopback, “off” – switch off any E1 interface loopback (for details refer to Chapter 3.14.6), # - MUX slot number.

• Baseband loopback: “BBloop on|analog|off [duration]”. Duration is set in minutes as values from 1. If duration is not specified the loopback will be set on 1 minute. There are two baseband loop tests available:

− Analog: if setting analog loopback, use “BBloop analog” command, analog loopback is not dual.

− Digital: if setting digital loopback, use “BBloop on” command, digital loopback is dual.

• RF loopback:

“RFloop on|off [duration]”, duration = 1 min by default.

3.14.3 Radio loopback

Radio (RF) loopbacks can be set on a fixed time interval only; if using LCD/Keypad, the RF loop test is set for 1 minute. If setting RF loop from Telnet or serial console, the duration of radio loopback mode can be specified from 1 minute.

The radio loop is set in the ODU. Radio loopback mode is a special ODU operation mode, where the Rx frequency during the loopback mode is set equal to the Tx frequency. During radio loopback mode, the signal is transmitted and looped back through the duplexer filter to the receiver block. The radio loopback is not dual.

3.14.4 Base-band loopbacks

The baseband loop is set in the baseband modem in the IDU. Base-band loopbacks can be set on a fixed time interval only; if using LCD/Keypad, the base-band loop test is set for 1 minute. If setting base-band loopback from Telnet or serial console, the duration of baseband loopback mode can be specified from 1 minute.

There are two types of baseband loopbacks (both can not be activated simultaneously): − Digital baseband loopback: the signal from the ODU and from the multiplexer (or

Bridge board) in the baseband modem is looped back to the receiving device; the digital baseband loopback is dual (see Figure below);

(!) 1. Because of the frequency characteristic of the duplexer filter, in order to set the radio loop, the ODUs operating in the Low band side must be switched to the highest available frequency channel, but the ODUs operating in the High band side must be switched to the lowest available frequency channel; 2. Before setting the radio loop, the transmitter power should be switched to maximum level;

3. In CFM-18-LM and CFM-18-L4 ODUs the radio loopback mode is not available.


59

− Analog baseband loopback: the modulated signal on the baseband modem output is looped back to the receiving device and also passed further to the ODU.

Filter ComparatorClock recovery/Data decoding/Descrambling

ODU

Data coding/ScramblingFilter

Rx

Tx

Base-band Modem

Filter Comparator

ODU

Data coding/ScramblingFilter

Rx

Tx

Base-band Modem

Analog loop Digital loop (dual)

Clock recovery/Data decoding/Descrambling

Figure 3.23. Baseband loopback modes: signal is looped in the modem

3.14.5 V.35 Interface Module Loopback

The loopback mode of V.35 interface module is dual.

CPU

OUT

IN

I C2

Remoteloop

Localloop

V.35Interface

RxDDSR

RxC

SCTETxDDTR

RTS

bus

Mul

tiple

xer

Figure 3.24. V.35 Interface Module Loopback

3.14.6 E1 Interface Module Loopbacks

The E1 interface module supports analog, digital and remote loopback modes. Only one loopback can be active at a time for a single E1 channel, when other is switched on, the current one is switched off.

The digital loopback mode is dual since there are two loops closed, remote and local (see Figure below).

CPU

E1G.703HDB3

OUT

IN

Mul

tiple

xer

Remoteloop

Localloop

AnalogInterface

I C2bus

Figure 3.25. E1 Interface Module Digital loopback mode

CPU

E1G.703HDB3

OUT

IN

Mul

tiple

xer

AnalogInterface

I C2bus

Figure 3.26. E1 Interface Module Analog loopback mode


60

CPU

E1G.703HDB3

OUT

IN

Remoteloop

AnalogInterface

I C2bus

Mul

tiple

xer

Figure 3.27. E1 Interface Module Remote loopback mode


61

4 1+1 Configuration CFM-M-MUX with I/O (alarm) port (DB-44 connector) supports 1+1 configuration.

The 1+1 configuration are not supported for CFM-M4-MUX IDUs.

The CFM-M-MUX IDUs can be used to set up protected link (1+1) configuration, if IDUs are equipped with 1+1 user I/O card (alarm port). The 1+1 I/O card provides alarm ports (outputs) and user inputs, as well as capability of interconnecting the M-MUX with other M-MUX for 1+1 configuration.

The protected site consists of active terminal and protection terminal. Active terminal and protection terminal are connected via 1+1 link cable. Both active terminal and protection terminal consists of IDU and ODU.

The following 1+1 configurations are supported (for more information see chapter 4.1):

• Hot Standby (HSB), • Frequency Diversity (FD).

The CFM-M-MUX 1+1 protected link configuration is supported for the following traffic types:

• E1 traffic • Management Ethernet traffic • Ethernet traffic (with software version 4.40 and above and with 1-port 100Base-T

Fast Ethernet Bridge Modules – P/N CFGMBF05)

The CFM-M-MUX 1+1 configuration is not supported for V.35 traffic.

Switch / Hub

Ethernet

Transformer

(1...4) x E1

1+1 I/O card / Alarm port

Figure 4.1. CFM-M-MUX IDUs with 1+1 user I/O cards (alarm ports)


62

4.1 1+1 Protection Modes

The following picture shows the principle of E1 traffic switching in FD mode and HSB mode.

ODU

ODU

ODU

ODU

( ( ( ( ) ) ) )

( ( ( ( ) ) ) )

Different frequencies;All ODUs are operating(transmitting, receiving)

ODU

ODU

( ( ( ( ) ) ) )

Same frequency for both links;Only ODUs of the active linkare operating

FDmode

HSBmode

IDU

IDU1

2(off)

Tx

Tx

Rx

Rx

Tx

Rx

1(off)

2

IDU

IDU 1

2(off)

Tx

Tx

Rx

Rx

Tx

Rx

1(off)

2IDU

IDU1

2(off)

Tx

Tx

Rx

Rx

Tx

Rx

1(off)

2

Transformer

E1

E1 E1

E1

E1

E1

2(off)

1

1(off)

2

IDU

IDU 1

2(off)

Tx

Tx

Rx

Rx

Tx

Rx

1(off)

2

E1

E1

2(off)

1

1(off)

2

ODU

ODU

Figure 4.2. E1 traffic switching principle for FD and HSB mode; all switches (at all four IDUs) are in position 1 or in position 2.

4.1.1 FD (Frequency diversity)

In FD mode, the outgoing (Tx) traffic at each site is passed to both ODUs, the transmitters of both ODUs are always switched on; the incoming signal (Rx) is picked from one of the IDUs, depending on the received signal level and alarm status of the link, as described in chapter 4.2.

4.1.2 HSB (Hot-standby)

In HSB mode, both the incoming (Rx) and outgoing (Tx) traffic is switched to either one link or other, only one link is operating; the transmitter of the inactive ODU is switched off at each side.

4.2 Traffic switching

The payload transmission is switched to be carried out via protection terminal if one of the following problems are detected in active terminal:

• Power failure, • IDU-ODU cable failure, • SL or RAI alarm switches on, • Rx level below threshold, • BER level above threshold.


63

4.3 Switching time

Traffic switching time (switchover time) is less than 50 ms (milliseconds) in case of

• Power supply failure; • IDU-ODU cable failure; • SL alarm; • RAI alarm (far-end SL alarm is switched on); • Rx level is too low (below the threshold level); • BER alarm is switched on.

4.4 E1 traffic switching

In 1+1 configuration, E1 ports on the active terminal and the protection terminal are connected in parallel. E1 ports on the active terminal and on the protection terminal receive the same data at the same time from WAN side. For impedance matching of paralleled E1 ports, impedance matching device – transformer are provided. E1 ports transmit data to WAN side only on the active terminal. Depending on IDU E1 ports, the following types of transformers applicable:

IDU

IDU

User equipment

1

Transformer:Unbalanced DB25Unbalanced DB25

IDU

IDU

User equipment

2

Transformer:Balanced DB25Balanced DB25

IDU

IDU

User equipment

3

Transformer:Balanced DB25 RJ45

4.5 Ethernet traffic switching

Ethernet traffic switching is implemented by means of Ethernet switch.

(!) Cables between IDUs and transformer are included with transformer.


64

4.6 V.35 traffic switching

CFM-M-MUX 1+1 configuration for V.35 traffic is not supported.

4.7 Management Ethernet traffic switching

Management Ethernet ports (both – from the active terminal and the protection terminal) of the protected site are connected to the Management network via Ethernet switch or Hub.

Management system can manage both, local – active and protection terminals at the same time. The remote terminals - active and protection terminals are reached via service channel over the active link.

Management system supports RIP2; new routing tables are transmitted over the management network in case if protection terminal takes over active terminal functions.

4.8 Ethernet traffic switching

CFM-M-MUX IDUs with software version 4.40 and above and with 1-port 100Base-T Fast Ethernet Bridge Modules (P/N CFGMBF05) installed support Ethernet traffic switching. Link status of Ethernet module in case of switching will show up as “Disabled”, and after several seconds traffic will be switched to protection terminal module. Switching conditions are listed in Chapter 4.2. Link status can be seen using command “mod # stat” in CLI.

4.9 Commands for Telnet/serial terminal

Please refer to chapter 3.5 for Console/Telnet commands related to 1+1 configuration.

4.10 IP configuration for 1+1 link

The following picture shows an example of IP configuration for 1+1 link (see also examples in Chapter 3.8). To test this configuration, proceed as follows:

- Open remote Telnet connection to IDU 1’ (or IDU 2’) and enter command ‘switch active’ if IDU is standby or ‘switch standby’ if IDU is active.

- If the Telnet session does not disconnect, the IP settings are properly configured.


65

IDU 2

ip addr 192.168.205.10ip mask 255.255.255.0ip seraddr 192.168.205.10ip remaddr 192.168.206.10ip remmask 255.255.255.0ip sideaddr 192.168.205.11

IDU 1 IDU 1'

IDU 2'

Managementconsole

Eth

Eth

Eth

Eth




Figure 4.3

4.11 Hardware Installation

E1 traffic cable restrictions: the cable length between transformer box and User equipment must not exceed 220 meters (750 feet).

User equipment

IDU

Length must notexceed 220 meters(750 feet)

IDU

Transformer

4.12 Replacing faulty 1+1 CFM-M-MUX IDU

In case if the switchover has occurred due to IDU failure, the faulty CFM-M-MUX with I/O (alarm) port should be replaced in the following order:

1) Switch off the power supply from the faulty IDU,

2) Disconnect all cables from faulty IDU,

3) Connect all cables to new IDU, - traffic cable and IDU-ODU cable.

4) Switch on the power supply for the new IDU.

(!) • SLIP port address must be equal to Ethernet port address (ip addr = ip seraddr).

• RIP must be enabled at both IDUs.


66

5 Pinouts

5.1 Management port pinouts

5.1.1 RS232

5.1.2 Ethernet

Standard Ethernet patch cables should be used with IDU management Ethernet port.

5.2 Alarm interface (I/O Port) pinouts

5.2.1 Alarm port specification for CFM-M-MUX (1+0) (DB-25 connector)

54321 876 131211109

17161514 21201918 25242322

Figure 5.1. DB-25 Male connector pin layout

The pin assignments for relay outputs are the following: Output A

(Power on\off),

Pin 2 - common

Output B

(SL alarm),

Pin 4 -common

Output C

(RAI alarm),

Pin 6 -common

Output D

(RA alarm),

Pin 8 -common

Pair of pins 1-2 2-14 3-4 4-16 5-6 6-18 7-8 8-20

Type: NC* or NO**

NO NC NO NC NO NC NO NC

NC* - Normally Closed

NO** - Normally Open

(!) To connect IDU to PC via RS-232 port, a “straight through” (modem) serial cable is required.

Unassigned

Unassigned

DB9 Female Connector

Received from DTE

Transmitted from DCE

Transmitted Data

Received Data

DTE Ready

Signal Ground

DCE Ready

Request to Send

Clear to Send

Shield

1

2

3

4

5

6

7

8

9


67

Input pins: Input A Input B Input C Input D

Pin 10 11 12 13

GND pins (closest) 22 23 24 25

Electrical specifications of the outputs of the alarm interface port:

Rated load: 0.5 A at 125 VAC; 2 A at 30 VDC

Max. switching current: 2 A

Max. switching voltage: 250 VAC, 220 VDC

Electrical specifications of the inputs of the alarm interface port: Impedance: 4,7 kΩ,

U”0” = 1…2 V DC,

U”1” = 2,4…48 V DC.

5.2.2 Alarm port specification for CFM-M-MUX (1+1) (DB-44 connector)

GNDGND

GND

INPUT 2

INPUT 3

INPUT 4

GND

INPUT 1

Relay D: NCRelay D: common

Relay D: NORelay C: NC

Relay C: commonRelay C: NO

Relay B: NCRelay B: common

Relay B: NO Relay A: NCRelay A: commonRelay A: NO

NC

NO

Common

NC - Normally closedNO - Normally open

Figure 5.2. DB-44 HD port pinouts

The pin assignments for relay outputs are the following: Output A

(Power on\off)

Output B

(SL alarm)

Output C

(RAI alarm)

Output D

(RA alarm)

Pair of pins

33-34 34-35 36-37 37-38 39-40 40-41 42-43 43-44

Type: NC or NO

NO NC NO NC NO NC NO NC

Electrical specifications of relay outputs: Rated load: 0.5 A at 125 VAC; 2 A at 30 VDC

Max. switching current: 2 A

Max. switching voltage: 250 VAC, 220 VDC


68

Electrical specifications of inputs: Impedance > 7 kΩ R”0” = 1 kΩ max. R”1” = 12 kΩ min. Open contact voltage: +5V Contact shortcut current: 0,7 mA.

5.3 Traffic port pinouts

5.3.1 V.35 traffic port pinouts

Signal M34 Pin 60 Pin Cisco*

P GND A 46 S GND B 45 RTS C 42 CTS D 35 DSR E 34 DCD (RLSD) F 33 DTR H 43 TxD+ P 18 TxD- S 17 RxD+ R 28 RxD- T 27 SCTE+ U 20 SCTE- W 19 RxC+ (SCR+) V 26 RxC- (SCR-) X 25 TxC+ (SCT+) Y 24 TxC- (SCT-) AA 23

Interconnectable pinouts at the Cisco equipment side:

48 & 49 50 & 51 & 52 53 & 54 & 55 & 56

Notes:

* This information is for user’s reference only

P GND – Protection Ground

S GND – Signal Ground

5.3.2 E1 port pinouts

RJ-45 E1 pinouts

The pinouts of RJ-45 ports for 1xE1 and 4xE1 modules are shown in Figure 5.3.

1 2 3 4 5 6 7 8

IN(Rx)

1 2 3 4 5 6 7 8

GND GNDNot

usedOUT(Tx)

E1 portINPUT (Rx)

OUTPUT (Tx)

RJ-45 pin numbering E1 port pinouts

Figure 5.3. E1 traffic port pinouts

(!) All pinouts for E1 transformer ports are the same as on IDU.


69

E1 unbalanced (75 Ω) DB-25 traffic port pinouts

See Figure 5.1 for DB-25 male connector pin numbering.

1 INPUT CH4

2 OUTPUT CH4

4 INPUT CH3

5 OUTPUT CH3

7 INPUT CH2

8 OUTPUT CH2

10 INPUT CH1

11 OUTPUT CH1

All other pins are GND.

E1 balanced (120 Ω) DB-25 traffic port pinouts

According to Figure 5.1:

14, 15 INPUT CH4

3, 4 OUTPUT CH4

17, 18 INPUT CH3

6, 7 OUTPUT CH3

20, 21 INPUT CH2

9, 10 OUTPUT CH2

23, 24 INPUT CH1

12, 13 OUTPUT CH1

All other pins are GND.


70

6 Mechanical data

IDU weight and dimensions

IDU model Weight without modules [kg]

Dimensions HxWxD [mm]

CFM-M-MUX 2.0 44x482x284

482

284

44

Dimensions of the IDU

Weight and dimensions of traffic modules

Module Weight [g] Dimensions HxWxD [mm]

(including connectors)

Low capacity 10\100Base-T 2-port Ethernet bridge

55 43x59x125

10\100Base-T 1-port Ethernet bridge 55 43x59x125

1xE1 75 43x59x143

4xE1 w\ DB25 port 76 43x59x126

4xE1 w\ RJ-45 ports 77 43x59x125

V.35 86 43x59x139


71

7 SAF Tehnika A/S Contacts Most up to date contacts of SAF Tehnika A/S could be found at Web site www.saftehnika.com.

SAF Tehnika A/S technical support could be reached at:

- Email: [email protected]

- Telephone: +371 67046840

- Fax: +371 67046809


72

8 References The following documents comprise the information about CFM-M-MUX IDU. These documents can be ordered from SAF Tehnika or its sales representative.

• SAF CFM LM Series Microwave Radio System Product Family: Technical Description - this document is a generic technical description of the CFM-LM ODU and IDUs that are compatible with it, it comprises the installation and commissioning issues and respective accessories, functional descriptions, technical data, a.o.

• Channel Plans - this document contains all available frequency channel plans for bands from 7 GHz to 38 GHz.

cfm-m m4-mux_td_en_v 2 1

Documents