Manual Radio SAF

CFM-M-MUX
Indoor Unit
Indoor Unit Management System

Technical Description and
Configuration Guide
© SAF Tehnika A/S 2006

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 ..............................................................................................................9
2.4.1 V.35 Interface Module ............................................................................................................... 9
2.4.2 E1 Interface Module ................................................................................................................. 10
2.4.3 4xE1 Interface Module ............................................................................................................ 11
2.4.4 100Base-T Fast Ethernet Bridge Modules ........................................................................ 12
2.5 Labelling ..............................................................................................................................14
3 Configuration and Management .................................................................................15
3.1 LCD/Keypad .......................................................................................................................15
3.1.1 “Status Display” Mode of the IDU LCD Management Interface ............................... 15
3.1.2 “Setup” Mode of IDU LCD Management Interface ........................................................ 18
3.1.3 Interface Module LEDs ............................................................................................................ 21
3.2 Resetting the IDU ............................................................................................................22
3.3 RS-232 Serial Management Port ...............................................................................23
3.4 Ethernet Port .....................................................................................................................26
3.4.1 Web Management ..................................................................................................................... 26
3.4.2 Telnet management ................................................................................................................. 29
3.4.3 SNMP Management................................................................................................................... 29
3.5 Command Interface ........................................................................................................33
3.5.1 Working with configuration script ....................................................................................... 40
3.5.2 File system................................................................................................................................... 41
3.5.3 Storage of radio parameters................................................................................................. 43
3.5.4 Security commands.................................................................................................................. 44
3.6 Updating management software................................................................................46
3.6.1 Uploading file via Ethernet management port (TFTP) ................................................. 47
3.6.2 Uploading file via serial port (Xmodem)........................................................................... 48
3.7 Alarms..................................................................................................................................50
3.7.1 Alarm Port (I/O Port) ............................................................................................................... 50
3.8 Configuring Management Service Channel ............................................................51
3.9 Algorithm of LCD Operation.........................................................................................56
3.10 Replacing the Indoor Unit.............................................................................................57
3.11 Default Settings................................................................................................................58
3.12 Configuring Radio Parameters ....................................................................................59
3.12.1 Default ODU Settings............................................................................................................... 59
3.12.2 Configuring Tx Frequency ...................................................................................................... 59
3.12.3 Configuring Tx Power............................................................................................................... 60
3.12.4 Evaluating RSL from RSSI signal ........................................................................................ 60
3.13 Performing Loop-back Tests........................................................................................61
3.13.1 Setting Loop Tests from IDU LCD/Keypad....................................................................... 61
3.13.2 Setting Loop Tests from Telnet/ASCII terminal............................................................. 61
3.13.3 Radio loopback ........................................................................................................................... 62
3.13.4 Base-band loopbacks ............................................................................................................... 62
3.13.5 V.35 Interface Module Loopback ......................................................................................... 63
3.13.6 E1 Interface Module Loopbacks ........................................................................................... 63
4 Using CFM-M-MUX in 1+1 Configuration ...............................................................64
4.1 1+1 Protection Modes....................................................................................................65
4.1.1 FD (Frequency diversity)........................................................................................................ 65
4.1.2 HSB (Hot-standby) ................................................................................................................... 65
4.2 Traffic switching ...............................................................................................................65
4.3 Switching time ..................................................................................................................66
4.4 E1 traffic switching..........................................................................................................66
The CFM-M-MUX IDU Management System Technical Description and Configuration Guide
Rev. 1.8 ● © SAF Tehnika A/S 2006
2
4.5 Ethernet traffic switching..............................................................................................66
4.6 V.35 traffic switching .....................................................................................................67
4.7 Management Ethernet traffic switching ..................................................................67
4.8 1+1 Configuration ...........................................................................................................67
4.8.1 Console/Telnet Commands.................................................................................................... 67
4.8.2 IP configuration for 1+1 link................................................................................................. 67
4.9 Hardware Installation.....................................................................................................68
5 Pinouts.......................................................................................................................................69
5.1 Management port pinouts ............................................................................................69
5.1.1 RS232 ............................................................................................................................................ 69
5.1.2 Ethernet ........................................................................................................................................ 69
5.2 Alarm interface (I/O Port) pinouts ............................................................................70
5.2.1 Alarm port specification for 1+0 CFM-M-MUX configurations................................... 70
5.2.2 Alarm port specification for 1+1 CFM-M-MUX configurations................................... 71
5.3 Traffic port pinouts..........................................................................................................72
5.3.1 V.35 traffic port pinouts.......................................................................................................... 72
5.3.2 E1 port pinouts........................................................................................................................... 73
6 Mechanical data....................................................................................................................74
7 SAF Tehnika A/S Contacts .............................................................................................75
8 References...............................................................................................................................75
3
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,
covering hardware features, built-in management system, configuration
functionality, etc.
The CFM-M-MUX is part of SAF Tehnika’s CFM series digital microwave radio
product family providing:
- 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.
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 E1, 4xE1, V.35 and 10/100Base-T
interfaces (for more information please refer to chapter 2.4).
- Local and remote management (incl. Web, Telnet, SNMP, ASCII),
- 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 maximum WAN capacity 34.368 Mbps; the capacity is software
selectable. Any capacity can be selected for any frequency band.
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.
4
2 Indoor Unit Appearance
2.1 Installation Notes

