CFM M MUX - Tech Description

CFM-M-MUX
Indoor Unit
Indoor Unit Management System
Technical Description and
Configuration Guide
SAF Tehnika A/S 2005
Table of Contents
1
2
CFM Multiplexer Indoor Unit Overview ....................................................................3

Indoor Unit Appearance ....................................................................................................4
2.1 Installation Notes...............................................................................................................4
2.1.1
2.1.2
2.2
Ports ................................................................................................................................................. 5
LEDs ................................................................................................................................................. 6
Interface Modules ..............................................................................................................8
2.2.1
2.2.2
2.2.3
2.2.4
V.35 Interface Module ............................................................................................................... 8

E1 Interface Module ................................................................................................................... 9
4xE1 Interface Module ............................................................................................................ 10
2-port 100Base-T Fast Ethernet Bridge Module ............................................................ 11
2.3 Labelling ..............................................................................................................................12

Configuration and Management .................................................................................13
3.1 LCD/Keypad .......................................................................................................................13
3.1.1
3.1.2
3.1.3
3.2
3.3
3.4
Status Display Mode of the IDU LCD Management Interface ............................... 13

Setup Mode of IDU LCD Management Interface ........................................................ 16
Interface Module LEDs ............................................................................................................ 19
Resetting the IDU ............................................................................................................20

RS-232 Serial Management Port ...............................................................................21
Ethernet Port .....................................................................................................................24
3.4.1
3.4.2
3.4.3
3.5
Web Management ..................................................................................................................... 24

Telnet management ................................................................................................................. 27
SNMP Management................................................................................................................... 27
Command Interface ........................................................................................................30
3.5.1
3.5.2
3.5.3
3.5.4
3.6
Working with configuration script ....................................................................................... 36

File system................................................................................................................................... 37
Storage of radio parameters ................................................................................................. 39
Security commands .................................................................................................................. 40
Uploading software .........................................................................................................42
3.6.1
3.6.2
3.7
Uploading file via Ethernet management port (TFTP) ................................................. 42

Uploading file via serial port (Xmodem)........................................................................... 43
Alarms..................................................................................................................................45
3.7.1
3.8
3.9
3.10
3.11
3.12
Alarm Port .................................................................................................................................... 45
Configuring Management Service Channel ............................................................46

Algorithm of LCD Operation.........................................................................................51
Replacing the Indoor Unit.............................................................................................52
Default Settings................................................................................................................53
Configuring Radio Parameters ....................................................................................54
3.12.1 Default ODU Settings............................................................................................................... 54

3.12.2 Configuring Tx Frequency ...................................................................................................... 54
3.12.3 Configuring Tx Power............................................................................................................... 55
3.13 Performing Loop-back Tests ........................................................................................56

3.13.1
3.13.2
3.13.3
3.13.4
3.13.5
3.13.6
4
5
6
7
Setting Loop Tests from IDU LCD/Keypad....................................................................... 56

Setting Loop Tests from Telnet/ASCII terminal............................................................. 56
Radio loopback ........................................................................................................................... 57
Base-band loopbacks ............................................................................................................... 57
V.35 Interface Module Loopback ......................................................................................... 58
E1 Interface Module Loopbacks ........................................................................................... 58
Pinouts.......................................................................................................................................59
Mechanical data....................................................................................................................62
SAF Tehnika A/S Contacts .............................................................................................63
References...............................................................................................................................63
The CFM-M-MUX IDU Management System Technical Description and Configuration Guide
Rev. 1.3 SAF Tehnika A/S 2005
1 CFM Multiplexer Indoor Unit Overview

Proprietary notice
The specifications or information contained in this document are subject to
change without notice due to continuing introduction of design improvements. If
there is any conflict between this document and compliance statements, the
latter will supersede this document.
This document describes the CFM modular multiplexer Indoor Unit, CFM-M-MUX,
covering hardware features, built-in management system, configuration
functionality, etc.
The CFM-M-MUX is part of SAF Tehnikas CFM series digital microwave radio
product family providing:
-
Means of interconnecting the user equipment with the Radio (ODU) at each
site of the 1+0 (unprotected) radiolink; The CFM-M-MUX Indoor Unit is
intended for use with the CFM-LM radios.
The modularity of the CFM-M-MUX IDU allows to install various CFM series
traffic interface modules, which include E1, 4xE1, V.35 and 10/100Base-T
interfaces (for more information please refer to chapter 2.2).
Local and remote management (incl. Web, Telnet, SNMP, ASCII),
TCP/IP service channel between sites over the radiolink,
Alarm interface (optional).
The CFM-M-MUX IDU supports various link capacities: 8 Mbps, 16 Mbps and 34
Mbps; the maximum WAN capacity 34.368 Mbps; the capacity is software
selectable. Any capacity can be selected for any frequency band.
The IDU is frequency-independent; the operating frequency is determined by the
ODU only.
Revision history
Revision
Date
Comments
1.0
January, 2005
1.1
February, 2005
1.2
June, 2005
For M-MUX SW ver. 4.09 (2005.05.31)
1.3
September, 2005
Chapter Labeling revised
2 Indoor Unit Appearance

