IDU GE3 16x Product Description

ECLIPSE IDU GE3 16x
TM
PRODUCT DESCRIPTION
Rev.001
260-668201-001
Copyright & Terms of Use
March 2011
This Product Description incorporates features and functions supported with Eclipse,
software version 05.09, plus features and functions targeted for near-term release.
Copyright 2011 by Aviat Networks, Inc.

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, with-
out the prior written permission of Aviat Networks Inc.
To request permission, contact techpubs@aviatnet.com.
Warranty
Aviat 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, Aviat Networks reserves the right to revise this publication and to make
changes from time to time in the content hereof without obligation of Aviat Networks
to notify any person of such revision or changes.
Safety Recommendations
The following safety recommendations must be considered to avoid injuries to persons
and/or damage to the equipment:
1. Installation and Service Personnel: Installation and service must be carried out by
authorized personnel who have the technical training and experience necessary to be
aware of any hazardous operations during installation and service, and of measures to
avoid any danger to themselves, to any other personnel, and to the equipment.
2. Access to the Equipment: Access to the equipment in use must be restricted to serv-
ice personnel only.
3. Safety Norms: Recommended safety norms are detailed in the Health and Safety
sections of the Eclipse user manual.
l Local safety regulations must be used if mandatory. Safety instructions in the
user manual should be used in addition to the local safety regulations.
l In the case of conflict between safety instructions stated in the user manual and
those indicated in local regulations, mandatory local norms will prevail.
l Should local regulations not be mandatory, then the safety norms in the user
manual will prevail.
260-668201-001 MARCH 2011 1

ECLIPSE IDU GE3 16X PRODUCT DESCRIPTION
4. Service Personnel Skill: Service personnel must have received adequate technical
training on telecommunications and in particular on the equipment this product
description refers to.
Trademarks
All trademarks are the property of their respective owners.
2 AVIAT NETWORKS
Aviat Networks Service and Sales

Support
Service and Technical Support:
For customer service and technical support, contact one of the regional Technical Help
Desks listed below.
Americas Technical Help EMEA Technical Help Desk Asia Pacific Technical Help
Desk Desk
Aviat Networks Aviat Networks Aviat Networks
5200 Great America Parkway 4 Bell Drive Bldg 10, Units A&B
Santa Clara Hamilton International Technology Philexcel Industrial Park
CA 95054 Park M. Roxas Hi-way
U.S.A. Blantyre, Glasgow, Scotland Clark Freeport Zone
G72 0FB Philippines 2023
United Kingdom
Toll Free: (Canada/USA): Phone: +44 1698 717 230 Phone: +63 45 599 5192
800 227 8332 Fax: +44 1698 717 204 Fax: +63 45 599 5196
Phone: 210 561 7400
Fax: 210 561 7399
TAC.AM@aviatnet.com TAC.EMEA@aviatnet.com TAC.APAC@aviatnet.com
Or you can contact your local Aviat Networks office. Contact information is available
on our website at: http://www.aviatnetworks.com/services/customer-sup-
port/technical-assistance/
Sales and Sales Support:

For sales information, contact one of the Aviat Networks headquarters, or find your
regional sales office at http://www.aviatnetworks.com/contact-us/sales/
260-668201-001 MARCH 2011 3

Corporate Headquarters International Headquarters

North Carolina, USA Singapore
Aviat Networks, Inc. Aviat Networks (S) Pte. Ltd.
5200 Great America Parkway 17, Changi Business Park Central 1
Santa Clara Honeywell Building, #04-01
CA 95054 Singapore 486073
U.S.A.
Phone: +65 6496 0900
Phone: 408 567 7000
Fax: + 65 6496 0999
Fax: 408 567 7001
Sales Inquiries:
+1-321-674-4252
4 AVIAT NETWORKS
Table of Contents
Copyright & Terms of Use 1

Aviat Networks Service and Sales Support 3
Table of Contents 5
Eclipse IDU GE3 16x Product Description 8
Introduction To Eclipse IDU GE3 16x 9
IDU GE3 16x Modules 13
Front Panel 13
Module Overview 15
The Modules 15
RAC 60 15
DAC GE3 16
DAC 16xV2 29
AUX Module 30
NCC 32
FAN 33
RF Units 34
ODUs 34
ODU Construction and Mounting 35
ODU Data 35
ODU Accessories 36
ODU Cables and Cable Kits 36
Lightning Arrestor 37
Waveguide Flange Data 38
Environmental 39
IRU 600 39
Frequency Bands 40
IRU 600 Link Configurations 41
Radio Frequency Unit (RFU) 43
Antenna Coupling Unit (ACU) 44
IRU 600 Power Supply 46
RFU Tx Power Calibration 46
Environmental 47
ATPC 47
ATPC Operation 47
FCC Implementation 49
Power Supply 50
Power Consumption 50
Licensing 53
Capacity Licensing 53
260-668201-001 MARCH 2011 5

Feature Licensing 53
Link Capacity and Bandwidth 55
Fixed Modulation 55
Adaptive Coding and Modulation (ACM) 56
Adaptive Modulation (AM) 56
Coding 58
Modulation Change Criteria 60
Reference Modulation 62
Capacity, Modulation, Ethernet Throughput and Latency 63
Protected Operation 65
Hardware and Radio Path Protection 65
Hot Standby and Space Diversity 66
Ethernet Interface and Module Protection 67
E1/DS1 Tributary Protection 70
Protection Switching Conditions and Criteria 70
Switch Conditions: Hot-standby and Space Diversity 70
Switching Guard Times 71
Tx Online Switch Criteria 71
Rx Online Switch Criteria 72
Silent Tx Switching 72
Switching Times 72
PCR Operation 73
Orderwire Options 74
VoIP Orderwire 74
Digital Orderwire 75
Management Tools 76
Portal 76
PC Requirements 77
Portal TCP and UDP Port Usage 77
Portal Auto Version 77
Portal PC to Eclipse Connection Options 78
Portal Log-in 78
Eclipse Online Help 79
Portal Features 79
ProVision 80
Network Management 80
Element Configuration 81
ProVision Feature Summary 81
Diagnostics 85
System Summary 85
Event Browser 86
Alarms 87
History 88
Performance 89
Link Performance 89
NCC Performance 90
6 AVIAT NETWORKS
E1 Trib Performance 90
Ethernet Performance 91
System/Controls 93
Safety Timers 93
Link Options 94
DAC 16xV2 Options 95
DAC GE3 Options 97
AUX Menu 99
Loopback Points 99
Parts Screen 100
Advanced Management 100
260-668201-001 MARCH 2011 7

Eclipse IDU GE3 16x Product Description

This product description introduces features and capabilities of IDU GE3 16x and its
split-mount and all-indoor radio transceiver options.
Refer to:
l Introduction To Eclipse IDU GE3 16x on page 9
l IDU GE3 16x Modules on page 13
l RF Units on page 34
l Power Supply on page 50
l Licensing on page 53
l Link Capacity and Bandwidth on page 55
l Protected Operation on page 65
l PCR Operation on page 73
l Orderwire Options on page 74
l Management Tools on page 76
l Diagnostics on page 85
8 AVIAT NETWORKS
Introduction To Eclipse IDU GE3 16x

IDU GE3 16x is the most complete compact radio terminal of its type. It brings
together for all-IP and hybrid wireless backhaul:
l Split-mount on licensed bands 6 to 38 GHz.
l All-indoor on ANSI licensed bands 6 to 11 GHz.
l All-indoor on license-free 5.8 GHz ISM band (North America, Canada).
l QPSK to 256 QAM adaptive modulation
l Extensive IP traffic management capabilities
l Packet-synchronization options
l Flexible IP or hybrid IP+PDH link operation
l Broad diagnostic functions
l Sub-compact, 1 /2RU rack-print
l Inter-operation with Eclipse Packet Node
RFU options are the ODU 300hp or ODU 300sp for split-mount operation, or the IRU
600 for all-indoor.
Li sted features not supported at the March 2011 product

rel ease i ncl ude operati on on ANSI bands and i nteroperati on
wi th Ecl i pse Packet Node.
Addi ti onal features, not l i sted herei n wi l l be i ntroduced i n l ater
rel eases.
Contact Aviat Networks or your supplier for roll-out information.
260-668201-001 MARCH 2011 9

Figure 1-1. Eclipse IDU GE3 16x with RFU Options
Smaller, Smarter, Faster

IDU GE3 16x is especially effective for hybrid backhaul towards the network edge
where 4G-LTE IP/Ethernet transport is being deployed, and must operate alongside
existing 2G/3G legacy deployments. Its small size eases associated space challenges of
curbside and rooftop cabinet installations, and its low power consumption (less than
30W) simplifies power supply and cooling management. For ANSI markets full NEBS
compliance is enabled with the installation of an optional fan filter unit.
Towards the core it can be air or terminal interfaced to its big brother Eclipse Packet
Node where enhanced multi-link capabilities for more capacity, superior traffic aggre-
gation, and more inter-connection options are needed.
Adaptive or Fixed Modulation

Extensive fixed and adaptive modulation options are available. Adaptive modulation
maximizes available channel bandwidth through automatic adjustment of modulation
and/or coding so that the most data efficient (highest possible) modulation is used
over the prevailing path conditions.
IDU GE3 16x supports four modulation rates, QPSK, 16 QAM, 64 QAM, or 256 QAM,
plus a coding option on each for a total of eight modulation states. Any of the mod-
ulation states can also be separately selected for fixed operation. The choices ensure
maximum deployment flexibility.
l Adaptive modulation refers to the dynamic adjustment of modulation rate.
l Coding refers to an ability to set individual modulation rates for maximum
throughput, or maximum system gain.
For more information see Link Capacity and Bandwidth on page 55.
Hot Standby or Diversity Protection

Paired IDUs support 1+1 hot standby or space diversity operation.
Ethernet and E1/DS1 interface protection options are enabled on protected IDUs.
For more information see Protected Operation on page 65.
10 AVIAT NETWORKS
Carrier Class Ethernet Features

The Gigabit L2 switch capabilities include Synchronous Ethernet, 1+1 interface pro-
tection, and superior packet buffering and queuing.
l 6 user ports; 4x RJ-45 plus 2x SFP with optical or electrical transceiver options
l 8 priority queues per port
l 1+1 interface protection with protected IDUs
l Port and protocol-based priority assignment (MPLS Exp, DSCP, 802.1p)
l Strict, DWRR (Deficit Weighted Round Robin), and Hybrid scheduling modes
l VLAN tagging, untagging and filtering
l 136 Kbyte port buffers
l Jumbo frames to 10 Kbytes bi-directional
l Flow control
l IFG and Preamble suppression
l Synchronous Ethernet
For more information see DAC GE3 on page 16.
Extended E1/DS1 Transport Capabilities

l Up to 16x E1/DS1 via high-density front panel connectors
l 1+1 interface protection on protected IDUs
For more information see DAC 16xV2 on page 29.
Migration Optimized
Hybrid mixed-mode operation supports NxE1/DS1 side-by-side with native Gig or
Fast Ethernet.
An operator can locally or remotely configure the payload between Ethernet and
NxE1/DS1.
l The ratio of link capacity assigned between Ethernet and up to 16xE1/DS1 can
be changed at any time.
l Changing from Ethernet+NxE1/DS1 to all-Ethernet only requires a
configuration change. All link capacity is simply directed to Ethernet.
l There is no loss of transport efficiency when a mixed-mode link is ultimately
migrated to all-Ethernet.
Eclipse Node Inter-operation

IDU GE3 16x can be air-interfaced on 1+0 links with Eclipse Packet Node with RAC
60, DAC GE3 and DAC 16xV2 cards installed.
Portal and ProVision craft and network management tools are common to both plat-
forms.
Auxiliary Data Channels and Alarm Mapping

An auxiliary data interface is configurable for synchronous 64 Kbit/s, or up to 19.2
Kbit/s asynchronous, to transport 3rd party NMS (or other data), or to transport
Eclipse NMS over a 3rd party network to a remote Eclipse terminal or network.
260-668201-001 MARCH 2011 11

The Alarm I/O function of two TTL alarm inputs or up to four Form C relay outputs
supports capture of external alarms and their output to local or remote sites. Sim-
ilarly, internal alarms may be mapped to any output in the network.
For more information see AUX Module on page 30.
RFUs
There is a choice of split-mount or all-indoor operation using the ODUs or the rack-
mounted IRU 600.
Latest technology optimizes system performance with low power consumption and
market-leading reliability.
l ODU 300hp high Tx power on ETSI and ANSI bands 6 to 38 GHz.
l ODU 300sp standard Tx power on ETSI bands 7 to 38 GHz.
l IRU 600 high power on ANSI bands L6 to 11 GHz, and on 5.8 GHz ISM band
for North America and Canada
l IRU 600 standard power option on ANSI L/U6.
The compact 3RU IRU 600 is 1+1 optimized using independent RF units and a com-
mon antenna coupler unit (ACU). The filter-based ACU supports a wide choice of sys-
tem architectures, and an expansion port allows easy addition of links on an existing
path.
For more information see RF Units on page 34.
12 AVIAT NETWORKS
IDU GE3 16x Modules

This section introduces IDU GE3 16x user interfaces, the modules, and their function.
Refer to:
l Front Panel on page 13
l Module Overview on page 15
l The Modules on page 15
Front Panel
The front panel interfaces are shown below.
Figure 1-2. IDU GE3 16x Front Panel
Item Description
1 NEBS air filter Option. Where IDU is required to be NEBS (Network
Equipment-Building System) compliant, the fan air filter
must be installed.
2 Ground connection To rack, station or master ground. Includes provision for
wrist strap connection.
3 -48 Vdc power input 2-pin Phoenix style connector.
4 Fuse 5A slow-blow.
5 ODU connector A 3m SMA-male to N-female jumper cable is supplied
with each IDU.
6 Auxiliary data DB-9 connector. One synchronous (64 kbit/s) or
asynchronous (max 19.2 kbit/s) data service channel.
7 Alarm I/O HD-15 connector. Two TTL alarm inputs / four form C
relay outputs.
260-668201-001 MARCH 2011 13

Item Description
8 Status LEDs ODU Status LED
l Green indicates normal operation
l Orange indicates configuration not supported, soft-
ware/hardware incompatible, or diagnostic mode
selected, such as Tx Mute.
l Red indicates a critical alarm (traffic affecting).
IDU Status LED

l Green indicates normal operation
l Orange flashing indicates configuration not sup-
ported, software/ hardware incompatible, or diag-
nostic mode selected.
l Red indicates a critical alarm (traffic affecting), such
as LOS on a commissioned trib or a SW/HW failure.
9 Protection port For 1+1 IDU interconnection.
Provides bus interconnection between paired IDUs for
hot-standby or space diversity. Tx switching is not
hitless, Rx path switching (voting) is hitless/errorless.
Tx/Rx online and primary/secondary status is indicated
as
l Green Online LED is on for an the Tx/Rx online IDU.
l Green Online LED is off for the offline IDU.
l Orange Primary LED is on for the primary IDU. (The
primary designated IDU is default online for Tx and
Rx).
l Orange Primary LED is off for the secondary IDU.
10 Maintenance port RJ-45 connector. Serial data port for Portal access.
11 NMS ports 2x Ethernet RJ-45 ports for Portal and/or ProVision
access.
Login to these ports requires entry of the IP address for
the IDU, or use of the DHCP connection option. Ports
also provide NMS connectivity to co-located IDUs, INUs,
or other Aviat Networks, or third party radios. Ports
auto-resolve for straight or cross-over cables.
Orange activity LED flashes to indicate Ethernet traffic
on port. LED is solid on when there is no activity.
Green LED indicates a valid Ethernet connection. Off
indicates no connection or an invalid connection.
Operation is only valid for a 1000 Mbit/s (Gigabit)
connection. For 10/100Base-T, the LED is not
activated.
12 Tribs 1-8 8x E1/DS1 trib ports, 50 pin HDR connector.
13 Tribs 9-16 8x E1/DS1 trib ports, 50 pin HDR connector.
14 10/100/1000 Base-T 4x 10/100/1000 Base-T RJ-45 Ethernet user ports.
The green connection-status LED is on for a valid
Ethernet connection. Off indicates no connection or an
invalid connection. The orange activity LED flashes to
indicate Ethernet traffic on the port. The LED does not
flash (is solid on) when there is no traffic activity.
14 AVIAT NETWORKS
Item Description
15 SFP 2x SFP ports for optical or electrical transceivers.
Module Overview
IDU GE3 16x employs similar functionality to the plug-in cards of the same name in
the Eclipse Packet Node. For Portal configuration purposes they are identified as plug-
ins to maintain this Packet Node commonality. The following figure illustrates main
IDU GE3 16x modules and internal interconnection.
Figure 1-3. IDU GE3 16x Main Modules
The Modules
Module function is similar to that supported on the plug-in cards of the same name
for the Eclipse INUs. Portal and ProVision configuration and management is common
to both.
Refer to:
l RAC 60 on page 15
l DAC GE3 on page 16
l DAC 16xV2 on page 29
l AUX Module on page 30
l IDU GE3 16x Modules on page 13
l FAN on page 33
RAC 60
RAC 60 uses a direct data packet-plane (DPP) connection to the DAC GE3 module to
support airlink capacities to 366 Mbit/s and Ethernet data throughputs to more than
450 Mbit/s.
260-668201-001 MARCH 2011 15

LDPC (Low Density Parity Check) FEC encoding, and adaptive equalization is stand-
ard.
Features include:
l Adaptive coding and modulation (ACM) - QPSK to 256 QAM with errorless
switching between ACM states
l Static/fixed modulation operation using any individual ACM rate
l Adaptive modulation channel bandwidths 7 to 56 MHz ETSI, 10 to 80 MHz
ANSI
l Fixed modulation channel bandwidths 7 to 56 MHz ETSI, 3.75 to 80 MHz ANSI
l Link capacities to 366 Mbit/s ETSI (56 MHz), or to 320 Mbit/s (50 MHz) or 365
Mbit/s (80 MHz) ANSI
l Ethernet throughputs to 460 Mbit/s (L1, 64 byte frames)
l Fully redundant 1+1 hot-standby or space diversity operation using paired
IDUs
For information on link capacity and bandwidth options, see Link Capacity and Band-
width on page 55
For information on 1+1 protected operation, see Protected Operation on page 65.
DAC GE3
DAC GE3 is an extended-feature Gig-Ethernet switch. It brings extended scheduling
options, implements true ingress traffic policing, supports synchronous Ethernet, and
supports interface protection in conjunction with an IDU protection partner.
Capabilities include:
l Synchronous Ethernet
l 1+1 protection
l Extended packet buffering and queuing options
l VLAN tagging
Capabilities will be extended with later releases of Eclipse SW.
Refer to:
l DAC GE3 Description on page 17
l Basic Port Settings on page 18
l Basic Switch Settings on page 19
l Switch Fabric and VLAN on page 19
l QoS on page 21
l Synchronous Ethernet on page 24
l Link Status Propagation on page 29
l Ethernet Traffic Redundancy on page 29
16 AVIAT NETWORKS
DAC GE3 Description