The CFM-M-MUX IDU is implemented as 19” rack mountable Aluminium 1U high
unit, 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, please see picture below.
12 cm
(4.72 ")
23 cm
(9.10 ")
4 cm
(1.57 ") 10 cm 8 cm
(3.94 ") (3.15 ")
48.6 cm (19.29 ") V.35 E1
42.6 cm (16.93 ")
The CFM-M-MUX IDU provides four sockets – module slots, for installation of
interface modules. For information about what data rate each multiplexer slot
supports, please see Table 9.
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.
CLEAR
AIS
RX
RX
TX
TX
SL
LB
LB
- 48V + CFM-M-MUX
SYNC
OUT IN
RADIO E1
REMOTE ENTER
ALARM
V.35
Figure 1. 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.
CLEAR
- 48V +
SYNC
RADIO
REMOTE ENTER Slot 1 Slot 2 Slot 3 Slot 4

ALARM
Figure 2. Numbering of module slots
5
2.2 Ports
The CFM-M-MUX IDU provides:
- Interfaces:
- Radio Unit (ODU), N-type Female connector;
- The CFM-M-MUX IDU provide 1 up to 4 slots for installation of traffic port
modules (1 module per slot), 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 1+1 configuration support, 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 1. Connectors
Port/connector Front panel connectors

+-48V Power connector, IDU should be powered from 20V – 60V
(power socket) 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 Female connector, the cable should be connected
(N-type connector) to the Radio Unit (ODU);
RS-232 RS232 management port for connection of ASCII console
(DB9 connector) (or analog line modem for the remote connection of ASCII
console). This port is also used to update management
software.
2x10\100Base-T Ethernet switch management ports, for Web or Telnet
Ethernet ports management; the ports have bridging function.
(RJ-45 socket)
DB25 connector Alarm port. This feature is optional.
Alarm port Serial management port Ethernet management port ODU port Grounding screw
Figure 3. Rear panel
6
2.3 LEDs
Table 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/ASCII console. The
default value for this parameter is -77 dBm;
− 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 syntheser 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).
Note: the RA LED will also switch on if the Radio loopback
is active and/or if the transmitter power is switched off.
The RA LED is updated one time per second.
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 ASCII terminal. The BER margin
can be changed form Telnet or ASCII console, for
information see chapter 3.5.
Note: The LEDs located on interface modules are described in chapter 3.1.3,
page 21.
7
Table 3.
Other front panel LED signals

Alarm Description
Wrong In case if due to wrong MUX slot speed configuration
Capacity − 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 If IDU hardware failure occurs, SYNC, RADIO, REMOTE and
HARDWARE ALARM LEDs simultaneously will be switching on and off.
FAILURE
Rear panel LEDs are shown in Figure 4.
Hidden reset Ethernet ODU Grounding

Serial management button management ports screw
port
port
Indicates operation of the Ethernet link\activity 100 Mbps speed

management module CPU LED LED
Figure 4. Rear panel LEDs
8
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 M.34 connector.
For description of LEDs, see chapter V.35 Interface Module LEDs on page 21.
RX
TX
LB
SL
V.35
Figure 5. V.35 module (front)
9
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.
Table 4. E1 Interface module ports
Out, Two BNC connectors of the 75 Ω unbalanced port provide means to

In 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.
Note: use either IDU keypad or console to switch between BNC and RJ-45 ports,
this is described in chapters 3.1.2 and 3.5 respectively.
Table 5. 1xE1 module LEDs

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.
AIS
RX
LB
TX
OUT IN
E1
Figure 6. 1xE1 module (front)
10
2.4.3 4xE1 Interface Module
The 4E1 module provides four E1 ports with RJ-45 connectors (120 Ω interfaces),
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
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 color; for details see Table 6.
Table 6. Description of LEDs
E1 port LED
Color Description
(highlighted)
Green Indicates normal operation of the channel, no

(loop-back LED yellow or problems with signal reception.
off)
Red Constant red indicates that E1 signal is lost. If

(loop-back LED yellow or red flashes momentarily, the bipolar violation
off) (line code error) was received from user
equipment.
Blinking green and red AIS signal is being received from user
(loop-back LED yellow or equipment.
off)
Yellow loop-back LED (loop- When loopback LED is switched on, analog,
back switched on) digital or remote loop-back mode is active for
that channel.
No LED is lit Channel is switched off.
2 E1 4
1 2 3 4
U75 E1 1 3
(1) (2)
Figure 7. 4xE1 modules: (1) with DB25 ports; (2) with RJ-45 ports
11
2.4.4 100Base-T Fast Ethernet Bridge Modules
The 1-port FREB module and 2-port FREB module (Fast Remote Ethernet
Bridge) performs bridging between LAN ports and WAN port, and between both
LAN ports. The FREB modules terminate any capacity up to 34 Mbps from the
multiplexer on 100Base-T ports with RJ-45 sockets (UTP). 1-port module has one
100-Base-T port; 2-port module has two 100-Base-T ports.
Feature summary:
1-port 100Base-T Fast Ethernet Bridge 2-port 100Base-T Fast Ethernet Bridge
Module Module
• 10M/100M Half/Full duplex auto- • 10M/100M Half/Full duplex auto-
detect detect
• TP auto MDIX TX/RX swap • TP auto MDIX TX/RX swap
• 10.000 MAC addresses table • 2048 MAC addresses table
• Store and forward architecture • Store and forward architecture
• Aging function • Aging function
• Supports up to 1760 byte packets • Supports up to 1522 byte packets
• Supports 802.1Q VLAN. • Supports 802.1Q VLAN.
For more information about 1-port module throughput, see Table 7.

Table 7. 1-port 100Base-T Ethernet module throughput for various frame sizes
Total Throughput,
Frame
[Mbit/sec]
Size,
[bytes] Autosensing
100 FDx mode
mode
64 30.260224 30.260224
128 31.643648 30.047232
256 32.466944 32.466944
512 33.09568 32.182272
1024 33.71008 33.71008
1280 33.83296 33.83296
1518 34.221792 34.221792
The maximum available WAN traffic capacity of the bridge is possible if modules
are 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 33.092 Mbps
(total capacity 34.368 Mbps).
Ethernet link/activity LED
(green), if flickers, indicates
data transmission,
100 Mbps speed LED

(yellow), -
if this LED is switched on,
the port speed is 100 Mbps
Figure 8. 2-port FREB module LEDs
12
100Base-T modules comply to:
• IEEE Std. 802.1D Media Access Control (MAC) Bridging capabilities (without
the spanning tree algorithm),
• IEEE Std.802.1Q (without prioritization),
• IEEE 802.3.
13
2.5 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).
Product type (internal use only) Hardware

version\
Product model specification
name
Product number
Consecutive
4-digit Product code number
assigned to Product Number
Figure 9. IDU label
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, page 56.
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 8.
15
Table 8. 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 Table 9 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 Syntheser 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 counter was reset on power up.
No data from ODU Indicates connectivity status between IDU and ODU:
RF Cable – OFF “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.
PW max = 20 Indicates maximum transmitter power.
RxAlarmLev =-77 Indicates the Rx level (in dBm) at which the Radio
Alarm is switched on.
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.
16
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.
BBLoopback=OFF Indicates if the base-band loopback is switched on or
off.
17
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, page 56.
Table 9
Parameter Description
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 ASCII 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 8.
Write config Saves current settings in EEPROM of management
controller, these settings will take effect the next time when
IDU will be restarted.
Loopbacks - RF loopback OFF – switch off the radio loopback
(local),
- RF loopback ON – switch on the radio loopback,
- BB loopback OFF - switch off the baseband loopback
(any),
- BB loop analog – switch on the analog baseband loop,
- BB loopback ON - switch on the digital baseband
loopback.
Outdoor Unit - Tx Power - adjust the radio output power; the default
setting is “OFF”.
- 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 ASCII terminal using ‘muxspeeds’
command; the new configuration must be saved
using ‘write’ command.
18
16M MUX Sets the data rate for each multiplexer slot; use 1E1…4E1
speeds modes for E1 modules, and 2M…16M 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.
• 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 supports speeds 0…16 Mbps with 2 Mbps step;
slot 3 and 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
FOD 0M 1E1 0M
The numbering of slots is shown in Figure 2.
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 - 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;
- Netmask – specify netmask for Ethernet management
port; default value - 255.255.255.000
- 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.
Note: It is necessary to restart the management CPU for
any changes in IP settings to take effect.
19
Setup mode menu tree
Access code Change

Restart CPU * - current channel number
Reset Counters ** - 'Dloop' - digital loopback
Write Config *** - 'Aloop' - analog loopback
Loopbacks RF loopback ON
RF loopback OFF
BB loopback ON
BB loop analog
BB loopback OFF
Outdoor unit Chan ##* Change Chan ##
Tx Power Tx Power
Modules Module 1 F2Bridg Port 1 P1 connection
Port 2 Port 1 priority
P1 Flow Cntrl.
Module 2 E1 E1 Interface Ch. Interface
E1 Dloop** Change Dloop
E1 Aloop*** Change Aloop
Module 3 V35 V.35 Speed Change Speed
V.35 Loopback Change Loopback
V.35 Clock Change Mode
Module 4 4xE1 Port 1 Port 1 loopbacks P1 rloop
Port 2 P1 aloop
Port 3 P1 dloop
Port 4
Capacity Change capacity
16M MUX speeds Change
Service line Select local IP Change
Select remote IP Change
Sel. remote MASK Change
Ping remote Ping
Ethernet Select IP Change
Select NETMASK Change
Select Gateway Change
20
3.1.3 Interface Module LEDs
V.35 Interface Module LEDs

Table 10.V.35 Module LEDs (see Figure 5)
LED Color Name Function Direction
Data
Data activity - data is being
Transmitting
TX Green transferred from module's V.35 MUX*
Active
front port to multiplexer.
SL Red Signal Loss V.35 port failure.
Loopback on V.35 module is

Dual loopback, please
switched on, informing that
refer to chapter 3.13.5 for
LB Red Loopback Active the connection between
more information about
V.35 port and MUX board
V.35 module loopback.
is interrupted.
Data activity - data is being

Data Receiving received from multiplexer
RX Green MUX V.35*
Active board and transmitted to
module front port
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 Ethernet Link/Activity LED, if flickers indicates data transmission
Yellow 100 Mbps speed LED, if this LED is switched on, the port speed is 100 mbps
21
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 Restarts the management module. Resets
system using “Restart CPU” option all management counters.
or from the Telnet/ASCII console
using “restartcpu” command
Reset using hidden button at the Restarts both the multiplexer module and
rear side of the IDU (see Figure 4) the management module. Resets all
Note: 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
22
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 (ASCII console) provides the same management
functionality as Telnet terminal, for complete description of command interface
please refer to chapter 3.5.
IDU RS-232
PC/Terminal
IDU RS-232
Modem PC/Terminal
Modem
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 ASCII 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
- DTR override
The modem configuration then should be saved (typically with AT&W string).
ASCII console window
23
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.
4. Choose port (COM1 or COM2).
24
5. Set port settings (bits per second: 19200, data bits: 8, parity: none, stop
bits: 1, no data flow control).
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.
25
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.
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
ASCII terminal. If User Name and Password is not specified, the user will not be
able to open configuration pages (configure settings).
Main Web management 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
26
To check the status of each module, click on a Status link to open the module
status window.
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.
Main Configuration window (Radio parameter configuration is disabled)
27
By default, the Main Configuration window does not allow to configure 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 ASCII console.
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.
Modules Configuration window
28
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 ASCII 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.
− 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: techsupport@saftehnika.com,
- 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
29
MIB variables
The following table describes all variables defined in the MIB.
Variable Name Variable Type Value List Description

termProduct String Textual name of terminal type
termDescription String Textual description of terminal
termLocation String IDU name
termVersion String Textual version of management
software
termOperation Integer (32 bit) none(0) Terminal (IDU) operational
booting(1) status:
ok(2) none – not initialized;
testing(3) testing, illegalSpeed, error –
error(4) reserved
termIduTemperature Integer (32 bit) Temperature within IDU
(range: -128..127)
termRfCablePowerStatus Integer (32 bit) off(0) Indicates power consumption of
ok(1) the ODU: ok - acceptable level,
short(2) short - short circuit in cable,
error(3) off - too low power consumption,
error – internal fault
termUpTime Integer (32 bit) System up-time in seconds
termDownTime Integer (32 bit) System down-time in seconds
bbVersion String Textual version of the Base-band
controller software
bbOperation Integer (32 bit) none(0) Operational status of the Base-
booting(1) band modem:
ok(2) none – not initialized
testing(3) loopback – Base-band loop is set
loopback(4) on
illegalSpeed(5) testing, illegalSpeed, error –
error(6) reserved
bbLinkCapacity Integer (32 bit) Base-band link capacity in Kbps
bbLinkCapacityDescriptio String Comment on Base-band link
n
bbLoopback Integer (32 bit) off(0) Base-band loopback
digital(1)
analog(2)
bbSyncLostAlarm Integer (32 bit) none(0) The Sync Lost Alarm
on(1) none – Off
rfOperation Integer (32 bit) none(0) Operational status of the Radio:
booting(1) none – not initialized
ok(2) testing, error – reserved
testing(3) noDataFromODU – no data is
error(4) being received from ODU
noDataFromODU(5)
rfAlarm Integer (32 bit) none(0) Radio Alarm, none – off
on(1)
rfVersion String Textual version of the Radio
rfSide Integer (32 bit) low(0) Band side of the Radio: low or
high(1) high
rfChannel Integer (32 bit) Channel number
rfTxFrequency String Tx frequency
rfRxFrequency String Rx frequency
rfTxPower Integer (32 bit) Transmitter power
rfRxState Integer (32 bit) low(0) Reception status:
ok(1) low – Rx signal level
error(2) ok - normal
loopback(3) error - internal fault in the Radio
loopback – RF loop is set on
rfRxLevel Integer (32 bit) Received signal level [dBm]
rfCableAttenuation Integer (32 bit) Signal attenuation in ODU-IDU
cable (0…-20 db - proper
operation)
rfTxOut Integer (32 bit) error(0) Operation status of the ODU
ok(1) transmitter:
off(2) ok – proper operation
error – internal fault (no data
from ODU)
off – Tx power = off
30
rfTxPLL Integer (32 bit) error(0) Operation status of ODU Tx
ok(1) syntheser loop (PLL lock):
ok – normal operation
error - internal fault in ODU
transmitter
rfRxPLL Integer (32 bit) error(0) Operation status of ODU Rx
ok(1) syntheser loop (PLL lock):
ok – normal operation
error - internal fault in ODU
transmitter
rfOduTemperature Integer (32 bit) Internal temperature of ODU (0 C)
rfOduHumidity Integer (32 bit) low(0) Humidity level inside ODU:
high(1) low - acceptable moisture level
rfLoopback Integer (32 bit) off(0) RF loopback
on(1)
rfRxAlarmLevel Integer (32 bit) Rx level (in dBm) at which the Radio
Alarm is switched on
m1Type error(0) Module type:
e1(33) error – internal fault
v35(37) none – no module installed or the
bridge(43) module does not support data
none(255) exchange with the management
controller (e.g., due to the software)
m1Description String Description of the module
m1Version String Textual version of the module
m1Speed Integer (32 bit) Module data transfer speed in kbps
m1Operation Integer (32 bit) none(0) Operational status of the module:
ok(2) none – no data from the module
loopback(4) loopback – loopback is switched on
illegalSpeed(5) illegalSpeed – the speed
configuration of the MUX slot does
not mach the module speed
m1Rx Integer (32 bit) none(0) Rx statuss of the module:
ok(1) none – not defined
noSignal(2) noLink – for the REB module only
noLink(3) rxAIS – for the E1 module only
rxAIS(4)
m1Tx Integer (32 bit) none(0) Tx statuss of the module:
ok(1) none – not defined
noSignal(2) noSignal – for V.35 module and REB
txAIS(4) module (same as no link or LOS
alarm)
txAIS – for E1 module only (usually
switches on with the SL alarm)
m1Loopback Integer (32 bit) off(0) Loopback in the module
on(1)
analog(2)
m1RxInput Integer (32 bit) other(0) Rx input of the module:
coax(1) other – not initialised
rj45(2)
v35(3)
m1TxMode Integer (32 bit) other(0) Tx mode of the module (for the REB
halfDuplex(1) module only):
fullDuplex(2) other – not initialised
m1TxClockSource Integer (32 bit) other(0) Tx clock source of the module (for
master(1) the V.35 module only):
slave(2) other – not initialised
m1TxClockPhase Integer (32 bit) other(0) Tx clock phase of the module (for
normal(1) the V.35 module only):
inverse(2) other – not initialised
m1DataPolarity Integer (32 bit) other(0) Polarity of the data signal (for the
normal(1) V.35 module only)
inverse(2) other – not initialised
Note: there are more variables with the “m2”, “m3” and “m4” prefix in their names, they are analogical
to those with the “m1” prefix; the “m1” denotes to the module in the slot 1, “m2” – module in the slot
2, etc.
31
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 ASCII 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 and Table 3.
Cold-start The trap is sent each time the IDU is started.
Authentification failure The trap is sent each time the attempt occurs to read or write the
variable with incorrect community name.
32
3.5 Command Interface
The CFM equipment (IDU and ODU) can be monitored and configured using
command interface described in this chapter, connecting with
- ASCII 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 ASCII management.
Tips:
− To end Telnet or ASCII 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.
33
Common commands
Command Description
Time Show current date and time.
Time <YYYY-MM-DD Set the date and time. The clock is not available on the
HH:mm:ss> 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/ASCII 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 EPROM. This command saves all
current settings in EPROM, 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} Set baseband loopback, “on” – set digital loopback
[duration] (dual), “analog” – set analog loopback (non-dual), “off”
– suspend baseband loopback. Duration can be from 1
to 10 minutes, it is equal to 1 min. by default. Example:
BBloop on 3
RFloop {on | off} [duration] Set RF loopback, - “on” – set loopback, “off” – suspend
loopback. Duration can be from 1 to 10 minutes, it is
equal to 1 min. by default. 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 <alarmLevel> Set the Rx signal level at which the Radio Alarm is
switched on. For default value see Chapter 3.11.
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 9.
Disable {telnet | www | “telnet” – Disable Telnet interface
snmp | rip} “www” – Disable Web interface
“snmp” – Disable SNMP interface
“rip” – Disable RIP;
Notes:
- after the command is entered, it is necessary to
save the configuration in EPROM (use write
command) and restart the IDU for changes to take
effect.
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.
34
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 {-10|-9|…|0|+1|+2|…|+20 |off} 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 ASCII 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.
WWWuser <username> Specify username and password (1 - 20 symbols) to
<password> prevent unauthorized access from Web terminal.
FTPuser <username> Specify username and password (1 - 20 symbols) to
<password> prevent unauthorized connection to FTP server.
Telnetuser <username> Specify username and password (1 - 20 symbols) to
<password> prevent unauthorized access from Telnet terminal.
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 Set the data rate for each multiplexer slot. See Table 9 for
{slt1}+{slt2}+{slt3}+ more information about speeds supported by each slot.
{slt4} Example: muxspeeds rmn+2E1+2E1+2M – configures the
multiplexer slots.
Muxcapacity Change the multiplexer maximum WAN capacity. After the
{8M|16M|34M} capacity change, the user must manually reconfigure all MUX
slot speeds using ‘muxspeeds’ command; 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 E1 vers. 2
E1 impedance 120
TxAIS OFF
Enable Analog Loopback OFF
Enable Local Loopback OFF
Enable Remote Loopback OFF
RxAIS OFF
RxLOS OFF
Example for REB interface module:
SAF>mod 4 stat
Module Bridge vers. 1
Link ON
FDX ON
Filter ON
35
Mod detect Detects and displays a list of currently installed modules. This
detection procedure is carried out each time when management
controller boots up.
Mod dump Show a list of modules and contents of their respective CPU
registers (in hexadecimal system). This command is for diagnostic
purposes only.
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
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
IP remaddr <IPaddress> Set the IP address of the serial port of service channel
for the remote (far-end) IDU management module
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 M-MUX configuration only!
Set the IP address of the alternate link.
Route add <destinationIPaddr> Add a static route to the routing table. The variable
Mask [netmask] <gateway> “metric” is set to 1 by default. Example:
[metric] Route add 192.168.205.010 Mask 255.255.255.0
155.13.79.13 5
Route delete Delete a static route from the routing table.
<destinationIPaddr> [netmask]
SNMP community read Specify the SNMP community name of the agent to
<communityname> enable parameters to be read (not configured). The
default read community name is not specified.
SNMP community write Specify the community name of the agent to enable
<communityname> parameters to be written (configured). The default
write community name is not specified.
SNMP trap <IPaddress> Set the IP address of the management terminal with
the installed software for SNMP trap management
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 {Aloop | Set the analog, digital or remote loopback in the
Dloop | Remote | Off} module (Aloop – analog loopback; Dloop – digital
loopback, Remote – remote loopback, off – disable
current E1 module loopback).
Example: Mod 3 setE1 Dloop
Mod {1|2|3|4} setE1 {120 | 75} Set the impedance of E1 interface, 120 Ω or 75 Ω.
(for 1xE1 modules)
36
Configuring 4xE1 Interface Module parameters
Command Description
Mod {1|2|3|4} setE1 {port1 | port2 | Set the analog, digital or remote loopback in
port3 | port4} {Aloop | Dloop | the module (Aloop – analog loopback; Dloop –
Remote | Off} digital loopback, Remote – remote loopback, off
– disable current E1 module loopback).
Example: Mod 3 setE1 Dloop
Mod {1|2|3|4} setE1 {port1 | port2 | Enable/Disable the transmission of AIS signal
port3 | port4} {on | off} (for testing purposes).
Configuring V.35 Interface Module parameters

Command Description
Mod {1|2|3|4} setV35 speed {64 | 128 | 256 Set the speed of V.35 interface (in
| 512 | 1024 | 2048 | 4096 | 6144 | 8192} kbps).
Mod {1|2|3|4} setV35 phase {normal | Invert the RxC clock signal (it is
inverse} transmitted from V.35 module to user
equipment)
Mod {1|2|3|4} setV35 polarity {normal | Invert the incoming and outgoing data
inverse} 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
Configuring 2-port 100Base-T Ethernet Bridge Module

Command Description
Mod {1|2|3|4} setf2bridge {port1 | Configure port speed and duplex, 10hdx – 10
port2} connection {auto | 10hdx | Mbps half duplex, 10fdx - 10 Mbps full duplex, etc.
10fdx | 100hdx | 100fdx} Example: Mod 3 setf2bridge port1 connection
100fdx
The factory setting for both ports is auto.
Mod {1|2|3|4} setf2bridge {port1 | Configure port priority. The factory setting for both
port2} priority {low | high} ports is low.
Mod {1|2|3|4} setf2bridge {port1 | Enable or disable flow control for the specified
port2} flowcntrl {enable | disable} port.
Mod {1|2|3|4} statistics 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.
Configuring 1-port 100Base-T Ethernet Bridge Module
Command Description
Mod {1|2|3|4} setbridge Configure port speed and duplex, 10hdx – 10 Mbps
connection {auto | 10hdx | half duplex, 10fdx - 10 Mbps full duplex, etc.
10fdx | 100hdx | 100fdx} Example: Mod 3 setbridge connection 100fdx
The factory setting is auto.
Mod {1|2|3|4} setbridge Enable or disable flow control.
flowcntrl {enable | disable}
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.
“Mod {1|2|3|4} stat” command will display Eth link
status (on/off), mode (FDx/Dx), speed.
37
Commands for script editing
Command Description
Cfg show Show the configuration script stored in RAM.
Cfg load Load the configuration script from EPROM into 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 EPROM. This command saves in
EPROM the current script as well as settings that are
specified in it.
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 <#> (# - default value, default
value depends on IDU, see Chapter 3.11)
- TxAlarm level
- 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 1023, the events are
written in EPROM 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.
Commands for operations with files and file system
Please refer to chapter ‘Working with files’, page 42.
Syntactic 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 (| ).
38
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.
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.
Switch commands for CFM-M-MUX 1+1 configuration

Command Description
Switch {enable | disable} Enable/Disable switching function in 1+1 site.
Switch stat Display switchover status information.
Switch active Set the M-MUX as Active if it is in normal operation
condition
Switch standby Set the M-MUX to Standby, allowing the other M-MUX to
become Active
Switch force {active | • ‘active’, ‘standby’ - Switch the M-MUX to the
standby | off} selected mode, ignoring any conditions;
• ‘off’ – disable forced mode for normal switching.
Switch mode {HSB | FD [ Set the switching mode:
primary]} HSB – hot-standby. Note: for switching to work
properly in HSB mode, all four M-MUX IDUs of the
radiolink must be set as HSB.
FD – frequency diversity
‘FD primary’ – sets the FD mode and if both links
operate normally, the M-MUX will be set as Active.
Note: 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 Specifies the minimum delay (in seconds) between
<time_milliseconds> consecutive switchover attempts. 2 seconds by default.
Note: this setting must be different for each of
four IDU of the hop.
Switch show {on | off} Allow (on) or disallow (off) displaying switching
information in command interface. Off by default.
39
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 EPROM into RAM. The bootstrap contains
the parameters that were previously stored in EPROM using write and/or cfg
write commands. These parameters are stored in EPROM 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 EPROM, the
original configuration will be restored from EPROM 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 EPROM using cfg write command line. Note: the
parameters, that are not specified in the configuration script will have their
default values when the IDU is restarted.
40
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., ‘MMUX400.elf.lzip’. 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
Notes:
- 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 not 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.
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. Note:
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.
The user can create and store several configuration files to quickly revert to other
CFM site configurations.
41
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 ASCII 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:
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.
42
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.
43
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.
Take note of upper case and lower case type, it should be taken into account for
both username and password!
The passwords may contain spaces, if using space(s) the password should be
entered in quote marks.
For ASCII, 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, or log off from ASCII terminal, press Ctrl+D.
To disable username and/or password, enter the password configuration
command with empty string in argument:
− for ASCII 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 ASCII 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:
− connect to IDU with ASCII console (via serial port);
− Enter ‘restartcpu’ command and follow the strings displayed on ASCII console
window; as soon as ‘Press <Esc> twice to stop initialisation’ string appears
(see Figure 10), press Esc key twice.
Figure 10
− 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 ASCII console, - when
user connects to IDU from ASCII console, no prompt is displayed to enter
password.
44
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
IDU.
Panel access code

The panel access code for the access from IDU panel can be specified from the
Telnet and ASCII 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 0 value, which means that this
feature is disabled (default setting).
45
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 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;
- 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.
46
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 11.
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 11
5) If uploaded file is large (like firmware file), it is recommended to defragment