2.1 Installation Notes
The CFM-M-MUX IDU is implemented as 19 rack mountable Aluminium 1U high
unit, the depth of the unit is 230 mm without front panel handles and 270 mm
with handles. Some space should be reserved for interface cables in front of the
IDU and RF cable behind the IDU, please see picture blow.
12 cm
(4.72 ")
23 cm
(9.10 ")
4 cm
(1.57 ") 10 cm 8 cm
(3.94 ") (3.15 ")
48.6 cm (19.29 ")
V.35
E1
42.6 cm (16.93 ")
The CFM-M-MUX IDU provides four sockets module slots, for installation of
interface modules. For information about what data rate each multiplexer slot
supports, please see Table 9.
The CFM-M-MUX IDU contains:
-
Multiplexer board;
Management controller board;
Power Supply module;
LCD and Keypad module;
Traffic interface modules.
SYNC
OUT
RADIO
REMOTE
LB
R
X
CFM-M-MUX
TX
CLEAR
- 48V +
AIS
All the aforementioned boards and modules are interconnected with flat ribbon
cables and snap-on connectors.
E1
C D S
IN
ENTER
ALARM
V.35
Figure 1. The CFM-M-MUX IDU, equipped with, E1 and V.35 interface modules
(front panel)
The numbering of multiplexer module slots is depicted in the following picture.
CLEAR
- 48V +
SYNC
RADIO
REMOTE
ENTER
Slot 1
Slot 2
Slot 3
Slot 4
ALARM
Figure 2. Numbering of module slots
2.1.1
Ports
The CFM-M-MUX IDU provides:

-
Interfaces:
-
Radio Unit (ODU), N-type Female connector;
The CFM-M-MUX IDU provide 1 up to 4 slots for installation of traffic port

modules (1 module per slot), for information about modules see chapter
2.2;
RS-232 serial management port;
10\100Base-T Ethernet management ports (2-port switch).
Alarm port (optional), for more information please refer to chapter 3.7.1.
LCD display and keypad buttons on the front panel of the IDU, to configure
and monitor the CFM site;
Port activity LEDs;
Power connector.
Table 1. Connectors
Port/connector
+-48V
(power socket)
Front panel connectors

Power connector, IDU should be powered from 20V 60V
DC power source. Both + or poles of the power
source could be grounded, one should make sure if the
chosen grounding wire is connected to ground on IDU
power connector.
Port/connector
Rear panel connectors
RF
(N-type connector)
N-type Female connector, the cable should be connected

to the Radio Unit (ODU);
RS-232
(DB9 connector)
2x10\100Base-T
Ethernet ports
(RJ-45 socket)
DB25 connector
Alarm port
RS232 management port for connection of ASCII console

(or analog line modem for the remote connection of ASCII
console). This port is also used to update management
software.
Ethernet switch management ports, for Web or Telnet
management; the ports have bridging function.
Alarm port. This feature is optional.
Serial management port
Ethernet management port
ODU port
Grounding screw
Figure 3. Rear panel
2.1.2
LEDs
Table 2. Front panel LEDs

Label
Color
Sync
Red
Description
Red Signal Lost LED indicates the loss of Multiplexer
synchronization; If not lit operating properly;
The SL LED is updated one time per second.
Radio
Red
Radio Alarm LED indicates problems with radio unit and

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

corresponding parameter is RxAlarmLev on the LCD
or RxAlarmLevel using Telnet/ASCII console. The
default value for this parameter is -77 dBm;
The humidity within the radio is too high (possibly
ODU is opened);
Transmitter malfunction (TxOut=Error)
RF Cable=Short cable is faulty, RF Cable=Off cable
or Radio is faulty;
Tx and Rx syntheser loops are not locked
(TxPLL=Error, RxPLL=Error)
If not lit operating properly (Rx=OK & TxOut=OK &

Humidity=Low & RF Cable OK & TxPLL=OK &
RxPLL=OK).
Note: the RA LED will also switch on if the Radio loopback
is active and/or if the transmitter power is switched off.
Remote
Red
Alarm
Yellow
The RA LED is updated one time per second.

Remote Alarm Indicator (RAI alarm), - indicates that the
far-end site has the SL alarm switched on.
User defined alarm LED, - the alarm type is specified by

user, the following options are available:
BER lower than 10-3,
BER lower than 10-6.
Note: The LEDs located on interface modules are described in chapter 3.1.3,
page 19.
Table 3.
Other front panel LED signals
Alarm
Wrong
Capacity
Description
In case if
the WAN capacity is lower than sum of MUX slot speeds (LAN
speed higher than WAN speed), or
one or more MUX slot speed settings does not support the
selected WAN capacity (for example, slot 1 configured with
RMN capacity while WAN capacity is 16 Mbps).
SYNC, RADIO, REMOTE and ALARM LEDs switch on and off

alternatively in the following combination:
(RADIO, REMOTE) <-> (SYNC, ALARM)
IDU
HARDWARE
FAILURE
If IDU hardware failure occurs, SYNC, RADIO, REMOTE and

ALARM LEDs simultaneously will be switching on and off.
Rear panel LEDs are shown in Figure 4.
Serial management
port
Hidden reset
button
Indicates operation of the

management module CPU
Ethernet
management ports
ODU
port
Grounding
screw
Ethernet link\activity 100 Mbps speed

LED
LED
Figure 4. Rear panel LEDs
2.2 Interface Modules

2.2.1
V.35 Interface Module
The V.35 interface module is provided with M34 standard connector. The V.35
module terminates 2, 4, 6, or 8 Mbps from modular multiplexer (from modular
Ethernet bridge multiplexer only 2 Mbps) and provides user selectable data rates
of 64 kbps, 128 kbps, 256 kbps, 512 kbps, 1024 kbps, 2048 kbps, 4096 kbps,
6144 kbps or 8192 kbps to V.35 interface port on M.34 connector.
Table 4. V.35 module LEDs
Color
TX
Green
SL
Red
Function
Data activity - data is
being transferred
from module's front
port to multiplexer.
Direction
V.35 MUX*
V.35 port failure.
Loopback
Active
Green
Data
Receiving
Active
Data activity - data is

being received from
multiplexer board
and transmitted to
module front port
Dual loopback,
please refer to
chapter 3.13.5 for
more information
about V.35 module
loopback.
MUX V.35*
TX
Red
Loopback on V.35
module is switched
on, informing that the
connection between
V.35 port and MUX
board is interrupted.
RX
RX
Data
Transmitting
Active
Signal Loss
SL
LB
Name
LB
LED
V.35
Figure 5. V.35 module (front)
2.2.2
E1 Interface Module
The E1 interface module is a single port module provided with two types of
interfaces:
120 balanced interface, connector type: RJ-45;
75 unbalanced interface, connector type: BNC, - requires a pair of coaxial

cables with BNC type connectors.
Both interfaces are provided for termination of 2 Mbps (G.703) streams.

Table 5. E1 Interface module ports
Out,
In
Two BNC connectors of the 75 unbalanced port provide means to

connect the customer equipment to the IDU;
Tx data stream is transmitted over OUT (output) port;
Rx data is to be received through IN (input) port.
RJ-45
RJ-45 connector for balanced 120 E1 interface.
Note: use either IDU keypad or console to switch between BNC and RJ-45 ports,
this is described in chapters 3.1.2 and 3.5 respectively.
Table 6. 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.
Steady red LED indicates the AIS signal from E1 input.
LB
Red
LoopBack LED (red) indicates loopback mode is activated

in the module.
OUT
E1
Steady green light indicates the data signal from E1 input.
RX
Red
LB
AIS
AIS
Green
TX
Rx
IN
Figure 6. 1xE1 module (front)
2.2.3
4xE1 Interface Module
The 4E1 module provides four E1 ports with RJ-45 connectors (120 interfaces),
the ports can be separately switched on/off, the speed of the module changes
according to the following table:
Active E1 ports
Module speed
4 (all ports)
3
2
1
0
8
6
4
2
0
Mbps
Mbps
Mbps
Mbps
Mbps
Each port has two LEDs indicating operations status of the port.
Table 7. Description of LEDs
Combination
LEDs
Description
Color
flashing green
Indicates normal operation of the channel,

no problems with signal reception.
any possible state

red
any possible state
blinking green and red
Constant red indicates that E1 signal is

lost. If red flashes momentarily, the bipolar
violation (line code error) was received
from user equipment.
AIS signal is being received from user
equipment.
any possible state

any possible state
Analog, digital or remote loopback mode is

switched on for that channel.
yellow
No LED is lit
U75
Channel is switched off.
E1
Figure 7. 4xE1 module with DB25 port (front view)
10
2.2.4
2-port 100Base-T Fast Ethernet Bridge Module
The 2-port FREB (Fast Remote Ethernet Bridge) module performs bridging
between LAN ports and WAN port, and between both LAN ports. The FREB
module terminates any capacity up to 34 Mbps from the multiplexer on two
100Base-T ports with RJ-45 sockets (UTP).
Features:
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.
The maximum available WAN traffic capacity of the bridge is possible if 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).
Ethernet link/activity LED
(green), if flickers, indicates
data transmission,
100 Mbps speed LED
(yellow), if this LED is switched on,
the port speed is 100 Mbps
Figure 8. FREB module LEDs
11
2.3 Labelling
The IDU label is found at the rear panel.
The IDU and ODU label contains the following information:
Product model name.

Product number (P/N): product number contains information of subband (A, B
or C) and band sid (L, H).
Serial number (S/N); the Serial Number has the following information:
4-digit product code,
Consecutive number of the product; the 5-digit consecutive numbering

for IDU label is separate for each IDU type (e.g. MUX IDU, REB IDU,
E1 IDU, etc.), for ODU label separate for each frequency band.
Product type and hardware version.
The Serial Number uniquely identifies the unit (IDU or ODU).
Product type (internal use only)
Hardware
version\
specification
Product model
Product number
4-digit Product code
assigned to Product
Notified body
Consecutive
number
Figure 9. IDU label
12
3 Configuration and Management

3.1 LCD/Keypad
LCD and keypad provides most basic method to locally configure and monitor the
local CFM terminal (IDU+ODU).
LCD display is constantly backlight and is able to display 2 lines of 16 symbols
each line.
LCD operates in two modes, Status display and Setup, please refer to Flow
Chart 1, page 51.
Keypad consists of 4 buttons:
Button
Description
ENTER
ENTER button is used
CLEAR
3.1.1
to switch from status display to setup mode.
to confirm the choice of selected value or parameter, or to

enter submenu;
CLEAR button is used
to cancel the choice and to move to previous (upper) menu

level;
to switch from the root menu of the setup to status

display mode.
Up/Down buttons are used:

-
To scroll through menu;
To choose parameter, and its value.
Status Display Mode of the IDU LCD Management

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

Parameter
Description
Tx=14518.500MHz
Rx=15246.500MHz
TxPower=+20dBm
Parameter indicates Tx frequency of the Radio.

Parameter indicates Rx frequency of the Radio.
Indicates current output power, see Table 9 for more
information.
Indicates various conditions of Rx signal from ODU:
OK - IDU receives acceptable signal from ODU;
Low - received signal level at IDU is too low for
proper operation;
Error - indicates internal fault in ODU receiver;
Loopback - radio loopback mode is switched on.
Indicates the level of the received signal.
Indicates signal attenuation in IDU-ODU cable, values of
0 -20 dB provide proper operation of IDU.
Indicates operation status of ODU transmitter:
Ok indicated proper operation;
Error indicates internal fault in ODU transmitter,
please contact sales representative or manufacturer.
Indicates operation status of ODU Tx Syntheser Loop
(PLL lock):
Ok indicates proper operation;
Error indicates internal fault in ODU transmitter.
Indicates operation status of ODU Rx synthesizer Loop
(PLL lock):
Ok indicated proper operation;
Error indicates internal fault in ODU receiver.
Indicates ODU internal temperature.
Indicates humidity level inside ODU,
Low indicate acceptable moisture levels;
High indicate too high level of humidity, condensing.
Indicates number of ODU management controller
restarts since counter was reset on power up.
Indicates connectivity status between IDU and ODU:
OK - indicates acceptable level;
Short - indicates short circuit in cable;
Off - indicates too low power consumption by ODU.
This is most likely due to the brake in the cable. If the
cable is intact, the ODU is faulty. While RF Cable = Off,
the IDU does not receive any data from ODU and will
not display any information related with ODU.
Indicates maximum transmitter power.
Indicates the Rx level (in dBm) at which the Radio
Alarm is switched on.
Indicates temperature within the IDU.
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.
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.
Time, during which all error measurements are
performed.
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.
Rx= OK
RxLev= -66dBm
Cable=5 dB
TxOut= Ok
TxPLL= Ok
RxPLL= Ok
ODU t= 23C
Humidity=Low
Restart= 99
No data from ODU
RF Cable OFF
PW max = 20
RxAlarmLev =-77
IDU t= 31C
BlkErr = 0
BBlkErr = 0
StatTime = 12107
ErrSec = 12194
14
SErrSec = 12214
SLTime = 12236
AvTime = 12306
UnAvTime = 9
BER = 4.8e-12
BBLoopback=OFF
Severely errored seconds. Severely errored second is a

one-second period which has a bit-error ratio 110-3
or during which SL alarm is switched on.
Synch Lost time, - time, during which SL alarm is
switched on.
Availability time. Please refer to ITU-T recommendation
G.826 (Annex A) for definition of availability of the path
or connection.
Unavailability time.
Bit Error Ratio. This indication is correct assuming, that
each block (WAN frame) may have maximum one
errored bit.
Indicates if the base-band loopback is switched on or
off.
15
3.1.2
Setup Mode of IDU LCD Management Interface
The following table describes parameters available for change from IDU in Setup
mode.
Algorithm of LCD operation is shown on Flow Chart 1, page 51.
Table 9
Parameter
Description
Access code
Specify the panel access code (a number from 0 200) to

enable configuration of the CFM site from IDU using
keypad. The panel access security feature can be enabled
by setting the panel access code as a number from 1 to
200, either from ASCII or Telnet terminal. If panel access
code is set as 0 (zero), the panel access security feature is
disabled.
Restart CPU
Reboots management controller; this will reset all

management counters.
Reset counters
Reset BlkErr, BBlkErr, StatTime, ErrSec, SErrSec, SLTime,

AvTime and UnAvTime counters. Counters are also cleared
when management controller is rebooted.
For more information about counters, see Table 8.
Write config
Saves current settings in EEPROM of management

controller, these settings will take effect the next time when
IDU will be restarted.
Loopbacks
Outdoor Unit
RF loopback OFF switch off the radio loopback

(local),
RF loopback ON switch on the radio loopback,
BB loopback OFF - switch off the baseband loopback
(any),
BB loop analog switch on the analog baseband loop,
BB loopback ON - switch on the digital baseband
loopback.
Tx Power - adjust the radio output power; the default
setting is OFF.
Change Chan change Tx/Rx frequency channel.
When choosing frequency channel, the LCD will display
only Tx frequencies, but when channel is changed, the
appropriate Rx frequency is also changed. Channel
numbers and corresponding Tx/Rx frequency values are
found in tables in the document Channel plans.
Modules
This item contains all the commands for configuration of the

installed modules. See Setup Mode Menu Tree below for all
commands available from Modules menu for 2-port
100Base-T, 1xE1, V.35, and 4xE1 modules.
Capacity
Set the maximum capacity of the multiplexer (WAN speed):

8 Mbps, 16 Mbps or 34 Mbps. Once the capacity is changed,
the IDU will configure the software for various IDU
components, this will take a few minutes. Once the
configuration is complete, the IDU will automatically
restart.
After the capacity change, the user must manually
reconfigure all MUX slot speeds from LCD or from
Telnet or ASCII terminal using muxspeeds
command; the new configuration must be saved
using write command.
16
16M MUX
speeds
Service line
Ethernet
Sets the data rate for each multiplexer slot; use 1E14E1
modes for E1 modules, and 2M16M modes for Ethernet
and V.35 modules; supported speeds for each slot are the
following:
CFM-M-MUX with the maximum capacity of 8 Mbps: all

slots support speeds 08 Mbps with 2 Mbps step.
CFM-M-MUX with the maximum capacity of 16 Mbps:

slot 1 and slot 2 supports speeds 016 Mbps with 2
Mbps step; slot 3 and slot 4 supports speeds 08 Mbps
with 2 Mbps step.
CFM-M-MUX with the maximum capacity of 34 Mbps:

slot 2 supports speeds 016 Mbps with 2 Mbps step;
slot 3 and slot 4 supports speeds 08 Mbps with 2 Mbps
step; slot 1 supports speeds 08 Mbps with 2 Mbps step
and RMN (remaining capacity) and FOD modes. In RMN
mode the slot operates with any capacity equal to (34
C2,3,4) Mbps, where C2,3,4 the sum of capacities of slots
2, 3 and 4. The slot 1 is the only slot which supports
capacity above 16 Mbps, including the maximum
capacity of 34 Mbps. The FOD mode should be used for
compatibility with the CFM Full Outdoor Unit, operating
with WAN capacity of 34 Mbps. In case if the opposite
site has the CFM series FODU installed, and link
operates with 34 Mbps capacity, the CFM-M-MUX must
have one of the following configurations:
In case if FODU and CFM-M-MUX operates with
34 Mbps capacity
Slot 1
Slot 2
Slot 3
Slot 4
FOD
1E1
1E1
0M
FOD
0M
0M
0M
FOD
1E1
0M
0M
FOD
0M
1E1
0M
The numbering of slots is shown in Figure 2.
- Select local IP - Sets the IP address of the serial port
of the local IDU management controller (local SLIP port
IP address).
- Select remote IP - Sets the IP address of the serial
port of the remote IDU management controller (far-end
SLIP port IP address).
- Ping remote pings the far-end IDU SLIP port, and
displays packet travel time in milliseconds.
- IP - specify IP address of the Ethernet management
port of the IDU management controller; default value
192.168.205.010 or 192.168.206.010;
- Netmask specify netmask for Ethernet management
port; default value - 255.255.255.000
- Gateway specify gateway for the IDU Ethernet
management controller; default value 255.255.255.255 (no gateway specified)
IP, Netmask, and Gateway parameters provide the means
of addressing management board of IDU in order to control
and manage the CFM site locally and remotely via service
channel.
Note: It is necessary to restart the management CPU for
any changes in IP settings to take effect.
17
Setup mode menu tree

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

There are four LEDs on V.35 module. LEDs have a multifunctional meaning, basic
meanings are:
C (DCD) - data carrier detected
D (Data, both TxD and RxD)
S (Send, both RTS - Request to Send, CTS - Clear to Send)
R (Ready, both DSR - Data Set Ready, DTR - Data Terminal Ready)
General color meaning:

Green normal operation; Yellow information for service modes;
Red fault indication; Not lit no signal; Flickering additional information.
Table 10. Reading the V.35 interface module LEDs
LED
C (DCD)
D (RxD, TxD)
S (RTS, CTS)
R (DSR, DTR)
Description
Green carrier is detected;
Red carrier is NOT detected, (problem with radio)
The following will be available through management facilities:
Flickering yellow and green(7:1) loopback is set and
carrier is detected;
Flickering yellow and red(7:1) loopback is set and carrier
is NOT detected;
Flickering yellow (7:1) loopback is set and cable is
damaged;
Flickering green (7:1) cable is damaged and loopback is
NOT set;
Green both received and transmitted data signals are OK,
Off none is present,
Green is blinking and goes off just one data signal is
present (TxD:RxD = 7:1),
Yellow remote loopback is set;
Green both signals are active,
Off both signals are inactive,
Flickering green one control signal is present, another is
absent (RTS:CTS = 7:1),
Blinks yellow and red module has set the CTS signal but
the returned signal is dissimilar to that set by the module, indicates cable fault;
Green both signals are active,
Off both signals are inactive,
Flickering green one control signal is present, another is
absent (DSR:DTR = 7:1),
Blinks yellow and red module has set the DSR signal but
the returned signal is dissimilar to that set by the module, indicates cable fault.
19
E1 Interface Module LEDs

Label
Color
Tx
Green
Description
Steady green light indicates the E1 module is ready to
transmit data to the user equipment (DTE Data Terminal
Equipment) connected to E1 port.
Normally Tx LED is switched on all the time.
In case if Multiplexer synchronization is lost (S.L. LED is lit),
Tx LED goes off and AIS signal is transmitted from E1 port
to CPE.
Rx
Green
Steady green light indicates that E1 port receives data from

DTE.
AIS
Red
Steady red light indicates that E1 port receives AIS (Alarm

Indication Signal) from DTE.
LB
Red
LoopBack LED (red) indicates loopback mode is activated

in the module.
REB Interface Module LEDs

There are two groups of LEDs on the front of the module:
LAN: Rx, Tx
WAN: Rx, Tx
Green LED color indicates activity.

Red LAN Tx LED color indicates the absence of the LAN link signal on the
Ethernet.
Red color of the LAN Rx LED indicates LAN collision in case if Ethernet port of the
REB module operates in Half Duplex mode.
3.2 Resetting the IDU

Depending on the method used, the user may reset
the whole terminal (IDU+ODU) which will disturb the traffic, or
the management controller individually, this will disturb the traffic for about a
second, see table below for details.
Type of IDU reset
Result
Reset through the LCD menu

system using Restart CPU option
or from the Telnet/ASCII console
using restartcpu command
Restarts the management module. Resets

all management counters.
Reset using hidden button at the

rear side of the IDU (see Figure 4)
Restarts both the multiplexer module and

the management module. Resets all
Note: This may require a pin, at least 15
mm long, approx. 1.5 mm in diameter.
Unplugging power supply
Restarts the multiplexer module and the

management module. Resets all
20
3.3 RS-232 Serial Management Port

RS-232 serial management port provides terminal management via connected PC
or other terminal device, using command interface. The terminal connected to
the serial management port (ASCII console) provides the same management
functionality as Telnet terminal, for complete description of command interface
please refer to chapter 3.5.
IDU
RS-232
PC/Terminal
IDU
RS-232
Modem
Modem
PC/Terminal
In order to interconnect the IDU and the management terminal directly through
serial ports, a straight through modem cable is needed. The serial port of the
management terminal should be configured with the following settings:
Bits per second: 19200
Data bits: 8
Parity: none
Stop bits: 1
Flow control: none.
The ASCII console can be connected to the IDU remotely through a telephone
line, using modems. In this case the modem, which is connected with the IDU,
should be configured as stated below:
-
Auto answer on first ring ON
Echo offline commands OFF
Suppress result codes
DTR override
The modem configuration then should be saved (typically with AT&W string).
ASCII console window
21
In order to connect the PC to the RS232 management port using Hyper Terminal
program (this program is included in any Windows version), proceed as described
below.
1. Connect PC to the RS232 serial port by means of straight through serial
cable (modem cable).
2. Run Hyper Terminal program.
3. Make a New connection, enter connection name.
4. Choose port (COM1 or COM2).
22
5. Set port settings (bits per second: 19200, data bits: 8, parity: none, stop
bits: 1, no data flow control).
6. Press OK
7. Press Enter. Password is disabled by default.
If successfully connected, the prompt should appear as in the picture below; see
Chapter 3.5 for available commands.
23
3.4 Ethernet Port

The 10\100Base-T Ethernet management port provides:
Web management via integrated Web server;
Telnet server, accessible using command interface;
SNMP management via integrated SNMP agent.
The IDU can be connected
directly to PC/Laptop,
to LAN via router or other TCP/IP packet network termination unit to have
IDU as part of network for transmission of management information.
3.4.1
Web Management
The CFM-M-MUX management system is running a Web server; the user can
connect to Web server via Ethernet management port. Using Web interface it is
possible to remotely configure and monitor the CFM site (counters, radio
parameters, configuration etc.) from Web page via HTTP.
The IDU management system supports up to 2 Web clients.
Web interface is accessible by any standards based Web browser.
Before connecting to Web server, it is necessary to specify User Name and
Password, using wwwuser <username> <password> command, from Telnet or
ASCII terminal. If User Name and Password is not specified, the user will not be
able to open configuration pages (configure settings).
Main Web management window: entries, which are highlighted in red, indicate
that specific parameters do not comply with the norms of normal operation, all
other parameters are satisfactory
24
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)
25
By default, the Main Configuration window does not allow to configure ODU
parameters (frequency channel and output power); the radio parameter
configuration from Web page is factory-set as disabled. It can be enabled with
enable rfweb yes command from Telnet or ASCII console.
The CFM IDU Main Configuration window extended with the ODU parameter
configuration
To configure each interface module (speed, loopbacks, etc.), open the Modules
Configuration window via Modules Configuration link.
Modules Configuration window

26
3.4.2
Telnet management
The user can connect to Telnet server via Ethernet management port (1 client is
supported).
In order to connect to IDU via Telnet, the user will be prompted for login name
and password. The default (factory preset) Telnet login-name\password is not
specified; in order to connect to IDU via Telnet, the user must specify Telnet
login-name and password using Telnetuser <username> <password>
command; information about command interface is given in chapter 3.5.
3.4.3
SNMP Management
The SNMP management allows to:

Read and configure parameters of IDU and ODU via SNMP;
Receive SNMP traps from IDU.
In order to use the SNMP management facilities, it is necessary to configure:
the IP address of the management PC with the installed SNMP Trap Manager
program; the IP address can be specified from a Telnet or ASCII console
using SNMP trap <IPaddress> command, or 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 SAF MIB to browsers MIB base.
SAF MIB is available from:
-
SAF Tehnika Web site, www.saftehnika.com,
From SAF Tehnika tech support, email: techsupport@saftehnika.com,
Contacting SAF Tehnika or distributors.
***** SNMP QUERY STARTED *****

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

27
The following table describes all variables defined in the MIB.

Variable Name
Variable Type
termProduct
termDescription
termLocation
termVersion
String
String
String
String
termOperation
Integer (32 bit)
termIduTemperature
Integer (32 bit)
termRfCablePowerStatus
Integer (32 bit)
termUpTime
termDownTime
bbVersion
Integer (32 bit)

Integer (32 bit)
String
bbOperation
Integer (32 bit)
bbLinkCapacity
bbLinkCapacityDescriptio
n
bbLoopback
Integer (32 bit)

String
Integer (32 bit)
bbSyncLostAlarm
Integer (32 bit)
rfOperation
Integer (32 bit)
rfAlarm
Integer (32 bit)
rfVersion
rfSide
String
Integer (32 bit)
rfChannel
rfTxFrequency
rfRxFrequency
rfTxPower
rfRxState
Integer (32 bit)

String
String
Integer (32 bit)
Integer (32 bit)
rfRxLevel
rfCableAttenuation
Integer (32 bit)

Integer (32 bit)
rfTxOut
Integer (32 bit)
Value List
none(0)
booting(1)
ok(2)
testing(3)
error(4)
off(0)
ok(1)
short(2)
error(3)
none(0)
booting(1)
ok(2)
testing(3)
loopback(4)
illegalSpeed(5)
error(6)
off(0)
digital(1)
analog(2)
none(0)
on(1)
none(0)
booting(1)
ok(2)
testing(3)
error(4)
noDataFromODU(5)
none(0)
on(1)
low(0)
high(1)
low(0)
ok(1)
error(2)
loopback(3)
error(0)
ok(1)
off(2)
Description
Textual name of terminal type
Textual description of terminal
IDU name
Textual version of management
software
Terminal (IDU) operational
status:
none not initialized;
testing, illegalSpeed, error
reserved
Temperature within IDU
(range: -128..127)
Indicates power consumption of
the ODU: ok - acceptable level,
short - short circuit in cable,
off - too low power consumption,
error internal fault
System up-time in seconds
System down-time in seconds
Textual version of the Base-band
controller software
Operational status of the Baseband modem:
none not initialized
loopback Base-band loop is set
on
testing, illegalSpeed, error
reserved
Base-band link capacity in Kbps
Comment on Base-band link
Base-band loopback
The Sync Lost Alarm

none Off
Operational status of the Radio:
none not initialized
testing, error reserved
noDataFromODU no data is
being received from ODU
Radio Alarm, none off
Textual version of the Radio
Band side of the Radio: low or
high
Channel number
Tx frequency
Rx frequency
Transmitter power
Reception status:
low Rx signal level
ok - normal
error - internal fault in the Radio
loopback RF loop is set on
Received signal level [dBm]
Signal attenuation in ODU-IDU
cable (0-20 db - proper
operation)
Operation status of the ODU
transmitter:
ok proper operation
error internal fault (no data
from ODU)
off Tx power = off
28
rfTxPLL
Integer (32 bit)
error(0)
ok(1)
rfRxPLL
Integer (32 bit)
error(0)
ok(1)
rfOduTemperature
rfOduHumidity
Integer (32 bit)

Integer (32 bit)
rfLoopback
Integer (32 bit)
rfRxAlarmLevel
Integer (32 bit)
m1Type
low(0)
high(1)
off(0)
on(1)
error(0)
e1(33)
v35(37)
bridge(43)
none(255)
m1Description
m1Version
m1Speed
m1Operation
String
String
Integer (32 bit)
Integer (32 bit)
m1Rx
Integer (32 bit)
m1Tx
Integer (32 bit)
m1Loopback
Integer (32 bit)
none(0)
ok(2)
loopback(4)
illegalSpeed(5)
none(0)
ok(1)
noSignal(2)
noLink(3)
rxAIS(4)
none(0)
ok(1)
noSignal(2)
txAIS(4)
Operation status of ODU Tx

syntheser loop (PLL lock):
ok normal operation
error - internal fault in ODU
transmitter
Operation status of ODU Rx
syntheser loop (PLL lock):
ok normal operation
error - internal fault in ODU
transmitter
Internal temperature of ODU (0 C)
Humidity level inside ODU:
low - acceptable moisture level
RF loopback
Rx level (in dBm) at which the Radio
Alarm is switched on
Module type:
error internal fault
none no module installed or the
module does not support data
exchange with the management
controller (e.g., due to the software)
Description of the module
Textual version of the module
Module data transfer speed in kbps
Operational status of the module:
none no data from the module
loopback loopback is switched on
illegalSpeed the speed
configuration of the MUX slot does
not mach the module speed
Rx statuss of the module:
none not defined
noLink for the REB module only
rxAIS for the E1 module only
Tx statuss of the module:
none not defined
noSignal for V.35 module and REB
module (same as no link or LOS
alarm)
txAIS for E1 module only (usually
switches on with the SL alarm)
Loopback in the module
off(0)
on(1)
analog(2)
Rx input of the module:
m1RxInput
Integer (32 bit)
other(0)
other not initialised
coax(1)
rj45(2)
v35(3)
m1TxMode
Integer (32 bit)
other(0)
Tx mode of the module (for the REB
halfDuplex(1)
module only):
fullDuplex(2)
Tx clock source of the module (for
m1TxClockSource
Integer (32 bit)
other(0)
the V.35 module only):
master(1)
slave(2)
m1TxClockPhase
Integer (32 bit)
other(0)
Tx clock phase of the module (for
normal(1)
the V.35 module only):
inverse(2)
Polarity of the data signal (for the
m1DataPolarity
Integer (32 bit)
other(0)
V.35 module only)
normal(1)
inverse(2)
Note: there are more variables with the m2, m3 and m4 prefix in their names, they are analogical
to those with the m1 prefix; the m1 denotes to the module in the slot 1, m2 module in the slot
2, etc.
29
3.5 Command Interface

The CFM equipment (IDU and ODU) can be monitored and configured using
command interface described in this chapter, connecting with
-
ASCII console to RS232 port, or
Telnet terminal via Ethernet management port; the Telnet management

supports only one client.
The command line management interface offers the widest configuration and
monitoring functionality. The following tables in this chapter summarize all
available commands for Telnet and ASCII management.
Tips:
To end Telnet or ASCII session press Ctrl+D, then, to open session again, the
prompt will appear to enter username and password.
For default (factory) usernames and passwords please refer to chapter 3.5.4.
30
Common commands
Command
Time
Time <YYYY-MM-DD HH:mm:ss>
Name <deviceName>
Lcd <1255>
Write
Ping <IPaddress>
BBloop {on | analog | off}

[duration]
RFloop {on | off} [duration]
Webrefresh <refreshperiod>
RxAlarmLevel <alarmLevel>
ResetWDT
ClearCounters
Disable {telnet | www | snmp |

rip}
Description
Show current date and time.
Set the date and time. The clock is not available on
the IDU LCD.
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
Adjust LCD contrast (values 0255), default value is
165.
Save all settings in the EPROM. This command saves
all current settings in EPROM, including those in the
script.
This command is for troubleshooting purposes to
verify the service channel connectivity, - sends a
special packet to the remote IDU and then waits for
a reply.
Set baseband loopback, on set digital loopback
(dual), analog set analog loopback (non-dual),
off suspend baseband loopback. Duration can be
from 1 to 10 minutes, it is equal to 1 min. by
default. Example: BBloop on 3
Set RF loopback, - on set loopback, off
suspend loopback. Duration can be from 1 to 10
minutes, it is equal to 1 min. by default. Example:
Rfloop on 3
Refreshes the contents of WEB interface with a
period specified with refreshperiod parameter. The
period is given in seconds; the minimum period is 2
seconds.
Example: webrefresh 5 the web page will be
updated after every 5 seconds.
Set the Rx signal level at which the Radio Alarm is
switched on. For default value see Chapter 3.11.
Example: rxalarmlevel 55
The management module has a watchdog timer
(WDT), which manages the automatic restart of the
management system if it freezes for about 2
seconds. Resetwdt command will reset watchdog
timer causing the management system to restart,
this will also reset all management counters.
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.
telnet Disable Telnet interface
www Disable Web interface
snmp Disable SNMP interface
rip Disable RIP;
Notes:
after the command is entered, it is necessary to
save the configuration in EPROM (use write
command) and restart the IDU for changes to
take effect.
31
Configuring ODU parameters

Command
Chan <channel#>
Txpower {-10|-9||0|+1|+2||+20 |off}

Txfreq <frequency-kHz>
Description
Set the ODU Tx\Rx channel. Channel
numbers and corresponding Tx\Rx
frequency values are found in tables in the
document Channel plans.
Set the ODU Transmitter power [dBm].
The default setting is OFF.
Set the ODU Tx\Rx channel by specifying
Tx frequency as integer in [kHz] units.
Example: txfreq 14711000
Configuring security parameters

Command
Enable password <password>
Panel access <accesscode>
WWWuser <username>
<password>
FTPuser
Telnetuser <username>
<password>
Enable rfweb {yes | AnyString}
Description
Specify a password to prevent unauthorized access
from ASCII console (PC connected to IDU via serial
port).
Specify a password to prevent unauthorized
configuration from IDU front panel (LCD\keypad).
The password can be a number from 0 200.
Specify username and password (1 - 20 symbols) to
prevent unauthorized access from Web terminal.
prevent unauthorized connection to FTP server.
prevent unauthorized access from Telnet terminal.
Enables configuration of ODU parameters
(frequency, Tx power) from the Web terminal. In
order to enable it, use yes with small caps; to
disable use any string instead of yes argument
except the empty string ( ).
By default, the ODU configuration from Web is
disabled.
Configuring IDU parameters

Command
RestartCPU
Muxspeeds
{slt1}+{slt2}+{slt3}+
{slt4}
Muxcapacity
{8M|16M|34M}
Mod {1|2|3|4} stat
Description
Restart CPU of the management controller for the new IP
settings to take effect. Resets all management counters.
Set the data rate for each multiplexer slot. See Table 9 for
more information about speeds supported by each slot.
Example: muxspeeds rmn+2E1+2E1+2M configures the
multiplexer slots.
Change the multiplexer maximum WAN capacity. 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.
Show parameters, - lists all parameters and input/output
status that refer to the specific module.
Example for E1 interface module:
SAF>mod 1 stat
Module E1 vers. 2
E1 impedance 120
TxAIS OFF
Enable Analog Loopback OFF
Enable Local Loopback OFF
Enable Remote Loopback OFF
RxAIS OFF
RxLOS OFF
Example for REB interface module:
SAF>mod 4 stat
Module Bridge vers. 1
Link ON
FDX ON
Filter ON
32
Mod detect
Detects and displays a list of currently installed modules. This

detection procedure is carried out each time when management
controller boots up.
Mod dump
Show a list of modules and contents of their respective CPU

registers (in hexadecimal system). This command is for diagnostic
purposes only.
IP addr <IPaddress>
Set the IP address of Ethernet management port

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

IP gw <IPaddress>
Set the IP address of the default gateway to the

service channel (requires to restart the management
module CPU).
IP seraddr <IPaddress>
Set the IP address of the serial port of service channel

for the local (near-end) IDU management module
IP remaddr <IPaddress>
Set the IP address of the serial port of service channel

for the remote (far-end) IDU management module
Route add <destinationIPaddr>

Mask [netmask] <gateway>
[metric]
Add a static route to the routing table. The variable

metric is set to 1 by default. Example:
Route add 192.168.205.010 Mask 255.255.255.0
155.13.79.13 5
Route delete
<destinationIPaddr> [netmask]
Delete a static route from the routing table.
SNMP community read

<communityname>
Specify the SNMP community name of the agent to

enable parameters to be read (not configured). The
default read community name is not specified.
SNMP community write

<communityname>
Specify the community name of the agent to enable

parameters to be written (configured). The default
write community name is not specified.
SNMP trap <IPaddress>
Set the IP address of the management terminal with

the installed Trap Manager software, based on SNMP
platform (requires to restart the management module
CPU).
Start ftp
Runs the FTP server on the IDU. By default it is

switched off. In order to use FTP server, it is required
to:
1) Start FTP server using start ftp command;
2) Specify username and password using ftpuser
command.
start tftp
Runs the TFTP server on the IDU, by default it is

switched off.
Configuring E1 Interface Module parameters

Command
Description
Mod {1|2|3|4} setE1 {Aloop |

Dloop | Remote | Off}
Set the analog, digital or remote loopback in the

module (Aloop analog loopback; Dloop digital
loopback, Remote remote loopback, off disable
current E1 module loopback).
Example: Mod 3 setE1 Dloop
Mod {1|2|3|4} setE1 {120 | 75}
Set the impedance of E1 interface, 120 or 75 .

(for 1xE1 modules)
33
Configuring 4xE1 Interface Module parameters

Command
Description
Mod {1|2|3|4} setE1 {port1 | port2 |

port3 | port4} {Aloop | Dloop |
Remote | Off}
Set the analog, digital or remote loopback in

the module (Aloop analog loopback; Dloop
digital loopback, Remote remote loopback, off
disable current E1 module loopback).
Example: Mod 3 setE1 Dloop
Mod {1|2|3|4} setE1 {port1 | port2 |

port3 | port4} {on | off}
Enable/Disable the transmission of AIS signal

(for testing purposes).
Configuring V.35 Interface Module parameters

Command
Mod {1|2|3|4} setV35 speed {64 | 128 | 256
| 512 | 1024 | 2048 | 4096 | 6144 | 8192}
Mod {1|2|3|4} setV35 phase {normal |
inverse}
Mod {1|2|3|4} setV35 polarity {normal |
inverse}
Mod {1|2|3|4} setV35 loop {on | off}

Mod {1|2|3|4} setV35 {Master | Slave}
Description
Set the speed of V.35 interface (in
kbps).
Invert the RxC clock signal (it is
transmitted from V.35 module to user
equipment)
Invert the incoming and outgoing data
signals (RxD outgoing, TxD
incoming) between DCE (module) and
DTE (user equipment).
Set the loopback mode of V.35 interface
module.
Set the sync status of V.35 interface
module, ie. master or slave.
Example: Mod 2 setV35 slave
Configuring 2-port 100Base-T Ethernet Bridge Module

Command
Description
Mod {1|2|3|4} setf2bridge {port1 |

port2} connection {auto | 10hdx |
10fdx | 100hdx | 100fdx}
Configure port speed and duplex, 10hdx 10

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

port2} priority {low | high}
Configure port priority. The factory setting for both