Four RJ-45 10/100/1000Base-T electrical ports and two SFP (Small Form-factor Plug-
gable) ports for optical or electrical transceivers connect to an Ethernet switch, which
provides bridge/switch and queuing functions between the user ports and an internal
DPP port for connection to the RAC 60 module.
The switch analyzes the incoming Ethernet frames for source and destination MAC
addresses and determines the output port over which the frames will be delivered. The
MAC address register supports 16k entries.
DPP capacity for Ethernet traffic is determined in multiples of 2 Mbit/s or 1.5 Mbit/s
up to the maximum configured on the RAC 60 link module
l Traffic capacity is a link function (link bandwidth).
l Burst capacity is a function of port buffer size (136 Kbytes).
Ethernet traffic throughputs are frame-size dependent and optimized by IFG and
Preamble suppression. For throughput and latency data see Link Capacity and Band-
width on page 55.
Fixed and dynamic traffic shaping is used in conjunction with the RAC 60 module to
ensure DAC GE3 traffic bandwidth is optimally matched to the link capacity on fixed
or adaptive modulation links. The full capacity of links can dedicated to Ethernet traf-
fic, or Ethernet can be configured to ride side by side with up to 16xE1/DS1 circuits.
Phased Release of Features

The features listed below apply from SW release 05.09. For information on features tar-
geted for future release, contact Aviat Networks or your supplier for details.
Features Supported at SW Release 05.09
l Four RJ-45 10/100/1000Base-T ports
l Two ports for SFP transceivers. SFP options are::
o 1000Base-LX optical 1310 nm single-mode (IEEE 802.3z compliant)
o 1000Base-SX optical 850 nm multi-mode (IEEE 802.3z compliant)
o 1000Base-T electrical with RJ-45 connector (IEEE 802.3ab compliant)
l Switch fabric configurable for Transparent or Advanced VLAN modes
l Quality of Service (QoS):
o 802.1p mapping
o DiffServ mapping (IPv4, IPv6)
o MPLS Exp bits mapping
o Priority scheduling for Strict, Deficit Weighted-Round-Robin (DWRR), or
Hybrid (Strict + DWRR)
o Eight transmission queues
l Flow control
l Frame and burst handling
o 136 Kbytes memory for each ingress/egress port buffer pairing
o Jumbo frames up to 10 Kbytes bi-directionally
260-668201-001 MARCH 2011 17

l Redundancy
o Optical Y-cable protection with 1+1 partnered IDUs
l Synchronization
o Synchronous Ethernet
o Timing via Airlink Recovered Timing (ART) or Eclipse Distributed Sync
(EDS) on radio links
o Local clock provides Stratum 3 hold-over performance
l Monitoring
o Status per port
o Resolved speed per port
o Resolved duplexing per port
o Performance graphs (RX and TX throughputs and discards per port)
o RMON-1 statistics per port
Table 1-1. SFP Optical Port Specifications
SFP Type: Single Mode 1000Base-LX Multimode 1000Base-SX

Center Wavelength 1310 nm 850 nm
Maximum launch power -3 dBm -4 dBm
Minimum launch power -9.5 dBm -9.5 dBm
Maximum optical input -3 dBm 0 dBm
power
Minimum optical input -20 dBm -18 dBm
power (sensitivity)
Link distance To 10 km / 6 miles with 9/125 m optical Less than 500m. Intended for local switch-
fiber; 550m / 600 yards with 50/125 m to-switch, bus extension and
or 62.5/125 m fiber. multiprocessing applications.
Supply SFP is an optional extra. Part number SFP is an optional extra. Part number 079-
079-422656-001. 422662-001.
Safety Class 1 laser product complies with EN 60825-1
Table 1-2. SFP Electrical Port Specifications
SFP Type: 1000Base-T

Connector RJ-45
Cable type Shielded or unshielded twisted pair Cat5 cable
Link distance 100m
Supply SFP is an optional extra. Part number 083-845434-001.
Basic Port Settings

Parameters for front-panel and backplane ports include:
l A port naming field
l Usage, with user port options of normal, disabled, optical-Y (for protected
IDUs)
18 AVIAT NETWORKS
l Speed-Duplex, with selections on auto or manual settings for speed, and half or
full duplex
l Port Status, with indications of Port-Up on detection of a valid Ethernet
connection with valid framing, and Resolved to indicate auto-resolution of
speed and duplex for an Auto or 1000 Mbit/s selection.
Basic Switch Settings

l Maximum Frame Size. Minimum 64 bytes, maximum 10,000 bytes, bi-
directional.
l Flow Control. Implements use of IEEE 802.3x PAUSE frames.
l MAC Address Learning. Address learning is default enabled. A disable option is
provided for use in a ring/mesh network where protection is provided by an
external RSTP switch.
Switch Fabric and VLAN

DAC GE3 supports extensive, flexible VLAN configuration capabilities. The options
provided not only set VLAN tagging and filtering, but also enable selection, and where
required customization of cross-connections (the switch fabric) between all ports using
an internal 'Tag0' 802.1Q/802.1p tagging mechanism. It provides a means to manage
all traffic within the DAC GE3 switch, from switch ingress to egress.
All traffic ingressing the switch is VLAN tagged, but the tagging is only carried
beyond the switch where:
l VLAN segregation of traffic streams is required over a common Ethernet path.
l A user-specific VID is added to an ingressing frame.
l The VID of an ingressing frame is replaced by a different VID.
Switch Fabric
l The VLAN screen sets the switch fabric, the association of ports with ports.
Diagrams within the Portal screen illustrate the selection.
l There are two operational modes, Transparent, and Advanced.
l Transparent mode is the normal (default) selection whereby all enabled ports
are grouped together (interconnected). Port grouping can be customized and
saved for export to other Portal PCs.
l Advanced mode table settings include Port VID and membership settings which
engineer the switch fabric, and the action taken (or not) on the tag settings for
traffic ingressing and egressing the switch.
VLAN Function
VLANs enable segregation of users on a LAN from other users on the same LAN.
VLANs behave as if they were on a separate LAN, even though they all share the same
physical network and network address.
They are typically used to segment a network to provide improved security, work-
group management and traffic control. Different user groups, such as HR, finance and
marketing, can be assigned their own virtual LAN that can span multiple sites.
260-668201-001 MARCH 2011 19

VLANs are software-configured; they are not constrained by the physical topology of a
network.
VLANs also enable traffic prioritization to support QoS needs. Where Ethernet band-
width is restricted, traffic tagged as high priority will transit a switched network
ahead of lower priority or untagged traffic. This is particularly relevant where VLANs
are transported over a service-provider network.
VLANs can also be stacked to provide a demarcation between customer and service
provider networks. Multiple customer VLANs can be stacked on a service-provider
VLAN, with the service provider able to provide each with a unique priority to support
service level agreements (SLAs).
The term VLAN i s speci fi ed i n I EEE 802.1Q. I t defi nes a method
of di fferenti ati ng traffi c on a LAN by taggi ng the Ethernet
frames. By extensi on, a VLAN refers to traffi c separated by Eth-
ernet frame taggi ng.
VLANs are typically established by grouping user switch ports under a common VLAN
membership identifier (VLAN ID). Each VLAN uses a different VLAN ID.
l Ethernet frames ingressing a VLAN port have a VLAN tag inserted that includes
the VLAN ID.
l Switches within the network use this tag to maintain VLAN
membership/segregation over common trunk links.
The tag format, defined in 802.1Q, uses 4 bytes, which are added to the normal Eth-
ernet frame.
l The first 2 bytes specify the Ethernet type (Ethertype), which is used to detect
tagged 'Q Ethernet' frames.
l The second 2 bytes provide tag control information, which includes 12 bits for
the VLAN ID, 3 bits for defining a Class of Service (CoS) priority, and 1 bit for
compatibility use between Ethernet and other technologies.
l The VLAN ID bits support a maximum of 4096 identifiers (0 to 4095). A
unique number within this range is used to identify all ports belonging to a
particular VLAN.
l The CoS bits are defined in 802.1p and support 8 different priority settings, 0 to
7, with 7 the highest. See QoS below.
With the DEC GE3 Advanced Mode selected, a wide range of VLAN based ingress and
egress combinations are provided. These include:
l The setting of user-specific VLAN transport options.
l Selective frame acceptance at ingress, with options of untagged only, tagged
only, or tagged only but then only for frames with an 8100 or 88a8 TPID
(Hexadecimal 0x8100 or 0x88a8). Other frames are blocked.
l The tagging of untagged frames only, or the tagging of all frames except frames
with an 8100 or 88a8 TPID.
l VID (VLAN ID) replacement, whereby the VID of an incoming 8100 or 88a8
frame is replaced by the DAC GE3 port VID.
l The pushing of frames that have been tagged by the DAC GE3 into an external
network. Currently VLAN tags applied within the switch have their priority bits
20 AVIAT NETWORKS
set to 0 (low/no priority). If pushed into an external network, it will be with a

an 802.1p priority of 0. Contact Aviat Networks or your provider for information
on planned changes to this capability.
l Settings can be saved for export to other Portal PCs.
QoS
QoS (Quality of Service) is generally referred to in the context of providing a priority
service for selected traffic. It particularly concerns delay-sensitive multimedia traffic,
such as voice and video. Without prioritization, such services may become unusable
on congested networks.
QoS also concerns service differentiation, where there is a need to support one cus-
tomer's traffic over another to ensure agreed service levels are maintained.
The need for prioritization goes hand-in hand with bandwidth, where the more
restricted the bandwidth, the greater the likelihood of congestion and consequent
delays and dropped frames.
The QoS tools most used are prioritization and scheduling, where priority tagged traf-
fic is queued within a buffer and scheduled for transmission using one or more prior-
ity management schemes such as strict or deficit weighted-round-robin (DWRR).
Pri ori ti zati on opti ons provi de operators wi th tool s to opti mi ze
traffi c fl ows when demands on Ethernet bandwi dth exceed
avai l abi l i ty. Thi s i s especi al l y rel evant to confi gurati ons where
l i nk capaci ty i s modi fi ed by adapti ve modul ati on, or by redun-
dancy wi thi n a l i nk aggregated group.
The DAC GE3 QoS tools include ingress truth and tag mapping, egress limiting, port
prioritization, and traffic scheduling (forwarding).
Ingress Truth and Tag Mapping
The Ingress Truth and Tag mapping facility queues traffic using tag prioritization tech-
niques.
Ingressing Ethernet traffic is prioritized on a frame-by-frame basis using the CoS
(Class of Service) bits in the VLAN field of an Ethernet header, the DSCP bits in the
Differentiated Services (DiffServ) field of an IP header, or the MPLS (Multi Protocol
Label Switching) Exp (experimental) bits within the MPLS header of a label switch
path network.
l CoS defines Ethernet frame priority. A priority is configured when a port is set
for IEEE 802.1Q VLAN tagging. The three bits available for CoS enable an eight-
level prioritization (0 to 7, with 7 the highest). The use of the prioritization bits
is defined in IEEE 802.1p.
l DiffServ defines IP packet priority (IP precedence) using the DSCP
(Differentiated Services Code Point) field. It is designed to tag a packet so that
it receives a particular forwarding treatment or per-hop-behavior (PHB) at each
network node. The six bits available enable 64 discrete DSCP values or
'priorities' (0 to 63) with 63 the highest.
260-668201-001 MARCH 2011 21

l MPLS Exp defines the Multiprotocol Label Switching (MPLS); IP traffic is

forwarded based on its MPLS label. The three bits available enable an eight-level
prioritization (0 to 7, with 7 the highest).
l Tag values are typically set using an L2 switch (CoS), router/L3 switch
(DiffServ), MPLS label switch router (MPLS Exp). They may also be set from
within some applications.
l Advanced L2 switches such as the DAC GE3 can look into the DiffServ field of
an IP header and into the Exp bits of an MPLS header. Similarly, L3 devices can
look into the CoS field of a L2 frame. This enables a DiffServ or MPLS value to
be mapped into the CoS range, and vice-versa.
Within the DAC GE3 module ingressing frames are mapped to the internal priority
queue according to their tag information. Frames are first examined for MPLS Exp
bits, followed by DSCP and 802.1p. Untagged frames are subject to a Port QoS profile
(Port Default). The following table illustrates the sequencing.
Figure 1-4. DAC GE3 QoS Truth Table
The table below shows the default queue mapping of MPLS Exp, DSCP and 802.1p to
the internal priority queue. Settings can be customized per port, or set to apply to all
ports, and saved onto your PC for distribution to other users.
Table 1-3. Default Priority Mapping Table
Traffic Class Internal Priority Queue 802.1p Tag IP DSCP MPLS EXP
Network Control Q7 7 56-63 7
Voice Q6 6 48-55 6
Video Q5 5 40-47 5
Controlled Load Q4 4 32-39 4
Excellent Effort Q3 3 24-31 3
Spare Q2 2 16-23 2
Background Q1 1 8-15 1
Best Effort Q0 0 0-7 0
22 AVIAT NETWORKS
Limit Egress
This option limits (shapes) the egress bandwidth (speed) on ports. It sets the max-
imum speed from a port. It is used where transmit rate-limiting is required on the net-
work transporting Ethernet traffic from the port.
Port Default
This facility allows traffic on one user port to be prioritized over that on other ports. It
has relevance where two or more ingress ports share a common egress port. For oper-
ation in the presence of tagged frames see the QoS Truth Table above.
Scheduler
Scheduling is about how traffic within a queue is managed for de-queuing (for-
warding) over a link.
Scheduler operation applies on ports that have multiple traffic classes enqueued for
transmission. On the DAC GE3 module queued traffic is forwarded using scheduling
options of Strict Priority (SP), Deficit Weighted Round Robin (DWRR), or a com-
bination of SP with DWRR (Hybrid).
l With Strict priority the scheduler serves a lower priority queue only if all higher
priority queues are empty.
l With DWRR the scheduler operates as a weighted round-robin (WRR) with a
deficit counter.
o DWRR adds a 'deficit counter' mechanism to WRR. Essentially it measures
and adjusts for packet sizes per queue.
o Compared to WRR, it enables fairer treatment of traffic flows that have
different packet sizes.
l Hybrid enables a combination of strict with DWRR. It default applies Strict to
Q7, Q6, Q0, and DWRR to the remainder. Hybrid represents a typical scheduler
implementation.
l The figure below illustrates Scheduler selection options in the DAC GE3 Portal >
Plug-ins screen.
o The option of Strict, DWRR or Hybrid is selected for each configured port or
transport channel.
o The scheduler option selected default applies to all traffic classes on the port
(all eight internal priority queues, 0 to 7).
o This can be user-configured (customized) to be a mix of any of the three
options, in any order.
o Colored icons indicate by size/segment the relative weighting applied to each
traffic class within a queue.
o For DWRR the weight applied to each traffic class within a queue can be
adjusted over a range of 1 to 255 to provide fine tuning of relative weights.
o A customized setting can be saved onto your Portal PC for forwarding to
other users.
260-668201-001 MARCH 2011 23

Figure 1-5. Example Scheduler Windows from the Portal QoS Screen
Synchronous Ethernet
Standard 802.3 Ethernet is asynchronous - it contains no provision for transferring a
clock reference. At issue is how to maintain required clocking during migration to an
all-IP network. This particularly applies to mobile backhaul networks (where TDM
clocking (E1/DS1) has been the norm) when migrating to IP/Ethernet.
l Mobile base stations must be synchronized to support hand-off between cells,
and to ensure frequencies on the air-interfaces have the accuracy and stability
needed to minimize channel interference.
l For GSM / UMTS nodes on a TDM wireless backhaul network, required
frequency synchronization has typically been provided by the TDM clock.
l For CDMA nodes requiring a time-referenced phase sync source, clocking has
typically been provided by a GPS receiver installed at the site.
l Both frequency and phase synchronization solutions are required for 4G/LTE
base stations.
IDU GE3 16x clock transport solutions include Synchronous Ethernet and hybrid
mixed-mode operation. Packet-based IEEE 1588v2 is passively (transparently) trans-
ported.
Synchronous Ethernet (SyncE) supports precise network timing in a manner sim-
ilar to that provided on a TDM network whereby a clock signal injected into the bit
stream. On IDU GE3 16x radio links the clock is transported using Airlink Recovered
Timing (ART) or Eclipse Distributed Sync (EDS).
On IDU GE3 16x links ART should be used. EDS should only be used if the mod-
ulation in use does not support ART. ART provides superior clock stability over mul-
tiple hops.
On the DAC GE3 module, SyncE clock source selection is provided for:
l Port, to source the clock from a front panel SyncE connection; ports P1-P4
electrical, ports P5-P6 optical. Sync port fall-back is not currently supported.
l Rx ART (Airlink Recovered Timing) to source clocking from the radio link.
24 AVIAT NETWORKS
l TDM Clock, to source E1/DS1 clocking from a DAC 16xV2 trib connection, or
from an EDS trib. Where an E1/DS1 input to a DAC 16xV2 is for sync purposes
only, it can be can be framed or unframed E1/DS1.
l Internal, to source the DAC GE3 internal clock (Stratum 3).
Should the selected clock-source fail the internal Stratum 3 clock provides high quality
holdover (will continue to provide clocking) at the clock rate established immediately
prior to loss of the selected clock source.
A feature license is required for Synchronous Ethernet operation; see Licensing on
page 53.
Airlink Recovered Timing (ART) versus Eclipse Distributed Sync

(EDS)
ART uses the radio link (symbol rate) clock.
l The link Tx clock is locked to the SyncE clock source and recovered at the far
end of the link.
l There is no impact on traffic payload.
l Clock quality is G.8262 compliant.
l ART operation is not supported on all RAC 60 modulation profiles.
EDS transports the clock via a multicasted E1 or DS1 circuit within the payload.
l Instead of a dedicated E1 or DS1 circuit per destination, just one E1 or DS1
circuit is used on links throughout the network for all destinations.
l It is primarily for use on Eclipse Packet Node networks; networks that do not
currently support ART on RAC 60, or have other RAC types installed.
l Clock quality is G.823 compliant.
l For the IDU GE3 16x, EDS should only be used where the modulation in use
does not support ART.
The distribution of the clock within the IDU GE3 16x for ART and EDS is similar.
ART Operation
From a SyncE user connection to a DAC GE3, the clock signal is extracted, cleaned,
and made available for distribution to the RAC 60 and/or DAC 16xV2 modules.
Similarly, the clock from an E1/DS1 trib connection (traffic-carrying or for sync only),
is likewise made available for distribution.
l A local clock input an can be sourced from a SyncE input to the DAC GE3, or
from an E1/DS1 trib.
l A local clock output can be delivered as SyncE from a DAC GE3 port, or as an
EDS E1/DS1 clock from a DAC 16xV2 tributary connection.
l The integrated 10/100/1000Base-T front-panel ports and the SFP ports
equipped with an optical transceiver are capable of SyncE input and output.
SFP ports equipped with 1000Base-T (electrical) transceivers do not support
SyncE.
An embedded Stratum 3 clock in the DAC GE3 provides high-quality hold-over in the
event the SyncE timing source is interrupted. The DAC GE3 is effectively the 'clock
master' for the IDU.
260-668201-001 MARCH 2011 25