Flash disk. Use ‘tfs clean’ command from Telnet or ASCII 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’, page 42.
Note: 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.
47
3.6.2 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 ASCII 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;
Note: while in MicroMonitor mode, the ‘uMON>’ prompt will be displayed,
instead of normal prompt with IDU name (default ‘SAF>’).
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
When upload is complete, the following information will be displayed

(Figure 12):
48
Figure 12
5) Enter ‘reset’ command to exit from MicroMonitor mode and restart the
IDU.
6) Proceed with steps 5) and 6) in chapter 0.
49
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. The state of RA can be verified from
− RA LED on the IDU front panel,
− Web page,
− Telnet or ASCII 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
− 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 Port (I/O Port)
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 (invert).
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 4 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.
50
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.
Management
Module
Service
2-port channel
(RJ-45)
Serial
Serial
Port
Port
Eth
Router
51
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
Remote virtual serial Remote virtual serial

port IP address port IP address
Local virtual serial port Local virtual serial port
IP address IP address
Management Management
Module Virtual Virtual Module
service channel
(router) Serial Serial (router)
Port Port
Eth Eth
Required to specify: Required to specify:

Local serial port IP addr., Local serial port IP addr.,
Remote serial port IP addr. Remote serial port IP addr.
Remote serial port netmask Remote serial port netmask
Required to specify:
IP address/Net Mask,
Management Default Gateway
Console
Local Site (Terminal A) Remote Site (Terminal B)
Note: it is recommended to use configuration where SLIP port netmasks are