ports is low.

port2} flowcntrl {enable | disable}
Enable or disable flow control for the specified

port.
Mod {1|2|3|4} statistics
Displays statistical information:
Received packets and bytes, transmitted

packets and bytes, errors for port 1, port 2
and WAN port;
Collisions for port 1 and port 2.
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.
Display MAC address of the Ethernet management port.
Display hardware and software version of the IDU and ODU, and IDU
serial number.
Mac
Ver
ODU
sernum
ustat
Display ODU software version.

Display IDU serial number.
Display inputs and outputs of the alarm port.
34
Commands for script editing

Command
Cfg show
Cfg load
Cfg clear
Cfg delete <stringNumber>
Cfg write
Description
Show the configuration script stored in RAM.
Load the configuration script from EPROM into RAM.
Clear the script stored in RAM.
Clear a single string in the configuration script. This
command is useful for script editing.
Save current script in EPROM. This command saves in
EPROM the current script as well as settings that are
specified in it.
cfg backup <filename>
Save current configuration script in text file on the Flash

disk, with the specified filename.
cfg restore <filename>
Load the configuration script (specified text file) in RAM,

but does not execute the script. Further,
Cfg factory yes
to apply the script (execute commands), use cfg run

command.
to store the script in EEPROM, use write command.
Reset the configuration by loading in EEPROM the script