The following figure illustrates the sync path through a non-protected terminal for
SyncE and E1/DS1 clock sources.
l For SyncE, the clock is directed to the DAC GE3 sync port where it is coupled to
the RAC 60 to provide its ART clock source.
l For E1/DS1, the clock is directed from the DAC 16xV2 to the DAC GE3 sync
port, where it is coupled to the RAC 60 to provide its ART clock source.
l The S3 clock on the DAC GE3 is synchronized to the incoming clock.
Figure 1-6. Sync Paths Through an IDU GE3 16x at Sync Source
The following figure illustrates the sync path through a 1+1 protected terminal for a
SyncE clock source. In this example the SyncE input is directed to the primary IDU
GE3 16x. It can be directed to both IDUs using an optical Y-cable connection. Sim-
ilarly, for an E1/DS1 source, a trib Y-cable can be used to connect the DAC 16xV2 mod-
ules. See Protected Operation on page 65.
l IDU and DAC GE3 protection cables, and an NMS inter-connect cable are
installed.
l On the primary IDU the clock source is directed to the DAC GE3 sync port,
where it is coupled to the RAC 60 as its ART clock source.
l It is also coupled to the DAC GE3 protection port, and made available to the
secondary (standby) RAC 60 via its DAC GE3 sync port.
26 AVIAT NETWORKS
Figure 1-7. Sync Paths Through a 1+1 Protected IDU GE3 16x at Sync Source
The following figure illustrates the sync path through a non-protected repeater.
l ART is sourced from the receiving RAC and directed to the DAC GE3 Sync port.
l From the Sync port it is made available to all enabled DAC GE3 user ports to
provide clocking for SyncE.
l For an E1/DS1 sync output, DAC GE3 Sync is directed to the DAC 16xV2.
l Sync is received on the upstream IDU GE3 16x via its DAC GE3 traffic port
connection, and directed to the sync port.
l With sync enabled on the RAC 60, sync is directed to the RAC 60 to provide its
ART clock.
l The S3 clock on each DAC GE3 module is synchronized with the ART clock to
provide a high-quality fail-over source.
Figure 1-8. Sync Path Through Repeater: ART Clock Source
The following figure illustrates the ART sync path through a 1+1 protected repeater.
IDU and DAC GE3 protection, and NMS inter-connect cables are installed.
For SyncE traffic the primary/online IDUs are shown interconnected via a single DAC
GE3 port P1. Superior protection capabilities are provided using back-to-back optical
Y-Cables as the interconnect.
E1/DS1 circuits (not shown) are trib-connected between the DAC 16xV2 modules.
l On both downstream IDUs the ART clock is sourced on its RAC 60 and directed
to the DAC GE3 sync port.
l Under normal operation the downstream primary IDU provides the sync (and
traffic) connection to the upstream primary IDU via DAC GE3 port 1.
l For an Rx path failure:
o For a secondary Rx path fail: no change.
260-668201-001 MARCH 2011 27

o For a primary Rx path fail the stratum 3 clock in the primary DAC GE3
provides clock holdover.
l For a downstream RAC 60 failure:
o For a secondary RAC 60 fail: no change.
o For a primary RAC 60 fail the secondary IDU becomes the online IDU, but
sync to the upstream IDUs is maintained by the stratum 3 holdover clock in
the primary DAC GE3 .
n To restore ART clocking to upstream IDUs the downstream primary DAC
GE3 is remotely or locally reconfigured to source its sync from the
secondary IDU via the IDU GE3 protection cable (P4).
n Alternately, to restore ART clocking to the upstream IDUs the Ethernet
interconnection cable from the upstream DAC GE3 is changed to the
downstream secondary DAC GE3.
l For a downstream DAC GE3 failure:
o For a secondary DAC GE3 fail: no change.
o For a primary DAC GE3 fail the secondary IDU becomes the online IDU.
ART and holdover clocking is restored by changing the Ethernet
interconnection cable from the upstream DAC GE3 to the downstream
secondary DAC GE3.
l For an upstream DAC GE3 failure:
o For a secondary DAC GE3 fail: no change.
o For a primary DAC GE3 fail the secondary IDU becomes the online IDU, and
sync is maintained by the stratum 3 clock in the secondary DAC GE3.
n ART clocking can be restored by changing the Ethernet interconnection
cable from the downstream DAC GE3 to the upstream secondary DAC
GE3.
l For an upstream RAC 60 failure:
o For a secondary RAC 60 fail: no change.
o For a primary RAC 60 fail the secondary IDU becomes the Tx online IDU,
but ART is maintained via the primary IDU GE3 via the DAC GE3
protection cable.
Figure 1-9. Sync Path Through 1+1 Protected Repeater: ART Clock Source
28 AVIAT NETWORKS
Link Status Propagation

Link Status Propagation (LSP) supports rapid detection of Ethernet link status. It is
intended for use by external equipment that relies only on port status (up/down) to
itself respond to changed link status.
l LSP forces a port shutdown at both ends of the link in the event of a link failure,
and restores operation at both ends when normal link operation returns.
l It is used where external user devices, such as switches running RSTP or other
protocols use only Ethernet port status to trigger a topology change, protection,
redundancy, or link recovery.
LSP must be enabled on DAC GE3 at both ends of the link for correct LSP operation.
l LSP operation is selected per user port.
l LSP-enabled user ports at both ends of a DAC GE3 link automatically shut
down upon failure of the link. Ports are opened once the link is recovered.
l When a local user port is down due to Ethernet cable disconnection or external
device failure, the related user port(s) on the far-end DAC GE3 are shut down.
l A Normal (default) or Degraded operational mode is available.
o With Normal selected, a degradation in path capacity, such as can occur
under adaptive modulation or link aggregation will not force a port
shutdown. A link has to be completely down to force a port shutdown.
o With Degraded selected, any reduction in link capacity will force a link/port
shutdown. Link is degraded when current Tx capacity is less than maximum
capacity. This mode is useful where there is preference on a customer
network to switch to an alternate path when the Eclipse link is degraded
(has reduced capacity), instead of being completely down.
LSP operati on i s currentl y not operati onal for 1+1 protected
I DUs.
Ethernet Traffic Redundancy

The DAC GE3 modules in 1+1 protected IDUs support comprehensive protection of
port and switch functions. See Protected Operation on page 65.
DAC 16xV2
Access to the DAC 16xV2 trib module requires installation of the EZF-10000 feature
license. See Licensing on page 53.
Operation supports 16xE1 or 16xDS1 tributaries with:
l E1/DS1 line code selection.
l Tributary protection.
l Compact HDR interface connector and cable sets.
260-668201-001 MARCH 2011 29

Line Code Selection

E1 options are 75 ohm unbalanced or 120 ohms balanced. Selection applies to individ-
ual tribs.
DS1 line impedance is fixed at 100 ohms balanced with per-trib selection of of AMI or
B8ZS.
Tributary Protection
l 1+1 protected IDUs (hot-standby, space diversity) provide trib protection on the
DAC 16xV2 modules.
l Y-cable assemblies are used to interconnect protected IDUs with the customer
equipment.
l Protection switching operates on all tribs. If one trib fails all tribs (Tx and Rx)
are switched.
For more information see Protected Operation on page 65.
Trib Connectors and Cables

E1/DS1 tribs are accessed on two high density 50 way HDR-E50 connectors; 8 tribs
per connector.
Compact trib cable sets for non-protected and protected operation are available to con-
nect to BNC or wire-wrap / displacement block. The cable exits the HDR connector
straight out from its back-shell.
Cable options are:
l HDR-E50 to 26AWG free end 3m, 10m, 15m, 32m
l HDR-E50 to 24AWG free end 3m, 10m, 15m, 32m
l HDR-E50 to 16xBNC 2m, 5m
l HDR-E50 to RJ45 straight cable 2m, 5m
l 2x HDR-E50 Y-cable to 24AWG free end 3m, 15m, 32m
l 2x HDR-E50 Y-cable to 16xBNC 2m
Refer to the Eclipse User manual, Appendix D, for cable pin-outs.
AUX Module
The AUX module provides a user-configurable auxiliary data channel, and alarm
input and output (I/O) options. Intended applications are:
l Transport of 3rd party NMS (or other data) over an Eclipse network.
l Transport of Eclipse NMS over a 3rd party network to a remote Eclipse node or
network.
30 AVIAT NETWORKS
Auxiliary Data Interface

The interface is configured in Portal for synchronous 64 kbps data or serial data to
19.2 kbps.
l Synchronous conforms to TIA/EIA-422 / V.11 at 64kbps, with selectable clock.
The source of the transmit clock can be set to internal (provided by the auxiliary
card) or external (provided by the user). For an external clock, channel
synchronization is supported by a selectable clock phase (rising or dropping
edge of the clock pulse).
l Asynchronous conforms to TIA/EIA-562 (electrically compatible with RS-232 /
V.24 but via a DB-15 connector rather than a DB-9)
l Asynchronous baud rates are 1200, 2400, 4800, 9600, or 19200bps with the
following format options:
l 1 start, 7 data, 1 parity, 2 stop
l 1 start, 8 data, no parity, 2 stop
Auxiliary Data and NMS Functions

Two data function options are provided, Data and NMS:
Data Option
Customer data type can be configured for asynchronous V.24/RS-232, or synchronous
V.11/RS-422.
At intermediate sites, the data channel must be re-directed to the next IDU (or Eclipse
INU).
At the destination site, the channel is directed to the required port on the AUX plug-
in.
NMS OPtion
l Eclipse NMS is provided for transport over a 3rd party network to a remote
Eclipse IDU/INU/network, where it must be ported back in via an AUX module.
l The data type is default configured for synchronous V.11/RS-422, 64 kbps.
Alarm I/O Interfaces

The AUX function supports two TTL alarm inputs and four Form C relay outputs.
Individual alarm inputs and relay outputs can be named. A severity level can be
assigned to alarm inputs.
260-668201-001 MARCH 2011 31

Alarm Inputs
The active state of each TTL alarm input is configurable to be active if the voltage on
the input is high, or active if the voltage is low. The alarm software detects a change
in the state of each input circuit, and raises or clears an input accordingly. The nom-
inal alarm polling rate is 1 second. Fleeting changes are ignored.
l Input state changes are captured in the event log as an alarm.
l TTL input thresholds are specified at 2V min high, and 0.8V min low. High
voltage (spike) protection to 48V is included.
Alarm Outputs
The output relays may be configured to be energized or de-energized on receipt of an
alarm event.
Both normally closed and normally open contacts are available on the I/O connector.
State changes are captured in the event log as an informational event.
Relay contact specifications:
l Maximum Voltage 250 Volts
l Maximum Current 2 Amps
l Maximum Power 60 Watts
These are maxi mum val ues, whi ch requi re de-rati ng i f the
rel ay i s to be used for frequent-swi tch appl i cati ons. The con-
tact vol tage must be restri cted to l ess than 60 Vol ts for compl i -
ance wi th SELV regul ati ons. Maxi mum current speci fi cati on
appl i es up to 30 Vol ts.
Alarm Mapping
Events are mapped to outputs:
l Individual AUX alarm inputs or internal alarm events may be mapped to any
output within the network.
l Multiple input or internal events may be mapped to a common output.
l Mapping is achieved using IP addressing for the destination node, plus a AUX
slot location (for an INU destination) and an output number.
NCC
The NCC module manages IDU operation. Primary functions include:
l Microprocessor control and management
l Bus clock and signaling distribution
l Boot (start-up) flash
l License and configuration flash
l DC/DC converter
32 AVIAT NETWORKS
l Network management access

l Voltage and temperature levels management
Configuration, software load, and license data for the IDU is held on a Comapct Flash
(CF) card, which is inserted into the rear of the IDU. Each CF card is identified by a
unique serial number; which is the license number for the IDU.
l The current configuration is held on the CF card.
l The operating system SW version and the version immediate prior are held on
the card. A facility allows SW rollback to the prior version.
FAN
IDU GE3 16x incorporates two long-life axial fans for cooling.
Fan operation is temperature controlled and is performance monitored by the NCC
module. Under normal conditions one fan operates, cycled between the two fans. Both
fans operate if the first fan fails to keep the temperature below a preset threshold.
For NEBS compliance an air filter option must be installed. It is supplied as a kit and
fitted to the left side of IDU (next to the grounding post).
260-668201-001 MARCH 2011 33

RF Units
IDU GE3 16x is installed as a split-mount radio with an ODU, or as an all-indoor
radio with the IRU 600.
l ODU 300hp supports ETSI and ANSI bands 6 to 38 GHz
l ODU 300sp supports ETSI bands 7 to 38 GHz
l IRU 600 supports ANSI bands 6 to 11 GHz, and the FCC and Industry Canada
5.8 GHz ISM band
For hot-standby protected split-mount operation the two IDUs are installed with two
ODUs, with the ODUs mounted onto a single antenna via a coupler unit. For space
diversity, each ODU is connected to its own antenna.
For hot standby protected all-indoor operation the two IDUs are connected to one IRU
600 fitted with two RFUs (IRU 600 is 1+1 optimized). A single waveguide feed con-
nects to the antenna. For space diversity, separate waveguide feeds are used.
Refer to:
l ODUs on page 34
l IRU 600 on page 39
l ATPC Operation on page 1
ODUs
Refer to:
l ODU Construction and Mounting on page 35
l ODU Data on page 35
l ODU Accessories on page 36
l ODU Cables and Cable Kits on page 36
l Lightning Arrestor on page 37
l Waveguide Flange Data on page 38
34 AVIAT NETWORKS
Figure 1-10. Eclipse ODU 300hp on 300mm Antenna
ODU Construction and Mounting

Construction comprises:
l Cast aluminium base (alloy 380)
l Pressed aluminium cover (sheet grade alloy 1050).
l Base and cover passivated and then polyester powder coated
l Compression seal for base-cover weatherproofing
l Carry-handle
ODUs meet the ASTME standard for a 2000 hour salt-spray test, and relevant IEC,
UL, and Bellcore standards for wind-driven rain.
Antenna mounting collars are designed for attachment to industry-standard 112mm
OD (4.5) pipe mounts.
ODU Data
There are two ODUs for IDU GE3 16x. These are frequency-band specific, but within
each band are capacity independent up to their design maximums.
l ODU 300hp, 6 to 38, GHz high power.
o ODU 300hp is over-air compatible with an ODU 300hp or IRU 600.
l ODU 300sp, 7 to 38 GHz, standard power.
o ODU 300sp is only over-air compatible with an ODU 300sp.
l Both ODUs support ATPC, and both include a Type-N female connector for the
ODU cable, a BNC female connector (with captive protection cap) for RSSI
access, and a grounding stud.
l ODU 300hp includes an internal lightning arrestor. ODU 300sp requires an
external lightning arrestor.
l The ODU waveguide antenna port is designed for direct antenna attachment via
an Eclipse-specific mounting collar supplied with the antennas.
260-668201-001 MARCH 2011 35

l Polarization is determined by the position of a polarization rotator fitted within

the ODU mounting collar.
l ODUs are fixed for Tx Hi or Tx Lo.
l For 1+1 hot-standby operation two ODUs are connected to a single antenna
using a direct-mount coupler. Equal or unequal loss versions are available.
Equal loss is nominally 3.5/3.5 dB. Unequal is nominally 1.5/6.5 dB.
l A remote ODU mounting kit option is available to connect to a standard
antenna.
For data on Tx power and Rx threshold by band and modulation, refer to the Eclipse
IDU 300 16x datasheet.
ODU performance characteristics are summarized below.
Table 1-4. ODU Characteristics for IDU GE3 16x Operation
Item ODU 300hp ODU 300sp

Frequency Bands 6 to 38 GHz 7 to 38 GHz (ETSI only)
Capacity 10 to 365 Mbit/s 8 to 100 Mbit/s
Modulation Options Fixed: QPSK, 16QAM, 32QAM, 64QAM, 128QAM, or 256QAM Fixed: QPSK, 16QAM, or 32QAM
Adaptive: ACM QPSK to 256 QAM
Bandwidths Supported 3.5 to 56 MHz ETSI 7 to 28 MHz
3.75 to 80 MHz ANSI
Tx Power High power Standard power
Max Tuning Range Typically (depending on T/R spacing) 56 MHz at 6 / 7 GHz to 230 MHz at 15 GHz. 340 to 380
MHz on higher bands.
Internal lightning surge Yes No
suppressor
Nominal Power 40W 6-11 GHz, 30W 13 to 38 GHz 20 - 25W
Consumption
Mechanical 287mm (11.3 in) x 287mm (11.3 in) x
HxWxD 287mm (11.3 in) x 287mm (11.3 in) x
119mm (4.7 in) 119mm (4.7 in)
6.4 kg (14 lb.) 6.4 kg (14 lb.)
ODU Accessories
Accessories's supplied with each ODU include:
l 2m earth strap with M6 stainless steel lug
l Type-N right angle adapter
l Silicone grease, 10z sachet
ODU Cables and Cable Kits

ODU cables are available in run lengths from 50 to 300+ meters. Nominal cable
impedance is 50 ohms. Two cable types are available:
CNT-300
l Maximum IDU - ODU cable run: 150m.
l Center conductor: solid copper
36 AVIAT NETWORKS
l Insulation: foam polyethylene

l Shield: aluminum tape + tinned copper braid
l Jacket: Polyethylene
l Overall diameter: 7.62 mm (0.3)
l Minimum bend radius: 22.2 mm (0.88)
l Available in lengths of 50, 75, 100, 150, 600m.
CNT-400
l Maximum IDU - ODU cable run: 300m
l Center conductor: solid BCCAI (copper-coated aluminum)
l Insulation: foam polyethylene
l Shield: aluminum tape + tinned copper braid
l Jacket: Polyethylene
l Overall diameter: 10.29 mm (0.405)
l Minimum bend radius: 25.4 mm (1)
l Available in lengths of 50, 75, 150, 300, 500m.
Cable Kits
Cable kits are available for inclusion with CNT-300 cable lengths of 50, 75, or 150m.
Kit contents are adjusted for the cable length. Contents include Type N connectors
(crimp type), grounding kits, ground conductor clamps, cable ties, weatherproofing
kit.
Cable Accessories
A range of cable accessories is available for both CNT-300 and CNT-400 cables. These
include Type N connectors (crimp type), grounding kits, ground conductor clamps,
cable ties, weatherproofing kits, crimp tool, cable stripping tool.
Lightning Arrestor
A dc-passing matrix-type universal lightning arrestor (ULA) is available for use in
ODU cables. It is intended for use at building entry, and at the ODU for ODU 300sp.
ODU 300hp includes an internal arrestor - an external ODU arrestor is not required.
At the building end it can be either bulkhead-mounted on the wall-feed-through plate,
or located just inside the building.
Two versions of arrestor are available, N-female to N-female, and N-male to N-female.
They are bi-directional - they can be installed with either connector facing the ODU.
The ULA is supplied in kit form. The kit includes the ULA plus a ground wire, crimp
lug, washer, nut, O-ring and installation sheet.
260-668201-001 MARCH 2011 37

Figure 1-11. ULA Kit
Waveguide Flange Data

