CFM-MP-MUX CFM-M4P-MUX Indoor Unit Insta PDF

CFM-MP-MUX /
CFM-M4P-MUX
Indoor Unit
Installation and Configuration Manual
© SAF Tehnika A/S 2006
1
Table of Contents
Table of Contents .......................................................................................................2
1 Introduction ........................................................................................................4
1.1 Protected Link Configuration............................................................................. 5
2 Hardware Features ..............................................................................................6
2.1 IDU Appearance ............................................................................................. 6
2.2 LEDs ............................................................................................................. 9
2.3 Mechanical Data ........................................................................................... 10
2.4 Interface modules......................................................................................... 11
2.4.1 V.35 Interface Module ............................................................................... 11
2.4.2 100Base-T Ethernet Modules ...................................................................... 11
2.4.3 E1 Interface Module .................................................................................. 13
2.4.4 4xE1 Interface Module............................................................................... 13
2.5 Functional Description ................................................................................... 15
2.5.1 FD Mode ................................................................................................. 17
2.5.2 Independent Mode.................................................................................... 17
2.5.3 HSB Mode ............................................................................................... 18
2.5.4 1+0 Operation Mode ................................................................................. 18
2.6 FEC Coding .................................................................................................. 18
2.7 Labelling ..................................................................................................... 18
3 Configuration and Management .........................................................................20
3.1 LCD/Keypad................................................................................................. 20
3.1.1 “Status Display” Mode of the LCD Management Interface ............................... 20
3.1.2 “Setup” Mode of the LCD Management Interface ........................................... 22
3.2 Resetting the IDU ......................................................................................... 26
3.3 RS-232 Serial Management Port...................................................................... 27
3.4 Command Interface ...................................................................................... 30
3.4.1 Working with configuration script ................................................................ 40
3.4.2 File system .............................................................................................. 40
3.4.3 Storage of radio parameters....................................................................... 42
3.4.4 Security commands .................................................................................. 43
3.5 Updating software......................................................................................... 44
3.5.1 Uploading file via Ethernet management port (TFTP) ..................................... 45
3.5.2 Uploading file via Ethernet management port (FTP) ....................................... 46
3.5.3 Uploading file via serial port (Xmodem) ....................................................... 46
3.6 Ethernet Management Port............................................................................. 48
3.6.1 SNMP Interface ........................................................................................ 48
3.6.2 Web Interface .......................................................................................... 51
3.6.3 Telnet management .................................................................................. 56
2
3.6.4 Engineering Order Wire ............................................................................. 56
3.7 Using IDU LCD ............................................................................................. 57
3.8 Alarm Port (I/O Port)..................................................................................... 57
3.9 Configuring Management Service Channel ........................................................ 58
3.10 Default Settings............................................................................................ 63
3.11 Automatic Transmit Power Control (ATPC) ........................................................ 64
3.11.1 ATPC Algorithm ........................................................................................ 64
3.11.2 ATPC commands ...................................................................................... 64
3.12 Performing Loop-back Tests ........................................................................... 65
3.12.1 Setting Loop Tests from IDU LCD/Keypad .................................................... 65
3.12.2 Setting Loop Tests from Telnet/ASCII terminal.............................................. 65
3.12.3 Radio loopback......................................................................................... 66
3.12.4 Base-band loopbacks ................................................................................ 66
3.12.5 V.35 Interface Module Loopback ................................................................. 67
3.12.6 E1 Interface Module Loopbacks................................................................... 67
3.13 Evaluating RSL from RSSI signal ..................................................................... 68
4 Pinouts ..............................................................................................................69
5 SAF Tehnika A/S Contacts .................................................................................73
3
1 Introduction
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 series 1+1 modular multiplexer Indoor Units, CFM-MP-
MUX and CFM-M4P-MUX, covering hardware features, built-in management system,
configuration functionality, etc.
The CFM-MP-MUX and CFM-M4P-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); The CFM-MP-MUX
Indoor Unit is intended for use with the CFM-LM radios. The CFM-M4P-MUX Indoor
Unit is intended for use with the CFM-L4 radios.
The modularity of the CFM-MP-MUX IDU allows installing various CFM series traffic interface
modules (for more information please refer to chapter 2.1).
Local and remote management functionality (incl. Web, Telnet, SNMP, ASCII)
Alarm interface (optional).
The CFM-MP-MUX IDU provides the total WAN capacity of 34 Mbps, and 4 slots for interface
modules.
The CFM-M4P-MUX IDU provides the total WAN capacity of 4 Mbps, and 2 slots for interface
modules.
The IDU is frequency-independent; the operating frequency is determined by the ODU only.
The following versions of CFM-MP-MUX IDUs are available (product codes):
CFGMXP02.
The CFM-M4P-MUX IDU versions are:
CFGM4P02.
Revision history
Revision Date Comments

1.0 May, 2005
1.1 June, 2005 For MP-MUX SW ver. 4.09 (2005.05.31)
1.2 October, 2005 Information about 1-port 100Base-T interface module added
1.3 December, 2005 Information about CFGMXP02 version MP-MUX added
1.4 March, 2006 Information about ATCP added
1.5 June, 2006 Chapter 3.4 revised due to IDU software release,
version 4.20.
1.6 October, 23 Version CFGMXP01 removed
1.7 December, 1 Information about FEC added (chapter 2.6)
1.8 December 2008 Information on software update expanded
CFM-MP-MUX and CFM-M4P-MUX Indoor Unit · Management System Technical Description and Configuration Guide 4
Rev.1.8 · © SAF Tehnika A/S 2008
1.1 Protected Link Configuration
The CFM-MP-MUX IDU is compatible with the CFM-M-MUX IDU.
The link may have both sites protected where each site consists of one protected IDU (CFM-
MP-MUX) and two ODUs.
The link may also have only one of sites protected, - one site with the protected IDU and
one or two ODUs and the other site with the non-protected modular multiplexer (CFM-M-
MUX IDU) and one ODU.
1 2 Directional
coupler
4 5 Directional
coupler
Figure 1.1. Supported 1+1 configurations:

1. frequency diversity with four antennas, two frequency pairs are used and both
transmitters operate simultaneously at each site;
2. frequency diversity with two antennas;
3. space diversity with four antennas, one transmitter and two receivers operate for
each direction, and only one frequency pair is used;
4. HSB (hot standby) configuration with four antennas, only one frequency pair is
used, only one transmitter transmits at each site;
5. HSB configuration with two antennas.
For 1+1 configurations with two antennas, a directional coupler is used, with insertion loss
of 1 dB and coupling 6 dB.
2 Hardware Features
2.1 IDU Appearance
Ethernet RS-232
management port management port
Grounding screw
23 cm
(9.10 ")
4 cm
10 cm 8 cm (1.57 ")
12 cm (3.15 ")
(3.94 ")
(4.72 ")
V.35 E1
48.6 cm (19.29 ")
42.6 cm (16.93 ")
Figure 2.1
The CFM-MP-MUX IDU is implemented as 19” rack mountable aluminium 2U high unit, the
depth of the unit is 230 mm without front panel handles and 270 mm with handles.
The CFM-MP-MUX IDUs (all versions) provide four sockets for installation of interface
modules. For information about data rate distribution among multiplexer slots, please see
Table 10.
CABLE CABLE
CFM-MP-MUX
ODU port POWER POWER
Module Module Module
TX ACTIVE TX ACTIVE Module
(N-type Slot 2 Slot 3 Slot 4
RX ACTIVE RX ACTIVE
Slot 1
connector)
FREB
RX
E1
TX
SL
LB
CLEAR
- - SYNC LAN
48V RADIO
48V
REMOTE
+ + ALARM
ENTER
V.35
V2 10/100 ETH
Hidden reset Ethernet

button management
Dry relay ports
alarm port
ASCII console port Grounding
(RS232) screw
Figure 2.2. Version CFGMXP02 of CFM-MP-MUX IDU (front and rear panel)
The CFM-M4P-MUX IDU provides four sockets for installation of interface modules.
CABLE CABLE
CFM-M4P-MUX Module
POWER POWER
Module
TX ACTIVE
RX ACTIVE
TX ACTIVE
RX ACTIVE Slot 1 Slot 2
RX
TX
SL
LB
CLEAR E1
SYNC
RADIO
REMOTE
ALARM
ENTER
V.35
ASCII console port Ethernet Grounding

Dry relay (RS232) management ports screw
alarm port
Figure 2.3. Version CFGM4P02 of CFM-M4P-MUX IDU (front and rear panel)
CFGMXP02/CFGM4P02 MP/M4P-MUX IDU Features:
Modules and > 4 x traffic module slots for CFGMXP02 model, 2 x traffic slots
Module sockets for CFGM4P02 model;
> 2 x hot-swappable power supply and cable interface modules
(1+1).
Traffic ports > V.35 interface module (port connector M34), supported
(supported traffic speeds: 64, 128, 256, 512, 1024, 2048, 4096, 6144 and 8192
modules) kbps;
> 2-port 100Base-T Ethernet module (RJ-45 sockets)
> 1-port 100Base-T Ethernet module (RJ-45 socket)
> E1 module, provides one E1 port, (2048 kbps speed) with 120
Ω RJ-45 socket and 75 Ω BNC interfaces);
> 4xE1 module, provides 4xE1 ports, the ports can be separately
switched on/off, accordingly the module capacity is 2 Mbps, 4
Mbps, 6 Mbps or 8 Mbps.
Management ports > RS-232 serial management port;
> Ethernet management ports for Web, Telnet or SNMP
management;
> RS232 console port;
> Alarm port and user inputs (optional).
Front panel > LCD/keypad;
interfaces > Port activity LEDs and alarm LEDs.
CABLE
POWER
TX ACTIVE
RX ACTIVE
-
48V
+
Figure 2.4. Hot-swappable Power Supply and Cable Interface module for CFGMXP02 and
CFGM4P02 IDU versions; the module has N-type connector for IDU-ODU cable connection
and Power Supply socket.
Table 1. Connectors
Connector(s) / label Comments
Front panel connectors
+ 48V - Power connector (D-sub type), IDU should be powered from
20 – 60 VDC power source. Either “+” or “–” pole of the
power source can be grounded, one should make sure if the
chosen grounding wire is connected to ground on IDU power
connector.
Rear panel connectors
DB-9 type connector RS232 management port for connection of ASCII console (or
analog line modem for the remote connection of ASCII
console);
The RS232 console port is also used to update management
software.
DB-25 type connector Alarm port.
RJ-45 sockets 2x10/100 Base-T Ethernet management ports to connect
Telnet or Web terminal.
The ports are numbered from left to right when facing the
IDU rear panel, thus port 1 is located next to serial
management port and port 2 – next to port 1.
2.2 LEDs
Table 2. LEDs
Front panel LEDs
Label Description
SYNC Red Signal Lost LED indicates the loss of Multiplexer synchronization; if
not lit – operating properly.
RADIO Radio Alarm LED indicates problems with radio unit and IDU-ODU cable.
The following problems cause the Radio Alarm to switch 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 synthesizer loops are not locked (TxPLL=Error,
RxPLL=Error)
If not lit – operating properly (Rx=OK & TxOut=OK & Humidity=Low &
RF Cable – OK & TxPLL=OK & RxPLL=OK).
Note: the RA LED will also switch on if the Radio loopback is active
and/or if the transmitter power is switched off.
REMOTE Remote Alarm Indicator (RAI alarm), - indicates that the far-end site
has the SL alarm switched on.
ALARM 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.4.
Rear panel LED (see Figure 2.5)
If blinking (with a period of about 1 sec.), indicates operation of the
management module CPU;
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 ALARM LEDs
HARDWARE simultaneously will be switching on and off.
FAILURE
Figure 2.5. Rear panel
Table 4. Power Supply and Cable Interface module LEDs (for CFGMXP02 version)
PSM/CI module LEDs (for CFGMXP02 CFM-MP-MUX version)
Label Description
CABLE Indicates the statuss of the IDU-ODU cable:
Switched off – normal operation (acceptable signal level from ODU);
Switched on red LED – indicates one of the following failures:
- short circuit in cable;
- 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.
POWER Switched on red LED indicates power supply failure, - one or more of
the power supply voltages (+3.3V, +5V, -5V) are out of operational
interval; Switched off – normal operation.
TX ACTIVE Switched off – the PSM/CI module is not set as a transmitting module;
Switched on – the PSM/CI module is set as a transmitting module.
RX ACTIVE Switched off – the PSM/CI module is not set as a receiving module;
Switched on – the PSM/CI module is set as a receiving module.
2.3 Mechanical Data
IDU version Weight (with no modules), [kg] Dimensions HxWxD, [mm]

CFGMXP02 2.7 88x482x284
CFM-MP-MUX and CFM-M4P-MUX Indoor Unit · Management System Technical Description and Configuration Guide
10
2.4 Interface modules
2.4.1 V.35 Interface Module
The V.35 module terminates 2, 4, 6, or 8 Mbps from modular multiplexer 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 port. The V.35 port has M.34 connector.
If multiplexer slot capacity is set to 2 Mbps, the V.35 module also supports fractional E1
mode, - up to thirty one 64 kbps channels can be selected from E1 stream from WAN side
(timeslots 2. – 32. in PCM31 mode).
Figure 2.6.
Table 5. V.35 Module LEDs (see Figure 2.6)

LED Color Name Function Direction
Data Data activity - data is being
TX Green Transmitting 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 refer
switched on, informing that
Loopback to chapter 3.12.5 for more
LB Red the connection between
Active information about V.35
V.35 port and MUX board
module loopback.
is interrupted.
Data activity - data is being

Data
received from multiplexer
RX Green Receiving MUX Æ V.35*
board and transmitted to
Active
module front port
2.4.2 100Base-T Ethernet Modules
The 1-port module terminates any capacity up to 34 Mbps from the multiplexer on
100Base-T ports (RJ-45 sockets), 1-port module has one 100-Base-T port;
The 2-port module terminates any capacity up to 12 Mbps from the multiplexer on
100Base-T ports (RJ-45 sockets), 2-port module has two 100-Base-T ports.
Feature summary:
Low capacity 2-port 100Base-T
Ethernet Bridge Module
• 10M/100M Half/Full duplex auto-
detect
• TP auto MDIX TX/RX swap
• 2048 MAC addresses table
• Store and forward architecture
• Aging function
• Supports up to 1522 byte packets
• Supports 802.1Q VLAN.
For more information about 1-port module throughput, see Table 6.

Table 6. 100Base-T Ethernet module throughput for various frame sizes
Frame
Total Throughput,
Size,
[bytes] [Mbit/sec]
64 30.04672
128 31.37228
256 32.46694
512 33.09568
1024 34.32448
1280 35.072
1518 35.14473
1600 35.1744
1700 36.4344
1760 36.45312
The maximum available WAN traffic capacity of the bridge is possible if 1-port module is
used in slot 1 of the CFM-M-MUX IDU, and slot 1 is configured as ‘RMN’; following this, the
maximum WAN traffic capacity (payload) is 33.092 Mbps (total capacity 34.368 Mbps).
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
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.
2.4.3 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. Switching between
BNC and RJ-45 ports is available from IDU (LCD/keypad) and from management terminal
(Web, Telnet or ASCII).
Table 7. 1xE1 module LEDs
Label Color Description
Tx Green Steady green light indicates the E1 module is ready to transmit data to
CPE connected to E1 port.
In case if Multiplexer synchronization is lost (S.L. LED is lit), Tx LED goes
off and AIS signal is transmitted from E1 port to user equipment.
Rx Green Steady green light indicates the data signal from E1 input.
AIS Red Steady red LED indicates the AIS signal from E1 input.
LB Red “LoopBack” LED (red) indicates loopback mode is activated in the module.
Figure 2.7. 1xE1 module (front)
2.4.4 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; for details see Table 8.
Table 8. Description of LEDs
E1 port LED
Color Description
(highlighted)
Green Indicates normal operation of the
(loop-back LED yellow or off) channel, no problems with signal
reception.
Red Constant red indicates that E1 signal is

(loop-back LED yellow or off) lost. If red flashes momentarily, the
bipolar violation (line code error) was
received from user equipment.
Blinking green and red AIS signal is being received from user
(loop-back LED yellow or off) equipment.
Yellow loop-back LED (loop- When loopback LED is switched on,

back switched on) analog, digital or remote loop-back mode
is active for that channel.
No LED is lit Channel is switched off.
(1) (2)
Figure 2.8. 4xE1 modules: (1) with DB25 ports; (2) with RJ-45 ports
2.5 Functional Description
Figure 2.9 shows the simplified block diagram.
Independent
FD mode HSB mode
mode
Rx Rx Rx
Tx Tx Tx
Rx Rx Rx
Tx Tx Tx
Rx Rx Rx
Tx Tx Tx
Rx
h
Tx
Rx
itc
Sw
Modem
Rx
Tx
Tx
Management
Joint traffic
controller board
Power Supply Module and
Power Supply Module and
Power supply
voltage level
control
Cable Interface
Cable Interface
Controller
Management traffic
Multiplexer board
SL
RAI
Power Supply
Data traffic
Main Board
to ODU to ODU
Figure 2.9. Block diagram of the CFM-MP-MUX and CFM-M4P-MUX IDU
The IDU consists of the following PCBs:

- Multiplexer board,
- Modem board,
- Management controller board,
- Power supply mainboard,
- 2 x Power supply and Cable Interface modules (PSM/CI modules); the PSM/CI modules
for model CFGMXP02 are hot-swappable and can be removed/inserted from panel
without restarting the IDU (for older model such as CFGMXP01, the PSM/CI module
replacement requires switching off the IDU and opening IDU cover).
The Power Supply mainboard has two slots onboard, each slot for one PSM/CI module, - the
PSM/CI module is duplicated. Each PSM/CI module
- provides the power supply voltages for each PCB in the IDU,
- provides power supply to the ODU (Cable Interface part),
- and transmits/receives IF traffic signals to/from ODU.
The Power supply mainboard has the traffic switch and the controller onboard. The controller
monitors the levels of power supply output voltages of both PSM/CI modules. Both PSM/CI
modules operate in parallel, but the incoming traffic is received solely from one PSM/CI
module and passed to the modem (see Figure 2.9).
The signal from the PSM/CI module is further passed to the radio via 50 Ω coaxial cable.
The switch-over between PSM/CI modules is performed in one of the following events (in
order of severity):
- SL alarm at the local site switches on meaning that the E3 frame synchronization has
been lost;
- RAI (Remote Alarm Indicator) signal is received from the WAN, this means that the far-
end site has the SL alarm switched on;
- Power supply failure;
- Radio cable failure, - if there is a break or short-circuit in the IDU-ODU cable (same as
the RF cable parameter returning “short” or “off” value in status display mode of the
LCD;
- RA (Radio Alarm) switches on, this occurs in one of the following cases:
o Boundaries of RF level max / RF level min / RF level delta parameters have
been reached;
o Received signal level lower the RxAlarmLevel value;
o Problems with Radio: Humidity = high, TxPLL failure;
BEGIN
NO
NO
NO
NO
NO
Switch force OFF ?
YES
NO
Alternative ODU:
SL and RAI alarms are OFF ? IDU-ODU cable
and
Power supply OK?
YES
Power supply voltages and YES

IDU-ODU cable ok ?
NO
Minimum delay between

YES
switchover attempts (switch
YES
delay) expired?
RxLev > RxMin ?

AND YES
RxLev < RxMax ?
AND Switchover
RxLev difference between Active and
Alternative ODU > RxDelta ?
YES
BER level below specified

threshold ?
RxLev - the the Rx level figure received from the far-end

RxMax - maximum permissible Rx level at the far-end
RxMin - minimum permissible Rx level at the far-end
RxDelta - the difference between link 1 Rx signal level and link 2 Rx
signal level which, when exceeded, causes to switch to the other
link with the higher Rx signal level
Figure 2.10
If the fault occurs, the total switch-over time does not exceed 50 milliseconds.
2.5.1 FD Mode
When operating in FD (frequency diversity) mode, the outgoing (Tx) traffic is passed to both
ODUs (see Figure 2.9), the transmitters of both ODUs are switched on; the incoming signal
(Rx) is choosed from one of the PSM/CI modules, depending on the received signal level and
alarm status.
The FD mode should be used for frequency-diversity protected link configurations.
Note: in FD mode both ODU LEDs (1 and 2) will be switched on (yellow), since both ODUs
are transmitting.
2.5.2 Independent Mode
When operating in Independent Mode, the incoming (Rx) and outgoing (Tx) traffic is
switched between PSM/CI modules independently, - the incoming traffic can be received
from one ODU while the outgoing traffic is passed to the other ODU (see Figure 2.9). One
ODU is transmitting and both ODUs are receiving signal at each end.
The Independent mode should be used for space-diversity protected link configurations.
2.5.3 HSB Mode
The HSB (hot standby) Mode is similar to Independent Mode, except that both, incoming and
outgoing traffic, are switched between PSM/CI modules simultaneously (see Figure 2.9).
2.5.4 1+0 Operation Mode
The CFM-MP-MUX and CFM-M4P-MUX can be ordered with only one PSM/CI module if the
user plans to upgrade the link later to 1+1; in this case the unit will operate as the CFM-M-
MUX (1+0).
If the IDU operates with two PSM/CI modules in 1+1 mode, and user disconnects one ODU
or removes one PSM/CI module, there is no need to perform any configurations for the
switching, but it is recommended to disable the switching using ‘switch force’ command (see
chapter 3.4 for Telnet/ASCII commands).
2.6 FEC Coding

The CFM-MP-MUX and CFM-M4P-MUX IDUs use RS (255, 223) FEC coding (Reed Solomon),
which improves receiver sensitivity by 4 dB. The FEC feature is available for IDUs with
software versions 5.xx.
2.7 Labelling
The IDU and ODU label contains the following information:
− Product brand name
− Product number (P/N)
− Serial number (S/N)
The Serial Number uniquely identifies the unit (IDU or ODU); the Serial Number contains 4-
digit number, which is derived from the Product Number of the unit, and a 5-digit
consecutive number of the product; the 5-digit consecutive numbering for IDU label is
separate for each IDU type (e.g. MUX IDU, E1 IDU, etc.), for ODU label – separate for each
frequency band.
Product number
Product
type Hardware version
Product brand (specification)
name
Band side,
Low or High
Notified body
Product code, derived
from Product Number
Consecutive number
Figure 2.11. Label of the CFM-15-LM ODU
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 in each line.
The LCD operates in two modes - Status and Setup display mode, please refer to Flow
Chart 1, page 57.
Keypad consists of 4 buttons:
ENTER is used to confirm the choice of displayed item or entered data as well as
to switch from “status display” to “setup” mode.
CLEAR is used to cancel the choice or to move to previous menu level
↑ ↓ Up/Down buttons are used:
- To switch between options for menu items displayed
- To choose parameter to set up and to set its value.
3.1.1 “Status Display” Mode of the 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 buttons to scroll through parameters). These
parameters are listed in the Table 9.
Table 9. Parameters displayed in “Status Display” mode
Parameter Values and description

Tx=15131.000MHz
Indicates current Tx frequency of ODU1 and ODU2.
Tx=15166.000MHz
Rx=14711.000MHz
Indicates current Rx frequency of ODU1 and ODU2.
Rx=14746.000MHz
TxPower=+20dBm
Indicates current output power of ODU1 and ODU2.
TxPower=+20dBm
Rx= OK Indicates various conditions of Rx signal from ODU1 and ODU2:
Rx= OK “OK” indicates IDU receives acceptable signal from ODU;
“Low” indicates that received signal level is too low for IDU to
operate properly;
“Error” indicates some internal fault in ODU receiver, please contact
sales representative or manufacturer;
“Loopback” indicates radio loopback mode: Rx = Tx frequency
RxLev= -46dBm
Indicates the level of the received signal (at ODU1 and ODU2).
RxLev= -48dBm
Cable=-5dBm Parameter indicates signal attenuation in ODU-IDU cable, values of 0
… -20 dB provide proper operation of IDU.
Cable=-10dBm
TxOut= Ok Indicates operation status of ODU transmitter:
TxOut= Ok “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):
TxPLL= Ok “Ok” indicates proper operation;
“Error” indicates internal fault in ODU transmitter, please contact
sales representative or manufacturer.
RxPLL= Ok Indicates operation status of ODU Rx Syntheser Loop (PLL lock):
RxPLL= Ok “Ok” indicated proper operation;
“Error” indicates internal fault in ODU receiver, please contact sales
representative or manufacturer.
ODU t= 23C
Indicates internal temperature of ODU1 and ODU2.
ODU t= 23C
Humidity=Low Indicates humidity level inside ODU1 and ODU2,
Humidity=Low “Low” indicates acceptable moisture levels;
“High” indicates too high level of humidity, condensing.
Restart= 00 Parameter indicates number of ODU management controller restarts
Restart= 00 since counter was last reset on power up.
RF Cable – OK Parameter indicates power consumption of the ODU units:

RF Cable – OK “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.
PW max = 20
Indicates maximum possible transmitting power (for both ODUs).
PW max = 20
RxAlarmLev =-77 Indicates the Rx level (in dBm) at which the Radio Alarm is switched
RxAlarmLev =-77 on.
IDU t= 31C Indicates temperature inside IDU.

BlkErr = 8275703 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 = 10196 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 = 90931 Time, during which all error measurements are performed.
ErrSec = 1361 Errored seconds; errored second is a one-second period in which one
or more bits are in error or during which SL alarm is switched on.
SErrSec = 1259 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 = 35 Synch Lost time, - time, during which SL alarm is switched on.
AvTime = 89773 Availability time. Please refer to ITU-T recommendation G.826
(Annex A) for definition of availability of the path or connection.
UnAvTime = 1258 Unavailability time.
BER = No Errors Indicates BER within the last BER time frame. BER time frame length
(in seconds) can be changed with ‘bertime’ command.
BBER = 5.9e-12 Indicates background BER.
BBLoop =OFF Indicates if the base-band loop is switched on or off.
3.1.2 “Setup” Mode of the LCD Management Interface
The following table describes parameters available for change from the IDU LCD in Setup
mode. Algorithm of LCD operation is shown on Flow Chart 1, page 57.
Table 10

Access Code Specify the panel access code (a number from 0 – 200) that was set
up from Telnet or ASCII console to enable any adjustments from IDU.
Restart CPU Restarts management module CPU for the new IP settings to take
effect. Resets all management counters.
Reset Counters Resets 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 9.
Write config Saves all settings in EPROM of management controller.
Remote IP Specifies the IP address of the remote (far-end) IDU Ethernet
management port.
Change Chan ## Set the Rx and Tx frequency.
“Change Chan” item provides ODU Tx and Rx frequency setup
functionality:
If this item is chosen LCD display shows, for example:
where “163” – number of currently used Tx channel and “Tx” -

frequency appropriate to channel.
This immediately changes the channel setting for both local ODUs, but
only one ODU is transmitting at a time, - the transmitter of the other
ODU is switched off.
ODU1 Tx Power Adjust the Transmitter power for ODU1 or ODU2.
+5dBm The default setting is “OFF”, allowing safe deployment of the
equipment avoiding interference risk with other radio equipment.
Capacity 34M Set the maximum capacity (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.
34M MUX speeds Sets the data rate for each multiplexer slot; use 1E1…4E1 modes for
E1 modules, and 2M…16M modes for Ethernet and V.35 modules;
supported speeds for each slot are the following:
CFM-MP-MUX
• CFM-MP-MUX with the maximum capacity of 8 Mbps: all slots
support speeds 0…8 Mbps with 2 Mbps step.
• CFM-MP-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-MP-MUX with the maximum capacity of 34 Mbps: slot 2 and
slot 3 supports speeds 0…16 Mbps with 2 Mbps step; slot 4
supports speeds 0…8 Mbps with 2 Mbps step; slot 1 supports
speeds 0…8 Mbps with 2 Mbps step and RMN (remaining capacity)
and FOD modes. In RMN mode the slot operates with any capacity
equal to (34 – C2,3,4) Mbps, where C2,3,4 – the sum of capacities of
slots 2, 3 and 4. The slot 1 is the only slot which supports capacity
above 16 Mbps, including the maximum capacity of 34 Mbps. The
FOD mode should be used for compatibility with the CFM Full
Outdoor Unit, operating with WAN capacity of 34 Mbps. In case if
the opposite site has the CFM series FODU installed, and link
operates with 34 Mbps capacity, the CFM-MP-MUX must have one
of the following configurations:
In case if FODU and CFM-MP-MUX operates with 34 Mbps
capacity
Slot 1 Slot 2 Slot 3 Slot 4
FOD 1E1 1E1 0M
Modes
FOD 0M 0M 0M
FOD 1E1 0M 0M
FOD 0M 1E1 0M
The numbering of slots is shown in Figure 2.2.
CFM-M4P-MUX
capacity. Slot 1 supports RMN (remaining capacity) mode. The total
capacity per both slots will not exceed 4 Mbps.
Select IP IP and NETMASK – IP address and netmask of the Ethernet port of

the management controller (default IP address - 192.168.205.010 or
Select NETMASK
192.168.206.010, default netmask 255.255.255.000)
Select Gateway
Gateway – IP address of the management console (Web or Telnet)
directly connected to the Ethernet management port or the IP address
of the gateway if the console is connected via network (indirectly), the
default value is 255.255.255.255 (no gateway specified).
IP, Netmask and Gateway parameters provide the means of
addressing the IDU management controller in order to control and
manage IDU locally and monitor ODU both locally and remotely.
Note: It is necessary to restart the management CPU for any changes
in IP settings (including SNMP terminal and service channel IP
settings) to take effect.
Service line - Select local IP - Sets the IP address of the local SLIP port.
- Select remote IP - Sets the IP address of the remote SLIP port.
- Sel. remote MASK - Sets the IP netmask for the remote IDU SLIP
port.
- Ping remote – pings the far-end IDU SLIP port, and displays
packet travel time in milliseconds.
RF loopback OFF Turns off the RF loopback (local), RF loopback ON turns the RF
loopback on.
BB loopback OFF Turns off the baseband loopback (any), BB loopback ON sets the
digital baseband loopback, BB loop analog sets the analog loop.
Modules This item contains all the commands for configuration of the installed
modules.
Notes:
− E1 interface – switch between 120 Ω and 75 Ω port of the E1
module;
− V.35 clock – invert the RxC signal. For more information refer to
V.35 Interface Module Installation and Configuration Guide, this
document can be found in the accompanying documentation CD.
Switch The ‘switch’ menu offers to configure all parameters related to 1+1
switching, for information about parameters regarding 1+1 switching,
see 1+1 configuration commands table in chapter 3.4.
Setup mode menu tree
Access code Change
Restart CPU * - current channel number
Reset Counters ** - 'Dloop' - digital loopback
Write Config *** - 'Aloop' - analog loopback
Loopbacks ODU1 RFloopb. ON
ODU1 RFloopb. OFF
ODU2 RFloopb. ON
ODU2 RFloopb. OFF
BB loopback Change Bbloop ON
Change Bbloop analog
Change Bbloop OFF
Outdoor unit ODU1 Chan ##* Change Chan ##
ODU2 Chan ##* Change Chan ##
ODU2 Tx Power Change Tx Power
ODU1 Tx Power Change Tx Power
Tx Frequency Change
Tx Frequency Change
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
Switch Active Link Change (1, 2)
RF level delta Change
ODU2 level max Change
ODU2 level min Change
ODU1 level max Change
ODU1 level min Change
Switch delay Change (1...900 sec.)
Force ON link Change (1, 2, none)
Note: CFM-M4P-MUX IDUs the Module menu has only Module 1 and Module 2 submenus.
3.2 Resetting the IDU

Depending on the method used, the user may reset the whole terminal (IDU+ODU) or the
management controller individually, see table below for details.
Reset through the LCD menu system Restarts the management module. Resets all
using “Restart CPU” option or from the management counters.
Telnet/ASCII console using “restartcpu”
command
Reset action using hidden button at the Restarts both the multiplexer module and the
rear side of the IDU (see Figure 2.5) management module. Resets all management counters.
Note: This may require a pin, at least 15 mm long,
approx. 1.5 mm in diameter.
Unplugging of power supply Restarts the multiplexer module and the management
module. Resets all management counters.
3.3 RS-232 Serial Management Port

The RS-232 serial management port provides terminal management via connected PC or
other terminal device or modem.
The terminal connected to the serial management port provides the same management
functionality as Telnet interfaces (refer to Command Interface). In order to interconnect the
IDU and the management terminal directly through serial ports, a “straight through modem
cable is needed.
IDU RS-232
PC/Terminal
IDU RS-232
Modem PC/Terminal
Modem
If using modems, the management terminal is connected with the IDU remotely through a
telephone line. In this case the modem, which is connected with the IDU should be set to
Auto Answer mode.
Telnet management window
In order to connect the console to the Radio via RS-232 interface, the serial port of the
management console should be configured as 19200 8-N-1, no data flow control.
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” or modem serial
cable (null-cable).
2. Run “Hyper Terminal” program.
3. Make a New connection, enter connection name.
4. Choose port (COM1 or COM2).
5. Set port settings (bits per second: 19200, data bits: 8, parity: none, stop bits: 1, data
flow control: none).
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.4 for available commands.
3.4 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.4.4.
Common commands
Command Description
Time Show current date and time.
Time <YYYY-MM-DD HH:mm:ss> Set the date and time. The clock is not available on 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.
Muxspeeds Set the data rate for each multiplexer slot. See Table 10 for
{slt1}+{slt2}+{slt3}+{slt4} more information about configuration of MUX slot speeds.
Example: muxspeeds rmn+2e1+2e1+2m.
capacity {8M|16M|34M} Set the multiplexer capacity (WAN data rate). After the capacity
change, the user must manually reconfigure all MUX slot speeds
using ‘muxspeeds’ command; the new configuration must be
saved using ‘write’ command.
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
specified address and then waits for a reply.
RxAlarmLevel <RxLevel> Set the Rx signal level at which the Radio Alarm is switched on.
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.
Common commands
Command Description
Webrefresh <refreshperiod> Refreshes the contents of WEB interface with a specified period
(refreshperiod); The period is given in seconds; the minimum
period is 2 seconds.
BBloop {on | analog | off} Set baseband loopback, “on” – set digital loopback (dual),
[duration] “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 {ODU1 | ODU2} {on | Set RF loopback, - “on” – set loopback, “off” – suspend
off} [duration] loopback. Duration can be from 1 to 10 minutes, it is equal to 1
min. by default. Example: Rfloop odu1 on 3
resetWDT 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.
Exit Close Telnet session (same as to press Ctrl+D)
telnet <IP_address> Open Telnet session with the IDU, IP_address – IP address of
the IDU management Ethernet port.
Disable {telnet | www | snmp | “telnet” – Disable Telnet interface
rip}
“www” – Disable Web interface
“snmp” – Disable SNMP interface
“rip” – Disable RIP
Note: 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.
RestartCPU Restart CPU of the management controller (new IP settings will
take effect). Resets all management counters.
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 {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
Common commands
Command Description
Mod dump Show a list of modules and contents of their respective CPU
registers (in hexadecimal system). This command is for
diagnostic purposes only.
Bertime <seconds> Change time frame for BER measurement (in seconds).
Ethernet {port1 | port2} Configures Ethernet management ports (1 and 2): change
connection {auto|10fdx connection mode for port 1 or port 2.
|10hdx|100fdx|100hdx}
Ethernet {port1 | port2} Configures Ethernet management ports (1 and 2): enable or
flowcntrl {enable | disable} disable flow control for port 1 or port 2.
Ethernet stat Displays the configuration and actual status of Ethernet
management port 1 and port 2.
1+1 configuration commands

Command Description
Switch stat Display information regarding 1+1 protection.
Switch mode {FD | Change operation mode of the 1+1 protection; for information
independent | HSB } about operation modes, refer to Chapter 2.5.
Switch {enable | disable} enable - enables 1+1 switching to be performed considering
rxmin, rxmax, delta and BER parameters.
disable – 1+1 switching is performed only in case of SL alarm.
The factory setting is ‘disable’.
Switch active {1|2} Change currently active Rx side, this command is applicable in
HSB and independent operation modes only.
Switch activetx {1|2} This command works only in Independent mode; - switch the
active ODU for Tx traffic. Note: In Frequency diversity mode both
ODUs will transmit, in HSB mode the transmitting ODU is set the
same as for Rx traffic (receiving ODU).
Switch force {1|2|Off} Force the side (1 or 2) to be active ignoring any condition(s) that
could cause to switch over to other side; “Off” – normal mode.
Switch rxmin <minRXlevel> Sets the minimum RX signal level, - if the RX signal appears below
it, the Rx traffic is switched from other ODU.
Switch rxmax <maxRXlevel> Sets the maximum RX signal level which, when exceeded, causes
to switch to the other ODU.
Switch delta <RxDifference> Sets the difference between link 1 RX signal level and link 2 RX
signal level which, when exceeded, causes to switch to the other
link with the higher RX signal level unless there is no conflict with
the “RF level max” parameter.
1+1 configuration commands
Command Description
Switch ber <BER_margin> Sets the maximum BER level which, when exceeded, causes to
switch over the Rx traffic from the other ODU.
Switch delay <seconds> Specify minimum delay between consecutive switchover attempts.
The default value is 2 seconds. The ‘switch delay’ must be
specified different at both sides of the hop, it is recommended to
specify 2 seconds for IDU at one side of the hop, and 3 seconds
for other side IDU.
Switch show {yes | no} - ‘yes’ – the IDU notifies about 1+1 switchover operations via
Telnet and ASCII management, by sending message, for
example:
SWITCH ACTIVE ODU[1] – SyncLoss problems when active ODU2
The message shows which ODU is set as active (receiving) and

why the switchover operation was performed.
- ‘no’ – disable notifications about switchover operations
(default)
Configuring ATPC settings

Command Description
ATPC enable Enable ATPC feature
ATPC disable Disable ATPC feature
ATPC delay <seconds> Specify minimum time delay (in seconds) between Tx
power adjustments; default value 1 second.
ATPC delta <Tx[dB]> Specify step for Tx power adjustments; default value is 1
dB, changing of this value is not recommended.
ATPC TXmin {1|2} <Tx[dBm]> Specify minimum Tx level (dBm), for link 1 or link 2.
ATPC TXmax {1|2} <Tx[dBm]> Specify maximum Tx level (dBm), for link 1 or link 2.
ATPC RXmin {1|2} <Rx[dBm]> Specify minimum Rx level (dBm), at which the Tx power
will not be changed for link 1 or link 2.
ATPC RXmax {1|2} <Rx[dBm]> Specify maximum Rx level (dBm), at which the Tx power
will not be changed for link 1 or link 2.
ATPC stat Display ATPC related parameters.
ATPC trace { on | off} Enable (on) or disable (off) displaying of information about
Tx power when ATPC adjustment occurs.
Configuring ODU parameters

Command Description
Chan {ODU1 | ODU2} <channel#> Set the ODU Tx and Rx frequency. Channel numbers
and corresponding Tx/Rx frequency values are found
in tables in the document ‘Channel plans’.
Txfreq {ODU1 | ODU2} <frequency-kHz> Set the ODU Tx\Rx channel by specifying Tx frequency
as integer in [kHz] units.
Example: txfreq 14711000
Txpower {ODU1 | ODU2} {-10|- Set the ODU Transmitter power [dBm]. The default
9|…|0|+1|+2|…|+20 |off} setting is “OFF”. Note: the IDU has an ATPC feature
which is disabled by default.
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.
Diag power Display power supply voltages supplied to PCBs and ODU power. Example:
SAF local>diag power
Power supply:
U +3.3V = 3.36V
U +5V = 5.12V
U -5V = -5.16V
U ODU = 23.64V
I ODU = 0.00A
P ODU = 0.00W
Iodu max= 0.75A
SAF local>
Mac Verify the MAC address of the Ethernet management port.
Ver Display hardware and software version of the IDU and ODU, and IDU and ODU
serial number. Example:
SAF>ver
SAF CFM-MP-MUX V4.20 2006.06.28
(c) 2006 SAF
SAF microwave radio
Mux Ver HW:1, SW:15, Speed:34368
Pow Ver HW:1, SW:3
IDU SN: 302090100172
ODU[2]: SAF CFM-18-LM +19dBm v2.20test1 2005.05.26
ODU[2] SN:C18RFM02H
ODU Display software version of both ODUs.
sernum Display IDU serial number.
ustat Display inputs and outputs of the alarm port.
Configuring E1 Interface Module parameters

Command Description
Mod {1|2|3|4} setE1 {Aloop | Set the analog, digital or remote loopback in the module (Aloop
Dloop | Remote | Off} – 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)
Configuring 4xE1 Interface Module parameters

Command Description
Mod {1|2|3|4} setE1 {port1 | port2 | Set the analog, digital or remote loopback in the module
port3 | port4} {Aloop | Dloop | (Aloop – analog loopback; Dloop – digital loopback, Remote
Remote | Off} – remote loopback, off – disable current E1 module
loopback). Example: Mod 3 setE1 Dloop
Configuring 4xE1 Interface Module parameters
Command Description
Mod {1|2|3|4} setE1 {port1 | port2 | Enable/Disable the transmission of AIS signal (for testing
port3 | port4} {on | off} purposes).
Configuring V.35 Interface Module parameters

Command Description
Mod {1|2|3|4} setV35 speed {64 | Set the speed of V.35 interface (in kbps).
128 | 256 | 512 | 1024 | 2048 | 4096 |
6144 | 8192}
Mod {1|2|3|4} setV35 phase {normal Invert the RxC clock signal (it is transmitted from V.35
| inverse} module to user equipment)
Mod {1|2|3|4} setV35 polarity Invert the incoming and outgoing data signals (RxD –
{normal | inverse} 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 | Set the sync status of V.35 interface module, ie. master or
Slave} slave.
Example: Mod 2 setV35 txc slave
Mod {1|2|3|4} setV35 fr {ON | ON – switches on fractional mode, fractional mode can be
PCM31 | PCM30 | OFF} switched on only if slot speed is 2 Mbps;
OFF – switches off fractional mode (uses all available
bandwidth).
Mod {1|2|3|4} setV35 mode {PCM31 The “mode” parameter refers to fractional mode:
| PCM30} PCM30– total of 30 timeslots can be used (except timeslot
1. and 16.)
PCM31– total of 31 timeslots can be used (except timeslot
1.).
Mod {1|2|3|4} setV35 TSC <count of Specify count of timeslots (up to 31).
time slots> The default TSC value depends on mode, - if mode is
PCM30, default value is 30, if mode is PCM31, - 31.
The count of timeslots must be equal to “ones” in TSM
parameter.
Mod {1|2|3|4} setV35 TSM <time slot Specify time slot selection mask. The length of the mask
select mask> must be 32 symbols, with “1” and “0” only. For example, if
all available timeslots are selected in mode PCM31, the
command is:
Mod 1 setv35 tsm 11111111111111111111111111111110
In PCM30 mode
Mod 1 setv35 tsm 11111111111111101111111111111110
Configuring Low capacity 2-port 100Base-T Ethernet Bridge Module

Command Description
Mod {1|2|3|4} setf2bridge {port1 | Configure port speed and duplex, 10hdx – 10 Mbps half
port2} connection {auto | 10hdx | 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 ports is
port2} priority {low | high} low.
Configuring Low capacity 2-port 100Base-T Ethernet Bridge Module
Command Description
Mod {1|2|3|4} setf2bridge {port1 | Enable or disable flow control for the specified port.
port2} flowcntrl {enable | disable}
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.
The subcommand for resetting these counters is:
mod {1|2|3|4} statistics reset
Configuring 1-port 100Base-T Ethernet Bridge Module

Command Description
Mod {1|2|3|4} setbridge Configure port speed and duplex, 10hdx – 10 Mbps half duplex,
connection {auto | 10hdx | 10fdx 10fdx - 10 Mbps full duplex, etc.
| 100hdx | 100fdx} Example: Mod 3 setbridge connection 100fdx
The factory setting is auto.
Mod {1|2|3|4} setbridge flowcntrl Enable or disable flow control.
{enable | disable}
Mod {1|2|3|4} statistics Displays statistical information:
− received packets and bytes,
− transmitted packets and bytes,
− count of FCS errors for LAN and WAN port,
− collisions for LAN port.
The subcommand for resetting these counters is:
mod {1|2|3|4} statistics reset
Configuring Ethernet management ports (located on IDU rear panel, see Figure
2.5)
Command Description
ethernet stat Displays the Ethernet statistics for port1 and port2. Example:
SAF>ethernet stat
Fast 2 Chan. Ethernet interface.
Configuration
Port 1
Speed: Auto
Duplex: Auto
Flow cntrl: Enabled
Port 2
Speed: Auto
Duplex: Auto
Flow cntrl: Enabled
Actual status
Port 1
Link: Off
Speed: 10Mb
Duplex: Half
Flow cntrl: Rx:Off Tx:Off
Port 2
Configuring Ethernet management ports (located on IDU rear panel, see Figure
2.5)
Command Description
Link: On
Speed: 100Mb
Duplex: Full
Flow cntrl: Rx:On Tx:On
Note: in case statistics display that Link is Off, the rest of Actual
Status data is not credible.
Configure port speed and duplex, 10hdx – 10 Mbps half duplex,
ethernet {port1 | port2}
10fdx - 10 Mbps full duplex, etc.
connection {auto | 10fdx |
10hdx | 100fdx | 100hdx} Example: ethernet port1 connection 10fdx
The factory setting for both ports is auto.
ethernet {port1 | port2} Enable or disable flow control for the specified port.
flowcntrl {enable | disable}
Example: ethernet port1 flowcntrl enable
Security commands
Command Description
Enable password <password> Specify a password to prevent unauthorized access to the
ASCII PC terminal (connected through RS232 serial port).
For more information, see chapter 3.4.4.
Panel access <accesscode> Specify a password to prevent unauthorized configuration
through the IDU management interface. The password can
be a number from 0 – 200.
For more information, see chapter 3.4.4.
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.
WWWuser <username> <password> Specify a password (1 - 20 symbols) to prevent
unauthorized access to the Web terminal.
Telnetuser <username> <password> Specify a password (1 - 20 symbols) to prevent
unauthorized access to the Telnet terminal.
FTPuser <username> <password> Specify username and password (1 - 20 symbols) to
prevent unauthorized connection to FTP server.
Management network configuration commands

Command Description
Start ftp Runs the FTP server on the IDU. By default it is switched off. In order
to use FTP server, it is required to:
1) Start FTP server using ‘start ftp’ command;
2) Specify username and password using ‘ftpuser’ command.
start tftp Runs the TFTP on the IDU, by default it is switched off.
Management network configuration commands
Command Description
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 (this requires to
restart the management module CPU for changes to take effect).
IP gw <IPaddress> Set the IP address of the default gateway connected to the Ethernet
management port (this requires to restart the management module
CPU for changes to take effect).
IP seraddr <IPaddress> Set the IP address of the serial port of service channel for the local
(near-end) IDU management module (requires to restart the
management module CPU).
IP remaddr <IPaddress> Set the IP address of the serial port of service channel for the remote
(far-end) IDU management module (requires to restart the
management module CPU).
IP remmask <IPnetmask> Set the netmask of the serial port for the remote (far-end) IDU
management module (requires to restart the management module
CPU).
Route add Add a static route to the routing table for packets destined to the
<destinationIPaddr> Mask network(s) which are not to be accessed via radiolink. The variable
[netmask] <gateway> “metric” is set to 1 by default. Example:
[metric]
Route add 192.168.205.0 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 enable
<communityname> parameters to be read (not configured). The default community name
to read parameters is saf-public.
SNMP community write Specify the community name of the agent to enable parameters to be
<communityname> written (configured). The default community name for writing
parameters is saf-private.
SNMP host add Adds the host IP address to the IDU SNMP host table. If the SNMP
<IPaddress> host connected to the IDU is not added to the IDU SNMP host table,
the IDU will not respond to the SNMP requests from that host.
SNMP trap <IPaddress> Set the IP address of the management terminal with the installed
Trap Manager software, based on SNMP platform (requires to restart
the management module CPU).
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.
Commands for script editing
Command Description
cfg backup <filename>
Save current configuration script in text file on the Flash disk, with
the specified filename.
cfg restore <filename>
Load the configuration script (specified text file) in RAM, but does not
execute the script. Further,
− to apply the script (execute commands), use ‘cfg run’ command.
− to store the script in EEPROM, use ‘write’ command.
Cfg factory yes
Reset the configuration by loading in EEPROM the script with default
settings. This command performs the following actions (in the
following order):
1. clears the current script from EEPROM,
2. creates and stores in EEPROM the new script with the following
settings:
- IP addr 192.168.205.010 or 192.168.206.010
- IP mask 255.255.255.000
- IP gw – 255.255.255.255 (default gateway - none)
- IP seraddr 192.168.0.10 – (SLIP configuration, - IP address
of the local serial port)
- IP remaddr 192.168.0.11 – (SLIP configuration, - IP address
of the remote serial port)
- Enable rfweb yes (enable configuration from Web terminal)
- SNMP trap 255.255.255.255 (none)
- RxAlarmLevel <#> (# - default value, see description of
rxalarmlevel command)
- 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’.
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 (| ).
3.4.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.
3.4.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.5.
- 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.5; 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 3.4.1 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.
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.
3.4.3 Storage of radio parameters
The radio parameter values (transmit frequency and power) are stored internally in Flash
memory of the Radio unit, the Radio operates exactly with those values stored in its Flash
memory. When the radio parameter is modified while the equipment is in operation, the
corresponding radio parameter value in the Radio Flash memory is overwritten with the new
one and applied in operation. Since the radio parameters are stored in ODU in Flash
memory, it is not necessary for the IDU configuration script (bootstrap) to contain strings
that configure radio parameters. In case if the configuration script stored in IDU EEPROM
contains strings that configure radio parameter(s), each time the equipment is booted, the
radio parameter values written in the IDU bootstrap are uploaded to the Radio and the
previously stored radio parameter values in Flash memory are overwritten with those in the
IDU bootstrap. Hence the radio parameter configuration in the IDU bootstrap has a higher
priority as they will override the values stored in the Radio Flash memory when the
equipment is rebooted.
It is useful to write the radio parameter configuration in the IDU configuration script for the
purpose to be able to quickly replace the ODU later.
3.4.4 Security commands
General tips
Telnet server supports one user only. The default username and password for Telnet
terminal is:
− Username (login): telnet
− Password: saf
− 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 3.1), press
Esc key twice.
Figure 3.1
− 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.
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 3.1.2). 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 by 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).
3.5 Updating software

Generally the user can update the IDU management software by uploading the appropriate
firmware file to IDU Flash disk, and then edit boot configuration file if necessary. The file
upload can be performed
- via Ethernet management port using FTP (recommended),
- via Ethernet management port using TFTP, or
- via RS232 serial port using Xmodem protocol.
To simplify the software update process, SAF Tehnika provides special update package as
new version is available. This update pack is available as archive (e.g. mpmux419.saf.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.5.1 and 3.5.3 describe other methods how to update the software without using
update pack.
3.5.1 Uploading file via Ethernet management port (TFTP)
Assuming that the IDU IP settings are properly configured, proceed as follows:
1) Connect the IDU to network or directly to PC,
2) Make sure TFTP is running on IDU (by default, the TFTP is switched off); to run the TFTP
on IDU, connect to IDU with Telnet client and enter the following command: ‘start tftp’.
3) Run the program that enables to use TFTP service, for example command interpreter
(cmd.exe) if using Windows, see Figure 3.2.
4) For example, to upload the firmware file ‘mmux400.elf.ezip’ with attribute flags ‘E’ and
‘c’, enter command:
tftp –i 192.168.205.11 put C:\files\mmux400.elf.ezip,Ec
where:
‘-i’ – key which specifies that file must be transferred in binary image transfer mode;
‘192.168.205.11’ – IDU Ethernet management port IP address (host);
‘C:\files\mmux400.elf.ezip’ – firmware file (source);
‘Ec’ – file attribute flags ‘E’ and ‘c’; the attribute flags are separated from file name or
source with comma (only comma and no space) and there are no commas or spaces
between flags;
Figure 3.2
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.
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 41.
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.
3.5.2 Uploading file via Ethernet management port (FTP)
Before uploading file via FTP, make sure IDU FTP server is running and username and
password are specified, using commands “Start ftp” and “FTPuser <username>
<password>” accordingly.
- Open command window.
- Start FTP client by entering “ftp” command (“ftp>” prompt will appear).
- Connect to IDU FTP server using command “open <IDU_IP_address>”. Type in
username and password when prompted.
- Enter command “type binary’ to make sure the binary transfer mode is selected.
- Use command “send <local file> <remote file>,<flags>” to upload files to IDU Falsh
disk. For example:
send c:\boot.ini boot.ini,Be
Use flags ‘E’ and ‘c’ if the file is firmware file; if the file is boot configuration file
(boot.ini), the flags must be ‘B’ and ‘e’ (‘Be’); the flags for configuration backup files
may not be specified.
Use command “ls” to list files on IDU flash disk.

