Professional Documents
Culture Documents
Product Ordering
Guide
Eclipse
Product Ordering Guide
Eclipse Product Ordering Guide
All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval
system, or translated into any language or computer language, in any form or by any means, electronic, magnetic,
optical, chemical, manual or otherwise, without the prior written permission of Stratex Networks. To request
permission, contact techpubs@stratexnet.com.
Disclaimer
Stratex Networks makes no representation or warranties with respect to the contents hereof and specifically disclaims
any implied warranties or merchantability or fitness for any particular purpose. Further, Stratex Networks reserves the
right to revise this publication and to make changes from time to time in the content hereof without obligation of
Stratex Networks to notify any person of such revision or changes.
This equipment has been tested for and meets EMC Directive 89/336/EEC. The equipment was tested using screened
cabling. If any other type of cable is used, it may violate compliance.
Trademark
CompactFlashTM
For sales information, contact one of the following regional Stratex Networks offices, during normal business hours.
SJ_techsupport@stratexnet.com dmcglasupport@stratexnet.com
dmcapsupport@stratexnet.com dmcnzsupport@stratexnet.com
You can also call your local Stratex Networks office. Contact information is available on our website:
www.stratexnet.com
Contents
Document Approval...................................................................................... ix
Eclipse Product Management ....................................................................... ix
Amendment Record ....................................................................................... x
Purpose.......................................................................................................... xi
Graphical Cues.............................................................................................. xi
vi Stratex Networks
Eclipse Product Ordering Guide
Appendix C. Abbreviations
Index
Document Approval
Richard Malley Updated accessories and revised document format and July, 2004
structure
Richard Malley Added 5 GHz and various other accessories and updated the December, 2004
available plug-ins in line with product rollout.
x Stratex Networks
Eclipse Product Ordering Guide
Purpose
The intent of this document is to assist sales staff and approved resellers when
quoting the Eclipse product. This document is intended as a guide to the Eclipse
platform and should be used to supplement the existing sales tools such as Focus
and Siebel.
Graphical Cues
The following icons function as graphical cues used to characterize particular
types of associated supporting information.
A note icon denotes additional information you may require to complete the
procedure or understand the function.
Eclipse from Stratex Networks is the first microwave radio to integrate all
point-to-point applications in a single product platform. Eclipse changes the way
networks are planned, deployed and maintained, dramatically reducing the total
cost of using microwave backhaul. Its highly scalable, software-configurable
architecture gives operators complete control of changing conditions and future
network needs, all with minimal cost and service disruption.
Eclipse is unique in providing single-platform coverage for all licensed
frequency bands from 5 to 38 GHz with capacities from 4xE1/DS1 to 2xSTM1/
OC3, plus Fast Ethernet. Eclipse is first to combine PDH and SONET
applications in one radio. Figure 1 shows the two types of hardware available
with the Eclipse platform.
Figure 1-1. Eclipse Terminal and Node
Capacity Migration
Eclipse provides capacity migration from low-capacity PDH to high-capacity
PDH or SONET, all in one platform. This flexibility allows operators to plan for
future network requirements with confidence that future risks on capacity are
minimized. The Eclipse capacity upgrade path is illustrated below in Figure 1-2.
Figure 1-2. Eclipse E1 Capacity Upgrade Path
Summary
Eclipse incorporates the latest technology to deliver a wireless solution optimized
for backhaul networks, whether connecting base stations for 2G or 3G mobile
networks or terminals for MMDS fixed wireless access or private networks.
Stratex Networks has concentrated on providing innovative features to lower the
total cost of wireless backhaul. It enhances the overall experience in planning,
ordering, and delivery through to deployment and ongoing maintenance, at the
same time providing an upgrade path to next generation network requirements.
Product Coverage
For information concerning availability, delivery and product information,
contact Product Management (refer to the front of this guide) or your local
Stratex Networks sales office or representative.
The following tables detail the available: frequency bands, spacing, capacity, and
the possible configurations for the Eclipse Node and Terminal
U6 GHz 6.425 to 7.125 160, 170, 340 STM1/OC3 NN, HH, HS, FF/2+0
7 GHz 7.110 to 7.900 154, 161, 245, 196, 168 STM1/OC3 NN, HH, HS, FF/2+0
8 GHz 7.250 to 8500 119, 126, 151.6, 266, 311.3 STM1/OC3 NN, HH, HS, FF/2+0
11 GHz 10.700 to 11.700 490, 500, 530 STM1/OC3 NN, HH, HS, FF/2+0
15 GHz 14.400 to 15.350 315, 420, 475, 490, 644, STM1/OC3 NN, HH, HS, FF/2+0
728
18 GHz 17.700 to 18.900 340, 1010, 1092, 1120, 1x/2x STM1/OC3 NN, HH, 2+0
1560
23 GHz 21.200 to 23.600 600, 1008, 1200, 1232 1x/2x STM1/OC3 NN, HH, 2+0
24 GHz 24.250 to 27.000 800, 855, 1008 1x/2x STM1/OC3 NN, HH, 2+0
26 GHz 27.500 to 29.500 800, 855, 1008 1x/2x STM1/OC3 NN, HH, 2+0
38 GHz 37.050 to 40.000 700, 1000, 1260 1x/2x STM1/OC3 NN, HH, 2+0
7-23 GHz As above for each As above for each 16x E1/DS1 NN
individual band individual band
For detailed sub-band information, refer to the Intranet at the following location:
http://www.go-stratex.com/field_marketing/sales_tools/eclipse.html
Eclipse Components
The Eclipse platform has two primary variants and each is used for a specific
application.
Eclipse Terminal
Eclipse Node
The Eclipse Node uses a modular chassis with multiple plug-ins that have the
ability to support multiple radio paths and add/drop capability in the one chassis.
An Eclipse platform using the Indoor Node Unit (INU) or Indoor Node Unit
extended (INUe) is called an Eclipse Node. The INU comprises the Indoor
Chassis (IDC) and the (INUe) comprises the Indoor Chassis extended (IDCe).
Both the INU and INUe are supplied with Node Control Card (NCC) and Fan
plug-in(s). The additional plug-ins are the Node Protection Controller (NPC),
RAC, DAC, and AUX plug-ins.
The Eclipse Node supports the ODU 100 and ODU 300. The ODU 100 supports
capacities of 4x E1 to 16x E1 with QPSK modulation only. The ODU 300
supports capacities from 4x E1 to 2x STM1with varying modulation options
from QPSK to 256 QAM.
Module Functions
Table 1-3 explains the function of the two chassis, the Eclipse plug-ins, and the
ODUs.
Table 1-3. Functional Description of Each Module
Terminal
IDU The IDU is a 1RU chassis for data rates from 4 to 16xE1 with QPSK modulation. It is for
non-protected operation only and requires the ODU 100. Two versions are provided, one for 4/
8xE1, and one for 4/8/16xE1.
Node
INU The INU is a 1RU chassis (the IDC) fitted with mandatory plug-ins (one NCC and one FAN)
plus optional plug-ins. It supports up to three ODUs for three non-protected links, or one
protected/diversity link and one non-protected link.
INUe The INUe is a 2RU chassis (the IDCe) fitted with slots for three mandatory plug-ins (one NCC
and two Fans) and ten optional plug-ins. It supports up to six ODUs for six non-protected links,
or up to three protected/diversity links.
NCC V2 The NCC performs the key node management and control functions and provides various dc
rails from the -48Vdc input. The NCC includes a plug-in flash card that stores node
configuration detail and license data. One NCC must be fitted in each chassis (IDC/IDCe).
NPC The NPC provides redundancy for the TDM bus management and power supply functions
normally provided by the NCC.
RAC A chassis may be fitted with a maximum of three RACs, and up to six for the IDCe. Each RAC
interfaces to a companion ODU via a single 50ohm coaxial cable. For most installations the
RAC 30 card is used, which provides access to all rates from 4xE1 to 1xSTM1/OC3. Other
RACs support specific applications, such as the ODU 100, capacity and bandwidth options
greater than 30 Mhz (2xSTM1/OC3), higher multiples of E3 and DS3 rates, and co-channel
operation.
DAC The DAC provides customer line interface options for E1, E3, DS1, DS3, STM1/OC3, and
Ethernet.
AUX The AUX provides auxiliary data channels and alarm inputs/outputs for third-party alarm
connections.
Outdoor Units
ODU 100 The ODU 100 supports capacities from 4 to 16xE1 the frequency range from 7 to 23 GHz. The
modulation is QPSK. It is used with the INU or IDU to provide an economical solution for
medium capacity spur links and non-protected single links.
ODU 300 The ODU 300 supports all capacities from 4xE1/DS1 to 2xSTM1/OC3, with bandwidths from
3.5 to 56 MHz and modulation rates from QPSK to 256QAM. It is used with the INU or INUe
only.
Because of the complexity of a typical node network and the number of nodes
typically used in a network, a configuration tool, Focus NC, has been created that
automatically configures the required nodes with the required plug-ins when the
capacity, frequency, modulation, and add/drop configurations have been
determined for each node/site. For more information refer to Focus NC on
page 2-3.
Eclipse Configurations
Non-Protected (NN)
A non-protected terminal, also known as 1+0, is a configuration in which there is
a single transmission path without redundancy of any kind. An NN terminal has a
single ODU and RAC or IDU. In this configuration any traffic-affecting fault in
either of these units will result in a loss of traffic over the link. An NN
configuration is normally chosen when traffic is non-critical or when path
redundancy is available (due to route/medial diversity rings).
Protected (HH)
A protected terminal, also known as 1+1, provides two redundant transmission
paths, but only one is active at any one time. A hot standby (HH) terminal
consists of two ODUs and two RACs. Each transceiver operates on a single
frequency, with the online transmitter active while the offline unit is operational
with the transmitter muted. With the offline transmitter constantly on, traffic can
be restored in a matter of milliseconds if the online unit fails, without any
warm-up time. In the receive path, the incoming signal is split between the two
receivers. The system software automatically selects the receiver with the better
quality signal. An HH configuration is normally chosen when traffic carried is
critical in nature.
Protected Space Diversity (HS) is not applicable to the RAC10 as it does not
have a hitless receiver.
Protected Frequency Diversity (FF) is not applicable to the RAC10 as it does not
have a hitless receiver.
When higher capacity is required on the overall path, dual INU or INUe chassis
can be used to increase the overall capacity so each combined path can have a
maximum capacity of 128 x E1, 168 x DS1 or 2 x STM1. Protecting any of the
paths requires duplicate RAC 40 plug-ins, ODU 300s and couplers on each
antenna. With the use of dual chassis and four pairs of RAC40 and ODU 300 the
platform will support up to 4+0 STM1 in one direction.
General Information
Type Approval
The Eclipse platform has extensive international approvals in place, but you must
ensure that the equipment is “Type Approved” for the country of deployment.
Most countries require microwave radio equipment to be “Type Approved” by
the National Regulator before equipment can be deployed. In many cases
licenses for operating frequencies cannot be obtained without an Approval
Reference.
To ascertain the Eclipse approval status for your specific requirement, please
contact Regulatory and Compliance manager (Product Management) or the
nearest Stratex Networks office or representative.
Acceptance of an order does not bind Stratex Networks to obtaining necessary
Approvals (if these are not already in place) in a country unless this has been
previously agreed.
Eclipse Product Preview Displays all existing Eclipse configurations that are
contained within the published roadmap document.
This allows the user/customer to fully explore the
flexibility they have available to them with Eclipse.
Price List reports can be created for information
purposes. However it is not possible to export any
items into .csv files for import into Siebel.
For detailed information concerning the use of the Focus NC refer to the
Focus NC 2.0 User Guide.pdf. This is bundled with the Focus NC tool available
from www.go-stratex.com.
For ordering examples of an Eclipse Node, refer to Appendix A.
Siebel
The Siebel sales tool has an inbuilt parts selector that can be used to manually
select Eclipse equipment on an item-by-item basis. All of the available hardware
is available in the explorer tree, and application notes and information is
available in the Literature section of the primary tasks tab.
Because of the complex nature of the Eclipse Nodes, the Siebel inbuilt parts
selector should be used only when ordering small numbers of Nodes, Terminals,
or accessories to complement an existing node network.
Figure 2-6. Inbuilt Parts Selector - Explorer Tree
Siebel has been upgraded to import complete networks from the Focus NC,
eliminating the need to manually configure each item line by line. Once a
budgetary quote has been created in Focus NC, it can be imported into Siebel.
Figure 2-7. The Siebel - Import Option
The Import button pulls the saved .csv format file from the Siebel folder and
imports the line items into the quote; depending on the size of the network this
can take several minutes.
Figure 2-8. The Imported Quote In Siebel
The Eclipse Terminal consists of an Indoor Unit and an ODU: each Terminal is
one end of a non-protected link. The IDU capacity is either 4/8E1 QPSK or
4/8/16E1 QPSK using an ODU 100.
Flow Chart of Decisions for the Terminal
1a. Select the Required
1. Required to carry NMS cables based on:
Order an Eclipse
8x or 16x traffic or when interfacing - Type of Traffic
Terminal
E1 with external alarms - Required termination
- I/O alarms are used
The License is
included with the
hardware unless What is the required:
requested - Tributary Impedance
2. Trib Cable How many of each
- Tributray length
Selection are required?
- Tributary termination
- Straight or X-over
Slip Fit
Option
KEY Start Point Decision Part Selection Option
To order an Eclipse Terminal:
1 IDU 8x or 16x E1or DS1 Refer to the flow chart on the previous page.
1a What NMS and I/O cables are required? Refer to Auxiliary Cables on page 3-54.
2 What tributary cables are required to terminate the Refer to DAC, IDU Accessories on page 3-47.
IDU to other equipment
3 Will IDU to ODU kits be used or will be parts be Refer to RAC/IDU to ODU Accessories on
selected individually? page 3-36.
4 How many lightning arrestors will be used per cable Refer to RAC/IDU to ODU Accessories on
run? page 3-36.
5 What ODU is required? Is there a channel plan? Refer to Eclipse ODUs on page 3-10 and to the
Intranet at the following location:
http://www.go-stratex.com/field_marketing/
sales_tools/eclipse.html
6 Will the ODU be slip fit or remote mount? Are remote Refer to Eclipse Remote Mount on page 3-23
mount or wave-guide required? and to Eclipse Flexible Waveguides on
page 3-23.
Option
KEY Start Point Decision Part Selection Option
To order an Eclipse Node:
1 Do you need an INU or INUe? Refer to Indoor Node Unit on page 3-3.
2 Will auxiliary traffic be transported and will the node Refer to Auxiliary Card (AUX) on page 3-9.
be interfacing with external equipment such as a BTS
2a What Auxiliary cables are required Refer to Auxiliary Cables on page 3-54.
3 Is a NPC required for TDM bus and dc protection Refer to Node Protection Card (NPC) on page 3-8.
4 What is the capacity of the path? This determines the RAC type. Refer to Radio
Access Cards (RAC) on page 3-6.
4a How many paths are required and what type Refer to Eclipse Configurations on page 1-9.
• 1 x RAC for NN
• 2 x RAC for HH, HS FF and 2+0
• 4 x RAC for 4+0
5 What is added or dropped at each site? Is it voice, data, Refer to Data Access Cards (DAC) on page 3-7.
or a combination of both?
5a What tributary cables are required for the selected Refer to E1/DS1 on page 3-47.
DAC plug-ins? Refer to E3/DS3 (Slim Line BNC) on page 3-49.
Refer to STM1/OC3 (SC Optical) on page 3-50.
Refer to STM1/OC3 (LC Optical) on page 3-51.
Refer to STM1/OC3 (BNC) on page 3-53.
Refer to Ethernet RJ45 on page 3-53.
6 If the INU or INUe is not fully populated, extra blank Refer to Blank Panel Cards on page 3-9.
panels are required.
7 Are you using IDU to ODU kits or are parts selected Refer to RAC/IDU to ODU Cables on page 3-37.
individually?
8 How many lightning arrestors are used per cable run? Refer to RAC/IDU to ODU Cables on page 3-37.
9 Which ODU is required and is there a relevant channel Refer to Eclipse ODUs on page 3-10.
plan? Refer to Tuning Guide on page 3-13.
10 How is the ODU be mounted? Is a coupler required? Refer to Eclipse Coupler on page 3-21.
11 Is the ODU(s) a slip-fit or remote mount? Is a remote Refer to Eclipse Remote Mount on page 3-23.
mount or wave-guide required? Refer to Eclipse Flexible Waveguides on
page 3-23.
13 What is the required capacity across each RAC/path Refer to Eclipse Licensing on page 3-29.
Ordering Eclipse Node Accessories
Table 2-1. Reference Table for Node Accessories
Accessories Reference
Indoor Unit Accessories Refer to INU, INUe, and IDU Accessories on page 3-43.
Refer to DAC, IDU Accessories on page 3-47.
Refer to RAC Accessories on page 3-36.
Component Qty
DAC16x 1
Component Qty
License upgrade: to match the current RAC capacity of the same path. 1
Component Qty
License upgrade (Must match the current RAC capacity of the same 1
path.)
Component Qty
Component Less than 100 of the 100 to 500 of the same 500 to 1000 of the
same module module same module
IDC Chassis 1 (or an IDC and an IDCe if both are used) (25+ in the network)
ODUs 2 (or enough ODUs to cover all of the (50+ of different types)
available variants)
Flashcards and Licenses
The correct part number for the spare flashcards is given in the following table.
Focus recommends a spare flash card for each spare NCC card by default. When
configuring quotes via the Siebel parts selector, spare licenses need to be added
manually.
Eclipse Packaging
With the Eclipse platform being very modular the same approach has been used
for packaging to give flexibility to how it can be packaged and distributed to the
customer and then to each site.
An Eclipse order will typically ship to a customer in four different box types:
• A bulk-shipping box (BSB) containing up to ten NCC modules or a mix of
twenty DAC, RAC, AUX or NPC modules that can be configured and then
dispatched to each site.
• An ODU box that is robust enough to be shipped directly to site.
• An INU or INUe box that is robust enough to be shipped to site as is: or when
fully configured with DAC, RAC, AUX and NPC modules.
• An Accessory box that will contain the required accessories for the installation.
Once a shipment of Eclipse arrives at the primary customer site the INU and/or
INUe can then be configured with the required plug-ins from the BSB(s) then
populated and configured. The complete INU or INUe can then be shipped to the
site in its original box.
Figure 2-10. Eclipse Node Shipping Box and Contents
If you request a preconfigured Eclipse Network the network will ship in INU/
IDU, ODU, and accessory boxes only. These boxes are site specific.
Chapter 3. Eclipse Equipment and
Part Numbers
SETUP CD 857-000004-001 1
SETUP CD 857-000004-001 1
Washer,SS,SLW,#12 006-311412-001 5
Con,N,Angle,Adapter,Plug/ 350-000001-001 1
Jack,Amphenol 82-64 RFX
The INU or INUe is the starting point to build an Eclipse Node, once the type of
INU has been selected, then the required module plug-ins and ODUs can be
selected to build the complete Eclipse node.
Washer,SS,SLW,#12 006-311412-001 5
An INU may be fitted with a maximum of three RACs, and up to six for the INUe. Each
RAC interfaces to a companion ODU via a single 50 ohm coaxial cable.
Every RAC 10, RAC 30, and RAC 3X comes with the following accessory:
The DAC provides customer line interface options for E1, E3, DS1, DS3, STM1/OC3,
and Ethernet. There will normally be only one DAC required per INU. These are
normally placed on the right side of the IDC chassis to help cable routing.
For required tributary cables, refer to DAC, IDU Accessories on page 3-47.
The NPC provides redundancy for the NCC TDM bus management and power supply
functions usually provided through the NCC. One NPC card can be installed per INU or
INUe. In the event of a NCC failure the NPC will manage the TDM bus and provide
power to the INU or INUe to keep customer traffic flowing. An NPC is recommended if
the INU or INUe supports more than two RACs/ODUs.
• The NPC has power supply functionality when used with the IDC V1 chassis
and the NCC V1.
• The NPC has power supply and TDM Bus functionality when used with the
IDC V2, IDCe chassis, and the NCC V2.
When the NPC card is used in an IDC chassis it must be in slot position 4, in an
IDCe chassis it must be in slot position 10.
The AUX provides three auxiliary data channels and six alarm inputs/outputs for
third-party alarm connections. The data channels are terminated with a HD26 type
female connector. The alarm connector is a HD15 type female. More than one AUX card
can be used per INU or INUe chassis depending on the TDM chassis configuration.
A blank panel must be installed in all slots that are not occupied with a DAC,
RAC, AUX, or NPC card. The blank panel ensures that the FAN can draw
adequate airflow across all modules installed in the chassis.
• Two are provided with every INU
• Four are provided with every INUe
EXX
ODU 100 Standard power output ODU 100v2 Standard power output ODU 300 High Power Output
Q4FY05 Q1FY06
Band /Modulation 13 15 18 7 8 23 GHz
QPSK 30.5 30.5 30.5 30.5 24.5 28 27 21.5 21.5 21.5 21 20.5 20 dBm
16QAM 26.5 26.5 26.5 26.5 20.5 24 23 17.5 17.5 17.5 17 16.5 16
64QAM 25.5 25.5 25.5 25.5 21.5 23 22 16.5 16.5 16.5 16 15.5 15
128QAM 24.5 24.5 24.5 24.5 20.5 22 21 15.5 15.5 15.5 15 14.5 14
1. The 11GHz ODU 300 is STD PWR and has an EDS part number.
FF (Frequency Band)
FF Designator 05 06 07 08 11 13 15 18 23 26 28 32 38 FF
Band 5 L6 U6 7 8 11 13 15 18 23 24 26 32 38
Optional 0312 0252 0160 0154 0119 0490 0266 0315 0340 0600 0800 0800 0812 0700
TR Spacing
(MHz) 0170 0161 0126 0500 0420 1010 1008 0855 0855 1000
0340 0245 0151 0530 0475 1092 1200 1008 1008 1260
0728
XX The first two numbers designate the channel number of the channel plan.
Number Description
1 TX Low
Freq 5 6 7 8 11 13 15 18 23 26 28 32 38
Band
(GHz)
Flange 7/16 UDR UDR UDR UDR UBR UBR UBR UBR UBR UBR UBR UBR
DIN F 70 84 84 100 120 140 220 220 220 320 320 320
Type
For detailed information concerning ODU flanges, refer to Flange Types and
Orientations on page 3-28.
Tuning Guide
For detailed information on the ODU sub-band and tuning capabilities, refer to
Appendix C.
Eclipse Antennas
The standard Eclipse antenna comes with pole/tower mounting hardware and
enables the Eclipse ODU to attach directly to the antenna via a slip-fit connector.
For antennas over 1.8 m (six feet), a remote mount kit is required for the ODU(s).
Figure 3-6. Eclipse Antennas With Slip-Fit Flange
FF Frequency Band
FF Designator 05 06 07 08 11 13 15 18 23 26 28 32 38
B Sub Band
Designator 0 1 2 3
SM Size in Meters
Designator 03 06 09 12 18 24 30 37
Size in Meters (m) 0.3 0.6 0.9 1.2 1.8 2.4 3 3.7
P Performance
Designator 1 2 3 4
PR Product Range
Designator 1 2 3 4 5 6
Product Range Eclipse XP4/DART Altium MX Type N Remote Single Pole Remote Dual Pole
M Mounting
Designator 01 02 03 04 05
Mounting Slip-fit Remote 5 GHz 7/16 DIN 5 GHz 7/16 DIN 5 GHz CPR187G
Remote Remote Rotator Remote
Antenna
Number Description
086 Antenna
3 Wide Sub-Band
09 0.9 m
1 HPLP
1 Eclipse
01 Slip-fit
NN (Non-Protected) X X
HH (Protected) X X
FF (Frequency Diversity) X X
2 + 0 (Dual Polarization) NA X
The 5 GHz ODU is always remote mounted. It is supplied with a 5 GHz remote
mount and requires jumper cables to connect it to a compatible 5 GHz antenna.
Dual ODUs are mounted to a slip-fit coupler then onto the antenna: HH, FF
The remotely mounted ODU is connected via a flexible waveguide cable to the
antenna: NN, HS
The ODUs are mounted remotely onto a coupler and then connected via a
flexible waveguide cable to the antenna: HH, FF
The ODUs are mounted remotely onto remote mounts and then connected via
flexible waveguides to the dual polarization antenna: 2+0
The ODUs are mounted directly to equal loss couplers and these are connected
via waveguides to a dual polarization antenna: 4+0, 2+2, and 4+4.
4+0 or 2+2
4+4
Eclipse Coupler
When dual ODUs interface to a single antenna, order a slip mount coupler.
The Eclipse ODU, coupler, and antenna design incorporates the ability to rotate
the ODU from vertical to horizontal polarization without the need for a rotational
coupler.
L Loss in dB
3 6
FF 13 12 12 11 10 09 08 07 06 04 03 02
Designator
Freq Band 6 7 8 11 13 15 18 23 26 28 32 38
GHz
5 GHz Splitter/Combiner
The 5GHz ODU uses a 7/16DIN connector, when a 1+1 configuration is required
a splitter combiner and 7/16 jumper cables are required to terminate the ODUs to
the antenna. The splitter/combiner is available in an equal and unequal loss
variant.
1. For more detail on flange patterns, refer to Flange Types and Orientations on page 3-28.
5GHz ODU showing the 7/16 female connector The 5GHz ODU mounted to the 5GHz remote
mount
All other connectors on the ODU are the same as the standard Eclipse ODU:
• IDU-to-ODU cables are N-type
• Compatible with the existing lightning arrestor kits and other N-type cable
accessories
Each 5GHz Eclipse ODU is supplied with a remote mount that will fit to tower or
pole hardware.
The jumper cable connects the ODU to the antenna. There are several variations
to connect to antennas that have different flange types. In addition, N-type
jumpers are offered for bench testing a link using N-type attenuators or test
equipment.
7/16 to 7/16
N-type to 7/16
CPR187G to 7/16
ODU Flange Flat 6-11 GHz UDR 70, 80, and 100 Rectangular
Waveguide Flange With groove and O ring 6-11 GHz PDR 70, 80, and 100 Rectangular
Eclipse Licensing
Terminal Licenses
The Eclipse Terminal has a CompactFlashTM card located in the rear of the IDU
that contains the operating software, license and configuration information.The
flash card is installed in the IDU when shipped from Stratex Networks.
The maximum capacity and modulation are determined by IDU hardware:
• 8xE1/QPSK for IDU 8x
• 16xE1/QPSK for IDU 16x
Where the IDU is to be shipped to countries that have an applicable hardware
tariff, the flash card (that works with both IDUs) can be shipped separately. The
license part number required is:
Node Licenses
The Eclipse Node architecture is controlled by a node based software license that
determines the throughput capability of the radio paths. Each node has one
license that enables all RAC/ODUs installed in the INU/INUe. Each RAC will
have a maximum capacity that it will carry before a new overall license for the
node is required.
The license is stored in a CompactFlash card that is inserted in the NCC, which in
turn is inserted in the IDC or IDCe. Each CompactFlash card has a unique
identifier called the License S/N that is required for license upgrade request and
repair and return processes. A software license “key” allows incremental
capacity selection up to 64xE1 or 2xSTM1 over each RAC/ODU.
When a radio requires extra capacity Stratex Networks will provide a license file
(software key) that is to be loaded in the CompactFlash card (located in the NCC)
remotely via Portal or ProVision V. The license file (software key) is a 170 bytes
binary file that can be delivered by email or by mail (on a CDROM).
The base license delivered on the CompactFlash card supports 6 RAC plug-ins
and 8 x E1 or 16 x DS1 of capacity, with a maximum corresponding modulation
of 16QAM. The base license is held on the CompactFlash card and is free of
charge. If the configuration is not known or the INU/INUe is ordered as a spare, a
base license will be supplied free of charge.
The two base license part numbers and the relevant descriptions are as follows:
EZE-00001 SW LICENSE, E1, 6RAC 8X, BASE The same license for the IDC and IDCe.
EZE-00119 SW LICENSE, DS1, 6RAC 16X The same license for the IDC and IDCe.
When initially configuring a node, a New License must be purchased for the node
where any of the paths are to carry more than 8 x E1 or 16 x DS1 of radio traffic
per RAC card, or where a higher modulation scheme than 16QAM is required.
The license can be ordered, meaning that a unique license part number is
assigned to each valid INU/INUe configuration. New licenses have a part
number that starts with EZE.
Figure 3-11. Basic License EZE-00001/ EZE-00119 - Maximum Capability
The following licenses upgrade one RAC path to the next step.
Each license step can cater to more than one modulation scheme as shown in
Table 3-1.
Table 3-1. Alternate Modulation Settings Available With Each License
QPSK QPSK
32QAM
64QAM
The total cost for an upgrade license is the cost per RAC/ODU (path) for each
path that requires an upgrade. Table 3-2 is a summary of the upgrade capacity
available per RAC card and the cost per RAC card.
Table 3-2. The upgrade costs per RAC card as capacity is increased
across the radio path.
Current Capacity per Required Capacity per Upgrade Cost Per RAC
RAC CARD RAC CARD CARD
Current Capacity per Required Capacity per Upgrade Cost Per RAC
RAC CARD RAC CARD CARD
License Upgrades
Licenses previously shipped on a CompactFlash card may be upgraded to support
higher capacities. License upgrade capacity is selected in the same manner as a
New License. A license upgrade is a software-only process (meaning that no
CompactFlash will be shipped when a license upgrade is requested) requiring a
new license file to be sent by Stratex Networks.
The price of the license upgrade equals the price of the new license minus the
price of the existing license.
To enable two of the radio paths in the previous example in Figure 3-11 on
page 3-30 to carry 16 x E1 would require an upgrade license:
To enable two of the radio paths to carry 28 x DS1 would require an upgrade
license:
Figure 3-12. The base license with either of the above license upgrades applied.
When upgrading a radio path, you must know the RAC and ODU capabilities and
that specialized RACs may be required for higher capacities. Refer to Table 3-3.
Table 3-3. Optional Modulation Options for each License.
QPSK QPSK
ODU 100 ODU 100
ODU 300 ODU 300
32QAM
ODU 300
64QAM
ODU 300
Eclipse Accessories
Setup CD
Every NCC shipped comes with the Setup CD (PN 857-000004-001) containing
the following:
Application/Document Description
Eclipse Software Release Notes Describes what is new in the Portal release and
any known issues
Documentation
The Eclipse User Manual can be ordered as hardcopy (PN 260-668066-001). It is
recommended that one hardcopy be purchased per order to assist in the
understanding and installation of the Eclipse platform.
The Best Practices Guide can be ordered as hardcopy (PN 260-668029-001).
The following items are supplied with each RAC but can be ordered as required.
RAC Accessories
1. The short kit is designed to be used when the RAC40 plug-ins are placed on top of each other.
2. The long kit is designed to be used when the RAC40 plug-ins are placed side-by-side.
LMR400 and 9913 cable connectors and accessories are fully compatible.
Conn,N,Angle,Adapter,Plug/Jack,Amphenol 350-000001-001 1
82-64 RFX
ODU Accessories
The following items are supplied with each ODU but can be ordered as required:
Lightning Protection
The recommended arrestor kit 179-530017-001 contains dual BGXZ arrestors
that protect the indoor and outdoor equipment. This kit and the 179-530016-001
are compatible with 9913 cables. For the BR400C cable, use the 103-0403A-B
kit.
Rack Ears
Flash Cards
dc Cables
Fuses
The following items are supplied with every INU and INUe but can be ordered as
required:
Setup CD 857-000004-001 1
Washer,SS,SLW,#12 006-311412-001 5
The following items are supplied with every IDU but can be ordered as required:
Setup CD 857-000004-001 1
Washer,SS,SLW,#12 006-311412-001 5
IDU Accessories
Alarm and AUX Accessories
E1/DS1
One cable is required for each tributary. The following cables are suitable to
terminate the DAC 4x and IDUs:
RJ45 to RJ45
RJ45 to BNC
1. Cross-over cables are used to connect two DACs/IDUs at the same node.
One cable required per 8 tributaries. The following cables are suitable to
terminate the DAC 16x:
RJ21 to BNC
RJ21 to RJ45
1. Cross-over cables are used to connect two DACs/IDUs at the same node.
1. The splitter/combiner cable is used for tributary protection when using dual DACs at a node.
SC to SC
SC to FC
2 x SC to Splitter1
SC Attenuator Cable2
1. These cables are used for optical protection when using dual DACs at a node.
2. Used when interfacing to other optical equipment requiring different signal levels.
LC to LC
Simplex 3 m SM LC to LC 037-579131-001 2
Simplex 5 m SM LC to LC 037-579132-001 2
Simplex 10 m SM LC to LC 037-579133-001 2
LC to FC
Simplex 3 m SM LC to FC 037-579134-001 2
Simplex 5 m SM LC to FC 037-579135-001 2
Simplex 10 m SM LC to FC 037-579136-001 2
LC to SC
Simplex 3 m SM LC to SC 037-579137-001 2
Simplex 5 m SM LC to SC 037-579138-001 2
Simplex 10 m SM LC to SC 037-579139-001 2
LC to ST
Simplex 3 m SM LC to ST 037-579140-001 2
2 x LC to Splitter1
LC Attenuator Cable2
1. These cables are used for optical protection when using dual DACs at a node.
2. Used when interfacing to other optical equipment requiring different signal levels.
STM1/OC3 (BNC)
Two cables required per tributary. The following cables are suitable to terminate
the DAC155e and DAC 155eM:
1. BNC to BNC cables are used to connect two DACs at the same node.
2. The splitter/combiner cable is used for tributary protection when using dual DACs at a node.
Ethernet RJ45
One cables required per port. The following cables are suitable to terminate the
DAC ES and DAC GE:
Auxiliary Cables
Standard Accessories for the AUX Card EXA-001
7. Click Next.
The Site Definition window is displayed.
8. Configure the add/drop capacity of each DAC per site by clicking the drop
down menu for the Voice Add/Drop Capacity and the Data Add/Drop
Capacity.
9. Define site locations by adding sites to a blank map.
• Click Add Site(s) then click the map.
This adds a site with the previously configured DAC capacity.
• To deploy sites with different DAC Add/Drop configurations, repeat
step 8.
10. To change the individual add/drop capacity or to add a NPC or AUX card to
In this example the window that enables the addition of rings has been skipped.
14. Select the capacity of each link by clicking the Capacity Bit Rate drop-down
menu.
15. If the link is protected, select the Protected option.
16. Click Add Link, then use the tool to place the links between the links between
the sites.
17. To deploy links with different bit rate and protected configurations, repeat
steps 14 to 16.
18. To deploy the paths as 16E1, select from the Capacity Bit Rate drop-down
19. Click Link Details and for each link configure: Capacity, Modulation, ODU
Type, Protected Configuration, Frequency Band, TR Spacing, Tx Low
Frequency, Tx Low Site, and Antenna.
The Link Details window is displayed.
This shows the default accessories that will be standard at every site. The
default surge protection, IDU to ODU cable length and the tributary cable
type can be edited.
24. Click OK and then Yes.
25. Click Select Accessories.
The Accessories window is displayed.
26. Select the required Accessories and spares for each site.
This window can be amended to reflect the specific requirements for each site.
30. To review reports generated by Focus click the View Reports tab.
The View Reports window is displayed.
To fully utilize the advanced operation of the Eclipse nodal TDM back plane it is
useful to know its capabilities and limitations to ensure possible configurations
will work and to ensure that some expansion capability remains if required.
There are five possible ways the backplane can be configured: E1, DS1, E3, DS3
and STM-1 (it is uncommon to configure the backplane for E3/DS3 operation).
For most applications the limiting factor will be the capacity of the RF path this
will be:
• 64 x E1
• 84 x DS1
• 2 x STM-1/OC3
The current maximum amount of traffic that can be configured on an Eclipse
backplane per INU or INUe chassis is measured in time slots.
• 100 x E1 (= 200 Time slots)
• 128 x DS1 (= 256 Time slots)
• 2 x STM-1 (= 4 Time slots)
The time slot methodology is used so when complex rings are used the
calculations that will determine the add/drop ability of a node will give whole
numbers each one representing a tributary.
For advanced Eclipse configurations refer to the Eclipse Networking Guide.pdf,
available from the Guides and White Papers section on:
http://www.go-stratex.com/field_marketing/sales_tools/eclipse.html
Rule 1 Maximum 100 x E1 or 128 x DS1 entering or leaving each INU or INUe
Add/Drop + Add/Drop + Add/Drop + ... < 2 x (50 x E1 per RF Path)
Rule 2 Maximum 100 x E1 or 128 x DS1 entering or leaving each INU or INUe
Add/Drop + Add/Drop + Add/Drop + ... < 2 x (64 x DS1 per RF Path)
Term Definition
AC alternating current
AU Administrative Unit
CW Continuous Wave
DC direct current
Term Definition
FF Frequency Diversity
GHz Gigahertz
HH Hot Standby
HS Space Diversity
IF Intermediate Frequency
LO Local Oscillator
NN Non-Protected
Term Definition
RF Radio Frequency
RU Rack Unit
RX Receive
TBD To Be Determined
TX Transmit
VC Virtual Container
2 Stratex Networks
E F
E1 FF
capacity upgrade 1-3 configuration 1-10
E1/DS1 flange
termination cables 3-47 types and orientations 3-28
E3/DS3 types,ODU 3-13
termination cables 3-49 flange materials
EBS 3-11 ODU and antenna 3-25
Eclipse components 1-6 flashcard
Eclipse configurations 1-9 ordering spares 2-16
Eclipse Node 1-1 part number 2-16
configurations 1-5 replacing 2-16
description 1-6 shipped separately 3-29
Eclipse Product Preview flexible waveguide
limitation 2-3 custom 3-24
quotation 2-3 hanger
Eclipse Terminal 1-1 part numbers 3-27
configurations 1-5 part number format 3-23
description 1-6 part numbers 3-24
Eclipse User Manual Focus 1-8, 2-3
softcopy 3-2 Configure Network window A-1
EDH 3-11 Default Accessories Summary window A-8
equipment example order A-1
availability and rollout 2-1 Link Definition Information window A-5
Node 2-10 Manual Configuration window A-7
ordering 2-1 network configuration 2-2
part numbers 3-1 Optional Spares/Software window A-9
selection 2-7 quotation type
snetwork topology 2-7 budgetary 2-3
system parameter configuration 2-7 detailed 2-3
type approved 2-1 Eclipse Product Preview 2-3
ethernet RJ45 3-53 sales tool xi
example Site Definition window A-3
antenna part number 3-16 Site Details window A-4
Focus created order A-1 View Network window A-7
Focus, links in network report 2-5 View Reports window A-10
Focus, parts by site report 2-5 formula
network built in Focus NC 2-4 price of license upgrade 3-32
ODU part number 3-12 frequency band
antenna part number format 3-15
ODU part number format 3-11
system parameter 2-7
future-proofing network 1-3
4 Stratex Networks
module functions 1-7 O
mounting options
ODU 3-17 ODU
multi-path fading accessories 3-40
reduction flange materials 3-25
FF 1-10 flange types 3-13
HS 1-9 mounting options 3-17
packaging box 2-16
part number format 3-10
N
100,modulation and band frequencies
National Regulator 3-11
equipment approval 2-1 300,modulations and band frequencies
NCC 1-7, 3-29 3-11
setup CD 3-35 CHD 3-12
NCC V2 example 3-12
description 1-8 frequency band 3-11
network TRSP 3-12
configuration remote mount kit 3-14
Focus 2-3 sub-band and tuning capabilities 3-13
configuration application 2-2 supplied with 3-10
greater thank 5 links,use Focus 2-2 types 3-10
less than 5 links,use Siebel 2-2 ODU 100 1-6
spares and site accessories 2-4 capacity support 1-7
Node description 1-8
AUX 1-8 ODU 300
base license support 3-29 capacity support 1-7
DAC 1-8 description 1-8
equipment 2-10 operation
license 3-29 TDM Bus B-1
NCC V2 1-8 optional
ordering 2-12 IDU accessories 3-36
ordering accessories 2-13 INU cables 3-54
RAC 1-8 RAC 40 accessories 3-36
non-protected Oracle 2-3
configuration 1-9 order
note icon xi creating example A-1
NPC 1-7 ordering
description 1-8, 3-8 equipment 2-1
part number 3-8 Node 2-12
Node accessories 2-13
Siebel 2-2
spares 2-15
Terminal 2-10
6 Stratex Networks
report T
BOM 2-4
links in network 2-5 TDM backplane
parts by site 2-5 maximum capacity limitations 1-10
RF path B-2 TDM Bus 1-11
rules architecture B-1
TDM Bus B-2 operation B-1
purpose B-1
rules and examples B-2
S
Terminal
sales application equipment 2-8
Siebel 2-2 IDU 1-7
sales tools license 3-29
Focus xi ordering 2-10
Siebel xi termination cables
setup CD DAC ES 3-53
accessories 3-35 DAC155e 3-53
Siebel 2-6 DAC155o 3-50
import .csv file 2-4 DAC155oM 3-51
import network from Focus NC 2-6 E1/DS1 3-47
ordering,sales application 2-2 E3/DS3 3-49
sales tool xi throughput capability
single-platform coverage 1-1 radio path 3-29
slip-fit connector 3-14 time slots
spares traffic measurement B-2
ordering 2-15 total cost
standard cables upgrade license 3-31
AUX EXA-001 3-54 traffic
STM1/OC3 critical 1-9
BNC 3-53 trib interface
LC optical 3-51 system parameter 2-8
SC optical 3-50 Tx to Rx spacing
Stratex Networks system parameter 2-7
intranet ix type approved 2-1
system parameters 2-7
add/drop capacity 2-8 U
equipment configuration 2-7
frequency band 2-7 upgrade
network topology 2-7 license,total cost 3-31
trib interface, backplane configuration 2-8
Tx to Rx spacing 2-7 V
V.24 modem driver 3-35
X
XPIC 1-10
8 Stratex Networks
Stratex Networks
Corporate Headquarters
120 Rose Orchard Way
San Jose, CA 95134
www.stratexnet.com
POG-000002-001_Rev 003_1204