The table below lists the antenna port flange types used with the ODU 300 series,
plus their mating flange options and fastening hardware for remote mount instal-
lations. UDR/PDR flanges are rectangular; UBR/PDR flanges are square.
On the ODU, the two flange styles are:
l UDR. 6-hole or 8-hole (6/8 bolt holes depending on frequency range/waveguide
type), flush-face flange with threaded, blind holes.
l UBR. 4-hole flush-face flange with threaded, blind holes.
The corresponding mating flange styles are:
l PDR. 6-hole or 8-hole flange with gasket groove and clear holes.
l PBR. 4-hole flange with a gasket groove and clear holes.
All fastening hardware is metric.
The 6 GHz coupl er has a UAR70 6 hol e (I EC) pattern fl ange on
the ODU ports and UDR on the antenna-faci ng port. F or other
bands the coupl ers use a PDR or BPR fl ange for the ODU ports,
and or UDR or UBR for the antenna-faci ng port. Thi s data i s rel -
evant where an unused ODU port on a coupl er must the
bl anked off wi th a mi crowave l oad, or where a fl exi bl e wave-
gui de attachment i s requi red i n a cascaded i nstal l ati on.
Table 1-5. Waveguide Flange Data
Freq Band Radio Waveguide Waveguide Spring Bolts Bolt Thread Hole Bolt Length Required
Flange Mating Type Washers Reqd Type Spec Depth
Flange Reqd mm
6GHz UDR70 PDR70 WR137 8 x M5 8 M5x0.8 6H 10 Flange thickness + Hole depth - 2mm
7/8GHz UDR84 PDR84 WR112 8 x M4 8 M4x0.7 6H 8 Flange thickness + Hole depth - 2mm
10/11GHz UDR100 PDR100 WR90 8 x M4 8 M4x0.7 6H 8 Flange thickness + Hole depth - 2mm
13GHz UBR120 PBR120 WR75 4 x M4 4 M4x0.7 6H 8 Flange thickness + Hole depth - 2mm
15GHz UBR140 PBR140 WR62 4 x M4 4 M4x0.7 6H 8 Flange thickness + Hole depth - 2mm
18/23/26GHz UBR220 PBR220 WR42 4 x M3 4 M3x0.5 6H 6 Flange thickness + Hole depth - 2mm
28/32/38 UBR320 PBR320 WR28 4 x M3 4 M3x0.5 6H 6 Flange thickness + Hole depth - 2mm
38 AVIAT NETWORKS
Environmental
ODU performance to specification is guaranteed over a temperature range of -33oC to
+55oC (-27oF to +131oF).
IRU 600
The Eclipse IRU 600 is a rack mounted radio unit. It co-locates with an IDU GE3 16x
to provide an extremely compact and versatile all-indoor radio.
Features and capabilities include:
l L6 to 11 GHz ANSI licensed frequency bands
l 5.8 GHz unlicensed frequency (ISM) band; USA, Canada only
l Common RFU for 5.8 GHz unlicensed and L6 licensed for easy transition and
sparing
l 3.75 to 40 MHz channel bandwidths with adaptive and fixed modulation
options
l High system gain with support for both paired and unpaired frequencies with
filter based ACU
l 3RU 1+1 / 2+0 optimized chassis; it accommodates one or two 2 RFUs + 1 ACU
l Expandable to N+N using co-located radios for scalability to ultra high
capacities
l Over-air compatible with ODU 300hp (supporting RAC must be RAC 60/6X)
l Two different bands may be used in the same chassis (such as 6 & 11 GHz in a
1+0 repeater)
l Lowest power consumption (for an all-indoor radio)
l High and standard power RFUs (high power on all bands; standard power is an
option for L/U 6 GHz)
l Wide-mouth +/- 21 to 60 Vdc power supply
l Multiple ACU options
l Expansion port in filter-based ACU accommodates parallel paths
l Expansion kits allow linking of multiple chassis
Figure 1-12. IRU 600, High Power
260-668201-001 MARCH 2011 39

Frequency Bands
IRU 600 provides comprehensive options on ANSI licensed bands L6 to 11 GHz, and
on the USA and Canada unlicensed 5.8 GHz (ISM) band.
5.8 GHz Unlicensed Band

The IRU 600 for North America and Canada 5.8 GHz unlicensed band is designed to
support easy and fast deployment. No license is required meaning that with a suitable
antenna, installation can be 'immediate'. Coupled with this is the common 5.8 GHz
and L6 RFU design; an installation at 5.8 GHz can be subsequently converted to L6
licensed operation by simply replacing the ACU.
5.8 GHz operati on supports fast turn-up for new l i nk requi re-
ments. On recei pt of a l i cense, operati on can be converted to
L6 l i censed band by repl aci ng the ACU.
Eclipse IDUs and INUs with IRU 600 are compliant with FCC CFR47, Part 15.247,
and Industry Canada RSS-210 Annex 8, on ISM frequency band 5725 to 5850 MHz.
International use is not supported; the system does not employ DFS and as such can-
not be deployed in countries where DFS is a regulatory requirement for protection of
radars.
Features and Capabilities:

l ACU filters are tuned 30 MHz wide.
o Filters can be spot tuned (pre-tuned) on any center frequency within the
band (within the filter/band boundaries).
o With 30 MHz filters just two Tx/Rx pairs can cover the complete band.
l Bandwidths 3.75, 10, 20, or 30 MHz.
o 65 MHz T/R spacing.
l Tx and Rx can be paired on different sub-bands (Tx on one 30 MHz sub-band,
RX on the other).
l Adaptive or fixed modulation options.
l Supports Ethernet and/or NxDS1 payloads, with air-link capacities to 189
Mbit/s (30 MHz Ch BW). See Link Capacity and Bandwidth on page 55.
l Common 5.8 GHz and L6 RFU supports easy migration from one band to the
other (from unlicensed to licensed and vice-versa).
o RFUs can be retained during migration, but the ACU must be replaced (not
retuned).
l Extensive protection and diversity options.
l Output power is limited to 29 dBm at the antenna port to ensure compliance
with the FCC 1 Watt rule.
l For Tx power and system gain figures, see the Eclipse Packet Node ANSI
Datasheet.
40 AVIAT NETWORKS
Operational Limitations and Restrictions

Unlicensed band operation means sharing the air-space with other operators of unli-
censed band links. Interference is possible.
l IRU 600 5.8 GHz operation is 'narrow-band'; it competes/shares spectrum with
other narrow-band links and with spread-spectrum links.
l Performance could deteriorate over time with the introduction of other links in
the same geographical area.
l Antennas must be approved (FCC or Industry Canada) for 5.8 GHz unlicensed
band.
L6 to 11 GHz ANSI Licensed Bands

The IRU 600 for North America and Canada complies with relevant FCC and Federal
(USA), and SRSP (Canada) requirements for frequency bands 6 to 11 GHz.
Features and Capabilities:

l Adaptive or fixed modulation options.
l Supports Ethernet and/or NxDS1 payloads, with airlink capacities to 255 Mbit/s
(40 MHz Ch BW). See Link Capacity and Bandwidth on page 55.
l ACU filter bandwidths:
o L6/U6 bands: 30 MHz
o 7/8/11 GHz bands: 40 MHz
o 10 GHz band: 15 MHz
o Filters are spot tuned on a center frequency within the band (within the
filter/band boundaries).
l Extensive protection and diversity options.
For Tx power and system gain figures, see the Eclipse Packet Node ANSI Datasheet.
IRU 600 Link Configurations

Link configurations supported in conjunction with IDU GE3 16x include:
Non-Protected (1+0)
A 1+0 terminal has a single RFU and RAC. In this configuration any traffic-affecting
fault in either of these units or in the radio path will result in a loss of traffic over the
link. A 1+0 configuration is normally chosen when traffic is non-critical or when path
redundancy is available (due to route diversity for example).
Non-Protected (1+0) HSB ready

A non-protected terminal is equipped for a later conversion to HSB. The ACU installed
is the HSB version so no changes to the ACU are required for the conversion. Plugging
in the additional RFU, installing coax cables between the ACU and the additional
RFU, and connecting an IF cable between this RFU to a second RAC card in the INU
facilitates an easy, quick field upgrade.
260-668201-001 MARCH 2011 41

1+0 Repeater
Two non-protected RF paths each over its own antenna. This is a common con-
figuration used in ring network topologies. This configuration can also be used for 2+0
CCDP operation.
HSB (1+1)
A HSB terminal provides two redundant transmission paths. Only one is active at any
one time. A HSB terminal consists of two RFUs and two RACs. Both RFUs transmit
on the same frequency, with the online transmitter active while the standby unit is
operational but with the transmitter output muted. Traffic is restored within mil-
liseconds if the online unit fails.
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. This selection
process is hitless/errorless.
Couplers/splitters are used within the RF filter assembly to connect the transmitters
and receivers to the common antenna waveguide feed.
HSB/SD
Space Diversity is used to reduce the adverse effects of multi-path fading. Two anten-
nas, spatially separated (vertically) are used. The better quality Rx signal is selected
errorlessly between the RACs.
HSB/SD uses a Tx coupler and therefore has an additional loss ratio of 1 & 7 dB in the
transmit direction. The receive direction does not suffer any additional loss compared
42 AVIAT NETWORKS
to 1+0 receive.
SD (Split Tx)
A Space Diversity Split Transmitter is an enhancement of HSB/SD where no Tx cou-
pler is required and losses are minimized. Each antenna is connected to its trans-
mitter and receiver.
Radio Frequency Unit (RFU)

RFU(s) connect to the IDU using short IF cables.
RFU features include:
l Individual Tx and Rx ports (Female SMA Connectors) for ACU connection.
l Settable Hi & Lo in every band.
l Integral cooling fans. Two fans provide forced-air cooling.
o Fan operation is monitored.
o Normally only one FAN is operational, and operation is cycled.
o Both FANs operate if preset temperature limits are exceeded.
o Fan replacement is non traffic affecting.
l Very low power consumption
o 1+0 standard power: 52 W
260-668201-001 MARCH 2011 43

o 1+0 high power: 90 W

o 1+1 standard power: 82 W
o 1+1 high power: 124 W
Antenna Coupling Unit (ACU)

The ACU filters and routes RF signals between the IRU 600 antenna port(s) and the
RFU module(s). It comprises:
l Isolators and circulators
l Tx and Rx filters
l Coupler - for HSB configurations only
l Associated mechanical hardware
An expansion port allows system expansion through the addition of co-located IRU
600 radios, or external radio equipment.
l When multiple carriers are deployed on a common branching network (same
antenna), the intermodulation frequency products that result from combining
two or more transmitter frequencies on a common antenna feeder must be 48
MHz or more above or below each of the receiver frequencies present on the
same antenna feeder.
Female SMA connectors are used on the interface to RFU Tx and Rx ports. Antenna
ports and expansion ports utilize standard waveguide flanges.
Where coupl ers are requi red (1+1 protecti on) unequal -l oss cou-
pl ers are standard. I f equal -l oss i s requi red, i t must be spec-
i fi ed at ti me of order.
ACU Losses
The following tables list ACU losses for a filter-based ACU with embedded Tx/Rx cou-
plers.
Al l l osses are rel ati ve to a 1+0 confi gurati on.
44 AVIAT NETWORKS
Table 1-6. Additional Tx ACU Loss (Relative to a 1+0 Configuration)
Configuration 6L/6H GHz 7/8 GHz 10 GHz 11 GHz

Non protected (1+0 loss reference) 0.0 0.0 0.0 0.0
HSB or "HSB Ready" 1.0 1.0 1.2 1.2
Unequal Tx / Unequal Rx, "A" Path
HSB or "HSB Ready" 7.1 7.1 7.3 7.3
Unequal Tx / Unequal Rx, "B" Path
HSB or "HSB Ready" 3.0 3.0 3.2 3.2
Equal Tx / Equal Rx, A Path
HSB or "HSB Ready" 3.0 3.0 3.2 3.2
Equal Tx / Equal Rx, B Path
HSB/SD, Unequal Tx, "A" Path 1.0 1.0 1.2 1.2
HSB/SD, Unequal Tx, "B" Path 7.1 7.1 7.3 7.3
HSB/SD, Equal Tx, "A" Path 3.0 3.0 3.2 3.2
HSB/SD, Equal Tx, "B" Path 3.0 3.0 3.2 3.2
2+0 1 Ant or FD 1 Ant, "A" Path 0.0 0.0 0.0 0.0
2+0 1 Ant or FD 1 Ant, "B" Path 0.3 Typ 0.3 Typ 0.4 Typ 0.4 Typ
0.5 Max 0.5 Max 0.7 Max 0.7 Max
2+0 1 Ant or FD 1 Ant, Expansion, 0.6 Typ 0.6 0.7 0.7
"Aexp" Path 1.0 Max Typ/1.0 Typ/1.2 Typ/1.2
Max Max Max
2+0 1 Ant or FD 1 Ant, Expansion, 0.9 Typ 0.9 Typ 1.0 Typ 1.0 Typ
"Bexp" Path 1.3 Max 1.3 Max 1.5 Max 1.5 Max
1+0 Repeater, SD Split Tx 2 Ant, 0.0 0.0 0.0 0.0
FD/SD (Hybrid) 2 Ant
Table 1-7. Additional Rx ACU Loss (Relative to a 1+0 Configuration)
Configuration 6L/6H GHz 7/8 GHz 10 GHz 11 GHz

Non protected (1+0 loss reference) 0.0 0.0 0.0 0.0
HSB or "HSB Ready" 1.0 1.0 1.2 1.2
Unequal Tx / Unequal Rx, "A" Path
HSB or "HSB Ready" 7.1 7.1 7.3 7.3
Unequal Tx / Unequal Rx, "B" Path
HSB or "HSB Ready" 3.0 3.0 3.2 3.2
Equal Tx / Equal Rx, A Path
HSB or "HSB Ready" 3.0 3.0 3.2 3.2
Equal Tx / Equal Rx, B Path
HSB/SD, Unequal Tx, "A" Path 0.0 0.0 0.0 0.0
HSB/SD, Unequal Tx, "B" Path 0.0 0.0 0.0 0.0
HSB/SD, Equal Tx, "A" Path 0.0 0.0 0.0 0.0
HSB/SD, Equal Tx, "B" Path 0.0 0.0 0.0 0.0
2+0 1 Ant or FD 1 Ant, "A" Path 0.0 0.0 0.0 0.0
2+0 1 Ant or FD 1 Ant, "B" Path 0.3 Typ 0.3 Typ 0.4 Typ 0.4 Typ
0.5 Max 0.5 Max 0.7 Max 0.8 Max
"Aexp" Path 1.0 Max 1.0 Max 1.2 Max 1.2 Max
"Bexp" Path 1.3 Max 1.3 Max 1.5 Max 1.6 Max
1+0 Repeater, SD Split Tx 2 Ant, 0.0 0.0 0.0 0.0
FD/SD (Hybrid) 2 Ant
More Information:
For data on capacity, bandwidth and modulation options refer to Link Capacity and
Bandwidth on page 55.
260-668201-001 MARCH 2011 45

For data on Tx power and Rx threshold by band and modulation, refer to the IDU
GE3 16x datasheets.
ACU Waveguide Flange Data

Table 1-8. ACU Flange Data
Freq, Flange Holes Screw Waveguide

GHz Type Length
6 l CPR 137 G l 8 x #10-32 tapped holes 1/2" l WR 137
10, 11 l CPR 90 G l 8 x #8-32 tapped holes 7/16" l WR 90
The screw length assumes a flex twist mating flange thickness of 1/4.
Flange screw kits comprising screws, lock washers and gasket are available from Aviat
Networks.
IRU 600 Power Supply

Power for the standard power RFU is derived from the IDU via the IDU-RFU cable.
The IDU requires a -48 Vdc input.
Power for the high power RFU is derived from the IDU and from a D-sub 2W2 front
panel connector. The front panel input is wide-mouth: +/- 21-60 Vdc.
l Note that while the IRU 600 will operate from -48Vdc (+ve ground) or +24 Vdc
(-ve ground) supplies, the associated IDU GE3 16x is -48 Vdc only (-40.5 to -
60 Vdc).
l Operation from +24 Vdc will require a separate +24 Vdc to -48 DC-DC
converter for the IDU.
For more information, see Power Supply on page 50.
RFU Tx Power Calibration

A Tx power calibration function is available for use in instances where an RFU is
replaced or where RFUs and the ACUs are ordered as separate entities for integration
in the field, and there is a wish to check, and if necessary reset Tx output power to
adjust for any slight change in output power when used at a frequency other than its
original spot-tuned frequency.
l RFU Tx power output is not absolutely flat across its frequency band.
l During factory alignment the calibration of the Tx output power control
function is performed at a specified frequency; the IRU 600 is supplied spot
tuned and labeled with a specific Tx insertion loss.
l The procedure re-calibrates RFU Tx power setting so that the set power best
matches Tx power as measured by precision factory test equipment.
46 AVIAT NETWORKS
Environmental
Performance to specification is guaranteed over a temperature range of -5oC to +55oC
(+23oF to +131oF).
ATPC
Automatic Transmit Power Control (ATPC) is an optional setting - except when con-
figured for adaptive modulation. ATPC is automatically enabled for adaptive
modulation.
ATPC allows radio links to maintain set thresholds for fade margin, and to maintain
overall link performance at an otherwise lower than maximum transmit power. If path
conditions deteriorate due to fading, ATPC gradually increases the transmitted power
to maintain the remote fade margin. When the condition causing the fade ends, the
TX power level is reduced back to the minimum level.
Refer to:
l ATPC Operation on page 47
l Interference and ATPC on page 48
l FCC Implementation on page 1
ATPC Operation
ATPC in Eclipse is based on two monitored values, Receive Signal Strength (RSL) and
Signal to Noise Ratio (SNR).
Each Eclipse terminal transmits information about its RSL and SNR levels to its part-
ner terminal. The terminals analyze this information, and each adjusts its Tx power to
maintain the target fade margin settings.
ATPC calculates the remote terminals fade margin based on current RSL and receiv-
er/modulation specifications. If a path fade reduces the fade margin on the remote ter-
minal, the local transmitter increases its power level to return the remote fade margin
to the target settings. When the fading condition passes and the fade margin
increases, the local transmitter reduces its power level to keep the remote fade margin
at the desired level.
l The ATPC algorithm does not adjust Tx power when a link is running normally,
and the RSL and SNR values are within normal limits.
260-668201-001 MARCH 2011 47

l If the local terminal determines that RSL at the remote terminal is too low, then
it increases its power level in 0.1 db increments until the RSL is within the
specified range.
l "If the RSL value is within range, but the SNR is low, then the transmit power is
increased until the SNR is within the specified range.
l ATPC power changes can occur at a rate of 6 dB/second to provide
compensation for rapid fading conditions.
l ATPC will fail to maintain the remote target threshold settings if the fading
condition is severe enough to require more local transmit power than set as the
maximum TX power, or if the power level required is beyond the capability of
the transmitter.
Interference and ATPC