255.255.255.255 or 255.255.255.252.
See examples on the next page.
52
Examples of service channel configuration
service channel
RIP = ON Serial Serial RIP = ON
Port Port
Eth Eth
IP seraddr 192.168.0.1 IP seraddr 192.168.0.2

IP remaddr 192.168.0.2 IP remaddr 192.168.0.1
IP remmask 255.255.255.252 IP remmask 255.255.255.252
IP Addr 192.168.205.10 IP Addr 192.168.206.10
IP mask 255.255.255.0 IP mask 255.255.255.0
IP GW 192.168.205.1
Telnet console/ Console IP address: 192.168.205.1, 255.255.255.0
Web client Route Add 192.168.206.0 Mask 255.255.255.0 192.168.205.10
Figure 13
service channel
Port Port
Eth Eth

IP Addr 192.168.205.10 IP Addr 192.168.206.10
Router
IP mask 255.255.255.0 IP mask 255.255.255.0
(RIP=OFF)
IP GW 192.168.205.1 IP GW 192.168.0.10
Router port IP address: 192.168.205.1, 255.255.255.0
Route Add 192.168.206.0 Mask 255.255.255.0 192.168.205.10
Ethernet
Telnet console/Web client

Figure 14
53
Port IP address: 192.168.205.1
Route Add 192.168.205.0 Mask 255.255.255.240 192.168.205.2