Use command “delete <filename>” to delete the fale from IDU Flash disk.
3.5.3 Uploading file via serial port (Xmodem)
File upload via serial port takes much longer time compared to using TFTP and should be
used only in case if Ethernet connection with IDU management system is not available, or
does not start normally.
1) Connect the 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 3.3):
Figure 3.3
5) Enter ‘reset’ command to exit from MicroMonitor mode and restart the IDU.
6) Proceed with steps 4) and 5) in chapter 3.5.1.
! NOTE: After any type of upgrade and when the IDU is rebooted, it is necessary to enter
the following command via Telnet or Hyper Terminal:
‘capacity <cap>m force’, where ‘<cap>’ can be 8, 16 or 34 respectively, depending on the

capacity used.
Example:
SAF>capacity 34m force
3.6 Ethernet Management Port

The Ethernet management port of the IDU terminal is intended as main source of
management connectivity and will provide the broadest range of management functionality:
• SNMP management via integrated SNMP agent of management board;
• Web management via integrated Web server of management board;
• Telnet server and CLI interface.
Ethernet interface could be used:

• To connect IDU to PC/Laptop to manage IDU;
• To LAN to constantly monitor IDU;
• To router or any other TCP/IP packet network termination unit to have IDU as part of
network for management information.
3.6.1 SNMP Interface
The SNMP management allows:

− Reading and configuring parameters of IDU via SNMP;
− Receiving 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 form 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
provided MIB file to the MIB browser application’s MIB module.
SAF MIB files are 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 *****

1: activeLink.0 (integer) link2(2)
2: localLink1Status.0 (integer) linkoff(3)
3: localLink2Status.0 (integer) on(4)
4: remoteLink1Status.0 (integer) unreachable(1)
5: remoteLink2Status.0 (integer) unreachable(1)
6: remoteControlStatus.0 (integer) unknown(0)
7: localLink1RxLevel.0 (integer) -65
8: localLink2RxLevel.0 (integer) -70
9: remoteLink1RxLevel.0 (integer) 0
10: remoteLink2RxLevel.0 (integer) 0
11: localLink1rfAlarm.0 (integer) 0
12: localLink2rfAlarm.0 (integer) 1
13: remoteLink1rfAlarm.0 (integer) 1
14: remoteLink2rfAlarm.0 (integer) 1
15: localLink1SyncLostAlarm.0 (integer) 0
16: localLink2SyncLostAlarm.0 (integer) 0
17: remoteLink1SyncLostAlarm.0 (integer) 1
18: remoteLink2SyncLostAlarm.0 (integer) 1
***** SNMP QUERY FINISHED *****
Sample of SNMP query
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 status:
booting(1) none – not initialized;
ok(2) testing, illegalSpeed, error – reserved
testing(3)
error(4)
termIduTemperature Integer (32 bit) Temperature within IDU
(range: -128..127)
termRfCablePowerStatus Integer (32 bit) off(0) Indicates power consumption of the
ok(1) 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
Variable Name Variable Type Value List Description
bbOperation Integer (32 bit) none(0) Operational status of the Base-band
booting(1) modem:
ok(2) none – not initialized
testing(3) loopback – Base-band loop is set on
loopback(4) testing, illegalSpeed, error – reserved
illegalSpeed(5)
error(6)
bbLinkCapacity Integer (32 bit) Base-band link capacity in Kbps
bbLinkCapacityDescription String Comment on Base-band link
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 being
error(4) 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
high(1)
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
bbVersion String Textual version of the Base-band
controller software
bbOperation Integer (32 bit) none(0) Operational status of the Base-band
booting(1) modem:
ok(2) none – not initialized
testing(3) loopback – Base-band loop is set on
loopback(4) testing, illegalSpeed, error – reserved
illegalSpeed(5)
error(6)
bbLinkCapacity Integer (32 bit) Base-band link capacity in Kbps
bbLinkCapacityDescription String Comment on Base-band link
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
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.
3.6.2 Web Interface
The CFM-MP-MUX and CFM-M4P-MUX IDU management system is running a Web server
which allows remote configuring and monitoring of the units (counters, radio parameters,
configuration etc.) from Web page via HTTP; the user can connect to Web server via
Ethernet management port. The Web server does not provide configuration of parameters
related to 1+1 switching (switch commands).
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
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)
By default, the Main Configuration window does not allow configuring ODU parameters
(frequency channel and output power); the radio parameter configuration from Web page is
factory-set as disabled. It can be enabled with ‘enable rfweb yes’ command from Telnet or
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
Command interface from Web