It is possible for a radio to have a good receive signal (high RSL), but poor residual
BER performance (poor SNR), such as can occur when there is co/adjacent inter-
ference. SNR is therefore also used as a factor in ATPC operation, preventing bit errors
occurring due to link fade beyond the point where Forward Error Correction (FEC) is
able to recover errored blocks.
The ATPC process calculates the SNR based on the signal level derived from the
demodulator and uses this information to maintain the SNR by adjusting the Tx
power at the local terminal.
The transmit power at the local terminal is increased when the SNR at the remote ter-
minal falls to the SNR calculated for an RSL 6dB above the 10-6 threshold. The dB
value will vary slightly, depending on the ODU/modulation combination.
RSL and SNR Interoperation

The ATPC algorithm uses both RSL and SNR inputs to set remote Tx power.
l An above-range RSL will initiate a reduction in remote Tx power.
l When both RSL and SNR are within range, no ATPC action is taken.
l When the RSL is within range but the SNR is below range, SNR will initiate an
increase in remote Tx power.
l With low levels of interference ATPC can, depending on the settings and the
degree of interference, optimize the remote Tx power. But with high levels of
interference ATPC action will not be effective.
Interference can be checked by muting the Tx at the far end and viewing RSSI/RSL at
the local end. Where there is a measurable RSL under this condition, ATPC should not
be used.
Note that the ODU RSSI (RSL) filter has a nominal 56 MHz bandwidth, which means
that depending on the channel bandwidth used, multiple adjacent channels can be
included within the filter passband1. Normally this will not cause a problem as
1RSSI filter bandwidth is not a function of, nor does it affect receiver adjacent channel
C/I performance. IDU GE3 16x complies with relevant ETSI and FCC co and adjacent
channel requirements.
48 AVIAT NETWORKS
antenna discrimination (beamwidth) and good frequency planning will exclude co and
adjacent channel RSL interferers.
ATPC shoul d not be used where there i s a measurabl e RSL
when the remote-end Tx i s muted.
FCC Implementation
FCC guidelines support use of ATPC to establish a coordinated Tx power, a power
lower than a maximum Tx power, for the purposes of calculating interference into vic-
tim receivers. These guidelines are provided within TIA TSB 10-F, Interference Criteria
for Microwave Systems.
From TIA TSB 10-F, the Tx powers associated with an ATPC system included on the
coordination notice may be summarized as:
l Maximum Transmit Power. The Tx power that will not be exceeded at any
time.
l Coordinated Transmit Power. The Tx power selected by the ATPC system
licensee as the power to be used in calculating interference levels into victim
receivers. The Coordinated Transmit Power is restricted to a 0 to 10 dB range
below the Maximum Transmit Power.
l Nominal (Normal) Transmit Power. The Tx power at or below the
Coordinated Transmit Power at which the system will operate in normal,
unfaded conditions. The Normal Transmit Power must be less than or equal to
the Coordinated Transmit Power, with typical values ranging from 6 to 15 dB
below the Maximum Transmit Power.
But to claim a coordinated Tx power less than the maximum Tx power, certain restric-
tions on the time that this power is exceeded during the course of one year must be
met, and a timer function applies to ensure that maximum power is not sustained for
more than five continuous minutes. As IDU GE3 16x does not currently support such
a timer, links must be coordinated at maximum Tx power.
260-668201-001 MARCH 2011 49

Power Supply
IDU GE3 16x is designed to operate from a -48Vdc (+ve ground) power supply.
l ODUs are powered from the IDU via the ODU cable.
l IRU 600 is powered from the IDU for standard power RFUs, and additionally
via a front-panel power connector on high power RFUs.
Note that while the high power RFUs incorporate a wide-mouth DC converter for oper-
ation from +/- 21 to 60 Vdc, when operated with the IDU GE3 16x, -48 Vdc must be
used as the supply voltage unless a stand-alone dc-dc converter is installed for the
IDU, such as a +24 to -48 Vdc converter for +24 Vdc operation.
The IDU and IRU 600 are polarity protected. An incorrect supply connection will not
cause damage to the units or cause a fuse to blow.
The dc power supplies must be UL or IEC compliant for SELV (Safety Extra Low Volt-
age) output (60Vdc maximum limited).
The IDU is supplied with a 2-pin Phoenix style power connector with screw fasteners.
The front panel fuse unit doubles as a power on/off switch. The fuse is 5A time-lag.
The associated rack circuit breaker or fuse should have maximum capacity of 8 A.
High-power RFUs for the IRU 600 are each supplied with a power input cable with a
2-pin D-series 2W2C power connector, with screw fasteners at one end, and free wire
at the other. The cable is nominally 5 m (16 ft), and the wires are 4 mm2 (AWG 12).
The associated rack circuit breaker or fuse should have maximum capacity of 8 A.
Power Consumption
Nominal power consumption figures for the IDU, ODUs and IRU 600 are as follows.
Figures are for a -48 Vdc supply voltage.
IDU GE3 16x: Less than 30W.
50 AVIAT NETWORKS
ODUs:
Table 1-9. ODU 300hp
BAND Nominal Average Max Power Min Power

Power Con- Power Con- Consumption Consumption
sumption sumption
6 GHz 40W 40.7W 45.7W 35.7W
7 GHz 40W 42.8W 48.6W 37.1W
8 GHz 40W 43.1W 48.5W 37.6W
10 GHz 40W 41.5W 44.01W 39.0W
11 GHz 40W 34.6W 38.0W 31.3W
13 GHz 30W 30.9W 37.1W 24.7W
15 GHz 30W 29.8W 35.9W 23.6W
18 GHz 30W 22.2W 25.6W 18.8W
23 GHz 30W 24.3W 27.0W 21.6W
28 GHz 30W 25.0W 28.1W 21.9W
32 GHz 30W 25.1W 27.5W 22.6W
38 GHz 30W 29.2W 31.6W 26.7W
Table 1-10. ODU 300sp
BAND Typical Power Max Power

Consumption Consumption
7 GHz 27W 35W
8 GHz 27W 35W
11 GHz 25W 35W
13 GHz 22W 27W
15 GHz 21W 27W
18 GHz 20W 25W
23 GHz 20W 25W
32 GHz 20W 25W
38 GHz 20W 25W
The following figure illustrates ODU cable power dissipation. Data is for CNT 400 and
RG-8 type cables. For CNT 300, increase dissipation figures by 40%.
260-668201-001 MARCH 2011 51

Figure 1-13. Nominal ODU cable Power Dissipation at -48v
IRU 600:
l For a standard power RFU, power is provided via its RAC - RFU cable (in the
same way as an ODU).
l For a high power RFU, power is supplied via its RAC cable and additionally by
a front-mounted DC connector.
Table 1-11. Nominal IRU 600 Power Consumption
Configuration Power Sourced Power Sourced Total DC

from INU from External DC Power
Connector
1+0 Standard Power (1xRFU) 52W N/A 52W
1+0 High Power (1xRFU) 52W 38W 90W
1+1 Standard Power (2xRFU) 82W N/A 82W
1+1 High Power (2xRFU) 82W 42W 124W
52 AVIAT NETWORKS
Licensing
Capacity and feature licenses apply.
Capacity Licensing
Capacity licensing steps are as follows. Capacity refers to total radio payload.
EZE-10020: 20 Mbit/s
EZE-10050: 50 Mbit/s
EZE-10100: 100 Mbit/s
EZE-10150: 150 Mbit/s
EZE-10200: 200 Mbit/s
EZE-10400: 400 Mbit/s
Upgrades from a lower to higher capacity are available.
Feature Licensing
Four features are available with SW release 5.9. More will be added at later releases.
l When a feature is required on a new IDU it is ordered together with the capacity
license for the IDU.
l Feature licenses can be separately ordered as upgrades on existing IDUs.
EZF-10000: Enable TDM Ports

Enables access to the DAC 16xV2 module for E1/DS1 trib use.
EZF-10020: Adaptive Modulation

Adaptive coding and modulation (ACM) is enabled on the RAC 60 module.
l Modulation settings provides access to QPSK, 16 QAM, 64 QAM, or 256 QAM.
l Code settings provide two sets of modulation states for each modulation; one
for maximum-throughput, one for maximum-gain, to provide a total of eight
modulation states.
l From two to four of the eight modulation states offered with ACM can be
selected for use.
EZF-10090: Synchronous Ethernet

Enables Synchronous Ethernet operation.
260-668201-001 MARCH 2011 53

EZF-10100: Advanced QoS

Enables access to advanced Qos features of:
l MPLS Exp prioritization (in addition to standard options of DSCP, 802.1Q,
port-based)
l 8 QoS queues per port (standard is 4 Qos queues)
l Hybrid scheduler (standard is Strict or DWRR)
54 AVIAT NETWORKS
Link Capacity and Bandwidth

Radio link (airlink) capacity and bandwidth options are shown for fixed and
adaptive modulation operation. Airlink capacity is a measure of the raw payload
capacity before application of bit-saving techniques available on Ethernet data using
IFG and Preamble suppression, which suppresses non-essential data at the sending
end of the link, and then re-instates it at the receiving end to provide significant
throughput improvements on small frame sizes.
Refer to:
l Fixed Modulation on page 55
l Adaptive Coding and Modulation (ACM) on page 56
Capaci ty, channel bandwi dth and modul ati on data provi ded i n
thi s secti on i s subj ect to change wi thout pri or noti ce. F or the
most up-to-date data refer to the I DU GE3 16x datasheets.
Fixed Modulation
Fixed modulation is used where ACM is not required.
Any of the available ACM modulation rates can be selected for fixed modulation oper-
ation. These are supplemented by additional fixed-only rates.
For ACM rates that can be selected for fixed modulation operation see Adaptive Cod-
ing and Modulation (ACM) on page 56
The table below lists the fixed-only ETSI modulation rates. ANSI rates will be advised
in a later release.
l Ethernet throughput and latency data is for one IDU GE3 - IDU GE3 link via
the internal DPP DAC GE3 to RAC 60 interconnect. Data is typical only, and
applies when the full payload capacity of the link is dedicated to Ethernet.
l IFG + Preamble suppression is operating on the Ethernet link. This significantly
improves throughput on small frame sizes.
l The results are for back-to-back connected radios; they exclude latency
associated with transmission path length of nominally 3.3 uS per km, or 5.4 uS
per mile.
Table 1-12. Fixed-only ETSI Rates
Airlink Channel Modulation Ethernet L1 Max Ethernet L2 Max Ethernet Latency uS
TDM
Capacity (MHz) Throughput Mbit/s Throughput Mbit/s
1518 byte 64 byte 1518 byte 64 byte 1518 byte 64 byte Latency uS
105 Mbit/s 27.5 32 QAM 102 132 101 101 260 114 342
154 Mbit/s 27.5 128 QAM 150 195 148 148 219 108 342
260-668201-001 MARCH 2011 55

Adaptive Coding and Modulation (ACM)

Adaptive modulation maximizes use of available channel bandwidth through auto-
matic adjustment of modulation and/or coding so that the most data efficient (high-
est possible) modulation is used over the prevailing path conditions.
Adaptive modulation refers to the dynamic adjustment of modulation rate to
ensure maximum data bandwidth is provided most of the time, with a guaranteed
bandwidth provided all of the time.
Coding refers to an ability to set individual modulation rates for maximum through-
put, or maximum system gain.
IDU GE3 16x supports four modulation rates, QPSK, 16 QAM, 64 QAM, or 256 QAM,
plus a coding option on each, for a total 0f eight modulation states, any four of which
can be selected for ACM operation.
Capacity and ACM feature licensing applies. See Licensing on page 53.
Refer to:
l Adaptive Modulation (AM) on page 56
l Coding on page 58
l Modulation Change Criteria on page 60
l Reference Modulation on page 62
l Capacity, Modulation, Ethernet Throughput and Latency on page 63
Adaptive Modulation (AM)

Wireless links are traditionally engineered to carry traffic with a 99.999% availability
under all path conditions. This requires a high fade margin, but this margin is only
needed to protect against worst-case fades that may occur for just a few minutes in a
year. For the rest of the year the margin is not used.
By using less robust but more efficient modulation schemes, the available fade margin
can be transformed into delivering more data throughput. This is the purpose of adap-
tive modulation; it dynamically changes the modulation so that the highest avail-
ability of capacity is provided at any given time.
When used in conjunction with traffic prioritization, it can be configured to ensure all
high priority traffic continues to get through when path conditions deteriorate; only
low priority 'best effort' data is discarded.
Modulation switching is hitless (errorless) for Ethernet traffic and/or E1/DS1 circuits
that are not affected by a reduction in modulation. For example, if sized (prioritized)
correctly, all high priority traffic will be unaffected by a transition from 256 QAM
down to QPSK, and then back to 256 QAM.
Ethernet connections enjoy real synergy through the QoS awareness on the GigE
switch, and the service provisioning provided by the network overlay.
56 AVIAT NETWORKS
l All high priority traffic, such as voice and video, continues to get through when
path conditions are poor.
l Outside these conditions 'best effort' lower priority traffic, such as email and file
transfers enjoy data bandwidths that can be up to four times the guaranteed
bandwidth.
While adaptive modulation can also be used on PDH links and combined PDH and
Ethernet links, unlike Ethernet there is no QoS synergy on PDH connections. E1/DS1
connections are dropped in user-specified order when link capacity is reduced, and
restored when capacity is increased.
While QPSK is the default base-rate for adaptive modulation, the base rate can be set
to any of the rates below the maximum rate.
The figure below illustrates the purpose and function of AM.
l Under favorable path conditions, the highest modulation rate of 256 QAM is
used, to deliver a fourfold increase in capacity compared to the base rate QPSK
modulation. This highest capacity state is typically available for better than
99.5% of the time.
l When conditions deteriorate, the more robust 64 QAM, then 16 QAM, and
ultimately QSPK modulations are switched into service to maintain
connectivity. QPSK, as the most robust modulation, is used to support critical
traffic with a 99.999% availability.
l Receiver SNR primarily determines a modulation change, up or down. See
Modulation Change Criteria on page 60.
l Options are provided to map high priority traffic to the base QPSK modulation,
followed by lesser priority traffic for 16 QAM, followed by 64 QAM and 256
QAM for lowest priority traffic.
260-668201-001 MARCH 2011 57

Figure 1-14. Adaptive Modulation At Work
Comprehensive adaptive modulation diagnostic options are provided within Portal.

These include information on unavailable capacity due to modulation change, number
of seconds in operation for each modulation type, unavailable seconds due to mod-
ulation switch-overs, successful switch-overs between modulation types, and average
throughput achieved.
Coding
The modulation code settings provide two sets of modulation states, one for max-
imum throughput, the other for maximum system gain. These apply on each of
the modulation rates (QPSK, 16 QAM, 64 QAM, 256 QAM) to provide a
total of eight modulation states, any two, three or four of which can be
selected for ACM operation.
Maximum throughput delivers maximum data throughput - at the expense of some
system gain.
Maximum gain delivers best system gain - at the expense of some throughput.
From two to four of the eight modulation states offered with ACM can be selected for
use. For example:
l With four modulation rates, each can be set for maximum throughput or
maximum gain.
l With three modulation rates, such as 16 QAM, 64 QAM, 256 QAM, one rate
(any) can be set for maximum gain and additionally for maximum throughput,
to provide four step AM operation. Or just three (any) of the four possible steps
can be selected.
l With two modulation rates, such as 64 QAM (or 16 QAM) with 256 QAM, each
can be set for maximum gain and additionally for maximum throughput, to
58 AVIAT NETWORKS
provide four step AM operation. Or just two, or three out of the four possible
steps can be selected.
This feature provides a practical trade-off between capacity and system gain to fine-
tune link performance. It also provides best balance on AM operation.
l The four modulation rates (QPSK, 16 QAM, 64 QAM, 256 QAM) support near-
linear 2x, 3x, 4x capacity steps.
l The coding options allow capacity/gain variations on these rates to always
support up to four steps, even when just two of the possible four modulation
rates are in use, or are permitted.
l It effectively eliminates the need for additional intermediate modulation rates,
such as 32 QAM or 128 QAM.
l Even where just one modulation rate is required/permitted, the coding option
supports two-step AM operation, one for maximum throughput, one for
maximum gain.
The figure below illustrates the eight modulation steps on a 56 MHz channel. They
provide smooth capacity and throughput progression from lowest to highest, from
base QPSK maximum system gain, to 256 QAM maximum throughput 1. Ethernet
throughput is shown for 64 byte frames at Layer 1 (L1).
Figure 1-15. Adaptive Modulation Granularity
When set for maximum gain:

l System gains are typically improved by between 1.5 dB to 4 dB compared to
maximum throughput.
l Link capacities are typically reduced by between 6% to 18% compared to
maximum throughput.
l For more information, refer to the Eclipse Packet Node datasheet.
1HG = maximum system gain; HT = maximum throughput.
260-668201-001 MARCH 2011 59

Whi l e both ends of an adapti ve modul ati on l i nk must be set to

have i denti cal modul ati on state opti ons (modul ati on rate and
codi ng steps), i n operati on the Tx and Rx states are not syn-
chroni zed - i t i s possi bl e for an I DU GE3 16x to be transmi tti ng
usi ng one state, and to be recei vi ng from i ts remote partner
that i s transmi tti ng on a di fferent state.
Modulation Change Criteria

Modulation changes are primarily determined by receiver SNR thresholds. Each con-
figured modulation has an improve SNR threshold and a degrade SNR threshold.
l SNR is the sole criteria for step-downs (degrade).
l SNR with ATPC settings are used for step-ups (improve).
When the receiver SNR reaches the improve threshold, and the target remote fade mar-
gin is maintained, a modulation switch request is sent to the remote transmitter
which results in the transmitted modulation from the remote end changing to the
next higher throughput modulation. Similarly, if the receiver SNR goes below the
degrade threshold, a modulation switch request is sent, resulting in the transmitted
modulation from the remote end changing to the next lower throughput modulation.
l APTC is optimized to improve received SNR at the far end to push for a
modulation increase (up to the maximum configured modulation).
l The improve and degrade thresholds incorporate a level of hysteresis (typically
2 dB) to prevent modulation oscillations occurring.
Because of spectrum mask reasons, modulations cannot be switched to a higher mod-
ulation unless the transmit power is below the maximum allowed for the requested
modulation. See Reference Modulation on page 62.
The table below lists the SNR improve and degrade change points for one of the ETSI
ACM channels.
l Degrade = down fade, the SNR threshold at which the modulation will step
down.
l Improve = up fade, the SNR threshold at which the modulation will step up.
l Step up/down are also dependent on the modulation selection (which
operational modulations are selected - maximum 4). If, for example, the
selections are 64 QAM HG and 256 QAM HT, the step down from 256 QAM will
occur with an SNR of 30 dB, and the step up from 64 QAM HG will occur at an
SNR of 33 dB.
60 AVIAT NETWORKS
Table 1-13. Example SNR Change Points