Route Add 192.168.205.0 Mask 255.255.255.240 192.168.204.1
Ethernet
Router Telnet console/Web client
(RIP = OFF) IP address: 192.168.204.2
IP Addr 192.168.205.2 IP Addr 192.168.205.5

IP mask 255.255.255.252 IP mask 255.255.255.252
IP GW 192.168.205.1 IP GW 192.168.0.1
service channel
Port Port
Eth Eth
Hop 1 IP remmask 255.255.255.252 IP remmask 255.255.255.252
Hop 2 IP Addr 192.168.205.9 IP Addr 192.168.205.6

IP mask 255.255.255.252 IP mask 255.255.255.252
IP GW 192.168.0.3 IP GW 192.168.205.5
service channel
Port Port
Eth Eth
IP Addr 192.168.205.10 IP Addr 192.168.205.13

IP mask 255.255.255.252 IP mask 255.255.255.252
IP GW 192.168.205.9 IP GW 192.168.0.5
service channel
Port Port
Eth Eth
Figure 15. The IP configuration of the management channel via three 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)
54
Route Add 192.168.205.0 Mask 255.255.255.240 192.168.205.2

Route add 192.168.205.0 Mask 255.255.255.240 192.168.204.1
Ethernet
Router Telnet console/Web client
(RIP = OFF)
IP GW 192.168.0.1
Route add 192.168.205.8 Mask 255.255.255.248 192.168.205.6
IP GW 192.168.205.1
Route add 192.168.205.4 Mask 255.255.255.252 192.168.0.2
Route add 192.168.205.8 Mask 255.255.255.248 192.168.0.2 IP Addr 192.168.205.5
IP Addr 192.168.205.2 IP mask 255.255.255.252
IP mask 255.255.255.252
service channel
RIP = OFF Serial Serial RIP = OFF
Port Port
Eth Eth
Hop 2 IP GW 192.168.205.5
Route add 192.168.205.8 Mask 255.255.255.248 192.168.0.6
IP GW 192.168.0.5
Route add 192.168.205.13 Mask 255.255.255.255 192.168.205.10
IP Addr 192.168.205.9 IP Addr 192.168.205.6
IP mask 255.255.255.252 IP mask 255.255.255.252
service channel
Port Port
Eth Eth
IP GW 192.168.205.9
Route add 192.168.205.13 Mask 255.255.255.252 192.168.0.10 IP GW 192.168.0.9
IP Addr 192.168.205.10 IP Addr 192.168.205.13
IP mask 255.255.255.252 IP mask 255.255.255.252
service channel
Port Port
Eth Eth
Figure 16. The IP configuration of the management channel via three 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
55
3.9 Algorithm of LCD Operation
Perform Restart Hardware reset