The Web interface allows using commands just like from Telnet or ASCII console. To use
commands, proceed as follows:
- Open Web browser;
- In navigation toolbar type “http://<ip_address>/configL.htm”, where <ip_address> is IP
address of the IDU; see example in the following screenshot;
- Enter Username and Password when prompted;

- Type the command in the “Command” box and press Enter.
3.6.3 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.4.
3.6.4 Engineering Order Wire
The service channel also enables the Engineering Order Wire (EOW) using IP telephones,
connected to the 10Base-T management port. For more information please refer to EOW
application guide.
3.7 Using IDU LCD
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. Using LCD
3.8 Alarm Port (I/O Port)

The Alarm port is optional feature.
The Alarm port shares the set of outputs of relay switches intended for the CFM site
supervision and the user inputs to connect an external device that requires to be supervised.
Each output of the port can be used either as NO type (normally open) or NC type (normally
closed).
The following alarms are available through the alarm port as parallel relay outputs:
• A: Power on\off relay. If power is on, the relay is closed (normal relay state); if
power is off – relay is open.
• B: SL – Synch Lost alarm, ON - relay is closed, OFF – relay is opened (normal
operation).
• C: RAI – Remote Alarm Indicator, ON - relay is closed, OFF – relay is opened (normal
operation).
• D: RA – Radio Alarm, ON - relay is closed, OFF – relay is opened (normal operation).
• Each output is available as normally opened and normally closed.
There are four parallel inputs of the alarm port available: input A, input B, input C, input D.
These inputs are used for connection of an external device which supplies DC voltage on
input, - “0” or “1”; the changes of inputs (triggering between “0” and “1”), can be monitored
from management terminal; refer to Chapter 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 4.
3.9 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
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.
Required to specify:
IP address/Net Mask,
Management Default Gateway
Console
Local Site (Terminal A) Remote Site (Terminal B)
IP parameters required to specify
See examples on the next page.
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
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
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 3.4 The IP configuration of the management channel via three 1+0 hops with the RIP
II switched on in each IDU; since the management controllers are running RIP II, there is no
necessary to specify gateway (see configuration strings in grey)
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 3.5. The IP configuration of the management channel via three 1+0 hops with the
RIP II switched off in each IDU; for proper routing between IDU management modules, the
default gateway and static routes must be set for each module
3.10 Default Settings
Parameter command or name Default
Parameter/description
Telnet / ASCII LCD value/setting
Rx signal level by which the RxAlarmLevel RxAlarmLev -77 dBm
Radio Alarm is switched on
MUX capacity (WAN data rate) Capacity Capacity (customer
specified)
MUX slot speeds Muxspeeds MUX speeds 0M+0M+0M+0M
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
Transmitter power txpower Tx Power 0 dBm
IDU name Name - SAF
SNMP community name of the SNMP - Saf-public
agent to read (all SNMP community read
parameters are read-only)
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 - (password
ASCII console disabled, - no
password required
to connect via
serial port)
Access number for LCD/Keypad Panel access - 0 (disabled)
Username and password for WWWuser -
Not specified.
Web terminal
Username and password for Telnetuser -
Not specified.
Telnet terminal
Switch operation mode Switch mode - HSB
Enable\disable 1+1 switching Switch - disabled
by performance, - Rx signal
level and BER level
Rx signal level difference Switch delta - 40 dB
Maximum RX signal level for Switch rxmax - -40 dBm
switchover to other ODU
Minimum RX signal level for Switch rxmin - -80 dBm
switchover to other ODU
BER margin for switchover to Switch ber - 10-3
other ODU
Minimum delay between Switch delay - 2 seconds
consecutive switchover
attempts
Forced side Switch force - off
3.11 Automatic Transmit Power Control (ATPC)
The ATPC feature is disabled by default. To enable it, use ‘ATPC enable’ command.
3.11.1 ATPC Algorithm
The local IDU receives from the far-end IDU information (each second) about Rx level
through the service channel; depending on the received Rx level parameter, the local IDU
adjusts the transmitter power according to the algorithm shown below.
Check info from far end
Link failure - Sync Loss and/or RAI