Modulation SNR dB
Degrade Improve
QPSK HG NA 14
QPSK HT 12 19
16 QAM HG 17 20
16 QAM HT 18 25
64 QAM HG 23 27
64 QAM HT 25 30
256 QAM HG 28 32
256 QAM HT 30 NA
The figure below illustrates ACM change-points and associated RSLs for one frequency
band. The figure also includes the SNRs for the 10-6 receive thresholds and their asso-
ciated RSLs.
l Each ACM channel (7 MHz, 14 MHz, 28 MHz, 40 MHz etc.) operates with a
defined set of SNR change points, which apply across all frequency bands.
l But the relationship between these SNR change points and receive signal level
(RSL) is different for each frequency band.
l Note the 2 db difference (hysteresis) between the improve and degrade
thresholds.
l Improve thresholds typically range between 6 dB to 10 dB above the 10-6 receive
threshold; degrade thresholds 3 dB to 4 dB.
260-668201-001 MARCH 2011 61

Figure 1-16. Example ACM Change Points and RSLs
Reference Modulation
A reference modulation setting in Portal applies to ACM operation, and works in con-
junction with the user-entered Max Tx Power setting. It particularly applies to ETSI
markets where the transmitted signal must be maintained within a specified transmit
mask over the various ACM modulation states.
The reference modul ati on i s the modul ati on rate that deter -
mi nes the maxi mum al l owabl e Tx power wi thi n an AM scheme.
ETSI Rates:
l Modulation-based transmit or spectral emission masks define spurious
emissions limits.
l Masks are more stringent at the higher modulation rates. This typically means
a transmit power back-off is required at the higher rates to provide compliance.
l The transmit mask that determines Tx output power maximums depends on
the reference modulation. This will be advised in the operating license issued by
the regulatory authority for the country/region.
l If a least stringent QPSK mask (QPSK reference modulation) is applicable on all
higher ACM rates, it permits use of higher transmit power maximums on these
rates, compared to a license for a fixed higher modulation rate. This improves
system gain.
l If on the other hand, the highest modulation rate is used to establish the
applicable Tx mask, Tx power maximums must be automatically backed off on
the lower modulation rates.
l One of the QPSK, 16 QAM, 64 QAM, or 256 QAM rates must be selected as the
reference modulation.
l In practice links should not be set at maximum Tx power, unless operated over
longer hop distances. A link license will specify a not-to-exceed power / EIRP on
a link.
l The max limit of the user-entered Max Tx Power setting will change based on
the Reference Modulation selected.
l Where the user-entered Max Tx Power setting is set below the maximum
allowable Tx power on the highest modulation rate, Tx power back-off will not
occur.
ANSI Rates:
Modulation-based transmit or spectral emissions masks do not apply. Instead the
operational limits are determined by channel bandwidth emission limits.
l For ANSI modulation rates the reference modulation settings currently have no
effect on Tx power maximums - Tx power backoff is not applicable. Any
modulation can be set as the reference modulation.
l Transmit output power maximums are effectively set for each modulation step
and are aligned with the maximums for non-ACM (fixed) operational modes.
62 AVIAT NETWORKS
Capacity, Modulation, Ethernet Throughput and Latency

The following tables list typical data for ETSI ACM operation. ANSI data will be pro-
vided in a later release.
These same modulation steps are used on Eclipse Packet Node (with RAC 60).
Modul ati ons and capaci ti es are subj ect to change. Check the
I DU GE3 16x datasheet or check wi th Avi at Networks or your
suppl i er for confi rmati on.
Ethernet throughput and latency figures are typical only.
l Performance is for Ethernet port to Ethernet port via IDU GE3 radios back-to-
back connected on a bench test unit.
l Latency figures exclude the free space latency associated with transmission path
length; nominally 3.3 us per km (5.4 us per mile).
l Longer latencies are associated with lower modulation and capacity options,
and higher Ethernet frame sizes.
l IFG + Preamble suppression is operating on the Ethernet link.
The tables also include typical TDM latency trib-to-trib. They do not include path-
length related delays.
Where Ethernet and E1/DS1 circuits are configured on a link, Ethernet capacity is
reduced by 2.048 Mbit/s for each E1 included in the payload, or by 1.544 Mbit/s for
each DS1.
Any of the BW/modulation/capacity options listed in these tables can also be
selected for fixed modulation (non-ACM) operation. See Fixed Modulation on page 55.
Table 1-14. Maximum Throughput Coding: ETSI
Channel BW Modulation Airlink Ethernet L1 Ethernet L2 Ethernet
(MHz) Capacity Throughput Throughput Latency uS TDM
Mbit/s Mbit/s Mbit/s
1518 64 1518 64 1518 64 Latency
byte byte byte byte byte byte uSec
55 256 QAM 366 356 462 352 352 180 115 340
55 64 QAM 267 260 337 257 257 195 115 340
55 16 QAM 181 176 228 174 174 215 120 340
55 QPSK 90 88 114 87 87 285 120 340
27.5 256 QAM 181 176 228 174 174 325 225 448
27.5 64 QAM 133 129 167 127 127 350 225 448
27.5 16 QAM 89 86 112 85 85 395 225 448
27.5 QPSK 44 43 56 42 42 535 235 448
13.75 256 QAM 87 85 110 84 84 625 455 672
13.75 64 QAM 64 62 81 61 61 675 455 672
13.75 16 QAM 42 41 54 41 41 775 465 672
13.75 QPSK 21 20 26 20 20 1070 480 672
7 256 QAM 44 43 56 42 42 1160 865 1073
7 64 QAM 31 30 39 30 30 1275 870 1073
7 16 QAM 21 20 26 20 20 1460 875 1073
7 QPSK 10 10 13 10 10 2050 905 1073
260-668201-001 MARCH 2011 63

Table 1-15. Maximum Gain Coding: ETSI

Channel BW Modulation Airlink Ethernet L1 Ethernet L2 Ethernet
(MHz) Capacity Throughput Throughput Latency uS TDM
Mbit/s Mbit/s Mbit/s
1518 64 1518 64 1518 64 Latency
byte byte byte byte byte byte uSec
55 256 QAM 343 334 433 330 330 185 115 340
55 64 QAM 245 239 310 236 236 200 115 340
55 16 QAM 146 143 185 141 141 230 115 340
55 QPSK 74 72 94 71 71 315 120 340
27.5 256 QAM 170 165 214 163 163 330 225 448
27.5 64 QAM 124 117 152 116 116 360 225 448
27.5 16 QAM 73 71 92 70 70 425 230 448
27.5 QPSK 36 35 45 34 34 600 240 448
13.75 256 QAM 82 80 103 78 78 630 455 672
13.75 64 QAM 58 57 74 56 56 690 460 672
13.75 16 QAM 35 34 44 33 33 835 465 672
13.75 QPSK 17 16 21 16 16 1205 485 672
7 256 QAM 41 41 52 40 40 1175 860 1073
7 64 QAM 29 29 37 28 28 1295 870 1073
7 16 QAM 17 17 22 17 17 1575 885 1073
7 QPSK 8 8 10 8 8 2320 920 1073
64 AVIAT NETWORKS
Protected Operation
Eclipse IDU GE3 16x protection options address hardware, radio path, Ethernet, and
tributary functions.
For additional information on protection, refer to Eclipse User Manual.
Protected operati on between an I DU GE3 16x and an I NU i s not
supported. F or protected I DU l i nk operati on, protected I DUs
must be i nstal l ed at both ends of the l i nk.
Hardware and Radio Path Protection

IDU GE3 16x terminals are used in pairs to support hot-standby or space diversity.
l Hardware/equipment protection is used to provide hardware redundancy; the
standby equipment is switched into service in the event of a failure. This
protection is not hitless.
l Path protection (voting) is used to protect against changes in radio-path
variables, such as anomalies caused by signal reflection over water or by
ducting. This protection is hitless (errorless) between the received radio paths.
Hot-standby is used for hardware protection. Space diversity is used for path and
hardware protection.
Protected IDUs are installed with either two ODUs or one IRU6001.
Adaptive modulation can be used on hot standby or space diversity links.
The IDU designated as primary is default online for Tx and Rx.
The IDUs must be identically configured for all radio (RAC 60 module) settings.
An IDU protection cable and Ethernet NMS cable must be installed between the part-
ners.
l For Ethernet protection a protection cable must also be installed between
nominated DAC GE3 ports, and optical Y-cables fitted between optical user
ports and the customer equipment.
l For E1/DS1 hardware/trib protection a Y-cable assembly must also be connected
between the IDU trib connectors and the customer equipment.
The IDUs must be loaded with the same release of operating (embedded) software.
A unique IP address is entered for the IDU partners (each must be seen as a separate
device on the management network).
1IRU 600 is 1+1 optimized.
260-668201-001 MARCH 2011 65

l The network portion of the IP address must be common; the host portion must
be unique (both IDUs are on the same LAN).
l OSPF or RIP should be selected. Static routing can be used but care must be
exercised within a network of two or more hops of protected IDUs in the event
the IDU providing the cabled Ethernet NMS connection to the next hop is
powered-down.
Each time a protection switch occurs an informational event is recorded to indicate
the reason for the switch.
Hot Standby and Space Diversity

Hot standby (single-antenna) operation :
l ODUs are direct-mounted onto a coupler, which in turn is direct or remote
mounted to its antenna.
l The IRU 600 ACU incorporates a coupler to combine the primary and secondary
RFUs onto one waveguide feed.
o Hybrid hot standby options are available.
l Equal or unequal loss couplers are available:
o Equal has a nominal 3.5/3.5 dB loss per side.
o Unequal has a nominal 1.6 /6.4 dB insertion loss.
o Equal-loss couplers are recommended for IDU installations.
l The table below lists nominal coupler losses for ODU split-mount operation. For
IRU 600 ACU losses, see Antenna Coupling Unit (ACU) on page 44.
Space diversity operation :
l ODUs are direct-mounted onto separate antennas.
l For IRU 600, separate waveguide feeds are used.
o Hybrid space diversity options are available. See IRU 600 Link
Configurations on page 41.
Protection Switching:
l Rx path switching is hitless using Rx path voting. The least errored Rx data
stream from the IDUs is selected by the online IDU.
l Tx online and Rx online switching is not hitless. When a Tx switch occurs the
online Rx function, which controls hitless Rx operation, is also switched. The
reverse is also true.
o Tx and Rx online are maintained on the same IDU.
o With a Tx switch (hot-standby or space diversity), Tx and Rx online are
transferred to the partner (standby) IDU.
o Similarly, with an online Rx switch, Rx and Tx online are transferred to the
partner IDU.
l The online IDU also provides the online DAC 16xV2 function for trib protection
purposes. An IDU protection switch also results a trib switch (Tx and Rx tribs)
to the partner IDU.
66 AVIAT NETWORKS
l The online IDU does not determine/change the online DAC GE3 module for
Ethernet protection.
l When a protection switch occurs, the link will stay - it will not auto-revert to
what was the online IDU. It will stay until forced to change by a subsequent
alarm condition or by a Portal command.
l Protection applies only to the payload and internal alarm I/O; auxiliary data is
not protected.
o If auxiliary data is required, it should be configured for the primary IDU at
each end of the link, which is the default online IDU. In the event of a
protection switch (to secondary IDU Tx or Rx), the link must be returned to
primary online to restore auxiliary data.
Table 1-16. Nominal Losses for ODU Equal and Unequal Couplers
Frequency Bands Primary Arm Insertion Secondary Arm Insertion

GHz Loss dB Loss dB
37.0 - 40.0 4.0 (Equal), 2.0 (Unequal) 4.0 (Equal), 7.0 (Unequal)
27.5 - 31.3
24.25 - 26.5
21.2 - 23.6
14.4 - 15.35
12.75 - 13.25
10.7 - 11.7
7.11 - 8.5
5.925 - 7.11
Ethernet Interface and Module Protection

Optical Y-cables are used to connect the protected IDUs (hot standby or space diver-
sity) to a customer Ethernet port.
l Two optical cables are required per protected user port; one for Tx/Rx, one for
Rx/Tx. (Requires installation of an optical SFP transceiver module in each IDU).
l A DAC GE3 protection cable (standard Ethernet cable) is installed between
user-nominated protection ports.
The protection mechanism considers the DAC GE3 user port(s), DAC GE3 switch, and
IDU separately. The online Ethernet ports can be on the online or offline IDU.
DAC GE3 Protection
l Protection switching is not hitless.
l Link protection switching (hot-standby or space diversity) does not impact the
status of protected DAC GE3 modules.
o Default the primary IDU is online for link Tx/Rx and Ethernet Tx/Rx.
260-668201-001 MARCH 2011 67

o A switch of link Tx/Rx to the secondary IDU does not force a change of DAC
GE3; the primary side DAC GE3 remains online for Tx/Rx.
l Ethernet protection considers DAC GE3 port and switch operation:
o A DAC GE3 port failure does not force an IDU link switch.
o A DAC GE3 switch failure does force an IDU link switch.
Ethernet Optical Y-cable Protection

The figure below illustrates optical Y-cable protection on 1+1 protected IDUs.
The primary DAC GE3 and its optical Y-cable port are default online to the external
equipment, and is online to its DPP-connected RAC 60 link module.
On the Ethernet side:
l Both IDUs are online to receive Ethernet traffic from the connected equipment
but only the online IDU forwards traffic over the link.
l Only the online DAC GE3 is transmitting to the connected equipment. The laser
on the standby DAC GE3 is muted.
l The external equipment is not involved in the protection process. Failure
detection and service restoration is controlled entirely by Eclipse.
On the radio side:
l Both IDUs are Rx active to receive link data. The online IDU controls the voting
process to select which Rx path to use.
l Only the online IDU is Tx active.
Figure 1-17. Protected IDUs: Default Ethernet Operational Status
The figure below illustrates Ethernet protection behavior for various failure modes.
l With an online user port failure, traffic is redirected via the Y-cable to the
secondary DAC GE3, and back via its protection cable to the primary DAC GE3;
the primary IDU remains online for link Tx/Rx.
l With an online DAC GE3 module failure, both port and module online status is
transferred is to the standby DAC GE3, which also forces an IDU switch.
l With an online RAC failure, the switch to the standby RAC forces redirection of
Ethernet traffic from the primary to secondary DAC GE3 via its protection
cable; the primary DAC GE3 retains the online user port connection.
68 AVIAT NETWORKS
Figure 1-18. Example Protection Switch Traffic Paths
260-668201-001 MARCH 2011 69

E1/DS1 Tributary Protection

Y-cable assemblies (one for each set of 8xE1/DS1 tribs) are used to connect protected
IDUs to customer equipment.
l From the customer both IDUs (DAC 16xV2 modules) receive data, but only the
online IDU sends data to its RAC 60 module.
l To the customer, the online IDU sends data to customer equipment; the partner
IDU mutes its Tx line interface.
l Trib Tx and Rx functions are bonded - they are switched together to always be
with the online IDU.
A tributary LIU failure (DAC 16xV2 line interface unit failure) is an IDU switching con-
dition (will force a switch to the partner IDU).
A tributary LOS (Loss of Signal) alarm is also an IDU switching condition.
An online IDU switch forces a trib switch (Trib Tx and Rx) to the partner IDU. Pro-
tection switching is not hitless.
Protection Switching Conditions and Criteria

Protection applies to the payload. Alarm I/O is protected for internal events, but not
for external inputs and outputs. Auxiliary data is not protected.
l The mapping and transport of internal alarm events is protected (transported
within the NMS overhead). However the front-panel TTL input and relay output
interfaces are not protected. Simple external logic can be installed where
protection is required on these interfaces.
Switch Conditions: Hot-standby and Space Diversity

The primary IDU of the protected pair is default online for Tx and Rx.
The Tx online and Rx online functions are bonded. They are held together on one IDU,
or the other; the functions cannot be split across the protection partners.
l Online for Tx means that it is transmitting.
l Online for Rx means that it is controlling the Rx path protection switch
function and is sending Rx data to the DAC modules.
l A switch condition affecting one forces a switch to both.
Tx online and Rx online switching is not hitless.
Rx path switching between the two receive paths is hitless (errorless) for Rx path
alarm events.
l Receiver voting is used between the two receiving IDUs such that the least
errored data stream is selected on a frame-by-frame basis within the online Rx
IDU.
70 AVIAT NETWORKS
An Rx path alarm will not cause an Rx online switch.

When a Tx online switch is forced, the Rx online function is switched to be with the
new Tx online IDU.
Similarly when an Rx online is forced, the Tx online function is switched to be with
the new Rx online IDU.
A switch will not occur if there is a blocking condition on the partner IDU, such as
IDU missing, IDU alarmed, or System/Controls locks in force.
Protection switch oscillation is prevented by the guard time mechanism.
Switching Guard Times

To prevent protection switch oscillation a switch oscillation guard time mechanism
applies to online protection switching. (Does not apply to Rx path voting).
l A period of guard time begins immediately after each protection switch occurs.
l No protection switches are permitted during the guard time. Protection
switching may resume once the guard time has elapsed.
l To damp possible oscillations in the system the guard time is adjusted, using
the following rules:
o The guard time doubles after each switch (up to the maximum).
o The guard time halves after each period of guard time during which no
switching occurs (down to the minimum).
o When the guard time decays to its minimum, subsequent switch requests are
actioned immediately.
l The switch guard time has a minimum period of 5 seconds and a maximum
period of 320 seconds (5 x 26 events).
l The guard time mechanism is disabled in protection diagnostic modes.
Tx Online Switch Criteria

Switching from the online Tx to standby is initiated for the following local alarm con-
ditions:
l Software load failure
l Tx path failure:
o Tx synthesizer not locked
o Transceiver Tx failure
o Tx power failure
o Tx IF synthesizer not locked
o Tx cable IF synthesizer not locked
l RFU Tx cable IF synthesizer not locked
l RFU cable unplugged
l E1/DS1 tributary LIU failure.
260-668201-001 MARCH 2011 71

l E1/DS1 tributary LOS failure (subject to there being no trib LOS on the same
trib on partner IDU).
l Ethernet module (DAC GE3) failure
l A transmitter switch is also forced for an undetected silent transmitter failure.
This occurs when both remote IDUs are in receive alarm.
An onl i ne Tx swi tch forces an onl i ne Rx swi tch, and vi ce-versa.
Tx swi tch condi ti ons are effecti vel y Rx swi tch condi ti ons, and
vi ce-versa.
Rx Online Switch Criteria