with default settings. This command performs the
following actions (in the following order):
1.
2.
log { show | <start_num> }
clears the current script from EEPROM,

creates and stores in EEPROM the new script with the
following settings:
IP addr 192.168.205.010 or 192.168.206.010
IP mask 255.255.255.000
IP gw 255.255.255.255 (default gateway none)
IP seraddr 192.168.0.10 (SLIP configuration, IP address of the local serial port)
IP remaddr 192.168.0.11 (SLIP configuration, IP address of the remote serial port)
Enable rfweb yes (enable configuration from Web
terminal)
SNMP trap 255.255.255.255 (none)
RxAlarmLevel <#> (# - default value, default
value depends on IDU, see Chapter 3.11)
TxAlarm level
muxspeeds 0M+0M+0M+0M
3. restarts the management controller
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 100120.
Commands for operations with files and file system

Please refer to chapter Working with files, page 38.
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 (| ).

35
3.5.1
Working with configuration script
The management module has RAM and EEPROM chips onboard. When IDU is
booted up, bootstrap is loaded from the EPROM into RAM. The bootstrap contains
the parameters that were previously stored in EPROM using write and/or cfg
write commands. These parameters are stored in EPROM in the form of script
and when booting up, the script parameters are loaded into RAM. These
parameters can be freely changed in run-time, - changing the data in RAM. If the
IDU is shut down without saving the current configuration (script) in EPROM, the
original configuration will be restored from EPROM on the next boot-up.
Here is an example of script:
SAF>cfg show
01: ip remaddr 192.168.0.11
02: ip seraddr 192.168.0.10
03: Chan 144
04: muxspeeds rmn+8M+8M+4E1
05: snmp community read safpub
06: snmp trap 255.255.255.255
07: route add 62.85.14.0 MASK 255.255.255.0 192.168.12.22
The script can be edited:
-
string can be added by simply entering the required command (the script will
be supplemented with the new string or the instant string entry will be
updated)
string can be deleted using cfg delete <string#> command line.
the changes can be saved in EPROM using cfg write command line. Note: the
parameters, that are not specified in the configuration script will have their
default values when the IDU is restarted.
36
3.5.2
File system
The software used by the IDU management controller is organised in files, which
are stored in Flash disk.
Firmware and boot configuration files
The following files are needed for the IDU to start:
-
Boot.ini file, - device boot configuration file. This file is text file and contains
the name of the firmware file which must be executed at startup. The file
name can be freely changed, but its default name is boot.ini, hereinafter it is
assumed, that this file has default filename. The most important factor about
this file is that it must be uploaded with B and e attribute flags (flags are
case sensitive!), only then it will be treated as executive script.
Attribute flags for boot.ini file:
B query run at boot; e executive script
For information how to upload files in the Flash disk, please refer to chapter
3.6.
Firmware file, - this file is the main firmware executable for the appropriate
IDU model. The file name can be freely changed, but its default name will
contain the version and IDU model, e.g., MMUX400.elf.lzip. The most
important factor about this file is that it must be uploaded with E and c
attribute flags, otherwise this file will not be used as the firmware.
Attribute flags for firmware file:
E executable binary; c - compressed
Notes:
-
The files are uploaded from PC to Flash disk using TFTP (via Ethernet
management port), or using Xmodem protocol (via RS232 serial port), for
more information about file upload please refer to chapter 3.6; configuration
backup files are created by IDU management system.
The flash disk may store other files as well, for example previous firmware
versions, configuration backup files, - up to 3.5 Mb (3 or 4 firmware files).
The attribute flags for files are case sensitive.
The file names can be changed, but it is very important that the file has the
necessary attribute flags otherwise the file will not be used neither as
firmware, nor as boot.ini type file.
There are no file extensions in the file system; either file, when edited, is
treated as ASCII text file.
When uploading the file, if the Flash disk stores the file with the same
filename as for uploadable file, it will be overwritten with the new file.
Configuration backup files

