User Guide SAGEM - SLF H PDF

Microwave Radio Link
SLF-H
Release 2.2
6 GHz 38 GHz
Installation and Operation Manual
Page 0-2 SLF-H Installation and Operation Manual 253 255 964-D
WARNING
Sagemcom carefully monitors all technical changes and strives continuously to improve its products for the
benefit of its customers.
HANDBOOK CHANGE LIST It therefore reserves the right to change its documentation without prior notice.
All trademarks are registered by their owners.
ENVIRONMENT
(Each new edition supersedes the previous edition)
Preservation of the environment as part of a sustainable development logic is an essential concern of
Sagemcom.
The desire of Sagemcom is to operate systems observing the environment and consequently it has decided
to integrate environmental performances in the life cycle of its products, from manufacturing to commissioning,
use and elimination.
No. Date Change description Page
253 255 964-A September Initial release in original issue All pages PACKAGING:
2009
(3 000 337 386 R11 000-01) The presence of the logo (green dot) means that a contribution is paid to an approved
national organisation to improve packaging recovery and recycling infrastructures.
253 255 964-B November ACM configuration 1.8, 2.4.1, 6.5 To facilitate recycling, please respect the sorting rules set up locally for this kind of waste.
2009
(3 000 337 386 R11 000-02)
253 255 964-C June 2010 Release 2.1 bis All pages BATTERIES:
(3 000 337 386 R11 000-03)

If your product contains batteries, they must be disposed of at appropriate collection points.
253 255 964-D February Release 2.2 All pages
2011
(3 000 337 386 R11 000-04)
THE PRODUCT:
The crossed-out waste bin stuck on the product (or on its accessories) means that the
product belongs to the family of electrical and electronic equipment.
In this respect, the European regulations ask you to dispose of it selectively:
x At sales points in the event of the purchase of similar equipment.
x At the collection points made available to you locally (drop-off centre, selective
collection, etc.).
In this way you can participate in the re-use and upgrading of WEE (Waste Electrical and Electronic
Equipment), which can have an effect on the environment and human health.
SLF-H Installation and Operation Manual 253 255 964-D Page 0-3 Page 0-4 SLF-H Installation and Operation Manual 253 255 964-D
3. INSTALLATION ........................................................................................................................................................ 3-1
3.1 - INTRODUCTION ...................................................................................................................................................... 3-1
TABLE OF CONTENTS 3.2 - UNPACKING THE EQUIPMENT ................................................................................................................................. 3-1
3.3 - IDU INSTALLATION................................................................................................................................................ 3-2
3.4 - ANTENNA INSTALLATION....................................................................................................................................... 3-2
3.4.1 - Antenna mount ............................................................................................................................... 3-3
1. SYSTEM DESCRIPTION .......................................................................................................................................... 1-1 3.4.2 - Antenna Installation ........................................................................................................................ 3-3
3.5 - ODU INSTALLATION .............................................................................................................................................. 3-4
1.1 - INTRODUCTION ...................................................................................................................................................... 1-1
3.5.1 - 1+0 Configuration with integrated antenna..................................................................................... 3-4
1.2 - DESCRIPTION.......................................................................................................................................................... 1-2
3.5.2 - 1+0 Configuration with pole mount and standard antenna............................................................. 3-5
1.2.1 - System composition ....................................................................................................................... 1-2
3.5.3 - "Hot standby" 1+1 configuration with coupler and integrated antenna .......................................... 3-5
1.2.2 - IDU version ..................................................................................................................................... 1-3
3.5.4 - 1+1 hot standby configuration with remote mounted coupler and standard antenna .................... 3-6
1.2.3 - Modem version ............................................................................................................................... 1-3
3.5.5 - 1+1 space diversity configuration with 2 antennas......................................................................... 3-7
1.2.4 - Fan version ..................................................................................................................................... 1-3
3.5.6 - 1+1 frequency diversity configuration with remote mounts and dual polarized antenna ............... 3-7
1.2.5 - Optional MUX64 SPDH version...................................................................................................... 1-3
3.5.7 - 1+1 frequency diversity configuration with 2 antennas .................................................................. 3-7
1.2.6 - ODU Versions................................................................................................................................. 1-4
3.5.8 - 2+0 frequency diversity configuration with remote mounts and dual polarized antenna ............... 3-7
1.3 - SLF-H FEATURES ................................................................................................................................................... 1-6
3.5.9 - 2+0 frequency diversity configuration with 2 antennas .................................................................. 3-7
1.3.1 - SLF-H block diagrams .................................................................................................................... 1-6
3.5.10 - 2+0 XPIC configuration with remote mounts and dual polarized antenna ................................... 3-7
1.3.2 - IDU features.................................................................................................................................... 1-7
3.6 - INSTALLING THE IDU TO ODU COAXIAL CABLE ................................................................................................... 3-8
1.3.3 - Modem features.............................................................................................................................. 1-7
3.7 - CONNECTING THE IDU TO EXTERNAL EQUIPMENT ................................................................................................. 3-9
1.3.4 - ODU features.................................................................................................................................. 1-8
3.7.1 - IDU Front panel accesses .............................................................................................................. 3-9
1.3.5 - MUX64 SPDH shelf features .......................................................................................................... 1-8
3.7.2 - Description of accesses and connectors...................................................................................... 3-10
1.4 - PROTECTED CONFIGURATIONS ............................................................................................................................... 1-9 3.7.2.1 - "POWER" access 4-pin connector ........................................................................................................................ 3-10
1.4.1 - 1+1 Hot Stand By ........................................................................................................................... 1-9 3.7.2.2 - The connector pinout is as follows: ......................................................................................................................... 3-10
1.4.1.1 - Transmitter operation & performances ...................................................................................................................... 1-9 3.7.2.3 - "Alarms in/out" access High density 15-pin DB connector .................................................................................. 3-10
1.4.1.2 - Receiver operation & performances ........................................................................................................................ 1-10 3.7.2.4 - "Mgmt" and "Wayside" Ethernet ports .................................................................................................................... 3-12
1.4.2 - 1+1 Space diversity ...................................................................................................................... 1-10 3.7.2.5 - Gigabit Ethernet ports "GbE1" to "GbE4" ............................................................................................................... 3-12
1.4.2.1 - Transmitter operation & performances .................................................................................................................... 1-10 3.7.2.6 - G703 2 Mbit/s ports - 44-pin DB connectors........................................................................................................... 3-13
1.4.2.2 - Receiver operation & performances ........................................................................................................................ 1-11 3.7.3 - Cable references for SLF-H.......................................................................................................... 3-16
1.4.3 - 1+1 Frequency diversity ............................................................................................................... 1-11 3.7.4 - Module references for SLF-H ....................................................................................................... 3-18
1.4.3.1 - Transmitter operation & performances .................................................................................................................... 1-12 3.8 - MUX64 SPDH UNIT (OPTIONAL) ........................................................................................................................ 3-18
1.4.3.2 - Receiver operation & performances ........................................................................................................................ 1-12
3.8.1 - Front panel accesses of MUX 64 SPDH shelf.............................................................................. 3-19
1.5 - ACM CONFIGURATION ......................................................................................................................................... 1-13
3.8.2 - Description of accesses and connectors...................................................................................... 3-19
1.6 - 2+0 CONFIGURATIONS .......................................................................................................................................... 1-17 3.8.2.1 - "POWER" access 4-pin connector ........................................................................................................................ 3-19
1.6.1 - 2+0 FD .......................................................................................................................................... 1-18 3.8.2.2 - G703 2 Mbit/s ports - 78-pin DB connectors........................................................................................................... 3-19
1.6.2 - 2+0 XPIC ...................................................................................................................................... 1-19 3.8.3 - MUX32 SPDH version .................................................................................................................. 3-21
2. GIGABIT ETHERNET FUNCTION ........................................................................................................................ 2-1 3.8.4 - Cable References for MUX64 SPDH shelf................................................................................... 3-22
3.9 - POWERING UP THE SYSTEM .................................................................................................................................. 3-23
2.1 - INTRODUCTION ...................................................................................................................................................... 2-1
2.2 - PORTS .................................................................................................................................................................... 2-1 4. COMMISSIONING CONFIGURATION AND TESTS .......................................................................................... 4-1
2.2.1 - Definition......................................................................................................................................... 2-1 4.1 - INTRODUCTION ...................................................................................................................................................... 4-1
2.2.2 - Jumbo frames ................................................................................................................................. 2-1 4.2 - CONFIGURING EQUIPMENT IP ADDRESSES .............................................................................................................. 4-1
2.2.3 - Available Ethernet radio bandwidth (ACM) .................................................................................... 2-1 4.3 - PILOT SOFTWARE AND IP CONNECTIVITY ............................................................................................................... 4-6
2.3 - TOPOLOGIES ........................................................................................................................................................... 2-2 4.3.1 - Installing the software Pilot Launcher............................................................................................. 4-6
2.3.1 - 4 EPLINE mode .............................................................................................................................. 2-2 4.3.2 - Installing the Pilot software............................................................................................................. 4-7
2.3.2 - Advanced mode.............................................................................................................................. 2-2 4.3.3 - IP connectivity................................................................................................................................. 4-8
2.3.2.1 - EPLAN mode ............................................................................................................................................................ 2-2
4.3.4 - Launch Auto Pilot with the Pilot Launcher:..................................................................................... 4-9
2.3.2.2 - EVPLINE/EVPLAN modes....................................................................................................................................... 2-2
4.3.5 - Starting a Pilot session ................................................................................................................. 4-10
2.4 - SERVICE QUALITY (QOS) ....................................................................................................................................... 2-3
4.4 - LINK PRELIMINARY CONFIGURATION ................................................................................................................... 4-11
2.4.1 - Generalities..................................................................................................................................... 2-3
4.4.1 - Setting the parameters of each IDU ............................................................................................. 4-11
2.4.2 - Frames classification ...................................................................................................................... 2-3
4.4.2 - Antenna alignment........................................................................................................................ 4-16
2.4.3 - Metering.......................................................................................................................................... 2-4
4.4.3 - Antenna alignment in XPIC mode ................................................................................................ 4-21
2.4.4 - Congestion handling....................................................................................................................... 2-4
2.4.4.1 - Description................................................................................................................................................................. 2-4
4.5 - TESTS AND MEASUREMENTS REQUIRED ................................................................................................................ 4-23
2.4.4.2 - Limitation of port bandwidth ..................................................................................................................................... 2-4 4.5.1 - Frequency Scan............................................................................................................................ 4-23
2.4.4.3 - Flow control............................................................................................................................................................... 2-4 4.5.2 - Receive signal level...................................................................................................................... 4-23
2.4.4.4 - Drop of frames........................................................................................................................................................... 2-5 4.5.3 - Giga Ethernet transmission test ................................................................................................... 4-24
2.4.4.4.1 - Principe................................................................................................................................................................ 2-5 4.5.4 - 2 Mbit/s tributary test (optional) .................................................................................................... 4-28
2.4.4.4.2 - Output queues (traffic classes)............................................................................................................................. 2-5 4.5.5 - Wayside test (optional) ................................................................................................................. 4-29
2.4.4.4.3 - Control of flows rate (policing) ........................................................................................................................... 2-5 4.5.6 - Alarm relay test (optional)............................................................................................................. 4-30
2.4.4.4.4 - CIR/PIR values .................................................................................................................................................... 2-5 4.5.6.1 - Simulating an IDU Alarm........................................................................................................................................ 4-30
2.4.4.4.5 - Shaping of "Very High Priority" traffic class ...................................................................................................... 2-6 4.5.6.2 - Simulating an ODU Alarm ...................................................................................................................................... 4-31
2.5 - MAC FILTERING .................................................................................................................................................... 2-6 4.5.6.3 - Simulating a Gigabit Ethernet Alarm....................................................................................................................... 4-31
2.6 - COUNTERS ............................................................................................................................................................. 2-6 4.5.6.4 - Simulating a tributary alarm .................................................................................................................................... 4-31
4.5.6.5 - Simulating an RSL alarm......................................................................................................................................... 4-31 6.2.3 - "File / IDU Configuration / Local or Remote / Load" menu ............................................................. 6-4
4.5.6.6 - Testing an external alarm......................................................................................................................................... 4-31 6.2.4 - "File / Boot Firmware / Local or Remote" menu ............................................................................. 6-5
4.5.6.7 - Testing the alarm outputs (relays)............................................................................................................................ 4-32 6.2.5 - "File / IDU Firmware / Local or Remote" menu .............................................................................. 6-5
4.5.7 - Testing 1+1 configuration (optional) ............................................................................................. 4-32 6.2.6 - "File / ODU Firmware / Local or Remote" menu............................................................................. 6-6
4.5.8 - Quality measurement ................................................................................................................... 4-34 6.2.7 - "File / Quit" menu............................................................................................................................ 6-6
4.5.9 - Recording configuration information............................................................................................. 4-34 6.3 - SESSION MENU ....................................................................................................................................................... 6-6
5. FINAL LINK CONFIGURATION............................................................................................................................ 5-1 6.4 - ALARMS MENU ....................................................................................................................................................... 6-7
6.4.1 - "Alarms / View / Local or Remote" menu........................................................................................ 6-7
5.1 - ENTERING SITE NAMES ........................................................................................................................................... 5-1 6.4.2 - "Alarms / Text Log / Local or Remote" menu ................................................................................. 6-8
5.2 - SETTING THE DATE AND TIME................................................................................................................................. 5-1 6.4.3 - "Alarms /Graphical Log / Local or Remote" menu.......................................................................... 6-9
5.3 - CONFIGURING GIGABIT ETHERNET ........................................................................................................................ 5-2 6.5 - CONFIGURATION / ALARMS MENU ......................................................................................................................... 6-9
5.3.1 - Notations used in this manual ........................................................................................................ 5-2 6.6 - CONFIGURATION / MANAGEMENT NETWORK / ETHERNET PORTS AND RADIO CHANNEL / LOCAL OR REMOTE MENU
5.3.2 - Ethernet Port configuration............................................................................................................. 5-2 ..................................................................................................................................................................................... 6-10
5.3.2.1 - Physical configuration ............................................................................................................................................... 5-3 6.6.1 - Description of the Management network...................................................................................... 6-10
5.3.2.2 - Advanced configuration............................................................................................................................................. 5-3
6.6.2 - Network configuration................................................................................................................... 6-12
5.3.3 - QOS Global configuration............................................................................................................... 5-5
6.6.3 - Wayside configuration .................................................................................................................. 6-13
5.3.4 - QOS & services configuration ........................................................................................................ 5-6
6.7 - CONFIGURATION / MANAGEMENT NETWORK /ROUTES / LOCAL OR REMOTE MENU ............................................ 6-14
5.3.4.1 - Service types.............................................................................................................................................................. 5-7
5.3.4.1.1 - 4 EPLINE mode................................................................................................................................................... 5-8 6.8 - CONFIGURATION / GIGABIT ETHERNET MENU ...................................................................................................... 6-15
5.3.4.1.2 - Advanced mode ................................................................................................................................................... 5-8 6.9 - CONFIGURATION / PROTECTION / LOCAL OR REMOTE MENU ................................................................................ 6-15
5.3.4.1.3 - EPLAN ................................................................................................................................................................ 5-8 6.10 - CONFIGURATION / ATPC / LOCAL OR REMOTE MENU........................................................................................ 6-16
5.3.4.1.4 - EVPLINE/EVPLAN............................................................................................................................................ 5-8 6.11 - CONFIGURATION /E1 TRIBUTARIES / LOCAL OR REMOTE MENU ........................................................................ 6-16
5.3.4.2 - Port modes and tagging possibilities.......................................................................................................................... 5-9 6.12 - CONFIGURATION / HARDWARE INVENTORY / LOCAL OR REMOTE MENU ........................................................... 6-16
5.3.4.2.1 - UNI-N................................................................................................................................................................ 5-10 6.13 - CONFIGURATION / PILOT MENU .......................................................................................................................... 6-17
5.3.4.2.2 - I-NNI ................................................................................................................................................................. 5-10 6.14 - CONFIGURATION / RESET TO DEFAULT DATABASE / LOCAL OR REMOTE MENU ................................................. 6-17
5.3.4.2.3 - E-NNI ................................................................................................................................................................ 5-10 6.15 - PERFORMANCE / RSL / LOCAL OR REMOTE MENU ............................................................................................. 6-17
5.3.4.2.4 - EtherType .......................................................................................................................................................... 5-11
6.16 - PERFORMANCE / LINK STATISTICS / LOCAL OR REMOTE MENU ......................................................................... 6-18
5.3.4.3 - QOS parameters....................................................................................................................................................... 5-11
5.3.4.3.1 - Available classes of service ............................................................................................................................... 5-11 6.17 - PERFORMANCE / GIGABIT ETHERNET / GENERAL ETHERNET STATISTICS / LOCAL OR REMOTE MENU............... 6-19
5.3.4.3.2 - Strict priority shaping ........................................................................................................................................ 5-12 6.18 - PERFORMANCE / GIGABIT ETHERNET / METERING STATISTICS / LOCAL OR REMOTE MENU .............................. 6-20
5.3.4.3.3 - Metering and policing........................................................................................................................................ 5-12 6.19 - PERFORMANCE / WAYSIDE / LOCAL OR REMOTE MENU ..................................................................................... 6-20
5.3.4.3.4 - Bandwidth computation examples..................................................................................................................... 5-15 6.20 - PERFORMANCE / CLEAR BER STATS / LOCAL OR REMOTE MENU ...................................................................... 6-21
5.3.4.4 - Services and QOS configuration.............................................................................................................................. 5-16 6.21 - PERFORMANCE / CLEAR/RESET ALL .................................................................................................................. 6-22
5.3.4.4.1 - Classification principle ...................................................................................................................................... 5-16 6.22 - MAINTENANCE / TX/RX FORCING MENU ............................................................................................................ 6-22
5.3.4.4.2 - Available classification types ............................................................................................................................ 5-18 6.23 - MAINTENANCE / LOOPBACKS MENU .................................................................................................................. 6-23
5.3.4.4.3 - User predefined classifications .......................................................................................................................... 5-23 6.24 - MAINTENANCE / FREQUENCY SCAN / CHANNEL 1 OR CHANNEL 2 MENU ........................................................... 6-23
5.3.4.4.4 - PCP encoding .................................................................................................................................................... 5-25
6.25 - MAINTENANCE / TRY TO UNMUTE REMOTE / LOCAL OR REMOTE MENU ............................................................ 6-24
5.3.5 - Other features............................................................................................................................... 5-27
5.3.5.1 - Flow control............................................................................................................................................................. 5-27
6.26 - MAINTENANCE / RESTRICTION / LOCAL OR REMOTE MENU ............................................................................... 6-24
5.3.5.2 - Mac filtering ............................................................................................................................................................ 5-28 7. TROUBLESHOOTING GUIDE................................................................................................................................ 7-1
5.3.5.3 - Fast link shutdown................................................................................................................................................... 5-29
5.3.5.4 - FDB management .................................................................................................................................................... 5-29 7.1 - INTRODUCTION ...................................................................................................................................................... 7-1
5.3.5.5 - Ethernet with 2+0 XPIC or FD modes..................................................................................................................... 5-30 7.2 - VISUAL INSPECTION ............................................................................................................................................... 7-1
5.3.5.6 - Ethernet with ACM.................................................................................................................................................. 5-30 7.3 - TROUBLESHOOTING PROCEDURE ............................................................................................................................ 7-2
5.4 - CONFIGURING 2 MBIT/S PORTS............................................................................................................................. 5-32 7.3.1 - Describe the symptom.................................................................................................................... 7-2
5.5 - CONFIGURING THE ALARM THRESHOLDS .............................................................................................................. 5-34 7.3.2 - Isolate the problem ......................................................................................................................... 7-2
5.5.1 - BER and ACM alarm thresholds................................................................................................... 5-34 7.3.3 - Fix the problem ............................................................................................................................... 7-2
5.5.2 - RSL alarm threshold..................................................................................................................... 5-34 7.4 - DESCRIPTION OF IDU FRONT PANEL LEDS ............................................................................................................. 7-2
5.5.3 - Ethernet bitrate alarm threshold ................................................................................................... 5-35 7.4.1 - IDU Leds......................................................................................................................................... 7-3
5.6 - CONFIGURING THE ALARMS ................................................................................................................................. 5-36 7.4.2 - Modem Leds ................................................................................................................................... 7-3
5.6.1 - General parameters...................................................................................................................... 5-36 7.4.3 - Leds of the MUX64 SPDH shelf ..................................................................................................... 7-3
5.6.2 - "IDU" tab ....................................................................................................................................... 5-37 7.5 - ALARMS MANAGED BY THE PILOT ......................................................................................................................... 7-4
5.6.3 - "Modem" tab ................................................................................................................................. 5-38 7.5.1 - Alarm summary screen................................................................................................................... 7-4
5.6.4 - "Radio" tab.................................................................................................................................... 5-38 7.5.2 - Direct and indirect alarms............................................................................................................. 7-11
5.6.5 - "Tributaries" tab ............................................................................................................................ 5-40 7.5.3 - Event log....................................................................................................................................... 7-11
5.6.6 - "Gigabit Ethernet" tab ................................................................................................................... 5-41 7.6 - TYPICAL SLF-H PILOT SCREENS IN CASE OF PROBLEM ........................................................................................ 7-11
5.6.7 - "Fans" tab ..................................................................................................................................... 5-41 7.6.1 - No IDU-Pilot software communication.......................................................................................... 7-11
5.6.8 - Default configuration of the alarm relays...................................................................................... 5-43 7.6.2 - No local equipment, no remote equipment................................................................................... 7-11
5.7 - CONFIGURING THE AUTOMATIC TRANSMIT POWER CONTROL (ATPC) ............................................................... 5-43 7.6.3 - No local radio................................................................................................................................ 7-12
5.8 - SPECIFIC CONFIGURATIONS FOR 1+1 SYSTEMS ..................................................................................................... 5-44 7.6.4 - No remote radio ............................................................................................................................ 7-12
6. OPERATION PILOT............................................................................................................................................... 6-1 7.6.5 - Low RSL ....................................................................................................................................... 7-13
7.6.6 - Low transmit power ...................................................................................................................... 7-13
6.1 - HELP MENU ............................................................................................................................................................ 6-3 7.6.7 - Link established correctly but with some alarms .......................................................................... 7-14
6.2 - FILE MENU ............................................................................................................................................................. 6-4 7.6.8 - Normal link no alarms................................................................................................................... 7-14
6.2.1 - "File / System Report" menu .......................................................................................................... 6-4 7.7 - REPLACING AN ODU............................................................................................................................................ 7-14
6.2.2 - "File / IDU Configuration / Local or Remote / Save" menu............................................................. 6-4 7.8 - REPLACING A MODEM .......................................................................................................................................... 7-15
7.9 - REPLACING AN IDU ............................................................................................................................................. 7-15
7.10 - REPLACING A FAN MODULE ............................................................................................................................. 7-15
7.11 - REPLACING A MUX64 SPDH SHELF .................................................................................................................. 7-15
APPENDIX 1- SLF-H SPECIFICATIONS .......................................................................................................................1 FIGURES
GENERAL CHARACTERISTICS ..............................................................................................................................................1
TRANSMISSION CHARACTERISTICS......................................................................................................................................2
RECEPTION CHARACTERISTICS............................................................................................................................................3 Figure 1.1 - SLF-H 1+0 terminal ....................................................................................................................................... 1-2
GIGABIT ETHERNET / 2 MBIT/S ACCESS ..............................................................................................................................4 Figure 1.2 - SLF-H 1+1 Terminal (HSB) .......................................................................................................................... 1-3
ALARMS, WAYSIDE AND NETWORK MANAGEMENT INTERFACES .........................................................................................4 Figure 1.3 - Minimum and maximum channel frequencies ............................................................................................... 1-4
MECHANICAL CHARACTERISTICS ........................................................................................................................................4 Figure 1.4 - SLF-H block diagram..................................................................................................................................... 1-6
POWER CONSUMPTION ........................................................................................................................................................5 Figure 1.5 - 1+1 Hot Stand By configuration .................................................................................................................... 1-9
ENVIRONMENTAL CHARACTERISTICS..................................................................................................................................5 Figure 1.6 - 1+1 Space diversity configuration................................................................................................................ 1-10
HEALTH CHARACTERISTICS ................................................................................................................................................5 Figure 1.7 - 1+1 Frequency diversity configuration ........................................................................................................ 1-11
APPENDIX 2 - SLF-H REFERENCES .............................................................................................................................1
Figure 3.1 - IDU installation.............................................................................................................................................. 3-2
LINK COMPOSITION .............................................................................................................................................................1 Figure 3.2 - ODU SLF-H with integrated antenna............................................................................................................. 3-4
REFERENCES OF ODUS HL.................................................................................................................................................2 Figure 3.3 - Polarization setting in 1+0 configuration ....................................................................................................... 3-4
REFERENCES OF ODUS H .................................................................................................................................................10 Figure 3.4 - ODU SLF-H mounted on pole ....................................................................................................................... 3-5
REFERENCES OF ODUS NL...............................................................................................................................................19 Figure 3.5 - SLF-H 1+1 configuration with coupler and integrated antenna ..................................................................... 3-6
REFERENCES OF ODUS N .................................................................................................................................................27 Figure 3.6 - Polarization setting on 1+1 coupler................................................................................................................ 3-6
Figure 3.7 - Front panel of the SLF-H IDU in 1+0 configuration...................................................................................... 3-9
Figure 3.8 - Front panel of the SLF-H IDU in 1+1 configuration...................................................................................... 3-9
Figure 3.9 - "Serial" connector pinout ............................................................................................................................. 3-10
Figure 3.10 - Relay output electrical interface................................................................................................................. 3-11
Figure 3.11 - External alarm electrical interface.............................................................................................................. 3-11
Figure 3.12 - Cables for a terminal station....................................................................................................................... 3-16
Figure 3.13 - Cables for a relay station ............................................................................................................................ 3-16
Figure 3.14 - Front panel of MUX64 SPDH Unit............................................................................................................ 3-18
Figure 3.15 - SLF-H 1+1 IDU ......................................................................................................................................... 3-23
Figure 4.1 - SLF-H ODU RSL voltage ............................................................................................................................ 4-17

Figure 4.2 - Antenna alignment ....................................................................................................................................... 4-18
Figure 4.3 - Main Pilot Screen for a 1+0 configuration Fixed modulation................................................................... 4-18
Figure 4.4 - Main Pilot Screen for a 1+0 configuration ACM modulation................................................................... 4-19
Figure 4.5 - Main Pilot Screen for a 1+1 configuration Fixed modulation................................................................... 4-19
Figure 4.6 - Main Pilot Screen for a 1+1 configuration ACM modulation................................................................... 4-20
Figure 4.7 - Local transmitter 1 and local receiver 1 active............................................................................................. 4-32
Figure 4.8 - Local transmitter1 and local receiver 2 active.............................................................................................. 4-33
Figure 4.9 - Local transmitter 2 and local receiver 2 active............................................................................................. 4-33
Figure 6.1 - Equipment shelf view without SPDH extension ............................................................................................ 6-1
Figure 6.2 - Equipment shelf view with SPDH extension ................................................................................................. 6-1
Figure 6.3 - Pilot menu tree structure ................................................................................................................................ 6-2
Figure 7.1 - IDU front panel Leds...................................................................................................................................... 7-2

Figure 7.2 - Alarms screen on the Pilot ............................................................................................................................. 7-4
TABLES
Table 3-1 - 4-pin "POWER" connector pinout ................................................................................................................ 3-10

Table 3-2 - "Alarm in/out" connector pinout ................................................................................................................... 3-12
Table 3-3 - Ethernet port pinout....................................................................................................................................... 3-12
Table 3-4 - Characteristics of the Gigabit Ethernet optical interface............................................................................... 3-13
Table 3-5 - TRIB 1-8 connector pinout............................................................................................................................ 3-14
Table 3-6 - TRIB 9-16 connector pinout.......................................................................................................................... 3-15
Table 3-7 - Cable References for SLF-H ......................................................................................................................... 3-17
Table 3-8 - SFP module references for SLF-H ................................................................................................................ 3-18
Table 3-9 - TRIB16E1 connector pinout for the MUX64 SPDH unit ............................................................................. 3-21
Table 3-10 - Cable References for MUX64 SPDH unit................................................................................................... 3-22
Table 4-1 - Configuration compatibility .......................................................................................................................... 4-14

Table 4-2 - Configuration compatibility .......................................................................................................................... 4-15
Table 5-1 - Default configuration of the alarm relays...................................................................................................... 5-43
Table 7-1 - Meaning of the Wayside alarm ....................................................................................................................... 7-5

Table 7-2 - Meaning of radio alarms ................................................................................................................................. 7-5
Table 7-3 - Meaning of the SPDH alarm ........................................................................................................................... 7-5
Table 7-4 - Meaning of Fan and Temperature alarms........................................................................................................ 7-6
Table 7-5 - Meaning of Modem alarms ............................................................................................................................. 7-7
Table 7-6 - Meaning of ODU alarms ................................................................................................................................. 7-8
Table 7-7 - Meaning of Gigabit Ethernet alarms ............................................................................................................... 7-9
Table 7-8 - Meaning of E1 Tributary alarms ..................................................................................................................... 7-9
Table 7-9 - Meaning of External alarms .......................................................................................................................... 7-10
SLF-H Installation and Operation Manual 253 255 964-D Page 0-11
0BSYSTEM DESCRIPTION 0BSYSTEM DESCRIPTION
1. SYSTEM DESCRIPTION 1.2 - DESCRIPTION
1.2.1 - System composition

1.1 - INTRODUCTION
All SLF-H configurations are built from standard units installed in a 19" 1U chassis.
The SLF-H range of microwave radio links provides highly reliable point to point communication with
low installation costs in different frequency bands. This high-capacity range of microwave frequencies x An IDU (Indoor Unit) composed of:
is characterized by excellent flexibility capabilities in terms of transmission capacity and of frequency x A Backplane connecting the various IDU units.
bands used. It allows simultaneous or independent transport of Giga Ethernet data and 2Mbit/s links
x An INT mother board providing the various IDU accesses: Giga Ethernet, Wayside, external
by PDH/Ethernet multiplexing.
alarm and relay outputs, serial management ports, PC access.
SLF-H proposes ACM (Adaptive Coding & Modulation) configurations thanks to which the system can x An optional TNM4 card (daughter card) inserted on the mother board and providing 16
automatically and dynamically change of profile (i.e. of modulation scheme) based on the radio ports, E1.
channel quality, so that if offers both the best throughput and the best robustness at any time.
x A hot pluggable U MODEM providing the cable interface with the ODU; in 1+1 and 2+0
SLF-H equipment is available in unprotected 1+0 configuration, in protected 1+1 configuration (Hot configurations, two Modems are installed in the chassis, each one being associated to an
Stand By, Space diversity, Frequency diversity) and in 2+0 configuration (XPIC, Frequency Diversity) ODU.
to double the radio channel capacity. x A hot pluggable FAN module with three speed-controlled fans to cool the IDU.
x Main telecommunication radio bands covered: 6, 7, 8, 11, 13, 15, 18, 23, 26, 32 and 38 GHz
x An ODU (Outdoor Unit) providing the cable interface with the IDU. It consists of one transmitter
x 4 Gigabit Ethernet Interfaces + 80 optional E1 ports and one receiver and performs frequency conversion and signal amplification.
x Advanced switching and quality of service configuration for Ethernet traffic
A 1+0 terminal using an integrated antenna is presented on Figure 1.1 - SLF-H 1+0 terminal and a
x Fixed Modulation: QPSK, 16QAM, 32QAM, 64QAM, 128QAM, 256QAM 1+1 terminal using a coupler is presented on Figure 1.2.
x ACM Modulation: QPSK (two different profiles), 16QAM, 32QAM, 64QAM, 128QAM, 256QAM
(three different profiles)
x Radio channel: 7MHz, 14 MHz, 28 MHz, 56 MHz
x XPIC mode (for 28MHz and 56MHz radio channels only)
x Integrated measurement of bit and packet errors rate and receive signal level
x Wide transmit power range in steps of 0.5 dB
x Automatic Tx Power Control (ATPC algorithm)
x Synthesizer frequency step: 250 kHz
x Full software control Integrated antenna
x Full compliance with ETSI standards ODU
Other features available:
x 1 Wayside 10/100BaseT Ethernet channel IDU

Modem Fan
x 5 external alarm inputs and 3 configurable relay outputs
x 1 management interface with two 10/100BaseT Ethernet ports connected by an integrated
switch
x 1 VT100 configuration RS232 interface
Figure 1.1 - SLF-H 1+0 terminal
1.2.6 - ODU Versions
SLF-H equipment is available in the following frequency bands: 6 GHz, 7 GHz, 8 GHz, 11 GHz,
13 GHz, 15 GHz, 18 GHz, 23 GHz, 26 GHz, 32 GHz and 38 GHz.
Each frequency band is divided into several sub-bands. For each sub-band, there is one Low Band
ODU and one high band ODU.
The complete list of ODUs is given in APPENDIX 2
The ODU minimum and maximum frequencies indicated in this list correspond to the duplexer useful
bandwidth.
The minimum and maximum channel frequencies depend on the channel occupied bandwidth and
therefore on the capacity.
The following diagram summarizes the rules used to determine the minimum and maximum
depending on the channel type used: see figure below.
Fmin (ODU) Fmax (ODU)
ODU bandwith
56 MHz radio channel

Figure 1.2 - SLF-H 1+1 Terminal (HSB) Fmin56 = FminODU+20 Fmax56 = FmaxODU-20
20 MHz 20 MHz
x An optional MUX64 SPDH shelf constituted of a "MUX64 Extension SPDH" card providing
64 x 2 Mbit/s ports. 28 MHz radio channel
Fmin28 = FminODU+10 Fmax28 = FmaxODU-10
1.2.2 - IDU version

10 MHz 10 MHz
x UFX-SP P2 (253302846): GE chassis
x UFE-16E1 (253302812): Optional 16E1 extension card (TNM4)
Fmin14 = FminODU+5 14 MHz radio channel Fmax14 = FmaxODU-5
1.2.3 - Modem version
5 MHz 5 MHz
x UFC-HW P2 (253115222): fixed or ACM QPSK to 256QAM 7 MHz to 56 MHz, software
selectable
x UFC-HX P2 (253199822): fixed or ACM QPSK to 256QAM 7 MHz to 56 MHz XPIC Fmin7 = FminODU+2.5 7 MHz radio channel Fmax14 = FmaxODU-2.5
support, software selectable
2.5 MHz 2.5 MHz
1.2.4 - Fan version
x UFF P2 (253183126): hot swap fan module.

Figure 1.3 - Minimum and maximum channel frequencies
1.2.5 - Optional MUX64 SPDH version

x For a 56 MHz radio channel, the minimum frequency is: FminODU + 20 MHz and the maximum
x UFE-R 64E1 (253199728): Optional 64E1 extension chassis
frequency is: FmaxODU - 20 MHz
x UFE-RL (253311134): Optional 32E1 extension chassis
x For a 28 MHz radio channel, the minimum frequency is: FminODU + 10 MHz and the maximum 1.3 - SLF-H FEATURES
x For a 14 MHz radio channel, the minimum frequency is: FminODU + 5 MHz and the maximum
1.3.1 - SLF-H block diagrams
x For a 7 MHz radio channel, the minimum frequency is: FminODU + 2.5 MHz and the maximum The IDU-ODU interface consists of a single coaxial cable in 1+0 system. This cable transports the
frequency is: FmaxODU - 2.5 MHz following frequency multiplexed signals:
Uplink:
x ODU remote power supply (-48 V DC).
x The modulated transmit IF signal (350 MHz).
x The uplink telemetry signal consisting of a 5.5 MHz carrier amplitude modulated by a 19200 bit/s
digital signal.
Downlink:
x The modulated receive IF signal (140 MHz).
x The downlink telemetry signal consisting of a 10 MHz carrier amplitude modulated by a 19200 bit/s
digital signal.
The SLF-H block diagram is given below.
Figure 1.4 - SLF-H block diagram
1.3.2 - IDU features x A 140 MHz demodulator including:

- 140 MHz I/Q Demodulator and analog filtering
The IDU, which is frequency independent, consists of:
- ADC
x A Microprocessor controlling the system and communicating with the ODU, the remote IDU, the - Timing and Carrier recovery
SNMP agent and the Pilot software. - Adaptive equalizer
x A Gigabit Ethernet Switch providing up to 4 Giga Ethernet interfaces equipped with optical or - Digital filter
electrical SFP modules.
- De-mapper
x An interface with an optional TNM4 card providing 16 x 2 Mbit/s G703 channels; the TNM4 card
acts as 2 Mbit/s line interface and tributary multiplexer / demultiplexer. - LDPC decoder (from which the BER is estimated)
x An extension interface located on the optional TNM4 for connecting an optional MUX64 SPDH - Descrambler
chassis offering up to 64 2 Mbit/s G703 channels, leading to a total of up to 80 2 Mbit/s
tributaries.
x A DC-DC power supply, providing the tertiary voltage for the whole IDU (+3.3 V). In 1+1
x A network management interface compliant with SNMP protocol. This management interface protected and 2+0 systems, the unprotected part of the IDU is powered in parallel by the two
includes 2 Ethernet ports. It communicates with the remote network management interface via power supplies from the two cable interfaces. A hot swap feature allows the Modem to be
an internal service channel (TSL). Once the interface has been configured, it acts as router for plugged in and out while powered up.
the network management traffic.
x An interface with 5 external alarm inputs and 3 configurable relay outputs.
x A 10/100BaseT Ethernet Wayside channel 1.3.4 - ODU features
x An RS232 interface to configure the installation
The ODU, which is capacity independent, is an integrated unit consisting of:
x The IDU cable Interface which is the reverse of the Modem interface:
1.3.3 - Modem features - Power supply input (-48 V)
The Modem, which is frequency independent, performs the following functions: - 350 MHz transmit IF input
- Uplink telemetry (5.5 MHz)
x Cable interface with the ODU.
- 140 MHz Receive IF output
Frequency multiplexing is used to carry the following 5 signals on a coaxial cable: - Downlink telemetry (10 MHz)
- ODU power supply (-48 V) x The transmitter which includes two frequency conversions. The frequency synthesis step is
- Transmit IF which is a carrier at 350 MHz frequency 250 kHz
- Uplink telemetry (5.5 MHz) which carries the ODU control signals x The duplexer filter
- Receive IF at 140 MHz x The receiver including two frequency conversions (140 MHz IF output)
- Downlink telemetry (10 MHz) which carries the information returned by the ODU (in x The ODU power supply
particular alarms, receive signal level). x The microcontroller which controls the ODU and communicates with the IDU
x A 350 MHz modulator including:

- Scrambler 1.3.5 - MUX64 SPDH shelf features
- LDPC coder
This optional chassis provides an interface via the TNM4 card allowing to propose 64 x 2 Mbit/s
- Mapper
G703 additional ports; this card provides a function of 2 Mbit/s line interface and a function of tributary
- Digital filter multiplexer/demultiplexer.
- DAC
- 350 MHz I/Q Modulator and analog filtering
1.4 - PROTECTED CONFIGURATIONS 1.4.1.2 - Receiver operation & performances

On the receive side, both receivers are active and receive the same signal from the radio.
1.4.1 - 1+1 Hot Stand By
By default, the selected path in the receiver equipment passes through the Master Modem.
C C When a hardware failure is detected on the Master Modem, Master and Slave states are swapped, so
ODU O O
ODU that the new Master Modem has no hardware problem.
Modem Modem
Master Master U U Master Master This switch leads to less than 1s of hit.
P P
INT L L INT When a hardware failure is detected on the Master ODU, no action is taken. The link is still up thanks to
E E the Slave ODU that is still receiving. The data will now come from the Slave receiver. No error occurs.
Modem ODU R R ODU Modem
Slave Slave Slave Slave When a hardware failure is detected on the Slave Modem or ODU, no action is taken. The link is still up
thanks to the Master path. No error occurs.
Figure 1.5 - 1+1 Hot Stand By configuration The Master/Slave state can be forced using the Pilot interface (for maintenance purpose for instance).
Changing these system parameters leads to less than 1s of hit and it remains forced until the user selects
In that system configuration, there is no radio diversity. Only the hardware (Modems and ODUs) is the automatic mode back.
protected.
In an equipment, one Modem-ODU couple is defined as Master", the other couple is defined as Slave. It is also possible to force the selected receiver path (either from the Master or the Slave). This allows the
user to verify that both receivers work properly, during system installation for instance: this is the
"Maintenance Rx forcing" mode. In that case, the switching is errorless. The system state remains forced
1.4.1.1 - Transmitter operation & performances
until the user selects the automatic mode back.
Only one transmitter is active at a time, the other is muted.
Active ODU is independent of the Master" configuration (meaning a Slave can be the active ODU).
When a dissymmetric coupler is used, the path that leads to the least losses should be associated to the
1.4.2 - 1+1 Space diversity
Main channel (the channel 1, physically the one at the bottom).
When using such a coupler, the user might want to activate the Revertive automatic switching mode,
which makes the system come automatically back to the path with the least losses when the hardware ODU ODU
state allows it. This provides the best transmit power, and so the best link budget. Modem Modem
Master Master Master Master
When a hardware failure is detected on the Master Modem, Master and Slave states are swapped, so
that the new Master Modem has no hardware problem. Additionally, the ODU associated to the broken INT INT
Modem is muted and the other one is un-muted. Thanks to these actions, the link is kept up. Modem ODU ODU Modem
This switch leads to less than 1s of hit. Slave Slave
Once the Slave Modem card is repaired and if the Revertive automatic switching is activated, the active Slave Slave
ODU may be switched automatically to get back the least loss Tx path.
This switch leads to less than 1s of hit.
Figure 1.6 - 1+1 Space diversity configuration
When a hardware failure is detected on the active transmitter, it is muted and the other one is un-muted
and become active, so that the active transmitter has no hardware problem and so the link is kept up. In that system configuration, there is radio protection using space diversity (two independent radio paths
This switch leads to less than 1s of hit. are used with one active transmitter and two active receivers; this greatly improves the link availability).
Once the fault is cleared and if the Revertive automatic switching is activated, the active ODU is The hardware (Modems and ODUs) is protected as well.
switched automatically to get back the least loss Tx path. In an equipment, one Modem-ODU couple is defined as Master" the other couple is defined as Slave.
1.4.2.1 - Transmitter operation & performances
When a hardware failure is detected on the Slave Modem or the muted ODU, no action is taken. The link
is still up because the active Master works properly. No error occurs. Only one transmitter is active at a time, the other is muted.
Active transmitter is independent of the Master" configuration (meaning a Slave can be the active
The Master/Slave state can be forced using the Pilot interface (for maintenance purpose for instance). ODU).
the automatic mode back. When a hardware failure is detected on the Master Modem, Master and Slave states are swapped, so
that the new Master Modem has no hardware problem. Additionally, the ODU associated to the broken
The active ODU can be forced using the Pilot interface (for maintenance purpose for instance). Changing Modem is muted and the other one is un-muted. Thanks to these actions, the link is kept up.
this system parameter leads to less than 1s of hit and it remains forced until the user selects the This switch leads to less than 1s of hit.
automatic mode back.
When a hardware failure is detected on the active ODU, it is muted and the other one is un-muted and
become active, so that the active ODU has no hardware problem and so the link is kept up.
When a hardware failure is detected on the Slave Modem or ODU, no action is taken. The link is still up In an equipment, one Modem-ODU couple is defined as Master" the other couple is defined as Slave.
because the active Master works properly. No error occurs.
The Master/Slave state can be forced using the Pilot interface (for maintenance purpose for instance). 1.4.3.1 - Transmitter operation & performances
the automatic mode back. Both Master and Slave transmitters are active; they emit the exactly same data at two different
frequencies.
The active ODU can be forced using the Pilot interface (for maintenance purpose for instance). Changing
these system parameters leads to less than 1s of hit and it remains forced until the user selects the When a hardware failure is detected on the Master (Modem or ODU), Master and Slave states are
automatic mode back. swapped, so that the new Master Modem has no hardware problem.
1.4.2.2 - Receiver operation & performances
When a hardware failure is detected on the Master ODU, no action is taken. The link is still up thanks to
On the receive side, both receivers are active and get independent signals (from independent radio the Slave ODU that is still emitting. No error occurs.
paths) carrying the same data.
When a hardware failure is detected on the Slave Modem or ODU, no action is taken. The link is still up
By default, the selected path in the receiver equipment passes through the Master Modem. thanks to the Master path. No error occurs.
At each airframe, the system checks whether the data coming from the Master and the Slave contains bit The Master/Slave state can be forced using the Pilot interface (for maintenance purpose for instance).
errors or not. Changing these system parameters leads to less than 1s of hit and it remains forced until the user selects
If the Master has errors whereas the Rx Slave is clean, then the system selects the airframe from the the automatic mode back.
Slave. This switching is of course errorless.
1.4.3.2 - Receiver operation & performances
When a hardware failure is detected on the Master Modem, Master and Slave states are swapped, so
that the new Master Modem has no hardware problem. On the receive side, both receivers are active and get independent signals (from the two emitted
This switch leads to less than 1s of hit. frequencies) carrying the same data.
When a hardware failure is detected on the Master ODU, no action is taken. The link is still up thanks to By default, the selected path in the receiver equipment passes through the Master Modem.
the Slave ODU that is still receiving. The data will now come from the Slave receiver. No error occurs.
At each airframe, the system checks whether the data coming from the Master and the Slave contains bit
When a hardware failure is detected on the Slave Modem or ODU, no action is taken. The link is still up errors or not.
thanks to the Master path. No error occurs. If the Master has errors whereas the Slave is clean, then the system selects the airframe from the Slave.
This switching is of course errorless.
The Master/Slave state can be forced using the Pilot interface (for maintenance purpose for instance).
Changing these system parameters leads to less than 1s of hit and it remains forced until the user selects When a hardware failure is detected on the Master Modem, Master and Slave states are swapped, so
the automatic mode back. that the new Master Modem has no hardware problem.
It is also possible to force the selected receiver path (either from the Master or the Slave). This allows the
user to verify that both receivers work properly, during system installation for instance: this is the When a hardware failure is detected on the Master ODU, no action is taken. The link is still up thanks to
"Maintenance Rx forcing" mode. In that case, the switching is errorless. The system state remains forced the Slave ODU that is still receiving. The data will now come from the Slave receiver. No error occurs.
until the user selects the automatic mode back.
When a hardware failure is detected on the Slave Modem or ODU, no action is taken. The link is still up
thanks to the Master path. No error occurs.
1.4.3 - 1+1 Frequency diversity The Master/Slave state can be forced using the Pilot interface (for maintenance purpose for instance).
F1 / F1
the automatic mode back.
ODU ODU
Modem Modem It is also possible to force the selected receiver path (either from the Master or the Slave). This allows the
Master Master Master Master user to verify that both receivers work properly, during system installation for instance: this is the
"Maintenance Rx forcing" mode. In that case, the switching is errorless. The system state remains forced
INT INT until the user selects the automatic mode back.
F2 / F2
Modem ODU ODU Modem
Slave Slave Slave Slave
Figure 1.7 - 1+1 Frequency diversity configuration
In that system configuration, there is radio protection using frequency diversity (two different frequencies
are used: two active transmitters and two active receivers, one transmitter being associated to one
receiver; this greatly improves the link availability). The hardware (Modems and ODUs) is protected as
well.
1.5 - ACM CONFIGURATION

In ACM configuration, the system is able to change automatically and dynamically parameters of the
transmitted signal to best match to the radio channel quality.
The idea consists in defining several ACM profiles characterized by a modulation scheme and an efficiency
of error correcting code. The system will move from an ACM profile to another according to the signal quality
estimated at the receiver end.
In order to offer a smooth and smart adaptation to the channel capacity at anytime, the SLF-H product offers
up to 9 ACM profiles.
The highest profile offered is user-configurable and will also depend on the SW license.
The lowest profile will depend on the number of PDH tributaries used. Please refer to the Table 4-2.
The changes of ACM profile do not generate any bit error and can handle flat fading rates greater than
100dB/s as well as strong selective fading.
When the ACM profile is changed, the effective data rate is modified accordingly. For example, when the
modulation scheme decreases and/or when the efficiency of the code is increased, the available throughput
being able to pass through the radio channel decreases; as a trade-off, the system becomes more robust
regarding radio disturbances and so keeps the link up without any bit errors on the still available traffic.
Only the rate allocated to the Ethernet traffic is modified to adapt to the current ACM profile. All the other
tributaries (PDH, management) keep the exactly same rate whatever is the current ACM profile.
If the quality of service (QoS) is activated, the Ethernet shaping is automatically adapted, making it possible to
guarantee the quality constraints on the different priority Ethernet flows.
See below a synthetic illustration of ACM:
Maximum profile:
The maximum profile defines the ACM profile above which the system will never go.
Min GE and Max profiles can be selected among up to 9 ACM profiles.

The choice of minimum and maximum profiles is done by the next configuration window:
See 2 for more details concerning the configuration of the quality of Ethernet service.
Four parameters are configurable: the maximum profile, the GE minimum profile, the adaptive tx power, and
the ACM 1+1 mode. The parameters are available in the capacity configuration window which is show below
(click on the capacity bar on top of Pilot software main screen to open it).
A modulation and an Ethernet bandwidth correspond to each profile.

The field value GE Bandwidth depend on radio channel bandwidth, ACM profile and number of E1 used.
Bandwidth is expressed in L2 Ethernet (Ethernet frame rate out IFG and preamble).
GE Tx mute on profile below:
The minimum GE profile corresponds to the ACM profile under which the Ethernet traffic will be cut. It is This strategy ensures that:
therefore possible to adjust the parameters of Ethernet QoS based on the bandwidth corresponding to the - the system always offers the best and highest output power, leading to an improved overall link
selected minimum profile (adjustment of the metering or of the shaping of the strict priority class). budget
However, the system can still continue moving down of modulation so it can keep the other tributaries up (E1, - the right output power is always used for each modulation scheme, making sure that the
Wayside, TSL) as long as possible in case of strong radio disturbance; only the Ethernet will be cut off. performances are good for each one of them
As a trade-off, changing the output power needs some time. Therefore, the optimized working of ACM with
adaptive output power is achieved under rather slower fading events.
ACM Adaptive TX power: Also, the ETSI standard specifies that the applicable ETSI class in ACM mode must be supported by all the
ACM profiles. Because of the high max output power offered by the QPSK modulation scheme, the system
When disabled, the max output power of the radio transmitter is fixed at the max output power offered by the can only comply with the class 2 (whatever is the selected maximum profile).
highest selected modulation scheme offered within the several ACM profiles (modulation of Maximum profile).
Under channel degradation, the ACM profile is changed down as soon as a predefined threshold is crossed. When ACM Adaptive TX power is enabled, the transmit power configuration remains the same as when it is
Under channel improvement, the ACM profile is changed up as soon as a predefined threshold is crossed. disabled. The configuration is always performed for the configured Maximum profile modulation.
When changing profile, applied transmit power will be equal to the configured transmit power plus a power
increase corresponding to the difference of maximum transmit power between maximum modulation and
current modulation. This power increase depends on the ODU type and radio frequency used.
For example, with 15GHz ODU H, if the maximum profile has a modulation scheme 256QAM, and the
configured transmit power is 17dBm, the current transmit powers in the different modulations will be as
follows:
256QAM: 17 dBm
128QAM: 18 dBm
64QAM: 18 dBm
32QAM: 23 dBm
16QAM: 23 dBm
QPSK: 26 dBm
Note that the transmit power displayed on the Pilot software is always the one configured for the maximum
modulation, even if current modulation is below that.
The maximum transmit power for each modulation, ODU type, and radio frequency is available in the
performances sheets.
This strategy ensures that:
- system can face extremely fast fading events in an optimized way, making it very robust regarding any
radio phenomenon ACM mode (1+1 protection):
- applicable ETSI class (up to class 6B) allows the customer to comply with all requirements of local
radio regulators and make it easier to get radio licenses As 1+1 configuration is generally associated with non symmetrical couplers, the receive signal level of the
As a trade-off, the max output power is limited to this offered by the highest modulation and remains the same standby receiver is lower than the main receiver. So, in case of ACM, two strategies are available: maximum
for all other modulation schemes. throughput mode with lower protection, or maximum protection mode.
In 1+1 configuration, the profile to be used by the remote transmitter(s) is decided by the local equipment
according to the quality of its two received signals.
When enabled, the max output power of the radio transmitter is adapted depending on the current modulation
scheme so that it always offers the highest reachable output power. - Max throughput mode:
Under channel degradation, the ACM profile is changed down as soon as a predefined threshold is crossed. The highest profile between this allowed by the Master modem and this allowed by the Slave modem is used.
Then the output power is improved up. Therefore, if the channel quality of the Master is degraded whereas the Slave one is still good, the system
Under channel improvement, the output power is reduced as soon as a predefined threshold is crossed. Then wont move down of profile; both Master and Slave will remain at the highest profile.
the ACM profile is changed up. The system first switches without error between the reception of the Master and of the Slave before changing
of ACM profile.
This solution provides to the user an optimized using of the available channel capacity.
Exemple:
In 2+0 configurations (either XPIC or FD), three modes are available for the PDH traffic:
- Max protection mode: - All E1 on one channel:

The lowest profile between this allowed by the modem Master and this allowed by the modem Slave is used. Every PDH tributaries are carried over the same radio channel (channel 1).
Therefore, if the channel quality of the Slave is degraded whereas the Master one is still good, the system - E1 split over the two channels:
wont remain at the highest profile; both Master and Slave will move down of profile. In this mode, the PDH tributaries are split over the two radio channels. This can be relevant especially
The system first changes of profile before switching between the reception of the Master and of the Slave. in ACM mode to make the system able to use lower ACM profile and so offer a better overall link
Exemple: availability.
- E1 duplicated over the two channels:
This mode is a protected configuration for the PDH tributaries. They are all duplicated and carried over
the two radio channels. On the receive side, the system will forward the incoming radio traffic from the
receiver that offers the best performances. This mode improves the PDH availability. As a trade off,
the available Ethernet throughput is reduced.
All E1 on one channel E1 split over the two channels E1 duplicated over the two channels
Nb of E1
Channel 1 Channel 2 Channel 1 Channel 2 Channel 1 Channel 2
0 0 0 0 0 0 0
2 2 0 2 0 2 2
4 4 0 2* 2* 4 4
8 8 0 4* 4* 8 8
16 16 0 8* 8* 16 16
32 32 0 16 16 32 32
48 48 0 32 16 48 48
64 64 0 32 32 64 64
80 80 0 48 32 80 80
* E1 lost if the other channel is lost
The Ethernet traffic is split over the two channels in all modes. The available total Ethernet bandwidth depends
on the number of E1 on each channel. To compute Ethernet bandwidth, refer to the performances sheets to
1.6 - 2+0 CONFIGURATIONS find the right configuration for each channel and simply sum the values obtained for both channels.
Since the ACM feature can be used in 2+0 configurations, this means that the radio bandwidth can change
The 2+0 configuration allows the system to double its transmission capacity. dynamically and independently on the two channels. In order to guarantee an optimized using of the available
To do so, it uses two different radio channels independently. This is achieved either by using two different bandwidth at any time, the Ethernet traffic is split over the two channels based on a proprietary and patented
frequencies (2+0 Frequency Diversity) or two different polarizations at the same frequency (2+0 XPIC). 2+0 solution, ensuring the QoS and keeping the frame order.
modes are available in the protection configuration window (accessible from the protection button on the main
window of the Pilot software). Bellow is a screenshot of the window.
1.6.1 - 2+0 FD
In that case, the system uses two different frequencies: one for each of the two radio channels.
F1 / F1
Modem 1
ODU ODU Modem 1
1 1
INT INT
F2 / F2
Modem 2 ODU ODU Modem 2
2 2
1.6.2 - 2+0 XPIC

XPIC requires the use of specific modem cards including an Interference canceller ASIC (XPIC algorithm) and
uses 2 ODUs linked to a double-polarization antenna.
Modem1
ODU ODU Modem1
XPIC V V XPIC
INT5 INT5
Modem2 ODU ODU Modem2
XPIC XPIC
H H
This configuration offers therefore two radio channels using the same path and at the same
frequency. These two channels differ by the used polarization of the electromagnetic waves.
No XPIC
V
V
H
XPIC
H
Due to physical limitations (antenna cross polar discrimination, antenna alignment, radio propagation
conditions ), the two signals will interfere with each other, making it mandatory to implement a cross
polarisation interference canceller at the receiver side. Thanks to that, the receiver sensitivity performances
are equivalent to those of non XPIC modes.
This is achieved by using a specific architecture on the modem card.
1BGIGABIT ETHERNET FUNCTION 1BGIGABIT ETHERNET FUNCTION
If the radio condition requires a lower profile than the minimum configured, the GE transmission is cut on
2. GIGABIT ETHERNET FUNCTION the radio port (all frames dropped).
This chapter introduces the Gigabit Ethernet functions available in equipment. It is recommended to read this
chapter before going further into Ethernet QOS configuration. Detailed description of the configuration can be
2.3 - TOPOLOGIES
found in chapter 5.3 -)
Three main modes corresponding to different topologies can be implemented.
2.1 - INTRODUCTION 2.3.1 - 4 EPLINE mode
SLF-H embeds a full layer 2 switch with advanced QOS (Quality Of Service) features. In this mode, no tag action is performed. Frames remain unmodified, and are only transmitted to the
other side of the link. Each GE port is connected to the radio port: GE ports are PVE (Private Virtual
4 GE port are available on the front panel of each IDU. An additional internal port allows the switch to Edge). Frames can't be transmitted between two local GE ports, but only between a GE port and the
send traffic over the radio to the other side of the link. radio. However, frames can be transmitted from radio port to any GE port. For example a frame can
Several configurations allow controlling services connectivity within the switch. enter equipment on port 1, be transmitted over the link, and leave remote equipment on port 2
MEF EPLINE/EVPLINE/EPLAN and EVPLAN modes are available. (depending on the remote equipment forwarding database).
Equipment is capable of performing SVLAN tagging (push/pop/keep) according to flexible classification No Tag is added on the frames, but frames can already contain one or more VLAN tag.
criteria. QOS is only performed on the radio port in this mode. GE ports are supposed to have enough available
bandwidth to avoid making egress congestions.
4 classes of services are available to classify traffic and enforce the QOS. Metering can be used to limit
the rate of certain flows.
2.3.2 - Advanced mode
2.2 - PORTS
In advanced mode, each port (GE ports and radio port) can be involved either in EPLAN mode or
EVPLINE/EVPLAN modes. The difference between the two modes is mainly the VLAN awareness.
2.2.1 - Definition
2.3.2.1 - EPLAN mode
The "radio port" allows the radio transmission between the two terminals. Since the radio transmission
bandwidth is limited, this is the main point of congestion for the Ethernet transmission. The available
In this mode, frames can be switched to any other port configured inside the EPLAN. No tagging action
bandwidth depends on the radio configuration (modulation, radio channel bandwidth) and the number of
is performed. QOS is performed on all ports involved in the EPLAN.
optional E1 channels activated. ACM and 2+0 configurations (XPIC) also affect the available bandwidth.
GE ports are the Gigabit Ethernet transmission accesses; they can be associated with either optical
interfaces (SX or LX), or electrical interfaces (10/100/1000BaseT). 2.3.2.2 - EVPLINE/EVPLAN modes
Electrical SFP ports can handle throughputs of 10/100/1000 Mbit/s in Full or Half duplex, except for
1000 Mbit/s which must be in Full duplex. The rate and mode can be auto negotiated with the remote In this mode, frames are switched based on SVLAN Id. Each port can be involved in one or more
equipment connected to the Ethernet port. SVLAN services. Tagging action can be performed. Different ports mode are available.
UNI port mode:

2.2.2 - Jumbo frames UNI (User to Network Interface) ports are tagging points in a network. Frame which ingress the
equipment on these ports will receive an additional SVLAN tag (push tag). Frames which egress the
Equipment in its default configuration accepts frame size from 64 to 2048 bytes. If the Ethernet frames equipment on these ports will loose a tag (pop tag). Ingress frame may already contain a VLAN tag, in
received on the GE ports are larger than 2048 bytes, "Jumbo frame" mode must be configured. When this case 802.1 QinQ is performed.
jumbo frame is enabled, frame size can go up to 10000 bytes.
I_NNI port mode:
I_NNI (Internal Network to Network Interface) ports are supposed to be inside the network. Frames
2.2.3 - Available Ethernet radio bandwidth (ACM) which ingress these ports should be SVLAN tagged. Frames which egress these ports will keep existing
tag. No tagging action will be performed. Internal means the port works in trust mode, and will use the
priority bits inside SVLAN tag of ingress frames to determine QOS parameters (classification, drop
The modulation of the equipment Modem(s) can be configured into fixed or ACM (Adaptive Coding & precedence). 802.1ad PCP encoding table is used for that. Priority bits won't be rewritten in this case.
Modulation) mode.
In ACM, the operator defines the range of profiles which can be used by the modems. A profile is a E_NNI port mode:
combination of a modem coding gain and a modulation. The higher the profile is, the higher the E_NNI (External Network to Network Interface) ports are equivalent to I_NNI, except that the priority bits
modulation order is, and the lower the code strength is. The available radio bandwidth for GE traffic are not trusted, and thus redefined and rewritten when frame ingress the equipment. Except from
depends on the current profile used. priority rewrite, no tagging action will be performed.
The Ethernet bandwidth will be able to vary from a maximum value (Bandwidth GE max) to a minimal
value (Bandwidth GE min) corresponding to the maximum and minimum profiles defined for the ACM.
The interest of ACM is to offer a transmission without error for the priority traffic even in case of bad radio
conditions. This result in an increased availability for higher priority traffic compared to fixed modulation
mode. Lower priority traffic will still pass through when possible, resulting in a lower availability for this
kind of traffic.
2.4 - SERVICE QUALITY (QOS) Classification is performed on ingress side, and applied on egress side. This means for example that if a
classification is defined on port 1, frame that ingress on port 1 will be classified in the destination port TC
according to port 1 classification. Congestion handling, and priority enforcement (scheduling) will be
2.4.1 - Generalities enforced on egress side (for example on another port, or radio port, according to frame destination
address).
The transport of the Ethernet frames induces two problems which are the traffic congestion on egress
port (mainly the radio port) and the time of routing of the frames through the equipment (latency time, ie. 2.4.3 - Metering
the delay between the instant a frame is sent on one side of the link, and the instant this frame is received
on the other side).
Four classes of service are available on each port of the equipment. When congestion occurs, the priority For each classification (or flow), it's possible to measure ingress rate. A contractual limit, CIR (Committed
of different classes will allow prioritizing part of the traffic. Information Rate) can be defined.
When no congestion occurs, no frames are dropped, all frames egress the equipment as fast as possible. When metering mode is enabled, the ingress rate of each flow will be monitored. Frames in flows below
the CIR limit will be marked green. Frames in flows above the CIR limit will be marked partly green and
When congestion occurs, frame with higher priority will be transmitted first, and if possible, lower priority partly yellow (rate of green frames within flow will be equal to CIR).
frames will be transmitted if there is enough bandwidth left.
On egress side, frame color marking will influence frame drop decision in case of congestion (see
The quality of service makes it possible to allocate guaranteed rates for Ethernet flows, to support the chapters below).
priority frames in the treatment of the congestion and to reduce their latency time.
2.4.4 - Congestion handling

2.4.2 - Frames classification
The quality of services uses 4 queues on each port. These queues are known as traffic class (TC). The
2.4.4.1 - Description
four queues are named TC0, TC1, TC2, and TC3. Each TC has a different priority: Several actions are involved in the congestion handling:
- TC3: Very high priority traffic class: Strict priority
- Limitation of the output rate on port.
- TC2: High priority traffic class: Weighted Round Robin 16 - Implementation of a GE flow control (Flow Control).
- TC1: Medium priority traffic class: Weighted Round Robin 8 - Destruction (Drop) of frames (with different drop criteria).
- TC0: Low priority traffic class : Weighted Round Robin 4
2.4.4.2 - Limitation of port bandwidth
The classification (assignment of Ethernet streams to a SVLAN service and a CoS) can be performed on To be able to manage the congestion, it is necessary to limit the rate on the egress port (with a port
several types of criteria: shaping) in order to guarantee that egress frames won't be dropped after QOS enforcement point. For
the radio port, the bandwidth limit comes from the radio capacity. For GE port, limitation comes from
Accessible in Accessible in port speed configuration (or negotiation). The shaping is activated when QOS mode is enabled. When
Classification Description topology port mode QOS mode is disabled, frames will be dropped randomly in the modem queue, and no QOS will be
Classify all frames that ingress on a performed.
Port based port all UNI When QOS mode is enabled, the shaping is automatically configured by the equipment according to
Classify based on UP field of CVLAN its current configuration.
tag of ingress frames For GE ports, shaping can be disabled, or manually configured if needed. When GE port shaping is
User priority based (CVLAN EtherType must be 0x8100) all UNI disabled, or configured manually to an excessive value, no QOS can be enforced on frames that
Classify based on VLAN Id field of egress on this port. Automatic shaping mode for GE ports configure automatically the port shaping to
CVLAN tag of ingress frames the highest safe value, making sure that no frames will be dropped after the shaper, and thus ensuring
Id can be a single value or a range of QOS proper enforcement.
values
CVLAN Id based (CVLAN EtherType must be 0x8100) all UNI
Classify based on VLAN Id field of 2.4.4.3 - Flow control
SVLAN tag of ingress frames
SVLAN Id base (SVLAN EtherType can be configured) EVPLINE/EVPLAN I_NNI, E_NNI Flow control can be used to prevent loosing frames when congestion happens.
Classify based on one of each of the 8 In case of congestion, equipment will send pause frames from GE ports, to stop incoming streams.
user predefined filters which can be: When congestion is solved, incoming streams are allowed back. The congestion detection is based on
- MAC address the number of frame waiting to be handled by the radio port. When the number of waiting frame
- IP DSCP field crosses a certain threshold (before total buffering capacity is reached) pause frames are sent. A
- IP protocol second threshold (lower) ends the pause to resume transmission.
- IP addresses
For the flow control to work properly, the equipments connected to GE ports must be able to handle
User predefined - UDP/TCP ports all UNI
pause frame, and be configured to do so (the flow control is often disabled by default on network
equipments).
Each port can be configured in a given classification (but two different classifications can't be used on the Flow control will only send pause frames out of GE ports. Transmission between local and remote
same port). Default modes can be used to classify remaining frames. radio ports can't be shutdown by flow control mechanism.
2.4.4.4 - Drop of frames In the Pilot interface, to allow more flexible configurations, there is no control performed on the CIR
defined for each flows. The CIR is defined for ingress flows, but the total CIR limit is applied on egress
2.4.4.4.1 - Principe side. This makes the total CIR available dependent on the destination port, which is a dynamic
decision taken inside the switch in EPLAN/EVPLAN modes and depends on the services
When flow control is not activated, and congestion occurs, some frames must be dropped. To control configuration. It's the user responsibility to ensure that no oversubscription is made for CIR
how frames will be dropped, two mechanisms exist. reservation.
First the frames are queued in different traffic classes. Each traffic class can be independently
overflowed or not. The higher the priority of the queue is the fewer frames are dropped.
Another mechanism can be used, to control, stream by stream, on which stream the frames should be 2.4.4.4.5 - Shaping of "Very High Priority" traffic class
dropped. This is the policing function (coupled with metering). It is used mainly to avoid loosing frame If the metering is not used (disabled), the output rate of the Very High Priority queue can be limited
from all streams when one stream is exceeding its normal bandwidth. with a dedicated shaping, called TC3 shaping (or SPTC shaping). The SPTC shaping can be defined
globally for the whole IDU to disable, or as a percentage of each port bandwidth. It can also be
2.4.4.4.2 - Output queues (traffic classes) configured on a per port basis to disable, or to a percentage of port bandwidth, or to a manually set
value.
The Very High Priority queue (TC3) is of type SP (Strict Priority). This queue is served as soon as In ACM mode, for the radio port, the port bandwidth taken into account for SPTC percentage is the
there is a frame in it; if no TC3 shaping is applied. Otherwise, the queue is served has soon as highest profile bandwidth.
possible when its shaping allows it. (See below, shaping of very high priority)
The High Priority, Normal Priority, Low Priority queues are of type WRR (Weighted Round Robin). 2.5 - MAC FILTERING
The principle is that the emptying of these queues is done in turn, considering each queue weight. The
weight defines the bandwidth ratio to a given queue can take on the bandwidth available to all WRR
The Switch can drop frames according to their source or destination MAC address (black list, maximum
queues.. The weights are respectively 16, 8 and 4 for the High Priority, Normal Priority and Low
16 addresses per port).
Priority queues. For example if all WRR queues are fully loaded and that the available bandwidth for
all WRR queues is 100, the resulting bandwidth will be: The MAC addresses are independently defined for each GE.
TC2: 100 x 16 / (16 + 8 + 4) = 57.1
TC1: 100 x 8 / (16 + 8 + 4) = 28.6 2.6 - COUNTERS
TC0: 100 x 4 / (16 + 8 + 4) = 14.3
The Switch can read the statistics counters for the data passing through each port; they are classified as
transmission/reception and with/without errors and can be reset for all ports at the same time.
2.4.4.4.3 - Control of flows rate (policing)
Probes can also be defined on each classification flow, to count frame under and above the CIR limit
Drop (green and yellow frames).
The Very High Priority queue does not accept yellow frames. If a yellow frame is classified in this
queue, the frame will be dropped automatically (even if the queue is empty).
The other queues can accept both yellow and green frames. Green frames are always accepted.
Yellow frames are queued only if the destination queue is empty enough. Internally there is a
queue level threshold. If the queue level is under the threshold, yellow frames are accepted. If the
queue level is above the threshold, yellow frames are not queued (they are dropped).
In the end, the result will be that when a given TC is under congestion, yellow frames will be
dropped, and green frames will pass. When there is no congestion, all frames will pass.
Thus the green frames (coming from streams that respect their CIR) will not be dropped.
PIR
A rate higher than the CIR is allowed for flows which are not classified in the Very High Priority.
The possible maximum rate PIR (Peak Information Rate) of a flow is equal to the bandwidth of the
destination port.
2.4.4.4.4 - CIR/PIR values
In fixed modulation mode, the total CIR available is equal to the available Ethernet bandwidth on the
destination port. For GE port, the maximum CIR is equal to the PIR, which is the port bandwidth
(configured or negotiated). For radio port, if the radio capacity is in fixed modulation mode, the CIR is
also equal to the PIR, which is the available Ethernet bandwidth on the link (depending on the
configuration). For radio port if the radio capacity is in ACM mode the PIR is the bandwidth of the
highest profile, and the CIR is equal to the bandwidth of the minimum profile.
2BINSTALLATION 2BINSTALLATION
3. INSTALLATION 3.3 - IDU INSTALLATION

To install the IDU in a 19-inch rack:
3.1 - INTRODUCTION x Attach the IDU in the 19 inch rack using M6 stainless steel screws of 12 mm. This attachment
grounds the IDU to the earth.
This paragraph explains how to install and set up SLF-H radio links.
Faston socket
The main topics covered are:
x Unpacking the Equipment,
x IDU installation,
x Antenna installation,
Figure 3.1 - IDU installation
x ODU installation,
x IDU to ODU coaxial cable installation, x An additional grounding is possible by the use of a Faston plug (left side of the IDU). Use a 6 mm2
section yellow/green cable (minimum length required).
x Connecting IDU to external equipment,
Note: when more than one IDU are to be mounted in the rack, it is recommended to keep a gap of 1
x Possible installation of an E1 ports extension MUX64 SPDH shelf (optional),
unit between two IDUs.
x Powering up the system.
3.4 - ANTENNA INSTALLATION

3.2 - UNPACKING THE EQUIPMENT Three types of antenna are available for SLF-H radios:
Verify that the items received are compliant with the packing list.
x Integrated antenna with SLF-H mechanical interface (0.3 m, 0.6 m, 0.9 m, 1.2 m or 1.8 m
diameter). The ODU is directly attached on the antenna using latches. In 1+1 configuration, a
If any part of the equipment is damaged, contact Sagemcom for repair or replacement instructions.
coupler can be attached directly to the integrated antenna, the ODUs being attached in the same
way on the coupler.
The IDU, the Modem(s) card(s), the FAN card, the ODU and the MUX64 SPDH shelf are packaged in
separate boxes. x External antenna with standard rectangular waveguide interface, which is connected to the
SLF-H ODU with a flex guide.
The IDU box contains the IDU equipped or not with a TNM4 card according to the customer configuration,
a power supply cable and a CD-ROM including the user manual, performances data, cable drawings and x External dual polarized antenna (frequency diversity or XPIC configurations) connected by flex
the PilotLauncher software. guides to two ODUs.
The FAN box contains the FAN unit only. Antennas models depend on the frequency bands:
The Modem(s) box contains one or two Modems unit(s) according to the customer configuration 1+0 or x 6 GHz (6L) o 5.9 - 6.4 GHz
1+1 or 2+0. Modem(s) can either be XPIC-capable or not, according to the customer order. x 6 GHz (6H)o 6.4 - 7.1 GHz
x 7 GHz o 7.1 - 7.7 GHz
The ODU box contains the ODU only. x 8 GHz o 7.7 - 8.5 GHz
x 11 GHz o 10.7 - 11.7 GHz
The MUX64 SPDH box contains the MUX64 SPDH chassis, a power supply cable and the cable needed x 13 GHz o 12.75 - 13.25 GHz
to link it to the IDU. x 15 GHz o 14.4 - 15.35 GHz
x 18 GHz o 17.7 - 19.7 GHz
Whenever possible, save packages and shipping material, in case the equipment has to be returned. x 23 GHz o 21.2 - 23.6 GHz
x 26 GHz o 24.5 - 26.5 GHz
x 32 GHz o 31.8 - 33.4 GHz
x 38 GHz o 37 - 39.5 GHz
Alternative antennas to those specified by Sagemcom may be used, but they must meet the following 3.5 - ODU INSTALLATION
requirements:
Depending on the configuration and on the antenna type, there are several ODU mounting
x minimum gain to achieve adequate link margin, possibilities:
x radiation Pattern Envelope compliant to the network and country regulations,
x mechanical characteristics to meet specific site requirements (wind and frost resistance).
3.5.1 - 1+0 Configuration with integrated antenna
Note: with some antennas, a pressurizing system is required. It is essential to observe the The ODU is directly attached to the antenna with 4 latches. It is connected to the IDU by a single
manufacturer's recommendations: coaxial cable terminated with N connectors.
y installation and connection of a pressurizing system if the antenna is connected to the ODU
with a waveguide;
y use pressurization windows and seals to protect waveguide connections.
3.4.1 - Antenna mount

In most cases, the antenna mounts consist of tubular poles (diameter 88.9 to 114 mm).
If the antenna is installed on towers using another type of structure (e.g., square-section tower),
special mounting kits must be used for this support.
The following precautions must always be taken:

- Allow enough clearance (r10) about the alignment axis. Leave also adequate space around
the ODU to allow easy mounting/dismantling.
- Make sure that nothing obstructs the link between the two antennas, even partially.
- Install a lightning rod (Franklin) and earthing.
Note: if there is an existing lightning rod, make sure that the ODU installation site is covered
by the lightning protection cone.
Figure 3.2 - ODU SLF-H with integrated antenna
- Misalignment under extreme weather conditions must not exceed r 20 min angle in elevation
and azimuth.
Setting the polarization:

The antenna mount may be secured in different ways depending on the antenna installation site
type and environment: For antennas with a circular waveguide interface (7 GHz, 8 GHz, 32 GHz or 38 GHz), polarization
setting depends only on the ODU position. For vertical polarization, make sure that the arrow on
- Mounting pole secured to the HEA section with back-plates or clips each side of the HRA the ODU cover is vertical, for horizontal polarization, turn the ODU 90 degrees.
section.
- Mounting pole secured to a concrete base plate with threaded rods embedded in the base.
- Wall-mounted staff (attached using dowels or back-plates with threaded rods).
- Antenna mount secured directly to a tower tube (diameter 88.9 or 114 mm).
3.4.2 - Antenna Installation

Refer to the antenna manufacturer's instructions.
Vertical polarization Horizontal polarization
Figure 3.3 - Polarization setting in 1+0 configuration
If the integrated antenna has a rectangular waveguide interface (6 GHz, 11 GHz, 13 GHz,
15 GHz, 18 GHz, 23 GHz or 26 GHz), then the choice of polarization depends on the antenna
source position. Note that in this case, the large side of the waveguides, antenna side, and the
ODU must coincide.
For vertical polarization, the large side of the waveguide must be in horizontal position. ODU side,
the arrow at the back of the box must be in vertical position.
For horizontal polarization, the large side of the waveguide must be in vertical position and the
arrow on the ODU must be in horizontal position.
3.5.2 - 1+0 Configuration with pole mount and standard antenna

For standard antennas (i.e. large diameter), the ODU is mounted on a pole with a specific
mounting kit and connected to the antenna with a standard rectangular flex guide.
In this case, polarization depends on the antenna source position (vertical polarization is obtained Figure 3.5 - SLF-H 1+1 configuration with coupler and integrated antenna
when the large side of the antenna waveguide is horizontal).
Vertical polarization Horizontal polarization
Figure 3.6 - Polarization setting on 1+1 coupler
3.5.4 - 1+1 hot standby configuration with remote mounted coupler and standard
Figure 3.4 - ODU SLF-H mounted on pole
antenna
The coupler is attached on the remote mount and connected to the standard antenna by a
3.5.3 - "Hot standby" 1+1 configuration with coupler and integrated antenna rectangular flex waveguide.
The two ODUs are mounted vertically each side of the coupler, in compliance with the
In this configuration, the coupler is attached on the integrated antenna with four latches. Two instructions shown on the coupler. Each ODU is connected to its Modem with a coaxial cable.
ODUs are mounted each side of the coupler with four latches. Depending on the type of coupler, Polarization setting is done antenna side.
the ODUs are mounted differently. Refer to the instructions marked on the coupler.
It is also necessary to identify ODU cables (Main or Standby) with labels.
Each ODU is connected to its Modem by a coaxial cable.
As in most cases the coupler is not symmetrical, it is important to identify which ODU is The IDU has two Modems connected to ODUs operating at the same frequency. The standby
connected to the main position, and which ODU is connected to protection (standby) position. transmitter is configured automatically by the software in "Mute" position.
The main and standby ODU positions are indicated on the coupler.
Whatever the polarization, the coupler is always mounted in the same position (the ODUs must
be vertical).
The IDU has two Modems connected to ODUs operating at the same frequency. The standby
transmitter is configured automatically by the software in "Mute" position.
3.5.5 - 1+1 space diversity configuration with 2 antennas

3.6 - INSTALLING THE IDU TO ODU COAXIAL CABLE
This configuration is similar to "hot standby" except that the ODUs are not coupled to the same
antenna: they are located at different positions, each connected to its own antenna. Two types of cable are recommended: RG8/X (1/4") for lengths less than or equal to 70 m, and
RG8/U (3/8") for length less than or equal to 200 m. Andrew LDF4-50A cable can be used for
This configuration is possible with integrated or standard antennas. lengths up to 500 m. Other cables may be used, but must be compatible as regards outdoor use
(resistance to UV), losses, (generally, cable attenuation in its total length shouldnt go above
The IDU has two Modems connected to ODUs operating at the same frequency. The standby 18dB at 350MHz), shielding (double or triple braid) and characteristics impedance (50 Ohm, N
transmitter is configured automatically by the software in "Mute" position. male straight connectors at each end).
Only connectors recommended by the cable manufacturer should be used. These connectors
must be assembled in compliance with the manufacturer's recommendations.
3.5.6 - 1+1 frequency diversity configuration with remote mounts and dual
polarized antenna Since the Modem ODU access is a TNC type connector, an optional RG223/U Type stub cable
equipped with a 50 ohm angled male TNC connector at one end and a 50 ohm straight female N
In this configuration, each ODU is remote mounted on a pole and connected to an antenna connector at the other must be inserted between the cable connecting the ODU and the Modem;
access with a flex guide. It is important to identify the cables of the ODU mounted in vertical this cable can be ordered from Sagemcom (see Table 3-7 - Cable References for SLF-H).
polarization (main) and that mounted in horizontal polarization (protection).
Self-vulcanizing tape is wound around the connectors to make them water-tight.
The IDU has two Modems connected to ODUs operating at the two different frequencies. The two
transmitters transmit permanently. Note: cables must be installed in compliance with the national and local regulations of the
installation site.
Special precautions are necessary when installing cables to prevent possible damage by
3.5.7 - 1+1 frequency diversity configuration with 2 antennas lightning (regular grounding).
In this configuration, each ODU is connected to its own antenna. In 1+1 configuration, it is important to distinguish between the cable connected to the main ODU
and that connected to the standby ODU. If the cables are not labelled, it is necessary to perform a
This configuration is possible with integrated or standard antennas. resistance check to identify each cable.
The IDU has two Modems connected to ODUs operating at the two different frequencies. The two Disconnect the cable IDU side and short circuit the connector main ODU side (the standby ODU
transmitters transmit permanently. connector being in open circuit). Measure the resistance of the two cables IDU side using a
multimeter. The cable to be connected on the main ODU is that with the lower resistance (now
identify the cables ODU and IDU side with a label, sticker, etc.).
3.5.8 - 2+0 frequency diversity configuration with remote mounts and dual Before reconnecting the IDU cables, disconnect the short circuit ODU side. Clean the connectors
polarized antenna if necessary and connect the cables on each ODU.
In this configuration, each ODU is remote mounted on a pole and connected to an antenna Cable Grounding
access with a flex guide. It is important to identify the cables of the ODU mounted in vertical
polarization (channel 1) and that mounted in horizontal polarization (channel 2). Good lightning protection is provided by grounding the antenna cable at several points. A cable
grounding kit is available on option.
transmitters transmit permanently. The number of grounding points required mainly depends on the cable length.
Good protection is achieved with:
x A grounding kit on the cable as close as possible to the ODU
3.5.9 - 2+0 frequency diversity configuration with 2 antennas
x A grounding kit on the cable at the building entrance
In this configuration, each ODU is connected to its own antenna. x A grounding kit on the cable at the bottom of the pylon
x A grounding kit every 50 meters
This configuration is possible with integrated or standard antennas.
transmitters transmit permanently.
3.5.10 - 2+0 XPIC configuration with remote mounts and dual polarized antenna
In this configuration, each ODU is remote mounted on a pole and connected to an antenna
access with a flex guide. It is important to identify the cables of the ODU mounted in vertical
polarization (channel 1) and that mounted in horizontal polarization (channel 2).
The IDU has two Modems connected to ODUs operating at the same frequency. The two
transmitters transmit permanently.
These modules can be 1000BaseSX (multimode optical), 1000BaseLX (single-mode optical) or

3.7 - CONNECTING THE IDU TO EXTERNAL EQUIPMENT 10/100/1000BaseT (electrical)
Each Gigabit Ethernet port is configured independently: one port can be configured with an
electrical module, another with an optical module. Note that the remote terminal ports are
3.7.1 - IDU Front panel accesses configured independently from those of the local terminal.
x 2 Mbit/s optional ports "TRIB 1-8" and "TRIB 9-16" G703 44-pin DB connector: configurable by
All IDU accesses are located on the front panel:
software either in 75: coaxial mode or in 120: balanced mode. This configuration is carried out by
connector.
Interface connector for
2Mbit/s extension
x "Trib extension" port - 44-pin DB connector for connecting cable with an E1 extension MUX64
PC serial port 2Mbit/s optional accesses SPDH shelf.
Trib 1-8 Trib 9-16
x 1 or 2 "ODU" ports TNC connector: connection with the ODU.
x One ground connection (male "Faston" connector).
3.7.2 - Description of accesses and connectors

-48 V input Wayside Giga Ethernet access
channel 3.7.2.1 - "POWER" access 4-pin connector
Fans
Alarms Ethernet
Inputs/Outputs management ports
Power connection is via a 4-pin male connector with the following pinout.
Figure 3.7 - Front panel of the SLF-H IDU in 1+0 configuration
Modem 2
Green Power Led To ODU2
Pin Signal name Meaning

1 -48V A -48 V DC
To ODU1 2 GND A Ground
On/off switch
Modem 1 3 GND B Ground
4 -48V B -48 V DC
Figure 3.8 - Front panel of the SLF-H IDU in 1+1 configuration Table 3-1 - 4-pin "POWER" connector pinout
Note: in 1+1 Hot Stand By configuration, since asymmetric couplers are used, the ODU 1 will be the 3.7.2.2 - The connector pinout is as follows:
main ODU and the ODU 2 will be the standby ODU.
x "POWER" access 4-pin connector: -48 V power supply input (voltage between -39 VDC and
-59 VDC), 9 6
x "Serial" (PC) access 9-pin DB connector: serial management access for connection to a PC. This 1 2 3 5
access is used to consult or change the IP address of the Ethernet Mgmt ports and the equipment
virtual IP address.
Ground
x "Alarms IN/OUT" access high density 15-pin DB connector: includes the 5 external alarm inputs Output
and the 3 programmable relay outputs.
Input
x Four Ethernet ports RJ 45 connectors:
x 1 "Protect" port reserved for future external IDU protection. Figure 3.9 - "Serial" connector pinout
x 1 "Wayside" 10/100BaseT port: auxiliary channel.
x 2 x 10/100BaseT ports dedicated to network management "Mgmt1" and "Mgmt2". 3.7.2.3 - "Alarms in/out" access High density 15-pin DB connector
x Four Gigabit Ethernet ports "GbE1", "GbE2", "GbE3", "GbE4: these ports receive optical SFP This connector allows access to:
(LC/PC connector) or electrical (RJ45 connector) modules.
x 3 configurable relay outputs: these alarms are managed by the Pilot software. The electrical Pin Signal Description
interface for each relay is given below:
6 RELAY 3C Relay #3 Common
7 RELAY 3NO Relay #3 Normally Open
Normally Open 8 RELAY 2NC Relay #2 Normally Closed

9 GND Ground
10 RELAY 1NC Relay #1 Normally Closed
Normally Closed 11 RELAY 3NC Relay #3 Normally Closed
Common 12 RELAY 2C Relay #2 Common

Figure 3.10 - Relay output electrical interface 14 RELAY 1C Relay #1 Common

The 3 relay contacts are available. These contacts can be assigned either to internal alarms of
the equipment, external alarms, or a combination of the two. Table 3-2 - "Alarm IN/OUT" connector pinout
The alarm state corresponds to the relay in standby position (normally closed).
x 5 external alarms (inputs)
Open : no alarm if con figu red in nor ma l position (N)

3.7.2.4 - "Mgmt" and "Wayside" Ethernet ports
Closed: alarm if confifgure d in normal position (N)
S LF-H
RJ 45 connectors are used for Ethernet type signals.
Open : alarm if config ured in in vert position (I)
Closed: No a larm if configured in invert po sition (I)
The ports "Mgmt1" and "Mgmt2" are part of an internal hub, and can be connected to the Ethernet port
10 k : of the PC, to another IDU or to an SNMP manager.
EXT IN
Ph otocoup ler
The 3 connectors have the same pinout (Ethernet standard):

GND
5 e xternal inputs
-48V
Figure 3.11 - External alarm electrical interface

Pin I/O Name Meaning
The alarm connector pinout is given below. 1 I RXETHP Receive Ethernet + wire
2 I RXETHN Receive Ethernet - wire
5
1 3 O TXETHP Transmit Ethernet + wire
4 - NC Not Connected
6 O TXETHN Transmit Ethernet - wire
10 6
15 11 8 - NC Not Connected
Table 3-3 - Ethernet port pinout
Each connector has two Leds:

Pin Signal Description - a green Led on the left: indicates Ethernet signal activity at the input. If this Led is not lit permanently,
1 EXT IN1 External alarm input #1 it means that the cable is not correctly connected to the port, or that the equipment connected to the
SLF-H does not work.
2 EXT IN2 External alarm input #2 - an orange Led on the right: indicates a 100BaseT transmission (10BaseT when the Led is off).
3 EXT IN3 External alarm input #3
4 EXT IN4 External alarm input #4
5 EXT IN5 External alarm input #5 3.7.2.5 - Gigabit Ethernet ports "GbE1" to "GbE4"
The IDU has four Gigabit Ethernet interfaces on the front panel.
1
These ports can receive: 15
- SFP optical modules (Small Form Factor Pluggable Transceiver MultiSource Agreement 14 Sept
2000).
Interfaces SX LX
30 16
Interface Multimode Single-mode 44 31
Standard IEEE 802.3z IEEE 802.3z
Wavelength 770 - 860 nm 1270 1355 nm Pin N Channel Name Meaning
16 GND Ground
1250 Mbit/s 1250 Mbit/s
Speed 31 TRIB_IN_01N Tributary input No. 1 negative polarity
100 ppm 100 ppm 1 TRIB_IN_01P Tributary input No. 1 positive polarity
1
Transmitted power 17 TRIB_OUT_01N Tributary output No. 1 negative polarity
32 TRIB_OUT_01P Tributary output No. 1 positive polarity
10 m fibre - -11 dBm min
2 TRIB_IN_02N Tributary input No. 2 negative polarity
50 m fibre -9.5 dBm min -11.5 dBm min
18 TRIB_IN_02P Tributary input No. 2 positive polarity
62.5 m fibre -9.5 dBm min -11.5 dBm min 2
33 TRIB_OUT_02N Tributary output No. 2 negative polarity
-10 3 TRIB_OUT_02P Tributary output No. 2 positive polarity
Sensitivity at 10 -17 dBm -19 dBm
Max. permitted 34 TRIB_IN_03P Tributary input No. 3 positive polarity
0 dBm -3 dBm 3
power 4 TRIB_OUT_03N Tributary output No. 3 negative polarity
Typical range 35 TRIB_IN_04N Tributary input No. 4 negative polarity
10 m fibre - 5000 m min 5 TRIB_IN_04P Tributary input No. 4 positive polarity
50 m fibre 500 m min 550 m min 4
62.5 m fibre 220 m min 550 m min 36 TRIB_OUT_04P Tributary output No. 4 positive polarity
Connector LC/PC LC/PC 22 TRIB_IN_05P Tributary input No. 5 positive polarity
5
Table 3-4 - Characteristics of the Gigabit Ethernet optical interface
6
- SFP electrical modules with the following characteristics: 8 TRIB_OUT_06N Tributary output No. 6 negative polarity
Speed 10, 100, or 1000 Mbit/s 39 TRIB_IN_07N Tributary input No. 7 negative polarity
Standard IEEE 802.3 9 TRIB_IN_07P Tributary input No. 7 positive polarity
7
Maximum cable attenuation 100 m UTP or STP Category 5 Gigabit Ethernet compatible 40 TRIB_OUT_07P Tributary output No. 7 positive polarity
Connector RJ45 26 TRIB_IN_08P Tributary input No. 8 positive polarity
8
A "GbE Lnk/Act" Led corresponds to each port: 11 TRIB_OUT_08P Tributary output No. 8 positive polarity
27 Not cabled
Led off: link down 42 Not cabled
Green Led lit permanently: link up 12 Not cabled
Green Led flashing: traffic indicator, flashes for each GE frame 28 Not cabled
43 GND Ground
Orange Led lit: collision 13 GND Ground
29 GND Ground
44 GND Ground
3.7.2.6 - G703 2 Mbit/s ports - 44-pin DB connectors 14 GND Ground
30 GND Ground
The 16 x 2 Mbit/s ports are available on the two 44-pin DB connectors. 15 GND Ground
These interfaces are designed to operate in 120 Ohm balanced or 75 Ohm unbalanced. To operate in Table 3-5 - TRIB 1-8 connector pinout
75 Ohm, the signals corresponding to the negative polarities (- wire) are connected to the ground by the
connector of the cable.
The pinout of the 44-pin DB connectors is given below (view of the IDU front panel).
3.7.3 - Cable references for SLF-H

Pin N Channel Name Meaning
16 GND Ground The cables which may be connected to the IDU front panel are listed below:
9
2 Mbit/s cable
32 TRIB_OUT_09P Tributary output No. 9 positive polarity (Balanced or unbalanced)
2 TRIB_IN_10N Tributary input No. 10 negative polarity (12 to 17) To distribution
18 TRIB_IN_10P Tributary input No. 10 positive polarity panel
10
3 TRIB_OUT_10P Tributary output No. 10 positive polarity Vers PC
19 TRIB_IN_11N Tributary input No. 11 negative polarity 2
11
12
13
37 TRIB_OUT_13N Tributary output No. 13 negative polarity Optical fiber (8 to 11)
7 TRIB_OUT_13P Tributary output No. 13 positive polarity or Ethernet cable (5)
To -48 V
23 TRIB_IN_14N Tributary input No. 14 negative polarity power supply 1 6 To customer To ODU
38 TRIB_IN_14P Tributary input No. 14 positive polarity Ethernet
14
8 TRIB_OUT_14N Tributary output No. 14 negative polarity To management network or IDU ODU cable (7)
24 TRIB_OUT_14P Tributary output No. 14 positive polarity other equipment
management access
To distribution To auxiliary Ethernet
9 TRIB_IN_15P Tributary input No. 15 positive polarity panel Straight or crossed RJ45
15 Ethernet cables (3 or 4)
Figure 3.12 - Cables for a terminal station
16
27 GND Ground A relay station consists of two terminals connected "back to back". Typical wiring of this configuration is given
42 GND Ground below:
12 GND Ground
28 GND Ground
43 GND Ground
13 GND Ground
29 GND Ground
44 GND Ground
2 Mbit/s channel transfer 18
14 GND Ground
30 GND Ground
15 GND Ground
Table 3-6 - TRIB 9-16 connector pinout

Optical fiber or Giga Ethernet cable
Ethernet crossed or straight cables
Figure 3.13 - Cables for a relay station
Figure N Drawing No Designation Length Sagem code 3.7.4 - Module references for SLF-H
2.5 m 253245103
1 3000335369 - Power cable (1 power supply) 5m 253245124
12 m 253245132
25 m 253245145 Designation Sagemcom P/N
2.5 m 253132640
1 3000319349 - Power cable with redundancy 5m 253132658 SFP Module GE SX 253 108 813
12 m 253132806 SFP Module GE LX 253 108 826
25 m 253132819
2 3000364085 - 9-pin sub-D serial cable (PC) 1.5 m 55670223 GE Electrical SFP Module
253 108 834
3m 55670224 (10/100/1000BaseT)
3 - Crossed ETHERNET cable 1.5 m 55671323
(NMI/NMI transfer or management) 3m 55671324
4 - ETHERNET straight cable 1.5 m 55671321
(NMI/NMI transfer or management) 3m 55671322 Table 3-8 - SFP module references for SLF-H
2.5 m
5 - GIGA ETHERNET straight cable 5m Off-the-shelf
(for electrical SFP module) 12 m cable
25 m 3.8 - MUX64 SPDH UNIT (OPTIONAL)
2.5 m 252867400
6 3000279379 - Alarm cable to distribution panel 5m 252577720
(DB15HD) 12 m 252867413
25 m 252577738 Interface connector for
7 3000281884 - IDU-ODU cable TNC angled male/N straight female 1m 252890368 2Mbit/s extension 2Mbit/s optional accesses
2.5 m 251559377 Faston socket TRIB 17-32 TRIB 33-48 TRIB 49-64 TRIB 65-80
8 251559356EA - Singe-mode optical jumper 5m 251559504
LC-PC/LC-PC 10 m 251559517
20 m 251559567
2.5 m 251454262
9 251454275EA - Singe-mode optical jumper 5m 251454283
LC-PC/SC-PC 10 m 251454296
20 m 251454410 Green Power Led
2.5 m 251616049 Secured
10 251615886EA - Multimode optical jumper 5m 251616060 -48 V input
LC-PC/LC-PC 10 m 251616078
20 m 251616099 Figure 3.14 - Front panel of MUX64 SPDH Unit
2.5 m 252064934
11 252064893EA - Multimode optical jumper 5m 252064947
LC-PC/SC-PC 10 m 252064955
20 m 252064989 A MUX64 SPDH shelf, allowing an extension up to 64 E1 2 Mbit/s ports can be installed in same rack as the
2.5 m 252867083 IDU. This shelf will increase the total number of physical E1 ports to 80.
12 3000279375 - Half 2 Mbit/s tributary120 : In/Out cable 5m 252867096
DB44HD 12 m 252867306 This 0.75U-height unit will be installed above the IDU. It's mandatory to have 1U margin between the IDU-H
25 m 252867314 and the SPDH
2.5 m 252867327
13 3000279376 - 2 Mbit/s tributary 75 : In/Out cable 5m 252867335 Attach the MUX64 SPDH shelf in the rack using M6 stainless steel screws of 12 mm. This attachment grounds
DB44HD BNC-F 12 m 252867348
the shelf to the earth.
25 m 252867356
2.5 m 252867369 2
14 3000279377 - 2 Mbit/s tributary 75 : In/Out cable 5m 252867377 An additional grounding is possible by the use of a Faston plug (left side of the shelf). Use a 6 mm section
DB44HD BNC-M 12 m 252867380 yellow/green cable (minimum length required).
25 m 252867398
2.5 m 253051829 The MUX64 SPDH unit will be connected to the IDU by a cable that interconnects the 2 Mbit/s extension
15 3000301874 - 2 Mbit/s tributary 75 : In/Out cable 5m 253021238 connector of each equipment.
DB44-1,6/5,6 6F-5M 12 m 253021832
25 m 253051840 The MUX64 SPDH shelf has its own secured -48V power input.
2.5 m 253051853 The same power supply must be used for both the IDU and the SPDH MUX64.
16 3000301875 - 2 Mbit/s tributary 75 : In/Out cable 5m 253021241
DB44-1,6/5,6 6M-5M 12 m 253021861
25 m 253051874
2.5 m 253051882
17 3000301877 - 2 Mbit/s tributary 75 : In/Out cable 5m 253021262
DB44 LIBRE-5M 12 m 253021902
25 m 253051915
18 3000279382 - Crossed 2 Mbit/s transfer cable 2.5 m 252867877
19 3000325442 - Cable DB44HD MUX64 0.30 m 253179789
Table 3-7 - Cable References for SLF-H
3.8.1 - Front panel accesses of MUX 64 SPDH shelf

1 GND Ground
x "POWER" access 4-pin connector: secured -48 V power supply input (voltage between -39 VDC
21 E1_ET1N_Gx Tributary input No. 1 negative polarity
and -59 VDC),
2 E1_ET1P_Gx Tributary input No. 1 positive polarity
1
x "Trib extension" port - 44-pin DB connector for connecting cable with the IDU. 22 E1_ST1N_Gx Tributary output No. 1 negative polarity
3 E1_ST1P_Gx Tributary output No. 1 positive polarity
x 2Mbit/s optional ports "TRIB 17-32", "TRIB 33-48", "TRIB 49-64" and "TRIB 65-80" G703 23 E1_ET2N_Gx Tributary input No. 2 negative polarity
78 pin DB connector: configurable by software either in 75: coaxial mode or in 120: balanced 4 E1_ET2P_Gx Tributary input No. 2 positive polarity
2
mode. This configuration is carried out by connector. 24 E1_ST2N_Gx Tributary output No. 2 negative polarity
x One ground connection (male "Faston" connector). 25 E1_ET3N_Gx Tributary input No. 3 negative polarity
3
26 E1_ST3N_Gx Tributary output No. 3 negative polarity
3.8.2 - Description of accesses and connectors 27 E1_ET4N_Gx Tributary input No. 4 negative polarity
4
3.8.2.1 - "POWER" access 4-pin connector 28 E1_ST4N_Gx Tributary output No. 4 negative polarity
This access is identical to the "POWER" access of the IDU (refer to 3.7.2.1 -) 10 E1_ET5P_Gx Tributary input No. 5 positive polarity
5
3.8.2.2 - G703 2 Mbit/s ports - 78-pin DB connectors 12 E1_ET6P_Gx Tributary input No. 6 positive polarity
6
The 64 x 2 Mbit/s ports are distributed on four 78-pin DB connectors. 33 E1_ET7N_Gx Tributary input No. 7 negative polarity
These interfaces are designed to operate in 120 Ohm balanced or 75 Ohm unbalanced. To operate in 7
75 Ohm, the signals corresponding to the negative polarities (- wire) are connected to the ground by the 15 E1_ST7P_Gx Tributary output No. 7 positive polarity
connector of the cable. 35 E1_ET8N_Gx Tributary input No. 8 negative polarity
8
The pinout of the 78-pin DB connectors is given below (view of the front panel). 17 E1_ST8P_Gx Tributary output No. 8 positive polarity
37 Not cabled
18 Not cabled
38 Not cabled
20 1 19 Not cabled
39 Not cabled
20 Not cabled
39 21
59 40
78 60
3.8.4 - Cable References for MUX64 SPDH shelf

40 GND Ground
60 E1_ET9N_Gx Tributary input No. 9 negative polarity Drawing N Designation Length Sagemcom code
9 2.5 m 253245103
42 E1_ST9P_Gx Tributary output No. 9 positive polarity 3000335369 - Power cable (1 power supply) 5m 253245124
62 E1_ET10N_Gx Tributary input No. 10 negative polarity 12 m 253245132
43 E1_ET10P_Gx Tributary input No. 10 positive polarity 25 m 253245145
10 2.5 m 253132640
44 E1_ST10P_Gx Tributary output No. 10 positive polarity 3000319349 - DC Power cable with redundancy 5m 253132658
11 25 m 253132819
46 E1_ST11P_Gx Tributary output No. 11 positive polarity 2.5 m 253133048
66 E1_ET12N_Gx Tributary input No. 12 negative polarity 3000319350 -2 Mbit/s tributary 120 In/Out cable 5m 253133069
12 DB78HD (1/2 cord) 12 m 253133072
48 E1_ST12P_Gx Tributary output No. 12 positive polarity 25 m 253133093
68 E1_ET13N_Gx Tributary input No. 13 negative polarity 2.5 m 253133100
13 3000319351 - 2 Mbit/s tributary 75 In/Out cable 5m 253133113
50 E1_ST13P_Gx Tributary output No. 13 positive polarity DB78HD BNC-F 12 m 253133121
14 2.5 m 253133142
52 E1_ST14P_Gx Tributary output No. 14 positive polarity 3000319352 - 2 Mbit/s tributary 75 In/Out cable 5m 253133155
72 E1_ET15N_Gx Tributary input No. 15 negative polarity DB78HD BNC-M 12 m 253133163
53 E1_ET15P_Gx Tributary input No. 15 positive polarity 25 m 253133176
15
54 E1_ST15P_Gx Tributary output No. 15 positive polarity 2.5m 253133184
74 E1_ET16N_Gx Tributary input No. 16 negative polarity 3000319353 - CORD2Mb TRIB 75 IN/OUT 5m 253133209
45 E1_ET16P_Gx Tributary input No. 16 positive polarity DB78HD-1,6/5,6F 12m 253133217
16
56 E1_ST16P_Gx Tributary output No. 16 positive polarity 25m 253133259
76 Not cabled 2.5m 253133262
57 Not cabled 3000319354 - CORD2Mb TRIB 75 IN/OUT 5m 253133283
77 Not cabled DB78HD-1,6/5,6M 12m 253133291
58 Not cabled 25m 253133311
78 Not cabled
59 Not cabled 2.5m 253133332
3000319355 - CORD2Mb TRIB 75 IN/OUT 5m 253133345
DB78HD LIBRE 12m 253133353
Table 3-9 - TRIB16E1 connector pinout for the MUX64 SPDH unit 25m 253133366
3000325442 - CORD DB44HD MUX64 0.30m 253179789
Note: "Gx" represents one of the four connectors of the MUX64 SPDH shelf, the pinout being identical for Table 3-10 - Cable References for MUX64 SPDH unit
each one.
G1: TRIBs 17 to 32
G2: TRIBs 33 to 48
G3: TRIBs 49 to 64
G4: TRIBs 65 to 80
3.8.3 - MUX32 SPDH version

An under-equipped version of the SPDH unit exists.
It provides up to 32 E1 2 Mbps/s interfaces, located on the TRIB 17-32 and TRIB 33-48 connectors.
TRIB 49-64 and TRIB 65-80 connectors are not available.
2BINSTALLATION
3.9 - POWERING UP THE SYSTEM

Before powering up the terminal, check that:
x the equipment has not been damaged during installation

x the equipment has been assembled correctly
x in 1+1 each Modem is connected to the corresponding ODU
x the antenna polarization is correct
x the IDUs, ODUs, MUX64 SPDH and connecting cables have been grounded
Modem 2
Green Power Led To ODU2
To ODU1
DC Power ln On/Off switch
Modem 1 Fans
Figure 3.15 - SLF-H 1+1 IDU
x the power supply voltage is within the range: -39 V to -59 V (-48 V nominal). Measure the
voltage (polarity and amplitude) on the cable plug before plugging it in the IDU. Only
negative DC voltage must be used.
x check in the same way the power supply connector connected to the MUX64 SPDH shelf
(polarities given in Table 3-1).
x make sure that these two power cable come from the same power supply
On the assumption of a MUX64 SPDH shelf, carry out in the order the following operations:
x connect the Trib extension connectors of IDU and MUX64 SPDH shelf using the
specific cable,
x plug the power supply cable to the MUX64 SPDH shelf,
x plug the power supply cable to the IDU,
x the green PWR Led on the front panel of the MUX64 SPDH shelf should be lit,
x if the terminal is a 1+0 system, switch on the terminal by setting the switch on the Modem
to ON. If the terminal is a 1+1 system, set the switch on the second Modem to ON as
well,
x the green Power Led(s) on the front panel(s) of the Modem(s) should be lit,
x measure voltage at the input of each terminal and record the values on the
Commissioning Form at the end of paragraph 4,
x measure voltage at the input of the MUX64 SPDH shelf and record the values on the
Commissioning Form at the end of paragraph 4.
3BCOMMISSIONING CONFIGURATION AND TESTS 3BCOMMISSIONING CONFIGURATION AND TESTS
Validate, the following window appears:

4. COMMISSIONING CONFIGURATION AND TESTS
4.1 - INTRODUCTION
This paragraph describes a preliminary configuration of a SLF-H, its commissioning and how to verify
correct operation after installation.
The equipment is commissioned and operated from a PC equipped with VT100 emulation and the
Pilot Software.
Configuration required
The minimum configuration proposed for the operating PC is as follows:

x OS: Windows XP, Windows Vista, or Windows 7
x Pentium 4 or equivalent, frequency: 1 GHz minimum
x RAM: 256 Mbytes (2 Gbytes for Vista)
x 300 Mbytes available on hard disk
x CD-ROM drive
x 10/100BaseT Ethernet port
x Serial port (or USB port + external USB/series adapter)
x SVGA screen, minimum resolution 600 x 800 (minimum 16 colours)
x Windows hyperterminal
x Pilot software To select a command, type the command number in the text zone Choice? and press ENTER to
validate.
4.2 - CONFIGURING EQUIPMENT IP ADDRESSES Choice 1: Configuration of the equipment IP address
Connect the IDU serial port to a serial port on the PC with an RS-232 cable.
Run Windows HyperTerminal: "Start/Programs/Accessories/Communications/HyperTerminal".
Enter a name in the window which is displayed (e.g. SLF-H), choose an icon for the connection then
validate.
In the next window choose the PC "COM" port which is connected to the equipment then validate.
In the next window, set the following parameters:

x Bits per second: 19200
x Data bits: 8
x Parity: none
x Stop bits: 1
x Flow control: none
Validate the settings and save the connection (Save command in the application File menu). The next
time you run Hyperterminal, simply choose the connection icon to connect to the equipment. The default IP address is 192.168.001.002.
Enter the required IP address, keeping in mind that it must be different from that of the other
Note: by default, the password is empty on first commissioning. equipment addresses and must be defined in a subnet different from that of the Ethernet interface.
The IP address of the remote equipment will belong to the same network.
Example: if the IP address of the local equipment is 192.168.113.141 the remote equipment IP
address should be 192.168.113.xxx with xxx not equal to 141.
You are prompted to reboot the equipment. You can reboot later, without affecting the traffic, after The IP address of the Ethernet interface for the equipment connected to the
entering the settings. management PC must belong to the same network and have the same subnet mask as
the PC IP address.
Error message "Equipment address is mandatory": you must enter the equipment address The IP address of the Ethernet interface for the remote equipment must belong to a
different network.
Example: management equipment address: 135.010.115.015 with a subnet mask of

Choice 2: Default gateway configuration 255.255.255.0
The PC address must be 135.010.115.xxx with xxx not equal to 0, 255 or 015.
The address of the remote equipment must belong to another network, e.g.
10.142.113.150.
These management Ethernet interfaces are available on the equipment accesses "Mgmt1" and
"Mgmt2".
You are prompted to reboot the equipment. You may reboot later, without affecting the traffic, after entering
the settings.
Choice 4: REBOOT the equipment

This command reboots the application immediately, restarting with the settings already stored in the
equipment.
Reboot takes place without affecting the traffic.
The default Gateway IP address is 000.000.000.000.
You are prompted to reboot the equipment. You can reboot later, without affecting the traffic, after
entering the settings. Choice 5: Logout
Setting finished, this command closes the current session.
The session is closed automatically after several minutes with no activity (delay configurable from the
manager).
Choice 3: Ethernet interface configuration
Choice 6: Ping
"IP Address": choice of IP address of the equipment you want to reach.

Return delay in ms.
Note: the Ping command is used to check the accessibility and return path from the remote equipment,
The Ethernet interface characteristics are displayed and can be modified: testing both the interface address and the equipment address. If the address of the port sending
the Ping command is different from the equipment address, two commands are transmitted.
"Interface State": use of the interface: 0 (Interface off) or 1 (Interface on).
"IP Address"
"Subnet mask"
"Route Protocol": 0 (None), 1 (RIP) or 2 (OSPF)
Choice 7: Trace route 4.3 - PILOT SOFTWARE AND IP CONNECTIVITY
4.3.1 - Installing the software Pilot Launcher

The Pilot Launcher allows to automatically run a version of the Pilot software compatible with the
software version of the IDU selected by its IP address.
It also allows you to view the record of the equipment (in French or English) according to the IDU
selected.
Note that it is not necessary to separately install the Pilot Software if pilot launcher is installed (chapter
4.3.2 -)
Insert the Pilot Launcher software CD-ROM into the drive. The installation software runs automatically
if the drive has been configured in "Autorun" mode.
Otherwise, run Windows explorer and double click on "setup.exe".
Once the software is installed, double click on the Pilot icon

"IP Address": choice of IP address of the equipment you want to reach.
The following window appears:
The screen displays the management routes already defined with their characteristics:
Hops: 1, 2, 3 Path to move from one machine to another.
IP Equipment address
1 2 3
Available and recognized

Equipment
Unavailable Equipment
IP address: IP address of the recipient (equipment or subnet).
Delay (ms): return time.
Unit. size: maximum size of the IP packet that can reach the remote equipment.
Choice 8: Factory settings
This command is used to restore the default factory settings.
Note: this command is only available from release R1.2.
These settings will also be applied on the remote equipment, making sure that:
- the IP address of the remote equipment is in the same network as that of the local equipment (not
mandatory but recommended),
- the IP address of the Ethernet interface for the remote equipment does not belong to the same
network as that of the local equipment.
The principle of equipment IP addressing is described in 6.6.1 -. Depending on the software release,
the routing tables may be static (R1.1) or dynamic (R1.2 and higher). In this case, the RIP and OSPF
protocols can be implemented in order to simplify network management configuration.
Choice 9: Default configuration of ODUs mute
This menu allows to configure the default mode for ODUs mute (mute On or Off when a new ODU is
connected).
4.3.2 - Installing the Pilot software 4.3.3 - IP connectivity

The Pilot allows the user to: Connect an RJ45 Ethernet cable between access "Mgmt1" or "Mgmt2" of the local IDU and the
x View local and remote terminal configurations management network.
x Set and change parameters on local and remote terminals Before starting a Pilot session, check the connectivity between the PC and the local IDU.
x Monitor RSL, BER and alarms
Check that the IP address of the management PC belongs to the same network as that of the local
x Download and activate a new software version IDU Ethernet interface, then check the connectivity with a ping of the IDU Ethernet address from the
Windows DOS command prompt.
x Perform installation and maintenance operations
x Configure the network management interface Declare the route to reach the local IDU equipment IP address, then check the connectivity by pinging
this address.
Insert the Pilot software CD-ROM into the drive. The installation software runs automatically if the
drive has been configured in "Autorun" mode.
Otherwise, run Windows explorer and double click on "setup.exe".
Once the software is installed, double click on the Pilot icon
The following window appears:
The Pilot software is specific to this version of SLF-H and is not compatible with the
previous versions.
4.3.4 - Launch Auto Pilot with the Pilot Launcher: 4.3.5 - Starting a Pilot session
After checking the connectivity, start a Pilot session from the Session/Open session menu.
The local IDU address is entered in the following window.
Double click on the address of the
IDU to start the session of the Pilot,
the Pilot's main screen appears in
default mode "View only".
The button "Add SLF Host" Allows to

add an IP address in the list of
equipment
Click on Add to enter the local IDU address.
Click on OK
The button "French" allows to edit the user

manual in French in pdf format
The button "English" allows to edit the user

manual in English in pdf format
The button "Measurements" allows to edit the

Measurement tables (Ethernet throughput and Double click on the IDU address to start the Pilot session; by default, the main Pilot screen is displayed in
latency, RSL thresholds, transmit power) "View Only" mode.
Click here to login

IDU Equipment IP address
View Only: read only mode

In this example, the equipment is neither receiving signal (RSL < -90) nor transmitting (mute ON).
Click on the "Login" button to enter the default password: "2345" for a "Super User" level.
This screen will display the local terminal parameters on the left of the screen and the remote terminal
4.4 - LINK PRELIMINARY CONFIGURATION parameters on the right when the link is established.
The radio channel, modulation, capacity, Ethernet bandwidth are displayed at the top of the screen.
The confirm/cancel modification request is also displayed in this bar: "Confirm" or "Cancel".
4.4.1 - Setting the parameters of each IDU
The IDU part of the screen is used to define the site name, configuration type, link ID code and to
The preliminary configuration of each IDU must be carried out separately at each end of the link. Once display generic alarms, bit error rate (BER) and packet error rate (PER) for a given counting period
the link is established, virtually all the parameters can be checked from the local terminal. (1 min, 15 min or 24 h).
The Channel 1 part indicates the received signal level and the reception BER; it is used to configure
The parameters of the local and remote terminals must be compatible.
the transmit frequency and transmit power values, ATPC activation and Mute function. In ACM
In order of priority, the first essential parameters to configure before establishing the link are for each
modulation, the current modulation will be indicated, those of the top bar being the max modulation of
IDU are:
operation and the modulation from which there is no more GigaEthernet transmission.
x channel transmit frequency,
The equipment Leds and the 3 programmable relays status are also displayed on the Pilot. In addition,
x modulation type, radio channel and capacity (E1 number), the "Shelf view" button is used to display the front panel of the equipment managed.
x link ID code, If you are logged on as a "Super User", you can change the terminal configuration with the buttons.
Each button provides access to a specific parameter. Note that only one change at a time is allowed.
x transmit power; the Automatic Transmit Power Control (ATPC) function must be inhibited at this
stage ("OFF" position on the Pilot screen). With the transmitter still in "Mute" and the ATPC "OFF", configure the following parameters:
Note: when powering up for the first time (factory output setting), the transmitter is in "MUTE" position, x Channel transmit frequency
in order to avoid transmitting signals at a frequency which could disturb neighbouring links.
The transmitter should be kept in mute position until the transmit frequency, modulation and capacity Move the cursor along the Tx Freq rule or click on the left or right button, then validate by
are properly configured. clicking on "Confirm" in the top toolbar.
Use the arrows to change the frequency in steps of 250 kHz.
When the link is not established, the Pilot screen indicates "NO REMOTE RADIO" or "No open
session" on the right side of the screen (see after).
x Modulation, radio channel and capacity parameters
Click on the top bar
(the displayed bandwidth is the Ethernet bandwidth level 2).
The following screen is displayed:
For ACM Modulation, the buttons Maximum Profile Table 4-1 - Configuration compatibility
Ge Tx mute on profile below allows user to have a choice of up to 9 profiles:
Please note that when switch configuration in ACM mode, by default the maximum and
minimum profiles will be set to the lowest value (0) which is QPSK modulation.
Choose the parameters according to the choices available for the link (following table) then
validate with "Apply".
Bellow is a list of available capacities that can be configured in fixed and ACM mode:
same frequency which could disturb the receiver. Link ID Codes of the local and remote
terminals must be the same. This code consists of a number from 1 to 255 chosen by the
customer.
x Transmit power
x The transmitter's "Mute" position is set to "OFF".

Adjust the transmit power value as planned in the design calculation, keeping ATPC "OFF".
Move the cursor along the Tx Power rule , or click on the left
or right button, then validate.
Use the arrows to change the power in steps of 0.5 dB. Moving the cursor in the middle
changes the power in steps of 2.5 dB.
Important: to avoid saturating the transmitter, the Pilot software automatically prevents
power values greater than the maximum allowed for the current modulation. Refer to the
values in APPENDIX 1 Transmission characteristics.
The local terminal is now correctly configured. Repeat the procedure for the remote terminal in order
to establish the link.
If by mistake, the remote equipment is muted (mute ON) but the rest of the configuration is properly
applied on both sides (frequency, modulation, radio channel, capacity), it is possible to remove the
mute on remote equipment. (See below screenshot).
Command to issue mute remove request

Numbers indicated in the green cells correspond to the profile number.
* If installation of a MUX64 SPDH shelf.
Table 4-2 - Configuration compatibility
The available capacities may vary according to Modem software licenses. Please refer to
chapter 6.26 -.
The available capacities also depend on the ODUs connected to Modem boards. Please refer to
ODU specifications in Appendix 1 at the end of this document.
x Link ID
Indication that remote equipment

might be muted
4.4.2 - Antenna alignment

The link ID code is used to avoid demodulating data from another neighbouring link using the
Antenna alignment is performed with both terminals operating, in normal weather conditions. The Bad alignment
received signal level (RSL) can be checked using the voltage available on the ODU BNC
connector. Figure 4.2 - Antenna alignment
A typical curve of RSL voltage against RSL at ODU input is given below. The RSL voltage is
directly proportional to the RSL expressed in dBm. The expected RSL was determined during the link budget calculation. This level depends on the
power of the remote terminal, the frequency, the antennas gain and the hop length.
RSL voltage
Antenna alignment is carried out on each antenna using the following procedure:
5V 1- Check that the remote terminal transmitter is on, with the planned parameters (frequency,
power, speed, modulation). Check that the ATCP is off and that the remote terminal power is
4.5 V
such that the RSL does not exceed 20 dBm.
4V 2- Remove the cap on the ODU BNC connector and connect a voltmeter.
3- Slowly rotate the antenna in the azimuth direction (horizontal) and find the maximum voltage.
If the voltage is around 4.5 V, reduce the remote transmit power to avoid saturation.
3V
4- Slowly rotate the antenna in the elevation direction (vertical) and find the maximum voltage.
Record the measured voltage.
5- When the maximum voltage has been found, tighten all the bolts. Check that the voltage has
2V not changed after tightening. Replace the protective cap on the BNC connector.
6- Compare the RSL obtained with the expected RSL. If the difference between the two values
exceeds 5 dB, readjust antenna alignment and polarization setting and check that there are
no obstacles on the radio path.
1V
0.5 V
RSL In principle, if the parameters have been entered correctly and if the antennas have been aligned
(ODU input) correctly, the link should be established (no screen with "NO REMOTE RADIO" message) and
the main Pilot screen should display the remote terminal parameters.
-90 dBm -80 dBm -70 dBm -60 dBm -50 dBm -40 dBm -30 dBm -20 dBm
In 1+0 and 1+1 configuration, the typical screens are as follows:
Figure 4.1 - SLF-H ODU RSL voltage
Note: RSL is measured at ODU antenna port. For 1+1 configurations involving a coupler, the
coupler losses must be taken into account to determine the RSL at antenna access.
Optimum alignment is achieved when main antenna lobe is aligned with the remote antenna.
During alignment, it is important to distinguish between the main lobe and the side lobes by
rotating the antenna around the maximum RSL value. Note that there is around 25 dB difference
between side lobes and main lobes (i.e. about 1.5 V on the RSL voltage).
Good alignment Receive signal levels should be similar on both ends of the link (with the same transmit power).
Figure 4.3 - Main Pilot Screen for a 1+0 configuration Fixed modulation
Note: if the parameters of the two terminals are correct, and if the main Pilot screen displays "NO
REMOTE RADIO", the antennas will probably have to be realigned. Check troubleshooting
guide for other potential issues.
Figure 4.4 - Main Pilot Screen for a 1+0 configuration ACM modulation
Figure 4.6 - Main Pilot Screen for a 1+1 configuration ACM modulation
The screens 1+1 display the master channel, the active transmitter and the percentage of use of
master and slave Modems. Note that in 1+1 FD, both transmitters are active at the same time, and
thus not active Tx information is displayed.
The channel 2, symbol "M" not greyed, is

the master channel.
The channel 1, symbol "M" greyed, is the

slave channel.
The channel 2, symbol "Tx" not greyed, is

the active channel in emission.
The channel 1, symbol "Tx" greyed, is the

inactive channel in emission (on mute).
Figure 4.5 - Main Pilot Screen for a 1+1 configuration Fixed modulation
The use rate of channel 1 in reception is
5%.
The use rate of channel 2 in reception is

95%.
Note: there may still be some alarms at this stage.

In case of "GE" or "tributary" alarm, check the access configuration and connections.
If there are other alarms, or if the link does not work, refer to the troubleshooting paragraph ( 7 in this
manual).
Note any discrepancies in the Commissioning Form at the end of paragraph 4.
4.4.3 - Antenna alignment in XPIC mode

This section describes the installation and commissioning procedure for a system in which the XPIC feature
is installed in a Co-Channel Dual Polarization configuration.
1. Install the dual polarization antenna and point it in the direction of the other site.
2. Install the two ODUs on a dual polarization antenna using appropriate mounting kit and mark
the ODUs with V and H respectively.
3. Install two cables between the ODUs and the Modems. Note that the cable length difference
should not exceed 10 meters.
4. Mark the cables with V and H respectively and make sure that V is connected to the right
Modem and H is connected to the left Modem. Mark the Modems respectively.
5. Power up V channel on both ends of the link and configure it to the desired frequency channel,
and maximum power.
6. Align the antennas, one at a time, until expected RSL is achieved. Make sure achieved RSL is
no more than 5dB from the expected level.
Note: there may still be some alarms at this stage.
Polarization alignment is required in order to verify that the antenna feeds are adjusted, ensuring that the
antenna XPD (Cross Polarization Discrimination) is achieved. In case of "GE" or "tributary" alarm, check the access configuration and connections.
If there are other alarms, or if the link does not work, refer to the troubleshooting paragraph ( 7 in this
Polarization adjustment should be done on one antenna only. manual).
Note any discrepancies in the Commissioning Form at the end of paragraph 4.
7. Disconnect the V cable from the V ODU and connect it to the H ODU.
8. Check the RSL achieved in the H ODU and compare it to the RSL achieved by the V ODU.
9. Verify that the XPI (Cross Polarization Interference) is at least 25dB whereby:
XPI=RSLPOL - RSLXPOL
With :
RSLPOL = received level with the same polarization used at both sites
RSLXPOL = received level with orthogonal polarizations used at both sites
10. If the XPI is less than 25dB, adjust the feed polarization by opening the polarization screw and
gently rotating the feed to minimize the RSLXPOL.
Bellow is a screenshot of the Pilot software main window in XPIC mode.
4.5 - TESTS AND MEASUREMENTS REQUIRED The following tolerances must be taken into account:
x 2 dB for the transmit power.
After installing and setting the link, check correct operation by performing the following tests and x 1 dB for the gain of each antenna.
measurements: x 3 dB for the received level measurement displayed on the Pilot.
x 0.5 dB for 1+1 coupler losses.
x Frequency Scan at ODU input
x Received Signal Level We see that in the worst case, for a 1+0 type system, the maximum uncertainty is 7 dB (2 1 1 3):
x Gigabit Ethernet transmission test In practice, the typical uncertainty to be considered is 5 dB.
x 2 Mbit/s channel test (optional)
So, if the difference between the receive level displayed by the Pilot and the receive level expected by
x Wayside access test (optional)
the link budget calculation is within the tolerance 5 dB, the installation is considered to be correct.
x Alarm In/Out test (optional)
x 1+1 switching check (optional) A difference of more than 5 dB, however, indicates a problem such as incorrect antenna alignment, a
x BER measurement propagation problem or bad polarization on one of the two antennas.
First check the antenna alignment and polarization. If the problem remains, refer to the
Measurement equipment required: troubleshooting guide in paragraph 7 and replace the defective element.
x Gigabit Ethernet tester Record the ODU RSL values of the link on the commissioning form.
x 2 Mbit/s bit error rate analyzer (optional)
x Digital multimeter
A SLF-H Commissioning Form is provided at the end of paragraph 4 in order to record the results of 4.5.3 - Giga Ethernet transmission test
the tests carried out together with any remarks made during installation and commissioning.
This test is carried out to check for correct transmission of Gigabit Ethernet signals.
The test must be carried out on each port used.
4.5.1 - Frequency Scan It is used to test Ethernet transmission over the entire link.
The Pilot software can be used to take an automatic measurement of the spectrum around the receive A Gigabit Ethernet tester is required to take the measurement. The measurement block diagram is
frequency without the need for external instruments. The measurement must be taken locally, given below:
successively at each end of the link.
Measurement is carried out with the local transmitter off (the Pilot software automatically sets the local - Test setup used with SFP optics (using a single tester and a loop TX / RX on the remote site):
transmitter to "mute", to avoid sending signals which could disturb other receivers.
After acquisition, the spectrum is displayed graphically. This measurement reveals the presence of
any interferers. A record of this measurement is stored in the IDU flash memory and can be consulted
afterwards using the Pilot or via the network management.
In order to check interferer level at the received frequency, the remote transmitter must be switched off
during the test.
The "Frequency scan" procedure is described in 6.24 -.
Note in the commissioning form the presence of any interferers at the received frequency as well as
on the adjacent channels (first adjacent and second adjacent).
Important: do not run a frequency scan from a remote site.
Tx / Rx loopback
4.5.2 - Receive signal level (in case of optical port)
Under normal weather conditions, the receive signal level depends on the following parameters: Gigabit Ethernet
x Remote Transmit Power. tester
x Local and remote antenna gains.

x Free space path attenuation depending on hop length and frequency.
The Gigabit Ethernet tester is connected to a GE port of the local terminal. On the remote terminal, the
x Coupling and connection losses for a 1+1 system. corresponding GE output is looped back on the input by a fiber of optical interface.
Compare the actual received signal level displayed on the main screen of the Pilot software, with the
expected signal level: - Test setup used with SFP optical or electrical (use a tester locally and on the remote site):
Gigabit Ethernet Gigabit Ethernet

tester tester
The Gigabit Ethernet TX tester is connected on a GE port local terminal. On the remote terminal is
connected the output GE corresponding to the input of the tester RX.
The test consists in measuring the throughput according to RFC 2544 for long enough to check the
quality of the link.
The test will be declared positive is no packets are lost and if the throughput measured is not less than
the limit specified. This limit depends mainly on the configuration: modulation, radio band and number
of associated optional E1s. (Refer to the performance datasheets to obtain the Ethernet bandwidth On the local IDU:
available according to the link configuration).
The tester must be connected to the GE port to be tested. It is configured as follows:
Choice of transmission configuration x Number of Gigabit Ethernet ports to be considered: 1

The Ethernet tester is connected to GE port #n of the IDU under test, where n = 1, 2, 3
x Define the configuration for each end of the link: modulation, radio channel, number of active or 4.
E1 tributaries (optional). GE port #n of the IDU must be configured in "Enable" mode.
Configure the tester so that it takes into account the type of SFP module installed on the
IDU: electrical or optical. If the operator uses optical SFP modules, auto negotiation
must be activated on the tester.
x Define a Unicast flow to be transmitted:

Define the size of this flow. Standard RFC2544 recommends the following sizes: 64,
128, 256, 512, 1024, 1280, 1518 bytes. SLF-H also supports frame sizes from 64 to
2048 bytes. Choose one of these sizes.
x Define the test duration.
x The throughput defined by standard RFC2544 characterizes the maximum data rate that
can be transmitted without losses. This parameter depends on the transmission
configuration and the associated Ethernet features (e.g. QoS).
x Define a throughput (generally called ILOAD on an Ethernet tester) less than or equal to
the throughput specified for the configuration defined.
On the remote IDU:
x Make the physical loopback on GE port #n of the remote equipment.
Choice of Ethernet configuration: 4.5.4 - 2 Mbit/s tributary test (optional)
x Configure each Ethernet port of the equipment as follows: These tests must be carried out on both terminals of the link. A 2 Mbit/s transmission analyzer is
required, which must be set with the following parameters:
QoS mode: "Disable".
Jumbo frame mode: "Disable". x BER test
Port mode: "Enable" for port #n being tested (local and remote equipment). x 2 Mbit/s
Configure the interface according to the SFP module type. x Internal clock
x PRBS: 215-1.
x 120 Ohm balanced, or 75 Ohm unbalanced interface depending on IDU configuration.
All channels designed to transport traffic must be tested one by one:
x Click on one of the "TRIB" connectors Shelf view or use the menu
"Configuration / E1 Tributaries / Local".
x Check that the channel under test is configured in normal mode (N), in service (blank
button) and no loopback (blank button).
x All other tributaries should be unconnected and configured as inverted (I).
x Check that there are no SFP alarms (GE Leds green).
x There should be a "tributary" alarm, the "Trib" Led of the equipment and its image on the
Pilot screen must be red.
x Connect the transmission analyzer to the 2 Mbit/s input, respecting the impedance selected
in the IDU. The tributary alarm should now be cleared.
x Click on the "Loopback" button corresponding to the tributary under test. Select a remote
loopback. See procedure in 5.4 -.
x Check on the transmission analyzer that no errors occurred for one minute.
x When the test is finished, disconnect the cable, change the alarm in invert mode (I) and
remove the remote loopback.
x Repeat this test on each 2 Mbit/s channel used on the site.

x Launch the tester script (frame loss test): check that no frames are lost.
x Record the results on the commissioning form.
x Check that there are no Wayside alarms on the equipment (Wayside Led green,
4.5.5 - Wayside test (optional) Alarms / View / Local). On the screenshot below, Wayside alarm is present.
The same procedure is used to test the Wayside port and the main Gigabit Ethernet ports.
A 10/100BaseT Ethernet tester is required to perform this test. As when testing the GE ports, make a
physical loopback on the remote terminal RJ45 access by connecting pins 1 and 3 together and 2 and
6 together.
The test consists in checking that the transmission has no losses on this access at the specified
throughput.
Note: the throughout is the same irrespective of the configuration (modulation / radio channel).
Tester configuration:
x Number of Ethernet ports to be considered: 1.

x Configure the tester in 10/100 Mbps auto negotiated mode.
x Define a unicast flow of size n bytes. (64 n 1760).
x Depending on the size of the Ethernet frame to be transmitted, define an ILOAD less than
or equal to the specified throughput in the following table:
Frame size
64 128 256 512 1024 1280 1518 1760
Throughput
1.25 1.05 0.96 0.96 0.96 0.95 0.96 0.96
(Mbps)
Configuration common to local and remote equipment:
Check that the Wayside port is "on" (box checked, when Wayside is selected under Port Id) on both
IDUs (Configuration / Management Network / Ethernet Ports and Radio Channel menu).
x Start the test (frame loss): check that no frames are lost.
4.5.6 - Alarm relay test (optional)

SLF-H can manage 5 local external alarms and 5 remote external alarms (image of the 5 external
alarms of the remote IDU).
If some external alarms are to be managed, it is necessary first to configure them (see 5.6 -).
SLF-H includes 3 fully programmable relay outputs. Internal or external alarms can be assigned to
each relay.
If alarm relays and/or external alarm inputs are used on the site, the tests described below must be
carried out to check correct operation.
These tests must be carried out on each terminal. Before starting the tests, check that no faults are
displayed by the equipment.
It is not possible to simulate all possible alarms without opening the equipment: for example,
simulating a Tx frequency alarm would require opening the ODU and disturbing the transmission
synthesizer phase loop.
However some alarms can be simulated simply, without having to carry out any operations on the
equipment.
4.5.6.1 - Simulating an IDU Alarm

An IDU alarm can be easily simulated by entering a wrong Link ID code in the local terminal. This
wrong ID Code generates an IDU alarm, but does not affect the radio transmission. Apply the following
procedure:
x Switch "On" the local ODU mute (the link with the remote ODU must be cut).
x Change the Link ID Code of the local terminal. 4.5.6.7 - Testing the alarm outputs (relays)
x Switch "Off" the local ODU mute; an IDU alarm should be displayed: front panel "idu" Led,
and its representation on the Pilot screen must be red. A multimeter is required for this test, to check continuity between the relay contacts.
Once the test is finished, do not forget to put back the correct Link ID code using the same procedure. The 3 contacts of each relay are available on the 15-pin DB connector (see Figure 3.10 and Figure
3.11, Table 3-2 - "Alarm IN/OUT" connector pinout).
4.5.6.2 - Simulating an ODU Alarm
When the IDU is not powered, NC is connected to the common point of the relay.
An ODU alarm can be generated by removing the cable to the ODU.
When the IDU is powered and when there is no alarm:
The equipment "ODU" Led and its image on the Pilot screen must be red. x NO is connected to common
x NC is in open circuit
4.5.6.3 - Simulating a Gigabit Ethernet Alarm
When the IDU is powered up and there is an alarm on the relay under test:
Two alarms can be easily obtained: x NC is connected to Common
x NO is in open circuit
Take the SFP module out of its housing: an "SFP Presence" alarm is triggered; the equipment "GbE
Lnk/Act" Led goes out, the "GE" Led of the Pilot screen and the "SFP Presence" Led in the alarm Simulate various alarms and test the operation of the relays as explained above.
detail becomes red.
Put back the SFP module without plugging the Ethernet cable: an "SFP LOS" alarm is triggered; the 4.5.7 - Testing 1+1 configuration (optional)
equipment "GbE Lnk/Act" Led stays out, the "GE" Led of the Pilot screen and the "SFP LOS" Led in
the alarm detail becomes red. 1+1 systems require additional tests compared with unprotected systems. These tests are carried out
to check that all parts are operational and that the switching system operates correctly.
4.5.6.4 - Simulating a tributary alarm These tests must be carried out on both ends of the link and require the presence of personnel in each
station.
A tributary alarm is easily obtained by changing the configuration from normal (N) to invert (I), or vice
versa.
The equipment "trib" Led and its image on the Pilot screen must be red. In Hot Stand By mode or in Space Diversity mode, only one transmitter is active, the other is in
position "Mute". In Frequency Diversity mode, the two transmitters operate permanently, transmitting
When the test is finished, do not forget to restore the initial configuration.
at two different frequencies, and only the receivers are switched.
4.5.6.5 - Simulating an RSL alarm In 1+1 Hot Stand By configuration, since asymmetric couplers are used (6 dB), the activation of
Revertive automatic switching Tx allows, when channel 1 is restored, to have a better system gain
First check that the ATPC is OFF. assessment (weaker coupler losses in emission and reception).
An RSL alarm can be simulated by reducing the remote terminal power and choosing a suitable RSL
alarm threshold, e.g. -60 dBm. In the figures below, the active transmitter and receiver are written in bold.
Decrease the remote transmit power in order to have a receive level below -60 dBm. Take care not to
drop below the link operating threshold, since the link cannot be restored from the local terminal. When the link is in operation and there are no faults, the configuration is as follows:
The equipment "RSL" Led and its image on the Pilot screen must be red. (note: L = local, R= remote).
When the test is finished, do not forget to restore the initial settings.
4.5.6.6 - Testing an external alarm M 1 (L) M 1 (R)

Tx 1 (L) Tx 1 (R)
To simulate a custom alarm, use the Pilot menu Configuration / Alarms / Local - IDU tab. Rx 1 (L) Rx 1 (R)
Depending on the alarm convention, select "N" if a closed loop corresponds to the alarm state, or "I" if
an open loop corresponds to the alarm state.
In order to test a specific external alarm, first disable all other external alarms. M 2 (L) M 2 (R)
Tx 2 (L) Tx 2 (R)
Rx 2 (L) Rx 2 (R)
Identify the pin of the 15-pin DB connector corresponding to the alarm input. Assuming that the alarm
is in "N" configuration, connect this pin to ground and observe the changes on the front panel of the
IDU and on the Pilot screens.
Figure 4.7 - Local transmitter 1 and local receiver 1 active
The "ext" Led on the IDU front panel and its image on the Pilot screen must be red.
Check that the alarm disappears when the pin is disconnected from the ground.
From the local terminal, connect a BER analyzer on one of the 2 Mbit/s channels and make a remote
loopback for this channel (see procedure in section 5.4 -). If there is no E1 installed, make a Gigabit 4.5.8 - Quality measurement
Ethernet test (as specified in paragraph 4.5.3 -). Check that there are no errors (or no frame loss) for
at least a minute (nominal RSL conditions, ATPC OFF). The link quality can either be measured on a Gigabit Ethernet port or on one or more chained E1 ports
(if the option is installed).
From the local terminal, in "Super User" mode, select menu "Maintenance/Tx/Rx Forcing" or click on
"Tx" on the main screen to access the manual switching command (refer to 6.22 -). Since the bit error rates on the Gigabit Ethernet train and on the E1s are the same, it is simpler to carry
out this test on an E1 tributary
Select the channel 2 receiver by clicking on the Rx2 box, and validate.
The test is either carried out with the arrangement as described in paragraph 4.5.3 - or that described in
paragraph 4.5.4 -.
M 1 (L) M 1 (R)
For a 1+1 link, only the quality on the main ODUs in automatic switching mode will be tested.
Tx 1 (L) Tx 1 (R)
Rx 1 (L) Rx 1 (R) The duration of the BER test depends on the type of network and the criticality of the links.
Generally:
M 2 (L) M 2 (R) x 30 minutes for low capacity links (GSM, Wifi, etc.),
Tx 2 (L) Tx 2 (R) x 24 hours for medium and high capacity links.
Rx 2 (L) Rx 2 (R)
Other durations could be considered upon request, but this will require Sagemcom approval.
Figure 4.8 - Local transmitter1 and local receiver 2 active
4.5.9 - Recording configuration information

Switching between receivers should be error free. There should be no transmission errors for at least
a minute. The configuration information can be recorded by the Pilot into files. These files must be attached to
the commissioning form
From the local terminal, in the same menu, select the channel 2 transmitter by clicking on the Tx2 box.
Link configuration information
A transmit switching causes errors (or frame losses). The number of errors counted by the analyzer
should be less than 2,048106 (maximum time of switching equal to 1s). Open the "File/System Report" menu, the following screen is displayed:
M 1 (L) M 1 (R)
Tx 1 (L) Tx 1 (R)
Rx 1 (L) Rx 1 (R)
M2 (L) M 2 (R)
Tx 2 (L) Tx 2 (R)
Rx 2 (L) Rx 2 (R)
Figure 4.9 - Local transmitter 2 and local receiver 2 active
Clear the counter and check that in this configuration, the transmission is carried out without error.
Select again automatic switching by clicking on the "Tx Auto" and "Rx Auto" boxes.
If Revertive automatic switching Tx is on, the system should return to the channel 1 transmitter.
Note: transmit switching will cause errors.
If Revertive automatic switching Tx is off, the system will remain on the channel 2; no error will be
displayed.
The system is now in automatic mode, the orange maintenance Led is off.
Use the same procedure from the remote terminal.
Check all the boxes and click on "Save As".

Save the file in the PC using a name indicating the local site and the remote site:
"[local site name] [remote site name].txt".

SLF-H
This text file contains information used to configure the local and remote sites, as well as information Page 1/3
regarding the hardware and software versions (serial numbers, manufacturing date, versions, etc.). To Commissioning Form
print the file, click on "Print".
Customer:
Saving local and remote terminal configurations
Link name:
The configurations can be saved in files on the PC. If the IDU or the ODU is replaced, these files can
be used to reload the configuration quickly.
Date:
To configurations are saved via the menu: "File/IDU Configuration/Local or Remote/Save".
Chose a file name indicating the names of the sites on the two ends of the link, e.g.: Configuration 1+0
1+1 HSB 1+1 SD 1+1 FD
"[local site name] [remote site name].sav", for the local terminal. 2+0 FD 2+0 XPIC
MUX64 SPDH MUX32 SPDH
"[remote site name] [local site name].sav", for the remote terminal.
Modulation Fixed ACM MaxProfile GE Tx Mute Profile
Configurations are loaded via the menu: File/IDU Configuration/Local or Remote/Load. QPSK QPSK low QPSK low
16QAM Mode if in 1+1: QPSK high QPSK high
32QAM Max throughput 16QAM 16QAM
64QAM Max protection 32QAM 32QAM
128QAM 64QAM 64QAM
256QAM 128QAM 128QAM
256QAM low 256QAM low
Radio channel
256QAM med 256QAM med
Optional E1s active 256QAM hgh 256QAM high
7 MHz 14 MHz 28 MHz 56 MHz
0 2 4 8 16 32 48 64 80
Mode if in 2+0: All E1 on one channel split E1 protected E1
For the configuration compatibility see Table 4-2
Giga Ethernet interfaces GE1 SX optical LX optical Electrical

Auto 10 Mbps 100 Mbps 1000 Mbps
Half Duplex Full Duplex
GE2 SX optical LX optical Electrical
Local site Remote site

Name: Name:
Antenna type: Antenna type:
IDU to ODU cable length: IDU to ODU cable length:
Transmit frequency: Transmit frequency:
SLF-H
SLF-H Page 3/3
Page 2/3 Commissioning Form
Commissioning Form
Attached electronic documents

TEST RESULTS
Diskette CD-ROM Other
Local site Remote site
Reference(s):
IDU Input voltage: VDC IDU Input voltage: VDC
MUX64 Input voltage: VDC MUX64 Input voltage: VDC
File retrieved via the "File/System Report/Save As" menu
RSL at ODU access (dBm) RSL at ODU access (dBm) File retrieved via the "File/IDU Configuration/Local /Save" menu
Measured Expected Difference Measured Expected Difference File retrieved via the "File/IDU Configuration/Remote/Save" menu
Channel 1 Channel 1 BER measurement file
Channel 2 Channel 2
Other:
(If in XPIC mode) (If in XPIC mode)
Channel 1 V H Channel 1 V H Notes
Channel 2 V H Channel 2 V H
Measured XPI* : dB Measured XPI* : dB
Measured on Channel 1 2 Measured on Channel 1 2

*XPI=RSLPOL - RSLXPOL *XPI=RSLPOL - RSLXPOL
Giga Ethernet tests: OK NOK Giga Ethernet tests: OK NOK

2Mbit/s tributary tests *: OK NOK 2Mbit/s tributary tests *: OK NOK
Alarms / loops *: OK NOK Alarms / loops *: OK NOK
Wayside *: OK NOK Wayside *: OK NOK
1+1 configuration *: OK NOK 1+1 configuration *: OK NOK
Giga Ethernet quality test
Duration:
OK NOK
Number of frame losses :
2 Mbit/s tributary quality tests *
Duration:
OK NOK
Number of Errors:
(*) Optional
4BFINAL LINK CONFIGURATION 4BFINAL LINK CONFIGURATION
5. FINAL LINK CONFIGURATION 5.3 - CONFIGURING GIGABIT ETHERNET
SLF-H can be used to transmit Ethernet frames simultaneously or not with 2 Mbit/s tributaries.
Once the link is established, the configuration must be finalized via the Pilot, still in "Super User"
mode. The following parameters must still be entered: The principle for transmission of Ethernet frames and the specific functions that can be associated
with them are described in 2. It is strongly recommended to read this chapter before using the
advanced Ethernet configuration capabilities.
x Useful information stored in the IDU memory, e.g. site names and some information which it
could be useful to consult or load later.
x Gigabit Ethernet access configuration. 5.3.1 - Notations used in this manual
x 2 Mbit/s access configuration.
x BER and RSL alarm thresholds. In this document, the front panel Ethernet ports (SFP slots) will be referred to as GE1, GE2, GE3
and GE4 ports. The radio port allowing transmission to remote equipment will be referred to as GER
x Configuration of local or external alarms, their severity, relays. or Radio port.
x Commissioning if necessary and configuration of Automatic Transmit Power Control (ATPC).
x 1+1 Switching configuration. Ethernet bandwidth can be stated L1 or L2. This refers to OSI layers. At L2 (layer 2), each frame is
composed of source address, destination address, EtherType field, and CRC field. At L1 (layer 1)
each frame is composed of the L2 frame, plus a preamble, and a minimum silence period must be
5.1 - ENTERING SITE NAMES ensured between two frames (IFG, Inter Frame Gap). These additional fields represent 20 bytes.
The bandwidth used for port speed is L1 bandwidth (10M, 100M, or 1000M). For a given frame size,
Enter the site names of the two terminals in "Site Name". the L2 corresponding bandwidth can be computed this way:
L2band = L1band * (frame size) / (frame size + 20)
Since IFG and preamble are remote by line interfaces, switch component only deal with L2
bandwidth. In this document and in the Pilot software, each bandwidth, unless specified, correspond
to a L2 bandwidth.
4 classes of service are available on each port. Very High priority is the SP (Strict priority) class,
High priority is the WRR (Weighted round robin) 16 class, Normal priority is the WRR 8 class, and
Low priority is WRR 4 class.
5.3.2 - Ethernet Port configuration
The first step in configuring Ethernet is to setup Ethernet port. The port configuration window can be
found in the Pilot menu here:
Configuration->Gigabit Ethernet->Ethernet port configuration->local/remote
5.2 - SETTING THE DATE AND TIME
Click at the bottom left of the Pilot main screen to display the following screen:
The date of local and remote equipment can be modified.

Click on "Synchronize" then "Apply" to transfer PC date and time to the equipments, independently
for the local and remote terminals or for both at the same time.
By applying the automatic value on a port, the equipment ensures that in any case, the QOS will be
enforced on this egress port. The drawback is that for larger frames than 64 bytes, not all the L1
bandwidth will be used. For example with 1500 bytes frames, the L1 maximum bandwidth will be
77.1Mbps. Equipment also take into account additional SVLAN tag that might be added to frames,
according to configuration.
To avoid facing this limitation, if needed, the port shaping of each port can be configured.
The following port shaping modes are available:

- Automatic:
in this mode, QOS is enforced on the target port, and shaping value is automatically
computed.
- Disabled:
In this mode, no shaping is applied. Full L1 bandwidth can be used at any time, but QOS
is not enforced on egress side of the target port
- Manual:
In this mode, a value can be entered (in 100kbps unit) to define the L2 shaping applied on
the port. Take care to set a value lower than the automatic value if QOS must be
5.3.2.1 - Physical configuration enforced.
For Each port (1 to 4), the SFP type must be configured (either Copper, or Fiber LX, or Fiber SX). By default the shaping is mode is automatic, if in doubt, leave the configuration to default.
Each port can be configured as disabled. Disabled ports will not link up, and thus will not carry any
traffic. Unused ports should be disabled to prevent eavesdrop issues. On radio port, port shaping is automatically applied, and can be improved with adaptive shaping
feature (see chapter 5.3.3 -).
For electrical SFP, auto-negotiation mode can be either enabled or disabled. If auto-negotiation is
disabled, it is possible to configure port speed and duplex mode. In addition to port shaping, a SPTC (Strict Priority Traffic Class) shaping may be applied. This
shaping limits the rate of traffic passing through the Very High priority queue (other queues are not
affected).
The SPTC shaping can be either configured globally (see chapter 5.3.3 -) or per port. If
configuration is per port, a SPTC shaping may be defined for each port (GE ports and Radio port)
For 1000Mbps speed, only full duplex mode is available.

The Ethernet port Configuration must be coherent between the two sides of Ethernet
Cable. If SLF port is in auto negotiation configuration, the equipment connected to
SLF must be in auto negotiation too. The same applies to a forced mode.
The following SPTC modes are available:

5.3.2.2 - Advanced configuration - Disable:
No SPTC shaping is applied. Traffic on Very High priority queue will not be limited (except
Additional configuration is available for Ethernet ports.
by port shaping if any).
To enforce QOS in EPLAN and EVPLAN configuration (see chapter 5.3.4 -), a shaping must be
- Absolute:
applied to each port. If no shaping is applied on the port, and congestion occurs on egress pipeline
An absolute value should be entered (in 100kbps unit) to limit the bandwidth of Very High
of this port, frame will be dropped randomly (no QOS is applied). If no congestion occurs on the
priority queue.
port, the shaping is not useful.
- Relative:
The bandwidth limitation for GE ports is the physical L1 bandwidth. Shaping is enforced in the
In this mode, a percentage of the port shaping will be taken as the Very High priority
switch (at L2). When automatic mode is selected, the L2 shaping must be computed based on the
queue bandwidth limit. For example if port shaping is 76.1Mbps, and 10% is entered,
worst case of L2 to L1 bandwidth conversion. The worst case corresponds to the smallest frames. In
SPTC shaping will be 7.6Mbps. If no port shaping is applied (port shaping mode set to
this case, the L2 bandwidth is:
disable), the percentage is applied on the L1 port speed. For example if port speed is
L2bandwidth = L1bandwidth * 64/84 100Mbps, and the percentage is set to 10%, the SPTC shaping will be 10Mbps.
So, for example, with a 100Mbps port speed, the automatic shaping value will be 76.1Mbps.
defined) the L1 port speed. The resulting SP TC value can de different from one port to
the other if port shaping is not the same.
5.3.3 - QOS Global configuration If set to "Per port", the global configuration is ignored, and the configuration defined for
each port is applied. (note that in other modes, port configuration is ignored). See chapter
5.3.2.2 -for details.
The QOS global configuration window can be found in the Pilot menu here:
Configuration->Gigabit Ethernet->Advanced configuration->Global QOS configuration->local/remote
5.3.4 - QOS & services configuration
When QOS mode is set to "Enable", Access to the QOS and services configuration window is
granted. The window can be found in the Pilot menu here:
Configuration->Gigabit Ethernet->Advanced configuration->QOS and Services configuration-
>local/remote
Below is a screenshot of the window in the default equipment configuration:
- QOS mode:
While QOS Mode is set to "Disable", no shaping is performed on any port. No QOS is
enforced on any port (including radio port). And mode is equivalent to 4 EPLINE. This
means that frame that ingress on a local port will be sent to the radio port, and frames that
ingress from the radio port can be sent to any GE port (according to FDB) or flooded.
If QOS mode is set to "Enable", Radio port shaping is enforced, and QOS & services
configuration window is available for QOS configuration. Note that it is strongly
recommended to check QOS and services configuration if QOS is enabled (see chapter
5.3.4 -).
It is recommended to set this parameter to "Enable".

- Adaptive shaping:
When QOS mode is set to enable, adaptive shaping mode might be set to "Enable".
Adaptive shaping feature enhances radio port shaping automatic configuration (it takes
into account the statistical size of frames in shaping calculation). This result in a higher
available bandwidth over the radio port. The drawback is a slight delay on the
transmission, making the latency a little bit higher.
It is recommended to set this parameter to "Enable" since it allows gaining some Mbps of
bandwidth and the latency increase is nearly nothing (less than 1s typical).
- Jumbo frame mode:
When jumbo frame mode is set to "Disable", switch can transmit frames size comprise
between 64 and 2048 bytes.
When jumbo frame mode is set to "Enable", switch can transmit frame size comprise
between 64 and 10000 bytes. Between two local ports (no using the radio) frame size with
jumbo mode can go up to 10256.
- SPTC shaping:
This setting allow to configure globally for all ports the shaping applied to Strict Priority
(Very High) queue. This shaping limits the bandwidth available to services in Strict Priority.
If set to "Disable", no SPTC shaping is applied on any port (no bandwidth limitation).
If set to "All ports", a relative SPTC shaping is applied to all ports. The SPTC shaping
value is based on the percentage configured in "SP TC Shaping Value" field. The
bandwidth limitation is the percentage of the port L2 shaping or (if no port shaping is
The top part of the window (Service type/metering ) is global equipment configuration.
The middle part of the window is port modes and port shaping and speed. 5.3.4.1.1 - 4 EPLINE mode
The bottom part is services/classifications configuration. In this mode, switching can only be performed to/from the radio port.
Frames that ingress on GE ports are sent to the radio port. Frames that ingress from the radio port
5.3.4.1 - Service types can be switched to any GE ports, according to the FDB, or flooded to all GE ports. Thus it is
possible to establish a communication between GE port 1 of local equipment and GE port 3 of
Service type defines the network (or topology) behavior of the embedded switch. Two main modes remote equipment. But two local GE ports can't exchange frames.
are available, 4 EPLINE and advanced. In advanced mode, ports can be involved either in EPLAN No tagging action can be performed in this mode. Though Ingress frames can contain one (or more)
or EVPLINE/EVPLAN mode. The configuration can be made from the "QOS and Services VLAN tags. This is equivalent to all ports being configured as UNI, internally using SVLAN service 1.
configuration window", as shown in the following screenshot.
Main mode selection QOS is only performed on the Radio port. No QOS is performed on GE ports. Thus classification
can only be defined for GE ports (see chapter 5.3.4.4 - for classification description). No port
shaping and no SPTC shaping is applied on GE ports (even if SPTC shaping is configured in Pilot
software). Only Radio port is port shaped and can be SPTC shaped.
5.3.4.1.2 - Advanced mode
Advanced mode gives access to EPLAN, EVPLINE and EVPLAN configurations.

If a port is assigned to EPLAN, it can't be used for EVPLINE/EVPLAN, and a port assigned to
EVPLINE/EVPLAN can't be used for EPLAN. A port is assigned to a given mode as soon as a
service is created in the relevant tab (see screenshots in following sections).
5.3.4.1.3 - EPLAN
In EPLAN mode, frames can be switched between all ports involved in this mode, including
switching between two local GE ports. QOS is performed on all ports (Radio port and GE ports).
No tagging action can be performed in this mode. Though Ingress frames can contain one (or more)
VLAN tags. This is equivalent to ports being configured as UNI, internally using SVLAN service 1.
5.3.4.1.4 - EVPLINE/EVPLAN
In EVPLINE/EVPLAN mode, frames can be switched between all ports involved in a given service
(SVLAN). Each port can be involved in more than one service. QOS is performed on all ports.
SVLAN tags can be pushed/popped on ingress/egress frames, or kept if already tagged. Three port
modes are available, UNI-N, I-NNI, and E-NNI (see chapter 5.3.4.2 - for more information regarding
ports mode and tagging possibilities).
For each classification defined on any port, a service must be defined (S-VLAN column in the
following screenshot).
EPLAN, EVPLINE/EVPLAN selection tab
Ports mode can be configured in the QOS and Services configuration window, in the middle part of
the window, as shown in following screenshot.
Port mode selection

5.3.4.2.1 - UNI-N
UNI stands for User to Network Interface. UNI ports are tagging points, when entering/leaving a
network. Only GE ports can be defined as UNI. Ingress frames will receive an additional SVLAN tag
(push) according to the classification configuration of the port (see chapter 5.3.4 - for details).
Egress frames will loose the topmost SVLAN tag (pop). It is possible to have different services
attached to a port. Ingress frames can be already tagged or not with one or more CVLAN or
SVLAN.
Priority field of added SVLAN tag is defined according to configured classification and PCP
encoding table. See chapters 5.3.4.4.4 - for details.
5.3.4.2.2 - I-NNI
In this example screenshot, frames can be switched between GE port 1, GE port 4 and Radio port I-NNI stands for Internal Network to Network Interface. I-NNI ports are used for connections
for service 200, and between GE port 2, GE port 3, and Radio port for service 100. between two ports inside a trusted network. Frames that ingress I-NNI ports must be already tagged
with a SVLAN tag. The SVLAN tag will be kept (both for ingress and egress frames). The QOS
parameters (destination TC, drop precedence) used for ingress frames will be defined according to
5.3.4.2 - Port modes and tagging possibilities the SP (Service Priority) field of the SVLAN tag already on the frame. I-NNI ports are trusted ports.
The only type of classification available for I-NNI ports is SVLAN classification. This classification
Ports mode is only meaningful for EVPLINE/EVPLAN mode. For other modes, ports can be allows filtering ingress SVLAN allowed, and services to which the port is involved. No QOS
considered to be all UNI (including Radio port), and not tagging action is performed. parameter is required for this classification (see chapter 5.3.4.2.2 - for details).
In EVPLINE/EVPLAN mode, each GE port can be UNI-N, I-NNI, or E-NNI. Radio port is necessarily
I-NNI. Following description only concerns EVPLINE/EVPLAN mode.
Before a port mode can be modified, all classifications defined for this port must be removed. 5.3.4.2.3 - E-NNI
E-NNI stands for External Network to Network Interface. E-NNI ports are used for connections
between two networks that don't share the same QOS marking. Frames that ingress E-NNI ports
must be already tagged with a SVLAN tag. The SVLAN tag will be kept (both for ingress and egress WRR Scheduling:
frames), but SP field will be rewritten for ingress frames. The QOS parameters (destination TC, drop
When SP TC is empty or at its limit rate, the remaining bandwidth is shared between the WRR TCs.
precedence) used for ingress frames will be defined according to the classification configuration. E-
The weights of the different WRR TCs define the relative bandwidth that can egress from each
NNI ports are distrusted ports.
WRR TC. Thus, when congestion occurs, the available bandwidth of each WRR TC will depend on
The only type of classification available for E-NNI ports is SVLAN classification. This classification its weight and on the load of the other WRR TCs. WRR ensure that a minimum throughput will be
allows filtering ingress SVLAN allowed, and services to which the port is involved. QOS parameter available at anytime for each TC, and allow to control, in case of congestion, the relative bandwidth
is required for this classification and SP field of SVLAN tag will be rewritten accordingly (see chapter available for each TC.
5.3.4.2.3 - for details).
In case of congestion, depending on the time a frame spend waiting in a TC queue, the latency can
5.3.4.2.4 - EtherType vary. To achieve low latency applications, use higher priority TC than the rest of the traffic. For
example voice traffic should be classified inside TC3.
In EVPLINE/EVPLAN mode, the EtherType used for SVLAN services can be configured. The
default value is 0x88A8. Any 2bytes value can be used, including the value used for CVLAN
(0x8100). Bellow is a diagram of egress side of a port:
The EtherType value is the value that will be used for SVLAN tag added to ingress frames for UNI-N
ports. On NNI ports, ingress frame must be tagged with a SVLAN tag using the configured
EtherType.
SPTC Shaper
TC3 (SP)
TC2 (WRR 16)

Egress pipeline
TC1 (WRR 8)
Port Scheduler
Port Shaper
WRR Scheduler
TC0 (WRR 4)
Ether type configuration
EtherType used for CVLAN tags (used for CVLAN Id classification) cannot be configured, and is
standard value 0x8100.
5.3.4.3.2 - Strict priority shaping

5.3.4.3 - QOS parameters
5.3.4.3.1 - Available classes of service

Strict priority shaping (or SPTC shaping) can be configured to allow limiting SP TC available
4 classes of service are available on each port. Each TC (Traffic Class) has a specific scheduling bandwidth. In some conditions, the traffic rate classified in SP TC (TC3) can't be controlled. If traffic
mode. Below is a list of the available TCs and the associated Scheduling mode: in SP TC uses all the bandwidth available on a port, other WRR TCs will not be served at all. To
avoid this situation, it is possible to configure a SP TC shaping, limiting the bandwidth only for the
traffic of SP TC. In this case only a part of the port bandwidth might be used for SP TC, and the rest
TC Description Scheduling of the bandwidth is always available for WRR TCs.
TC3 Very high priority SP (Strict Priority)

SP TC can be either disabled, or configured globally as a percentage of the port shaped bandwidth
TC2 High priority WRR (Weighted round robin) with weight 16
(or port speed if no shaping is applied on the port), or configured per port. Per port configuration can
TC1 Normal priority WRR (Weighted round robin) with weight 8 be disabled, a percentage of the port shaped bandwidth, or a manually configured value. Chapter
5.3.3 - and 5.3.2.2 - describe the SP TC configuration.
TC0 Low priority WRR (Weighted round robin) with weight 4
Note: SP TC can only be used if metering is disabled.

SP Scheduling:
Strict priority means that as soon as there is a frame waiting to be transmitted in the associated TC,
it will be transmitted. Other TCs must wait for the SP TC to be empty or for the SP TC to have 5.3.4.3.3 - Metering and policing
reached the authorized SP TC shaped bandwidth limit (see chapter 5.3.4.3.2 - for details) to be
served.
It is possible to perform metering and policing actions on the equipment. Metering configuration is
global to the equipment and if turned on, metering and policing will be performed on all
classifications.
Metering configuration can be found on the top of the QOS and Services configuration window, as
shown in the following screenshot:
Below screenshot shows a classification add window with metering enabled:
Metering:
CIR value
Equipment performs a two color marking for the metering (Green and Yellow) which is called SrTcm
(Single rate, Two color marking). When metering is enabled, for each classification, a CIR value
must be entered. Equipment will monitor the used bandwidth for each classification, and compare it
with CIR value. If the used bandwidth is bellow the CIR, all frames in the associated flow will be
marked Green. Otherwise, part of the frames will be marked Yellow, and part of the frames will be
marked Green, so that the bandwidth for Green frames is equal to the CIR value.
For I-NNI ports, according to PCP encoding (5.3.4.4.4 - ), the CIR value might be required. If PCP
encoding already include a drop precedence information (for example 5P3D encoding), the drop
precedence from the SP field of SVLAN tag is used to define drop precedence. Thus no CIR value
is required. Green frames have no drop precedence, and Yellow frame have drop precedence. If the
PCP encoding mode doesn't include drop precedence information (for example 8P0D encoding), a
CIR value must be defined for each SVLAN classification. Policing:
For UNI ports, the CIR defined for a classification is applied differently according to the equipment On the egress side, queuing in the different TCs will depend on the frame color and destination TC.
mode. If mode is EPLINE or EPLAN, the CIR is the limit for the flow identified by the classification When queuing frame in SP TC (TC3, very high priority), Green frames will be queued normally, and
it's configured for. If mode is EVPLINE or EVPLAN, the CIR is the limit for the total bandwidth used Yellow frame will be automatically dropped (whatever the queue status). Thus the egress bandwidth
by all flows (classifications) that share the same service (SVLAN) on the port it's defined on. In the of the traffic classified on SP TC will never go above the CIR limit.
screenshot below, CVLAN 20 and 30 share the same SVLAN 300 on port 1. The limit for the
bandwidth of both CVLAN cumulated is 5Mbps (even if 5Mbps is displayed for each of them). The When queuing frame in a WRR TC (TC2, TC1, TC0), Green frames will be queued normally, and
CIR is share between these two. CIR for SVLAN 300 on other ports (for example port 2) is Yellow frame will be queued only if queue is not too heavily loaded (enough free space in the queue
independent. is available). The result of this behavior is that when a classified traffic exceeds the CIR value,
Yellow frames will be dropped while Green frames pass through. Thus the traffic below CIR will
pass through without loss while traffic above CIR will be shaped if needed.
Note: TC priority (scheduling) acts on top of policing. Thus the CIR bandwidth can only be
guaranteed within the bandwidth available to that TC (see 5.3.4.3.4 - for TC bandwidth calculation
examples).
Note: Metering can only be enabled if flow control is disabled.
To give more freedom of configuration, no CIR oversubscription limit is implemented in

either Equipment or Pilot software. User must be careful to avoid oversubscription while
configuring QOS
Metering is performed on the ingress side.

Below screenshot shows an example with CIR value defined for some classifications:
5.3.4.3.4 - Bandwidth computation examples TC0 egress rate is then:

(100M 10M 20M) x 4 / (8+4) = 23.3M
Examples assume that frames in different TCs have the same size (to make bandwidth calculation
easier).
5.3.4.4 - Services and QOS configuration

1)
5.3.4.4.1 - Classification principle
Port shaping: 100M
SPTC shaping: none Classification goal is to distinguish traffic flows and assign them to services and apply different level
TC Ingress Load Egress Load of QOS on them. Several criteria can be used to classify traffic (see 5.3.4.4.2 - ).
TC3 (SP) 1000M 100M When QOS is disabled, no classification can be configured. In this case, all traffic competes on a
TC2 (WRR 16) 1000M 0M best effort basis to use the available Ethernet or Radio port physical bandwidth. Frames will be
TC1 (WRR 8) 1000M 0M randomly dropped.
TC0 (WRR 4) 1000M 0M When QOS is enabled, all frames that ingress the equipment must be classified. All unclassified
traffic will be dropped by equipment.
In this example, No SPTC is configured, and TC3 use more bandwidth than port shaping. Thus TC3 In EVPLINE/EVPLAN, classification also allows defining to which service a given traffic belongs (for
takes all the available bandwidth of the port, which is 100M. other modes, the classifications defaults to service 1).
2) A classification is a set of up to 5 parameters:

Port shaping: 100M - An ingress port
SPTC shaping: 50M
- A classification type (with specific classification type parameters, for eg. VLAN Id)
TC Ingress Load Egress Load
- A priority (One of the destination TC, if port mode is not I-NNI)
TC3 (SP) 1000M 50M
TC2 (WRR 16) 1000M 28.6M - A Service or SVLAN (default to 1 for all classification in EPLINE or EPLAN)
TC1 (WRR 8) 1000M 14.3M - A CIR value (if metering is enabled, default values is 0 and is ignored if metering is disabled).
TC0 (WRR 4) 1000M 7.1M
In this example, TC3 load is higher than the SPTC shaping. The egress rate of TC3 is limited by the
SPTC shaping, thus available egress rate for TC3 is 50M. Other WRR queues share the remaining Classification can be defined and seen from the QOS and Services configuration window, on the
bandwidth (100-50 = 50M) according to their weights. The load for TC2 for example is: bottom part, as shown below.
(100M - 50M) x 16 / (16+8+4) = 28.6M

Same goes for TC1 and TC0.
3)
Port shaping: 100M
SPTC shaping: 50M
TC Ingress Load Egress Load
TC3 (SP) 10M 10M
TC2 (WRR 16) 20M 20M
TC1 (WRR 8) 1000M 46.6M
TC0 (WRR 4) 1000M 23.3M
In this example, TC3 load is under the SPTC shaping. Thus all traffic rate on TC3 is not limited, and
10M egress from TC3. Other WRR queues share the remaining bandwidth (90M) according to their
weights. The load for TC2 should be:
(100M 10M) x 16 / (16+8+4) = 51.4M
But TC2 is only loaded with 20M. Thus the total 20M of TC2 pass through, and the rest of the
bandwidth is shared between TC1 and TC0. TC1 egress rate is then:
(100M 10M 20M) x 8 / (8+4) = 46.6M
In advanced mode, be sure to select the desired tab (EPLAN or EVPLINE/EVPLAN) before adding
a classification. Classifications displayed are only the one relevant for the currently selected tab.
Only one type of classification may be used on a given port. Exception is for the default modes,
which can be used to make default rules for other classification types (see details in the following
chapter).
The following screenshot show an example of the classification add window (when add button is
clicked) in EVPLINE/EVPLAN with metering enabled:
Port on which the classification
will be applied.
Type of classification used.
Parameter specific to this type of

classification.
Service associated with this

classification (if mode is
EVPLINE/EVPLAN).
Priority assigned to this

classification (Low, Normal,
High, or Very high)
CIR value for this service (if

metering is enabled).
The following screenshot is the same window except that the classification is added for EPLAN and
metering is disabled:
Classification Control buttons
List of configured classifications
Columns header
5.3.4.4.2 - Available classification types
The list of classification can be sorted using the column headers. Hereafter is the list of available classifications and associated parameters. All classification can be
applied to UNI port, except SVLAN classification. SVLAN classification can only be applied to I-NNI
or E-NNI ports (and is the only classification available for these ports mode).
Existing classifications on the list can be deleted or modified when selected by using the Delete or
Modify button. Modifying an existing classification allows to change the priority or the CIR. If the
other fields have to be modified, the classification must be deleted and recreated. Screenshots are taken for a classification in EVPLINE/EVPLAN mode with metering enabled. If
classification is added in EPLINE or EPLAN mode, the SVLAN field will be absent (default to 1). If
Use Add button to add a new classification. Delete all button will delete all existing classifications. metering is disabled, CIR field will be absent. But the classification remains the same.
Default equipment configuration is in 4 EPLINE mode, with a port classification on each GE port CVLAN Id classification.
with priority High and metering disabled.
x Port classification VLAN Id parameter.

Port classification includes all frames that ingress from a given port. All traffic will fall under this
classification. No additional parameter is required. No other classification may be added to the port.
Target port.
Port classification.
In this example, frame with a CVLAN tag (EtherType 0x8100) with a VLAN Id field equal to 10 that
ingress from port 1 will be added to SVLAN 200 (a tag will be pushed on top of the frame) and will
be classified on Normal priority queue (TC1). The CIR limit here is 10M. All other frames will be
dropped, if there is no other classification on this port.
In this example, any frame that ingress from port 1 will be added to SVLAN 200 (a tag will be
pushed on top of the frame) and will be classified on Normal priority queue (TC1). The CIR limit
here is 10M.
x CVLAN Id classification
This classification is based on the VLAN Id field of ingress frames containing a CVLAN tag. The
CVLAN tag of ingress frames must have an EtherType value of 0x8100. An additional VLAN Id
value must be supplied. The value can be a single value or a range of value. Note that when
defining a range of value, more than one service slot might be used on the total number available. It
is possible to add another VLAN Id classification or a default classification (default_all,
default_tagged, default_untagged) on the same port.
In this classification mode, it is possible to use a special priority level, called "user". With this "user"
priority selected, the behavior will be a little different. UP (User Priority) field of ingress CVLAN tag In this example, frame with a CVLAN tag (EtherType 0x8100) with a VLAN Id field equal to 10 that
will be copied to the SP (Service Priority) of added SVLAN tag. The PCP decoding table (see ingress from port 1 will be added to SVLAN 200 (a tag will be pushed on top of the frame) and will
chapter 5.3.4.4.4 - ) will be used to classify frames. If PCP table have drop precedence information be classified according to UP value of ingress CVLAN tag. The SP field of SVLAN tag will be copied
and metering is enabled, the drop precedence will also be extracted from UP field. Otherwise, if from UP field of CVLAN tag.
metering is enabled, a CIR value must be defined for the classification.
x CVLAN UP classification
This classification is based on the VLAN UP (User Priority) field of ingress frames containing a
CVLAN tag. The CVLAN tag of ingress frames must have an EtherType value of 0x8100. An
additional UP value must be supplied. It is possible to add another CVLAN UP classification or a
default classification (default_all, default_tagged, default_untagged) on the same port.
This classification takes all unclassified frames.

Default_tagged:
CVLAN UP classification.
This classification takes all CVLAN tagged frames that are unclassified. CVLAN tag must have
an EtherType of 0x8100.
Default_untagged:
VLAN UP parameter.
This classification takes all frames that are not CVLAN tag with an EtherType of 0x8100, and
unclassified.
Default_tagged and default_untagged can be used together if available. But default_all can't be
used along with default_tagged nor default_untagged.
Below is a screenshot of the QOS and Services configuration window with some services defined:
x User predefined classification

The user predefined classifications are configured on a separate window (see chapter 5.3.4.4.3 -
for details). Here, any of the user predefined classification can be selected. It is possible to add
another User predefined classification (but only of the same type) or a default classification
(default_all) on the same port.
User predefined classification.
Selected User predefined.
In this example, frame which match the filter defined for user create rule named "DSCP_10" will be
added to SVLAN 200 (a tag will be pushed on top of the frame) and will be classified on Normal
priority queue (TC1). The CIR limit here is 10M. All other frames will be dropped, if there is no other
classification on this port.
x Default classifications
The default classifications allow completing some other classifications with default rules. Other
classifications are done in priority, which ensure that only the unclassified frames fall in the default
mode. Three default modes may be available (depending on the port other classification, see other
classification description for availability):
Default_all:
Each of the filters can be modified. For each filter, a name, a target field, and a value should be
provided. The name is used in the QOS and Services configuration window to identify the user
predefined classification. The target field can be any of the following frame field with the associated
values:
- MAC SA: Ethernet MAC source address

A mask on MAC address must be entered. For each byte of the address, a value can be
entered or a wildcard can be used (enter two wildcards), address bytes are separated with
dashes:
00-**-**-**-12-AB
Here all Ethernet MAC source addresses starting with byte 00 and ending with bytes 12
followed by AB will match the defined classification.
- MAC DA: Ethernet MAC destination address
Same behavior and configuration than MAC SA but with destination address.
- DSCP: DSCP field of IP header
Any value from 0 to 63 might be entered. This value will be compared to the 6 bits of
DSCP field of IP header (if any) of ingress frames. Combined with default classification
mode, this allows creating up to 8 DSCP based classes of service.
- IP protocol: IP protocol field of IP header
Any value from 0 to 255 might be entered. This value will be compared to the byte of IP
header specifying used upper protocol (for example ICMP, TCP, IGMP, OSPF ..).
5.3.4.4.3 - User predefined classifications - Source IP: Source IP address
User predefined classification provides 8 additional classifications that can be chosen and A mask on IP address must be entered. For each byte of the address, a value can be
configured according to customer necessity. User predefined configuration window can be found entered or a wildcard can be used (enter two wildcards), address bytes are separated with
here: dots:
Configuration->Gigabit Ethernet->Advanced configuration->User predefined->local/remote 192.168.**.**

Here all IP source addresses starting with bytes 192 followed by 168 will match the
defined classification.
Below is a screenshot of the window:
- Dest IP: destination IP address
Same behavior and configuration than SIP but with destination address.
- Source port: UDP/TCP source port
Any value from 0 to 65535 might be entered. This value will be compared to the source
port of UDP or TCP protocol. 8P0D decoding 8P0D encoding
SP field Priority Priority SP field
- Dest port : UDP/TCP destination port
0 Low Low 1
Same behavior and configuration than Source port by with destination port. 1 Low Medium 3
2 Medium High 5
3 Medium Very high 7
Note: it is not possible to modify an entry if a classification is using this entry (in the QOS and
Services configuration window). 4 High
5 High
6 Very high
5.3.4.4.4 - PCP encoding 7 Very high
PCP encoding and decoding tables are used to handle the priority field of SVLAN tags (SP) used as
PCP code.
It will be used in the following situations:
5P3D table:
- UNI ports, in EVPLINE/EVPLAN (encode table)
The 5P3D table includes up to 5 levels of priority and 3 levels of drop precedence. Since the
To define the value of the UP field of added SVLAN tag, based on the classification
equipment has 4 TCs, the two higher priorities are grouped (6 and7). For each other priority two
selected priority and drop precedence (resulting from metering if used).
values are available, one with drop precedence, and one without drop precedence.
- I-NNI ports, in EVPLINE/EVPLAN (decode table)
If metering is enabled, decoding table will give the drop precedence to use for I-NNI ports. Encoding
To decode the SVLAN UP field of ingress frames and obtain the priority to apply and the table allows encoding the priority selected, and the result of the metering.
drop precedence (metering result, if used).
- UNI ports, in EVPLINE/EVPLAN, with CVLAN Id classification and "user" priority selected
Priority assignments are as follows:
(decode table)
5P3D decoding 5P3D encoding
In this case, the UP bits of ingress CVLAN tagged frames are copied to SP bits of SVLAN
tag (see chapter 5.3.4.4.2 - for details). The table is then used like in the previous I-NNI SP field Priority Drop precedence Priority Drop precedence SP field
use case, to decode SP bits and extract the target priority and drop precedence if any. 0 Low yes Low yes 0
1 Low no Low no 1
2 Medium yes Medium yes 2
The desired PCP table can be selected in the upper part of the QOS and Services configuration 3 Medium no Medium no 3
window, in advanced mode. High yes 4
4 High yes
5 High no High no 5
6 Very high no Very high yes (not used) -
7 Very high no Very high no 7
Note: encoding for very high priority and drop precedence is unused because frame with drop
precedence on Strict priority queue are systematically dropped, and thus don't egress the
equipment.
User defined table:

In this mode, the user may configure the PCP table manually. When clicking on the "Table" button
Three tables are available, 8P0D, 5P3D, and User. The User selection allows defining the table
of the QOS and Services window, the following window appears:
manually by clicking on the "Table" button.
8P0D table:
The 8P0D table doesn't include drop precedence information (0D) and allows up to 8 priority levels.
Since the equipment has 4 TCs, priorities are grouped two by two.
Metering result information doesn't influence SP field value and no drop precedence information can
be extracted from the table. For I-NNI ports classifications, if metering is enabled, the CIR value has
to be defined for the equipment to measure the ingress rate and determine the drop precedence to
apply internally.
Priority assignments are as follows:
Flow control can't be enabled if metering is enabled at the same time. Metering must first be
disabled before enabling flow control.
Flow control will only send pause frames for local GE ports. For example if congestion occurs on the
Radio port, pause frames will be sent to all GE port (from 1 to 4). If congestion occurs on GE port 3,
pause frames will be sent to GE port 1, 2 and 4.
In EVPLINE/EVPLAN mode, pause frame is sent only to the ports that share at least one common
SVLAN with the port on which congestion occurs.
It is mandatory for flow control to work that Client equipments connected to GE port are fow
control capable and that the flow control option is turned on for these equipments (generally
found in the port configuration or QOS configuration). It is recommended that all equipments
have flow control enable if one of them is.
5.3.5.2 - Mac filtering

MAC filtering option allows filtering (dropping) some selected addresses. It is possible to filter up to
16 addresses per port. When a new filter is applied, it is possible to apply it to more than one port at
a time.
This table is used both for encoding and decoding. For each SP field value, a corresponding priority Mac filtering can be found in the following menu of the Pilot software:
can be selected (Low, Medium, High, Very high).
Configuration->Gigabit Ethernet->Advanced configuration->Security configuration->MAC filtering-
For decoding, the priority is deduced from the table directly. >local/remote
For encoding, the lowest SP field value corresponding to the destination priority is used.
For example, in the previous screenshot, the decoded priority for SP field value 5 is Very high. The
SP field encoded value for priority Normal is 3.
5.3.5 - Other features
5.3.5.1 - Flow control

Flow control can be enabled to avoid having congestion inside the equipment. Flow control function
monitors egress queues and above a threshold starts sending pause frames to stop queuing
frames. Equipments connected to GE ports receive the pause frames and stop sending traffic.
Traffic is resumed when queues are empty enough.
Clicking on the Add button brings the following window, where it is possible to enter a new address
and select target ports. Address can be either source address (SA) or destination address (DA).
Flow control configuration can be found in the following Pilot menu:
Configuration->Gigabit Ethernet->Advanced configuration->Congestion configuration->local/remote
5.3.5.3 - Fast link shutdown Note: Aging time is in fact the aging period. FDB is parsed every aging period to check addresses
that were not used during the period and remove them if needed. From the customer point of view,
Fast link shutdown function allows forcing a link shutdown on GE ports when radio channel is an address that stop being used at a time T will be forgotten at a time between T + aging time and T
unavailable. This behavior can be useful to speed up network protection protocol triggering like for + 2 x aging time.
example RSTP.
Fast link shutdown configuration can be found in the following menu of Pilot software:
5.3.5.5 - Ethernet with 2+0 XPIC or FD modes
Configuration->Gigabit Ethernet->Advanced configuration->Fast link shutdown->local/remote
When 2+0 radio function is enabled, Ethernet configuration remains the same. No additional
parameter is required. Both radio channels are aggregated using a proprietary patented link
aggregation mechanism. The full radio bandwidth available for Ethernet traffic can always be fully
used, whatever the Ethernet traffic is (LAPC on the contrary rely on MAC addresses and has a
statistical aspect that doesn't guarantee full link exploitation). Moreover, even in dissymmetrical
conditions (when channel 1 has more available bandwidth than channel 2 for example in ACM, or
when on channel is down), the equipment can still guarantee full link exploitation.
Thus Ethernet bandwidth can be computed at any time as the sum of available bandwidth for
channel 1 and 2 (or H and V in case of XPIC).
To compute available bandwidth, refer to performance sheets specific to the software version in
use. The bandwidth is given for a single channel, and thus must be summed for 2+0 applications
(taken into account each channel configuration, in particular, the number of E1).
5.3.5.6 - Ethernet with ACM
Function can enabled or disabled. If enabled, the target ports must be selected. When equipment is in ACM mode, the modulation and coding gain of the radio channel is
dynamically adapted to available radio signal quality. For Ethernet part, the consequence is that the
When the equipment radio modem reception gets unlocked (very bad radio conditions or hardware bandwidth available on Radio port will vary in time to adapt to the current radio configuration. For
failure), the equipment will force a link down on the selected ports. The link down is applied in less each ACM profile, an Ethernet bandwidth is available (see chapter 1.5 - for explanations about
than 50ms. When radio condition gets better or hardware failure is fixed, ports are enabled again ACM).
and resume normal behavior.
The dynamic bandwidth should be taken into consideration to defined QOS configuration (in
particular SPTC shaping and metering).
Where network protection protocol such as RSTP would have to wait for generally 3 Hellotime
message timeout before stating that link is unavailable (by default around 6 seconds), the link down
applied by fast link shutdown mechanism force the link unavailability directly, and reduce this delay It is possible to define a minimum profile for Ethernet part of the equipment. To do so, go to the
to 50ms. capacity configuration window, and select the "GE Tx mute on profile below", As show in the
following screenshot.
5.3.5.4 - FDB management

Equipment's switch FDB (Forward DataBase can store up to 16k Ethernet MAC addresses. The
FDB configuration window can be found in the following menu of Pilot software:
Configuration->Gigabit Ethernet->Advanced configuration->FDB management->local/remote
The aging time of the FDB can be configured by steps of 10 seconds. Default value is 30, which
gives an aging time of 5 minutes.
The table can be flushed at anytime using the "Flush FDB" button.
Bring the minimum GE profile

selection window. 5.4 - CONFIGURING 2 MBIT/S PORTS
Click on one of the "TRIB" connectors in the Shelf view or open the "Configuration / E1
Tributaries / Local or Remote" menu to open the window used to configure the 2 Mbit/s ports.
This screen may vary depending on the current capacity. A screen example for a capacity of
16 x 2 Mbit/s ports is given below:
When this button is "ON", an AIS Set the loopback

signal is transmitted when the error time required
rate is higher than the threshold
configured for the alarm BER Alarm"
Select the desired minimum in

the list of available profiles.
If at anytime the radio switches to a profile below (strictly) the selected minimum, Ethernt Radio port Blank: active (normal)
available bandwidth will be set to 0. This stops all transmission over the Radio channel for Ethernet. Blank: No loopback S: AIS transmission
L: Local loopback Balanced 75:
Other tributaries (E1, management channel, wayside) are unaffected, and keep functioning R: Remote loopback I: the access is not used The connector corresponding to
normally. N: The access is used (Normal) this group of tributaries is in
unbalanced 75 Ohm configuration
This can be useful to force network protection equipments to select another path in the network
when available bandwidth of radio channel is not sufficient. For example in the screenshot above,
All QOS can be configured as if the minimum bandwidth available for radio channel was 74.4Mbps,
knowing that if equipment goes to a lower bandwidth (or suffer a hardware failure), traffic will be
Click on the corresponding button to change the settings.
stopped to force using another path in the network.
x AIS insert on BER: when this button is ON, an AIS is transmitted when the error rate is higher
than the threshold configured for the alarm BER Alarm".
To give customer more freedom of configuration, no limitation is enforced in embedded or
Pilot software regarding minimum bandwidth, CIR reservation or SPTC shaping. User must x Monitoring:
be careful while configuring QOS to avoid oversubscription. x If the access is not connected, configure it as invert "I". In this case, no alarm is generated
since there is no signal at the input. However, if the access is configured as invert, a
tributary alarm is generated if a signal is present.
x If the access is used for traffic, it must be configured as normal "N". In this mode, an alarm
is generated if there are no signals on the access.
x Service: in normal operation, select "blank" button (active). If "S" is selected, an AIS is returned
locally on the reception access of the channel concerned. Note that, in this case, no AISs are
transmitted to the remote terminal.
x Interface: each DB44 or DB78 connector on the front panel includes the access for eight or 16
x 2 Mbit/s inputs/outputs. The electrical interface of the accesses can be configured by the Pilot
one connector at a time by clicking on the corresponding Balanced 120 / Unbalanced 75
buttons.
x Tributaries loopbacks remote timer for E1 loopback. This loopback time can be also defined via the "Maintenance
/ Loopbacks / Loopback Timer" menu.
x Loopback: click on a button on the loopback line of a port "x" to display the screen allowing
the local or remote E1 loopbacks for this port. This screen can also be displayed from the When a local loopback is activated, a maintenance indication is displayed in the Pilot status bar, the
"Maintenance / Loopbacks / Tributary x-y" menu. An Equipment loopack (Maintenance / orange "Maint" Led on the local IDU front panel and its image on the Pilot are lit.
Loopbacks / Equipment Loopback On menu) will make inaccessible this menu and the E1 When a remote loopback is activated, the orange "Maint" Led on the remote IDU front panel and its
ports loopback. image on the Pilot are lit but no maintenance indication in the Pilot status bar, this one being
connected to the local IDU.
Check one or more Check one or more
boxes to activate boxes to activate
local loopback remote loopback 5.5 - CONFIGURING THE ALARM THRESHOLDS
BER and RSL alarms thresholds can be adjusted with the Pilot software.
Open the "Configuration / Alarms / Local" menu or click on the "Alarms In/Out" connector in the
Shelf view.
5.5.1 - BER and ACM alarm thresholds
Select the Modem tab.

Two BER thresholds can be configured: BER Alarm (default: 10-3) and BER Warning (default: 10-6)
These thresholds may be modified between 10-3 and 10-6. It is advised to keep the default values.
For ACM mode, a threshold profile can be selected to trigger modem ACM alarm when modem
current profile goes bellow (strictly) the threshold.
The principle of remote loopback is explained in the following diagram:
Local tributary
loopback
2 Mbit/s Input 2 Mbit/s Output
2 Mbit/s Output 2 Mbit/s Input
2 Mbit/s Input 2 Mbit/s Output

2 Mbit/s Output 2 Mbit/s Input
Remote tributary
loopback 5.5.2 - RSL alarm threshold
Local terminal Remote terminal
Select the Radio tab.

Local loopback is used to check the wiring on the local terminal.
The threshold can be adjusted between -40 dBm and -90 dBm (default: -60 dBm).
Remote loopback is used to check the radio transmission.
x Timer: define the loopback time for the link (maximum 8 hours, default value 1 hour) so that
it returns to non-looped back mode automatically: local timer for Equipment or E1 loopback,
5.6 - CONFIGURING THE ALARMS

Configuration is carried out via the "Configuration / Alarms / Local or Remote" menu, by clicking
on one of the "Relay" Leds on the Pilot front panel, or by clicking on the "Alarms In/Out" connector
on the Shelf view. Six tabs are available to configure the site alarms, their severity, their assignment
to a relay and their transmission to the manager.
Whenever a box is checked, an "Apply" window is displayed: click to validate the configuration.
A view of each of the six tabs is given for information or to indicate a special configuration. The
meaning of the alarms is described in 7.5.1 -.
5.6.1 - General parameters

On all tabs, each alarm can:
5.5.3 - Ethernet bitrate alarm threshold
x be assigned to one or more relays if the corresponding boxes are checked; the default
assignment of the relays is given in 5.6.8 -.
Select the Gigabit Ethernet tab. 3 relay outputs are available on the "Alarms IN/OUT" connector. These relays are fully
The threshold can be adjusted by steps of 1 kpbs. Alarm will be raised if Radio port bandwidth goes programmable: Internal local alarms or external (local or remote) alarms can be assigned to each
below the threshold (useful in ACM). Default value is 0, which disables the alarm. relay.
Relay operation can be enabled or disabled by checking or unchecking the "Enable relays" box in
"General Parameters"; in the default configuration, the box is checked.
If an alarm is generated the names of the alarm and of the associated relay are written in red.
Click on a Relay box to check or uncheck all boxes in the alarm column in one go.
x Define a severity level: "None", "Warning", "Minor", "Major" or "Critical" by checking the
corresponding box.
The default alarm severities are indicated in the tables of 7.5.1 -.
x Check the corresponding box "Enable Trap", if you want to send the SNMP trap to network
managers. The default configuration is "box checked" for all alarms except for "Link Status"
and "Rx Frame".
The traps sent to the network manager can be filtered according to the severity: check the
"Disable traps with severity" box corresponding to the severity level you do not want to send the
trap to the manager, for all alarms configured at this level; the default configuration is "box
unchecked".
The list of managers authorized to manage the equipment traps can be completed by clicking on
"Trap Managers". The maximum number of authorized managers in a network is 10.
Enter the IP address of Add, modify or delete a

the authorized manager manager
to be added
5.6.2 - "IDU" tab 5.6.3 - "Modem" tab
SLF-H can manage up to 5 external alarm inputs available locally. These signals are connected to
This tab can also be used to set the BER alarm thresholds (see 5.5.1 -).
the "Alarms IN/OUT" connector. The pinout of this connector is given in 3.7.2.3 -.
These five alarms can only be configured locally and named; they will be either:
x "D": the alarm is disabled 5.6.4 - "Radio" tab
x "N": the alarm is configured as normal; there will be no alarms if the corresponding input on the
connector is in open circuit, and an alarm will be generated if this input is shorted to the ground.
x "I": the alarm is configured as invert; the alarm state corresponds to open circuit.
SLF-H can also display locally the 5 alarm inputs from the remote terminal by checking the
corresponding box; the "ext" Led of the local IDU will be red.
If the status of any activated external alarm changes, the "Ext" Led on the IDU front panel is lit red.
This tab can also be used to display or not an alarm regarding the Wayside channel by checking or
unchecking the corresponding box.
5.6.5 - "Tributaries" tab
This tab can also be used to:
- Set the RSL alarm thresholds (see 5.5.2 -).
- Define RSL Gap, which is the minimal variation of RSL above which the RSL change will be recorder in the
Event log.
5.6.6 - "Gigabit Ethernet" tab
This tab can also be used to:
- Set the Ethernet bitrate threshold (see 5.5.3 -).
5.6.7 - "Fans" tab
5.6.8 - Default configuration of the alarm relays 5.8 - SPECIFIC CONFIGURATIONS FOR 1+1 SYSTEMS
Revertive Automatic Switching Tx for "Hot Stand By" or "Space Diversity" configurations.
Relays Alarms assigned by default
Relay 1 Wayside This option gives priority to the transmitter channel 1.
Modem alarms When this box is checked "ON", the transmitter in traffic is that from the ODU 1. If there is a fault on
Fan alarms the channel 1, traffic is switched over onto the channel 2. When the fault on the main channel
disappears, the system switches the traffic back to the channel 1.
Relay 2 Tributary alarms
Giga Ethernet alarms
Click on the protection button of the Pilot screen or open the "Configuration / Protection / Local or
Relay 3 Radio alarms
Remote" menu to display the following screen:
Table 5-1 - Default configuration of the alarm relays
5.7 - CONFIGURING THE AUTOMATIC TRANSMIT POWER CONTROL (ATPC)

ATPC is used to increase the density of a network by allowing frequency reuse. This process
consists in automatically reducing the transmit power of each transmitter, while keeping good
transmission.
ATPC must not be active during antenna installation and commissioning.
ATPC settings depend on the structure of the network (frequency re-use, radio interferers, link
margin). The operator must define 3 main parameters:
x Maximum ATPC transmit power
x Minimum ATPC transmit power
x ATPC reception threshold
When the Revertive Automatic Switching Tx option is not selected, transmit switch position is free.
The minimum and maximum powers must be within the transmitter power ranges.
The system stays in the current position until a fault appears.
The ATPC receive threshold must be within the range -40 dBm to -70 dBm.
Note that the transmit and receive switches are independent.
The ATPC process consists in modifying transmit power automatically within the specified range
while ensuring that there are no transmission errors and that the received level on the remote
terminal remains equal to the specified threshold (+/- 1dB).
To enable ATPC, click on the ATPC button and set it to "ON".
ATPC parameters are configured via the Configuration / ATPC / Local or Remote / Channel 1 or
Channel 2 menu or by clicking "ATPC" on the main screen.
Enter the three values and validate with the Apply button.
5BOPERATION PILOT
6. OPERATION PILOT
SLF-H operation and maintenance are carried out:

- directly on the equipment, via the Leds on the front panel,
- from a PC equipped with the Pilot software, or,
- from a network manager by using SNMP protocol.
This paragraph describes the Pilot screens used to access all functions of SLF-H equipment.
5BOPERATION PILOT
File Session Alarms Configuration Performance Maintenance Help
Open Session View Alarms RSL Tx/Rx Forcing Shortcuts

Close Session Text Log Management Network Link Statistics Loopbacks About FH HC
Graphical Log Gigabit Ethernet Gigabit Ethernet Frequency Scan Pilot
Protection Wayside Constructor Maintenance
ATPC Clear BER stats Restriction
System Report
E1 Tributaries Clear/Reset All Try to unmute remote
IDU Configuration Local
Boot Firmware Remote Hardware Inventory
IDU Firmwares Pilot
ODU Firmwares Reset to default database
Channel 1 Tributary 1-8
Quit Save Channel 2 General Ethernet Statistics Tributary 9-16
Load Metering Statistics
Tributary 17-32
Click on in the screen to display the front panel of the equipment managed by the Pilot. Tributary 33-48
Tributary 49-64
Tributary 65-80
Ethernet port configuration
Equipment Loopback On
Advanced configuration
Equipment Loopback Off
Ethernet Ports and Radio Channel Loopback Timer
Routes
QoS global configuration
QoS and Services configuration
Congestion configuration Channel 1
Security configuration Channel 2
Mac filtering
User predefined
FDB management
Fast Link Shutdown
Figure 6.1 - Equipment shelf view without SPDH extension

Figure 6.3 - Pilot menu tree structure
For some configuration, the tree structure items include the "local" or "remote" submenu, which is not displayed here.
Menus in bold have submenus
Page 6-2 SLF-H Installation and Operation Manual 253 255 964-D
Figure 6.2 - Equipment shelf view with SPDH extension
This view also provides direct access to several Pilot menus, by clicking on the various elements. For
example, clicking on the "Alarms In/Out" connector opens the equipment alarm configuration window.
The Pilot menus, available when logged on as "Super User" mode, are described in the following tree
structure.
5BOPERATION PILOT 5BOPERATION PILOT
6.1 - HELP MENU 6.2 - FILE MENU
"Help / Shortcuts" menu: gives the list of functions that can be accessed via keyboard shortcuts. 6.2.1 - "File / System Report" menu
This menu can be used to print or save on PC a text file containing various useful information, like for
example equipment configuration data and the detailed equipment composition (serial numbers,
hardware and software versions, etc.) of the local and remote sites. Items can be added or not in the
report depending on the boxes checked (see 4.5.9 -).
6.2.2 - "File / IDU Configuration / Local or Remote / Save" menu

This menu can be used to save on PC the local or remote site configurations (cards, alarms,
performance, connections, protection, etc.).
If the IDU or the ODU is replaced, these files can be used to reload the configuration quickly.
Note: always use a ".sav" extension for these configuration files.
Warning, configuration filename should not contain special characters (otherwise,

configuration file retrieve will fail).
6.2.3 - "File / IDU Configuration / Local or Remote / Load" menu

This menu can be used to quickly load a previously saved IDU configuration, either in the list proposed
or in an external file retrieved by "Other file"; in this case, click on "Download".
"Help / About FH HC Pilot" menu: indicates the Pilot software version
Download: downloads a firmware version selected in the list proposed or in an external file retrieved
6.2.4 - "File / Boot Firmware / Local or Remote" menu by "Other file"; in this case, click on "Download".
After downloading, the Pilot proposes immediate or deferred activation of the new firmware.
This menu gives the current version of the boot firmware and can be used to load another firmware
selected in the list proposed or in an external file retrieved by "Other file"; in this case, click on Warning, firmware filename should not contain special characters (otherwise, firmware file
"Download". download will fail). It is safer to keep the name of the firmware files provided by Sagemcom
unmodified.
6.2.6 - "File / ODU Firmware / Local or Remote" menu

The menu indicates the current version of the ODU firmware and the version stored in reserve bank.
Warning, boot filename should not contain special characters (otherwise, boot file download
will fail). It is safer to keep the name of the boot files provided by Sagemcom unmodified.
6.2.5 - "File / IDU Firmware / Local or Remote" menu

The menu indicates the current version of the IDU firmware and the version stored in reserve bank.
Activate reserve firmware: activates the ODU firmware from the reserve bank.
Download: downloads a firmware version selected in the list proposed or in an external file retrieved
by "Other file"; in this case, click on "Download".
After downloading, the Pilot proposes immediate or deferred activation of the new firmware.
In 1+1 configuration, the standby ODU is downloaded independently.
Warning, firmware filename should not contain special characters (otherwise, firmware file
download will fail). It is safer to keep the name of the firmware files provided by Sagemcom
unmodified.
6.2.7 - "File / Quit" menu

"File / Quit" menu: after confirmation, closes the Pilot software.
6.3 - SESSION MENU

The "Open Session" and "Close Session" menus are used to open or close a session concerning a
link without exiting the Pilot.
Activate reserve firmware: activates the IDU firmware from the reserve bank.
6.4 - ALARMS MENU 6.4.2 - "Alarms / Text Log / Local or Remote" menu
6.4.1 - "Alarms / View / Local or Remote" menu This menu is used to display two types of record:
This menu is used to display all alarms of the local or remote site. - Alarms: date and time when they were triggered, location, severity, alarm type, appearance or
disappearance information.
- Event log: date and time when the events occurred, location, event type, additional information.
This screen can also be accessed by clicking on one of the alarm Leds on the Pilot front panel or on
the icon at the top left of the screen.
Green Led: no alarm

Red Led: alarm (on the shelf view, the corresponding connector will be surrounded in red)
Grey Led: no corresponding physical elements or alarm indication not required or deactivated alarm. Click on "Save Log" to save the alarm log or the event log on the PC in a .log file which can be kept
for consultation.
The meaning of these alarms, their default severity and the corrective action required are indicated in
7.5.1 -. Click on "Reset Log" to clear all records on the "Alarms" and "Events" tabs simultaneously and start a
new record.
Note: event dating is based on the Pilot clock which has been preferably synchronized on the clock of 6.6 - CONFIGURATION / MANAGEMENT NETWORK / ETHERNET PORTS AND RADIO
the PC connected.
CHANNEL / LOCAL OR REMOTE MENU
6.4.3 - "Alarms /Graphical Log / Local or Remote" menu
6.6.1 - Description of the Management network
SLF-H equipment can be operated via an SNMP type management network, by the Pilot software,
and/or an SNMP manager (IONOS NMS).
The equipment can be managed via the integrated network management interface acting as an IP
router.
MGMT1
Ethernet Network TSL/PPP (to remote IDU)
Switch management
L2 interface
MGMT2
The router has two ports:
- The IDU management Ethernet port (MGMT1 or MGMT2), associated with a MAC address.
This MAC address is unique and non modifiable. An IP address is associated with this MAC
address.
- The radio port (TSL) communicating with the remote IDU via a PPP type protocol. To make the
management system easier to implement, the IP addresses of these ports are managed internally
and are transparent for the user.
This display is the graphical representation of the alarms contained in the equipment log.
To make the terminals easier to identify, a virtual IP address is defined for each terminal (terminal =
In the top part, check the element for which you want to display a graphical analysis; the alarm IDU+ODU). This address will be used by the Pilot software and the network manager to identify the
statuses are plotted in red. terminal. This address is independent of the IDU Ethernet port address and must not belong to the
same subnet.
Zoom in with the mouse wheel if required.
This address is called the Management IP Address.
Click on "Reset Log" to clear all records simultaneously and start a new record. The IDU Ethernet port IP address does not operate with SNMP, since the equipment always answers
with the management address.
Note common to 4.4.2 and 4.4.3: the log information is stored in the IDU flash memory.
The IDU flash memory is limited to 2048 alarm transitions or events. When the log is full, the oldest A SLF-H equipment can be connected via the IDU Ethernet interface to another equipment, whether
alarms or events are overwritten by the most recent. or not SLF-H.
When the equipment is off, the log is kept in the flash memory. To route the datagrams on the various network elements, the routes to reach these elements must be
defined.
A route is defined for an IP network; e.g. 135.11 if the network mask is 255.255.0.0.
6.5 - CONFIGURATION / ALARMS MENU The network entities can exchange their routes using the RIP and OSPF protocols.
This menu is described in 5.6 -. On IDU PPP interfaces, the OSPF protocol is systematically implemented.
On IDU Ethernet interfaces, the user has to define whether or not to involve RIP or OSPF protocols.
Static routes and a default gateway can be also be defined for each IDU.
Network management interface configuration examples

OSPF 2.0.0.2
- One hop link 10.0.0.1 Eth TSL TSL Eth 255.255.255.0
Manager
The manager is connected to the IDU of site A via the Ethernet access. The IDU of site B may be 10.0.0.10
connected to a laptop for local maintenance. 255.255.255.0
192.168.114.11 192.168.114.12
Static route 192.168.114.x
/255.255.255.0 => 10.0.0.1
OSPF 2.0.0.3
Ethernet Site A Site B 10.0.1.1 Eth TSL TSL Eth 255.255.255.0
Laptop PC
Manager 10.0.1.10
255.255.255.0 192.168.114.14 192.168.114.13
Static route 192.168.114.x

OSPF /255.255.255.0 => 10.0.1.1
10.0.0.1
2.0.0.2
Eth TSL TSL Eth
Manager Laptop
10.0.0.10 2.0.0.10
6.6.2 - Network configuration
192.168.114.11 192.168.114.12
- Two hop link
Site A
Ethernet
Manager Site B
Site C
Laptop
The meaning of the configuration parameters is described in the previous paragraph.
On system initialization, the addresses are entered via the serial interface (VT100). These values can
then be modified via the Pilot or the manager, but in this case, note that if an incorrect value is entered
via a remote terminal, it will be impossible to reach the equipment and intervention on site will be
required to put back the correct address.
Port Id: used to display the statuses of the MGMT1, MGMT2 and Wayside ports.
6.6.3 - Wayside configuration 6.7 - CONFIGURATION / MANAGEMENT NETWORK /ROUTES / LOCAL OR REMOTE MENU
The Wayside is a point to point 10/100BaseT Ethernet channel between the local and remote This table lists the IP routes known by the equipment.
equipment. Direct routes are known due to the configuration of the equipment interfaces.
Indirect routes may result from the routing protocol (OSPF or RIP) or definition of a static route.
This access can be physically disconnected by setting the "Wayside transmission" setting to "Off".
To add a static route, click on "Add"
The IP network to be reached is defined by the "Destination Address" and "Subnet Mask" fields.
The "Gateway" field is the equipment address to which network frames will be sent.
If the Ethernet interface is to be used, the Gateway address must be in the Ethernet interface network;
the MAC address of the Gateway will be used to reach it.
If the TSL (PPP) interface is to be used, the Gateway address must be the remote equipment
management address.
Cost: defines the cost of using the route.
There is a maximum of 20 static routes.
6.8 - CONFIGURATION / GIGABIT ETHERNET MENU 6.10 - CONFIGURATION / ATPC / LOCAL OR REMOTE MENU
This menu is described in 5.3 -. This menu is described in 5.7 -.
6.9 - CONFIGURATION / PROTECTION / LOCAL OR REMOTE MENU 6.11 - CONFIGURATION /E1 TRIBUTARIES / LOCAL OR REMOTE MENU
SLF-H IDU is common to the 1+0 and 1+1 configurations. The hardware difference is that the 1+0 IDU This menu is described in 5.4 -.
uses only one Modem while the 1+1 IDU contains two.
There are two ways to establish a 1+1 link: 6.12 - CONFIGURATION / HARDWARE INVENTORY / LOCAL OR REMOTE MENU
- On first installation: with the two Modems inserted in the IDU each Modem being connected its ODU This screen gives the equipment hardware inventory (references, serial numbers, components
a cable. Switch on both Modems to power up the terminal. manufacturing dates) and main ODU features.
- On a 1+0 link already established: there is no need to disconnect the link; install Modem2/ODU2
and switch on the second Modem.
Then, to switch from one configuration to the other, use the Pilot software as described below.
x Click on the protection button of the Pilot screen or open the "Configuration / Protection /
Local or Remote" menu to display the following screen:
x Select the box corresponding to the new configuration and validate.

x If the changeover is refused, there may be a hardware problem or the two ODUs may not be
compatible with the required 1+1 mode (e.g. different ODUs in 1+1 HSB, etc.).
Perform these operations on the local and remote equipment.
Note: it is important to have both terminals in the same configuration. Avoid having the two terminals
in different configurations.
The various system configurations are described in 3.5 -.
Revertive automatic switching Tx: see 5.8 -.
6.13 - CONFIGURATION / PILOT MENU 6.16 - PERFORMANCE / LINK STATISTICS / LOCAL OR REMOTE MENU
This graph displays the link performance log for measurement periods of 1 min, 15 min or 24h, either
in number of seconds or as a percentage of the period.
This menu can be used to display/hide tool tips when pointing the mouse on the various screen
parameters.
6.14 - CONFIGURATION / RESET TO DEFAULT DATABASE / LOCAL OR REMOTE MENU

This menu is used to restore the system factory settings. Only the management network configuration
is kept unmodified, which allows remote configuration of the equipment afterwards.
6.15 - PERFORMANCE / RSL / LOCAL OR REMOTE MENU

This graph displays the ODU minimum and maximum RSLs over time and the number of seconds
during which the high and lower configurable thresholds have been crossed.
Quality processing is carried out by calculating and determining various states: ES (Errored Second),
SES (Severely Errored Second) and UAS (UnAvailable Second).
Quality counters ES, SES and UAS:
The quality counters are as follows:

ES (Errored Seconds): number of seconds with at least one error detected within a period of 1 s or
a fault.
SES (Severely Errored Seconds): number of severely errored seconds
An SES is a second during which the number of errors exceeds the threshold defined or during
which at least one fault is detected.
UAS (UnAvailable Second): number of unavailable seconds.
Clear: clears the graph and starts a new display.
Clear: clears the graph and starts a new record.
6.17 - PERFORMANCE / GIGABIT ETHERNET / GENERAL ETHERNET STATISTICS / 6.18 - PERFORMANCE / GIGABIT ETHERNET / METERING STATISTICS / LOCAL OR
LOCAL OR REMOTE MENU REMOTE MENU
This menu displays the statistics counters of the Ethernet ports. The IDU board supplies counters indicating the quantity of valid (green) and unvalid (yellow) traffic
received for each Classification (or service).
A total of 16 probes are available. For each classification or service, a probe can be activated or not.
The configuration window displays a summary of configured classifications, and allow probe
configuration.
To enable/disable a probe, select the target classification in the list displayed on the top of the
window, and click on the "enable"/"disable button". A counter displays the total number of
enabled probes.
To view counter for a probe, select the corresponding classification in the list, the probe
information are then displayed in the bottom part of the window.
Refresh: allows you to update counter values. (Refresh is done automatically every few seconds).
Reset: resets the counters and starts a new count.
6.19 - PERFORMANCE / WAYSIDE / LOCAL OR REMOTE MENU

Reset counters: resets the counters and starts a new count.
This menu is used to display the number of bytes transmitted and received on the Wayside Ethernet
Refresh: allows you to update counter values. (Refresh is done automatically every few seconds).
port.
6.21 - PERFORMANCE / CLEAR/RESET ALL

This menu resets all the local and remote counters: "RSL" performances, "link statistics"
performances, "GigaEthernet" performances, "Wayside" performances, BER indicators; it also clears
the alarms and events logs. New counts start.
Reset counters: resets the counters and starts a new count.

Refresh: allows you to update counter values. (Refresh is not done automatically).
6.20 - PERFORMANCE / CLEAR BER STATS / LOCAL OR REMOTE MENU

This menu resets the local or remote BER counters and starts new counts. 6.22 - MAINTENANCE / TX/RX FORCING MENU
Only active for 1+1 links, this menu can be used to perform manual transmit or receive switching. It is
also possible to click on "Tx" in the main screen.
Transmit and Receive switches are independent. A system can work with ODU (1) transmitting, and
ODU (2) receiving.
In normal position "Tx Auto", "Rx Auto", "Mst Auto", switching is carried out automatically.
The "Tx 1/2", "Rx 1/2", "Mst 1/2" forcings are used for maintenance actions.
In manual mode, the equipment is in maintenance mode (maintenance indication at the bottom of the
Pilot screen, orange Led "Maint" on the Pilot screen and orange Led lit on the IDU front panel).
To perform manual switching commands (forcing), click on the box corresponding to the transmitter,
receiver or master to be activated and validate with OK.
The main Pilot screen indicates the active transmitter and master.
The active transmitters and masters are shown in bold.

Forced configurations appear in red and trigger the maintenance display.
6.25 - MAINTENANCE / TRY TO UNMUTE REMOTE / LOCAL OR REMOTE MENU
This menu is not permanent; it is displayed when the radio link has been lost (no received signal) and
6.23 - MAINTENANCE / LOOPBACKS MENU local transmit part suffer no critical issues. Clicking on this menu entry will try to remove mute on
remote equipment (if any), provided the remote equipment has a correct matching radio configuration
This menu is used to make loopbacks on the 2 Mbit/s channels (see 5.4 -) or on the resulting signal. (frequencies, bandwidth, modulation, number of E1, link id).
x Equipment Loopback On: active a local Equipment loopback provided that there is no The bar at the bottom of the Pilot screen can be used to access this menu.
loopback on E1 ports. An Equipment loopback (IDU card) operates in the same way as a
tributaries loopback, except that they are carried out on the resulting frame. This loopback is
used to test Equipment operation. 6.26 - MAINTENANCE / RESTRICTION / LOCAL OR REMOTE MENU
x Equipment Loopback Off: can set the time after which the closures will be automatically
deleted. This menu is used to extend the flow transmitted by SLF-H. Indeed, according to the need, the
equipment can be ordered with the following options:
x Equipment timer: remove all Equipment loopback.
Radio channel
Modulation 7MHz 14MHz 28MHz 56MHz
6.24 - MAINTENANCE / FREQUENCY SCAN / CHANNEL 1 OR CHANNEL 2 MENU QPSK
16QAM
This menu is used to carry out a frequency scan around the receive frequency, in order to identify 32QAM
possible radio interferers. 64QAM
The measurements results are displayed graphically and stored in memory for future consultation. 128QAM
256QAM * *
The process is carried out separately on each terminal. The user defines the frequencies to scan. The
local transmitter is muted, while the receiver measures the Receive Signal Levels for each frequency. 70Mbps License * = not available in ACM mode
150Mbps License
Clicking on the "Frequency scan" menu displays the following window: 300Mbps License
400Mbps License
4 licenses are available for the modulation/bandwidth available. An additional license allows using
ACM feature. In ACM, the limitation for available modulation restricts the maximum configurable
profile.
See Table 4-2 and Table 4-2 for the list of the accessible configurations in each license.
5BOPERATION PILOT
It is possible to upgrade to a higher capacity or enabled ACM by purchasing a new license. A software
code supplied by Sagemcom is used to update the terminal. A code depending on the Modem serial
number must be entered Modem by Modem (2 codes for a 1+1 configuration).
A window indicates the current maximum configuration for each Modem (modulation / radio
bandwidth).
Please note that in 1+1 configuration, the lower Modem configuration is taken into account to enforce
the limitation.
When using the Expansion chassis MUX64 SPDH, the number of available E1 tributaries can be
extended also. The total number of E1 can be 32, 48, 64 or 80.
To extend the number of E1 a license must be bought. A software code provided by Sagemcom
allows updating the terminal. A code based on the MUX64 SPDH serial number must be entered.
The bottom part of the window contains a textbox that can be copied for easy request of new licenses.
Note: the keyword "none" displayed next to a restriction entry state that there is no restriction (so
everything is available up to the capacity of the hardware).
6BTROUBLESHOOTING GUIDE 6BTROUBLESHOOTING GUIDE
7. TROUBLESHOOTING GUIDE 7.3 - TROUBLESHOOTING PROCEDURE

The goal is to make a precise diagnostic of the problem, in order to determine the faulty unit quickly
and replace it.
7.1 - INTRODUCTION
This paragraph helps you solve problems using the information available (front panel Leds and Pilot 7.3.1 - Describe the symptom
software) and describes the procedures for replacing defective units.
This is generally made by the field technician: common symptoms are "the link is broken", "there are
excessive transmission errors", "there are alarms", etc.
Main points discussed These symptoms may be permanent (failure) or intermittent. The alarm and event data and the
graphic records available in the Pilot can generally be used to improve the diagnostic ( 6.4 -).
x Visual inspection
x Description of front panel alarm Led operation 7.3.2 - Isolate the problem
x Troubleshooting procedure
x Alarms managed by the Pilot Once the symptom has been defined, the faulty unit can be isolated using information supplied by the
x Typical screens in case of problem Leds on the IDU front panel and the information available on the Pilot.
x Replacing an ODU SLF-H replacement units are the ODU, the IDU (without Modem and without FAN), the Modem, the
x Replacing a Modem FAN drawer, the MUX64 SPDH shelf.
x Replacing an IDU A 1+0 link is composed of several units. The goal of this step is to determine what the most probable
unit to replace is.
The difficulty is that, in some cases, the problem may be generated by the remote terminal, external
Measurement equipment required equipments (power supplies, bad interface signal levels, etc.) or the external environment (path
obstruction, radio interferers, severe climatic conditions, etc.).
x Laptop with serial port
x Pilot software 7.3.3 - Fix the problem
x Gigabit Ethernet tester
x 2 Mbit/s transmission analyzer (optional) Once the problem has been isolated, it is important to understand its cause and to apply corrective
x Digital multimeter actions to avoid reoccurrence of the problem.
Some typical problems are described in 7.6 -.

7.2 - VISUAL INSPECTION
Before starting the operation, it is important to perform a visual inspection of the terminal and its 7.4 - DESCRIPTION OF IDU FRONT PANEL LEDS
installation.
The Leds on the IDU Front panel and the Modem are shown below:
Visual inspection Look for Actions

IDU / ODU coaxial cable Cuts, short circuits, moisture in Clean or repair
connectors
IDU, ODU and MUX64 SPDH shelf Dust, humidity, lightning strike Clean or replace
damage Clean the fans regularly
Alarms (front panel and Pilot) No red Leds lit If some alarms are red, use this
troubleshooting guide ( 0 and 7.5
-) GbE Lnk/Act
EM
L
Maint
U
1 2 3 4
OD
Receive Signal Level (Pilot) Nominal value (installation data) Realign antenna, check remote FAN
M
RS
OD
terminal transmit power idu

Power supply voltage Within specified range Replace power supply trib POWER
Antenna mounting Tight mount Mount antenna correctly
ext
Figure 7.1 - IDU front panel Leds
7.4.1 - IDU Leds 7.5 - ALARMS MANAGED BY THE PILOT

The Pilot software provides more details than the Leds on the front panel of the equipment.
x "maint" Led is orange during a maintenance operation (remote loopback, manual control of 1+1
switching). It is off in normal mode.
7.5.1 - Alarm summary screen
x "idu" Led is red when there is multiplexer or a demultiplexer failure, when receive data is not
recovered (link broken), or if there is no fan drawer installed.
Click on the "Alarms / View / Local or Remote" menu to access the alarm summary screen. The
x "trib" Led is red if there is no input signal on a tributary configured as normal, or if there is an active alarms are red.
input signal on a tributary configured as inverted.
This screen can also be accessed by clicking on one of the alarm Leds on the main Pilot screen.
x "ext" Led is red if there is a status change on one of the external alarms which have been
associated with this Led (see 5.6 - for a description of this alarm). Click on the icon at the top left of the screen to access the local alarm display window.
x "GbE Lnk/Act" Leds 1 to 4 are dedicated to the Gigabit Ethernet transmission

Led off: link down
Green Led lit permanently: link up
Green Led flashing: traffic indicator, flashes for each GE frame
Orange Led lit: collision
x The "FAN" Led is red if the FAN module or one of the fans is faulty.
7.4.2 - Modem Leds
x The "MODEM" Led is red if there is a problem on the ODU cable, if the modulator, demodulator
or power supply is faulty, or if the link is down (no received data).
x The "RSL" Led is red if the level received by the ODU is below the programmed threshold, or if
there is a BER alarm (BER alarm, or BER warning). In most cases, this alarm corresponds to a
propagation or radio interferer problem.
x The "ODU" Led is red if there is an ODU alarm or if an ODU is not connected (cable problem).
The Led is also red if the ODU is muted on a 1+0 link or if the two ODU of a 1+1 link are muted.
x The "POWER" Led is green when the Modem is powered up.
7.4.3 - Leds of the MUX64 SPDH shelf
x If an E1 extension MUX64 SPDH shelf is connected with the IDU and powered up, the "PWR"
Led of this shelf is green after startup of the IDU.
Figure 7.2 - Alarms screen on the Pilot
Green Led: no alarm

Red Led: alarm (on the shelf view, the corresponding connector will be surrounded in red)
Grey Led: no corresponding physical elements or alarm indication not required
The meaning of these alarms, their default severity and the corrective action required are indicated in
the following tables.
Leds on the Default alarm

IDU alarms Description Corrective actions
equipment severity
Wayside No input signal Wayside port Led None Check cable Fan /
( 3.7.2.4 -) temperature Description Corrective actions
equipment severity
alarms
Fans This alarms is triggered if there a fan or
Table 7-1 - Meaning of the Wayside alarm FAN
FAN module fault or if there is no fan Major Replace faulty or missing unit.
idu (absence)
drawer
Radio link Leds on the Default alarm IDU This alarm is triggered when the IDU
Description Corrective actions Look for the possible alarm causes: IDU faulty or room
alarms equipment severity Temperature temperature is greater than the FAN Major temperature too hot.
Link ID This alarm is present if local and remote Check that the remote terminal has the same Link ID. If maximum permitted value
ID Codes do not match. The receive data the Link IDs of the 2 terminals do not match, they are
is replaced by an AIS. displayed in red on the main Pilot screen; if identical they Modem 1 This alarm is triggered when the
IDU Minor Temperature temperature of the Modem 1 is greater Look for the possible alarm causes: IDU or Modem 1
are displayed in black. If the alarm remains, another link FAN Major
than the maximum permitted value faulty or room temperature too hot.
operating at the same frequency may be disturbing the
link.
Modem 2 This alarm is triggered when the
Link Status This alarm indicates that the dialog is Temperature temperature of the Modem 2 (1+1 Look for the possible alarm causes: IDU or Modem 2
Depends on alarm Examine the various alarms on the 2 terminals of the link FAN Major
interrupted between local and remote Major configuration) is greater than the faulty or room temperature too hot.
origin to improve the diagnostic
equipment maximum permitted value
Rx Frame Indicates that the INT demultiplexer is Depends on alarm Examine the various alarms on the 2 terminals of the link
Major
unlocked origin to improve the diagnostic
Table 7-4 - Meaning of Fan and Temperature alarms
Table 7-2 - Meaning of radio alarms

SPDH alarms Description Corrective actions
equipment severity
SPDH state SPDH equipment is not responding to Depends on alarm Major Check power supply of SPDH equipment. Check the
IDU board. origin cable between IDU and SPDH equipments. If alarm is still
present, power down the SPDH and IDU, and apply
power to SPDH and then IDU. If alarm is still present,
replace SDPH equipment
Table 7-3 - Meaning of the SPDH alarm

ODU alarms Description Corrective actions
equipment severity
Leds on the Default alarm RSL (Receive This alarm is generated when the RSL is
Modem alarms Description Corrective actions
equipment severity Signal Level) below the programmed threshold (default
Demodulation This alarm is generated if there is a threshold: -60 dBm). It may also be Use the indications on the remote terminal such as RSL
Check all alarms on both terminals to find the cause of RSL Minor
demodulator fault or if received data is MODEM Major generated in case of a power problem on and alarms to make a diagnostic.
the problem, as well as possible propagation problems.
not recovered a remote transmitter, a propagation
Modulation This alarm is generated if there is problem, or a faulty receiver.
modulator fault. When a modulation Power supply Power supply alarm returned by the
MODEM Major Replace the Modem Check power supply voltage (-48 V) and cable losses. If
alarm occurs, the transmitter is ODU. This alarm indicates an ODU
ODU Minor the power supply voltage and the cable are OK, replace
automatically muted. power supply fault or input voltage too
the ODU
BER alarm This alarm is generated when BER is low
greater than the programmed threshold Cable Cable alarm returned by the ODU. This
Check other parameters such as the RSL, remote
(default 10-3). A BER alarm can be MODEM, RSL Major alarm is generated if the transmit IF level Check IDU / ODU cable losses.
terminal alarms and possible propagation problems.
generated by a poor receive level, a at ODU input is outside the limits. This ODU Minor
Modem fault or radio interference alarm causes the transmitter is Replace the Modem or the ODU.
BER warning This warning is generated when BER is automatically switched off (Mute).
Check other parameters such as the RSL, remote
greater than the programmed threshold MODEM, RSL Minor Tx Frequency This alarm is generated in case of
terminal alarms and possible propagation problems.
(default 10-6). transmit synthesizer fault. This alarm ODU Major Replace the ODU
Power supply Power supply alarm returned by the Check power supply voltage -48 V at the IDU input: automatically mutes the transmitter.
Modem. This alarm indicates a Modem the measured value must be included between -39V and Rx Frequency This alarm is generated in case of
MODEM ODU Minor Replace the ODU
power supply fault or input voltage too Major -59V. receive synthesizer fault.
low at the IDU input. If alarm remains present, change the Modem. Tx Power A transmit power alarm is generated in
ACM Current modulation profile is below the Check the configured threshold for this alarm. Check case of a transmitter AGC loop fault, or
MODEM Minor
Modulation configured threshold. radio conditions. in case of a transmitter mute set by the
ODU Minor Replace the ODU
operator (in 1+1 system when both
transmitters of a terminal are in mute
Table 7-5 - Meaning of Modem alarms position).
Mute Tx Power alarm present If the transmitter was not muted intentionally and the fault
ODU Minor
remains, replace the ODU
Table 7-6 - Meaning of ODU alarms
Gigabit External Leds on the Default alarm

Leds on the Default alarm Description Corrective actions
Ethernet Description Corrective actions alarms equipment severity
equipment severity
alarms External alarms (local terminal incoming
SFP Presence Module absent Gbe Lnk/Act off Local External loops), alarms concerning the 5 local
Major Plug in the module correctly or replace it of faulty ext Major Check generating event: e.g. door open, etc.
Alarms external alarm inputs configured (see
SFP Type The SFP module inserted do not match Insert the correct module or change the configuration 5.6.2 -)
Gbe Lnk/Act off Major
Mismatch with the expected configured type (Gbe Lnk/Act equipment might be on in this case) External alarms (remote terminal
Remote
SFP LOS Loss of input signal or auto negotiation Check Ethernet cable (fiber or RJ45) and connected incoming loops), alarms concerning the 5
Gbe Lnk/Act off Major External ext Major Check generating event: e.g. door open, etc.
failed equipment configuration remote external alarm inputs configured
Alarms
(see 5.6.2 -)
SFP Tx Default Ethernet link assembly fault (e.g. auto Make sure that the Ethernet link cable (fiber or RJ45) is
Gbe Lnk/Act off Major
nego FAIL, cannot transmit in Tx) not faulty. Also check the SFP module. Table 7-9 - Meaning of External alarms
Tx Mute In ACM mode, current profile is below
configured minimum for Ethernet radio None Minor Check radio conditions. Minimum profile can be reduced.
port
Ge Bitrate In ACM mode, current available
Check the alarm configured threshold. Check radio
bandwidth for the Ethernet radio port is None Minor
conditions.
below the configured threshold
Table 7-7 - Meaning of Gigabit Ethernet alarms
E1 tributary Leds on the Default alarm

Description Corrective actions
alarms equipment severity
Trib Alarm This alarm is generated when there is no
input signal for a tributary configured as Check tributary alarm configuration, cable continuity and
normal (N), or when there is an input trib Major presence of signal at output of equipment connected to
signal for a tributary configured as SLF-H.
inverted (I).
Table 7-8 - Meaning of E1 Tributary alarms
Check that that the IDU is powered correctly and that the Ethernet cable between the PC and the IDU is
7.5.2 - Direct and indirect alarms correctly installed. Try to ping equipments all along the network path to reach IDU.
There are two types of alarm in a microwave radio link:
x Direct alarms which occur when there is a fault on a unit (e.g. transmit frequency alarm). 7.6.3 - No local radio
x Indirect alarms caused by a fault on another unit or by an external problem to determine the The IDU is recognized by the Pilot, but the ODU does not operate: absent, faulty or not answering the
cause of an indirect alarm, analyze all possible causes of the alarm and select the most likely. IDU requests. In this case, the typical Pilot screen is as follows:
7.5.3 - Event log

In some cases with transient faults, it may be worthwhile examining the graphic log available and the
alarm or event data to determine the cause of the fault ( 6.4 -).
7.6 - TYPICAL SLF-H PILOT SCREENS IN CASE OF PROBLEM

The following screens are representative of some typical problems.
7.6.1 - No IDU-Pilot software communication

When connecting the IDU to the PC, the following screen may be displayed:
Check the cable between IDU and ODU. If the problem remains, replace the ODU or the Modem.
7.6.4 - No remote radio

The local terminal operates correctly but communication with the remote terminal is down. In this case,
the typical Pilot screen is as follows:
The Pilot cannot communicate with the IDU. Check the Ethernet cable between IDU and PC and check
that the IP addresses and subnet masks of the PC and the IDU are compatible. From the PC, ping the
IDU Ethernet address. If the ping result is negative, change the IP address of the PC or of the IDU
Ethernet port (see 4.2 -).
7.6.2 - No local equipment, no remote equipment

If the connection between PC and IDU breaks during a Pilot session, the Pilot displays the following
screen:
Check the remote terminal configuration (frequency, capacity, modulation, transmit power), correct
antenna alignment and possible presence of obstacles between the two antennas.
In the bottom bar, the software suggests trying to "unmute" the remote equipment, which could be one
of the reasons why it fails to operate. Go to the maintenance menu to access this command.
7.6.5 - Low RSL 7.6.7 - Link established correctly but with some alarms
The link is established but the RSL is low. The typical Pilot screen is as follows:
Check the alarm configuration ( 5.6 -).
Check antenna alignment, transmit power levels and make sure that the fault is not due to a temporary
propagation problem.
7.6.8 - Normal link no alarms
The link is established without alarms. All Leds are green.
7.6.6 - Low transmit power
The RSL of one of the two terminals is too low with respect to the other terminal. In this case, the typical
Pilot screen is as follows:
7.7 - REPLACING AN ODU

Apply the following procedure:
Increase the transmit power if possible. If the problem remains, replace the ODU on the site with the 1- Disconnect the IDU/ODU cable at IDU Modem output.
doubtful transmitter. 2- Before removing the ODU, note the position of the arrow on the ODU cover, disconnect cable.
3- Replace the ODU with another one of the same type according to the installation procedure ( 3.5 -),
respecting the polarization (arrow in the same position as before). Replace the gasket (antenna or
coupler interface) if damaged.
4- Connect the cable and protect the connector with isolation tape.
5- Connect the cable on the IDU side.
Remark: it is not necessary to cut off the power supply of the IDU (switch Modem off) to carry out this
operation.
Note: for a 1+1 system, an ODU can be replaced with the second one operating. Before replacing an ODU,
select manual switching Tx and Rx on the transmitter and the receiver, which continue to operate (see
6.22 -). It is useless to force the Master channel (leave master channel configured to automatic).
Once the change has been done, return to automatic switching.
6BTROUBLESHOOTING GUIDE
7.8 - REPLACING A MODEM

1- Switch off the Modem connected to the ODU (check that the green Modem Led is off).
2- Disconnect the ODU cable (IDU side).
3- Remove the two screws.
4- Remove the Modem and replace by a new one.
5- Attach the Modem with the screws and connect the cable to the ODU.
6- Power up the Modem.
Note: for a 1+1 system, a Modem can be replaced with the second one operating. Before replacing it,
select manual switching Tx, Rx and Master on the transmitter and the receiver, which continue to operate
(see 6.22 -).
Once the change has been done, return to automatic switching.
7.9 - REPLACING AN IDU

1- Load the configuration file saved previously to avoid having to reconfigure everything (see 6.2 -).
2- Switch off the Modem(s).
3- Remove all cables from the IDU.
4- Remove the IDU.
5- Remove the Modem(s) from the IDU and install them in the new IDU.
6- Install the new IDU and reconnect all cables.
7- Switch on the IDU, reconfigure network access using the VT100 serial link.
8- Connect a Pilot and load the previously saved configuration file.
7.10 - REPLACING A FAN MODULE

1- Remove the two screws.

2- Remove the FAN module and replace by a new one.
3- Attach the FAN module with the screws
4- Wait a few seconds and make sure the FAN speed is regulated and that there is no alarm
Note: the FAN module is fully hot-extractible and hot-pluggable.
7.11 - REPLACING A MUX64 SPDH SHELF

1- Switch off the Modem(s).

2- Disconnect from the MUX64 SPDH shelf the power supply cable then the 2 Mbit/s interface cable
("Trib extension" connector) connected to the IDU.
3- Replace the MUX64 SPDH shelf.
4- Connect again the 2 Mbit/s interface cable then the power supply cable.
5- Switch on the Modem(s).
APPENDIX 1- SLF-H SPECIFICATIONS APPENDIX 1- SLF-H SPECIFICATIONS
APPENDIX 1- SLF-H SPECIFICATIONS Modulation (fixed and ACM) QPSK, 16QAM, 32QAM,
(ODU-HL / ODU-H / ODU-NL) 64QAM, 128QAM, 256QAM
Modulation (fixed) QPSK, 16QAM, 32QAM

General characteristics (ODU-N)
Tx-Tx spacing 7MHz, 14 MHz, 28 MHz, 56 MHz

Versions and configurations Frequency bands 6L, 6H, 7, 8, 11, 13, 15, 18, 23, 26, 32, (ODU-HL / ODU-H)
38 GHz
Bitrates Giga Ethernet 1000BaseSX, 1000BaseLX, Tx-Tx spacing 7MHz, 14 MHz, 28 MHz
10/100/1000BaseT (ODU-NL / ODU-N)
10/100BaseT Ethernet
0, 2, 4 8, 16, 32, 48, 64, or 80 x 2 Mbit/s Error-correcting code LDPC
Radio configuration (protection) 1+0 Unprotected Frequency agility see APPENDIX 2 and 1.2.6 -
1+1 Hot standby (HSB)
1+1 Space or frequency diversity
2+0 XPIC or frequency diversity
Transmission characteristics
Applicable ETSI standards All bands EN 302 217
Frequency bands 6 GHz (6L) * 5.9 GHz - 6.4 GHz QPSK 16QAM/32QAM 64QAM/128QAM 256QAM
6 GHz (6H) * 6.4 GHz - 7.1 GHz Output power Please refer to Please refer to Please refer to Please refer to
* = ODU-H only 7 GHz 7.1 GHz - 7.7GHz the Performance the Performance the Performance the Performance
sheets sheets sheets sheets
8 GHz 7.7 GHz - 8.5 GHz
11 GHz 10.7 GHz - 11.7 GHz
Power step 0.5 dB 0.5 dB 0.5 dB 0.5 dB
13 GHz 12.75 GHz - 13.25 GHz
15 GHz 14.4 GHz - 15.35 GHz
Automatic Tx Power Control
18 GHz 17.7 GHz - 19.7 GHz (ATPC algorithm)
23 GHz 21.2 GHz - 23.6 GHz Dynamic range Max Power Min Power
26 GHz 24.5 GHz - 26.5 GHz
32 GHz 31.8 GHz - 33.4 GHz Output power with Transmit <-50 dBm <-50 dBm <-50 dBm <-50 dBm
38 GHz 37 GHz - 39.5 GHz Mute "
Duplex spacing 6 GHz (6L) * 240, 252.04 MHz Frequency step 250 kHz 250 kHz 250 kHz 250 kHz
6 GHz (6H) * 340 MHz
* = ODU-H only 7 GHz 154, 160, 161, 168, 196, 245 MHz, Frequency stability 10 ppm 10 ppm 10 ppm 10 ppm
8 GHz 119, 126, 151.614, 208, 266, 311.32 MHz
11 GHz 490, 500, 530 MHz
13 GHz 266 MHz
15 GHz 315, 420, 475, 490, 640, 644, 728 MHz
18 GHz 1010, 1560 MHz
23 GHz 1008, 1200, 1232 MHz
26 GHz 800, 1008 MHz
32 GHz 812 MHz
38 GHz 700, 1260 MHz
SLF-H Installation and Operation Manual 253 255 964-D Page A1-1 Page A1-2 SLF-H Installation and Operation Manual 253 255 964-D
Gigabit Ethernet / 2 Mbit/s access

Reception characteristics
Giga Ethernet 1 to 4 GE, 1000BaseSX optical SFP, 1000BaseLX, 10/100/1000BaseT electrical SFP
Maximum non destructive level at ODU input -10 dBm 2 Mbit/s 0, 2, 4 8, 16, 32, 48, 64 or 80 x2 Mbit/s / 120 : or 75 : - IUT-R G. 703 2xDB44HD
Maximum level for BER < 10-6 -22 dBm +4xDB78HD
1+1 coupler losses - 3 dB (channel 1/channel 2) 3.5 dB / 3.5 dB
1+1 coupler losses - 6 dB (channel 1/channel 2) 2 dB / 6.5 dB Alarms, wayside and network management interfaces
-12 -6
Residual error rate < 10 When receive signal level is 5dB above the 10 Number Type
threshold and less than -30dBm Alarm relays (outputs) 3 DB15 HD
Analog RSSI voltage (ODU BNC connector) 4.5V 20 dBm; 0.1V 90 dBm, courbe monotone External alarms (inputs) 5 DB15 HD
Loi de variation: RSL (dBm) = 15.77 VBNC-91.58
RSSI voltage accuracy 3 dB Wayside Interface Ethernet 10/100BaseT RJ45
1
RSL indication accuracy (from the Pilot) 3 dB
VT100 interface 1 Access PC RS232 DB9
Network management interfaces 2 (Integ. Hub) Interfaces Ethernet 10/100BaseT, RJ45
Mechanical characteristics
Dimensions
Station shelf (IDU) 1U, 19 inches : 44(H) x 485 (L) x 300 (D) mm
Radio box (ODU) Diameter: 267 mm, Depth: 89 mm
Optional MUX64 SPDH 0.6U, 19 inches : 26(H) x 485 (L) x 170 (D) mm
Weight
IDU without TNM and without Modem 3.050 Kg
IDU with TNM and without Modem 3.250 Kg
MODEM 0.376 Kg
FAN module 0.270 Kg
Optional MUX64 SPDH 1.9 Kg
Radio box (ODU-H / ODU-N) 5 kg
Radio box (ODU-HL / ODU-NL) 4 kg
Installation
Station shelf (IDU) 19 inches rack
Radio box (ODU) Tubes diameter 50 mm to 115 mm
Optional MUX64 SPDH 19 inches rack
IDU/ODU interconnection
1+0 1 coaxial cable
1+1 2 coaxial cables
Impedance 50 :
Length Maximum attenuation of 18dB at 350MHz
Power consumption 4m
Input voltage -39 V to -59 V
Power consumption IDU only < 15W (typ.: 8.5W)

TNM < 7W (typ.: 5W)
MODEM < 20W (typ.: 15W)
FAN module < 10W (typ.: 6W)
Optional MUX64 SPDH < 30W (typ.: 25W)
Example: IDU-H/1+0/GE without TNM Typical = 29W
ODU-HL <40W (typ.: 30W) Antenna diameter: 0.3 up to 0.75 m:

region with exposure > 10 W/m
ODU-H < 50W (typ.: 40W)
ODU-NL <35W (typ.: 25W) Note: with antenna diameters greater than 0.75m, the 10W/m is not reached.
ODU-N <45W (typ.: 35W)
Environmental characteristics
Environmental conditions IDU, MUX64 SPDH EN 300 019-1-3 class 3.1

ODU EN 300 019-1-4 class 4.1
Temperature range IDU, MUX64 SPDH -5C to +45C

ODU -33 C to +55C
Storage conditions EN 300 019-1-1 class 1.1

(equipment packed)
Transport conditions EN 300 019-1-2 class 2.3

(equipment packed)
Electromagnetic compatibility EN 301 489-1/4
Health characteristics
This chapter gives the safety distance from the antenna, according to R&TTE Art 3.1a EMF Effects on
Health.
The maximum exposure limit figures to consider are 50 W/m (occupational), or 10 W/m (general public).
The radiation exposure depends on transmit power value, on antenna gain and on the distance from the
antenna.
The analysis and below result takes the worst case: maximum transmit power and radiation on the antenna
axis.
APPENDIX 2 - SLF-H REFERENCES APPENDIX 2 - SLF-H REFERENCES
APPENDIX 2 - SLF-H REFERENCES

References of ODUs HL
Link composition It covers channel bandwidth from 7MHz to 56MHz and modulation schemes from QPSK to 256QAM.
Depending on the configuration, a SLF-H link is composed of the following items:

Transmit Range T to R Diplexer
Sagem Model Sagem Min Freq Max (MHz) Range
ODU-H MODEM-H IDU-H Sagem Description
Number P/N (MHz) Freq (MHz)
HB LB wo wo wo wo wo GE GE+ 16E1 SFP FAN
(MHz)
7 GHz ODUs
SLF-H
CHB07-YYYY-XX-00 ODU SLH 07GHZ TR YYYY LO XX
(070)
(070)
UHBxx
UHHxx
ODU SLH 07GHZ TR YYYY HI XX
SW150
SW300
SW400
CHH07-YYYY-XX-00
UFF P2
SFP GE
UFDxxCy : Coupler
UFX_SP P2
UFC_HX P2
UFX _SP P2
+ UFE_16E1
UFC_HW P2
(optional ACM)
(optional ACM)
(optional ACM)
GE / 70 Mbps 1 1 2 2 2 2 CHB07-A154-01-00 253375691 ODU SLH 07GHZ TR A154 LO B1 7,428.0 7,484.0 154 56
GE + 16 E1 / 70 Mbps 1 1 2 2 2 2 CHH07-A154-01-00 253375703 ODU SLH 07GHZ TR A154 HI B1 7,582.0 7,638.0 154 56
GE / 150 Mbps 1 1 2 2 2 2 2 CHB07-A154-02-00 253375711 ODU SLH 07GHZ TR A154 LO B2 7,470.0 7,526.0 154 56
GE + 16 E1 / 150 Mbps 1 1 2 2 2 2 2 CHH07-A154-02-00 253375724 ODU SLH 07GHZ TR A154 HI B2 7,624.0 7,680.0 154 56
1+0
GE / 300 Mbps 1 1 2 2 2 2 2 CHB07-A154-03-00 253375732 ODU SLH 07GHZ TR A154 LO B3 7,512.0 7,568.0 154 56
GE + 16 E1 / 300 Mbps 1 1 2 2 2 2 2 CHH07-A154-03-00 253375745 ODU SLH 07GHZ TR A154 HI B3 7,666.0 7,722.0 154 56
GE / 400 Mbps 1 1 2 2 2 2 2
GE + 16 E1 / 400 Mbps 1 1 2 2 2 2 2 7,128.0 7,184.0 154 56
CHB07-B154-01-00 253375753 ODU SLH 07GHZ TR B154 LO B1
GE / 70 Mbps 2 2 4 2 2 2 2
1+1 CHH07-B154-01-00 253375766 ODU SLH 07GHZ TR B154 HI B1 7,282.0 7,338.0 154 56
HSB GE + 16 E1 / 70 Mbps 2 2 4 2 2 2 2
CHB07-B154-02-00 253375774 ODU SLH 07GHZ TR B154 LO B2 7,170.0 7,226.0 154 56
(1 GE / 150 Mbps 2 2 4 4 2 2 2 2
CHH07-B154-02-00 253375787 ODU SLH 07GHZ TR B154 HI B2 7,324.0 7,380.0 154 56
antenna GE + 16 E1 / 150 Mbps 2 2 4 4 2 2 2 2
port) GE / 300 Mbps 2 2 4 4 2 2 2 2 CHB07-B154-03-00 253375795 ODU SLH 07GHZ TR B154 LO B3 7,212.0 7,268.0 154 56
(3 or 6 GE + 16 E1 / 300 Mbps 2 2 4 4 2 2 2 2 CHH07-B154-03-00 253375807 ODU SLH 07GHZ TR B154 HI B3 7,366.0 7,422.0 154 56
dB
GE / 400 Mbps 2 2 4 4 2 2 2 2
coupler)
GE + 16 E1 / 400 Mbps 2 2 4 4 2 2 2 2 CHB07-C154-01-00 253375815 ODU SLH 07GHZ TR C154 LO B1 7,135.0 7,198.0 154 63
GE / 70 Mbps 2 2 4 2 2 2 CHH07-C154-01-00 253375828 ODU SLH 07GHZ TR C154 HI B1 7,289.0 7,352.0 154 63
1+1 SD
or FD or GE + 16 E1 / 70 Mbps 2 2 4 2 2 2 CHB07-C154-02-00 253375836 ODU SLH 07GHZ TR C154 LO B2 7,163.0 7,226.0 154 63
2+0 FD GE / 150 Mbps 2 2 4 4 2 2 2 7,317.0 7,380.0 154 63
(2
CHH07-C154-02-00 253375849 ODU SLH 07GHZ TR C154 HI B2
antenna GE + 16 E1 / 150 Mbps 2 2 4 4 2 2 2 CHB07-C154-03-00 253375857 ODU SLH 07GHZ TR C154 LO B3 7,191.0 7,254.0 154 63
ports) GE / 300 Mbps 2 2 4 4 2 2 2
without CHH07-C154-03-00 253375860 ODU SLH 07GHZ TR C154 HI B3 7,345.0 7,408.0 154 63
pole GE + 16 E1 / 300 Mbps 2 2 4 4 2 2 2 CHB07-C154-04-00 253375878 ODU SLH 07GHZ TR C154 LO B4 7,219.0 7,282.0 154 63
mounting, GE / 400 Mbps 2 2 4 4 2 2 2
coupler CHH07-C154-04-00 253375881 ODU SLH 07GHZ TR C154 HI B4 7,373.0 7,436.0 154 63
GE + 16 E1 / 400 Mbps 2 2 4 4 2 2 2
GE / 70 Mbps 2 2 4 2 2 2
CHB07-A160-01-00 253375899 ODU SLH 07GHZ TR A160 LO B1 7,433.5 7,496.5 160 63
2+0 XPIC GE + 16 E1 / 70 Mbps 2 2 4 2 2 2
(2 CHH07-A160-01-00 253375901 ODU SLH 07GHZ TR A160 HI B1 7,593.5 7,656.5 160 63
GE / 150 Mbps 2 2 4 4 2 2 2
antenna CHB07-A160-02-00 253375914 ODU SLH 07GHZ TR A160 LO B2 7,478.5 7,541.5 160 63
ports) GE + 16 E1 / 150 Mbps 2 2 4 4 2 2 2
without GE / 300 Mbps CHH07-A160-02-00 253375922 ODU SLH 07GHZ TR A160 HI B2 7,638.5 7,701.5 160 63
2 2 4 4 2 2 2
pole
mounting, GE + 16 E1 / 300 Mbps 2 2 4 4 2 2 2 CHB07-A160-03-00 253375935 ODU SLH 07GHZ TR A160 LO B3 7,526.0 7,589.0 160 63
coupler GE / 400 Mbps 2 2 4 4 2 2 2 CHH07-A160-03-00 253375943 ODU SLH 07GHZ TR A160 HI B3 7,686.0 7,749.0 160 63
GE + 16 E1 / 400 Mbps 2 2 4 4 2 2 2
CHH07-A161-01-00 253375964 ODU SLH 07GHZ TR A161 HI B1 7,278.0 7,341.0 161 63
Minimum configuration for one link.
Transmit Range T to R Diplexer Transmit Range T to R Diplexer

Sagem Model Sagem Min Freq Max (MHz) Range Sagem Model Sagem Min Freq Max (MHz) Range
Sagem Description Sagem Description
Number P/N (MHz) Freq (MHz) Number P/N (MHz) Freq (MHz)
(MHz) (MHz)
CHB07-A161-03-00 253375998 ODU SLH 07GHZ TR A161 LO B3 7,198.0 7,261.0 161 63 CHB07-A168-01-00 253376437 ODU SLH 07GHZ TR A168 LO B1 7,443.0 7,499.0 168 56
CHH07-A161-03-00 253376007 ODU SLH 07GHZ TR A161 HI B3 7,359.0 7,422.0 161 63 CHH07-A168-01-00 253376440 ODU SLH 07GHZ TR A168 HI B1 7,611.0 7,667.0 168 56
CHB07-B161-01-00 253376036 ODU SLH 07GHZ TR B161 LO B1 7,417.0 7,480.0 161 63 CHB07-A168-03-00 253376479 ODU SLH 07GHZ TR A168 LO B3 7,527.0 7,583.0 168 56
CHH07-B161-01-00 253376049 ODU SLH 07GHZ TR B161 HI B1 7,578.0 7,641.0 161 63 CHH07-A168-03-00 253376482 ODU SLH 07GHZ TR A168 HI B3 7,695.0 7,751.0 168 56
CHB07-B161-02-00 253376057 ODU SLH 07GHZ TR B161 LO B2 7,459.0 7,522.0 161 63
CHH07-B161-02-00 253376060 ODU SLH 07GHZ TR B161 HI B2 7,620.0 7,683.0 161 63 CHB07-B168-01-00 253376490 ODU SLH 07GHZ TR B168 LO B1 7,093.0 7,149.0 168 56
CHB07-B161-03-00 253376078 ODU SLH 07GHZ TR B161 LO B3 7,498.0 7,561.0 161 63 CHH07-B168-01-00 253376502 ODU SLH 07GHZ TR B168 HI B1 7,261.0 7,317.0 168 56
CHB07-B161-04-00 253376099 ODU SLH 07GHZ TR B161 LO B4 7,513.0 7,576.0 161 63 CHH07-B168-02-00 253376523 ODU SLH 07GHZ TR B168 HI B2 7,317.0 7,373.0 168 56
CHB07-C161-01-00 253376114 ODU SLH 07GHZ TR C161 LO B1 7,114.0 7,177.0 161 63 CHH07-B168-03-00 253376544 ODU SLH 07GHZ TR B168 HI B3 7,373.0 7,429.0 168 56
CHH07-C161-01-00 253376122 ODU SLH 07GHZ TR C161 HI B1 7,275.0 7,338.0 161 63
CHB07-C161-02-00 253376135 ODU SLH 07GHZ TR C161 LO B2 7,149.0 7,212.0 161 63 CHB07-A196-01-00 253376557 ODU SLH 07GHZ TR A196 LO B1 7,093.0 7,149.0 196 56
CHH07-C161-02-00 253376143 ODU SLH 07GHZ TR C161 HI B2 7,310.0 7,373.0 161 63 CHH07-A196-01-00 253376565 ODU SLH 07GHZ TR A196 HI B1 7,289.0 7,345.0 196 56
CHB07-D161-01-00 253376198 ODU SLH 07GHZ TR D161 LO B1 7,239.0 7,302.0 161 63 CHB07-A196-04-00 253376619 ODU SLH 07GHZ TR A196 LO B4 7,177.0 7,233.0 196 56
CHH07-D161-01-00 253376205 ODU SLH 07GHZ TR D161 HI B1 7,400.0 7,463.0 161 63 CHH07-A196-04-00 253376627 ODU SLH 07GHZ TR A196 HI B4 7,373.0 7,429.0 196 56
CHB07-D161-02-00 253376218 ODU SLH 07GHZ TR D161 LO B2 7,274.0 7,337.0 161 63 CHB07-A196-05-00 253376630 ODU SLH 07GHZ TR A196 LO B5 7,205.0 7,261.0 196 56
CHH07-D161-02-00 253376226 ODU SLH 07GHZ TR D161 HI B2 7,435.0 7,498.0 161 63 CHH07-A196-05-00 253376648 ODU SLH 07GHZ TR A196 HI B5 7,401.0 7,457.0 196 56
CHB07-D161-03-00 253376239 ODU SLH 07GHZ TR D161 LO B3 7,309.0 7,372.0 161 63
CHH07-D161-03-00 253376247 ODU SLH 07GHZ TR D161 HI B3 7,470.0 7,533.0 161 63 CHB07-A245-01-00 253376651 ODU SLH 07GHZ TR A245 LO B1 7,400.0 7,484.0 245 84
CHB07-D161-04-00 253376250 ODU SLH 07GHZ TR D161 LO B4 7,344.0 7,407.0 161 63 CHH07-A245-01-00 253376669 ODU SLH 07GHZ TR A245 HI B1 7,645.0 7,729.0 245 84
CHH07-D161-04-00 253376268 ODU SLH 07GHZ TR D161 HI B4 7,505.0 7,568.0 161 63 CHB07-A245-02-00 253376672 ODU SLH 07GHZ TR A245 LO B2 7,484.0 7,568.0 245 84
CHB07-E161-01-00 253376271 ODU SLH 07GHZ TR E161 LO B1 7,414.0 7,477.0 161 63 CHH07-A245-02-00 253376680 ODU SLH 07GHZ TR A245 HI B2 7,729.0 7,813.0 245 84
CHH07-E161-01-00 253376289 ODU SLH 07GHZ TR E161 HI B1 7,575.0 7,638.0 161 63 CHB07-A245-03-00 253376693 ODU SLH 07GHZ TR A245 LO B3 7,568.0 7,652.0 245 84
CHB07-E161-02-00 253376292 ODU SLH 07GHZ TR E161 LO B2 7,449.0 7,512.0 161 63 CHH07-A245-03-00 253376705 ODU SLH 07GHZ TR A245 HI B3 7,813.0 7,897.0 245 84
CHH07-E161-02-00 253376304 ODU SLH 07GHZ TR E161 HI B2 7,610.0 7,673.0 161 63
CHB07-E161-03-00 253376312 ODU SLH 07GHZ TR E161 LO B3 7,484.0 7,547.0 161 63 8 GHz ODUs
CHH07-E161-03-00 253376325 ODU SLH 07GHZ TR E161 HI B3 7,645.0 7,708.0 161 63 CHB08-YYYY-XX-00 ODU SLH 08GHZ TR YYYY LO XX
CHB07-E161-04-00 253376333 ODU SLH 07GHZ TR E161 LO B4 7,519.0 7,582.0 161 63 CHH08-YYYY-XX-00 ODU SLH 08GHZ TR YYYY HI XX
CHH07-E161-04-00 253376346 ODU SLH 07GHZ TR E161 HI B4 7,680.0 7,743.0 161 63
CHB07-F161-01-00 253376354 ODU SLH 07GHZ TR F161 LO B1 7,539.0 7,602.0 161 63 CHB08-A126-01-00 253376713 ODU SLH 08GHZ TR A126 LO B1 8,279.0 8,307.0 119 & 126 28
CHH07-F161-01-00 253376367 ODU SLH 07GHZ TR F161 HI B1 7,700.0 7,763.0 161 63 CHH08-A126-01-00 253376726 ODU SLH 08GHZ TR A126 HI B1 8,398.0 8,426.0 119 & 126 28
CHB08-A126-05-00 253376797 ODU SLH 08GHZ TR A126 LO B5 8,335.0 8,363.0 119 & 126 28

(MHz) (MHz)
CHH08-A126-05-00 253376809 ODU SLH 08GHZ TR A126 HI B5 8,454.0 8,482.0 119 & 126 28 CHB11-A490-04-00 253377158 ODU SLH 11GHZ TR A490 LO B4 11,035.0 11,215.0 490 180
CHB08-A126-06-00 253376817 ODU SLH 08GHZ TR A126 LO B6 8,349.0 8,377.0 119 & 126 28 CHH11-A490-04-00 253377166 ODU SLH 11GHZ TR A490 HI B4 11,525.0 11,705.0 490 180
CHH08-A126-06-00 253376820 ODU SLH 08GHZ TR A126 HI B6 8,468.0 8,496.0 119 & 126 28
CHB11-A490-05-00 253377179 ODU SLH 11GHZ TR A490 LO B5 10,700.0 10,890.0 490 & 500 190
CHB08-A151-01-00 253376838 ODU SLH 08GHZ TR A151 LO B1 8,203.0 8,271.0 151.614 68.0 CHH11-A490-05-00 253377187 ODU SLH 11GHZ TR A490 HI B5 11,200.0 11,390.0 490 & 500 190
CHH08-A151-01-00 253376841 ODU SLH 08GHZ TR A151 HI B1 8,355.0 8,423.0 151.614 68.0 CHB11-A490-06-00 253377190 ODU SLH 11GHZ TR A490 LO B6 10,855.0 11,045.0 490 & 500 190
CHH08-A151-02-00 253376862 ODU SLH 08GHZ TR A151 HI B2 8,392.0 8,460.0 151.614 68.0 CHB11-A490-07-00 253377210 ODU SLH 11GHZ TR A490 LO B7 11,010.0 11,200.0 490 & 500 190
CHH08-A151-03-00 253376883 ODU SLH 08GHZ TR A151 HI B3 8,429.0 8,497.0 151.614 68.0
CHB08-A208-01-00 253376891 ODU SLH 08GHZ TR A208 LO B1 8,043.0 8,113.0 208 70 CHH11-A530-01-00 253377244 ODU SLH 11GHZ TR A530 HI B1 11,205.0 11,385.0 530 180
CHH08-A208-01-00 253376903 ODU SLH 08GHZ TR A208 HI B1 8,251.0 8,321.0 208 70 CHB11-A530-02-00 253377252 ODU SLH 11GHZ TR A530 LO B2 10,795.0 10,975.0 530 180
13 GHz ODUs
CHB08-A213-01-00 253376979 ODU SLH 08GHZ TR A213 LO B1 8,005.0 8,075.0 213.5 70 CHB13-YYYY-XX-00 ODU SLH 13GHZ TR YYYY LO XX
CHH08-A213-01-00 253376987 ODU SLH 08GHZ TR A213 HI B1 8,219.0 8,289.0 213.5 70 CHH13-YYYY-XX-00 ODU SLH 13GHZ TR YYYY HI XX
CHB08-A266-01-00 253376990 ODU SLH 08GHZ TR A266 LO B1 7,905.0 8,024.0 266 119 CHB13-A266-01-00 ODU SLH 13GHZ TR A266 LO B1 12,751.0 12,814.0 266 63
253377314
CHH08-A266-01-00 253377009 ODU SLH 08GHZ TR A266 HI B1 8,171.0 8,290.0 266 119 CHH13-A266-01-00 ODU SLH 13GHZ TR A266 HI B1 13,017.0 13,080.0 266 63
253377327
CHB08-A266-02-00 253377012 ODU SLH 08GHZ TR A266 LO B2 8,017.0 8,136.0 266 119 CHB13-A266-02-00 ODU SLH 13GHZ TR A266 LO B2 12,807.0 12,870.0 266 63
253377335
CHH08-A266-02-00 253377020 ODU SLH 08GHZ TR A266 HI B2 8,283.0 8,402.0 266 119 CHH13-A266-02-00 ODU SLH 13GHZ TR A266 HI B2 13,073.0 13,136.0 266 63
253377348
CHB08-A311-01-00 253377033 ODU SLH 08GHZ TR A311 LO B1 7,731.0 7,867.0 311.32 136 CHH13-A266-03-00 ODU SLH 13GHZ TR A266 HI B3 13,129.0 13,192.0 266 63
253377369
CHH08-A311-01-00 253377041 ODU SLH 08GHZ TR A311 HI B1 8,042.0 8,178.0 311.32 136 CHB13-A266-04-00 ODU SLH 13GHZ TR A266 LO B4 12,919.0 12,982.0 266 63
253377377
CHB08-A311-02-00 253377054 ODU SLH 08GHZ TR A311 LO B2 7,835.0 7,971.0 311.32 136 CHH13-A266-04-00 ODU SLH 13GHZ TR A266 HI B4 13,185.0 13,248.0 266 63
253377380
CHH08-A311-02-00 253377062 ODU SLH 08GHZ TR A311 HI B2 8,146.0 8,282.0 311.32 136
CHB08-A311-03-00 253377075 ODU SLH 08GHZ TR A311 LO B3 7,717.0 7,867.0 311.32 136
15 GHz ODUs
CHH08-A311-03-00 253377083 ODU SLH 08GHZ TR A311 HI B3 8,028.0 8,178.0 311.32 136
CHH15-YYYY-XX-00 ODU SLH 15GHZ TR YYYY HI XX
11 GHz ODUs
CHB11-A490-01-00 253377096 ODU SLH 11GHZ TR A490 LO B1 10,675.0 10,855.0 490 180 CHH15-A315-02-00 ODU SLH 15GHZ TR A315 HI B2 15,040.0 15,159.0 315 119
253377421
CHH11-A490-01-00 253377103 ODU SLH 11GHZ TR A490 HI B1 11,165.0 11,345.0 490 180 CHB15-A315-03-00 ODU SLH 15GHZ TR A315 LO B3 14,823.0 14,942.0 315 119
253377434
CHB11-A490-02-00 253377116 ODU SLH 11GHZ TR A490 LO B2 10,795.0 10,975.0 490 180 CHH15-A315-03-00 ODU SLH 15GHZ TR A315 HI B3 15,138.0 15,257.0 315 119
253377442

(MHz) (MHz)
CHB15-A420-02-00 253377476 ODU SLH 15GHZ TR A420 LO B2 14,606.0 14,725.0 420 119 CHH18-1010-02-00 253377822 ODU SLH 18GHZ TR 1010 HI B2 18,940.0 19,240.0 1010 300
CHH15-A420-02-00 253377484 ODU SLH 15GHZ TR A420 HI B2 15,026.0 15,145.0 420 119 CHB18-1010-03-00 253377835 ODU SLH 18GHZ TR 1010 LO B3 18,180.0 18,480.0 1010 300
CHB18-1560-01-00 253377877 ODU SLH 18GHZ TR 1560 LO B1 17,700.0 18,000.0 1560 300
23 GHz ODUs
CHB15-A490-01-00 253377591 ODU SLH 15GHZ TR A490 LO B1 14,403.0 14,522.0 490 119 CHB23-YYYY-XX-00 ODU SLH 23GHZ TR YYYY LO XX
CHH15-A490-01-00 253377603 ODU SLH 15GHZ TR A490 HI B1 14,893.0 15,012.0 490 119 CHH23-YYYY-XX-00 ODU SLH 23GHZ TR YYYY HI XX
CHH15-A490-02-00 253377624 ODU SLH 15GHZ TR A490 HI B2 15,005.0 15,124.0 490 119 CHB23-1008-01-00 ODU SLH 23GHZ TR 1008 LO B1 1008 336
253377939 21,994.0 22,330.0
CHB15-A490-03-00 253377632 ODU SLH 15GHZ TR A490 LO B3 14,627.0 14,746.0 490 119 CHH23-1008-01-00 ODU SLH 23GHZ TR 1008 HI B1 1008 336
253377947 23,002.0 23,338.0
CHH15-A490-03-00 253377645 ODU SLH 15GHZ TR A490 HI B3 15,117.0 15,236.0 490 119 CHB23-1008-02-00 ODU SLH 23GHZ TR 1008 LO B2 1008 336
253377950 22,274.0 22,610.0
CHB15-A490-04-00 253377653 ODU SLH 15GHZ TR A490 LO B4 14,739.0 14,858.0 490 119 CHH23-1008-02-00 ODU SLH 23GHZ TR 1008 HI B2 1008 336
253377968 23,282.0 23,618.0
CHB23-1200-01-00 253377971 ODU SLH 23GHZ TR 1200 LO B1 21,200.0 21,530.0 1200 330.0
CHB15-A640-01-00 253377674 ODU SLH 15GHZ TR A640 LO B1 14,500.0 14,610.0 640 110 CHH23-1200-01-00 ODU SLH 23GHZ TR 1200 HI B1 1200 330.0
253377989 22,400.0 22,730.0
CHH15-A640-01-00 253377687 ODU SLH 15GHZ TR A640 HI B1 15,140.0 15,250.0 640 110 CHB23-1200-02-00 ODU SLH 23GHZ TR 1200 LO B2 1200 330.0
253377992 21,490.0 21,820.0
CHB15-A640-02-00 253377695 ODU SLH 15GHZ TR A640 LO B2 14,605.0 14,715.0 640 110 CHH23-1200-02-00 ODU SLH 23GHZ TR 1200 HI B2 1200 330.0
253378001 22,690.0 23,020.0
CHH15-A640-02-00 253377707 ODU SLH 15GHZ TR A640 HI B2 15,245.0 15,355.0 640 110 CHB23-1200-03-00 ODU SLH 23GHZ TR 1200 LO B3 1200 330.0
253378014 21,780.0 22,110.0
CHH23-1200-03-00 253378022 ODU SLH 23GHZ TR 1200 HI B3 22,980.0 23,310.0 1200 330.0
CHB15-A644-01-00 253377715 ODU SLH 15GHZ TR A644 LO B1 14,400.0 14,512.0 644 112 CHB23-1200-04-00 ODU SLH 23GHZ TR 1200 LO B4 1200 330.0
253378035 22,070.0 22,400.0
CHH15-A644-01-00 253377728 ODU SLH 15GHZ TR A644 HI B1 15,044.0 15,156.0 644 112 CHH23-1200-04-00 ODU SLH 23GHZ TR 1200 HI B4 1200 330.0
253378043 23,270.0 23,600.0
CHH15-A644-02-00 253377749 ODU SLH 15GHZ TR A644 HI B2 15,142.0 15,254.0 644 112 CHB23-1200-05-00 ODU SLH 23GHZ TR 1200 LO B5 21,200.0 21,600.0 1200 400
253378056
CHB15-A644-03-00 253377757 ODU SLH 15GHZ TR A644 LO B3 14,596.0 14,708.0 644 112 CHH23-1200-05-00 ODU SLH 23GHZ TR 1200 HI B5 22,400.0 22,800.0 1200 400
253378064
CHH15-A644-03-00 253377760 ODU SLH 15GHZ TR A644 HI B3 15,240.0 15,352.0 644 112 CHB23-1200-06-00 ODU SLH 23GHZ TR 1200 LO B6 21,600.0 22,000.0 1200 400
253378077
CHH23-1200-06-00 253378085 ODU SLH 23GHZ TR 1200 HI B6 22,800.0 23,200.0 1200 400
CHB15-A728-01-00 253377778 ODU SLH 15GHZ TR A728 LO B1 14,500.0 14,615.0 728 115 CHB23-1200-07-00 253378098 ODU SLH 23GHZ TR 1200 LO B7 22,000.0 22,400.0 1200 400
CHH15-A728-01-00 253377781 ODU SLH 15GHZ TR A728 HI B1 15,228.0 15,343.0 728 115 CHH23-1200-07-00 253378105 ODU SLH 23GHZ TR 1200 HI B7 23,200.0 23,600.0 1200 400
18 GHz ODUs CHB23-1232-01-00 253378118 ODU SLH 23GHZ TR 1232 LO B1 21,200.0 21,500.0 1232 300
CHB18-YYYY-XX-00 ODU SLH 18GHZ TR YYYY LO XX CHH23-1232-01-00 253378126 ODU SLH 23GHZ TR 1232 HI B1 22,432.0 22,732.0 1232 300
CHH18-YYYY-XX-00 ODU SLH 18GHZ TR YYYY HI XX CHB23-1232-02-00 253378139 ODU SLH 23GHZ TR 1232 LO B2 21,472.0 21,786.0 1232 314
CHB18-1010-01-00 253377799 ODU SLH 18GHZ TR 1010 LO B1 17,685.0 17,985.0 1010 300 CHB23-1232-03-00 253378150 ODU SLH 23GHZ TR 1232 LO B3 21,779.0 22,093.0 1232 314
CHH18-1010-01-00 253377801 ODU SLH 18GHZ TR 1010 HI B1 18,695.0 18,995.0 1010 300 CHH23-1232-03-00 253378168 ODU SLH 23GHZ TR 1232 HI B3 23,011.0 23,325.0 1232 314
CHB18-1010-02-00 253377814 ODU SLH 18GHZ TR 1010 LO B2 17,930.0 18,230.0 1010 300 CHB23-1232-04-00 253378171 ODU SLH 23GHZ TR 1232 LO B4 22,086.0 22,386.0 1232 300

Sagem Model Sagem Min Freq Max (MHz) Range References of ODUs H
Sagem Description
(MHz)
It covers channel bandwidth from 7MHz to 56MHz and modulation schemes from QPSK to 256QAM.
26 GHz ODUs Transmit Range T to R Diplexer

CHB26-YYYY-XX-00 ODU SLH 26GHZ TR YYYY LO XX Sagem Model Sagem Min Freq Max (MHz) Range
Sagem Description
(MHz)
6 GHz ODUs
UHB06-YYYY-XX-00 ODU SLH 06GHZ TR YYYY LO XX
UHH06-YYYY-XX-00 ODU SLH 06GHZ TR YYYY HI XX
UHB06-A240-01-00 253086728 ODU SLH 06GHZ TR A240 LO B1 5,925.0 6,025.0 240 100
UHH06-A240-01-00 253086749 ODU SLH 06GHZ TR A240 HI B1 6,175.0 6,275.0 240 100
32 GHz ODUs
UHB06-A252-01-00 253086799 ODU SLH 06GHZ TR A252 LO B1 5,925.0 6,025.0 252.04 100
UHH06-A252-01-00 253086801 ODU SLH 06GHZ TR A252 HI B1 6,175.0 6,275.0 252.04 100
UHB06-A252-02-00 253086822 ODU SLH 06GHZ TR A252 LO B2 6,000.0 6,100.0 252.04 100
CHB32-A812-01-00 253378275 ODU SLH 32GHZ TR A812 LO B1 31,815.0 32,207.0 812 392 UHB06-A252-03-00 ODU SLH 06GHZ TR A252 LO B3 6,075.0 6,175.0 252.04 100
253086851
CHH32-A812-01-00 253378288 ODU SLH 32GHZ TR A812 HI B1 32,627.0 33,019.0 812 392 UHH06-A252-03-00 ODU SLH 06GHZ TR A252 HI B3 6,325.0 6,425.0 252.04 100
253086864
CHH32-A812-02-00 253378308 ODU SLH 32GHZ TR A812 HI B2 32,991.0 33,383.0 812 392 UHB06-A340-01-00 ODU SLH 06GHZ TR A340 LO B1 6,430.0 6,540.0 340 110
253086872
38 GHz ODUs UHB06-A340-02-00 253086893 ODU SLH 06GHZ TR A340 LO B2 6,520.0 6,630.0 340 110
CHB38-YYYY-XX-00 ODU SLH 38GHZ TR YYYY LO XX UHH06-A340-02-00 253086939 ODU SLH 06GHZ TR A340 HI B2 6,860.0 6,970.0 340 110
CHH38-YYYY-XX-00 ODU SLH 38GHZ TR YYYY HI XX UHB06-A340-03-00 253086947 ODU SLH 06GHZ TR A340 LO B3 6,600.0 6,710.0 340 110
CHB38-A700-01-00 253378316 ODU SLH 38GHZ TR A700 LO B1 38,595.0 38,805.0 700 210 UHB06-A340-04-00 253086968 ODU SLH 06GHZ TR A340 LO B4 6,670.0 6,780.0 340 110
CHH38-A700-01-00 253378329 ODU SLH 38GHZ TR A700 HI B1 39,295.0 39,505.0 700 210 UHH06-A340-04-00 253086971 ODU SLH 06GHZ TR A340 HI B4 7,010.0 7,120.0 340 110
CHH38-A700-02-00 253378340 ODU SLH 38GHZ TR A700 HI B2 39,495.0 39,705.0 700 210 7 GHz ODUs
CHB38-A700-03-00 253378358 ODU SLH 38GHZ TR A700 LO B3 38,995.0 39,205.0 700 210 UHB07-YYYY-XX-00 ODU SLH 07GHZ TR YYYY LO XX
CHH38-A700-03-00 253378361 ODU SLH 38GHZ TR A700 HI B3 39,695.0 39,905.0 700 210 UHH07-YYYY-XX-00 ODU SLH 07GHZ TR YYYY HI XX
CHH38-A700-04-00 253378382 ODU SLH 38GHZ TR A700 HI B4 39,895.0 40,105.0 700 210 UHB07-A154-01-00 ODU SLH 07GHZ TR A154 LO B1 7,428.0 7,484.0 154 56
252957519
CHB38-1260-01-00 253378390 ODU SLH 38GHZ TR 1260 LO B1 37,044.0 37,632.0 1260 588 UHB07-A154-02-00 252957530 ODU SLH 07GHZ TR A154 LO B2 7,470.0 7,526.0 154 56
CHH38-1260-01-00 253378402 ODU SLH 38GHZ TR 1260 HI B1 38,304.0 38,892.0 1260 588 UHH07-A154-02-00 252957548 ODU SLH 07GHZ TR A154 HI B2 7,624.0 7,680.0 154 56
CHB38-1260-02-00 253378415 ODU SLH 38GHZ TR 1260 LO B2 37,604.0 38,192.0 1260 588 UHB07-A154-03-00 252957551 ODU SLH 07GHZ TR A154 LO B3 7,512.0 7,568.0 154 56
CHH38-1260-02-00 253378423 ODU SLH 38GHZ TR 1260 HI B2 38,864.0 39,452.0 1260 588 UHH07-A154-03-00 252957569 ODU SLH 07GHZ TR A154 HI B3 7,666.0 7,722.0 154 56
UHB07-B154-01-00 253250493 ODU SLH 07GHZ TR B154 LO B1 7,128.0 7,184.0 154 56

(MHz) (MHz)
UHH07-B154-01-00 253250505 ODU SLH 07GHZ TR B154 HI B1 7,282.0 7,338.0 154 56 UHH07-C161-04-00 253087051 ODU SLH 07GHZ TR C161 HI B4 7,380.0 7,443.0 161 63
UHB07-B154-02-00 253250518 ODU SLH 07GHZ TR B154 LO B2 7,170.0 7,226.0 154 56 UHB07-D161-01-00 253087064 ODU SLH 07GHZ TR D161 LO B1 7,239.0 7,302.0 161 63
UHH07-B154-02-00 253250526 ODU SLH 07GHZ TR B154 HI B2 7,324.0 7,380.0 154 56 UHH07-D161-01-00 253087072 ODU SLH 07GHZ TR D161 HI B1 7,400.0 7,463.0 161 63
UHB07-B154-03-00 253250539 ODU SLH 07GHZ TR B154 LO B3 7,212.0 7,268.0 154 56 UHB07-D161-02-00 253087085 ODU SLH 07GHZ TR D161 LO B2 7,274.0 7,337.0 161 63
UHH07-B154-03-00 253250547 ODU SLH 07GHZ TR B154 HI B3 7,366.0 7,422.0 154 56 UHH07-D161-02-00 253087105 ODU SLH 07GHZ TR D161 HI B2 7,435.0 7,498.0 161 63
UHB07-D161-03-00 253087118 ODU SLH 07GHZ TR D161 LO B3 7,309.0 7,372.0 161 63
UHB07-C154-01-00 253262802 ODU SLH 07GHZ TR C154 LO B1 7,135.0 7,198.0 154 63 UHH07-D161-03-00 253087147 ODU SLH 07GHZ TR D161 HI B3 7,470.0 7,533.0 161 63
UHH07-C154-01-00 253262815 ODU SLH 07GHZ TR C154 HI B1 7,289.0 7,352.0 154 63 UHB07-D161-04-00 253087150 ODU SLH 07GHZ TR D161 LO B4 7,344.0 7,407.0 161 63
UHB07-C154-02-00 253262823 ODU SLH 07GHZ TR C154 LO B2 7,163.0 7,226.0 154 63 UHH07-D161-04-00 253087168 ODU SLH 07GHZ TR D161 HI B4 7,505.0 7,568.0 161 63
UHH07-C154-02-00 253262836 ODU SLH 07GHZ TR C154 HI B2 7,317.0 7,380.0 154 63 UHB07-E161-01-00 253087171 ODU SLH 07GHZ TR E161 LO B1 7,414.0 7,477.0 161 63
UHB07-C154-03-00 253262844 ODU SLH 07GHZ TR C154 LO B3 7,191.0 7,254.0 154 63 UHH07-E161-01-00 253087192 ODU SLH 07GHZ TR E161 HI B1 7,575.0 7,638.0 161 63
UHB07-C154-04-00 253262865 ODU SLH 07GHZ TR C154 LO B4 7,219.0 7,282.0 154 63 UHH07-E161-02-00 253087212 ODU SLH 07GHZ TR E161 HI B2 7,610.0 7,673.0 161 63
UHH07-E161-03-00 253087233 ODU SLH 07GHZ TR E161 HI B3 7,645.0 7,708.0 161 63
UHB07-A160-01-00 252957572 ODU SLH 07GHZ TR A160 LO B1 7,433.5 7,496.5 160 63 UHB07-E161-04-00 253087241 ODU SLH 07GHZ TR E161 LO B4 7,519.0 7,582.0 161 63
UHH07-A160-01-00 252957580 ODU SLH 07GHZ TR A160 HI B1 7,593.5 7,656.5 160 63 UHH07-E161-04-00 253087254 ODU SLH 07GHZ TR E161 HI B4 7,680.0 7,743.0 161 63
UHB07-A160-02-00 252957593 ODU SLH 07GHZ TR A160 LO B2 7,478.5 7,541.5 160 63 UHB07-F161-01-00 253087262 ODU SLH 07GHZ TR F161 LO B1 7,539.0 7,602.0 161 63
UHH07-A160-02-00 252957605 ODU SLH 07GHZ TR A160 HI B2 7,638.5 7,701.5 160 63 UHH07-F161-01-00 253087275 ODU SLH 07GHZ TR F161 HI B1 7,700.0 7,763.0 161 63
UHB07-A160-03-00 252957613 ODU SLH 07GHZ TR A160 LO B3 7,526.0 7,589.0 160 63 UHB07-F161-02-00 253087283 ODU SLH 07GHZ TR F161 LO B2 7,574.0 7,637.0 161 63
UHH07-A160-03-00 252957626 ODU SLH 07GHZ TR A160 HI B3 7,686.0 7,749.0 160 63 UHH07-F161-02-00 253087308 ODU SLH 07GHZ TR F161 HI B2 7,735.0 7,798.0 161 63
UHB07-F161-03-00 253087329 ODU SLH 07GHZ TR F161 LO B3 7,609.0 7,672.0 161 63
UHB07-A161-01-00 252957634 ODU SLH 07GHZ TR A161 LO B1 7,117.0 7,180.0 161 63 UHH07-F161-03-00 253087337 ODU SLH 07GHZ TR F161 HI B3 7,770.0 7,833.0 161 63
UHH07-A161-01-00 252957647 ODU SLH 07GHZ TR A161 HI B1 7,278.0 7,341.0 161 63 UHB07-F161-04-00 253087340 ODU SLH 07GHZ TR F161 LO B4 7,644.0 7,707.0 161 63
UHB07-A161-02-00 252957655 ODU SLH 07GHZ TR A161 LO B2 7,159.0 7,222.0 161 63 UHH07-F161-04-00 253087358 ODU SLH 07GHZ TR F161 HI B4 7,805.0 7,868.0 161 63
UHB07-A161-03-00 252957676 ODU SLH 07GHZ TR A161 LO B3 7,198.0 7,261.0 161 63 UHB07-B168-01-00 253337287 ODU SLH 07GHZ TR B168 LO B1 7,093.0 7,149.0 168 56
UHH07-A161-03-00 252957689 ODU SLH 07GHZ TR A161 HI B3 7,359.0 7,422.0 161 63 UHH07-B168-01-00 253337323 ODU SLH 07GHZ TR B168 HI B1 7,261.0 7,317.0 168 56
UHB07-A161-04-00 252957697 ODU SLH 07GHZ TR A161 LO B4 7,213.0 7,276.0 161 63 UHB07-B168-02-00 253337344 ODU SLH 07GHZ TR B168 LO B2 7,149.0 7,205.0 168 56
UHH07-A161-04-00 252957709 ODU SLH 07GHZ TR A161 HI B4 7,374.0 7,437.0 161 63 UHH07-B168-02-00 253337365 ODU SLH 07GHZ TR B168 HI B2 7,317.0 7,373.0 168 56
UHB07-B161-01-00 252957717 ODU SLH 07GHZ TR B161 LO B1 7,417.0 7,480.0 161 63 UHB07-B168-03-00 253337373 ODU SLH 07GHZ TR B168 LO B3 7,205.0 7,261.0 168 56
UHH07-B161-01-00 252957720 ODU SLH 07GHZ TR B161 HI B1 7,578.0 7,641.0 161 63 UHH07-B168-03-00 253337394 ODU SLH 07GHZ TR B168 HI B3 7,373.0 7,429.0 168 56
UHB07-B161-02-00 252957738 ODU SLH 07GHZ TR B161 LO B2 7,459.0 7,522.0 161 63
UHH07-B161-02-00 252957741 ODU SLH 07GHZ TR B161 HI B2 7,620.0 7,683.0 161 63 UHB07-A168-01-00 252957791 ODU SLH 07GHZ TR A168 LO B1 7,443.0 7,499.0 168 56
UHB07-B161-03-00 252957759 ODU SLH 07GHZ TR B161 LO B3 7,498.0 7,561.0 161 63 UHH07-A168-01-00 252957803 ODU SLH 07GHZ TR A168 HI B1 7,611.0 7,667.0 168 56
UHB07-B161-04-00 252957770 ODU SLH 07GHZ TR B161 LO B4 7,513.0 7,576.0 161 63 UHH07-A168-02-00 252957824 ODU SLH 07GHZ TR A168 HI B2 7,653.0 7,709.0 168 56
UHB07-C161-01-00 253086989 ODU SLH 07GHZ TR C161 LO B1 7,114.0 7,177.0 161 63 UHH07-A168-03-00 252957845 ODU SLH 07GHZ TR A168 HI B3 7,695.0 7,751.0 168 56
UHH07-C161-01-00 253086992 ODU SLH 07GHZ TR C161 HI B1 7,275.0 7,338.0 161 63
UHB07-C161-02-00 253087001 ODU SLH 07GHZ TR C161 LO B2 7,149.0 7,212.0 161 63 UHB07-A196-01-00 253087382 ODU SLH 07GHZ TR A196 LO B1 7,093.0 7,149.0 196 56
UHH07-C161-02-00 253087019 ODU SLH 07GHZ TR C161 HI B2 7,310.0 7,373.0 161 63 UHH07-A196-01-00 253087390 ODU SLH 07GHZ TR A196 HI B1 7,289.0 7,345.0 196 56
UHH07-C161-03-00 253087030 ODU SLH 07GHZ TR C161 HI B3 7,345.0 7,408.0 161 63 UHH07-A196-02-00 253087410 ODU SLH 07GHZ TR A196 HI B2 7,317.0 7,373.0 196 56

(MHz) (MHz)
UHB07-A196-04-00 253087444 ODU SLH 07GHZ TR A196 LO B4 7,177.0 7,233.0 196 56 UHB08-A213-01-00 253177363 ODU SLH 08GHZ TR A213 LO B1 8,005.0 8,075.0 213.5 70
UHH07-A196-04-00 253087452 ODU SLH 07GHZ TR A196 HI B4 7,373.0 7,429.0 196 56 UHH08-A213-01-00 253177371 ODU SLH 08GHZ TR A213 HI B1 8,219.0 8,289.0 213.5 70
UHH07-A196-05-00 253087473 ODU SLH 07GHZ TR A196 HI B5 7,401.0 7,457.0 196 56 UHB08-A266-01-00 252958131 ODU SLH 08GHZ TR A266 LO B1 7,905.0 8,024.0 266 119
UHB07-A245-01-00 253087486 ODU SLH 07GHZ TR A245 LO B1 7,400.0 7,484.0 245 84 UHB08-A266-02-00 252958152 ODU SLH 08GHZ TR A266 LO B2 8,017.0 8,136.0 266 119
UHH07-A245-01-00 253087506 ODU SLH 07GHZ TR A245 HI B1 7,645.0 7,729.0 245 84 UHH08-A266-02-00 252958160 ODU SLH 08GHZ TR A266 HI B2 8,283.0 8,402.0 266 119
UHH07-A245-02-00 253087548 ODU SLH 07GHZ TR A245 HI B2 7,729.0 7,813.0 245 84 UHB08-A311-01-00 252958173 ODU SLH 08GHZ TR A311 LO B1 7,731.0 7,867.0 311.32 136
UHB07-A245-03-00 253087569 ODU SLH 07GHZ TR A245 LO B3 7,568.0 7,652.0 245 84 UHH08-A311-01-00 252958181 ODU SLH 08GHZ TR A311 HI B1 8,042.0 8,178.0 311.32 136
UHH07-A245-03-00 253087572 ODU SLH 07GHZ TR A245 HI B3 7,813.0 7,897.0 245 84 UHB08-A311-02-00 252958194 ODU SLH 08GHZ TR A311 LO B2 7,835.0 7,971.0 311.32 136
8 GHz ODUs UHB08-A311-03-00 253078990 ODU SLH 08GHZ TR A311 LO B3 7,717.0 7,867.0 311.32 136
UHB08-YYYY-XX-00 ODU SLH 08GHZ TR YYYY LO XX UHH08-A311-03-00 253079009 ODU SLH 08GHZ TR A311 HI B3 8,028.0 8,178.0 311.32 136
11 GHz ODUs
UHB08-A126-01-00 252957879 ODU SLH 08GHZ TR A126 LO B1 8,279.0 8,307.0 119 & 126 28 UHB11-YYYY-XX-00 ODU SLH 11GHZ TR YYYY LO XX
UHH08-A126-01-00 252957887 ODU SLH 08GHZ TR A126 HI B1 8,398.0 8,426.0 119 & 126 28 UHH11-YYYY-XX-00 ODU SLH 11GHZ TR YYYY HI XX
UHB08-A126-02-00 252957890 ODU SLH 08GHZ TR A126 LO B2 8,293.0 8,321.0 119 & 126 28
UHH08-A126-02-00 252957907 ODU SLH 08GHZ TR A126 HI B2 8,412.0 8,440.0 119 & 126 28 UHB11-A490-01-00 252958235 ODU SLH 11GHZ TR A490 LO B1 10,675.0 10,855.0 490 180
UHB08-A126-03-00 252957910 ODU SLH 08GHZ TR A126 LO B3 8,307.0 8,335.0 119 & 126 28 UHH11-A490-01-00 252958248 ODU SLH 11GHZ TR A490 HI B1 11,165.0 11,345.0 490 180
UHH08-A126-06-00 252957981 ODU SLH 08GHZ TR A126 HI B6 8,468.0 8,496.0 119 & 126 28
UHB11-A490-05-00 253087580 ODU SLH 11GHZ TR A490 LO B5 10,700.0 10,890.0 490 & 500 190
UHB08-A151-01-00 252957994 ODU SLH 08GHZ TR A151 LO B1 8,203.0 8,271.0 151.614 68.0 UHH11-A490-05-00 253087593 ODU SLH 11GHZ TR A490 HI B5 11,200.0 11,390.0 490 & 500 190
UHH08-A151-01-00 252958003 ODU SLH 08GHZ TR A151 HI B1 8,355.0 8,423.0 151.614 68.0 UHB11-A490-06-00 253087600 ODU SLH 11GHZ TR A490 LO B6 10,855.0 11,045.0 490 & 500 190
UHH08-A151-02-00 252958024 ODU SLH 08GHZ TR A151 HI B2 8,392.0 8,460.0 151.614 68.0 UHB11-A490-07-00 253087642 ODU SLH 11GHZ TR A490 LO B7 11,010.0 11,200.0 490 & 500 190
UHH08-A151-03-00 252958045 ODU SLH 08GHZ TR A151 HI B3 8,429.0 8,497.0 151.614 68.0
UHB08-A208-01-00 252958058 ODU SLH 08GHZ TR A208 LO B1 8,043.0 8,113.0 208 70 UHH11-A530-01-00 252958321 ODU SLH 11GHZ TR A530 HI B1 11,205.0 11,385.0 530 180

(MHz) (MHz)
13 GHz ODUs UHH15-A475-03-00 253087762 ODU SLH 15GHZ TR A475 HI B3 15,258.0 15,358.0 475 100
UHH13-YYYY-XX-00 ODU SLH 13GHZ TR YYYY HI XX UHB15-A490-01-00 252958657 ODU SLH 15GHZ TR A490 LO B1 14,403.0 14,522.0 490 119
15 GHz ODUs UHB15-A640-02-00 253087791 ODU SLH 15GHZ TR A640 LO B2 14,605.0 14,715.0 640 110
18 GHz ODUs
ODU SLH 15GHZ TR A322 LO B3 UHH18-YYYY-XX-00 ODU SLH 18GHZ TR YYYY HI XX
UHB15-A322-03-00 253351782 14,823.0 14,942.0 322 119
UHB18-1010-01-00 252951038 ODU SLH 18GHZ TR 1010 LO B1 17,685.0 17,985.0 1010 300
UHB15-A420-01-00 ODU SLH 15GHZ TR A420 LO B1 14,501.0 14,613.0 420 112 UHH18-1010-01-00 252951046 ODU SLH 18GHZ TR 1010 HI B1 18,695.0 18,995.0 1010 300
252958574
UHH15-A420-01-00 ODU SLH 15GHZ TR A420 HI B1 14,921.0 15,033.0 420 112 UHB18-1010-02-00 252951111 ODU SLH 18GHZ TR 1010 LO B2 17,930.0 18,230.0 1010 300
252958582
252958595
252958607
252958615
252958628
252958636
253087663
253087676
253087684
253087697
253087759

(MHz) (MHz)
UHH26-1008-02-00 252959104 ODU SLH 26GHZ TR 1008 HI B2 25,837.0 26,173.0 1008 336
23 GHz ODUs UHB26-1008-03-00 252959112 ODU SLH 26GHZ TR 1008 LO B3 25,109.0 25,445.0 1008 336
UHB23-YYYY-XX-00 ODU SLH 23GHZ TR YYYY LO XX UHH26-1008-03-00 252959125 ODU SLH 26GHZ TR 1008 HI B3 26,117.0 26,453.0 1008 336
32 GHz ODUs
UHB23-1008-01-00 252958839 ODU SLH 23GHZ TR 1008 LO B1 21,994.0 22,330.0 1008 336 UHB32-YYYY-XX-00 ODU SLH 32GHZ TR YYYY LO XX
UHH23-1008-01-00 252958847 ODU SLH 23GHZ TR 1008 HI B1 23,002.0 23,338.0 1008 336 UHH32-YYYY-XX-00 ODU SLH 32GHZ TR YYYY HI XX
UHH23-1008-02-00 252958868 ODU SLH 23GHZ TR 1008 HI B2 23,282.0 23,618.0 1008 336 UHB32-A812-01-00 252959154 ODU SLH 32GHZ TR A812 LO B1 31,815.0 32,207.0 812 392
UHB23-1200-01-00 252958871 ODU SLH 23GHZ TR 1200 LO B1 21,200.0 21,530.0 1200 330.0 UHB32-A812-02-00 252959175 ODU SLH 32GHZ TR A812 LO B2 32,179.0 32,571.0 812 392
UHH23-1200-01-00 252958889 ODU SLH 23GHZ TR 1200 HI B1 22,400.0 22,730.0 1200 330.0 UHH32-A812-02-00 252959188 ODU SLH 32GHZ TR A812 HI B2 32,991.0 33,383.0 812 392
UHB23-1200-02-00 252958892 ODU SLH 23GHZ TR 1200 LO B2 21,490.0 21,820.0 1200 330.0
UHH23-1200-02-00 252958909 ODU SLH 23GHZ TR 1200 HI B2 22,690.0 23,020.0 1200 330.0 38 GHz ODUs
UHB23-1200-03-00 252958912 ODU SLH 23GHZ TR 1200 LO B3 21,780.0 22,110.0 1200 330.0 UHB38-YYYY-XX-00 ODU SLH 38GHZ TR YYYY LO XX
UHH23-1200-03-00 252958920 ODU SLH 23GHZ TR 1200 HI B3 22,980.0 23,310.0 1200 330.0 UHH38-YYYY-XX-00 ODU SLH 38GHZ TR YYYY HI XX
UHB23-1200-04-00 252958933 ODU SLH 23GHZ TR 1200 LO B4 22,070.0 22,400.0 1200 330.0
UHH23-1200-04-00 252958941 ODU SLH 23GHZ TR 1200 HI B4 23,270.0 23,600.0 1200 330.0 UHB38-A700-01-00 253087960 ODU SLH 38GHZ TR A700 LO B1 38,595.0 38,805.0 700 210
UHB23-1200-05-00 253087845 ODU SLH 23GHZ TR 1200 LO B5 21,200.0 21,600.0 1200 400 UHB38-A700-02-00 253088003 ODU SLH 38GHZ TR A700 LO B2 38,795.0 39,005.0 700 210
UHH23-1200-05-00 253087853 ODU SLH 23GHZ TR 1200 HI B5 22,400.0 22,800.0 1200 400 UHH38-A700-02-00 253088024 ODU SLH 38GHZ TR A700 HI B2 39,495.0 39,705.0 700 210
UHB23-1232-01-00 252958954 ODU SLH 23GHZ TR 1232 LO B1 21,200.0 21,500.0 1232 300 UHB38-1260-01-00 ODU SLH 38GHZ TR 1260 LO B1 37,044.0 37,632.0 1260 588
252959216
UHH23-1232-01-00 252958962 ODU SLH 23GHZ TR 1232 HI B1 22,432.0 22,732.0 1232 300 UHH38-1260-01-00 ODU SLH 38GHZ TR 1260 HI B1 38,304.0 38,892.0 1260 588
252959229
UHB23-1232-02-00 252958975 ODU SLH 23GHZ TR 1232 LO B2 21,472.0 21,786.0 1232 314 UHB38-1260-02-00 ODU SLH 38GHZ TR 1260 LO B2 37,604.0 38,192.0 1260 588
252959237
UHH23-1232-02-00 252958983 ODU SLH 23GHZ TR 1232 HI B2 22,704.0 23,018.0 1232 314 UHH38-1260-02-00 ODU SLH 38GHZ TR 1260 HI B2 38,864.0 39,452.0 1260 588
252959240
26 GHz ODUs

References of ODUs NL Sagem Model Sagem Min Freq Max (MHz) Range
Sagem Description
(MHz)
CNH07-A161-03-00 253367110 ODU SLF 07GHZ TR A161 HI B3 7,359.0 7,422.0 161 63
CNB07-A161-04-00 253367128 ODU SLF 07GHZ TR A161 LO B4 7,213.0 7,276.0 161 63
Transmit Range T to R Diplexer CNH07-A161-04-00 253367131 ODU SLF 07GHZ TR A161 HI B4 7,374.0 7,437.0 161 63
Sagem Model Sagem Min Freq Max (MHz) Range CNB07-B161-01-00 253367149 ODU SLF 07GHZ TR B161 LO B1 7,417.0 7,480.0 161 63
Sagem Description
Number P/N (MHz) Freq (MHz) CNH07-B161-01-00 253367152 ODU SLF 07GHZ TR B161 HI B1 7,578.0 7,641.0 161 63
(MHz) CNB07-B161-02-00 253367160 ODU SLF 07GHZ TR B161 LO B2 7,459.0 7,522.0 161 63
7 GHz ODUs CNH07-B161-02-00 253367173 ODU SLF 07GHZ TR B161 HI B2 7,620.0 7,683.0 161 63
CNB07-YYYY-XX-00 ODU SLF 07GHZ TR YYYY LO XX CNB07-B161-03-00 253367181 ODU SLF 07GHZ TR B161 LO B3 7,498.0 7,561.0 161 63
CNH07-YYYY-XX-00 ODU SLF 07GHZ TR YYYY HI XX CNH07-B161-03-00 253367194 ODU SLF 07GHZ TR B161 HI B3 7,659.0 7,722.0 161 63
CNB07-B161-04-00 253367201 ODU SLF 07GHZ TR B161 LO B4 7,513.0 7,576.0 161 63
CNB07-A154-01-00 253365864 ODU SLF 07GHZ TR A154 LO B1 7,428.0 7,484.0 154 56 CNH07-B161-04-00 253367214 ODU SLF 07GHZ TR B161 HI B4 7,674.0 7,737.0 161 63
CNH07-A154-01-00 253365926 ODU SLF 07GHZ TR A154 HI B1 7,582.0 7,638.0 154 56 CNB07-C161-01-00 253367222 ODU SLF 07GHZ TR C161 LO B1 7,114.0 7,177.0 161 63
CNB07-A154-02-00 253365947 ODU SLF 07GHZ TR A154 LO B2 7,470.0 7,526.0 154 56 CNH07-C161-01-00 253367235 ODU SLF 07GHZ TR C161 HI B1 7,275.0 7,338.0 161 63
CNB07-A154-03-00 253365968 ODU SLF 07GHZ TR A154 LO B3 7,512.0 7,568.0 154 56 CNH07-C161-02-00 253367256 ODU SLF 07GHZ TR C161 HI B2 7,310.0 7,373.0 161 63
CNH07-C161-03-00 253367425 ODU SLF 07GHZ TR C161 HI B3 7,345.0 7,408.0 161 63
CNB07-B154-01-00 253366001 ODU SLF 07GHZ TR B154 LO B1 7,128.0 7,184.0 154 56 CNB07-C161-04-00 253367433 ODU SLF 07GHZ TR C161 LO B4 7,219.0 7,282.0 161 63
CNH07-B154-01-00 253366022 ODU SLF 07GHZ TR B154 HI B1 7,282.0 7,338.0 154 56 CNH07-C161-04-00 253367446 ODU SLF 07GHZ TR C161 HI B4 7,380.0 7,443.0 161 63
CNB07-B154-02-00 253366064 ODU SLF 07GHZ TR B154 LO B2 7,170.0 7,226.0 154 56 CNB07-D161-01-00 253367454 ODU SLF 07GHZ TR D161 LO B1 7,239.0 7,302.0 161 63
CNH07-B154-02-00 253366085 ODU SLF 07GHZ TR B154 HI B2 7,324.0 7,380.0 154 56 CNH07-D161-01-00 253367467 ODU SLF 07GHZ TR D161 HI B1 7,400.0 7,463.0 161 63
CNB07-B154-03-00 253366093 ODU SLF 07GHZ TR B154 LO B3 7,212.0 7,268.0 154 56 CNB07-D161-02-00 253367475 ODU SLF 07GHZ TR D161 LO B2 7,274.0 7,337.0 161 63
CNH07-B154-03-00 253366105 ODU SLF 07GHZ TR B154 HI B3 7,366.0 7,422.0 154 56 CNH07-D161-02-00 253367488 ODU SLF 07GHZ TR D161 HI B2 7,435.0 7,498.0 161 63
CNB07-D161-03-00 253367496 ODU SLF 07GHZ TR D161 LO B3 7,309.0 7,372.0 161 63
CNB07-C154-01-00 253366118 ODU SLF 07GHZ TR C154 LO B1 7,135.0 7,198.0 154 63 CNH07-D161-03-00 253367532 ODU SLF 07GHZ TR D161 HI B3 7,470.0 7,533.0 161 63
CNH07-C154-01-00 253366126 ODU SLF 07GHZ TR C154 HI B1 7,289.0 7,352.0 154 63 CNB07-D161-04-00 253367553 ODU SLF 07GHZ TR D161 LO B4 7,344.0 7,407.0 161 63
CNB07-C154-02-00 253366139 ODU SLF 07GHZ TR C154 LO B2 7,163.0 7,226.0 154 63 CNH07-D161-04-00 253367574 ODU SLF 07GHZ TR D161 HI B4 7,505.0 7,568.0 161 63
CNH07-C154-02-00 253366147 ODU SLF 07GHZ TR C154 HI B2 7,317.0 7,380.0 154 63 CNB07-E161-01-00 253367602 ODU SLF 07GHZ TR E161 LO B1 7,414.0 7,477.0 161 63
CNB07-C154-03-00 253366150 ODU SLF 07GHZ TR C154 LO B3 7,191.0 7,254.0 154 63 CNH07-E161-01-00 253367615 ODU SLF 07GHZ TR E161 HI B1 7,575.0 7,638.0 161 63
CNB07-C154-04-00 253366192 ODU SLF 07GHZ TR C154 LO B4 7,219.0 7,282.0 154 63 CNH07-E161-02-00 253367657 ODU SLF 07GHZ TR E161 HI B2 7,610.0 7,673.0 161 63
CNH07-E161-03-00 253367686 ODU SLF 07GHZ TR E161 HI B3 7,645.0 7,708.0 161 63
CNB07-A160-01-00 253366663 ODU SLF 07GHZ TR A160 LO B1 7,433.5 7,496.5 160 63 CNB07-E161-04-00 253367699 ODU SLF 07GHZ TR E161 LO B4 7,519.0 7,582.0 161 63
CNH07-A160-01-00 253366770 ODU SLF 07GHZ TR A160 HI B1 7,593.5 7,656.5 160 63 CNH07-E161-04-00 253367701 ODU SLF 07GHZ TR E161 HI B4 7,680.0 7,743.0 161 63
CNB07-A160-02-00 253366783 ODU SLF 07GHZ TR A160 LO B2 7,478.5 7,541.5 160 63 CNB07-F161-01-00 253367730 ODU SLF 07GHZ TR F161 LO B1 7,539.0 7,602.0 161 63
CNH07-A160-02-00 253366791 ODU SLF 07GHZ TR A160 HI B2 7,638.5 7,701.5 160 63 CNH07-F161-01-00 253367743 ODU SLF 07GHZ TR F161 HI B1 7,700.0 7,763.0 161 63
CNB07-A160-03-00 253366803 ODU SLF 07GHZ TR A160 LO B3 7,526.0 7,589.0 160 63 CNB07-F161-02-00 253367764 ODU SLF 07GHZ TR F161 LO B2 7,574.0 7,637.0 161 63
CNH07-A160-03-00 253366824 ODU SLF 07GHZ TR A160 HI B3 7,686.0 7,749.0 160 63 CNH07-F161-02-00 253367772 ODU SLF 07GHZ TR F161 HI B2 7,735.0 7,798.0 161 63
CNB07-F161-03-00 253367793 ODU SLF 07GHZ TR F161 LO B3 7,609.0 7,672.0 161 63
CNB07-A161-01-00 253367045 ODU SLF 07GHZ TR A161 LO B1 7,117.0 7,180.0 161 63 CNH07-F161-03-00 253367805 ODU SLF 07GHZ TR F161 HI B3 7,770.0 7,833.0 161 63
CNH07-A161-01-00 253367053 ODU SLF 07GHZ TR A161 HI B1 7,278.0 7,341.0 161 63 CNB07-F161-04-00 253367826 ODU SLF 07GHZ TR F161 LO B4 7,644.0 7,707.0 161 63
CNB07-A161-02-00 253367066 ODU SLF 07GHZ TR A161 LO B2 7,159.0 7,222.0 161 63 CNH07-F161-04-00 253367834 ODU SLF 07GHZ TR F161 HI B4 7,805.0 7,868.0 161 63
CNB07-A161-03-00 253367095 ODU SLF 07GHZ TR A161 LO B3 7,198.0 7,261.0 161 63 CNB07-A168-01-00 253367847 ODU SLF 07GHZ TR A168 LO B1 7,443.0 7,499.0 168 56

(MHz) (MHz)
CNH07-A168-01-00 253367855 ODU SLF 07GHZ TR A168 HI B1 7,611.0 7,667.0 168 56 CNB08-A126-06-00 253368617 ODU SLF 08GHZ TR A126 LO B6 8,349.0 8,377.0 119 & 126 28
CNB07-A168-02-00 253367868 ODU SLF 07GHZ TR A168 LO B2 7,485.0 7,541.0 168 56 CNH08-A126-06-00 253368620 ODU SLF 08GHZ TR A126 HI B6 8,468.0 8,496.0 119 & 126 28
CNB07-A168-03-00 253367889 ODU SLF 07GHZ TR A168 LO B3 7,527.0 7,583.0 168 56 CNB08-A151-01-00 253368638 ODU SLF 08GHZ TR A151 LO B1 8,203.0 8,271.0 151.614 68.0
CNH07-A168-03-00 253367909 ODU SLF 07GHZ TR A168 HI B3 7,695.0 7,751.0 168 56 CNH08-A151-01-00 253368659 ODU SLF 08GHZ TR A151 HI B1 8,355.0 8,423.0 151.614 68.0
CNB08-A151-02-00 253368670 ODU SLF 08GHZ TR A151 LO B2 8,240.0 8,308.0 151.614 68.0
UHB07-B168-01-00 253367912 ODU SLH 07GHZ TR B168 LO B1 7,093.0 7,149.0 168 56 CNH08-A151-02-00 253368683 ODU SLF 08GHZ TR A151 HI B2 8,392.0 8,460.0 151.614 68.0
UHH07-B168-01-00 253367920 ODU SLH 07GHZ TR B168 HI B1 7,261.0 7,317.0 168 56 CNB08-A151-03-00 253368691 ODU SLF 08GHZ TR A151 LO B3 8,277.0 8,345.0 151.614 68.0
UHB07-B168-02-00 253367933 ODU SLH 07GHZ TR B168 LO B2 7,149.0 7,205.0 168 56 CNH08-A151-03-00 253368703 ODU SLF 08GHZ TR A151 HI B3 8,429.0 8,497.0 151.614 68.0
UHH07-B168-02-00 253367941 ODU SLH 07GHZ TR B168 HI B2 7,317.0 7,373.0 168 56
UHB07-B168-03-00 253367954 ODU SLH 07GHZ TR B168 LO B3 7,205.0 7,261.0 168 56 CNB08-A208-01-00 253368711 ODU SLF 08GHZ TR A208 LO B1 8,043.0 8,113.0 208 70
UHH07-B168-03-00 253367962 ODU SLH 07GHZ TR B168 HI B3 7,373.0 7,429.0 168 56 CNH08-A208-01-00 253368724 ODU SLF 08GHZ TR A208 HI B1 8,251.0 8,321.0 208 70
CNB07-A196-01-00 253367975 ODU SLF 07GHZ TR A196 LO B1 7,093.0 7,149.0 196 56 CNH08-A208-02-00 253368753 ODU SLF 08GHZ TR A208 HI B2 8,307.0 8,377.0 208 70
CNH07-A196-01-00 253367983 ODU SLF 07GHZ TR A196 HI B1 7,289.0 7,345.0 196 56 CNB08-A208-03-00 253368766 ODU SLF 08GHZ TR A208 LO B3 8,155.0 8,225.0 208 70
CNB07-A196-04-00 253368039 ODU SLF 07GHZ TR A196 LO B4 7,177.0 7,233.0 196 56 CNB08-A213-01-00 253368828 ODU SLF 08GHZ TR A213 LO B1 8,005.0 8,075.0 213.5 70
CNH07-A196-04-00 253368047 ODU SLF 07GHZ TR A196 HI B4 7,373.0 7,429.0 196 56 CNH08-A213-01-00 253368849 ODU SLF 08GHZ TR A213 HI B1 8,219.0 8,289.0 213.5 70
CNH07-A245-01-00 253368089 ODU SLF 07GHZ TR A245 HI B1 7,645.0 7,729.0 245 84 CNH08-A266-02-00 253368894 ODU SLF 08GHZ TR A266 HI B2 8,283.0 8,402.0 266 119
CNH07-A245-02-00 253368109 ODU SLF 07GHZ TR A245 HI B2 7,729.0 7,813.0 245 84 CNB08-A311-01-00 253368901 ODU SLF 08GHZ TR A311 LO B1 7,731.0 7,867.0 311.32 136
CNB07-A245-03-00 253368112 ODU SLF 07GHZ TR A245 LO B3 7,568.0 7,652.0 245 84 CNH08-A311-01-00 253368914 ODU SLF 08GHZ TR A311 HI B1 8,042.0 8,178.0 311.32 136
CNH07-A245-03-00 253368120 ODU SLF 07GHZ TR A245 HI B3 7,813.0 7,897.0 245 84 CNB08-A311-02-00 253368922 ODU SLF 08GHZ TR A311 LO B2 7,835.0 7,971.0 311.32 136
CNH08-A311-02-00 253368935 ODU SLF 08GHZ TR A311 HI B2 8,146.0 8,282.0 311.32 136
8 GHz ODUs CNB08-A311-03-00 253368943 ODU SLF 08GHZ TR A311 LO B3 7,717.0 7,867.0 311.32 136
CNB08-YYYY-XX-00 ODU SLF 08GHZ TR YYYY LO XX CNH08-A311-03-00 253368956 ODU SLF 08GHZ TR A311 HI B3 8,028.0 8,178.0 311.32 136
CNH08-YYYY-XX-00 ODU SLF 08GHZ TR YYYY HI XX
11 GHz ODUs
CNB08-A126-01-00 253368472 ODU SLF 08GHZ TR A126 LO B1 8,279.0 8,307.0 119 & 126 28 CNB11-YYYY-XX-00 ODU SLF 11GHZ TR YYYY LO XX
CNH08-A126-01-00 253368480 ODU SLF 08GHZ TR A126 HI B1 8,398.0 8,426.0 119 & 126 28 CNH11-YYYY-XX-00 ODU SLF 11GHZ TR YYYY HI XX
CNB08-A126-02-00 253368493 ODU SLF 08GHZ TR A126 LO B2 8,293.0 8,321.0 119 & 126 28
CNH08-A126-02-00 253368500 ODU SLF 08GHZ TR A126 HI B2 8,412.0 8,440.0 119 & 126 28 CNB11-A490-01-00 253368964 ODU SLF 11GHZ TR A490 LO B1 10,675.0 10,855.0 490 180
CNB08-A126-03-00 253368521 ODU SLF 08GHZ TR A126 LO B3 8,307.0 8,335.0 119 & 126 28 CNH11-A490-01-00 253368977 ODU SLF 11GHZ TR A490 HI B1 11,165.0 11,345.0 490 180

(MHz) (MHz)
CNH11-A490-04-00 253369060 ODU SLF 11GHZ TR A490 HI B4 11,525.0 11,705.0 490 180 CNH15-A420-02-00 253374889 ODU SLF 15GHZ TR A420 HI B2 15026 15145 420 119
CNB15-A420-03-00 253374897 ODU SLF 15GHZ TR A420 LO B3 14718 14837 420 119
CNB11-A490-05-00 253374326 ODU SLF 11GHZ TR A490 LO B5 10,700.0 10,890.0 490 & 500 190 CNH15-A420-03-00 253374909 ODU SLF 15GHZ TR A420 HI B3 15138 15257 420 119
CNH11-A490-05-00 253374339 ODU SLF 11GHZ TR A490 HI B5 11,200.0 11,390.0 490 & 500 190 CNB15-A420-04-00 253374917 ODU SLF 15GHZ TR A420 LO B4 14816 14928 420 112
CNB11-A490-06-00 253374347 ODU SLF 11GHZ TR A490 LO B6 10,855.0 11,045.0 490 & 500 190 CNH15-A420-04-00 253374920 ODU SLF 15GHZ TR A420 HI B4 15236 15348 420 112
CNH11-A490-06-00 253374350 ODU SLF 11GHZ TR A490 HI B6 11,355.0 11,545.0 490 & 500 190
CNB11-A490-07-00 253374368 ODU SLF 11GHZ TR A490 LO B7 11,010.0 11,200.0 490 & 500 190 CNB15-A475-01-00 253374938 ODU SLF 15GHZ TR A475 LO B1 14,500.0 14,668.0 475 168
CNH11-A490-07-00 253374623 ODU SLF 11GHZ TR A490 HI B7 11,510.0 11,700.0 490 & 500 190 CNH15-A475-01-00 253374941 ODU SLF 15GHZ TR A475 HI B1 14,975.0 15,143.0 475 168
CNB11-A530-03-00 253374678 ODU SLF 11GHZ TR A530 LO B3 10,915.0 11,135.0 530 220 CNB15-A490-01-00 253374991 ODU SLF 15GHZ TR A490 LO B1 14403 14522 490 119
CNB11-A530-04-00 253374699 ODU SLF 11GHZ TR A530 LO B4 11,035.0 11,215.0 530 180 CNB15-A490-02-00 253375013 ODU SLF 15GHZ TR A490 LO B2 14515 14634 490 119
13 GHz ODUs CNH15-A490-03-00 253375047 ODU SLF 15GHZ TR A490 HI B3 15117 15236 490 119
CNB13-YYYY-XX-00 ODU SLF 13GHZ TR YYYY LO XX CNB15-A490-04-00 253375055 ODU SLF 15GHZ TR A490 LO B4 14739 14858 490 119
CNH13-YYYY-XX-00 ODU SLF 13GHZ TR YYYY HI XX CNH15-A490-04-00 253375068 ODU SLF 15GHZ TR A490 HI B4 15229 15348 490 119
CNH13-A266-03-00 253374769 ODU SLF 13GHZ TR A266 HI B3 13,129.0 13,192.0 266 63 CNB15-A644-01-00 253375112 ODU SLF 15GHZ TR A644 LO B1 14400 14512 644 112
CNB13-A266-04-00 253374772 ODU SLF 13GHZ TR A266 LO B4 12,919.0 12,982.0 266 63 CNH15-A644-01-00 253375120 ODU SLF 15GHZ TR A644 HI B1 15044 15156 644 112
CNH13-A266-04-00 253374780 ODU SLF 13GHZ TR A266 HI B4 13,185.0 13,248.0 266 63 CNB15-A644-02-00 253375133 ODU SLF 15GHZ TR A644 LO B2 14498 14610 644 112
CNH15-A644-02-00 253375141 ODU SLF 15GHZ TR A644 HI B2 15142 15254 644 112
15 GHz ODUs
CNB15-YYYY-XX-00 ODU SLF 15GHZ TR YYYY LO XX
18 GHz ODUs
ODU SLF 15GHZ TR A315 LO B3 CNH18-YYYY-XX-00 ODU SLF 18GHZ TR YYYY HI XX
CNB15-A315-03-00 253374834 14,823.0 14,942.0 315 119
CNB18-1010-01-00 253378824 ODU SLF 18GHZ TR 1010 LO B1 17,685.0 17,985.0 1010 300
CNB15-A420-01-00 253374855 ODU SLF 15GHZ TR A420 LO B1 CNH18-1010-01-00 253378837 ODU SLF 18GHZ TR 1010 HI B1 18,695.0 18,995.0 1010 300
14501 14613 420 112
CNH15-A420-01-00 253374868 ODU SLF 15GHZ TR A420 HI B1 CNB18-1010-02-00 253378845 ODU SLF 18GHZ TR 1010 LO B2 17,930.0 18,230.0 1010 300
14921 15033 420 112
CNB15-A420-02-00 253374876 ODU SLF 15GHZ TR A420 LO B2 CNH18-1010-02-00 253378858 ODU SLF 18GHZ TR 1010 HI B2 18,940.0 19,240.0 1010 300
14606 14725 420 119

(MHz) (MHz)
CNH18-1010-03-00 253378879 ODU SLF 18GHZ TR 1010 HI B3 19,190.0 19,490.0 1010 300 26 GHz ODUs
CNB18-1010-04-00 253378887 ODU SLF 18GHZ TR 1010 LO B4 18,400.0 18,700.0 1010 300 CNB26-YYYY-XX-00 ODU SLF 26GHZ TR YYYY LO XX
CNH18-1010-04-00 253378890 ODU SLF 18GHZ TR 1010 HI B4 19,410.0 19,710.0 1010 300 CNH26-YYYY-XX-00 ODU SLF 26GHZ TR YYYY HI XX
CNB18-1560-01-00 253378907 ODU SLF 18GHZ TR 1560 LO B1 17,700.0 18,000.0 1560 300 CNB26-A800-01-00 253375456 ODU SLF 26GHZ TR A800 LO B1 24,250.0 24,450.0 800 200
CNH18-1560-01-00 253378910 ODU SLF 18GHZ TR 1560 HI B1 19,260.0 19,560.0 1560 300 CNH26-A800-01-00 253375469 ODU SLF 26GHZ TR A800 HI B1 25,050.0 25,250.0 800 200
CNH18-1560-02-00 253378931 ODU SLF 18GHZ TR 1560 HI B2 19,400.0 19,700.0 1560 300 CNB26-1008-01-00 253375477 ODU SLF 26GHZ TR 1008 LO B1 24,549.0 24,885.0 1008 336
CNB18-1560-03-00 253378949 ODU SLF 18GHZ TR 1560 LO B3 17,700.0 18,140.0 1560 440 CNH26-1008-01-00 253375480 ODU SLF 26GHZ TR 1008 HI B1 25,557.0 25,893.0 1008 336
CNH18-1560-03-00 253378952 ODU SLF 18GHZ TR 1560 HI B3 19,260.0 19,700.0 1560 440 CNB26-1008-02-00 253375498 ODU SLF 26GHZ TR 1008 LO B2 24,829.0 25,165.0 1008 336
CNH26-1008-02-00 253375500 ODU SLF 26GHZ TR 1008 HI B2 25,837.0 26,173.0 1008 336
23 GHz ODUs CNB26-1008-03-00 253375513 ODU SLF 26GHZ TR 1008 LO B3 25,109.0 25,445.0 1008 336
CNB23-YYYY-XX-00 ODU SLF 23GHZ TR YYYY LO XX CNH26-1008-03-00 253375521 ODU SLF 26GHZ TR 1008 HI B3 26,117.0 26,453.0 1008 336
32 GHz ODUs
CNB23-1008-01-00 253375196 ODU SLF 23GHZ TR 1008 LO B1 21,994.0 22,330.0 1008 336 CNB32-YYYY-XX-00 ODU SLF 32GHZ TR YYYY LO XX
CNH23-1008-01-00 253375203 ODU SLF 23GHZ TR 1008 HI B1 23,002.0 23,338.0 1008 336 CNH32-YYYY-XX-00 ODU SLF 32GHZ TR YYYY HI XX
CNH23-1008-02-00 253375224 ODU SLF 23GHZ TR 1008 HI B2 23,282.0 23,618.0 1008 336 CNB32-A812-01-00 253375534 ODU SLF 32GHZ TR A812 LO B1 31,815.0 32,207.0 812 392
CNB23-1200-01-00 253375237 ODU SLF 23GHZ TR 1200 LO B1 21,200.0 21,530.0 1200 330.0 CNB32-A812-02-00 253375555 ODU SLF 32GHZ TR A812 LO B2 32,179.0 32,571.0 812 392
CNH23-1200-01-00 253375245 ODU SLF 23GHZ TR 1200 HI B1 22,400.0 22,730.0 1200 330.0 CNH32-A812-02-00 253375563 ODU SLF 32GHZ TR A812 HI B2 32,991.0 33,383.0 812 392
CNB23-1200-02-00 253375258 ODU SLF 23GHZ TR 1200 LO B2 21,490.0 21,820.0 1200 330.0
CNH23-1200-02-00 253375266 ODU SLF 23GHZ TR 1200 HI B2 22,690.0 23,020.0 1200 330.0
38 GHz ODUs

References of ODUs N Sagem Model Sagem Min Freq Max (MHz) Range
Sagem Description
(MHz)
UFB07-C161-03-00 253084860 ODU SLF 07GHZ TR C161 LO B3 7,184.0 7,247.0 161 63
It does not offer the ACM feature. UFH07-C161-03-00 253084878 ODU SLF 07GHZ TR C161 HI B3 7,345.0 7,408.0 161 63
UFB07-C161-04-00 253084881 ODU SLF 07GHZ TR C161 LO B4 7,219.0 7,282.0 161 63
Transmit Range T to R Diplexer UFH07-C161-04-00 253084899 ODU SLF 07GHZ TR C161 HI B4 7,380.0 7,443.0 161 63
Sagem Model Sagem Min Freq Max (MHz) Range UFB07-D161-01-00 253084901 ODU SLF 07GHZ TR D161 LO B1 7,239.0 7,302.0 161 63
Sagem Description
Number P/N (MHz) Freq (MHz) UFH07-D161-01-00 253084919 ODU SLF 07GHZ TR D161 HI B1 7,400.0 7,463.0 161 63
(MHz) UFB07-D161-02-00 253084930 ODU SLF 07GHZ TR D161 LO B2 7,274.0 7,337.0 161 63
7 GHz ODUs UFH07-D161-02-00 253084943 ODU SLF 07GHZ TR D161 HI B2 7,435.0 7,498.0 161 63
UFB07-YYYY-XX-00 ODU SLF 07GHZ TR YYYY LO XX UFB07-D161-03-00 253084951 ODU SLF 07GHZ TR D161 LO B3 7,309.0 7,372.0 161 63
UFH07-YYYY-XX-00 ODU SLF 07GHZ TR YYYY HI XX UFH07-D161-03-00 253084964 ODU SLF 07GHZ TR D161 HI B3 7,470.0 7,533.0 161 63
UFB07-D161-04-00 253084972 ODU SLF 07GHZ TR D161 LO B4 7,344.0 7,407.0 161 63
UFB07-A154-01-00 251307294 ODU SLF 07GHZ TR A154 LO B1 7,428.0 7,484.0 154 56 UFH07-D161-04-00 253084985 ODU SLF 07GHZ TR D161 HI B4 7,505.0 7,568.0 161 63
UFH07-A154-01-00 251307400 ODU SLF 07GHZ TR A154 HI B1 7,582.0 7,638.0 154 56 UFB07-E161-01-00 253084993 ODU SLF 07GHZ TR E161 LO B1 7,414.0 7,477.0 161 63
UFB07-A154-02-00 251307418 ODU SLF 07GHZ TR A154 LO B2 7,470.0 7,526.0 154 56 UFH07-E161-01-00 253085007 ODU SLF 07GHZ TR E161 HI B1 7,575.0 7,638.0 161 63
UFB07-A154-03-00 251307439 ODU SLF 07GHZ TR A154 LO B3 7,512.0 7,568.0 154 56 UFH07-E161-02-00 253085028 ODU SLF 07GHZ TR E161 HI B2 7,610.0 7,673.0 161 63
UFH07-E161-03-00 253085057 ODU SLF 07GHZ TR E161 HI B3 7,645.0 7,708.0 161 63
UFB07-A160-01-00 251305943 ODU SLF 07GHZ TR A160 LO B1 7,433.5 7,496.5 160 63 UFB07-E161-04-00 253085060 ODU SLF 07GHZ TR E161 LO B4 7,519.0 7,582.0 161 63
UFH07-A160-01-00 251305951 ODU SLF 07GHZ TR A160 HI B1 7,593.5 7,656.5 160 63 UFH07-E161-04-00 253085078 ODU SLF 07GHZ TR E161 HI B4 7,680.0 7,743.0 161 63
UFB07-A160-02-00 251305964 ODU SLF 07GHZ TR A160 LO B2 7,478.5 7,541.5 160 63 UFB07-F161-01-00 253085081 ODU SLF 07GHZ TR F161 LO B1 7,539.0 7,602.0 161 63
UFH07-A160-02-00 251305972 ODU SLF 07GHZ TR A160 HI B2 7,638.5 7,701.5 160 63 UFH07-F161-01-00 253085099 ODU SLF 07GHZ TR F161 HI B1 7,700.0 7,763.0 161 63
UFB07-A160-03-00 251305985 ODU SLF 07GHZ TR A160 LO B3 7,526.0 7,589.0 160 63 UFB07-F161-02-00 253085101 ODU SLF 07GHZ TR F161 LO B2 7,574.0 7,637.0 161 63
UFH07-A160-03-00 251305993 ODU SLF 07GHZ TR A160 HI B3 7,686.0 7,749.0 160 63 UFH07-F161-02-00 253085119 ODU SLF 07GHZ TR F161 HI B2 7,735.0 7,798.0 161 63
UFB07-F161-03-00 253085122 ODU SLF 07GHZ TR F161 LO B3 7,609.0 7,672.0 161 63
UFB07-A161-01-00 251306804 ODU SLF 07GHZ TR A161 LO B1 7,117.0 7,180.0 161 63 UFH07-F161-03-00 253085130 ODU SLF 07GHZ TR F161 HI B3 7,770.0 7,833.0 161 63
UFH07-A161-01-00 251306825 ODU SLF 07GHZ TR A161 HI B1 7,278.0 7,341.0 161 63 UFB07-F161-04-00 253085143 ODU SLF 07GHZ TR F161 LO B4 7,644.0 7,707.0 161 63
UFB07-A161-02-00 251306838 ODU SLF 07GHZ TR A161 LO B2 7,159.0 7,222.0 161 63 UFH07-F161-04-00 253085151 ODU SLF 07GHZ TR F161 HI B4 7,805.0 7,868.0 161 63
UFH07-A161-02-00 251306846 ODU SLF 07GHZ TR A161 HI B2 7,320.0 7,383.0 161 63
UFB07-A161-03-00 251306859 ODU SLF 07GHZ TR A161 LO B3 7,198.0 7,261.0 161 63 UFB07-A168-01-00 252832452 ODU SLF 07GHZ TR A168 LO B1 7,443.0 7,499.0 168 56
UFH07-A161-03-00 251306867 ODU SLF 07GHZ TR A161 HI B3 7,359.0 7,422.0 161 63 UFH07-A168-01-00 252832460 ODU SLF 07GHZ TR A168 HI B1 7,611.0 7,667.0 168 56
UFB07-B161-01-00 251307210 ODU SLF 07GHZ TR B161 LO B1 7,417.0 7,480.0 161 63 UFB07-A168-03-00 252832494 ODU SLF 07GHZ TR A168 LO B3 7,527.0 7,583.0 168 56
UFH07-B161-01-00 251307228 ODU SLF 07GHZ TR B161 HI B1 7,578.0 7,641.0 161 63 UFH07-A168-03-00 252832600 ODU SLF 07GHZ TR A168 HI B3 7,695.0 7,751.0 168 56
UFB07-B161-02-00 251307231 ODU SLF 07GHZ TR B161 LO B2 7,459.0 7,522.0 161 63
UFH07-B161-02-00 251307249 ODU SLF 07GHZ TR B161 HI B2 7,620.0 7,683.0 161 63 UFB07-A196-01-00 253085172 ODU SLF 07GHZ TR A196 LO B1 7,093.0 7,149.0 196 56
UFB07-B161-03-00 251307252 ODU SLF 07GHZ TR B161 LO B3 7,498.0 7,561.0 161 63 UFH07-A196-01-00 253085185 ODU SLF 07GHZ TR A196 HI B1 7,289.0 7,345.0 196 56
UFB07-B161-04-00 251307273 ODU SLF 07GHZ TR B161 LO B4 7,513.0 7,576.0 161 63 UFH07-A196-02-00 253085205 ODU SLF 07GHZ TR A196 HI B2 7,317.0 7,373.0 196 56
UFB07-C161-01-00 253084828 ODU SLF 07GHZ TR C161 LO B1 7,114.0 7,177.0 161 63 UFH07-A196-03-00 253085239 ODU SLF 07GHZ TR A196 HI B3 7,345.0 7,401.0 196 56
UFH07-C161-01-00 253084836 ODU SLF 07GHZ TR C161 HI B1 7,275.0 7,338.0 161 63 UFB07-A196-04-00 253085247 ODU SLF 07GHZ TR A196 LO B4 7,177.0 7,233.0 196 56
UFB07-C161-02-00 253084849 ODU SLF 07GHZ TR C161 LO B2 7,149.0 7,212.0 161 63 UFH07-A196-04-00 253085250 ODU SLF 07GHZ TR A196 HI B4 7,373.0 7,429.0 196 56
UFH07-C161-02-00 253084857 ODU SLF 07GHZ TR C161 HI B2 7,310.0 7,373.0 161 63 UFB07-A196-05-00 253085268 ODU SLF 07GHZ TR A196 LO B5 7,205.0 7,261.0 196 56

(MHz) (MHz)
UFH07-A196-05-00 253085271 ODU SLF 07GHZ TR A196 HI B5 7,401.0 7,457.0 196 56 UFB08-A266-01-00 251323313 ODU SLF 08GHZ TR A266 LO B1 7,905.0 8,024.0 266 119
UFB07-A245-02-00 253085320 ODU SLF 07GHZ TR A245 LO B2 7,484.0 7,568.0 245 84
UFH07-A245-02-00 253085333 ODU SLF 07GHZ TR A245 HI B2 7,729.0 7,813.0 245 84 UFB08-A311-01-00 251715115 ODU SLF 08GHZ TR A311 LO B1 7,731.0 7,867.0 311.32 136
UFB07-A245-03-00 253085354 ODU SLF 07GHZ TR A245 LO B3 7,568.0 7,652.0 245 84 UFH08-A311-01-00 251715128 ODU SLF 08GHZ TR A311 HI B1 8,042.0 8,178.0 311.32 136
UFH07-A245-03-00 253085362 ODU SLF 07GHZ TR A245 HI B3 7,813.0 7,897.0 245 84 UFB08-A311-02-00 251715136 ODU SLF 08GHZ TR A311 LO B2 7,835.0 7,971.0 311.32 136
UFH08-A311-02-00 251715149 ODU SLF 08GHZ TR A311 HI B2 8,146.0 8,282.0 311.32 136
8 GHz ODUs UFB08-A311-03-00 253078966 ODU SLF 08GHZ TR A311 LO B3 7,717.0 7,867.0 311.32 136
UFB08-YYYY-XX-00 ODU SLF 08GHZ TR YYYY LO XX UFH08-A311-03-00 253078987 ODU SLF 08GHZ TR A311 HI B3 8,028.0 8,178.0 311.32 136
UFH08-YYYY-XX-00 ODU SLF 08GHZ TR YYYY HI XX
11 GHz ODUs
UFB08-A126-01-00 251308147 ODU SLF 08GHZ TR A126 LO B1 8,279.0 8,307.0 119 & 126 28 UFB11-YYYY-XX-00 ODU SLF 11GHZ TR YYYY LO XX
UFH08-A126-01-00 251308155 ODU SLF 08GHZ TR A126 HI B1 8,398.0 8,426.0 119 & 126 28 UFH11-YYYY-XX-00 ODU SLF 11GHZ TR YYYY HI XX
UFB08-A126-02-00 251308168 ODU SLF 08GHZ TR A126 LO B2 8,293.0 8,321.0 119 & 126 28
UFH08-A126-02-00 251308176 ODU SLF 08GHZ TR A126 HI B2 8,412.0 8,440.0 119 & 126 28 UFB11-A490-01-00 252549396 ODU SLF 11GHZ TR A490 LO B1 10,675.0 10,855.0 490 180
UFB08-A126-03-00 251308189 ODU SLF 08GHZ TR A126 LO B3 8,307.0 8,335.0 119 & 126 28 UFH11-A490-01-00 252550000 ODU SLF 11GHZ TR A490 HI B1 11,165.0 11,345.0 490 180
UFH08-A126-06-00 251610951 ODU SLF 08GHZ TR A126 HI B6 8,468.0 8,496.0 119 & 126 28
UFB11-A490-05-00 253085375 ODU SLF 11GHZ TR A490 LO B5 10,700.0 10,890.0 490 & 500 190
UFB08-A151-01-00 252550307 ODU SLF 08GHZ TR A151 LO B1 8,203.0 8,271.0 151.614 68.0 UFH11-A490-05-00 253085383 ODU SLF 11GHZ TR A490 HI B5 11,200.0 11,390.0 490 & 500 190
UFH08-A151-01-00 252550315 ODU SLF 08GHZ TR A151 HI B1 8,355.0 8,423.0 151.614 68.0 UFB11-A490-06-00 253085396 ODU SLF 11GHZ TR A490 LO B6 10,855.0 11,045.0 490 & 500 190
UFH08-A151-02-00 252550357 ODU SLF 08GHZ TR A151 HI B2 8,392.0 8,460.0 151.614 68.0 UFB11-A490-07-00 253085429 ODU SLF 11GHZ TR A490 LO B7 11,010.0 11,200.0 490 & 500 190
UFH08-A151-03-00 252550399 ODU SLF 08GHZ TR A151 HI B3 8,429.0 8,497.0 151.614 68.0
UFB08-A208-01-00 251307450 ODU SLF 08GHZ TR A208 LO B1 8,043.0 8,113.0 208 70 UFH11-A530-01-00 252550097 ODU SLF 11GHZ TR A530 HI B1 11,205.0 11,385.0 530 180
13 GHz ODUs
UFB08-A213-01-00 252610835 ODU SLF 08GHZ TR A213 LO B1 8,005.0 8,075.0 213.5 70 UFB13-YYYY-XX-00 ODU SLF 13GHZ TR YYYY LO XX
UFH08-A213-01-00 252610848 ODU SLF 08GHZ TR A213 HI B1 8,219.0 8,289.0 213.5 70 UFH13-YYYY-XX-00 ODU SLF 13GHZ TR YYYY HI XX

(MHz) (MHz)
UFB13-A266-01-00 251308209 ODU SLF 13GHZ TR A266 LO B1 12,751.0 12,814.0 266 63 UFB15-A490-02-00 251308390 ODU SLF 15GHZ TR A490 LO B2 14515 14634 490 119
UFH13-A266-01-00 251308212 ODU SLF 13GHZ TR A266 HI B1 13,017.0 13,080.0 266 63 UFH15-A490-02-00 251308506 ODU SLF 15GHZ TR A490 HI B2 15005 15124 490 119
15 GHz ODUs UFB15-A640-02-00 253085531 ODU SLF 15GHZ TR A640 LO B2 14,605.0 14,715.0 640 110
UFB15-YYYY-XX-00 ODU SLF 15GHZ TR YYYY LO XX UFH15-A640-02-00 253085544 ODU SLF 15GHZ TR A640 HI B2 15,245.0 15,355.0 640 110
UFB15-A644-01-00 251707001 ODU SLF 15GHZ TR A644 LO B1 14400 14512 644 112
UFB15-A315-01-00 252503733 ODU SLF 15GHZ TR A315 LO B1 14,627.0 14,746.0 315 119 UFH15-A644-01-00 251707019 ODU SLF 15GHZ TR A644 HI B1 15044 15156 644 112
UFH15-A315-01-00 252503808 ODU SLF 15GHZ TR A315 HI B1 14,942.0 15,061.0 315 119 UFB15-A644-02-00 251707022 ODU SLF 15GHZ TR A644 LO B2 14498 14610 644 112
UFH15-A315-02-00 252503712 ODU SLF 15GHZ TR A315 HI B2 15,040.0 15,159.0 315 119 UFB15-A644-03-00 251707043 ODU SLF 15GHZ TR A644 LO B3 14596 14708 644 112
UFB15-A728-01-00 251308717 ODU SLF 15GHZ TR A728 LO B1 14500 14615 728 115
UFB15-A322-01-00 ODU SLF 15GHZ TR A322 LO B1 14,627.0 14,746.0 322 119 UFH15-A728-01-00 251308725 ODU SLF 15GHZ TR A728 HI B1 15228 15343 728 115
253351688
UFB15-A322-02-00 253351708 ODU SLF 15GHZ TR A322 LO B2 14,725.0 14,844.0 322 119 18 GHz ODUs
UFH15-A322-02-00 253351716 ODU SLF 15GHZ TR A322 HI B2 15,040.0 15,159.0 322 119 UFB18-YYYY-XX-00 ODU SLF 18GHZ TR YYYY LO XX
UFB15-A322-03-00 253351729 ODU SLF 15GHZ TR A322 LO B3 14,823.0 14,942.0 322 119 UFH18-YYYY-XX-00 ODU SLF 18GHZ TR YYYY HI XX
UFB18-1010-01-00 251308738 ODU SLF 18GHZ TR 1010 LO B1 17,685.0 17,985.0 1010 300
UFB15-A420-01-00 251308316 ODU SLF 15GHZ TR A420 LO B1 14501 14613 420 112 UFH18-1010-01-00 251308746 ODU SLF 18GHZ TR 1010 HI B1 18,695.0 18,995.0 1010 300
UFH15-A420-01-00 251308324 ODU SLF 15GHZ TR A420 HI B1 14921 15033 420 112 UFB18-1010-02-00 251308759 ODU SLF 18GHZ TR 1010 LO B2 17,930.0 18,230.0 1010 300
UFH15-A420-04-00 251385412 ODU SLF 15GHZ TR A420 HI B4 15236 15348 420 112
UFB15-A475-01-00 253085440 ODU SLF 15GHZ TR A475 LO B1 14,500.0 14,668.0 475 168 UFH18-1560-01-00 251308832 ODU SLF 18GHZ TR 1560 HI B1 19,260.0 19,560.0 1560 300
UFH15-A475-01-00 253085458 ODU SLF 15GHZ TR A475 HI B1 14,975.0 15,143.0 475 168 UFB18-1560-02-00 251308845 ODU SLF 18GHZ TR 1560 LO B2 17,840.0 18,140.0 1560 300
UFH15-A475-02-00 253085482 ODU SLF 15GHZ TR A475 HI B2 15,135.0 15,303.0 475 168 UFB18-1560-03-00 253085552 ODU SLF 18GHZ TR 1560 LO B3 17,700.0 18,140.0 1560 440
23 GHz ODUs
UFB15-A490-01-00 251308379 ODU SLF 15GHZ TR A490 LO B1 14403 14522 490 119 UFB23-YYYY-XX-00 ODU SLF 23GHZ TR YYYY LO XX
UFH15-A490-01-00 251308387 ODU SLF 15GHZ TR A490 HI B1 14893 15012 490 119 UFH23-YYYY-XX-00 ODU SLF 23GHZ TR YYYY HI XX

(MHz) (MHz)
32 GHz ODUs
UFB23-1008-01-00 251308866 ODU SLF 23GHZ TR 1008 LO B1 21,994.0 22,330.0 1008 336 UFB32-YYYY-XX-00 ODU SLF 32GHZ TR YYYY LO XX
UFH23-1008-01-00 251308874 ODU SLF 23GHZ TR 1008 HI B1 23,002.0 23,338.0 1008 336 UFH32-YYYY-XX-00 ODU SLF 32GHZ TR YYYY HI XX
UFH23-1008-02-00 251308895 ODU SLF 23GHZ TR 1008 HI B2 23,282.0 23,618.0 1008 336 UFB32-A812-01-00 252809268 ODU SLF 32GHZ TR A812 LO B1 31,815.0 32,207.0 812 392
UFB23-1200-01-00 251308907 ODU SLF 23GHZ TR 1200 LO B1 21,200.0 21,530.0 1200 330.0 UFB32-A812-02-00 252811341 ODU SLF 32GHZ TR A812 LO B2 32,179.0 32,571.0 812 392
UFH23-1200-01-00 251308915 ODU SLF 23GHZ TR 1200 HI B1 22,400.0 22,730.0 1200 330.0 UFH32-A812-02-00 252811359 ODU SLF 32GHZ TR A812 HI B2 32,991.0 33,383.0 812 392
UFB23-1200-02-00 251308928 ODU SLF 23GHZ TR 1200 LO B2 21,490.0 21,820.0 1200 330.0
UFH23-1200-02-00 251308936 ODU SLF 23GHZ TR 1200 HI B2 22,690.0 23,020.0 1200 330.0 38 GHz ODUs
UFB23-1200-03-00 251308949 ODU SLF 23GHZ TR 1200 LO B3 21,780.0 22,110.0 1200 330.0 UFB38-YYYY-XX-00 ODU SLF 38GHZ TR YYYY LO XX
UFH23-1200-03-00 251308957 ODU SLF 23GHZ TR 1200 HI B3 22,980.0 23,310.0 1200 330.0
UFB23-1200-04-00 251610993 ODU SLF 23GHZ TR 1200 LO B4 22,070.0 22,400.0 1200 330.0
UFH23-1200-04-00 251611031 ODU SLF 23GHZ TR 1200 HI B4 23,270.0 23,600.0 1200 330.0
UFH23-1200-05-00 253085586 ODU SLF 23GHZ TR 1200 HI B5 22,400.0 22,800.0 1200 400
26 GHz ODUs
UFB26-YYYY-XX-00 ODU SLF 26GHZ TR YYYY LO XX
253 255 964-D / February 2011 Issue 04
SLF-H Installation and Operation Manual 253 255 964-D
www.sagemcom.com
Headquarters: 250, route de lEmpereur
92848 Rueil-Malmaison Cedex - FRANCE
SAGEMCOM ENERGY & TELECOM SAS
Tel: +33 (0)1 57 61 10 00 - Fax: +33 (0)1 57 61 10 01

All rights reserved. The information and specifications included are subject to change without prior notice. Sagemcom tries to ensure that all information in this document is correct, but does not accept liability for error or omission.
Non contractual document.
APPENDIX 2 - SLF-H REFERENCES
Page A2-35
All trademarks are registered by their respective owners. Simplified joint stock company - Capital 44 824 840 Euros - 518 250 337 R.C.S. NANTERRE -

User Guide SAGEM - SLF H PDF

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

User Guide SAGEM - SLF H PDF

Cargado por

Copyright:

Formatos disponibles

Microwave Radio Link

Installation and Operation Manual

(3 000 337 386 R11 000-03)

Figure 4.1 - SLF-H ODU RSL voltage ............................................................................................................................ 4-17

Figure 7.1 - IDU front panel Leds...................................................................................................................................... 7-2

Table 3-1 - 4-pin "POWER" connector pinout ................................................................................................................ 3-10

Table 4-1 - Configuration compatibility .......................................................................................................................... 4-14

Table 5-1 - Default configuration of the alarm relays...................................................................................................... 5-43

Table 7-1 - Meaning of the Wayside alarm ....................................................................................................................... 7-5

1. SYSTEM DESCRIPTION 1.2 - DESCRIPTION

1.2.1 - System composition

x Full compliance with ETSI standards ODU

Other features available:

x 1 Wayside 10/100BaseT Ethernet channel IDU

Figure 1.1 - SLF-H 1+0 terminal

1.2.6 - ODU Versions

Fmin (ODU) Fmax (ODU)

56 MHz radio channel

1.2.2 - IDU version

x UFF P2 (253183126): hot swap fan module.

1.2.5 - Optional MUX64 SPDH version

The SLF-H block diagram is given below.

Figure 1.4 - SLF-H block diagram

1.3.2 - IDU features x A 140 MHz demodulator including:

x A 350 MHz modulator including:

1.4 - PROTECTED CONFIGURATIONS 1.4.1.2 - Receiver operation & performances

Figure 1.7 - 1+1 Frequency diversity configuration

1.5 - ACM CONFIGURATION

See below a synthetic illustration of ACM:

Min GE and Max profiles can be selected among up to 9 ACM profiles.

A modulation and an Ethernet bandwidth correspond to each profile.

GE Tx mute on profile below:

- Max protection mode: - All E1 on one channel:

1.6.2 - 2+0 XPIC

2.1 - INTRODUCTION 2.3.1 - 4 EPLINE mode

UNI port mode:

2.4.4 - Congestion handling

2.4.4.4.4 - CIR/PIR values

3. INSTALLATION 3.3 - IDU INSTALLATION

x Unpacking the Equipment,

3.4 - ANTENNA INSTALLATION

3.4.1 - Antenna mount

The following precautions must always be taken:

Setting the polarization:

3.4.2 - Antenna Installation

Figure 3.3 - Polarization setting in 1+0 configuration

3.5.2 - 1+0 Configuration with pole mount and standard antenna

Vertical polarization Horizontal polarization

Figure 3.6 - Polarization setting on 1+1 coupler

3.5.5 - 1+1 space diversity configuration with 2 antennas

These modules can be 1000BaseSX (multimode optical), 1000BaseLX (single-mode optical) or

3.7.2 - Description of accesses and connectors

Figure 3.7 - Front panel of the SLF-H IDU in 1+0 configuration

Green Power Led To ODU2

Pin Signal name Meaning

Normally Open 8 RELAY 2NC Relay #2 Normally Closed

Common 12 RELAY 2C Relay #2 Common

Figure 3.10 - Relay output electrical interface 14 RELAY 1C Relay #1 Common

x 5 external alarms (inputs)

Open : no alarm if con figu red in nor ma l position (N)

The 3 connectors have the same pinout (Ethernet standard):

Figure 3.11 - External alarm electrical interface

Table 3-3 - Ethernet port pinout