Switching from the online Rx to standby is initiated for the following alarm con-
ditions:
l Software load failure
l E1/DS1 tributary LIU failure.
Silent Tx Switching
Silent Tx switching forces a local transmit switch when both far-end receivers are in
receive alarm. Its purpose is to prevent a silent transmit failure (a failure not detected
by the local hardware/software) from causing the link to go down indefinitely.
The switching command is returned immediately on loss of frame synchronization
(demodulator not locked) on both IDUs. The switch oscillation guard timer minimizes
the effects of any unwanted switch action due to momentary path fades or other
switching events.
Note that where both IDUs are in receive path alarm due to a path fade, no signal is
received in either direction. In such situations the silent Tx switch command will be
prompted by receive path alarms at both ends of the link, but will not be received at
the transmit ends of the link. No Tx switch will occur.
Switching Times
For an online switch, traffic (Ethernet and/or E1/DS1) is restored to service within 150
ms, typically within 100 ms.
For an silent Tx switch, traffic (Ethernet and/or E1/DS1) is restored to service within
150 ms, typically within 100 ms.
72 AVIAT NETWORKS
PCR Operation
PCR (Paperless Chart Recorder) is a software tool for RF path analysis. It is used
mostly after installation is completed to troubleshoot path performance degradation
like dribbling errors, intermittent loss of synchronization, and unusually high pro-
tection switching activity. It provides information that supports identification of root
causes of path performance degradation.
l PCR Viewer is ordered from Aviat Networks, and installed on a PC (Windows
NT, 2000, XP, Vista, 7).
l Files for analysis on PCR are downloaded to a PC from the Portal RAC History
screen, using the Export PCR tab.
l Downloaded PCR files are opened in the PCR application.
l Within PCR Viewer, RAC history data is presented as a time-referenced graph of
RSL, Tx output power, S/N ratio, and PA temperature, together with all RAC
alarms.
l The graph can be scrolled and the period shown on one screen view can be
adjusted from months, to weeks, days, hours, or minutes.
l Search options are provided for alarm, time, amplitude/level.
The RAC history and alarm data for PCR access is stored in non-volatile memory
(Eclipse flash card). See History on page 88.
Figure 1-19. Example Eclipse PCR Viewer Screen
260-668201-001 MARCH 2011 73

Orderwire Options
IDU GE3 16x does not include a built-in orderwire capability. Instead, where required,
a VoIP (Voice over IP) phone system can be installed using industry-standard VoIP
phones connected via the Ethernet NMS channel, or via the payload connections pro-
vided by the DAC GE3 module. Another option is to use a dedicated digital orderwire
system interconnected via the AUX sync or async data ports.
VoIP Orderwire
A VoIP orderwire network provides call access throughout the IP network or call
group. For IDU GE3 16x an orderwire network can be supported on the NMS, a routed
network, or on the L2 LAN payload connections established via the Ethernet DAC
GE3 module.
These Ethernet network connections simply provide the fabric over which the phones
communicate. Generally no additional Eclipse intervention or configuration is
involved - all configuration for VoIP operation is performed on the VoIP phones.
l Each phone is configured with its own unique IP address, which will be on the
same subnet as the radio it is connected to.
l VoIP phones share bandwidth with other traffic on the network.
One exception to this rule can be on a routed network, such as Eclipse NMS, where
there is a need to talk between phones on separate branches of the network. Normally,
NMS routing is biased towards and away from the Network Operation Center (NOC),
meaning routing between branches may not be enabled. Therefore, in instances where
VoIP interconnection is required to and from all points, a dynamic routing, such as
OSPF, should be enabled on all Eclipse nodes. It facilitates routing by propagating all
routes to all nodes from all points in the network.
Where VoIP operation is supported via Eclipse payload network connections (L2
LAN), priority tags such as DiffServ can be set on the VoIP phones to prioritize VoIP
traffic against other traffic on the LAN. In this case, DiffServ QoS options must be set
within the DAC GE3 to act on VoIP frame prioritization.
VoIP connections can be established beyond Eclipse network boundaries - to any point
within a wider IP network that may incorporate other network provider products, and
do so over the Internet. All that is needed is a contiguous IP/Ethernet network con-
nection.
The recommended VoIP phone is the Welltech LANPhone 201 (LP-201). It provides
basic point-to-point communication - conference or multi-party calls are not sup-
ported. It uses Session Initiation Protocol (SIP) for establishing call sessions. 1
1SIP is an RFC standard (RFC 3261) from the Internet Engineering Task Force (IETF).
74 AVIAT NETWORKS
The LP-201 may be ordered from Aviat Networks or Welltech. A user manual is sup-
plied with each phone. For more information on the LP-201 go to www.welltech.com.
The LP-201 may be used to communicate with SIP compliant VoIP products from
other suppliers.
Welltech and other suppliers of IP phones offer an extensive range of IP phones and
phone systems. IP PBX, conference, and call management products are available.
Digital Orderwire
An orderwire network can be established with digital orderwire products using options
on the AUX plug-in to provide the data interconnection.
Suitable orderwire products are available from suppliers such as Raven and Ardex.
Where orderwire interconnection with legacy Aviat Network products is required
(TRuepoint, Constellation, Megastar), the approved solution requires the Raven 61510
Digital Orderwire.
The Raven 61510, enables voice communication over a 64kb/s digital service channel.
It supports 64kb/s RS-422 (V.11) ports for connection to the Eclipse AUX data ports,
as well as two analog VF ports, or one VF port and one or two RS-232 data ports for
connection to legacy radios. A digital bridge function provides a conference capability
for all signal paths. Linear and loop network architectures are supported.
For information on use of the Raven digital orderwire within mixed Eclipse and lea-
gacy radio networks, refer to the Aviat Networks paper: Orderwire Interopability
Between Eclipse and Legacy radios. A user manual is supplied with each Raven prod-
uct.
260-668201-001 MARCH 2011 75

Management Tools
This section provides an introduction to the Portal craft tool and to the ProVision ele-
ment management system (EMS). Refer to:
l Portal on page 76
l ProVision on page 80
Portal
Portal is the Eclipse configuration, commissioning and diagnostics craft tool. It is a
web-enabled application supported in the Eclipse system software.
Portal works seamlessly with ProVision, the related element manager, to provide an
integrated solution for network rollouts, fault resolution, and maintenance.
It is installed from an installation file on the Eclipse SW Setup CD, which is supplied
as part of the Eclipse Installation Kit. The Installer installs both Portal and Online
Help.
When Portal is installed on a PC, it automatically downloads support from the radio
as needed to ensure that Portal always matches the version of system software sup-
plied, or subsequently downloaded in any radio upgrade.
Portals connection to an Eclipse IDU or INU may be via Ethernet or V.24. The V.24
connection is for local access only and should only be used to initially load an IP
address into a new node before reconnecting your PC using the much faster Ethernet
connection.
Portal is a Java based application. All screens have the look and feel of a Windows
environment with access to on-screen features and commands provided by mouse
click or quick-access key commands.
Refer to:
l PC Requirements on page 77
l Portal TCP and UDP Port Usage on page 77
l Portal Auto Version on page 77
l Portal PC to Eclipse Connection Options on page 78
l Portal Log-in on page 78
l Eclipse Online Help on page 79
l Portal Features on page 79
76 AVIAT NETWORKS
PC Requirements
Hardware Requirements
The minimum PC hardware requirements are:
l Pentium 4 or later
l 512 Mb RAM (1 Gb recommended)
l 250 Mb free hard disk space
l Serial COM port (COM1 or COM2), or USB port plus external USB-to-serial
adaptor for local V.24 connection, or Ethernet 10Base-T LAN port with RJ-45
connector for Ethernet local connection.
l 1280x768 screen resolution
l 2 or 3-button Mouse
l 101-key US keyboard
Software Requirements
To run Portal Microsoft Windows 7, Windows XP or Vista is required. Earlier oper-
ating systems may operate, but are no longer supported/tested.
Both 64-bit and 32-bit versions of Windows 7 are supported on the Portal installer.
The same installer also supports 32-bit versions of both XP and Vista.
Portal TCP and UDP Port Usage

Portal requires TCP ports 80 and 26003. The config restore function uses TCP port
26000.
For software loading a connection is made in the reverse direction on a random port.
This means software loading does not work through a firewall.
Auto detection uses UDP port 26005 and the first available port between 26006 to
26099.
Portal Auto Version

The auto version feature within Portal ensures the Portal software version running on
your PC automatically matches the version of embedded (system) software installed
on Eclipse IDUs and INUs. This avoids the need to hold multiple versions of Portal on
your PC, and to select from them when connecting to an Eclipse radio.
Version matching is achieved through the use of difference (diff) files, each containing
the difference between the Portal software version files. The diff files needed to match
Portal to the version of Eclipse embedded software, are held within the embedded soft-
ware set. This means that:
260-668201-001 MARCH 2011 77

l For a new Eclipse installation the version of Portal supplied in the Setup CD
will always match the embedded software of the equipment being installed.
l In other situations, the auto version feature delivers transparent version
matching to ensure the version of Portal used is always compatible with Eclipse
software.
Portal PC to Eclipse Connection Options

Connection options are 10/100Base-T Ethernet, or V.24/RS-232:
Ethernet provides faster communication and supports access to all other NMS-con-
nected node on the network. There are three Ethernet connection options:
l Auto discovery of the IP address and name of the connected node, with auto
matching of the Portal PC addressing.
l Direct-entry of a LAN compatible IP address within the TCP/IP properties
window on your Portal PC. This is used where the auto discovery mechanism
cannot establish compatible routing with the connected node.
l DHCP connection, where the Eclipse node is the server and your Portal PC the
client.
V.24/RS-232 is typically only used to load an IP address into a new, unconfigured
node, from which point Ethernet is used.
Portal Log-in
The IDU GE3 16x includes Ethernet and V.24 front-panel Portal PC (NMS) ports.
Ethernet Connection
For Ethernet (10/100Base-T NMS port) there are two connection options:
l Direct addressing using the Portal PC TCP/IP properties window to set a LAN
compatible address on your PC. It requires knowledge of the IP address of the
connected radio. Where not provided, it is discovered using Portal address auto-
discovery.
l DHCP server, where a server function in the INU provides an IP address to the
Portal PC client. The TCP/IP properties on the Portal PC must first be set to
obtain and IP address automatically. This option does not require knowledge of
the IP address of the connected terminal.
V.24 Connection
For a V.24 connection, knowledge of the IP address for the connected INU/INUe is not
required.
For information on Portal PC connection, refer to Eclipse User Manual.
Log-in Security
Basic login security options, if set in Portal, require username and password entry.
Options are prompted for administrator, engineer, or operator.
78 AVIAT NETWORKS
Eclipse Online Help

Eclipse Portal Online Help provides access to the Portal volume of the Eclipse User
Manual for general and context-sensitive viewing. It is a web-based (html) helpset.
Portal Online Help is installed from an installation file on the Eclipse Software Setup
CD - the Installer installs both Online Help and Portal application software.
l It displays using the default Web browser on your PC, and is accessed from
Portal to provide general or context sensitive help.
l Version matching is used to ensure that the version of Portal being used to
communicate with the radio is matched to the relevant version of Online Help.
Portal Features
The table below introduces configuration features. The following table introduces diag-
nostic features. For more information see Diagnostics on page 85. Note that Portal
treatment for the INU and IDUs is common, hence the use of 'Plug-in' terminology,
which for IDUs is the equivalent 'module'.
For detail information, refer to Eclipse User Manual.
Table 1-17. Portal Configuration Overview
Configuration Function Summary

Feature
Plug-in/module Screens prompt for all configuration actions relevant to the selected
setup plug-in. RAC, DAC, AUX.
Protection Supports RAC/ODU and RAC/RFU partnering for hot-standby or space
settings diversity.
Circuit cross- Screens prompt for traffic, auxiliary, and EDS cross-connections
connect between relevant modules.
configuration
Network Screens support single or individual port-based addressing, and
management IP static or dynamic routing. Also selection of an Ethernet DHCP server
addressing and option for Portal PC log-in.
routing
Alarm Actions Prompts the mapping of alarm input/output actions within the
network.
Date and time Screens prompt for date and time settings based on locality, SNMP, or
PC settings.
License upgrade Screen provides a view of the licensed capacity and any licensed
features, and prompts for the up-loading of a new license.
Software Screens supports loading of system software.
management
260-668201-001 MARCH 2011 79

Table 1-18. Portal Diagnostic Features
Diagnostic Fea- Function Summary

ture
System summary Screen provides a system layout and real-time status overview.
Circuit connection data provides a visual indication of traffic cross-
connections. Quick-access is provided into relevant configuration and
diagnostics screens.
Event browser Screen provides a real-time view of all alarms, both active and cleared.
Icons indicate severity, and if active or cleared. All events are time and
date stamped, and options are provided to view just current alarms, or
all occurrences of a selected alarm type. The events listing can be
exported as a csv (Excel) file.
History History screens provide selection of 15-minute or 24-hour options.
15-minute provides viewing of seven days worth of 15 minute data
bins; 24-hour provides one months worth of 1 day data bins. Screens
are provided for the RAC and DAC GE3 modules.
Alarms Screens provide a tree-view of all alarm actions for a selected plug-in
since log-on, or a history reset.
Performance Screens provides provide a range of operational data including G.826,
RSL, current BER, remote fade margin, transmit power. For ACM
operation it includes current and statistical data on the configured
modulations.
For the DAC GE3 it presents throughput, discards and errors and
RMON performance data per port.
System controls Screens present relevant diagnostic menus for setting loopbacks, AIS,
protection locks, Tx mute, and BER testing.
Parts Screen provides serial number, part number, and time in service for
the IDU.
Advanced Provides software reset and history-clear functions.
Management
ProVision
ProVision is a network-wide manager of Aviat Networks' devices, the network ele-
ments. It also manages supported third party devices.
ProVision is installed on a Windows or Solaris server, typically at a network operating
center. It communicates with network elements using standard LAN/WAN IP address-
ing and routing. Each node or terminal has its own unique IP network address.
ProVision provides both management and configuration functions.
Network Management
The management application is SNMP based (Simple Network Management Protocol).
All elements on the network are polled and their responses checked to determine cur-
rent status. Any state change since the previous poll is captured as an event specific
to the polled device. The action taken by ProVision to present the change to an oper-
80 AVIAT NETWORKS
ator is dependant on the significance of the change (event severity), and any event fil-
tering applied within ProVision for the alarm type.
Hierarchical network views allow rapid incorporation of network events. These may be
map-based, event-tree, or event-log, and presented independently or in combination.
Specified elements may be assigned to one or more service groups to allow service-
level prioritization on essential circuits, or to match different customer requirements.
Through the Scoreboard function, pie or bar graphs of network event information are
available as a visual summary of system activity. Collected data can also be presented
in graphical or tabular form to assist trend analysis.
ProVision also supports a circuit tracing capability to automatically discover the rout-
ing of traffic circuits through the Eclipse network, and the remote download feature
supports software upgrades to selected devices simultaneously.
Element Configuration
ProVision uses Portal to configure Eclipse devices. On operator command a Portal ses-
sion is remotely opened and is managed just as if the operator was locally connected.
ProVision Feature Summary

This table provides a summary of ProVision features. For more information, refer to
the ProVision User Guide.
260-668201-001 MARCH 2011 81

Table 1-19. ProVision Feature Summary
Feature Description
Circuit Allows you to diagnose problems within a circuit and isolate faulty
Diagnostics equipment.
Circuit Trace Circuit trace initiates the tracing of all circuits that originate or terminate
from the selected DAC or from an Eclipse radio.
Circuits and Trace and provision all Eclipse radio circuits through the network. Adjust
Circuit end-to-end circuits directly and remotely from ProVision.
Provisioning
Device Craft Enables you to connect any craft tool to a device to manage, troubleshoot and
Tools maintain the device. The craft tools can be launched from within ProVision.
Data Collection Background G.826 error performance data is automatically collected and
stored on a per-radio basis. This feature allows you to review historical data
on a particular radio to better diagnose any problems that may come up.
Database Enables you to enter a backup description and to indicate what the system
Backup should include in the backup, as well as the frequency of the scheduled
backup and any backup purges. Manual backup can be performed at any
time.
Diagnostic Supported for multiple devices, including Constellation, XP4, TNet and DART,
Tools used when an event indicates there is a fault with a radio. ProVision
automatically logs into the radio, retrieves the diagnostic settings from the
radio and displays them.
Ethernet BW Presents the Ethernet bandwidth use for a selected part of the network,
Utilization which can be set by region, devices or circuit.
Ethernet Presents in graphical formats the packet size and type per port and channel
Packet Type over time.
and Size
Ethernet Presents in a graphical format, the Ethernet throughput discards and errors
Throughput per port and channel.
Discards and
Errors
Event Browser Displays a scrolling list of events captured by the system, color coded by
event severity, to view crisis events at a glance. You can adjust the event
browser display criteria, acknowledge/unacknowledge events, and clear
events.
Event Notifies you via email, pop-up message, or audio signal whenever selected
Notification events occur within the network. You can also instruct ProVision to run a
shell script for a batch file whenever selected events occur.
Event Pre- Events that match the pre-filter values are blocked before reaching the
Filter system. Filtering events at input reduces the number of events being fully
processed and increases performance.
Event Severity Each event has a color-coded to indicate its severity level. The six levels and
their color codes are critical (red), major (orange), minor (yellow), warning
(cyan), normal (green) and informational (white).
Generic SNMP ProVision allows you to monitor and manage non-HSX devices deployed to
Devices your network. Load and edit devices yourself or use one of HSXs pre-defined
Generic Device Packages.
NBI Collects all the information relevant to the configuration of an Eclipse network
Configuration into XML format and includes information such as the names and IP
Management addresses of the Eclipse radios, information on the plug-ins, link information,
cross-connect information and ProVision server name and IP address.
NBI Event Converts ProVision events, as displayed in the event browser, into a
Management consistent format for porting to the Network Management layer.
82 AVIAT NETWORKS
Feature Description
NBI Converts the collected performance data from the managed network devices
Performance into ASCII text files so that it can be integrated with the Network Management
Data layer.
Management
NBI Topology Collects all the information on the network topology such as object name,
Management object type, object container information, device IP address, SNMP
community strings, object coordinates (on the map viewer).
Network Events ProVision continuously monitors and reports on key network incidents.
Events are generated whenever monitored changes occur in the status of
individual network elements, their connections, or the network as a whole.
Northbound Provides the connection between the ProVision application and the higher
Interface management level functions.
(NBI)
Performance Performance thresholds screens enable an alarm function to be associated
Thresholds with one or more RMON performance statistics, which are captured within 5
minute, 15 minute or daily bins for each port and channel.
Performance Enables you to monitor the network performance at all times and helps you
Trends identify the bottlenecks created by problem devices in your network.
Scoreboard Provides a summary of the status of a network in a graphical (pie-chart or bar
Groups chart) format. You can modify the filters for each scoreboard and open a
specific event browser to view all events associated with that scoreboard.
Search Search your network using parameters such as IP address, object container,
Capability location, object type or data collection type, or search the Tree View to find
specific devices.
Security for Allows you to set up secure access to Eclipse, TRuepoint, XP4 and DART
Devices radios where a valid user name and password must be provided to access the
radios diagnostic functions. This feature may also be set for multiple radios
of the same type and within the same container.
Security Log Allows you as the network administrator to check on ProVison user activities.
The security log is displayed in an event browser and you can change and
save the filter settings just like any other event browser.
Security Each user has a login and a password set by the system administrator to
Password prevent unauthorized access to the network.
Server Reports Saves and retrieves reports from one device or from multiple devices. Report
on Inventory, Capacity, Network Health, Eclipse Fault, and more.
Sleep / Wake Allows you to put a device to sleep. The device is active, but ProVison
Devices ignores all events from the device. This can be useful to prevent unnecessary
events from being collected. The wake command reverses the sleep
command.
Software Update and activate the software for Eclipse, TRuepoint, or StarMAX devices
Loading simultaneously.
Task Manager Lists all tasks, completed or otherwise, that have been executed in ProVision.
Pop-up windows provide additional information and functions.
Topology Import and export ProVision network topologies as XML files. These backup
Import / Export files can be reloaded onto ProVision when upgrading to a newer version.
User Accounts The network administrator can create separate user accounts for each user.
Each user can be assigned one of three levels of security (NOC Engineer,
Portal Engineer, NOC Operator) depending on responsibilities of the user.
User Log-Ins Logging in allows multiple, simultaneous user sessions. Changes made by
one user are immediately reflected in the ProVision base. The system locks an
object when changes are made so no two users can change the same at the
same time.
View Radio Icons in both the tree viewer and the map viewer indicate changes in the
Icons radios status.
260-668201-001 MARCH 2011 83