Using cfg backup <filename> command, the user can create the backup file of
the current CFM site configuration. The configuration backup file is text file and,
when created, contains the current configuration script, - the same configuration
script that are stored in EEPROM. Please refer to chapter 3.5.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.
37
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.
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.
38
3.5.3
Storage of radio parameters
The radio parameter values (transmit frequency and power) are stored internally
in Flash memory of the Radio unit, the Radio operates exactly with those values
stored in its Flash memory. When the radio parameter is modified while the
equipment is in operation, the corresponding radio parameter value in the Radio
Flash memory is overwritten with the new one and applied in operation. Since the
radio parameters are stored in ODU in Flash memory, it is not necessary for the
IDU configuration script (bootstrap) to contain strings that configure radio
parameters. In case if the configuration script stored in IDU EEPROM contains
strings that configure radio parameter(s), each time the equipment is booted, the
radio parameter values written in the IDU bootstrap are uploaded to the Radio
and the previously stored radio parameter values in Flash memory are
overwritten with those in the IDU bootstrap. Hence the radio parameter
configuration in the IDU bootstrap has a higher priority as they will override the
values stored in the Radio Flash memory when the equipment is rebooted.
It is useful to write the radio parameter configuration in the IDU configuration
script for the purpose to be able to quickly replace the ODU later.
39
3.5.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 reentering the appropriate security command while logged on, and then saving the
configuration in EEPROM using write command.
To terminate Telnet session, or log off from ASCII terminal, press Ctrl+D.
To disable username and/or password, enter the password configuration
command with empty string in argument:
for ASCII console: enable password
for Telnet terminal: telnetuser
for Web access: wwwuser
In case if user has forgotten username and password for Telnet access and
password for access from ASCII console, it is possible to restart the IDU without
applying settings stored in EEPROM, and then find out the Username and
Password using cfg show command. Proceed as follows:
connect to IDU with ASCII console (via serial port);