IDU is powered on
CPU from menu button is pressed
Management Controller
Boot-up
Status Display
mode
NO Enter is
pressed
YES
Setup mode
Clear is pressed,
- at the top level
of the Setup
mode menu tree
Clear is pressed, - in the Setup mode NO
menu tree level lower than the top level
YES
Jump 1 level up on the

Setup mode menu tree
YES Idle for about 10 NO

seconds ?
Flow Chart 1. LCD operation
56
3.10 Replacing the Indoor Unit
Before replacing the IDU, verify the configuration of Radio if possible, - inspect
the channel an transmit power settings. Then configure the new IDU in one of the
following ways:
− delete the bootstrap via Telnet or ASCII console using cfg clear
command, or
− configure Radio channel and transmit frequency as needed (from LCD or
via management console);
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.
57
3.11 Default Settings
Parameter name or command line
Parameter/description Default value/setting
Telnet / ASCII LCD
Tx/Rx channel In the middle of the
Chan Chan band covered by
Radio
Transmitter power Txpower Tx Power Off
Rx signal level by which the RxAlarmLevel RxAlarmLev Equal or greater than
Radio Alarm is turned on -77 dBm
Fdx/Hdx port mode and speed Bridge Bridge Ethernet Auto
for Ethernet bridges
Management controller IP IP addr IP 192.168.205.10 or
address 192.168.206.10
Management controller IP IP mask Netmask 255.255.255.0
address netmask
IP address of the gateway to IP gw Gateway 255.255.255.255
the service channel
IP address of the local virtual IP seraddr Local IP 192.168.0.10
serial port of service channel
IP address of the remote IP remaddr Remote IP 192.168.0.11
virtual serial port of service
channel
IDU name Name - SAF
IDU capacity capacity Capacity (customer specified)
Multiplexer slot speed settings muxspeeds MUX slot All slots 0 Mbps (for
speeds all IDU capacities)
SNMP read community name SNMP community - Not specified
read
SNMP write community name SNMP community - Not specified
write
IP address of the SNMP trap SNMP trap - 255.255.255.255 ->
manager trap manager not
specified
Web page refresh time Webrefresh - 5 seconds
Username and password for Enable password - (disabled)
ASCII console
Access number for -
Panel access 0 (disabled)
LCD/Keypad
- Username and
Username and password for
WWWuser password not
Web management
specified
Username and password for -
Telnetuser Not specified
Telnet terminal
Configuration of Radio -
parameters from the Web Enable rfweb (disabled)
terminal
58
3.12 Configuring Radio Parameters
3.12.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.12.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 “Set Channel” item of IDU LCD menu system.
If this item is chosen, display indicates:
Channel = xxx
Tx = xxxxx.x MHz
where “Channel” corresponds to Tx channel number and “Tx frequency” 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 ASCII 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.
59
3.12.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 Set TxPower item of IDU LCD menu system.
2) The Tx Power can be adjusted using Txpower command from Telnet or
ASCII terminal, example: Txpower +10
The Tx Power can be adjusted from -10 dBm to +20 dBm 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.12.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.
Typical RSSI=f(RSL) chart