Feature Description
View Submap View and drill down into the elements of a selected device using a submap.
View via Displays the network as icons with lines representing the links between
Physical Map radios. Individual containers and radios can be placed anywhere on the
Viewer screen. A map image can also be imported to serve as a background to the
map viewer.
View via Tree Organizes the entire radio network as a tree of containers and devices. Each
container (for example, a region) is represented as a parent with all the
devices positioned underneath as its children.
84 AVIAT NETWORKS
Diagnostics
This section introduces diagnostics provided by Portal for Eclipse. For detailed infor-
mation see the Eclipse User Manual.
Refer to:
l System Summary on page 85
l Event Browser on page 86
l Alarms on page 87
l History on page 88
l See "History: Ethernet"
l Performance on page 89
l System/Controls on page 93
l Parts Screen on page 100
l Advanced Management on page 100
System Summary
The System Summary screen provides a real time overview of system status.
It illustrates:
l IDU status
l Module type, function, and status
l Traffic interconnects (DPP for Ethernet, circuit/bus for E1/DS1)
l Configured link capacity
l Capacity available on the DPP for Ethernet
l IP address, terminal name, and site name
260-668201-001 MARCH 2011 85

Figure 1-20. Example IDU GE3 16x System Summary Screen
Event Browser
The Event Browser provides a real time view of all events, both active and cleared. The
browser has a nominal capacity of 5000 events, after which time new events replace
earliest events on a one-for-one basis.
The screen opens to an event listing, which scrolls down to the latest event, unless
auto-scroll is turned off. Other lists (boxes) can be enabled using tabs on the lower
right.
Events provides a date/time-stamped listing for each new event (alarm and infor-
mational). Events are shown in true chronological order with time-stamping to a 0.1
second resolution. Indicators assist with identification of event source (plug-in loca-
tion), whether it is a new or cleared event, and the severity and status of the event.
All Occurrences provides an automatic listing for all like events selected (high-
lighted) in the Event box. It is particularly useful in matching and viewing the history
of one event type, and when coupled with the plug-in location graphic, also by plug-
in.
Export Events allows an event listing to be saved as an Excel compatible CSV file to
a folder on your PC. With Active Only selected, only active events are exported.
Help for Event provides access to Eclipse Online Help for alarm and informational
events. For an alarm event it provides an on-screen description, probable cause and
recommended action for the selected alarm.
l Providing Online Help is loaded on your Portal PC, it is automatically opened
to the relevant alarm page when the Help for Event is selected.
86 AVIAT NETWORKS
Figure 1-21. Event Browser Screen
Alarms
The Alarms screen provides a tree view of alarm history for a selected module since
logon or since a History reset.
The alarm tree automatically opens out to the base level of the highlighted alarm
point.
l Tabs indicate an active alarm point, and the color its severity. Colors used
reflect the international severity standard.
l Alarm Management options support quick identification of, and navigation
between active alarms.
l With Reset History historical events can be removed to display only currently
active alarms and subsequently any new alarms, or change in alarm status.
l Help for Alarm provides access to the Online Help alarm files for alarm
description, probable cause and recommended action.
o Providing Online Help is loaded on your Portal PC it opens to the relevant
alarm page when the Help for Alarm is selected.
260-668201-001 MARCH 2011 87

Figure 1-22. Alarms Screen
History
A Link History screen supports graph, report, and combined graph and report screen
views of link-based operational status.
A resolution option provides selection of 15 minute or daily (24 hour) options. 15 min-
ute provides viewing of seven days worth of 15 minute data bins; daily provides one
months worth of 1 day data bins.
l The Graph screen provides a histogram of 15 minute or daily data bins of RSL,
G.826 statistics, event detected, and configuration changes.
l The Report screen enables selection of summary data for a selected period (min,
max and mean). It also supports an event listing for the selected period.
l Report and Graph screen data can be combined and shown on the same screen.
l A PCR Export tab is used to download history and alarm data to a PC for
subsequent analysis using the PCR Viewer application. See PCR Operation on
page 73
Tooltips provide information on screen options and function.
Both 15-mi nute and one-day data bi ns are captured from
power-on.
Hi story data i s hel d on a F I F O basi s. Data i n excess of the 15
mi nute or dai l y bi n maxi mums i s del eted i n favor of new-i n
data.
88 AVIAT NETWORKS
Figure 1-23. Link History Graph Screen
Performance
Performance screens support:
l Link Performance on page 89
l E1 Trib Performance on page 90
l NCC Performance on page 90
l Ethernet Performance on page 91
All performance screens include an Export tab, which allows data to be saved to an
Excel compatible CSV file on your Portal laptop.
Link Performance
The Link Performance screen provides a comprehensive overview of performance data
for the radio link.
Data is shown in two tables, Status Monitors and G.826 Monitors.
Status Monitors captures RSL, Remote Fade Margin, Detected Tx power, ODU/RFU
Temperature, -48Vdc ODU/RFU Supply Voltage, and Current BER Reading. Data is
updated at 2 second intervals.
The current BER reading presents a BER estimate from one 2-second measurement
interval to the next. It does not reflect an average-over-time BER.
For the IRU 600 the status field also captures RSL and Tx power output at the ACU
waveguide antenna port.
260-668201-001 MARCH 2011 89

With adaptive modulation selected, the field includes data on the current modulation
in use (modulation rate and coding) for Tx and Rx. (Tx and Rx are not synchronized -
it is possible for an IDU to be transmitting using one modulation, and receiving from
its remote partner that is transmitting on a different modulation).
G.826 Monitors captures link G.826 statistics. Data is aggregated from the time a
start button is clicked and continues until the Stop or Clear buttons are selected, or
the Portal session is terminated (log0ff). Data is updated at 2 second intervals.
This field includes data on:
l Available Rx time (demod locked time - no sync loss).
l Sync loss time (demod unlocked).
l Time spent on each modulation state.
A DPP field captures good/bad packet counts on the RAC 60 to DAC GE3 connection.
Figure 1-24. Link Performance Screen
NCC Performance
The NCC Performance screen presents temperature and -48Vdc supply voltage.
E1 Trib Performance
Buffer slip and CRC error performance is available on E1 DAC 16xV2 tribs.
Buffer Slip Warning enables buffer slip events to be captured as warnings (infor-
mational events) in the Event Browser screen.
90 AVIAT NETWORKS
Buffers are used to absorb any small fluctuations between the frequency of the incom-
ing signal with that of the local (DAC) clock frequency. Buffers slips occur when there
is excessive jitter or wander on E1 tribs - the buffer is unable to cope with the
frequency difference.
l Data is written into the buffer at its arrival rate and read at the local frequency.
l The buffer absorbs any small random zero-mean-frequency fluctuations, but
frequency offsets will make the buffer empty or overflow, sooner or later.
l There are two buffer slip event types; Trib Input, and Trib Output. A trib input
event records a buffer slip on the trib input to the DAC. A trib output event
records a buffer slip on the trib input from the RC 60 module, which is in the
trib output direction.
Error Performance enables a cyclic redundancy check (CRC) on DAC 16xV2 mod-
ule, thereby providing a background error performance indicator for the selected trib.
This CRC function is provided for E1 rates only and is enabled on one trib at a time.
Traffic on the selected trib is not affected.
The check process accesses the G.704, CRC4 Multiframe, which is a background error
check function provided between devices operating with G.704 framing.
l The circuit being monitored must be end-to-end terminated on framed-rate
multiplexers, or similar, to generate the G.704 framing, which includes the CRC
function. In other words, the circuit supported by the DAC 16xV2 must be
operational for user traffic to provide the multiframe needed for the monitoring
process.
l The errors detected by the monitoring process are circuit errors. That is, they
may have been generated by any device within the circuit, which includes all
upstream or downstream devices from the IDU.
l Separate monitoring options are provided for upstream and downstream traffic
directions.
l The Line Facing option monitors CRC error counts on the stream from the trib
interface.
l The Bus Facing option monitors counts on the stream from a link (RAC).
Ethernet Performance
Ethernet performance is monitored using Statistical and Graphical views.
The Statistics screen, provides RMON performance statistics for each port.
A Customize option provides a performance filter. Selected (not required) items can be
hidden from the main view. When used, the main screen includes a warning that the
filter is active.
An Export option saves performance data to your PC as a .csv file.
260-668201-001 MARCH 2011 91

Figure 1-25. Ethernet Statistics Screen
The Graphs screen displays for a selected port/channel the utilization (throughput),
traffic type, and errors/discards for Tx and Rx directions.
Data is captured in 3 second intervals. Data/counts are averaged/totaled for the inter-
val.
In the detail (main) window data per capture interval is viewed using your mouse
pointer.
92 AVIAT NETWORKS
Figure 1-26. Ethernet Graphs Screen
System/Controls
System/Controls presents diagnostic menus for plug-in cards. See:
l Safety Timers on page 93
l Link Options on page 94
l System/Controls on page 93
l DAC 16xV2 Options on page 95
l DAC GE3 Options on page 97
l AUX Menu on page 99
l Loopback Points on page 99
Safety Timers
A safety timer acts on all System/Controls On selections. Applies to Tx mute, digital
and IF loopbacks, and to Tx and Rx locks for protected operation. Timer options are:
l Test for 60 seconds
l On for a user-set time
l Always on (until manually turned off)
260-668201-001 MARCH 2011 93

Diagnostic Indications of a System/Controls Application

The Event Browser and Alarm screens capture the application and subsequent release
of System/Controls diagnostic options. While options are active:
l The diagnostic icon is displayed in the Portal status bar.
l The NCC Test LED flashes orange.
Link Options
For a 1+0 non-protected link the options are:
Tx Mute: Mutes the RFU transmitter.
Digital Loopback: Applies a bus facing digital loopback.
IF Loopback: Applies a bus facing IF loopback.
For a 1+1 protected link the options include:
l An indication of which IDU is online.
l Controls to lock a Tx/Rx online.
l An ability to switch to an online secondary from primary, and vice-versa. This
is used for field testing purposes and to restore an IDU to online status.
l A graphical indication of protection status.
l Tx mute and digital or IF loopbacks per RAC.
The screen below shows System/Controls for a protected link, with the secondary IDU
online for Tx/Rx. The secondary IDU is controlling the Rx path voting (Rx signal from
both IDUs).
Figure 1-27. Link System/Controls Screen: Protected Link
94 AVIAT NETWORKS
DAC 16xV2 Options

Screen-based options support trib-by-trib selection of:
l Line facing loopback
l Radio facing (bus facing) loopback
l Transmit AIS
l PRBS generator with G.821 data receiver
A loopback or AIS can be enabled on a trib (loopback and AIS selections are mutually
exclusive; only one can be selected per trib).
A loopback or AIS can be enabled on any number of tribs at the same time.
PRBS is enabled on one trib at a time.
The figure below shows loopback points and directions.
l Icon confirms that a line facing loopback is applied to trib 1.
l Icon confirms that a radio facing loopback is applied to trib 3.
l The highlighted trib has PRBS enabled.
l Trib names are set from the Plug-ins screen.
An On selection of loopback or AIS brings up Safety Timer options.
260-668201-001 MARCH 2011 95

Figure 1-28. DAC 16xE1 System Controls Screen
PRBS Generation
The built-in PRBS generator and G.821 receiver support looped, and both-way tests on
tribs. The Generator provides a standard BER 215-1 test pattern.
For a looped test the DAC provides the PBBS generator and G.821 receiver.
For a both-way test, the PRBS generator on one DAC is G.821 received on its remote
DAC, and vice-versa.
External BER testers provi de superi or measurement accuracy
and access to a wi der range of test and measurement func-
ti ons.
Auto Insertion of AIS or PRBS on Tribs

Auto insertion of AIS occurs when:
l A demodulator unlock occurs
l Loopbacks are set
96 AVIAT NETWORKS
Demodulator Unlock
When a demodulator-unlock occurs, it inserts an alarm signal (AIS) on all traffic cir-
cuits towards the customer. Demodulator unlock may occur under severe fading or an
equipment fault.
An on-board master clock within the DAC/IDU maintains customer-facing clocking ref-
erences when the expected signal input and associated clocking reference from its
RAC/radio is missing, or below the minimum level required.
Loopbacks
When loopbacks are applied:
l AIS is transmitted on the affected tributary towards the customer.
l For a line-facing tributary loopback, and for a link digital loopback, AIS is not
transmitted. Instead, as well as traffic from the customer being looped back
towards the customer, it is also transmitted in the radio facing direction of the
affected circuit(s).
l For a link IF loopback traffic from the customer is looped back to the customer,
and at the remote end the resultant demodulator-unlock initiates AIS on all
traffic circuits towards the remote customer.
AI S may al so be forced onto a DAC tri butary usi ng the System
Control screen.
DAC GE3 Options

The System/Controls screen presents options for:
l Diagnostics
l Synchronization
l MAC Address Table
Diagnostics
The Diagnostics screen displays port and module status, port interconnects, summary
port speeds in Mbit/s, port shutdown and MAC flush prompts, and protection pair-
ing. The shutdown includes a safety timer function. The port RJ-45 graphic reflects
real-time status of the activity and connection status LEDs.
260-668201-001 MARCH 2011 97

Figure 1-29. DAC GE3 System/Controls Diagnostics Screen
Synchronization
The Synchronization screen summarizes Synchronous Ethernet settings for sync
source, sync status, and whether a port is enabled as a master or slave for sync
in/out.
MAC Address Table

The MAC Address Table lists the addresses held in the MAC register, with filter
options to sort by MAC Address, Port Members, Status, and VLAN ID.
l An address can be entered to check its presence within the table.
l Port Member provides a port-based filter on the MAC address listing.
l Status provides a filter on address type: dynamic, static or invalid.
l VLAN ID provides a filter on the VLAN ID range: 0 to 4095.
98 AVIAT NETWORKS
Figure 1-30. System/Controls MAC Address Table Screen
AUX Menu
The AUX System/Controls screen enables line and radio facing loopbacks, and loop-
back duration.
Loopback Points
Loopbacks are set via Portal or ProVision.
l DAC / Trib loopbacks are applied per trib and multiple loopbacks can be set at
the same time. Loopbacks only affect traffic on the selected trib(s).
l RAC / Radio / Line loopbacks affect all traffic on a link.
l A Circuit loopback only affects traffic on the selected circuit.
l Loopback timers are provided.
The figure below shows loopback application points for The RAC 60 and DAC 16xV2
modules.
AUX supports line and radio facing loopbacks; as for DAC 16xV2.
Loopbacks are not supported on DAC GE3.
260-668201-001 MARCH 2011 99

Figure 1-31. Loopbacks
Parts Screen
The Parts screen presents:
l Part number
l Part revision
l Serial number
l Time -in-service
Data is provided per module for the IDU - IDU data is common to all modules. Data
for the ODU or IRU 600 is included.
Time-in-service is initiated from the time the item is placed in operation. The counter
resets to zero on removal from service or power-down. The count is in whole hours.
Advanced Management
The advanced management screen supports two functions:
l Software Reset provides a hard reset for the software-resettable modules:
NCC, DAC GE3, ODU, IRU 600.
o A software reset is equivalent to a power-down reboot (power off - pause -
power on), with one important difference; a copy of the Helpdesk Data File is
automatically saved to a default folder on your Portal PC at C:\Program
Files\Portal\Reset Logs\. It can be likened to a reboot for a PC.
l Clear Events and History clears all historical data from the Event Browser
and History screens. It is for use post-commissioning or after re-configuration
or remedial work to clean out unwanted, prior data.
l Lock Out enables a time to be set after a reset (software reset of power reset)
before Portal write access is permitted. It has application in ProVision managed
networks where precedence for any ProVision network applied configuration
updates (after a reset) are required to have precedence (be applied) over any
local Portal applied updates.
100 AVIAT NETWORKS

260-668201-001 MARCH 2011 101

260-668201-001
WWW.AVIATNETWORKS.COM

IDU GE3 16x Product Description

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IDU GE3 16x Product Description

Uploaded by

Copyright:

Available Formats

ECLIPSE IDU GE3 16x

Copyright 2011 by Aviat Networks, Inc.

260-668201-001 MARCH 2011 1

Aviat Networks Service and Sales

Sales and Sales Support:

260-668201-001 MARCH 2011 3

Corporate Headquarters International Headquarters

Copyright & Terms of Use 1

260-668201-001 MARCH 2011 5

260-668201-001 MARCH 2011 7

Eclipse IDU GE3 16x Product Description

Introduction To Eclipse IDU GE3 16x

Li sted features not supported at the March 2011 product

260-668201-001 MARCH 2011 9

Figure 1-1. Eclipse IDU GE3 16x with RFU Options

Smaller, Smarter, Faster

Adaptive or Fixed Modulation

Hot Standby or Diversity Protection

Carrier Class Ethernet Features

Extended E1/DS1 Transport Capabilities

Eclipse Node Inter-operation

Auxiliary Data Channels and Alarm Mapping

260-668201-001 MARCH 2011 11

IDU GE3 16x Modules

260-668201-001 MARCH 2011 13

IDU Status LED

260-668201-001 MARCH 2011 15

DAC GE3 Description

Phased Release of Features

260-668201-001 MARCH 2011 17

SFP Type: Single Mode 1000Base-LX Multimode 1000Base-SX

Table 1-2. SFP Electrical Port Specifications

SFP Type: 1000Base-T

Basic Port Settings

Basic Switch Settings

Switch Fabric and VLAN

260-668201-001 MARCH 2011 19

set to 0 (low/no priority). If pushed into an external network, it will be with a

260-668201-001 MARCH 2011 21

l MPLS Exp defines the Multiprotocol Label Switching (MPLS); IP traffic is

260-668201-001 MARCH 2011 23

Airlink Recovered Timing (ART) versus Eclipse Distributed Sync

260-668201-001 MARCH 2011 25

260-668201-001 MARCH 2011 27

Link Status Propagation

Ethernet Traffic Redundancy

260-668201-001 MARCH 2011 29

Line Code Selection

Trib Connectors and Cables

Auxiliary Data Interface

Auxiliary Data and NMS Functions

Alarm I/O Interfaces

260-668201-001 MARCH 2011 31

l Network management access

260-668201-001 MARCH 2011 33

Figure 1-10. Eclipse ODU 300hp on 300mm Antenna

ODU Construction and Mounting

260-668201-001 MARCH 2011 35

l Polarization is determined by the position of a polarization rotator fitted within

Item ODU 300hp ODU 300sp

ODU Cables and Cable Kits

l Insulation: foam polyethylene

260-668201-001 MARCH 2011 37

Figure 1-11. ULA Kit