alarm is switched on. Tx level is set
Far end info OK NO
to maximum.
Tx level = Tx max
YES
BER level received from far end END
BER level > BER min ? YES Tx level = Tx max ? NO Increase Tx level by ‘Delta’
NO
YES END
Rx level indication received from far end
Rx level < Rx min ? YES Tx level = Tx max ? NO Increase Tx level by ‘Delta’
NO YES END
Rx level > Rx max ? YES Tx level = Tx min ? NO Decrease Tx level by ‘Delta’
YES
NO END
Rx level - the the Rx level figure received from the far-end

Rx max - maximum permissible Rx level at the far-end
Rx min - minimum permissible Rx level at the far-end
BER min - minimum permissible BER level at the far-end
Tx level - current transmitter power at the local site (Tx power)
Tx max - maximum permissible Tx power at the local site
Tx min - minimum permissible Tx power at the local site
Delta - the value by which the Tx power is increased or decreased
according to far-end Rx level indication (1 dBm by default)
Figure 3.6. ATPC algorithm
3.11.2 ATPC commands
Please refer to chapter 3.4.
3.12 Performing Loop-back Tests
Loopback tests are accessible using local or remote management methods.
All baseband and RF loopbacks (local and remote) for safety purposes can be set on a fixed
time interval only. The interface loopbacks (E1, V.35) does not have time limit and must be
switched off manually.
3.12.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:
select “Loopbacks” → select “RFloopback ON” → select “Yes”.
• V.35 interface loopback:
select “Modules” → select “Module # V35” → select “V.35 Loopback” → “Change
Loopback”, switch over to ON and confirm.
• E1 interface loopback:
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.
3.12.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 39).
• 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.12.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.
3.12.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.12.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 3.7. Baseband loopback modes: signal is looped in the modem
3.12.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.8. V.35 Interface Module Loopback
3.12.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.9. E1 Interface Module Digital loopback mode
2
I C bus
CPU
Multiplexer
IN
E1
Analog
G.703 Interface
HDB3
OUT
Figure 3.10. E1 Interface Module Analog loopback mode
2
I C bus
CPU
Multiplexer
IN
E1
Analog
G.703 Interface
HDB3
OUT
Remote
loop
Figure 3.11. E1 Interface Module Remote loopback mode
3.13 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 1,7
-90 0 1,6
1,5
-85 0,1 1,4
-80 0,2 1,3
RSSI port output, V
-75 0,3 1,2