Displayed RSSI,
RSL, dBm V
-90 0 1,7
1,6
-85 0,1 1,5
-80 0,2 1,4
-75 0,3 1,3
RSSI port output, V
1,2
-70 0,4
1,1
-65 0,5 1,0
-60 0,6 0,9
-55 0,7 0,8
0,7
-50 0,8 0,6
-45 0,9 0,5
-40 1 0,4
0,3
-35 1,1 0,2
-30 1,2 0,1
-25 1,3 0,0
-20 1,4 -90 -85 -80 -75 -70 -65 -60 -55 -50 -45 -40 -35 -30 -25 -20 -15 -10 -5
-15 1,5 Displayed RSL, dBm
-10 1,6
Important note:
The RSSI port is typically labelled with RSSI . The ODUs which does not have such
label, does 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.
60
3.13 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 lopbacks (E1, V.35) does not have
time limit and must be switched off manually.
3.13.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 “BBloopback ON” to set the digital
baseband loops or “BBloop analog“ to set the analog baseband loop →
select “Yes”.
• RF loopback:
mode → select “Loopbacks” → select “RFloopback ON” → select “Yes”.
• V.35 interface loopback:
mode → select “Modules” → select “Module # V35” → select “V.35
Loopback” → “Change Loopback”, switch over to ON and confirm.
• E1 interface loopback:
mode → select “Modules” → select “Module # E1” → select “E1 Aloop” for
analog loopback (non-dual) or “E1 Dloop” for digital loopback → “Change”,
switch over to ON and confirm.
• REB interface loopback: not available.
3.13.2 Setting Loop Tests from Telnet/ASCII 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 on page 38).
• E1 interface module loopback:
“Mod # setE1 {Aloop|Dloop}”, if argument is “Aloop” - analog loopback is
activated, “Dloop” activates digital loopback, “Remote” –remote loopback,
“off” – switch off any E1 interface loopback (for details refer to Chapter
3.13.6), # - MUX slot number.
• Baseband loopback:
“BBloop {on|analog|off} [duration]”. Duration is set in minutes as values
from 1 to 10. 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.
61
3.13.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
ASCII console, the duration of radio loopback mode can be specified from 1 to 10
minutes.
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.
Important notes:
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.
3.13.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 ASCII console, the duration of baseband loopback mode can be
specified from 1 to 10 minutes.
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);
− 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.
Base-band Modem Base-band Modem

Rx Clock recovery/ Rx Clock recovery/
Filter Comparator Data decoding/ Filter Comparator Data decoding/
Descrambling Descrambling
ODU ODU
Tx Tx
Data coding/ Data coding/
Filter Filter
Scrambling Scrambling
Analog loop Digital loop (dual)
Figure 17. Baseband loopback modes: signal is looped in the modem
62
3.13.5 V.35 Interface Module Loopback
The loopback mode of V.35 interface module is dual.

2
I C bus
CPU
Remote
Multiplexer
loop
SCTE
TxD
IN DTR
RTS
V.35 Local
Interface
loop
DSR
OUT RxD
RxC
Figure 3.18. V.35 Interface Module Loopback
3.13.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).
2
I C bus
CPU
Multiplexer
IN
E1
Analog
G.703 Interface
HDB3
OUT
Remote Local
loop loop
Figure 3.19. E1 Interface Module Digital loopback mode
2
I C bus
CPU
Multiplexer
IN
E1
Analog
G.703 Interface
HDB3
OUT
Figure 3.20. E1 Interface Module Analog loopback mode
2
I C bus
CPU
Multiplexer
IN
E1
Analog
G.703 Interface
HDB3
OUT
Remote
loop
Figure 21. E1 Interface Module Remote loopback mode
63
4 Using CFM-M-MUX in 1+1 Configuration
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. 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 (currently not supported)
The CFM-M-MUX 1+1 configuration is not supported for V.35 traffic.
Mechanical and environmental specifications are the same as for CFM-M-MUX
IDU.
Ethernet
Switch / Hub
(1...4) x E1
Transformer
1+1 I/O card / Alarm port
64
4.1 1+1 Protection Modes
Currently the 1+1 configuration is supported for E1 traffic only.
The following picture shows principle of E1 traffic switching in FD mode and HSB
mode.
FD Tx
O O
Tx
1
IDU
E1
mode D (((( )))) D IDU
E1 1
Rx U U Rx
2(off)
2(off)
Tx Transformer Different frequencies;

Tx
All ODUs are operating
Rx (transmitting, receiving)
Rx
1(off) 1(off)
Rx
O O Rx
2 E1 IDU D (((( )))) D IDU 2
E1
Tx U U
Tx
HSB 2(off)
Tx
2(off)
1 Tx 1
mode 1 E1
IDU
O
(((( ))))
O
D D IDU E1 1
Rx U U Rx
2(off) 2(off)
Tx Same frequency for both links; Tx

Only ODUs of the active link
Rx are operating Rx
1(off) 1(off)
Rx Rx
O O
2 E1 IDU D D IDU E1 2
2 Tx U U
Tx 2
1(off) 1(off)
Figure 22. 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.
65
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).
Traffic switching time is less than 50 ms in case of
• Rx level is too low (below the threshold level), or
• 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:
1
IDU
IDU
User equipment
Transformer:
Unbalanced DB25
Unbalanced DB25
2
IDU
IDU
User equipment
Transformer:
Balanced DB25
Balanced DB25
3
IDU
IDU
User equipment
Transformer:
Balanced DB25
RJ45
Note: cables between IDUs and transformer are included with transformer.
4.5 Ethernet traffic switching

Ethernet traffic switching is implemented by means of Ethernet switch.
66
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 1+1 Configuration
4.8.1 Console/Telnet Commands
Please refer to chapter 3.5 for commands related to CFM-M-MUX 1+1

configuration.
4.8.2 IP configuration for 1+1 link
The following picture shows an example of IP configuration for 1+1 link. 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.
ip addr 192.168.205.10 ip addr 192.168.206.10
ip mask 255.255.255.0 ip mask 255.255.255.0
ip seraddr 192.168.205.10 ip seraddr 192.168.206.10
ip remaddr 192.168.206.10 ip remaddr 192.168.205.10
ip remmask 255.255.255.0 ip remmask 255.255.255.0
ip sideaddr 192.168.205.11 ip sideaddr 192.168.206.11
IDU 1 IDU 1'

Eth Eth
Management
console
IDU 2 IDU 2'

Eth Eth
ip addr 192.168.205.11 ip addr 192.168.206.11

ip mask 255.255.255.0 ip mask 255.255.255.0
ip seraddr 192.168.205.11 ip seraddr 192.168.206.11
ip remaddr 192.168.206.11 ip remaddr 192.168.205.11
ip remmask 255.255.255.0 ip remmask 255.255.255.0
ip sideaddr 192.168.205.10 ip sideaddr 192.168.206.10
Figure 23
Important notes:
SLIP port address must be equal to Ethernet port address (ip addr = ip seraddr).
67
4.9 Hardware Installation
E1 traffic cable restrictions: the cable length between transformer box and User
equipment must not exceed 220 meters (750 feet).
IDU
IDU
Length must not