Enter restartcpu command and follow the strings displayed on ASCII console
window; as soon as Press <Esc> twice to stop initialisation string appears
(see Figure 10), press Esc key twice.
Figure 10
Enter cfg show command to display boot configuration script, which will also
include security commands with Usernames and Passwords.
By default there are no password specified for access from ASCII console, - when
user connects to IDU from ASCII console, no prompt is displayed to enter
password.
40
Important!
The specification of username and password (or access code) should always be
followed by saving the configuration script (using write or cfg write
commands) otherwise the password request will be ignored after the restart of
IDU.
Panel access code
The panel access code for the access from IDU panel can be specified from the
Telnet and ASCII terminals only. When the access code is specified, the
adjustment and configuration of any IDU/ODU parameters and loopbacks from
IDU LCD is not available, unless the correct access code is specified at IDU using
keypad (refer to chapter Setup Mode of IDU LCD Management Interface). The
specification of access code should also be followed by saving the configuration
script otherwise the access code value will be set to default (none) on the IDU
restart. The panel access code can be changed simply entering the new access
code (number from 0 200) using panel access command.
To disable the panel access code feature, enter 0 value, which means that this
feature is disabled (default setting).
41
3.6 Uploading software

The user can upgrade the IDU management software by uploading the
appropriate firmware file to IDU Flash disk, and then edit boot configuration file if
necessary. The file upload can be performed
-
via Ethernet management port using TFTP, or
via RS232 serial port using Xmodem protocol.
3.6.1
Uploading file via Ethernet management port (TFTP)
Assuming that the IDU IP settings are properly configured, proceed as follows:
1) Connect the IDU to network or directly to PC,
2) Make sure TFTP is running on IDU (by default, the TFTP is switched off); to
run the TFTP on IDU, connect to IDU with Telnet client and enter the following
command: start tftp.
3) Run the program that enables to use TFTP service, for example command
interpreter (cmd.exe) if using Windows, see Figure 11.
4) For example, to upload the firmware file mmux400.elf.ezip with attribute
flags E and c, enter command:
tftp i 192.168.205.11 put C:\files\mmux400.elf.ezip,Ec
where:
-i key which specifies that file must be transferred in binary image transfer
mode;
192.168.205.11 IDU Ethernet management port IP address (host);
C:\files\mmux400.elf.ezip firmware file (source);
Ec file attribute flags E and c; the attribute flags are separated from file
name or source with comma (only comma and no space) and there are no
commas or spaces between flags;
Figure 11
5) If uploaded file is large (like firmware file), it is recommended to defragment
Flash disk. Use tfs clean command from Telnet or ASCII terminal to perform
defragmentation.
6) If the uploaded file is firmware file which should be used by IDU, it is
necessary to edit boot.ini file by deleting the entry with old file name and
writing file name of the new firmware file; the boot.ini file must be saved
with B and e flags (file attributes), for more information how to edit files,
please refer to chapter Working with files, page 38.
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.
42
3.6.2
Uploading file via serial port (Xmodem)
File upload via serial port takes much longer time compared to using TFTP and
should be used only in case if Ethernet connection with IDU management system
is not available, or does not start normally.
1) Connect the ASCII console to IDU RS232 port, make connection with the
following properties: Bits per second: 19200; Data bits: 8; Parity: none;
Stop bits: 1; Flow control: none; if using Hyper Terminal program, please
refer to chapter 3.3 for information how to make a connection.
2) Type restartcpu and, while IDU is booting, press any key when boot.ini?
prompt appears. This will stop executing script in boot.ini file and the IDU
will remain in MicroMonitor mode, this is system startup mode which loads
the management system firmware;
Note: while in MicroMonitor mode, the uMON> prompt will be displayed,
instead of normal prompt with IDU name (default SAF>).
3) In MicroMonitor mode enter the following command:
xmodem cd F <filename-no_flags> -f Ec
where
<filename-no_flags> - file name with no flags specified
Ec file flags, in case the file is firmware file - E and c flags must be
used; if the file is boot configuration file (boot.ini), the flags must be Be
(B and e); the flags for configuration backup files may not be specified,
in that case the command will be
xmodem cd F < filename-no_flags >
4) Use terminal emulation software with file upload function, such as Hyper
Terminal (in Windows) to upload the firmware file to IDU as binary image
(use binary transfer mode), using Xmodem protocol.
If using Hyper Terminal, proceed as follows: from menu select
TransferSend File, then select file and in protocol box select
Xmodem protocol and press Send button, the following box should
appear
When upload is complete, the following information will be displayed

(Figure 12):
43
Figure 12
5) Enter reset command to exit from MicroMonitor mode and restart the
IDU.
6) Proceed with steps 5) and 6) in chapter 3.6.1.
44
3.7 Alarms
The following types of alarms
Radio alarm (RA): when active, indicates problems with ODU or IDU-ODU
cable, for more information see Table 2. The state of RA can be verified from
RA LED on the IDU front panel,
Web page,
Telnet or ASCII console.
Sync Lost alarm (SL): when active, indicates failure of Multiplexer frame
synchronization, when switched off the frame synchronisation is
established. The state of SL can be verified from
SL LED on the IDU front panel,
Web page,
Remote Alarm Indicator (RAI): this alarm signal is received from the far-end
site (WAN side), indicating that the far-end site has the SL alarm switched on.
The state of RAI can be verified from
3.7.1
RAI LED on the IDU front panel,
Web page,
Alarm Port
The Alarm port is optional feature.

The Alarm port comprises 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:
Each
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).
output is available as normally opened and normally closed (invert).
There are four parallel inputs of the alarm port available: input A, input B, input
C, input D. These inputs are used for connection of an external device which
supplies DC voltage on input, - 0 or 1; the alarm status triggers if input
voltage is changed between 0 and 1; 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.
45
3.8 Configuring Management Service Channel

The service channel capacity varies depending on the configured WAN capacity:
Maximum IDU capacity
Service channel capacity
8 Mbps
16 Mbps
34 Mbps
40 kbps
80 kbps
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 service channel virtual