-70 0,4 1,1
1,0
-65 0,5
0,9
-60 0,6 0,8
-55 0,7 0,7
-50 0,8 0,6
0,5
-45 0,9
0,4
-40 1 0,3
-35 1,1 0,2
-30 1,2 0,1
-25 1,3 0,0
-90 -85 -80 -75 -70 -65 -60 -55 -50 -45 -40 -35 -30 -25 -20 -15 -10 -5
-20 1,4
-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.
4 Pinouts
RS-232 management port pinouts

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” serial cable (modem cable) is
required.
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
DSR E 34 50 & 51 & 52
DCD (RLSD) F 33 53 & 54 & 55 & 56
DTR H 43
TxD+ P 18
TxD- S 17 Notes:
RxD+ R 28
RxD- T 27 * This information is for
SCTE+ U 20 user’s reference only
SCTE- W 19
RxC+ (SCR+) V 26
P GND – Protection
RxC- (SCR-) X 25 Ground
TxC+ (SCT+) Y 24 S GND – Signal Ground
TxC- (SCT-) AA 23
Ethernet and 1xE1 port pinouts
RJ-45 pin numbering

INPUT (Rx)
port
OUTPUT (Tx)
1 2 3 4 5 6 7 8 E1 interface pinouts Ethernet interface pinouts
IN OUT Not
(Rx) GND (Tx) used GND Tx Rx
12345678 12345678
Figure 4.1. E1 and Ethernet interface pinouts
4xE1 unbalanced (75 Ω) DB25 traffic port pinouts