exceed 220 meters Transformer
(750 feet) User equipment
68
5 Pinouts
5.1 Management port pinouts
5.1.1 RS232
DB9 Female Connector
1
Unassigned 6
2 DCE Ready
Transmitted Data 7
Clear to Send
3
Received Data 8
Request to Send
4
DTE Ready 9
5 Unassigned
Signal Ground
Shield
Received from DTE

Transmitted from DCE
Note:
• To connect IDU to PC via RS-232 port, a “straight through” (modem) serial
cable is required.
5.1.2 Ethernet
Standard Ethernet patch cables should be used with management Ethernet port
of the IDU.
69
5.2 Alarm interface (I/O Port) pinouts
5.2.1 Alarm port specification for 1+0 CFM-M-MUX configurations
1 2 3 4 5 6 7 8 9 10 11 12 13
14 15 16 17 18 19 20 21 22 23 24 25
Figure 24. DB25 Male connector pin layout
The pin assignments for relay outputs are the following:

Output A Output B Output C Output D
(Power on\off) (SL alarm) (RAI alarm) (RA alarm)
Pair of pins 1-2 2-14 3-4 4-16 5-6 6-18 7-8 8-20
Type: NC* or NO NC NO NC NO NC NO NC
NO**
NC* - Normally Closed
NO** - Normally Open
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.
70
5.2.2 Alarm port specification for 1+1 CFM-M-MUX configurations
GND
GND
GND
INPUT 2
INPUT 3
Relay D: NC GND
Relay D: common INPUT 1
Relay D: NO INPUT 4
Relay C: NC Relay B: NC
Relay A: NO
Relay C: common Relay B: common
Relay A: common
Relay C: NO Relay B: NO
Relay A: NC
NC
Common
NO
NC - Normally closed
NO - Normally open
Figure 25. DB-44 HD port pinouts
The pin assignments for relay outputs are the following:

Output A Output B Output C Output D
(Power on\off) (SL alarm) (RAI alarm) (RA alarm)
Pair of 33-34 34-35 36-37 37-38 39-40 40-41 42-43 43-44
pins
Type: NC NO NC NO NC NO NC NO NC
or NO
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
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.
71
5.3 Traffic port pinouts
5.3.1 V.35 traffic port pinouts
Signal M34 Pin 60 Pin Interconnectable pinouts

Cisco* at the Cisco equipment
P GND A 46 side:
S GND B 45
RTS C 42
48 & 49
CTS D 35 50 & 51 & 52
DSR E 34 53 & 54 & 55 & 56
DCD (RLSD) F 33
DTR H 43
TxD+ P 18 Notes:
TxD- S 17 * This information is for
RxD+ R 28 user’s reference only
RxD- T 27
SCTE+ U 20 P GND – Protection
SCTE- W 19 Ground
RxC+ (SCR+) V 26 S GND – Signal Ground
RxC- (SCR-) X 25
TxC+ (SCT+) Y 24
TxC- (SCT-) AA 23
72
5.3.2 E1 port pinouts
Note: All pinouts for E1 transformer ports are the same as on IDU.
RJ-45 E1 pinouts
The pinouts of RJ-45 ports for 1xE1 and 4xE1 modules are shown in Figure 26.
RJ-45 pin numbering E1 port pinouts
INPUT (Rx)
E1 port
OUTPUT (Tx)
1 2 3 4 5 6 7 8
IN OUT Not
(Rx) GND (Tx) used GND
12345678
Figure 26. E1 traffic port pinouts
E1 unbalanced (75 Ω) DB25 traffic port pinouts

See Figure 24 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 Ω) DB25 traffic port pinouts

According to Figure 24:
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.
73
6 Mechanical data
IDU weight and dimensions
IDU model Weight without Dimensions HxWxD [mm]

modules [kg]
CFM-M-MUX 2.0 44x482x284
44
482
284
Dimensions of the IDU
Weight and dimensions of traffic modules
Module Weight [g] Dimensions HxWxD [mm]

10\100Base-T 2-port 55 43x59x125
Ethernet bridge
10\100Base-T 1-port 55 43x59x125
Ethernet bridge
1xE1 75 43x59x143
4xE1 w\ DB25 port 76 43x59x126
4xE1 w\ RJ-45 ports 77 43x59x125
V.35 86 43x59x139
74
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: techsupport@saftehnika.com
- Telephone: +371 7046840
- Fax: +371 7020009
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.
75

Manual Radio SAF

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Manual Radio SAF

Hochgeladen von

Copyright:

Verfügbare Formate

CFM-M-MUX

Indoor Unit Management System

© SAF Tehnika A/S 2006

1 CFM Multiplexer Indoor Unit Overview ....................................................................4

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.7 March 15, 2006 Chapters 3, 4, 5 revised.

2.1 Installation Notes

48.6 cm (19.29 ") V.35 E1

42.6 cm (16.93 ")

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

REMOTE ENTER Slot 1 Slot 2 Slot 3 Slot 4

Figure 2. Numbering of module slots

Port/connector Front panel connectors

Port/connector Rear panel connectors

Figure 3. Rear panel

Other front panel LED signals

Rear panel LEDs are shown in Figure 4.

Hidden reset Ethernet ODU Grounding

Indicates operation of the Ethernet link\activity 100 Mbps speed

Figure 4. Rear panel LEDs

2.4.1 V.35 Interface Module

Figure 5. V.35 module (front)

Out, Two BNC connectors of the 75 Ω unbalanced port provide means to

Label Color Description

Figure 6. 1xE1 module (front)

Green Indicates normal operation of the channel, no

Red Constant red indicates that E1 signal is lost. If

No LED is lit Channel is switched off.

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

100 Mbps speed LED

Figure 8. 2-port FREB module LEDs

Product type (internal use only) Hardware

Figure 9. IDU label

ENTER ‘ENTER’ button is used

CLEAR ‘CLEAR’ button is used

↑ ↓ Up/Down buttons are used:

3.1.1 “Status Display” Mode of the IDU LCD Management

Access code Change

V.35 Interface Module LEDs

SL Red Signal Loss V.35 port failure.

Loopback on V.35 module is

Data activity - data is being

E1 Interface Module LEDs

Label Color Description

Ethernet Interface Module LEDs

Green Ethernet Link/Activity LED, if flickers indicates data transmission

Type of IDU reset Result

ASCII console window

4. Choose port (COM1 or COM2).

The IDU can be connected

3.4.1 Web Management

Module Status window

Main Configuration window (Radio parameter configuration is disabled)

Modules Configuration window

3.4.3 SNMP Management

The SNMP management allows to:

Sample of SNMP query

Variable Name Variable Type Value List Description

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

Configuring security parameters

Configuring IDU parameters