serial port (also referred as service channel IP 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 of
these ports have their IP address.
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 virtual serial port (service channel 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.
2-port
Router
Serial
Port
Eth
(RJ-45)
Management
Module
Service
channel
Serial
Port
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.
46
The configuration of local and remote virtual service channel IP addresses should
conform the following principle.
Terminal A
Terminal B
Local serial port (SLIP) IP address
IP 1
IP 2
Remote serial port (SLIP) IP address
IP 2
IP 1
Remote virtual serial

port IP address
Local virtual serial port
IP address
Management
Module
(router)
Eth
Virtual
Serial
Port
Required to specify:
Local serial port IP addr.,
Remote serial port IP addr.
Management
Console
Remote virtual serial

port IP address
Local virtual serial port
IP address
service channel
Virtual
Serial
Port
Management
Module
(router)
Eth
Local serial port IP addr.,
Remote serial port IP addr.
IP address/Net Mask,
Default Gateway
Local Site (Terminal A)
Remote Site (Terminal B)
See examples on the next page.
47
Examples of service channel configuration

Management
Module
RIP = ON
Virtual
Serial
Port
Eth
service channel
IP Seraddr 192.168.0.10
IP Remaddr 192.168.0.11
Management
Module
RIP = ON
Eth
IP Seraddr 192.168.0.11
IP Remaddr 192.168.0.10
IP Addr 192.168.205.10
IP mask 255.255.255.0
IP GW 192.168.205.1
Telnet console/
Web client
Virtual
Serial
Port
IP Addr 192.168.206.10
IP mask 255.255.255.0
Console 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
Figure 13
Management
Module
RIP = ON
Eth
Virtual
Serial
Port
IP Seraddr 192.168.0.10
IP Remaddr 192.168.0.11
Router
(RIP=OFF)
IP Addr 192.168.205.10
IP mask 255.255.255.0
IP GW 192.168.205.1
service channel
Virtual
Serial
Port
Management
Module
RIP = ON
Eth
IP Seraddr 192.168.0.11
IP Remaddr 192.168.0.10
IP Addr 192.168.206.10
IP mask 255.255.255.0
IP GW 192.168.0.10
Router port IP address: 192.168.205.1, 255.255.255.0

Route Add 192.168.206.0 Mask 255.255.255.0 192.168.205.10
Ethernet
Telnet console/Web client
Figure 14
48
Port IP address: 192.168.205.1

Route Add 192.168.205.0 Mask 255.255.255.240 192.168.205.2
Ethernet
Router
(RIP = OFF)

IP address: 192.168.204.2
IP Addr 192.168.205.2
IP mask 255.255.255.252
IP GW 192.168.205.1
Management
Module
RIP = ON
Eth
Virtual
Serial
Port
IP Addr 192.168.205.5
IP mask 255.255.255.252
IP GW 192.168.0.1
service channel
Hop 2
IP Addr 192.168.205.9
IP mask 255.255.255.252
IP GW 192.168.0.3
Management
Module
RIP = ON
Eth
Virtual
Serial
Port
service channel
Eth
Hop 3
IP Seraddr 192.168.0.5
IP Remaddr 192.168.0.6
Virtual
Serial
Port
Management
Module
RIP = ON
Eth
IP Addr 192.168.205.10
IP mask 255.255.255.252
IP GW 192.168.205.9
Virtual
Serial
Port
Eth
IP Addr 192.168.205.6
IP mask 255.255.255.252
IP GW 192.168.205.5
Management
Module
RIP = ON
Management
Module
RIP = ON
Hop 1
Virtual
Serial
Port
IP Addr 192.168.205.13
IP mask 255.255.255.252
IP GW 192.168.0.5
service channel
Virtual
Serial
Port
Management
Module
RIP = ON
Eth
Figure 15. The IP configuration of the management channel via three hops with
the RIP II switched on in each IDU; since the management controllers are
running RIP II, there is no necessary to specify gateway (see configuration
strings in grey)
49

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
(RIP = OFF)
IP GW 192.168.0.1
Route add 192.168.205.8 Mask 255.255.255.248 192.168.205.6
Route add 192.168.205.13 Mask 255.255.255.255 192.168.205.6
IP GW 192.168.205.1
Route add 192.168.205.12 Mask 255.255.255.252 192.168.0.2
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 mask 255.255.255.252
IP Addr 192.168.205.2
IP mask 255.255.255.252
Management
Module
RIP = OFF
Eth
Virtual
Serial
Port
service channel
Hop 2
Eth
Hop 1
Management
Module
RIP = OFF
Virtual
Serial
Port
IP GW 192.168.205.5
Route add 192.168.205.8 Mask 255.255.255.248 192.168.0.4
Route add 192.168.205.13 Mask 255.255.255.255 192.168.0.4
IP GW 192.168.0.3
Route add 192.168.205.13 Mask 255.255.255.255 192.168.205.10
IP Addr 192.168.205.6
IP mask 255.255.255.252
IP Addr 192.168.205.9
IP mask 255.255.255.252
Management
Module
RIP = OFF
Eth
Virtual
Serial
Port
service channel
IP GW 192.168.205.9
Route add 192.168.205.13 Mask 255.255.255.255 192.168.0.6
IP GW 192.168.0.5
IP Addr 192.168.205.10
IP mask 255.255.255.252
Eth
Hop 3
Virtual
Serial
Port
Eth
Management
Module
RIP = OFF
Management
Module
RIP = OFF
Virtual
Serial
Port
IP Addr 192.168.205.13
IP mask 255.255.255.252
service channel
Virtual
Serial
Port
Management
Module
RIP = OFF
Eth
Figure 16. The IP configuration of the management channel via three hops with
the RIP II switched off in each IDU; for proper routing between IDU management
modules, the default gateway and static routes must be set for each module
50
3.9 Algorithm of LCD Operation

Perform Restart
CPU from menu
IDU is powered on
Hardware reset
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
menu tree level lower than the top level
NO
YES
Jump 1 level up on the

Setup mode menu tree
YES
Idle for about 10

seconds ?
NO
Flow Chart 1. LCD operation
51
3.10 Replacing the Indoor Unit

Before replacing the IDU, verify the configuration of Radio if possible, - inspect
the channel an transmit power settings. Then configure the new IDU in one of the
following ways:
delete the bootstrap via Telnet or ASCII console using cfg clear
command, or
configure Radio channel and transmit frequency as needed (from LCD or
via management console);
In order to replace the faulty IDU while in operation, take the following steps:
Disconnect the faulty IDU from the Radio:

disconnect the N-type female connector;
unplugging of power is optional;
Connect the new IDU:
if the new IDU is previously configured (the transmit power and
channel settings are made and the configuration is saved), the
Radio will apply these settings after the management controller will
be restarted,
if configuration script (bootstrap) is empty or does not contain
entries on channel and transmit power, the Radio will keep the
configuration that was last received from IDU;
Restart the management controller, for instance, using RestartCPU
option on the LCD.
52
3.11 Default Settings

Parameter/description
Parameter name or command

line
Telnet / ASCII
Tx/Rx channel
LCD
Default
value/setting
In the middle of
the band covered
by Radio
Off
Equal or greater
than -77 dBm
Chan
Chan
Transmitter power
Rx signal level by which
the Radio Alarm is
turned on
Fdx/Hdx port mode and
speed for Ethernet
bridges
Management controller
IP address
Txpower
RxAlarmLevel
Tx Power
RxAlarmLev
Bridge
Bridge
Ethernet
Auto
IP addr
IP
Management controller
IP address netmask
IP address of the
gateway to the service
channel
IP address of the local
virtual serial port of
service channel
IP address of the
remote virtual serial
port of service channel
IDU name
IDU capacity
IP mask
Netmask
192.168.205.10
or
192.168.206.10
255.255.255.0
IP gw
Gateway
255.255.255.255
IP seraddr
Local IP
192.168.0.10
IP remaddr
Remote IP
192.168.0.11
Name
capacity
Capacity
Multiplexer slot speed

settings
muxspeeds
MUX slot
speeds
SNMP read community

name
SNMP write community
name
IP address of the SNMP
trap manager
SNMP
community read
SNMP
community write
SNMP trap
SAF
(customer
specified)
All slots 0 Mbps
(for all IDU
capacities)
Not specified
Not specified
Web page refresh time

Username and password
for ASCII console
Access number for
LCD/Keypad
Webrefresh
Enable password
255.255.255.255
-> trap manager
not specified
5 seconds
(disabled)

for Web management
for Telnet terminal
Configuration of Radio
parameters from the
Web terminal
Panel access
WWWuser
Telnetuser
Enable rfweb
0 (disabled)
Username and
password not
specified
Not specified
(disabled)
53
3.12 Configuring Radio Parameters

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

The Tx frequency of the CFM LM and the CFM L4 type ODUs can be adjusted in
the following ways:
1) It can be set through Set Channel item of IDU LCD menu system.
If this item is chosen, display indicates:
Channel = xxx
Tx = xxxxx.x MHz
where Channel corresponds to Tx channel number and Tx frequency indicates
appropriate frequency in MHz.
Operator sets desired channel number scrolling through values with Up or
Down buttons and confirming the choice with Enter button.
2) The Tx frequency can be set using Chan command from ASCII or Telnet
management terminal, example: Chan 22
22 channel number.
Since the telemetry data is transmitted between the ODU and the IDU, the
concordance of Tx frequency to Low or High band side is detected automatically,
and when the Tx channel is configured from the IDU LCD, the LCD displays
frequencies within the subband (Low or High) that is covered by the Radio.
However, if the ODU covers only a half of the subband (e.g., LA, HA, LB or HB, depends on the duplexer filter within the ODU), the user should only choose from
those Tx frequencies (channels) that are covered by the half of the subband
specific to the Radio.
If a fault occurs in the ODU that prevents the transmission of telemetry data, the
IDU LCD shows No data from ODU.
The Rx frequency is set automatically by Tx frequency.
54
3.12.3 Configuring Tx Power

The Tx Power level of the CFM series ODU can be adjusted in the following ways:
1) It can be set through Set TxPower item of IDU LCD menu system.
2) The Tx Power can be adjusted using Txpower command from Telnet or
ASCII terminal, example: Txpower +10
The Tx Power can be adjusted from -10 dBm to +20 dBm in steps of 1 dBm as
well as turned off (Txpower off).
To avoid possible interference with other radio equipment, the default setting is
OFF.
55
3.13 Performing Loop-back Tests

Loopback tests are accessible using local or remote management methods.
All baseband and RF loopbacks (local and remote) for safety purposes can be set
on a fixed time interval only. The interface lopbacks (E1, V.35) does not have
time limit and must be switched off manually.
3.13.1 Setting Loop Tests from IDU LCD/Keypad

From the IDU LCD all loop tests are set on 1 minute time interval.
Baseband loopback:
From status display mode do the following: Press ENTER to enter setup
mode select Loopbacks select BBloopback ON to set the digital
baseband loops or BBloop analog to set the analog baseband loop
select Yes.
RF loopback:
mode select Loopbacks select RFloopback ON select Yes.
V.35 interface loopback:

mode select Modules select Module # V35 select V.35
Loopback Change Loopback, switch over to ON and confirm.
E1 interface loopback:
mode select Modules select Module # E1 select E1 Aloop for
analog loopback (non-dual) or E1 Dloop for digital loopback Change,
switch over to ON and confirm.
REB interface loopback: not available.
3.13.2 Setting Loop Tests from Telnet/ASCII terminal

From the remote management terminal, the loopbacks can be activated using the
following commands:
V.35 interface module loopback:

Use command Mod # setV35 loop {on|off}, # - MUX slot number
Example: mod 3 setv35 loop on (see also syntax notes on page 35).
E1 interface module loopback:

Mod # setE1 {Aloop|Dloop}, if argument is Aloop - analog loopback is
activated, Dloop activates digital loopback, Remote remote loopback,
off switch off any E1 interface loopback (for details refer to Chapter
3.13.6), # - MUX slot number.
Baseband loopback:
BBloop {on|analog|off} [duration]. Duration is set in minutes as values
from 1 to 10. If duration is not specified the loopback will be set on 1
minute. There are two baseband loop tests available:
Analog: if setting analog loopback, use bbloop analog command,

analog loopback is not dual.
Digital: if setting digital loopback, use bbloop on command, digital

loopback is dual.
RF loopback:
RFloop {on|off} [duration], duration = 1 min by default.
56
3.13.3 Radio loopback