See Figure 4.2 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.
4xE1 balanced (120 Ω) DB25 traffic port pinouts

According to pin numbering shown in Figure 4.2:
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.
Male DB25 connector
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 4.2. DB25 pin layout
Alarm interface port specification

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 4.3. 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
Input pins:
Input A Input B Input C Input D
Pin 32 16 17 18
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:

Impedance > 7 kΩ
R”0” = 1 kΩ max.
R”1” = 12 kΩ min.
Open contact voltage: +5V
Contact shortcut current: 0,7 mA.
5 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 67046840
- Fax: +371 67046809

CFM-MP-MUX CFM-M4P-MUX Indoor Unit Insta PDF

Uploaded by

Copyright:

Available Formats

You might also like

CFM-MP-MUX CFM-M4P-MUX Indoor Unit Insta PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CFM-MP-MUX CFM-M4P-MUX Indoor Unit Insta PDF

Uploaded by

Copyright:

Available Formats

CFM-MP-MUX /

Installation and Configuration Manual

© SAF Tehnika A/S 2006

Revision Date Comments

1.3 December, 2005 Information about CFGMXP02 version MP-MUX added

1.4 March, 2006 Information about ATCP added

Figure 1.1. Supported 1+1 configurations:

42.6 cm (16.93 ")

Hidden reset Ethernet

ASCII console port Ethernet Grounding

CFGMXP02/CFGM4P02 MP/M4P-MUX IDU Features:

Figure 2.5. Rear panel

2.3 Mechanical Data

IDU version Weight (with no modules), [kg] Dimensions HxWxD, [mm]

2.4.1 V.35 Interface Module

Table 5. V.35 Module LEDs (see Figure 2.6)

Loopback on V.35 module is

Data activity - data is being

2.4.2 100Base-T Ethernet Modules

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

100Base-T modules comply to:

Figure 2.7. 1xE1 module (front)

2.4.4 4xE1 Interface Module

Red Constant red indicates that E1 signal is

Yellow loop-back LED (loop- When loopback LED is switched on,

Figure 2.9. Block diagram of the CFM-MP-MUX and CFM-M4P-MUX IDU

The IDU consists of the following PCBs:

Power supply voltages and YES

Minimum delay between

RxLev > RxMin ?

BER level below specified

RxLev - the the Rx level figure received from the far-end

2.5.2 Independent Mode

2.5.3 HSB Mode

2.5.4 1+0 Operation Mode

2.6 FEC Coding

Figure 2.11. Label of the CFM-15-LM ODU

3.1.1 “Status Display” Mode of the LCD Management Interface

Parameter Values and description

RF Cable – OK Parameter indicates power consumption of the ODU units:

IDU t= 31C Indicates temperature inside IDU.

3.1.2 “Setup” Mode of the LCD Management Interface

Parameter Values and description

where “163” – number of currently used Tx channel and “Tx” -

Select IP IP and NETMASK – IP address and netmask of the Ethernet port of

3.2 Resetting the IDU

3.3 RS-232 Serial Management Port

Telnet management window

4. Choose port (COM1 or COM2).

1+1 configuration commands

The message shows which ODU is set as active (receiving) and

Configuring ATPC settings

Configuring ODU parameters

Configuring E1 Interface Module parameters

Configuring 4xE1 Interface Module parameters

Configuring V.35 Interface Module parameters

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

Configuring 1-port 100Base-T Ethernet Bridge Module

* SNMP QUERY STARTED *