Radio (RF) loopbacks can be set on a fixed time interval only; if using
LCD/Keypad, the RF loop test is set for 1 minute. If setting RF loop from Telnet or
ASCII console, the duration of radio loopback mode can be specified from 1 to 10
minutes.
The radio loop is set in the ODU. Radio loopback mode is a special ODU operation
mode, where the Rx frequency during the loopback mode is set equal to the Tx
frequency. During radio loopback mode, the signal is transmitted and looped back
through the duplexer filter to the receiver block. The radio loopback is not dual.
Important notes:
1. Because of the frequency characteristic of the duplexer filter, in order to
set the radio loop, the ODUs operating in the Low band side must be
switched to the highest available frequency channel, but the ODUs
operating in the High band side must be switched to the lowest available
frequency channel;
2. Before setting the radio loop, the transmitter power should be switched to
maximum level;
3. In CFM-18-LM and CFM-18-L4 ODUs the radio loopback mode is not
available.
3.13.4 Base-band loopbacks

The baseband loop is set in the baseband modem in the IDU. Base-band
loopbacks can be set on a fixed time interval only; if using LCD/Keypad, the
base-band loop test is set for 1 minute. If setting base-band loopback from
Telnet or ASCII console, the duration of baseband loopback mode can be
specified from 1 to 10 minutes.
There are two types of baseband loopbacks (both can not be activated
simultaneously):
Digital baseband loopback: the signal from the ODU and from the multiplexer
(or Bridge board) in the baseband modem is looped back to the receiving
device; the digital baseband loopback is dual (see figure below);
Analog baseband loopback: the modulated signal on the baseband modem

output is looped back to the receiving device and also passed further to the
ODU.
Base-band Modem
Rx
Filter
Comparator
Base-band Modem
Clock recovery/
Data decoding/
Descrambling
Rx
Filter
Comparator
Clock recovery/
Data decoding/
Descrambling
ODU
ODU
Tx
Filter
Data coding/
Scrambling
Analog loop
Tx
Filter
Data coding/
Scrambling
Digital loop (dual)
Figure 17. Baseband loopback modes: signal is looped in the modem
57
3.13.5 V.35 Interface Module Loopback

The loopback mode of V.35 interface module is dual.
2
I C bus
CPU
Multiplexer
Remote
loop
SCTE
TxD
DTR
RTS
IN
Local
loop
V.35
Interface
DSR
RxD
RxC
OUT
Figure 3.18. V.35 Interface Module Loopback
3.13.6 E1 Interface Module Loopbacks

The E1 interface module supports analog, digital and remote loopback modes.
Only one loopback can be active at a time for a single E1 channel, when other is
switched on, the current one is switched off.
The digital loopback mode is dual since there are two loops closed, remote and
local (see figure below).
2
I C bus
Multiplexer
CPU
IN
E1
G.703
HDB3
Analog
Interface
OUT
Remote
loop
Local
loop
Figure 3.19. E1 Interface Module Digital loopback mode

2
I C bus
Multiplexer
CPU
IN
E1
G.703
HDB3
Analog
Interface
OUT
Figure 3.20. E1 Interface Module Analog loopback mode
IN
E1
G.703
HDB3
Analog
Interface
OUT
I C bus
Multiplexer
CPU
Remote
loop
Figure 21. E1 Interface Module Remote loopback mode
58
4 Pinouts
RS-232 management port pinouts
DB9 Female Connector
1
Unassigned
DCE Ready
Transmitted Data
Clear to Send
Received Data
Request to Send
DTE Ready
Unassigned
Signal Ground
Shield
Received from DTE
Transmitted from DCE
Notes:
Standard Ethernet patch cables should be used with management Ethernet

port of the IDU;
Any straight through or modem serial cable could be used with RS-232
management port of the IDU.
V.35 traffic port pinouts

Signal
P GND
S GND
RTS
CTS
DSR
DCD (RLSD)
DTR
TxD+
TxDRxD+
RxDSCTE+
SCTERxC+ (SCR+)
RxC- (SCR-)
TxC+ (SCT+)
TxC- (SCT-)
M34 Pin
60 Pin
Cisco*
A
B
C
D
E
F
H
P
S
R
T
U
W
V
X
Y
AA
46
45
42
35
34
33
43
18
17
28
27
20
19
26
25
24
23
Interconnectable pinouts
at the Cisco equipment
side:
48 & 49
50 & 51 & 52
53 & 54 & 55 & 56
Notes:
* This information is for
users reference only
P GND Protection
Ground
S GND Signal Ground
59
Alarm interface port specification
15
14
16
17
19
18
10
21
20
22
11
23
12
13
25
24
Figure 22. DB25 Male connector pin layout

The pin assignments for relay outputs are the following:
Output A
Output B
Output C
Output D
(Power on\off)
(SL alarm)
(RAI alarm)
(RA alarm)
Pair of pins
1-2
2-14
3-4
4-16
5-6
6-18
7-8
8-20
Type: NC* or
NO**
NO
NC
NO
NC
NO
NC
NO
NC
NC* - Normally Closed

NO** - Normally Open
Input pins:
Input A
Input B
Input C
Input D
Pin
10
11
12
13
GND pins (closest)
22
23
24
25
Electrical specifications of the outputs of the alarm interface port:

Rated load: 0.5 A at 125 VAC; 2 A at 30 VDC
Max. switching current: 2 A
Max. switching voltage: 250 VAC, 220 VDC
Max. switching capacity: 62.5 VA, 60 W
Electrical specifications of the inputs of the alarm interface port:
Impedance: 4,7 k,
U0 = 12 V DC,
U1 = 2,448 V DC.
60
E1 port pinouts
The pinouts of RJ-45 ports for 1xE1 and 4xE1 modules are shown in Figure 23.
E1 port pinouts
RJ-45 pin numbering
INPUT (Rx)
OUTPUT (Tx)
E1 port
1 2 3 4 5 6 7 8
OUT Not
IN
(Rx) GND (Tx) used GND
12345678
Figure 23. E1 traffic port pinouts
E1 unbalanced (75 ) DB25 traffic port pinouts
See Figure 22 for DB-25 male connector pin numbering.
1
INPUT CH4
OUTPUT CH4
INPUT CH3
OUTPUT CH3
INPUT CH2
OUTPUT CH2
10
INPUT CH1
11
OUTPUT CH1
All other pins are GND.
61
5 Mechanical data
IDU weight and dimensions
Weight without
modules [kg]
Dimensions HxWxD [mm]
CFM-M-MUX
2.0
44x482x284
44
IDU model
284
482
Dimensions of the IDU
Weight and dimensions of traffic modules

Module
Weight [g]
Dimensions HxWxD [mm]
10\100Base-T 2-port
Ethernet bridge
55
43x59x125
1xE1
75
43x59x143
4xE1 w\ DB25 port
76
43x59x126
4xE1 w\ RJ-45 ports
77
43x59x125
V.35
86
43x59x139
62
SAF Tehnika A/S Contacts
Most up to date contacts of SAF Tehnika A/S could be found at Web site
www.saftehnika.com.
SAF Tehnika A/S technical support could be reached at:
-
Email:
techsupport@saftehnika.com
Telephone:
+371 7046840
Fax:
+371 7020009
7 References
The following documents comprise the information about CFM-M-MUX IDU. These
documents can be ordered from SAF Tehnika or its sales representative.
SAF CFM LM Series Microwave Radio System Product Family: Technical

Description
- this document is a generic technical description of the CFM-LM ODU and
IDUs that are compatible with it, it comprises the installation and
commissioning issues and respective accessories, functional descriptions,
technical data, a.o.
Channel Plans
- this document contains all available frequency channel plans for bands from
7 GHz to 38 GHz.
63

CFM M MUX - Tech Description

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CFM M MUX - Tech Description

Hochgeladen von

Copyright:

Verfügbare Formate

CFM-M-MUX

SAF Tehnika A/S 2005

CFM Multiplexer Indoor Unit Overview ....................................................................3

Interface Modules ..............................................................................................................8

V.35 Interface Module ............................................................................................................... 8

2.3 Labelling ..............................................................................................................................12

Status Display Mode of the IDU LCD Management Interface ............................... 13

Resetting the IDU ............................................................................................................20

Web Management ..................................................................................................................... 24

Command Interface ........................................................................................................30

Working with configuration script ....................................................................................... 36

Uploading software .........................................................................................................42

Uploading file via Ethernet management port (TFTP) ................................................. 42

Alarm Port .................................................................................................................................... 45

Configuring Management Service Channel ............................................................46

3.12.1 Default ODU Settings............................................................................................................... 54

3.13 Performing Loop-back Tests ........................................................................................56

Setting Loop Tests from IDU LCD/Keypad....................................................................... 56

1 CFM Multiplexer Indoor Unit Overview

Local and remote management (incl. Web, Telnet, SNMP, ASCII),

TCP/IP service channel between sites over the radiolink,

Alarm interface (optional).

For M-MUX SW ver. 4.09 (2005.05.31)

Chapter Labeling revised

2 Indoor Unit Appearance

48.6 cm (19.29 ")

42.6 cm (16.93 ")

Management controller board;

Power Supply module;

LCD and Keypad module;

Traffic interface modules.

Figure 2. Numbering of module slots

The CFM-M-MUX IDU provides:

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

The CFM-M-MUX IDU provide 1 up to 4 slots for installation of traffic port

RS-232 serial management port;

10\100Base-T Ethernet management ports (2-port switch).

Port activity LEDs;

Front panel connectors

Rear panel connectors

N-type Female connector, the cable should be connected

RS232 management port for connection of ASCII console

Ethernet management port

Figure 3. Rear panel

Table 2. Front panel LEDs

Radio Alarm LED indicates problems with radio unit and

Rx signal level is lower the predefined value, - the

If not lit operating properly (Rx=OK & TxOut=OK &

The RA LED is updated one time per second.

User defined alarm LED, - the alarm type is specified by

SYNC, RADIO, REMOTE and ALARM LEDs switch on and off

If IDU hardware failure occurs, SYNC, RADIO, REMOTE and

Rear panel LEDs are shown in Figure 4.

Indicates operation of the

Ethernet link\activity 100 Mbps speed

Figure 4. Rear panel LEDs

2.2 Interface Modules

V.35 Interface Module

V.35 port failure.

Data activity - data is

120 balanced interface, connector type: RJ-45;

75 unbalanced interface, connector type: BNC, - requires a pair of coaxial

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