Eclipse Platform Product Description Rev - 011

ECLIPSE PLATFORM
TM
PRODUCT DESCRIPTION
Rev.011
260-668139-001
Copyright & Terms of Use

July 2014
This Product Description incorporates capabilities supported under SW release 08.00
plus selected capabilities targeted for near-term release.
Copyright 2014 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,
without the prior written permission of Aviat Networks Inc.
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.
Trademarks
All trademarks are the property of their respective owners.
260-668139-001
JULY 2014
ECLIPSE PLATFORM PRODUCT DESCRIPTION
Customer Support
Sales and Sales Support:
For worldwide office locations go to http://www.aviatnetworks.com/contact-us/locations-worldwide/
For sales information, contact one of the Aviat Networks headquarters, or find your
regional sales office at http://www.aviatnetworks.com/contact-us/sales/
Corporate Headquarters
International Headquarters
North Carolina, USA
Singapore
Aviat Networks, Inc.
Aviat Networks (S) Pte. Ltd.
5200 Great America Parkway

Santa Clara
17, Changi Business Park Central 1
CA 95054
Singapore 486073
Honeywell Building, #04-01
U.S.A.
Phone: +65 6496 0900
Phone: +1 408 567 7000
Fax: + 65 6496 0999
Fax: +1 408 567 7001
Service and Technical Support:

For customer service and technical support, contact one of the regional Technical Help
Desks listed below, or for 24/7 (all day, every day of the year) there is the Global Technical Help Desk (GTHD).
The GTHD number is: +1-210-526-6345, or toll free 1-800-227-8332
within USA
l
For 24/7 access you will need your Support Assurance PIN. Without a PIN you
will still receive support, but the support process will require an additional
screening step.
After-hours calls to Paris are routed to the GTHD. The Paris number is manned
during business hours.
AVIAT NETWORKS
Americas Technical Help

Desk
EMEA Technical Help Desk
Asia Pacific Technical Help

Desk
Aviat Networks
Aviat Networks
Aviat Networks
5200 Great America Parkway

Santa Clara CA 95054
4 Bell Drive
Bldg 10, Units A&B
Hamilton International
Technology Park
Philexcel Industrial Park
Blantyre, Glasgow, Scotland
Clark Freeport Zone
G72 0FB
Philippines 2023
U.S.A.
M. Roxas Hi-way
United Kingdom
Toll Free (Canada/USA): 800
227 8332
Phone:
Phone: +63 45 599 5192
Hamilton: +44 (0) 1698 717 230
Fax: +63 45 599 5196
Phone: 210 561 7400
Paris: +33 (0) 1 77 31 00 33
Fax: 210 561 7399
Fax: +44 (0) 1698 717 204
[email protected]
[email protected]
[email protected]
Or you can contact your local Aviat Networks office. Contact information is available
on our website at: http://www.aviatnetworks.com/services/customer-support/technical-assistance/
260-668139-001
JULY 2014
Table of Contents
Copyright & Terms of Use
Customer Support
Table of Contents
Eclipse Packet Node Product Description
Introduction To Packet Node
Unique Operational Features
Capacity Maximized
Solution Optimized
MEF Certified
Platform Elements
Indoor Units
Plug-ins
DAC 3xE3/DS3M
Platform Architecture
Data Packet Plane plus Backplane
Platform Essentials
Slot Assignments
Backplane Bus Operation
Radio Frequency Units
ODUs
IRU 600
Protection Options
Power Supply
INU and ODU
INU and IRU 600
Power Consumption and INU Load Maximums
NEBS Compliance
Antennas
Link Capacity, Throughput and Latency
DPP and Backplane Traffic Assignment
STM1 + E1 Wayside Assignment
Fixed (non-adaptive) Modulation
RAC 60E/6XE Fixed-only Modulation Profiles
RAC 30v3 Modulation Profiles
Adaptive Coding and Modulation (ACM)
Adaptive Modulation (AM)
Coding
Modulation Change Criteria
Reference Modulation
1
2
4
9
10
10
12
12
14
15
15
16
21
25
25
26
27
28
29
29
30
31
33
33
34
34
41
41
42
42
44
44
44
47
48
49
50
52
54
AVIAT NETWORKS
RAC 60E/6XE Capacity, Throughput, Latency

L1 versus L2 Throughput
IFG and Preamble Suppression
TDM Latency
TDM Latency: Fixed-Only Modulation
TDM Latency: ACM
TDM Card Latency
Example Latency Calculations
Licensing
Node-based Capacity Licensing
Feature Licensing
Feature Overview
Upgrade Licenses
Plug-in Cards
Overview
NCC Plug-In
NCC User Interfaces
Compact Flash Card
FAN Plug-In
RAC Plug-Ins
RAC 30v3 Plug-In
RAC 60E/6XE Plug-Ins
DAC Plug-Ins
DAC 4x Plug-In
DAC 16xV2 Plug-In
DAC 3xE3/DS3 Plug-In
DAC 3xE3/DS3M Plug-In
DAC 1x155o, DAC 2x155o Plug-Ins
DAC 155oM and DAC 155eM Plug-Ins
DAC 2x155e Plug-In
DAC GE3 Plug-in
NCM Plug-in
NCM Front Panel
AUX Plug-In
Auxiliary Interfaces
Alarm I/O Interfaces
AUX Front Panel
NPC Plug-In
PCC Plug-In
ODUData
ODU Overview
5.8 GHz Unlicensed Band
ODU Accessories, Cables and Cable Kits
Lightning Arrestor
Waveguide Flange Data
Construction and Mounting
260-668139-001
JULY 2014
55
64
64
66
67
68
69
70
72
72
73
73
76
77
77
79
80
81
81
82
83
84
86
87
88
93
94
98
99
110
111
126
127
127
128
130
131
131
132
135
135
137
138
139
140
140
Outdoor Branching Unit

IRU 600 Data
IRU 600 Features
Frequency Bands
Radio Frequency Units (RFU)
Antenna Coupling Unit (ACU)
Version Compatibility
RFU Tx Power Calibration
Power Supply
ACU Losses
ACU Waveguide Flange Data
IRU 600 Configurations
ATPC Operation
Benefits of ATPC
ATPC Operation
Interference and ATPC
RSL and SNR Interoperation
Setting ATPC
FCC Implementation
Ethernet Operation
QoS
Storm Control
Buffer Memory Management
Link Aggregation
Layer 2 Link Aggregation
Layer 1 Link Aggregation (L1LA)
VLANs
DAC GE3 VLAN Options
Synchronous Operation
Synchronous Ethernet
IEEE 1588v2
Eclipse Clock Management for Synchronous Ethernet
Eclipse Clock Transport over Radio Links
Enhanced PDH Clock Transport: ART Re-Timing
Eclipse Native Mixed Mode Links
Ethernet OAM
Fault Management
Performance Monitoring
Protected Operation
Hardware and Radio Path Protection
Link Protection Options
Ring Protection - E1/DS1 Loop-switch
Ring Protection - Super PDH (SPDH)
SPDH Rings
SPDH Ring Operation
Ring Protection - Ethernet
142
146
146
147
149
150
151
152
152
153
154
154
158
158
158
159
159
160
160
163
163
165
166
168
170
173
178
179
179
180
181
181
184
189
190
190
191
193
195
195
196
200
202
202
204
208
AVIAT NETWORKS
ERP
RSTP
DAC/Tributary Protection
DAC/Ethernet Protection
DPP Protection
Protected/Stacked Operation
Protection Switching Criteria
Switching Guard Times
Revertive Switch Mode
Hot-standby and Diversity Switching Criteria
Dual Protection Switching Criteria
E1/DS1 Ring Protection Switching Criteria
DAC Protection Switching Criteria
NCC Protection with NPC Option
Co-path Operation
Antennas for CCDP
XDM
XPIC RAC Operating Guidelines
DPP Operation
CCDP Settings, Protection, and ATPC
Example Co-Path Configurations
CCDP Configurations
OBU Configurations
STM1+1E1 Operation
RAC 60E or RAC 30 1+0 Operation
RAC 6XE CCDP 1+0 Operation
1+1 Hot-Standby or Space Diversity Operation
Secure Operation
Secure Management
User Management
Security and Log Management
RADIUS Client
Payload Encryption
Alarms Action Operation
Orderwire Options
VoIP Orderwire
Digital Orderwire
PCR Operation
Networking and Management Tools
Addressing and Routing
Address Representation
Overhead Transport of NMS
In-band Transport of NMS
NMS Transport over 3rd Party Links
Portal
260-668139-001
JULY 2014
208
209
211
213
213
213
220
220
221
221
225
226
228
231
232
234
234
235
236
236
237
239
239
242
249
250
251
252
253
253
255
256
258
259
261
262
262
263
264
266
266
267
267
268
269
269
PC Requirements
Portal TCP and UDP Port Usage
Portal Auto Version
Portal PC to Eclipse Connection Options
Log-in Security
Eclipse Online Help
Portal Features
ProVision
Network Management
Element Configuration
ProVision Feature Summary
Diagnostics
System Summary
Event Browser
Alarms
Alarms Action
History: RACs
History: Ethernet
Performance
Link Performance
NCC Performance
E1 Trib Performance
Ethernet Performance
System/Controls
Safety Timers
Link Options
DAC Options: PDH and SDH
DAC Options: Ethernet
AUX Menu
Loopback Points
Parts Screen
Advanced Management
Index
270
271
271
271
272
272
272
273
274
274
274
277
277
278
279
280
281
282
283
284
285
285
286
289
289
289
291
294
298
299
300
301
302
AVIAT NETWORKS
Eclipse Packet Node Product Description

This product description introduces the features and capabilities of Eclipse Packet
Node with its split-mount and all-indoor transceiver options.
Updated June 2014 for Ecl i pse GA 8.
Refer to the following sections:
l
Introduction To Packet Node on page 10
Platform Elements on page 15
Link Capacity, Throughput and Latency on page 42
Licensing on page 72
Plug-in Cards on page 77
ODUData on page 135
Outdoor Branching Unit on page 142
IRU 600 Data on page 146
ATPC Operation on page 158
Ethernet Operation on page 163
Protected Operation on page 195
Co-path Operation on page 232
STM1+1E1 Operation on page 249
Secure Operation on page 253
Alarms Action Operation on page 261
PCR Operation on page 264
Orderwire Options on page 262
Networking and Management Tools on page 266
Diagnostics on page 277
Avi at Networks i s I SO90001:2008 and TL9000 Certi fi ed. F ul l

certi fi cati on means al l departments and busi ness uni ts wi thi n
Avi at Networks have been stri ctl y assessed for compl i ance to
both standards. I t testi fi es that Avi at Networks i s a certi fi ed
suppl i er of products, servi ces and sol uti ons to the hi ghest I SO
and Tel ecommuni cati on standards avai l abl e.
260-668139-001
JULY 2014
Introduction To Packet Node

Eclipse Packet Node is designed to provide comprehensive solutions for all wireless
network needs. From basic point-to-point connections through to complete backhaul
networks for broadband HSPA, WiMAX or LTE, Eclipse offers broad, flexible, cost-efficient solutions.
Refer to:
l
Unique Operational Features on page 10
Platform Elements on page 15
Unique Operational Features

A high-speed data plane in conjunction with adaptive coding and modulation (ACM)
provides highest nodal packet processing capabilities, highest link throughputs, and
low latency.
l
Support for up to six links from one compact indoor unit.
Split-mount on licensed bands 5 GHz to 38 GHz.
All-indoor on licensed bands 6 GHz to 11 GHz.
All-indoor on the 5.8 GHz FCC and Industry Canada unlicensed band.
Comprehensive support for new IP and existing TDM services with easy
migration from TDM to mixed-mode Ethernet+TDM, and ultimately to allEthernet.
Co-channel operation with XPIC, to achieve double density links in a single
frequency channel.
Ultra capacity trunked operation for throughputs to 3+ Gbit/s using c0-path
split-mount 4+0, 4+4, 8+0, or 8+8, single antenna or dual antenna (space
diversity) links.
Ethernet ring and mesh network protection with carrier-class ERP, and RSTP.
Synchronous Ethernet with clock selection and fallback options.
Extensive Ethernet traffic management capabilities, including scheduling,

policing, VLAN tagging, buffer management, storm control.
Ethernet service OAM.
Layer 1 and Layer 2 link aggregation options.
10
QPSK to 256 QAM adaptive coding and modulation (ACM) to optimize channel
usage and throughputs.
Advanced packet processing to increase Ethernet throughputs across the radio

link.
TDM ring protection mechanisms; loop-switch and ring-wrap.
Payload encryption, secure management, and RADIUS client options.
Power efficient design.
AVIAT NETWORKS
l
l
NEBs Level 3 environmental compliance.

Exceptional craft and network-wide management tools for configuration,
operation, and administration.
Figure 1-1. INU with ODU 600
Figure 1-2. INUe with IRU 600v3
Figure 1-3. Outdoor Branching Unit (OBU) with ODUs for 4+0 Operation
260-668139-001
JULY 2014
11
Capacity Maximized
Nodal IP traffic capacity extends to 3+ Gbit/s.
l
l
l
Individual airlink capacities (link capacity available for Ethernet and/or TDM)
extend to 318 Mbit/s for a 50 MHz link; 366 Mbit/s for a 56 MHz link.
L2 throughputs extend to 310 Mbit/s for 50 for a MHz link; 355 Mbit/s for a 56
MHz link (1518 byte frames).
L1 throughputs (port utilization speed) extend to 400 Mbit/s for a 50 MHz link;
463 Mbit/s for a 56 MHz link (64 byte frames).
Capacities/throughputs are doubled per frequency channel using CCDP/XPIC.
Capacities/throughputs are extended to 4x or 8x using L1LA and the OBU for
co-path CCDP, ACAP and/or ACCP channel arrangements.
Individual user interfaces support up to 1 Gbit/s (L1).
Solution Optimized
Innovative transport options coupled with solutions for sending more data over existing channel bandwidths ensure efficient, cost-effective provision of services. Capabilities include all-IP or mixed-mode operation, Ethernet-over-TDM, adaptive
modulation, CCDP/XPIC link operation, 4x or 8x trunked operation, Ethernet L1 or
L2 link aggregation, and IP synchronization solutions.
All IP
Whether from new or from existing TDM or mixed-mode installations Eclipse Packet
Node provides an uncompromising suite of features and functions for all-IP operation.
Operation is centered on a full-featured switch with features that include synchronous
Ethernet, traffic scheduling, policing, VLAN tagging, advanced buffer management,
ring protection, service OAM, and much more.
Mixed Mode
Hybrid mixed-mode operation transports native Ethernet side-by-side with TDM. It
means Ethernet can be overlaid on a TDM network to meet rapidly growing data
demands, with existing network synchronization maintained via the TDM connections. Investments in existing TDM infrastructure can be maximized, and the risks
associated with the introduction of Ethernet minimized.
Adding Ethernet to an Eclipse radio link simply requires installation of a GigE card,
at which point an operator can locally or remotely configure the capacity split between
Ethernet and PDH - Ethernet can be activated when and where needed in the network
with minimal disruption.
l
12
The ratio of link capacity assigned between Ethernet and TDM can be changed
at any time.
Changing from mixed-mode Ethernet+TDM to all-Ethernet only requires a
configuration change. All link capacity is simply directed to Ethernet, and the
TDM interface card(s) removed, leaving native Ethernet radio with capacity,
AVIAT NETWORKS
flexibility and IP intelligence the match of any IP-only radio. There is no loss of
transport efficiency when a mixed-mode link is ultimately migrated to allIP/Ethernet.
Ethernet over TDM
Legacy TDM links can be retained using Ethernet over TDM. It means wholesale
replacement of TDM links can be avoided or delayed when migrating to an all-IP backhaul.
l
Ethernet data is transported over one or more intermediary legacy NxE1/DS1,

NxDS3, or STM1/OC3 links.
Synchronization integrity is maintained via the TDM clock.
Adaptive Modulation
Eclipse AM operates as ACM (Adaptive Coding and Modulation) to provide two modulation states for each of the four modulation rates to maximize modulation step
scalability.
CCDP/XPIC
Existing channel occupancy is doubled using CCDP with XPIC (Co-Channel Dual
Polarized / Cross Polar Interference Cancellation). XPIC effectively eliminates interference from one link to the other.
Ultra Capacity Trunked Solutions
Compact and low-cost trunking to 8+0 or 8+8 becomes a reality using the Eclipse
OBU for split-mount co-path links.
Link Aggregation
Ethernet Layer 1 or Layer 2 link aggregation combines traffic from two or more copath links onto one user interface.
l
L2 link aggregation is IEEE 802.1AX compliant for static and dynamic (LACP)
use. Fixed modulation applies on radio links.
L1 link aggregation applies on radio links for adaptive or fixed modulation.
Synchronization Solutions
Eclipse supports Synchronous Ethernet or TDM-based distributed sync. ART (Airlink
Recovered Timing) or EDS (Eclipse Distributed Sync) are used to transport the clock
reference over radio links.
l
260-668139-001
Multiple clock sources can be installed under Synchronous Ethernet to provide

fallback should the primary source fail or become impaired. SSM (Synchronous
Status Messaging) is used to provide information about the quality level of
clocks throughout the network.
ART clock transport quality meets G.8262 limits.
o
ART requires RAC 60E or RAC 6XE
SSM is supported
JULY 2014
13
EDS clock transport quality meets G.823/824 limits1.

o
Operates with RAC 30v3 and legacy RACs
SSM is not supported
IEEE 1588v2 packet-based sync solutions are transported transparently.

Ethernet Ring Network Protection
Ring protection is available using industry-standard ERP or RSTP.
TDM Ring Network Protection
Two ring protection mechanisms are available for E1/DS1 networks, Loopswitch and
Super PDH.
l
Loopswitch operation employs redundant traffic streams on a bi-directional

ring. Traffic at a node is received from both redundant streams and a local
selection is made on which direction to use.
Super PDH operation uses a ring wrapping process on east/west facing primary
and secondary rings. With a failure on the primary, traffic is looped onto the
secondary ring at one side of the break point, and off at the other side, to
bypass the break.
Network Management
Craft and network management tools for comprehensive and user-friendly configuration, monitoring, administration and maintenance.
Strong Security
Extensive strong security options for management authentication, access, and payload protection.
Certification to FIPS 140-2 is scheduled.
Ecl i pse has the scal abl e capaci ty, I P network i ntel l i gence,
redundancy, and key convergence features requi red for al l
wi rel ess access and backhaul needs. There i s no need to
change up to a new pl atform duri ng the mi grati on process
meani ng upgrade ri sks are el i mi nated, upgrade costs mi ni mi zed, and val ue-add i s maxi mi zed.
MEF Certified
Eclipse Packet Node meets the requirements of MEF 9 and MEF 14 for carrier-class
Ethernet inter-operability and performance. MEF 9 specifies the User Network Interface (UNI). MEF 14 specifies Quality of Service (QoS).
1 An enhanced version of EDS is available from SW release 7.5, which operates with legacy RAC 60/6X to provide
a clock transport quality meeting G.8262 limits, with SSM support.
14
AVIAT NETWORKS
Platform Elements
This section introduces the indoor units, their architecture, plug-in cards, RFUs,
power supply requirements, and antennas. Refer to:
l
Indoor Units on page 15
Plug-ins on page 16
Platform Architecture on page 25
Radio Frequency Units on page 29
Protection Options on page 31
Power Supply on page 33
Antennas on page 41
Indoor Units
There are two indoor units, the INU and INUe (extended INU). The INU is a 1RU
chassis, the INUe 2RU.
Mandatory plug-ins are the NCC (Node Control Card) and FAN (Fan card). The
optional plug-ins comprise RAC (Radio Access Card), DAC (Digital Access Card),
NCM (Node Convergence Module), AUX (Auxiliary) and NPC (Node Protection Card).
Each ODU/RFU is connected by a single coax cable.
INU
The INU has four option slots for plug-is. It supports a maximum of three non-protected links, or one protected/diversity link and one non-protected link.
Figure 1-4. INU
INUe
The INUe has ten option slots. It supports up to six non-protected links, or three protected/diversity links.
260-668139-001
JULY 2014
15
Figure 1-5. INUe
Plug-ins
Plug-in cards enable quick and easy service customization. All cards are hot-pluggable.
Thi s secti on overvi ews the cards and thei r functi ons. F or more
detai l ed data see Plu g-in C ard s on p age 77.
Pl atform support i s mai ntai ned for al l l egacy pl ug-i n cards.
These i ncl ude RAC 60, RAC 6X, RAC 30A, RAC 3X, RAC 40, RAC
4X, DAC ES, DAC GE, DAC 16x (v1).
RACs support the radio modem function. In the transmit direction they take digital
traffic from the backplane or data packet plane and convert it to an IF signal for connection to a radio frequency unit (RFU); an ODU for split-mount operation, or
IRU600 for all-indoor. The reverse occurs in the receive direction.
l
l
l
l
One RAC/ODU or RAC/IRU 600 combination is used for a 1+0 link.

Two RAC/ODUs or two RACs with one 1+1 IRU 600 are used for hot-standby,
diversity, or co-path links.
RACs control TX switching and RX voting on protected / diversity links.
Different RACs support different capacity and modulation options, including
ACM (adaptive coding and modulation).
XPIC (cross polarization interference cancellation) RACs support CCDP (cochannel dual polarization) operation.
DACs support the user interface. They take the user traffic and convert it into a
format compatible for connection to a RAC or RACs, or to other DACs.
l
l
l
16
The GigE DAC GE3 switch features advanced QoS, VLAN tagging, link
aggregation, synchronous Ethernet, service OAM, ring protection with ERP or
RSTP, 1+1 redundancy, and buffer management.
TDM DACs support E1/DS1, E3/DS3, or STM1/OC3 connections.
Multiplexer DACs support transport of STM1/OC3 or E3/DS3 using NxE1/DS1
link connections.
Most DACs can be protected using a stacked (paired) configuration.
AVIAT NETWORKS
E1/DS1, DS3, and STM1/OC3 DACs support Ethernet-over-TDM options to

enable Ethernet transport over legacy TDM radio or leased-line links.
NCM supports the E1/DS1 loop-switch capability.

AUX (Auxiliary card) supports async or sync service-channel connections, and alarm
I/O options for connection to external devices.
NCC (Node Controller Card) provides the Node management and DC voltage conversion functions. It is a mandatory card.
l
l
It manages node operation and event collection and management.

It incorporates a router function for local and remote network management
interconnection.
Node configuration and licensing data is held in flash-memory.
Required power supply is -48 Vdc.
FAN (Fan card) provides forced-air cooling. It is a mandatory card.

NPC (Node Protection Card) provides 1+1 protection on essential NCC functions.
PCC (Power Conversion Card) supports operation from a +24 Vdc power supply.
The following figure illustrates the nodal concept, the range of plug-in cards, and their
function.
Figure 1-6. Backplane Data Bus and Plug-in Cards
260-668139-001
JULY 2014
17
RAC 60E
RAC 60E supports DPP (Data Packet Plane) operation, ACM (Adaptive Coding and
Modulation), and synchronous Ethernet clock transport using airlink recovered timing
(ART) .
The DPP port enables direct routing of Ethernet traffic to a DAC GE3; it bypasses the
backplane. Traffic, Ethernet and/or TDM, can also be directed via the backplane, as
for other Eclipse RACs.
ACM supports four dynamically switched modulation rates; QPSK, 16 QAM, 64 QAM,
256 QAM. Coding options additionally apply on each of these modulations, one for
maximum throughput, one for maximum gain, to provide a total of eight modulation
states.
l
l
l
l
l
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.
Up to four (any) of the eight modulation states offered with ACM can be
selected for use.
Modulation switching (state change) is errorless for priority traffic.
Individual ACM modulation rates can be set as fixed rates. These are
complemented by fixed-only rates for selected TDM capacities.
Node-based l i censi ng i s requi red for DPP operati on and a feature l i cense i s requi red for ACM. See Licensing on p age 72.
ETSI channel bandwidths extend from 7 to 56 MHz. ANSI from 3.5 to 80 MHz.
Air-link capacities extend to 366 Mbit/s, 100xE1, 127xDS1, 4xDS3, 2xSTM1/OC3.
The ART capability provides high quality clock transport over Eclipse links for Synchronous Ethernet networking.
l
A DAC GE3 to DAC GE3 Synchronous Ethernet connection using ART for clock
transport over radio links meets G.8262 limits.
ART consumes no traffic bandwidth.
Payload encryption is supported as a licensed option.

RAC 60E interfaces to an ODU 600, ODU 600sp, ODU 300hp, or IRU 600.
A RAC 60E can link to a RAC 6XE in non-CCDP mode.
Figure 1-7. RAC 60E
RAC 6XE
RAC 6XE adds CCDP/XPIC operation to the RAC 60E capabilities.
18
AVIAT NETWORKS
Two RAC 6XE cards are operated as a CCDP pair, either in the same INU or in separate co-located INUs, to enable two radio links to operate in the same frequency channel, one using the horizontal polarization, the other the vertical polarization. The
XPIC function between the RACs effectively eliminates cross-polarization interference.
Figure 1-8. RAC 6XE
RAC 30v3
RAC 30v3 interfaces to an ODU 600, ODU 600sp, or ODU 300hp/ep for channel bandwidths up to 28 MHz (ETSI) or 30 MHz (ANSI) for capacities of:
l
10 to 150 Mbit/s Ethernet
5x to 75xE1
4x to 100xDS1
1x, 3x, 4xDS3
1xSTM1/OC3
Where transport of E3 rates is required, the DAC 3xE3/DS3M is used in E13 mode to
multiplex E3 data to NxE1 over the radio link.
Figure 1-9. RAC 30
DAC GE3
DAC GE3 is an advanced Gigabit switch. Capabilities include synchronous Ethernet,
link aggregation, VLAN tagging, service OAM, ERP, RSTP, superior packet buffering
and queuing, 1+1 card protection.
l
Three RJ-45 10/100/1000Base-T ports
Two multi-purpose SFP ports with plug-ins for:

o
Optical LC, 1000Base-LX, 1310 nm single-mode
Optical LC, 1000Base-ZX, 1550 nm single-mode
Optical LC, 1000Base-SX, 850 nm multi-mode
Electrical RJ-45 10/100/1000Base-T
Six transport channel (TC) ports
Comprehensive QoS options
260-668139-001
802.1p mapping
DiffServ mapping (IPv4, IPv6)
MPLS Exp bits mapping
Strict priority scheduling
JULY 2014
19
Deficit Weighted-Round-Robin (DWRR) scheduling
Hybrid strict + DWRR scheduling
Eight transmission queues
Direct data packet plane (DPP) connection to RAC 60E/6XE
Policing, TrTCM with color blind and color aware options
Advanced options for VLAN tagging, including Q (802.1Q), QinQ (802.1ad),

Translation, Filtering
Synchronous Ethernet with Stratum 3 hold-over performance on timing
subsystem
L1 link aggregation on fixed or adaptive modulation links
L2 LAG, static, or dynamic (LACP)
Service OAM (802.1ag connectivity fault management, Y.1731 fault management

and performance monitoring)
Ring/ladder network protection options: ERP or RSTP
Superior burst management with advanced buffer solutions
Storm control
Jumbo frames to 10 Kbytes bi-directional
1+1 card protection
Inter-frame gap (IFG) and preamble stripping and re-insertion
RMON stats per port, channel, and queue
In-band NMS
Figure 1-10. DAC GE3
For DPP operation a DAC GE3 must be used with a RAC 60E/6XE.
NCM
The NCM (Network Convergence Module) provides an E1/DS1 loop-switch capability.
l
Data inserted into the drop tributary is transmitted on both redundant streams
to provide a bi-directional ring. Similarly data is received on both redundant
streams and a local selection is made on which direction to use.
Switching can be set for revertive or non-revertive.
Up to 5oE1/63DS1 drop/inserts per INU/INUe.
20
Ring nodes have access to two redundant traffic streams, one for data input
(insert), one for output (drop).
NCM directly supports 8 drops. Additional drops are enabled using DAC 16xV2
or DAC 4x.
Link connections can be protected; 1+1 or diversity for RAC links; 1+1 for DAC
mux card links.
NCM cards can be 1+1 protected.
AVIAT NETWORKS
For more information see Ring Protection - E1/DS1 Loop-switch on page 200.
Figure 1-11. NCM
DAC 16xV2
DAC 16xV2 supports:
l
16xE1 or 16xDS1 tributaries on compact HDR connectors.
Tributary protection.
Ethernet over unframed E1/DS1 tribs. An Ethernet-over-TDM feature license

required.
75 ohm unbalanced or 120 ohms balanced on E1 tribs.
Individual line code selection for AMI or B8ZS on balanced 100 ohm DS1 tribs.
Figure 1-12. DAC 16xV2
DAC 4X
DAC 4x supports 4xE1 or 4xDS1 tributaries on individual RJ-45 connectors.
Figure 1-13. DAC 4X
DAC 3xE3/DS3
DAC 3xE3/DS3 supports 3xDS3 tributaries on paired mini-BNC connectors1.
Figure 1-14. DAC 3xE3/DS3
DAC 3xE3/DS3M
DAC 3xE3/DS3M has four operational modes:
1E3 airlink rates are not supported. To transport E3 tribs over a radio link use the
DAC 3xE3/DS3M in E13 mode.
260-668139-001
JULY 2014
21
l
l
Normal DS3 tributary operation (as for DAC 3xE3/DS3)

E13 multiplexer mode. One or two E3 interfaces are multiplexed to an NxE1
backplane.
M13 multiplexer mode. One or two DS3 interfaces are multiplexed to an NxDS1
backplane.
34 Mbit/s transparent E3 mode for video (MPEG) transport. One or two
transparent E3 tributaries are each mapped to a 34xE1 backplane.
DS3 Ethernet mode to transport up to 43 Mbit/s Ethernet over legacy TDM
radio or leased-line links (links must support transparent DS3). An Ethernetover-TDM feature license is required.
Tribs are accessed on paired mini-BNC connectors.

Figure 1-15. DAC 3xE3/DS3M
DAC 2x155e
DAC 2x155e supports two STM1/STS3 electrical tributaries on paired BNC connectors.
Figure 1-16. DAC 2x155e
DAC 1x155o and 2x155o

DAC 1x155o supports one STM1/OC3 single-mode optical tributary on SC connectors;
DAC 2x155o supports two tributaries.
Figure 1-17. DAC 2x155o
DAC 155oM
DAC 155oM multiplexes an STM1/OC3 optical tributary to an NxE1 or NxDS1 backplane. Plug-in SFP transceivers provide access for 1310 nm single-mode (long or short
range), or 850 nm multi-mode.
It functions as a terminal multiplexer; it terminates or originates the STM1/OC3
frame. It does not support interconnection of ADMs as there is no provision to transport STM1/OC3 overheads for ADM to ADM synchronization.
22
AVIAT NETWORKS
In virtual tributary mode it transports up to 130 Mbit/s Ethernet over an STM1/OC3

link.
Options are provided for external/recovered, or internal clock sourcing.
DAC 155eM
DAC 155eM multiplexes an STM1/STS3 electrical tributary to an NxE1 or NxDS1 backplane. An SFP transceiver (included) provides the electrical interface. The connector
type is coaxial DIN 1.0/2.3, 75 ohm. Typical maximum cable length is 100m.
It functions as a terminal multiplexer; it terminates or originates the STM1/STS3
frame. It does not support interconnection of ADMs as there is no provision to transport STM1/STS3 overheads for ADM to ADM synchronization.
In virtual tributary mode it transports up to 130 Mbit/s Ethernet over an STM1/STS3
link.
Options are provided for external/recovered, or internal clock sourcing.
AUX
AUX provides synchronous and/or asynchronous auxiliary data channels, NMS porting, and alarm input and output functions. Data options are sync at 64 kbps or async
to 19.2 kbps.
NCC
The NCC is a mandatory plug-in for an INU/INUe. It performs key node management
and control functions, and provides various internal dc rails from the -48 Vdc input.
It incorporates a plug-in flash card, which holds Node configuration and license data.
Where NEBS compliance is required the external power line filter option must be
installed.
260-668139-001
JULY 2014
23
FAN
The FAN is a mandatory plug-in. There are 2RU and 1RU versions. Each is fitted with
two long-life axial fans plus monitoring and control circuits.
l
One 1RU FAN is fitted in an INU.
One 2RU FAN is fitted in the INUe (INUe will also accept two 1RU FANs).
Where NEBS compliance is required a fan filter option is installed.
NPC
NPC provides redundancy for the NCC TDM bus management and power supply functions.
Where NEBS compliance is required the external power line filter option must be
installed.
Figure 1-18. NPC
PCC
The PCC provides a voltage conversion function. It converts +24 (19 to 36) Vdc to -56
Vdc for connection to the INU -48Vdc input. -56 Vdc represents a typical float voltage
for a battery-backed -48 Vdc supply.
Load rating is 200 Watts in an air-conditioned room (max 25oC); 150 Watts in a nonair-conditioned environment.
24
AVIAT NETWORKS
Platform Architecture
The flexible customization for traffic type, traffic capacity, traffic protection, and support for advanced IP data bridging and management are key elements of Eclipse
Packet Node.
A universal modem design is used to transport data natively over Eclipse wireless
links - it does not distinguish between the type of data to be transported. Whether
Ethernet or TDM, the data is simply mapped into byte-wide frames to provide a particularly efficient and flexible wireless transport mechanism.
This section describes the data plane and backplane, INU/INUe slot location and
usage, and backplane capacity and cross-connects. Refer to:
l
Data Packet Plane plus Backplane on page 25
Platform Essentials on page 26
Slot Assignments on page 27
Backplane Bus Operation on page 28
Data Packet Plane plus Backplane

A high-performance data packet plane (DPP) is used for IP data, and a high-speed
backplane for circuit-connected TDM or TDM and Ethernet traffic.
l
The DPP is enabled through direct cable connection between the front panel
packet data port on Radio Access Cards (RACs) and associated Ethernet switch
Data Access cards (DACs).
The backplane provides a high-speed bus connections for circuit-based
connections between all Eclipse plug-in card options.
The result is optimized transport options for IP only or IP and TDM.

l
IP traffic is unconstrained by backplane maximums. One Eclipse Packet Node

supports up to six radio links, each to airlink maximums of 366 Mbit/s.
Circuit-based TDM traffic maximums extend to 100xE1, 127xDS1, 4xDS3, or
2xSTM1/OC3 per node and link. See Backplane Bus Operation below.
Capacity on individual radio links can be dedicated to IP traffic, IP + TDM, or
TDM only.
The figure below illustrates operation.

l
260-668139-001
Packet plane ports on the RAC 60E and RAC 6XE directly connect to a DAC
GE3, which in turn provides direct user access. The same RACs also access the
backplane to source/send Ethernet and/or TDM data.
Where required, customer data can also be sourced via the circuit-switched
backplane, meaning both the DPP and backplane are used to source/send
traffic.
This has special relevance where native mixed-mode IP+TDM traffic is to be
sent over a Packet Node wireless link; GigE IP traffic is sourced via the DPP,
and TDM traffic (or TDM and IP traffic) via the backplane. TDM-only links can
JULY 2014
25
be migrated to mixed-mode Ethernet+TDM or to Ethernet-only simply by

replacing plug-in cards and reconfiguring the transport options.
l
l
DPP operation requires a Node-based license.

RAC 60E/6XE support ACM (Adaptive Coding and Modulation). For more
information see Adaptive Coding and Modulation (ACM) on page 48.
Note that under DPP operation a RAC 60E/6XE and its associated DAC GE3 do not
need to be installed in the same INU.
Figure 1-19. Eclipse Packet Node DPP and Backplane
Platform Essentials
The table below lists INU and INUe platform support for:
INU
Non-protected and protected/diversity links
Slot availability for option plug-ins
Over-air data types supported
RFU options
INU supports 3 non-protected links or 1

protected/diversity and 1 non-protected link
Slots 1 to 4 support link or interface options for:
- Ethernet, E1/DS1, E3/DS3, STM1/OC3
- Auxiliary data and alarm I/O
- NPC option may only be installed in slot 4
26
AVIAT NETWORKS
INUe
INUe supports up to 6 non-protected links for:

- 1 protected/diversity and 4 non-protected links
- 2 protected/diversity and 2 non-protected links
- 3 protected/diversity links
Slots 1 to 6 support link or interface options. Slots
7 to 9 support interface options only.
Interface traffic options include:
- Ethernet, E1/DS1, E3/DS3, STM1/OC3
- Auxiliary data and alarm I/O
Slot 10 is reserved for NPC option
ODUs
All ODUs QPSK to 256QAM

ODU 600: 5 to 42 GHz ETSI and ANSI, adaptive or
fixed modulation, licensed extended Tx power
option
ODU 600sp: 6 to 23 GHz ETSI, adaptive or fixed
modulation, licensed extended Tx power option
ODU 300hp: 6 to 38 GHz, ETSI and ANSI,
adaptive or fixed modulation
ODU 300ep: 5 GHz, ETSI and ANSI, fixed
modulation only
IRU 600v3
IRU 600: QPSK to 256 QAM, 6 to 11 GHz ANSI

licensed bands, and 5.8 GHz FCC/Industry Canada
unlicensed band
Fixed or adaptive modulation, 1+1 optimized
Two variants: V2 and V3. Both incorporate a Tx
coaxial switch for HSB and MHSB/SD operation.
V2 is 3RU; V3 is 2RU.
Slot Assignments
The table below shows INU and INUe slot assignment options.
INU/INUe
Slots
INU
Slots 1, 2, 3, 4 are universal: any RAC, DAC,

NCM or AUX plug-in
If NPC is required it must be installed in slot 4
NCC and FAN slots are dedicated
For protected operation the RAC/RAC,
RAC/DAC, or DAC/DAC pairings can be installed
in any of the universal slots
260-668139-001
JULY 2014
27
INU/INUe
Slots
INUe
Slots 1, 2, 3, 4, 5, 6 are universal: any RAC,

DAC, NCM or AUX plug-in
Slots 7, 8, 9 are restricted: any DAC, NCM, or
AUX, except DAC 155oM/eM and AUX where
NMS access is required1
Slot 10 is reserved for NPC option
NCC and FAN slots are dedicated - the INUe is
supplied standard with a single 2RU FAN,
though accepts two 1RU FANs
RAC/RAC, or RAC/DAC protected pairings must
be installed in the positions indicated by the
arrows
For protected DACs, NCMs, the protection
partners can be installed in slots 1 to 9, except
for the DAC 155oM/eM where NMS access is
needed, in which case install only in slots 1 to 6

All cards (except PCC) plug into a backplane, which carries a high-speed parallel bus
to provide the cross-connect and end-to-end circuit connectivity for traffic channels,
auxiliary data, NMS, and protection switching.
The backplane is set to operate in one of the following bus sizes:
l
Nx2 Mbit/s / NxE1
Nx1.5 Mbit/s / NxDS1
NxE3
NxDS3
Nx150 Mbit/s / NxSTM1/OC3
NxSTM1 + E1
These options enable node configuration for Ethernet, NxE1, NxDS1, NxE3, NxDS3,
NxSTM1/OC3, or NxSTM1 + E1. Ethernet operation can be with or without companion
TDM traffic.
The traffic-handling capacity limit of the backplane for each rate is:
l
204 Mbit/s for an Nx2 Mbit/s or Nx1.5 Mbit/s setting
300 Mbit/s for an Nx150 Mbit/s setting
100 x E1 (204.8 Mbit/s)
128 x DS1 (197.6 Mbit/s)
6 x DS3 (268 Mbit/s)
2xSTM1/OC3 (311 Mbit/s)
2xSTM1 + E1 (312 Mbit/s)
1Internal (backplane bus) NMS access is only provided on slots 1 to 6.
28
AVIAT NETWORKS
DPP capaci ty i s not constrai ned by backpl ane maxi mums. Ethernet data through a Packet Node extends to 2 Gbi t/s, wi th i ndi vi dual RAC 60Es or RAC 6XEs confi gured for over-ai r capaci ti es
to 366 Mbi t/s.
Protected RACs are i nterconnected by a di versi ty bus to support the errorl ess Rx path swi tchi ng (voti ng) capabi l i ty. Thi s
di versi ty bus operates i ndependentl y of the backpl ane bus and
i s not capaci ty dependent. (The di versi ty bus connecti ons are
why RACs must be i nstal l ed i n sl ot pai ri ngs 1&4, 2&5, 3&6 on
an I NUe).
Where a mix of different rates is required, such as NxE1 and STM1/OC3, a multiplexer
DAC enables STM1/OC3 mapping to an E1-configured bus. In this way E1 and
STM1/OC3 interfaces are supported on the same INU without the need for a standalone SDH mux.
E3 user traffic is transported over the radio as 16xE1 using the DAC 3xE3/DS3M E13
mux option.
Where Ethernet data is transported on the backplane, capacity is assigned in 2
Mbit/s, 1.5 Mbit/s or 150 Mbit/s steps to align with the capacity needed for E1, DS1 or
STM1/OC3 waysides.
Radio Frequency Units

All RFUs incorporate the latest technology to optimize both system performance with
low power consumption and market-leading reliability.
l
ODUs are installed for split-mount operation.
Rack-mounting IRU 600s are installed for all-indoor operation (ANSI only).
Ambi ent temperatures must not exceed 55 0 C (131 0 F ).
ODUs
There are four variants: ODU 600, ODU 600sp, ODU 600T, ODU 300hp:
l
ODU 600 for high power and licensed flexible power mode (FPM) operation on
ETSI and ANSI bands 5 to 42 GHz. Also for operation on USA and Canada 5.8
GHz unlicensed band (ISM band).power
ODU 600sp for standard and licensed flexible power mode (FPM) operation on
ETSI bands 6 to 23 GHz.
ODU 600T for use with the OBU (Outdoor Branching Unit). See Outdoor
Branching Unit on page 142.
ODU 300hp for ETSI and ANSI bands 6 to 38 GHz, high power.
Channel bandwidths range from 3.5 to 80MHz depending on the ODU, the bandplan, and the capacity/modulation option selected.
260-668139-001
JULY 2014
29
ODUs are band specific and supplied with diplexers for Tx Hi or Tx Lo working.
The one exception is ODU 600T at 6 GHz and above where Tx Hi or Tx Lo is
user selectable.
ODUs for 5.8 to 42 GHz are designed for direct-antenna mounting, but can be
remote mounted using a flexible waveguide antenna connection.
ODU 600 for 5 GHz requires remote mounting, with coax cable connection to its
antenna.
ODUs connect to its indoor unit by coaxial cable. Cable runs can be up to 300m
/1,000 ft.
ODUs are environmentally hardened to withstand extremes of temperature and
driven rain/snow.
Equal-loss and unequal-loss direct-mounting couplers are available for hotstandby and frequency diversity single antenna operation (5.8 to 42 GHz).
A direct-mount unit (XDM) supports two ODUs for CCDP/XPIC operation (6 to
42 GHz).
The OBU supports four ODU 600Ts for CCDP/XPIC, ACAP, and/or ACCP
operation (5 to 11 GHz).
All ODUs include an internal lightning surge suppressor.
For more information see ODUData on page 135.

Figure 1-20. ODU 600 Direct-Mounted on 300 mm (1ft) Antenna
IRU 600
The IRU 600 is a compact rack-mounted transceiver unit for co-location with an
INU/INUe as an all-indoor installation.
Operation is 1+1 optimized. It comprises one or two RFUs (radio frequency units),
and a filter-based ACU (antenna coupler unit).
l
30
The filter-based ACU design supports paired and unpaired Tx/Rx frequency
splits and incorporates an optional expansion port to allow other radio links
onto its waveguide feed for co-path operation.
AVIAT NETWORKS
Protected/diversity options include:

l
1+1 hot-standby
1+0 hot-standby-ready
Space diversity (dual antennas) with common or split Tx
Frequency diversity (single antenna) or frequency diversity with space diversity

(dual antennas)
IRU 600 may also be used for 1+0 repeater (back-to-back) operation where the links
may be in the same or different bands, and for 2+0 co-path ACCP, ACAP, or
CCDP/XPIC operation.
Operation encompasses ANSI L6/U6, 7/8, 10, 11 GHz licensed bands, and the FCC /
Industry Canada 5.8 GHz unlicensed (ISM) band.
IRU 600 is only supported from a RAC 60/6X, or RAC 60E/6XE.
For more information see IRU 600 Data on page 146.
Figure 1-21. IRU 600v2 High Power
Figure 1-22. IRU 600v3
Protection Options
This section introduces the protection options for link, interface, network, and platform. For more detailed information see Protected Operation on page 195.
Link/Path Protection
Hot-standby, space diversity, frequency diversity, or dual protection options are available.
l
All RACs and their companion ODU or IRU 600 are protectable.
Rx path switching is hitless/errorless; Tx switching is not hitless. Refer to:

l
Service Restoration Times for Hot Standby and Diversity on page 225
Dual Protection Switching Criteria on page 225
A remote Tx switch is forced in the event of a silent Tx failure. See Silent Transmitter
Switching on page 223.
260-668139-001
JULY 2014
31
Interface Protection
Ethernet, E1/DS1, E3/DS3 and STM1/OC3 interfaces can be hot-standby protected
using paired (stacked) DACs.
The protectable DACs are DAC GE3, DAC 16xV2, DAC E3/DS3, DAC 3xE3/DS3M,
DAC 2x155o, DAC 2x155e, DAC 155oM, DAC 155eM.
Y-cable and straight cable options are available to connect paired DACs to external
equipment.
For more information, see:
l
DAC/Tributary Protection on page 211.
DAC/Ethernet Protection on page 213.
Network Data Protection

l
Ethernet ring network protection is supported on DAC GE3 using ERP (ITU-T
8032v2 Ethernet Ring Protection) or RSTP (IEEE 802.1w).
Ethernet data redundancy is supported on L1 and L2 link-aggregated links
(DAC GE3).
PDH ring protection is supported by an E1/DS1 loopswitch capability, or a ringwrap Super PDH (SPDH) option.
Ethernet Ring and Mesh Networks

ERP uses standard Ethernet bridging and OAM protocols and OAM automatic protection switching (APS) messaging to provide a fast-acting protection mechanism for
ring networks.
RSTP uses a development of the spanning tree protocol (STP) to prevent network
loops and provide path redundancy.
For more information see Ring Protection - Ethernet on page 208.
Ethernet Link Aggregation (N+0 Protection)
Traffic redundancy is supported on co-path Ethernet links using L1 or L2 link aggregation. If one link fails its traffic is recovered on the remaining link or links. While the
reduced bandwidth may result in some traffic loss for low-priority traffic, appropriate
QoS settings should ensure security for all higher priority traffic.
For more information see Link Aggregation on page 168.
PDH Ring Protection
Eclipse supports two E1/DS1 ring protection mechanisms, loop-switch and SPDH.
l
32
The loop-switch function uses the NCM to configure a bi-directional redundant

ring with a hitless switching capability. Rings can be configured using RACs,
and PDH/SDH mux DACs.
SPDH uses a ring-wrap mechanism formed on east/west facing RAC/RAC or
RAC/DAC 155oM combinations. Switching is not hitless.
AVIAT NETWORKS
For more information see Ring Protection - E1/DS1 Loop-switch on page 200, or Ring
Protection - Super PDH (SPDH) on page 202.
Platform Protection
Platform management functions provided by the NCC are protected using the NPC
option. It backs up essential backplane bus and power supply functions.
See NCC Protection with NPC Option on page 231.
Power Supply
Eclipse is designed to operate from a -48Vdc power supply. A +24 Vdc voltage
cooption is available.
All Eclipse power supply units are polarity protected - an incorrect supply connection
will not cause damage to the units or cause a fuse to blow.
DC power supplies for Eclipse must be UL or IEC compliant for SELV (Safety Extra
Low Voltage) output (60Vdc maximum limited).
Voltage changes due to the regulation of the power supply must not exceed a changerate (linear variation slope) of 7 V/ms, as specified in TSI EN 300 132-2 V2.4.6.
Refer to:
l
INU and ODU on page 33
INU and IRU 600 on page 34
Power Consumption and INU Load Maximums on page 34
NEBS Compliance on page 41
INU and ODU

INUs and ODUs are designed to operate from a -48Vdc power supply (+ve ground)
but will operate to specification over a voltage range of -40.5 to -60Vdc. The ground
pin (dc return pin) on the NCC and NPC D-sub 2W2 power connector is connected to
chassis ground.
Power for the ODU(s) is provided over the RAC-ODU cable.
Operation from a +24 Vdc supply (+19 to +36 Vdc) is achieved using the optional
PCC plug-in.
l
260-668139-001
The PCC converts +24 Vdc to -56 Vdc for connection the NCC (or NPC) -48 Vdc
input (-56 Vdc represents a typical float voltage for a -48 Vdc battery bank).
The -ve pin (dc return pin) on the PCC power input connector is isolated from
chassis ground - it is grounded by the power-supply ground.
Two PCCs are required for NCC + NPC operation - one for the NCC, one for the
NPC.
JULY 2014
33
The PCC is load-rated to 200 Watts in an air-conditioned environment

(ambient max 25oC). See Power Consumption and INU Load Maximums on
page 34.
For more information see PCC Plug-In on page 132.
INU and IRU 600

As for the ODUs, -48Vdc (+ve ground) and +24 Vdc (-ve ground) power options are
supported by the IRU 600 RFUs.
l
The standard power IRU 600v2 is powered over the RAC-RFU cable (in the
same way as an ODU). For +24 Vdc operation the PCC plug-in is required (two
required if an NPC is installed).
The high power IRU 600v2 is powered by its RAC and additionally through a
front-mounted D-sub 2W2 DC connector on each of the RFUs to provide the
additional current needed for high power operation. The connector is the same
type as used on the NCC and NPC.
o
High power RFUs incorporate a wide-mouth +/- 21-60 Vdc voltage converter
unit (the +ve and -ve pins on the 2W2 power connector are isolated from
chassis ground). This means that no additional dc-dc converter is required
for the high power RFU - but a PCC is still required for the INU (two
required if an NPC is installed).
For IRU 600v3 both standard and high Tx power RFU operation is supported from
the same RFU under software/license control.
l
Power for standard and high Tx power operation is provided via the INU cable.
For +24 Vdc operation the PCC plug-in is required (two required if an NPC is
installed).
Power consumption is reduced when Tx power output is lowered. Applies to
both ATPC and manual control of Tx power.
The PCC is rated to 200 Watts at a maximum ambient of 45oC. Not more than four
ODUs or three IRU 600 RFUs, plus any combination of RACs and DACs, can be supported from an INUe powered from +24 Vdc. See Power Consumption and INU Load
Maximums on page 34.
Power Consumption and INU Load Maximums

Total power consumed is dependent on the number and type of plug-in cards, the
number and type of ODU(s) or IRU 600 RFUs, plus for the ODUs, the frequency band.
INU loading maximums (the number and type of RACs and DACs that can be
installed in an INU), are determined by the load capacity and temperature limits of
the DC converter in the NCC, which supplies various DC rails to the plug-in cards.
l
34
ODUs, IRU 600s and FANs are not powered via the NCC converter circuit,
meaning the ODU and IRU 600 type does not impact INU link loading. Their
DC supply is taken from the -48 Vdc power supply input connector.
AVIAT NETWORKS
However, if a PCC is installed for +24 Vdc operation, the INU cards and associated
ODUs or IRU 600s are supplied from the PCC, meaning PCC power limits are determined by the INU cards and by the number and type of ODUs or IRU 600s fitted.
A PCC should always be installed to receive maximum FAN cooling. This means
it should be installed in the immediate FAN-side slots in an INU/INUe.
Power Consumption
The table below lists nominal power consumption figures for Eclipse cards. Use these
together with the ODU or IRU 600 consumption figures in the following tables to
determine total nodal power consumption.
Data is also provided to determine ODU cable power dissipation. Data is for CNT 400
and RG-8 type cables. For CNT 300, increase dissipation figures by 40%.
Nominal power consumption for the ODU 300ep (5 GHz) is 50 w.
Power consumption figures are for a -48 Vdc supply voltage at normal room ambients.
Plug-in Cards
Table 1-1. Typical Plug-in Power Consumption
Item
Consumption
RAC30v3
8W
RAC 60E
12W
RAC 6XE
17W
DAC 16xV2, 4x, 3xE3/DS3, 3xE3/DS3M
2.5W
DAC 2x155o, 2x255e, 155oM, 155eM
4W
DAC GE3
13W
NCM
10W
NCC
11W
NPC
8W
AUX
1W
FAN 1RU
2W
FAN 2RU
2W
ODU 600
ODU 600 power consumption figures apply to both standard and high power operation.
Table 1-2. ODU 600 Power Consumption
BAND
Average Power Max Power ConConsumption

sumption W
W
6 GHz
50.2
59.2
7 GHz
49.5
59.4
8 GHz
49.9
59.6
260-668139-001
JULY 2014
35
BAND
Average Power Max Power ConConsumption

sumption W
W
11 GHz
45.0
59.7
13 GHz
38.3
50.0
15 GHz
37.8
46.4
18 GHz
39.2
44.9
23 GHz
40.0
43.8
26-42 GHz
35.0
38.0
ODU 300hp
Table 1-3. ODU 300hp Power Consumption
BAND
Average Power
Consumption W
Max Power Consumption W
6 GHz
40.7
45.7
7 GHz
42.8
48.6
8 GHz
43.1
48.5
10 GHz
41.5
44.01
11 GHz
34.6
38.0
13 GHz
30.9
37.1
15 GHz
29.8
35.9
18 GHz
22.2
25.6
23 GHz
24.3
27.0
28 GHz
25.0
28.1
32 GHz
25.1
27.5
38 GHz
29.2
31.6
ODU Cable Power Dissipation

The data provided is for CNT 400 and RG-8 type cables. For CNT 300, increase dissipation figures by 40%.
Figure 1-23. Nominal ODU cable Power Dissipation at -48v
36
AVIAT NETWORKS
IRU 600v2
The table below lists typical power consumption figures for IRU 600v2.
For a standard power RFU, power is provided via its RAC - RFU cable (in the
same way as an ODU).
For a high power RFU, power is supplied via its RAC cable and additionally by
a front-mounted DC connector.
Table 1-4. Nominal IRU 600v2 Power Consumptions

Configuration
Power Sourced
from INU
Power Sourced
from External
DC Connector
Total DC
Power
1+0 Standard Power (1xRFU)
52W
N/A
52W
1+0 High Power (1xRFU
52W
38W
90W
2+0 or 1+1 FD, Standard Power (2xRFU),

IRU 600, IRU 600v2
104W
N/A
104W
2+0 or 1+1 FD, High Power (2xRFU)
104W
76W
180W
1+1 MHSB or SD, Std Power (2xRFU)
104W
N/A
104W
1+1 MHSB or SD, High Power (2xRFU)
104W
76W
180W
1+1 MHSB or SD, Power save Mode (Offline Tx Mute), Std Power (2xRFU)
82W
N/A
82W
1+1 MHSB or SD, Power Save Mode (Offline Tx Mute), High Power (2xRFU)
82W
42W
124W
IRU 600v3
The table below lists power consumption figures for the 5.8/6 GHz band for QSPK
operation at maximum Tx power settings.
l
A common RFU is used for standard and high power modes. High power is
enabled through feature license. See Licensing on page 72.
For both standard power and high power operation, DC power to the RFU(s) is
provided from its INU/INUe via the RAC - RFU cable.
There is a small power consumption reduction on higher modulations (higher
modulations have reduced Tx power output maximums).
Power consumption is reduced as Tx power is reduced (either when enabling
ATPC or when manually configuring Tx power to a value below the maximum
capability).
o
High power and standard power operation realizes power consumption

savings of approximately 5W when operated 3dB below maximum power,
and approximately 15 W when operated 10dB below.
Table 1-5. Nominal IRU 600v3 Power Consumptions for QPSK at Max Tx Power
Configuration
5.8/L6
Typical
5.8/6
GHz
Maximum
1+0 Standard Power (1xRFU)
58W
63W
1+0 High Power (1xRFU)
63W
68W
2+0 or 1+1 FD, Standard Power (2xRFU)
116W
126W
2+0 or 1+1 FD, High Power (2xRFU)
126W
136W
260-668139-001
JULY 2014
37
Configuration
5.8/L6
Typical
5.8/6
GHz
Maximum
1+1 MHSB or SD, Std Power (2xRFU)
116W
128W
1+1 MHSB or SD, High Power (2xRFU)
126W
138W
1+1 MHSB or SD, Power save Mode (Offline Tx Mute), Std Power
(2xRFU)
106W
115W
1+1 MHSB or SD, Power save Mode (Offline Tx Mute), High Power
(2xRFU)
111W
118W
Node Card Maximums

Figures are provided for the INUe and INU.
INUe Loading Rules

These loading rules apply from SW release 5.04, when used with standard and highoutput NCC and NPC cards.
High INUe loading
Cooling fan operating logic allows high card loadings, together with maximum ambients to 55oC (131oF), or 45oC (113oF).
l
Maximized INUe loading requires installation of an NPC, and must be fitted

where specified below.
o
The NPC provides power supply load sharing with the NCC, allowing the
overall loading to be increased. Should the NPC fail, airflow from the 2RU
FAN is increased to compensate.
Extended FAN failure/impairment detection is included. For example, an alarm

will be raised on a reduction in fan speed (RPM), such as can occur as a result
of bearing wear/friction.
The loading maximums are designed to ensure systems will continue to operate
correctly in the event of failure of either the NCC or NPC.
Extended INUe loading

Extended loading is available through installation of high-output NCC and NPC
cards. These cards have part numbers of EXN-003 and EXS-002 respectively.
l
l
These cards are required where node loading exceeds 120W.

The prior NCC and NPC cards, those with part numbers EXN-002 and EXS-001
respectively, must only be retained where node loadings do not exceed 120W.
CAUTION:When planning the number and type of cards to be installed,
the following rules must be observed. They apply retrospectively (back
to software release 5.04).
INUe Loading Rules for Operation up to 55C (131F)

The following loading rules must be followed when dimensioning the total power consumption of an INUe required to operate in ambient temperatures up to 55C (131F):
l
38
If the total power consumption of all cards installed exceeds 85W, an NPC must
be fitted, a 2RU FAN card must be fitted, and 5.04 or later SW loaded.
AVIAT NETWORKS
With this configuration confirmed (NPC + 2RU FAN + 5.04 SW or later) the
maximum INUe loading enabled is:
o
12oW with NCC EXN-002 and NPC EXS-001.
125W with high-output NCC EXN-003 and NPC EXS-002.
The installed total of DAC GE3 cards must not exceed four.
If an earlier version of SW is loaded, the maximum INUe loading allowed is 85

Watts. This applies whether or not an NPC and 2RU FAN are fitted.
CAUTION:55C (131F) operation does not apply to the PCC. Operational ambient temperatures with a PCC installed must not exceed
45 0C (113 0F).
INUe Loading Rules for Operation up to 45C (113F)

The following loading rules must be followed when dimensioning total power consumption of an INUe operating in ambient temperatures that do not exceed 45C
(113F):
l
If the total power consumption of all cards installed exceeds 85W, an NPC must
be fitted, a 2RU FAN card must be fitted, and 5.04 or later SW loaded.
With this configuration confirmed (NPC + 2RU FAN + 5.04 SW or later) the
maximum INUe loading enabled is:
o
12oW with NCC EXN-002 and NPC EXS-001.
146W with high-output NCC EXN-003 and NPC EXS-002.
The installed total of DAC GE3 cards must not exceed four.
If an earlier version of SW is loaded, the maximum INUe loading permitted is

100W. This applies whether or not an NPC and 2RU FAN are fitted.
Typical compliant loading examples are shown below with 5.04 SW or later (48Vdc
power source).
Table 1-6. NCC EXN-002 with EXS-001, 45C (113F)
Total Watts:
119
118
120
120
Qty RAC 60E
Qty RAC 6x
Qty DAC 16xV2
Qty AUX
Qty NPC
Qty NCC
Qty FAN
Qty DAC GE3
Table 1-7. NCC EXN-003 with EXS-002, 45C (113F)

Total Watts
139
135
132
146
Qty RAC 60E
Qty RAC 6XE
Qty DAC 16xV2
Qty AUX
260-668139-001
JULY 2014
39
Qty NPC
Qty NCC
Qty FAN
Qty DAC GE3
INU Loading Rules

The INU (1RU) chassis should not be loaded above the follow limits:
l
65 watts total for operation up to 45C
50 watts total for operation up to 55C
El evated ambi ent temperatures shoul d be avoi ded. Ambi ent

maxi mums must not be exceeded. Over-temperature operati on
i s a pri mary factor affecti ng l ong term component rel i abi l i ty.
The ambi ent temperature i s the ai r temperature i n the i mmedi ate operati ng envi ronment of the chassi s, whi ch i f i nstal l ed
i n a rack, i s the ambi ent appl yi ng to i ts l ocati on wi thi n the
rack.
PCC +24 Vdc Operation

The PCC is for use with standard +24 Vdc (-ve grounded) battery-backed power supply systems.
l
The PCC +ve and -ve input terminals are isolated from chassis (ground). The ve input is grounded by the -ve grounded power supply connection.
The PCC 20A fuse is fitted in the +ve input. It is a PCB mount type and is not
field replaceable.
Reverse polarity protection is provided. The PCC will automatically recover from
a reverse polarity connection - the fuse will not blow. Over temperature thermal
protection is included.
Load rating is 200 Watts in an air-conditioned room (ambient max 25oC). This
should be de-rated to 150 Watts for non-air-conditioned.
l
l
40
Operational ambient temperature must not exceed 450C (1130F).

The PCC conversion efficiency is nominally 90%. To determine the power
consumed by the PCC, use a figure of 110% of the power consumed by the
INU/INUe cards and RFUs (ODU / IRU 600).
When installed in an INUe the INUe should be fitted with the 2RU FAN module
as it provides almost double the air flow of the 1RU FAN modules.
The PCC can be plugged into any INU/INUe option slot, but should always be
installed next to the FAN card to get best air-flow cooling.
Where an NPC is fitted, two PCCs are required, one for the NCC, one for the
NPC. This means an INUe must be used for NCC + NPC operation.
Note that it is not connected to the INU backplane and its function is not
monitored within Portal.
AVIAT NETWORKS
NEBS Compliance
For NEBS compliance an external DC power line filter option must be installed with
an INU/INUe . It ensures Eclipse meets EMI requirements specified within Telcordia
GR-1089-CORE, Issue 4, June 2006.
The filter is 1RU tall, 140mm wide (5.5), and is supplied as a kitset comprising the filter unit, bracket for left or right side rack mounting, and a short 2W2 to 2W2 cable for
connecting the filter unit to the NCC or NPC -48 Vdc inputs.
l
Where an NPC is fitted, two filter units are required, one for the NCC, one for
the NPC.
The standard power cable supplied with an INU or NPC is re-used as the power
input cable for the filter unit.
The high power IRU 600 is NEBS compliant - it does not require the power line filter
unit.
Figure 1-24. Power Line Filter with Bracket
Antennas
Antennas for ODU direct mounting are available in diameters from 0.3m (1ft) to 1.8m
(6ft), depending on the frequency band. These antennas are high performance, low profile shielded types and are supplied complete with a customized ODU mounting collar
and feed-point.
A polarization rotator is included within the antenna collar, and direct-mounting
equal or unequal loss couplers are available for single antenna protected operation.
Antennas for direct-mount CCDP/XPIC operation are from the Eclipse Edge-series.
These have a circular waveguide feed-point and no ODU mounting collar. Instead the
XPOL Direct Mount (XDM) attaches to the back of the antenna, and the two ODUs
attach directly onto the XDM.
ODUs can also be used with standard antennas via a remote-mount kit and flexible
waveguide.
Antennas for use with the IRU 600 are industry-standard, waveguide-port, high-performance types.
Antenna mounts are designed for use on industry-standard 115 mm OD (4.5 inch)
pipe-mounts.
260-668139-001
JULY 2014
41
Link Capacity, Throughput and Latency

Link capacity, throughput and latency figures are provided for RAC 60E and RAC
6XE.
Link capacity figures are provided for RAC 30v3
Radio link (airlink) capacity and bandwidth options are listed for fixed modulation (RAC 60E/6XE, RAC 30v3) and adaptive modulation operation (RAC
60E/6XE).
l
Airlink capacity is a measure of the payload capacity for Ethernet and/or TDM
traffic.
Ethernet throughput and latency is listed for fixed and adaptive modulation operation using RAC 60E/6XE.
l
Data is provided for 64 byte and 1518 byte frames at L1 and L2, with and
without payload encryption.
IFG and Preamble suppression applies on radio link connections between DAC
GE3s to significantly improve throughput on small frame sizes.
TDM latency is listed for fixed and adaptive modulation operation, with and
without payload encryption, using RAC 60E/6XE.
Whi l e thi s secti on focuses on i ndi vi dual l i nk capaci ti es and

data throughputs, Ecl i pse supports techni ques to aggregate
(combi ne) the capaci ty of two or more co-path l i nks. F or more
i nformati on see Link Aggregat ion on p age 16 8, and C o-p at h Op erat ion on p age 232.
Refer to:
l
DPP and Backplane Traffic Assignment on page 42
Fixed (non-adaptive) Modulation on page 44
Adaptive Coding and Modulation (ACM) on page 48
L1 versus L2 Throughput on page 64
For fiber links using the DAC 155oM, refer to DAC 155oM and DAC 155eM Plug-Ins on
page 99 .
DPP and Backplane Traffic Assignment

RAC 60E/6XE support interconnection to/from other plug-ins via the DPP (Ethernet
only) and backplane (Ethernet and/or TDM).
l
42
RAC 60E/6XE support both fixed and adaptive modulation profiles.
AVIAT NETWORKS
For RAC 30v3 the backplane (Ethernet and/or TDM) is the only interconnection
medium to/from other plug-in cards.
l
RAC 30v3 supports fixed modulation only.
DPP Traffic Assignment

DPP traffic bypasses the INU backplane to support aggregate Ethernet capacities to 1
Gbit/s or higher. This is in addition to the backplane maximums.
l
DPP capacity is assigned directly between a RAC 60E/6XE and its companion
DAC GE3 in 1.5 Mbit/s, 2 Mbit/s, 45 Mbit/s, or 155 Mbit/s multiples.
o
The capacity multiple in use is determined by the bus-size setting.
Traffic maximums are determined by the RAC airlink capacity - they are not
constrained by the backplane bus maximums.
o
ETSI airlink maximum is 366 Mbit/s (56 MHz, 256 QAM).
ANSI airlink maximums are 320 Mbit/s (50 MHz, 256 QAM) or 365 Mbit/s
(80 MHz, 256 QAM).
Multiple links can be configured from one INU/INUe, each to their airlink
maximums.
o
Co-path links can be operated as CCDP/XPIC, ACAP, or ACCP pairs. See Copath Operation on page 232 .
Traffic capacity on co-path links can be link aggregated to a common user

interface. See Link Aggregation on page 168.
Backplane Traffic Assignment

Backplane bus-size settings determine the backplane fabric and the capacity multiples
used to configure a connection capacity. The settings are Nx2 Mbit/s / E1, Nx1.5
Mbit/s / DS1, NxDS3 (TDM only), or Nx155 Mbit/s / STM1/OC3.
One INU/INUe supports backplane maximums of:
l
204 Mbit/s/100xE1 for an Nx2 Mbit/s/E1 backplane selection
198 Mbit/s/128xDS1 for an Nx1.5 Mbit/s/DS1 backplane selection.
311 Mbit/s/2xSTM1 for an Nx155 Mbit/s/STM1 backplane selection.
Mixed Mode DPP Plus Backplane Traffic Assignment

For hybrid mixed-mode Ethernet+TDM links, DPP traffic (Ethernet only) and backplane traffic (TDM and/or Ethernet) is assigned to a RAC 60E/6XE payload.
l
260-668139-001
Link capacity assignment between Ethernet and TDM traffic is fully scalable
depending on the backplane bus-size setting. For example, for each E1 or DS1
assigned via the backplane, 2 Mbit/s or 1.5 Mbit/s respectively is taken away
from the capacity available on the DPP.
RAC capacity not assigned to backplane connections is default assigned to the
DPP.
Mixed mode operation is supported under both fixed and adaptive modulation
profiles.
JULY 2014
43
STM1 + E1 Wayside Assignment

STM1+E1 and 2xSTM1+E1 modulation profiles are supported on a backplane bus-size
setting of 155 Mbit/s.
l
1xSTM1+E1 is a 27.5 MHz/128 QAM option for RAC 60E/6XE and RAC 30v3.
2xSTM1+E1 is a 55 MHz/128 QAM option for RAC 60E/6XE.
Operation applies to:

l
1+0 or 1+1 hot-standby or space diversity operation.
DAC 155o, 2xDAC 155o, or 2xDAC155e for STM1 trib access.
Paired DACs for 1+1 STM1 trib protection.
DAC 4x for E1 wayside trib access.
A maximum of two STM1+E1 links or one 2xSTM1+E1 link can be configured from one
INU/INUe.
When STM1+E1 is enabled:
l
A wayside circuit option is enabled in the Portal circuits screen.
Auxiliary data circuits cannot be configured if the wayside circuit is configured.

o
Auxiliary data circuits can be configured providing the wayside E1 is not

configured.
If auxiliary data circuits (one or more) are configured, a wayside E1 cannot

be configured.
For more information see STM1+1E1 Operation on page 249.
Fixed (non-adaptive) Modulation

This section applies to the fixed-only modulation profiles supported by RAC 60E/6XE
and RAC 30v3.
l
Use the RAC 60E or RAC 6XE for link capacities to 366 Mbit/s, 100xE1,
127xDS1, 4xDS3, 1xOC3, 1xSTM1+E1, 2xSTM1+E1, on channel bandwidths to
55 MHz (ETSI) or 80 MHz (ANSI).
Use the RAC 30v3 for link capacities to 150 Mbit/s, 75xE1, 100xDS1, 4xDS3,
1xSTM1/OC3, on channel bandwidths to 28 MHz (ETSI) or 30 MHz (ANSI).
Refer to:
l
Fixed (non-adaptive) Modulation on page 44
RAC 30v3 Modulation Profiles on page 47
RAC 60E/6XE Fixed-only Modulation Profiles

Modulation profiles below are for fixed-only operation (not ACM capable). These supplement the ACM modulation profiles, any of which can also be selected for fixed
(single) modulation operation.
44
AVIAT NETWORKS
Fixed-only profiles are used where:

NxDS3, STM1 or OC3 transport is required.
Operation on historic Eclipse profiles is required (profiles not supported under

ACM).
Lower link latency is required (Ethernet latency using non-ACM modulations is

lower than for near-equivalent adaptive modulation options).
Ethernet Throughput and Latency, and Max TDM

Latency figures are provided with and without payload encryption enabled.
The additional latency when enabled is independent of the encryption scheme
selected (128, 192, 256 CCM).
The additional latency when enabled is independent of frame size - with PE

enabled the additional latency is the same for all frame sizes.
Figures are with shaper-mode set for maximum throughput.

The shaper mode determines the process used to shape Ethernet traffic to radio
link bandwidth.
Maximum Throughput uses a dynamic shaper to achieve maximum

Ethernet throughput, but at the expense of true strict priority when traffic
loading for high priority traffic is at or near maximum.
Static ensures strict priority is maintained under all traffic load conditions,
but at the expense of a slightly lower throughput.
n
To estimate Ethernet throughputs with static mode selected, reduce L1

and L2 throughputs by 0.5% for 64 byte frames, 3.5% for 1518 byte
frames.
Maximum throughput is the default selection.
The tables also show the maximum TDM tribs supported by each profile.
TDM circuits are mapped via the backplane bus, unlike Ethernet which can be
mapped via the DPP and/or the backplane.
The total TDM circuits configured on one radio link cannot exceed backplane
maximums of 100xE1, 127xDS1, 4xDS3, 2xSTM1/OC3.
For TDM latency figures see TDM Latency on page 66.
Table 1-8. Typical Data for Fixed-only Modulation Profiles: ETSI

Ch BW
MHz
Mod.
Airlink
XPIC
Capacity
Capable
Mbit/s
Ethernet L1
Throughput
Mbit/s
Ethernet L2
Throughput
Mbit/s
Ethernet
Latency us
No P. Encr.
1518
byte
1518
byte
1518
byte
64
byte
64
byte
64
byte
Ethernet
Latency us
With P. Encr.
1518
byte
Max TDM
64
byte
55
256 QAM 366.4
Yes
370
465
365
355
114
46
117
49
100xE1
55
128 QAM 312.6
Yes
307
397
303
302
120
47
N/A
N/A
2xSTM1+E1
55
128 QAM 312.6
No
307
397
303
302
132
58
N/A
N/A
2xSTM1+E1
55
64 QAM
267.6
Yes
270
340
267
259
131
51
137
57
100xE1
27.5
256 QAM 181.3
Yes
183
230
181
175
183
82
191
90
88xE1
27.5
128 QAM 157.3
Yes
155
200
153
152
193
82
N/A
N/A
STM1+E1
260-668139-001
JULY 2014
45
Ch BW
MHz
Mod.
Airlink
XPIC
Capacity
Capable
Mbit/s
27.5
128 QAM 157.3
27.5
128 QAM 154.5
Ethernet L1
Throughput
Mbit/s
Ethernet L2
Throughput
Mbit/s
Ethernet
Latency us
No P. Encr.
1518
byte
1518
byte
1518
byte
64
byte
64
byte
Ethernet
Latency us
With P. Encr.
64
byte
1518
byte
Max TDM
64
byte
No
155
200
153
152
215
105
N/A
N/A
STM1+E1
Yes
156
196
154
150
200
88
210
98
75xE1
27.5
128 QAM 154.6
No
156
196
154
150
220
108
229
117
75xE1
27.5
64 QAM
132.9
Yes
134
169
132
129
216
92
227
103
64xE1
27.5
32 QAM
105.0
No
106
133
105
101
262
115
276
129
51xE1
13.75
64 QAM
64.3
Yes
65
82
64
62
396
178
418
200
31xE1
13.75
64 QAM
58.4
Yes
59
74
58
56
440
203
479
242
28xE1
13.75
32 QAM
55.7
No
56
71
55
54
510
263
535
288
27xE1
64 QAM
31.3
Yes
31
40
31
30
780
373
825
418
15xE1
64 QAM
29.7
Yes
30
38
29
29
830
400
876
446
14xE1
3.5
16 QAM
No
11
2540
1140 2700
1300
4xE1
Table 1-9. Typical Data for Fixed-only Modulation Profiles: ANSI

Ch BW
MHz
Mod.
Airlink
Capacity
XPIC
Capable
Ethernet L1 Ethernet L2
Throughput Throughput
Mbit/s
Mbit/s
1518
byte
Mbit/s
64
1518
byte byte
Ethernet
Latency us
No P. Encr.
64
1518
byte byte
64
byte
Ethernet
Latency us
With P. Encr.
1518
byte
Max TDM
64
byte
50
256 QAM 321.8
Yes
325
409
321
311
122
50
127
55
127xDS1
50
64 QAM
235.8
Yes
238
300
235
228
140
55
147
62
127xDS1
40
256 QAM 256.0
Yes
258
325
255
248
139
60
145
66
127xDS1
40
256 QAM 256.0
No
258
325
255
248
153
72
160
78
127xDS1
40
64 QAM
179.6
No
175
227
173
173
187
87
4xDS3
40
64 QAM
178.0
Yes
179
226
177
168
172
72
180
80
115xDS1
40
64 QAM
178.0
No
179
226
177
172
184
83
192
92
115xDS1
40
64 QAM
157.0
No
153
198
151
151
200
90
1xOC3
40
64 QAM
156.4
No
158
199
156
151
200
90
209
99
100xDS1
40
32 QAM
137.9
No
134
174
133
133
210
90
3xDS3
40
32 QAM
135.2
No
136
172
135
131
205
85
223
103
87xDS1
30
256 QAM 179.3
No
176
222
174
169
206
107
4xDS3
30
256 QAM 178.1
No
180
226
177
172
206
106
214
114
115xDS1
30
256 QAM 178.1
Yes
180
226
177
172
186
85
194
93
115xDS1
30
128 QAM 157.2
No
154
193
152
147
214
105
1xOC3
30
128 QAM 154.8
Yes
152
192
150
146
198
88
208
98
100xDS1
30
128 QAM 154.8
No
152
192
150
146
218
108
227
117
100xDS1
30
64 QAM
134.9
No
133
167
131
127
233
112
3xDS3
30
64 QAM
135.0
Yes
133
167
131
127
210
88
222
100
87xDS1
30
64 QAM
135.0
No
133
167
131
127
230
110
242
122
87xDS1
10
256 QAM 55.9
No
56
71
56
54
536
293
562
319
36xDS1
10
128 QAM 50.0
No
50
63
50
48
564
296
592
324
32xDS1
10
64 QAM
45.2
No
44
57
44
43
576
283
1xDS3
10
64 QAM
45.1
No
45
57
45
43
581
288
613
320
29xDS1
128 QAM 24.8
No
25
31
25
24
1061
558
1117
614
16xDS1
No
12
16
12
12
1790
822
1898
930
8xDS1
5
3.75
46
32 QAM
12.4
AVIAT NETWORKS
RAC 30v3 Modulation Profiles

RAC 30v3 uses fixed modulation - it does not support adaptive modulation.
Depending on capacity/bandwidth options, modulation rates are programmed for
QPSK, 16QAM, 32QAM, 64QAM, 128QAM, or 256QAM.
Enhanced System Gain Option for STM1 and OC3
An additional enhanced system gain option for 1xSTM1/128 QAM and 1xOC3/128
QAM improves Rx threshold and system gain by 1.5dB compared to the standard
1xSTM1/OC3 option.
ETSI Options
The table below lists the ETSI capacity, modulation, and bandwidth options for RAC
30v3. E3 rates are not supported - instead use the DAC 3xE3/DS3M to multiplex an
E3 to an NxE1 link.
Table 1-10. RAC 30v3 ETSI System Options
Channel BW MHz
Modulation
Airlink Capacity2
3.5
16QAM
10 Mbit/s, 5xE1
QPSK
10 Mbit/s, 5xE1
16QAM
20 Mbit/s, 10xE1
64 QAM
32 Mbit/s, 16xE1
13.75 / 14
QPSK
20 Mbit/s, 10xE1
13.75 / 14
16 QAM
40 Mbit/s, 20xE1
13.75 / 14
64 QAM
65 Mbit/s, 32xE1
27.5 / 28
QPSK
40 Mbit/s, 20xE1
27.5 / 28
16 QAM
80 Mbit/s, 40xE1
27.5 / 28
32 QAM
106 Mbit/s, 52xE1
27.5 / 28
64 QAM
131 Mbit/s, 64xE1
27.5 / 28
128 QAM
150 Mbit/s, 75xE1, 1xSTM1 1
27.5 / 28
128 QAM
STM1+1E1 (wayside E1)
ANSI Options
The table below lists North American (ANSI) Common Carrier capacity, modulation
and bandwidth options.
Table 1-11. RAC 30v3 ANSI System Options
Channel BW MHz
Modulation
Airlink Capacity2
3.75
32 QAM
12 Mbit/s, 8xDS1
QPSK
6 Mbit/s, 4xDS1
16 QAM
12 Mbit/s, 8xDS1
1An enhanced system gain option is provided for this capacity.

2Nominal (rounded) Ethernet capacities are used.
260-668139-001
JULY 2014
47
Channel BW MHz
Modulation
Airlink Capacity1
128 QAM
24 Mbit/s, 16xDS1
10
QPSK
12 Mbit/s, 8xDS1
10
16 QAM
24 Mbit/s, 16xDS1
10
64 QAM
40 Mbit/s, 28xDS1
10
64 QAM
1xDS3
20
QPSK
24 Mbit/s, 16xDS1
20
16 QAM
43 Mbit/s, 28xDS1
20
16 QAM
1xDS3
20
16 QAM
49 Mbit/s, 32xDS1
30
QPSK
43 Mbit/s, 28xDS1
30
32 QAM
100 Mbit/s, 70xDS1
30
64 QAM
130 Mbit/s, 84xDS1
30
64 QAM
3xDS3
30
128 QAM
30
128 QAM
150 Mbit/s, 100xDS1

150 Mbit/s, 1xOC3 1
30
256 QAM
4xDS3
Adaptive Coding and Modulation (ACM)

ACM maximizes use of available channel bandwidth through automatic adjustment of
modulation and coding so that the most data efficient (highest possible) modulation
is used over the prevailing path conditions. ACM operation requires RAC 60E/6XE.
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 throughput or maximum system gain.
Adapti ve modul ati on i s not supported on Super PDH ri ng l i nks,
or on frequency di versi ty l i nks.
Adapti ve modul ati on can be used on ERP and RSTP ri ng/mesh
networks. No network re-convergence acti on wi l l occur wi th a
change of modul ati on. Traffi c pri ori ti zati on opti ons can be
appl i ed to ensure pri ori ty traffi c conti nues to get through on
l ower modul ati ons / l ower throughputs. Otherwi se normal I P
traffi c contenti on operati on appl i es.
RAC 60E and RAC 6XE
l
Supports four modulation rates, QPSK, 16 QAM, 64 QAM, or 256 QAM, plus a
coding option on each.
The coding options enable maximum throughput or maximum gain to provide
a total of eight modulation states.
RFU options are ODU 600, ODU 600sp, ODU 300hp, or IRU 600.
1Nominal (rounded) Ethernet capacities are used.
48
AVIAT NETWORKS
Capacity and ACM feature licensing applies. Refer to Licensing on page 72.
ACM is supported on ETSI CCDP/XPIC links (27.5, 40, 55 MHz Ch BW).
ACM is supported on ANSI CCDP/XPIC links (25, 30, 40, 50 MHz Ch BW).
Refer to:
l
Adaptive Modulation (AM) on page 49
Coding on page 50
RAC 60E/6XE Capacity, Throughput, Latency on page 55
Adaptive Modulation (AM)

Wireless links are traditionally engineered to carry traffic with a 99.999% availability
under all path conditions. This can require 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
adaptive modulation; it dynamically changes the modulation so that the highest availability 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 DAC GE3
GigE switches, and the service provisioning provided by the network overlay.
l
All high priority traffic, such as voice and video, continues to get through when
path conditions are poor.
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 mixed mode Ethernet
and PDH links, unlike Ethernet there is no QoS synergy on PDH connections. E1/DS1
circuits are simply 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
260-668139-001
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.
This highest capacity state is typically available for better than 99.5% of the
time.
JULY 2014
49
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.
Receiver SNR primarily determines a modulation change up, or down. See
Modulation Change Criteria on page 52.
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.
Figure 1-25. 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 modulation switch-overs, successful switch-overs between modulation types, and average
throughput achieved.
Coding
For RAC 60E and RAC 6XE modulation code settings provide two sets of modulation
states, one for maximum 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.
50
AVIAT NETWORKS
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.
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.
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
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 finetune link performance. It also provides best balance on AM operation.
l
The four modulation rates (QPSK, 16 QAM, 64 QAM, 256 QAM) support nearlinear 2x, 3x, 4x capacity steps.
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.
It effectively eliminates the need for additional intermediate modulation rates,
such as 32 QAM or 128 QAM.
Even where just one modulation rate is required/permitted, the coding option
still 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 gain, to 256 QAM maximum throughput 1. Ethernet throughput
is shown for 64 byte frames at Layer 1 (L1).
1HG = high (maximum) gain coding; HT = high (maximum) throughput coding.
260-668139-001
JULY 2014
51
Figure 1-26. 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.
Link capacities are typically reduced by between 6% to 18% compared to
maximum throughput.
For more information, refer to the Eclipse Packet Node datasheet.
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 synchroni zed - i t i s possi bl e for a RAC 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 configured modulation has an improve SNR threshold and a degrade SNR threshold.
l
SNR is the sole criteria for step-downs (degrade).
SNR with ATPC settings are used for step-ups (improve).
When the receiver SNR reaches the improve threshold, and the target remote fade margin 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
52
APTC is optimized to improve received SNR at the far end to push for a
modulation increase (up to the maximum configured modulation).
AVIAT NETWORKS
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 modulation unless the transmit power is below the maximum allowed for the requested
modulation. See Reference Modulation on page 54.
The table below lists the SNR improve and degrade change points for one of the ETSI
ACM channels.
Degrade = down fade, the SNR threshold at which the modulation will step
down.
Improve = up fade, the SNR threshold at which the modulation will step up.
Step up/down are also dependent on the modulation selection (the 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.
Table 1-12. Example SNR Change Points

SNR dB
Modulation
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 associated RSLs.
l
260-668139-001
Each ACM channel bandwidth operates with a defined set of SNR change
points, which apply across all frequency bands.
But the relationship between these SNR change points and receive signal level
(RSL) is different for each frequency band.
Note the 2 db difference (hysteresis) between the improve and degrade
thresholds.
Improve thresholds typically range between 6 dB to 10 dB above the 10-6 receive
threshold; degrade thresholds 3 dB to 4 dB.
JULY 2014
53
Figure 1-27. Example ACM Change Points and RSLs
Reference Modulation
A reference modulation setting in Portal applies to ACM operation, and works in conjunction with the user-entered Max Tx Power setting. It particularly applies to ETSI
markets where there can be a requirement to ensure the transmitted signal is maintained within a specified transmit mask over the various ACM modulation states
(transmit mask is modulation dependent).
The reference modul ati on i s the modul ati on rate that determi nes the maxi mum al l owabl e Tx power wi thi n an AM scheme.
ETSI Rates:
l
54
Modulation-based transmit or spectral emission masks define spurious

emissions limits.
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.
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.
If a least stringent QPSK mask (QPSK reference modulation) is applicable on all
higher ACM rates, it permits use of transmit powers up to the maximum
applicable to these rates.
If on the other hand, the highest modulation rate is used to establish the
applicable Tx mask (256 QAM reference modulation), the maximum Tx power
that can be set on the lower modulation rates must be backed off.
AVIAT NETWORKS
The maximum permitted user-entered Max Tx Power setting will change based
on the Reference Modulation selected.
For RAC 60E and RAC 6XE one of the QPSK, 16 QAM, 64 QAM, or 256 QAM
rates must be selected as the reference modulation.
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.
Where the user-entered Max Tx Power setting is set sufficiently below the
maximum allowable Tx power on the highest modulation rate, Tx power backoff 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.
Transmit output power maximums are effectively set for each modulation step
and are aligned with the maximums for non-ACM (fixed) operational modes.
RAC 60E/6XE Capacity, Throughput, Latency

The following tables summarize Ethernet throughput and latency for ACM profiles.
l
Under ACM operation up to four modulation profiles can be selected for a

particular channel bandwidth. The selection is made from a total of eight
profiles; four from the maximum throughput coding options, and four from
maximum gain.
Alternatively, where ACM operation is not required, any ONE of the listed
profiles can be selected for fixed use.
Two sets of tables are provided, one for DPP operation, one for Backplane Bus.
They show Ethernet latency figures with payload encryption set to OFF.
l
Latency is extended with payload encryption ON. The additional latency to

apply can be calculated using the data provided at Adaptive Coding and
Modulation (ACM) on page 48.
Latency is unaffected by a DPP shaping mode selection.
The tables also show the maximum number of E1/DS1 tribs supported by each profile.
l
E1/DS1 circuits are mapped via the backplane bus, unlike Ethernet which can
be mapped via the DPP and/or the backplane.
The total E1 or DS1 circuits configured on one radio link cannot exceed
backplane maximums of 100xE1 or 127xDS1.
For TDM latency figures see TDM Latency on page 66.
Refer to:
DPP on page 56
260-668139-001
JULY 2014
55
Backplane Bus on page 59

Ethernet Latency With Payload Encryption on page 63
DPP
ETSI and ANSI tables are provided for DPP RAC-to-DAC connection, with coding set
for maximum throughput, and separately for maximum system gain.
Additionally, each table shows the effect of DPP shaper-mode selection of maximum
throughput or static.
l
The DPP shaper mode determines the process used to shape Ethernet traffic to
radio link bandwidth.
o

but at the expense of a slightly lower throughput.
n
Note that with static shaping, L2 throughput is frame-size independent.
Maximum throughput is the default selection.
Ethernet latency is shown for 64 and 1518 byte frames with payload encryption OFF.
The additional latency to apply can be calculated using the data provided at Ethernet
Latency With Payload Encryption on page 63.
TDM (E1/DS1) maximums show the maximum number of tribs supported under each
profile.
Where Ethernet and E1/DS1 circuits are configured on a link, capacity for Ethernet is
reduced by 2.048 Mbit/s for each E1 included in the payload, or by 1.544 Mbit/s for
each DS1.
CCDP/XPIC operation is supported on selected ACM channel bandwidths of:
l
ETSI: 27.5, 40, 55 MHz.
ANSI: 25, 30, 40, 50 MHz.
Typical Data for ETSI ACM Profiles: Maximum Throughput, DPP

RAC 60E/6XE
DAC GE3
Ethernet Throughput
Static Shaping
Ch BW
(MHz)
Mod.
Airlink
L1 Mbit/s
Cap.
1518
64
Mbit/s
byte
byte
L2 Mbit/s
TDM
Ethernet Throughput
Max Throughput Shaping
L1 Mbit/s
L2 Mbit/s
Avg Ethernet
Latency us
(No P. Encr)
All
1518
byte
64
byte
1518
byte
64
byte
1518
byte
64
byte
Max
E1s
55
256 QAM
366
357
463
353
370
465
365
354
183
115
100
55
64 QAM
267
260
338
258
270
340
266
259
195
115
100
55
16 QAM
181
177
229
175
183
230
181
175
219
118
88
55
QPSK
90
88
114
87
91
115
90
87
285
119
44
40
256 QAM
251
245
317
242
253
319
250
243
247
164
100
40
64 QAM
184
179
232
177
186
234
184
178
265
165
89
40
16 QAM
117
114
148
113
118
149
117
113
302
167
57
56
AVIAT NETWORKS
RAC 60E/6XE
DAC GE3
Ethernet Throughput
Static Shaping
Ch BW
(MHz)
Mod.
Airlink
L1 Mbit/s
Cap.
1518
64
Mbit/s
byte
byte
L2 Mbit/s
TDM
Ethernet Throughput
L1 Mbit/s
L2 Mbit/s
Avg Ethernet
Latency us
(No P. Encr)
Max
E1s
All
1518
byte
64
byte
1518
byte
64
byte
1518
byte
64
byte
56
59
74
58
56
408
173
28
40
QPSK
27.5
256 QAM
181
177
229
174
183
230
181
175
323
222
88
27.5
64 QAM
132
129
168
128
134
169
132
129
347
224
64
27.5
16 QAM
89
86
112
85
90
113
89
86
390
225
43
27.5
QPSK
44
43
56
42
45
56
44
43
534
234
21
13.75
256 QAM
87
85
110
84
88
111
87
85
624
455
42
13.75
64 QAM
64
63
81
62
65
82
64
62
675
457
31
13.75
16 QAM
42
41
54
41
43
54
42
41
774
465
20
13.75
QPSK
21
20
26
20
21
27
21
20
1070
480
10
256 QAM
44
43
56
42
45
56
44
43
1163
863
21
64 QAM
31
30
39
30
32
40
31
30
1275
865
15
16 QAM
21
20.5
26.5
20
21
27
21
20
1462
875
10
QPSK
10
10
13
10
10
13
10
10
2050
900
58
57
74
Table 1-13. Typical Data for ETSI ACM Profiles: Maximum Gain, DPP
RAC 60E/6XE
DAC GE3
Ethernet Throughput
Static Shaping
Ch BW
(MHz)
Mod.
Airlink
L1 Mbit/s
Cap.
1518
64
Mbit/s
byte
byte
L2 Mbit/s
TDM
Ethernet Throughput
L1 Mbit/s
L2 Mbit/s
Avg Ethernet
Latency us
(No P. Encr)
All
1518
byte
64
byte
1518
byte
64
byte
1518
byte
64
byte
Max
E1s
55
256 QAM
343
335
434
331
347
436
343
332
185
114
100
55
64 QAM
246
240
310
236
248
312
245
238
201
117
100
55
16 QAM
146
143
185
141
148
186
146
142
233
117
71
55
QPSK
74
72
94
71
75
94
74
72
315
121
36
40
256 QAM
234
228
295
225
236
297
233
226
248
162
100
40
64 QAM
167
163
210
160
168
212
166
161
269
163
81
40
16 QAM
100
97
126
96
101
127
99
96
319
166
48
40
QPSK
50
49
63
48
50
63
49
48
445
175
24
27.5
256 QAM
169
165
214
163
171
215
169
164
326
221
82
27.5
64 QAM
121
118
153
116
122
154
120
117
356
224
58
27.5
16 QAM
73
71
92
70
73
92
72
70
423
227
35
27.5
QPSK
36
35
45
34
36
46
36
35
595
236
17
13.75
256 QAM
82
80
103
79
82
104
81
79
633
454
39
13.75
64 QAM
58
57
74
56
59
74
58
56
693
458
28
13.75
16 QAM
35
34
44
33
35
44
35
34
835
465
16
13.75
QPSK
17
16
21
16
17
21
17
16
1204
485
256 QAM
41
40
52
40
42
53
41
40
1177
862
20
64 QAM
29
29
37
28
30
38
29
30
1298
870
14
16 QAM
17
17
22
17
18
22
17
17
1576
884
QPSK
10
11
2320
920
260-668139-001
JULY 2014
57
Table 1-14. Typical Data for ANSI ACM Profiles: Maximum Throughput, DPP
RAC 60E/6XE
DAC GE3
Ethernet Throughput
Static Shaping
Ch BW
(MHz)
Mod.
Airlink
L1 Mbit/s
Cap.
1518
64
Mbit/s
byte byte
L2 Mbit/s
TDM
Ethernet Throughput
L1 Mbit/s
L2 Mbit/s
Avg Ethernet
Latency us
(No P. Encr)
All
1518
byte
64
byte
1518
byte
64
byte
1518
byte
64
byte
Max
DS1s
60/80
256 QAM
365
357
462
352
369
464
364
354
190
123
127
60/80
64 QAM
269
263
341
259
272
342
268
261
205
125
127
60/80
16 QAM
182
178
230
175
184
232
182
177
224
124
117
60/80
QPSK
90
88
114
86
91
115
90
87
292
126
58
50
256 QAM
317
310
401
306
321
404
316
307
206
133
127
50
64 QAM
232
227
294
224
235
295
232
225
220
133
127
50
16 QAM
147
144
186
142
149
187
147
143
250
135
94
50
QPSK
73
72
93
71
74
93
73
71
335
140
46
40
256 QAM
254
248
321
245
257
323
253
246
257
175
127
40
64 QAM
186
182
235
179
188
236
186
180
275
175
120
40
16 QAM
118
115
149
113
119
150
117
114
312
177
76
40
QPSK
58
57
74
56
59
74
58
57
418
183
37
30
256 QAM
189
184
239
182
191
240
188
183
320
222
122
30
64 QAM
138
135
175
133
140
176
138
134
344
224
89
30
16 QAM
88
85
111
84
89
112
87
85
395
226
56
30
QPSK
43
42
55
42
44
55
43
42
537
233
28
25
256 QAM
156
153
198
151
158
199
156
152
387
275
101
25
64 QAM
114
112
145
110
116
146
114
111
415
277
74
25
16 QAM
72
71
92
70
73
92
72
70
478
280
46
25
QPSK
36
35
45
34
36
46
36
35
650
290
23
20
256 QAM
342
79
20
123
120
155
118
124
157
123
119
473
64 QAM
90
88
114
87
91
115
90
88
510
344
58
20
16 QAM
61
60
77
59
62
78
61
59
570
344
39
20
QPSK
30
29
38
29
30
38
30
29
775
354
19
10
256 QAM
60
58
76
58
61
76
60
58
915
684
38
10
64 QAM
42
42
54
41
43
54
42
41
995
690
27
10
16 QAM
29
30
37
28
30
37
29
29
1125
695
19
10
QPSK
14
14
18
14
14
18
14
14
1555
715
Table 1-15. Typical Data for ANSI ACM Profiles: Maximum Gain, DPP
RAC 60E/6XE
DAC GE3
Ethernet Throughput
Static Shaping
Ch BW
(MHz)
Mod.
Airlink
L1 Mbit/s
Cap.
1518
64
Mbit/s
byte byte
L2 Mbit/s
TDM
Ethernet Throughput
L1 Mbit/s
L2 Mbit/s
Avg Ethernet
Latency us
(No P. Encr)
All
1518
byte
64
byte
1518
byte
64
byte
1518
byte
64
byte
Max
DS1s
60/80
256 QAM
344
336
435
332
348
438
343
333
194
123
127
60/80
64 QAM
246
240
311
237
249
313
245
238
210
125
127
60/80
16 QAM
147
144
186
142
149
187
147
143
240
125
95
60/80
QPSK
73
71
93
71
74
93
73
71
325
130
47
58
AVIAT NETWORKS
RAC 60E/6XE
DAC GE3
Ethernet Throughput
Static Shaping
Ch BW
(MHz)
Mod.
Airlink
L1 Mbit/s
Cap.
1518
64
Mbit/s
byte byte
L2 Mbit/s
TDM
Ethernet Throughput
L1 Mbit/s
L2 Mbit/s
Avg Ethernet
Latency us
(No P. Encr)
All
1518
byte
64
byte
1518
byte
64
byte
1518
byte
64
byte
Max
DS1s
50
256 QAM
296
289
375
285
299
377
295
287
210
133
127
50
64 QAM
211
206
267
203
213
265
210
204
225
134
127
50
16 QAM
126
123
160
122
127
161
126
122
265
136
80
50
QPSK
62
61
79
60
63
80
62
61
365
140
40
40
256 QAM
237
231
300
228
240
301
236
230
260
175
127
40
64 QAM
169
165
214
163
171
215
168
164
280
176
109
40
16 QAM
101
99
128
97
102
128
101
98
330
178
65
40
QPSK
50
49
63
48
51
64
50
48
455
185
32
30
256 QAM
179
175
226
173
181
228
179
173
325
223
115
30
64 QAM
135
132
171
130
137
127
135
131
345
223
87
30
16 QAM
78
76
99
75
79
92
78
75
415
228
50
30
QPSK
38
38
49
37
39
49
38
37
573
235
24
25
256 QAM
146
143
185
141
148
185
146
142
390
276
94
25
64 QAM
104
102
132
100
105
132
104
101
426
278
67
25
16 QAM
63
61
80
61
64
80
63
61
502
280
40
25
QPSK
30
30
39
29
31
39
31
30
705
292
19
20
256 QAM
116
113
147
112
117
148
116
112
475
340
75
20
64 QAM
83
81
105
80
84
105
83
80
520
342
53
20
16 QAM
50
49
63
48
50
63
50
48
617
347
32
20
QPSK
24
24
31
24
25
31
24
24
870
360
15
10
256 QAM
56
55
71
54
57
72
56
55
926
685
36
10
64 QAM
40
39
51
39
41
51
40
39
1015
690
25
10
16 QAM
24
23
30
23
24
31
24
23
1215
700
15
10
QPSK
11
11
15
11
12
15
11
11
1755
725
Backplane Bus
ETSI and ANSI tables are provided for backplane bus RAC-to-DAC connection, with
coding set for maximum throughput, and separately for maximum system gain.
l
Under ETSI operation the backplane is set for a Bus Connection Size of 2.048
Mbit/s (E1 capable).
o
Under ANSI operation the backplane is set for a Bus Connection Size of 1.544
Mbit/s (DS1 capable).
o
260-668139-001
The maximum capacity supported on the bus is 204 Mbit/s, which

represents the maximum capacity provided for transport of bus-connected
Ethernet data.
The maximum throughput supported on the bus is 197 Mbit/s, which

represents the maximum capacity provided for transport of bus-connected
Ethernet data.
Where the selected profile has an air link capacity in excess of that which is
needed for backplane bus traffic, the difference can be used to transport DPPconnected traffic.
JULY 2014
59
For example, the first two 55 MHz profiles in the table below provide an
airlink capacity greater than the 204 Mbit/s capacity maximum of the
backplane bus. The capacity difference can be used to transport DPPconnected traffic.
Ethernet latency is shown for 64 and 1518 byte frames with payload encryption OFF.
The additional latency to apply can be calculated using the data provided at Ethernet
Latency With Payload Encryption on page 63.
TDM (E1/DS1) maximums show the maximum number of tribs supported under each
profile.
Where Ethernet and E1/DS1 circuits are configured on a link, capacity for Ethernet is
reduced by 2.048 Mbit/s for each E1 included in the payload, or by 1.544 Mbit/s for
each DS1.
CCDP/XPIC operation is supported on selected ACM channel bandwidths of:
l
ETSI: 27.5, 40, 55 MHz.
ANSI: 25, 30, 40, 50 MHz.
Table 1-16. Typical Data for ETSI ACM Profiles: Max Throughput, Backplane Bus
RAC 60E/6XE
DAC GE3
Ethernet Throughput
Ch BW
(MHz)
60
Mod.
Airlink
Cap.
Mbit/s
L1 Mbit/s
L2 Mbit/s
TDM
Avg Ethernet
Latency us
(No P. Encr)
1518
byte
64
byte
All
1518
byte
64
byte
Max
E1s
55
256 QAM
366
191
248
189
385
305
100
55
64 QAM
267
191
248
189
385
305
100
55
16 QAM
181
168
218
166
394
305
88
55
QPSK
90
84
109
83
463
308
44
40
256 QAM
251
191
248
189
433
352
100
40
64 QAM
184
170
221
168
441
353
89
40
16 QAM
117
109
141
107
479
355
57
40
QPSK
58
53
69
53
589
360
28
27.5
256 QAM
181
168
218
166
658
413
88
27.5
64 QAM
132
122
158
121
527
414
64
27.5
16 QAM
89
82
106
81
574
416
43
27.5
QPSK
44
40
52
39
723
423
21
13.75
256 QAM
87
80
104
79
803
641
42
13.75
64 QAM
64
59
77
58
855
645
31
13.75
16 QAM
42
38
49
38
963
650
20
13.75
QPSK
21
19
25
19
1270
660
10
256 QAM
44
40
52
39
1348
1049
21
64 QAM
31
28
37
28
1464
1056
15
16 QAM
21
19
25
19
1669
1065
10
QPSK
10
12
2276
1096
AVIAT NETWORKS
Table 1-17. Typical Data for ETSI ACM Profiles: Max Gain, Backplane Bus
RAC 60E/6XE
DAC GE3
Ethernet Throughput
Ch BW
(MHz)
Mod.
Airlink
Cap.
Mbit/s
L1 Mbit/s
L2 Mbit/s
TDM
Avg Ethernet
Latency us
(No P. Encr)
1518
byte
64
byte
All
1518
byte
64
byte
Max
E1s
55
256 QAM
343
191
248
189
385
305
100
55
64 QAM
246
191
248
189
385
305
100
55
16 QAM
146
136
176
134
410
306
71
55
QPSK
74
69
89
68
494
310
36
40
256 QAM
234
191
248
189
433
352
100
40
64 QAM
167
155
201
153
447
353
81
40
16 QAM
100
91
119
90
499
356
48
40
QPSK
50
46
59
45
627
362
24
27.5
256 QAM
169
207
203
155
506
412
82
27.5
64 QAM
121
111
144
109
537
414
58
27.5
16 QAM
73
67
87
66
606
418
35
27.5
QPSK
36
32
42
32
790
427
17
13.75
256 QAM
82
74
97
73
814
643
39
13.75
64 QAM
58
53
69
53
875
646
28
13.75
16 QAM
35
30
39
30
1039
653
16
13.75
QPSK
17
15
20
15
1420
672
256 QAM
41
38
49
38
1362
1049
20
64 QAM
29
26
34
26
1494
1057
14
16 QAM
17
15
20
15
1820
1072
QPSK
10
2582
1112
Table 1-18. Typical Data for ANSI ACM Profiles: Max Throughput, Backplane Bus
RAC 60E/6XE
DAC GE3
Ethernet Throughput
Ch
BW
(MHz)
260-668139-001
Mod.
Airlink
Cap.
Mbit/s
L1 Mbit/s
L2 Mbit/s
TDM
Avg Ethernet
Latency us
(No P. Encr)
1518
byte
64
byte
All
1518
byte
64
byte
Max
DS1s
60/80
256 QAM
365
183
237
181
456
373
127
60/80
64 QAM
269
183
237
181
456
373
127
60/80
16 QAM
182
169
218
166
462
374
117
60/80
QPSK
90
83
108
82
532
377
58
50
256 QAM
317
183
237
181
464
381
127
50
64 QAM
232
183
237
181
464
381
127
50
16 QAM
147
135
176
134
486
382
94
50
QPSK
73
66
86
65
575
385
46
40
256 QAM
254
183
237
181
508
423
127
40
64 QAM
186
173
224
171
511
425
120
40
16 QAM
118
109
142
108
550
427
76
40
QPSK
58
53
69
52
664
433
37
30
256 QAM
189
176
228
174
557
471
122
JULY 2014
61
RAC 60E/6XE
DAC GE3
Ethernet Throughput
Ch
BW
(MHz)
Mod.
Airlink
Cap.
Mbit/s
L1 Mbit/s
L2 Mbit/s
TDM
Avg Ethernet
Latency us
(No P. Encr)
1518
byte
64
byte
All
1518
byte
64
byte
Max
DS1s
30
64 QAM
138
128
166
126
581
472
89
30
16 QAM
88
81
105
80
633
475
56
30
QPSK
43
40
52
40
778
481
28
25
256 QAM
156
145
188
143
623
525
101
25
64 QAM
114
106
138
105
653
527
74
25
16 QAM
72
66
86
65
718
529
46
25
QPSK
36
33
43
32
894
538
23
20
256 QAM
20
123
114
147
112
708
588
79
64 QAM
90
83
108
82
746
591
58
20
16 QAM
61
56
73
55
813
595
39
20
QPSK
30
27
35
27
1032
606
19
10
256 QAM
60
55
71
54
1156
933
38
10
64 QAM
42
39
50
38
1242
935
27
10
16 QAM
29
27
35
27
1369
944
19
10
QPSK
14
13
17
13
1842
965
Table 1-19. Typical Data for ANSI ACM Profiles: Max Gain, Backplane Bus
RAC 60E/6XE
DAC GE3
Ethernet Throughput
Ch BW
(MHz)
62
Mod.
Airlink
L1 Mbit/s
Cap.
1518
64
Mbit/s
byte byte
L2 Mbit/s
TDM
Avg Ethernet
Latency uS
(No P. Encr)
All
1518
byte
64
byte
Max
DS1s
60/80
256 QAM
344
183
237
181
457
373
127
60/80
64 QAM
246
183
237
181
457
373
127
60/80
16 QAM
147
137
177
135
478
374
95
60/80
QPSK
73
68
88
67
566
378
47
50
256 QAM
296
183
237
181
464
381
127
50
64 QAM
211
183
237
181
464
381
127
50
16 QAM
126
115
149
114
501
382
80
50
QPSK
62
58
75
57
601
386
40
40
256 QAM
237
183
237
181
508
424
127
40
64 QAM
169
157
204
155
518
425
109
40
16 QAM
101
93
121
92
569
428
65
40
QPSK
50
46
60
45
698
434
32
30
256 QAM
179
166
215
163
560
471
115
30
64 QAM
135
125
162
124
583
472
87
30
16 QAM
78
72
93
71
652
475
50
30
QPSK
38
34
45
34
829
485
24
25
256 QAM
146
135
176
134
629
525
94
25
64 QAM
104
96
125
95
664
527
67
25
16 QAM
63
58
75
57
745
530
40
AVIAT NETWORKS
RAC 60E/6XE
DAC GE3
Ethernet Throughput
Ch BW
(MHz)
Mod.
25
QPSK
20
256 QAM
20
20
Airlink
L1 Mbit/s
Cap.
1518
64
Mbit/s
byte byte
L2 Mbit/s
TDM
Avg Ethernet
Latency uS
(No P. Encr)
All
1518
byte
64
byte
Max
DS1s
30
27
35
27
969
543
19
116
108
140
106
714
590
75
64 QAM
83
76
99
75
759
591
53
16 QAM
50
46
60
45
860
596
32
20
QPSK
24
21
28
21
1145
611
15
10
256 QAM
56
52
67
51
1169
933
36
10
64 QAM
40
36
46
35
1267
958
25
10
16 QAM
24
21
28
21
1483
949
15
10
QPSK
11
10
13
10
2098
980
Ethernet Latency With Payload Encryption

Ethernet latency with payload encryption ON can be calculated by adding the figures
below to the latency figures in the tables above.
l
l
l
Payload encryption can be applied on adaptive and fixed (single) modulation

selections.
The additional latency applies per channel bandwidth - the 'Add us' is
applicable on all modulation rates within a channel bandwidth, irrespective of
coding and whether or not CCDP/XPIC is enabled.
The additional latency is agnostic to frame size.
For example, the latency for 1518 byte frames on an DPP-connected 55 MHz Ch
BW link with 64 QAM max throughput coding, is 195 us. To determine latency
with payload encryption, 20 us is added for a total of 215 us.
The additional latency is independent of the encryption scheme selected (128,
192, 256 CCM).
Table 1-20. Additional Ethernet Latency with Payload Encryption On

Ch. BW MHz
Std
Add us
55
ETSI
20
40
ETSI
29
27.5
ETSI
39
13.75
ETSI
80
ETSI
153
80
ANSI
19
50
ANSI
23
40
ANSI
28
30
ANSI
36
25
ANSI
45
20
ANSI
56
10
ANSI
113
260-668139-001
JULY 2014
63
L1 versus L2 Throughput
L1 throughput represents the total bit rate through an Ethernet user port based on
Frame Space; the Ethernet frame plus the full 20 byte IFG + Preamble.
l
Where a link does not support IFG + Preamble suppression, the L1 throughput
represents the link throughput.
Where a link incorporates suppression it can accept more incoming frame
spaces - more bit/s - than would otherwise be the case. This is frame-size
dependent - smaller frames have a greater proportion of their frame space taken
up by the IFG + Preamble overhead - so they have more to gain with the
application of IFG + Preamble suppression.
L1 throughput is sometimes referred to as the port utilization rate.
L2 throughput represents the bit rate count on Ethernet frames through a user port.
The count does not include the IFG + Preamble bytes.
l
Throughput is highly frame-size-dependant on links that do not support IFG

and Preamble suppression.
On links that do, the reduction in overhead from 20 to just 4 bytes improves L2
throughput on all frame sizes. But smaller frames receive most benefit, resulting
in L2 throughput being much less affected by frame size. In fact with DAC GE3
the Ethernet frame to radio link air-frame shaper delivers near identical L2
throughputs for all frame sizes.
Figures quoted at L1 are typically based on 64 byte frames to provide a maximum

indication of bits-per-second throughput.
Layer 2 throughput figures have traditionally and more realistically represented Ethernet throughput, as they look only at the Ethernet frame; IFG and preamble bytes are
ignored. Measurement practice is specified in RFC 2544 to provide a standardized test
methodology for the industry.
IFG and Preamble Suppression

IFG and preamble suppression is a bit-saving data technique. Non-essential framing
data on a link between L2 switches is removed at the input to the link, and then
restored on exit, to provide an effective means to increase throughput and hence data
efficiency.
Standard IP data packets are encapsulated within Ethernet framing, which adds
frame address and check bytes, plus an inter-frame gap (IFG) and Preamble (PRE).
l
Standard IP packets range in size from 46 to 1500 bytes. Ethernet framing

results in a frame size ranging from 64 to 1518 bytes respectively, and a frame
space of 84 to 1538 bytes.
o
64
The Ethernet Frame comprises the IP Packet plus MAC header (MAC DA and
MAC SA), Length/Type and FCS bytes. The number of error-free frames that
can be sent over an Ethernet link represents the L2 throughput for that link.
AVIAT NETWORKS
The Ethernet Frame Space comprises the Ethernet Frame plus IFG and
Preamble bytes. The number of error-free frame-spaces that can be sent over
an Ethernet link represents the L1 throughput for that link.
IFG and Preamble add 20 bytes to the Ethernet frame size, and as overheads deliver
no useful content data.
This is where IFG and Preamble suppression act to provide throughput efficiencies;
the 20 bytes are replaced by 4 bytes.
The resulting 16 byte reduction in frame space represents a 23.5% throughput improvement for 64 byte frames. For average-size 260 byte frames it represents a 6% traffic
throughput improvement. For 1518 byte frames it represents a 1% improvement.
The smaller the frame size, the more frames it takes to fill the 'pipe'. And with
more frames there are more overheads, so overheads consume a proportionally
larger slice of the available Ethernet bandwidth.
Hence, the smaller the frame size the greater the gains to be made by employing
frame suppression techniques.
The figure below illustrates Ethernet framing of an IP packet for standard and VLAN
tagged (802.1Q and 802.1Q-in-Q) frames.
Figure 1-28. Ethernet Frame
Table 1-21. Ethernet Frame Content (802.3)

Description
Bytes
IFG
Inter-Frame Gap
12
PRE
Preamble: Synchronization + SFD.Consists of

seven preamble synchronization bytes
(alternating ones and zeros), plus one start of
frame delimiter (SFD) byte.
MAC DA and MAC SA

(Media Access Control)
Destination Address 6 bytes and Source

Address 6 bytes
12
L/T
Length/Type
Q Tag
VLAN 802.1Q Tag
Q-in-Q Tag
VLAN 802.1Q-in-Q Tag
260-668139-001
JULY 2014
65
Description
Bytes
Packet
Includes: IP Header 20 bytes typical, TCP

46 to 1500
header 20 bytes, and application data max 1460
bytes (std packets)
FCS
Frame Check Sequence
Total Frame Space: Std Frame
84 to 1538
Total Frame Space: Q Frame
88 to 1542
Total Frame Space: Q-in-Q Frame
92 to 1546
I F G + Preambl e suppressi on parti cul arl y appl i es to rate or

bandwi dth l i mi ted l i nks wi thi n an Ethernet network, such as
mi crowave l i nks or l eased-l i ne connecti ons, where maki ng
most effi ci ent use of the avai l abl e capaci ty i s paramount. They
are typi cal l y appl i ed over l i nks between L2 swi tches where the
dedi cated nature of the connecti on means there i s no need to
retai n the I F G and Preambl e bytes. I nstead these overhead
bytes are suppressed at the sendi ng end, and then re-i nserted
at the recei vi ng end.
By reduci ng overheads more useful (packet) data i s sent i nsi de
each frame.
The following table summarizes the percent throughput improvements for several
frames sizes, including an average-size 260 byte frame.
For standard Ethernet frames 20 bytes are added by the IFG and Preamble. The
resulting byte total is the Frame Space.
With IFG and Preamble suppression, the 20 bytes are reduced to 4. Frame
Space is reduced by 16 bytes.
The reduced overhead on frames sent over the link allows more frames to enter
the link - throughput efficiency is improved.
Table 1-22. Nominal Throughput Improvements by Frame Size for a 100 Mbit/s Link
Frame Size Standard Frame
Frame with IFG + Preamble Supp.
Frame
Space
FPS
Frame
Space
FPS
FPS%
Increase
64
84
148809.5
68
183823.5
23.5
128
148
84459.5
132
94697.0
12.1
260
280
44642.9
264
47348.5
6.1
512
522
23496.2
516
24224.8
3.1
1518
1538
8127.4
1522
8212.9
1.1
TDM Latency
This section provides TDM latency figures for radio links, TDM plug-in cards, and the
NCM loopswitch to enable estimation of end-end latency on a TDM circuit, from trib
port to trib port.
66
AVIAT NETWORKS
TDM latency on fixed-only modulations is specific to each modulation.
TDM latency on ACM modulations is common across each channel bandwidth

regardless of the modulation in use.
TDM Latency: Fixed-Only Modulation

These latency figures are for radio links using fixed-only (non ACM) modulation profiles.
They show latency to/from the backplane bus; the backplane is the common interconnection point.
Latency is measured from RAC/RFU to far end RFU/RAC.
RAC is RAC 60E/6XE. RFU is ODU 600 or IRU 600.
TDM latency figures are dependent on payload encryption; latency is extended

with payload encryption ON.
The table shows latencies per channel bandwidth, with and without payload
encryption.
Latency with encryption ON is independent of the encryption scheme

selected (128, 192, 256 CCM).
The figures exclude free-space latency, which adds 3.3 us per km or 5.4 us per
mile.
Table 1-23. Link Latency With and Without Payload Encryption: ETSI
Ch BW
MHz
Mod.
XPIC
Capable
Max TDM
Latency us Payload
Encryption Off
Latency us Payload
Encryption On
55
256 QAM Yes
100xE1
204
267
55
64 QAM
100xE1
209
275
Yes
27.5
256 QAM Yes
88xE1
239
247
27.5
128 QAM Yes
75xE1
244
254
27.5
128 QAM No
75xE1
267
276
27.5
64 QAM
Yes
64xE1
247
258
27.5
32 QAM
No
51xE1
267
281
13.75
64 QAM
Yes
31xE1
329
351
13.75
64 QAM
Yes
28xE1
353
392
13.75
32 QAM
No
27xE1
412
437
64 QAM
Yes
15xE1
514
559
64 QAM
Yes
14xE1
540
586
3.5
16 QAM
No
4xE1
1007
1167
Table 1-24. Link Latency With and Without Payload Encryption: ANSI
Ch BW
MHz
Mod.
XPIC
Capable
Max TDM
Latency us Payload
Encryption Off
Latency us Payload
Encryption On
50
256 QAM
Yes
127xDS1
263
268
50
64 QAM
Yes
127xDS1
267
274
40
256 QAM
Yes
127xDS1
274
280
40
256 QAM
No
127xDS1
287
293
40
64 QAM
Yes
115xDS1
286
294
260-668139-001
JULY 2014
67
Ch BW
MHz
Mod.
XPIC
Capable
Max TDM
Latency us Payload
Encryption Off
Latency us Payload
Encryption On
40
64 QAM
No
115xDS1
297
306
40
64 QAM
No
100xDS1
302
311
40
32 QAM
No
87xDS1
296
314
30
256 QAM
No
115xDS1
299
307
30
128 QAM
Yes
100xDS1
302
312
30
128 QAM
No
100xDS1
322
331
30
64 QAM
Yes
87xDS1
300
312
30
64 QAM
No
87xDS1
321
333
10
256 QAM
No
36xDS1
498
524
10
128 QAM
No
32xDS1
500
528
10
64 QAM
No
29xDS1
490
522
128 QAM
No
16xDS1
750
806
32 QAM
No
8xDS1
988
1096
5
3.75
The figures below are for NxDS3 and OC3 link latency measured DAC to DAC: DAC/RAC/RFU
to remote end RFU/RAC/DAC.
l
l

For NxDS3 the DAC is DAC 3xE3/DS3M in DS3 mode (backplane bus set as DS3
capable).
For OC3 the DAC is DAC 155o or DAC 2x155o.
Payload encryption is not available on these profiles.

Table 1-25. DAC-DAC Link Latency for DS3 and OC3 Modulation Profiles
Ch BW
MHz
Mod.
XPIC
Capable
Max TDM
Latency us
40
64 QAM
No
4xDS3
101
40
64 QAM
No
1xOC3
89
40
32 QAM
No
3xDS3
104
30
256 QAM
No
4xDS3
122
30
128 QAM
No
1xOC3
102
30
64 QAM
No
3xDS3
126
10
64 QAM
No
1xDS3
287
TDM Latency: ACM

These TDM latency figures are for radio links using ACM capable modulation profiles.
They show latency to/from the backplane bus; the backplane is the common interconnection point.
l
Latency is measured from RAC/RFU to far-end RFU/RAC.

o
68
TDM latency figures are common across each channel bandwidth regardless of
the modulation in use, the coding in use, and selection of XPIC or non-XPIC
operation. It is however dependent on payload encryption; latency is extended
with payload encryption ON.
AVIAT NETWORKS
The table shows latencies per channel bandwidth, with and without payload
encryption.
Latency with encryption ON is independent of the encryption scheme

selected (128, 192, 256 CCM).
The figures exclude free-space latency, which adds 3.3 us per km or 5.4 us per
mile.
Table 1-26. Radio Link Latency With and Without Payload Encryption
Ch. BW
MHz
Std
Latency us
Payload Encryption Off
Latency us
Payload Encryption On
55
ETSI
270
290
40
ETSI
322
351
27.5
ETSI
382
421
13.75
ETSI
608
688
ETSI
1007
1160
80
ANSI
339
358
50
ANSI
346
369
40
ANSI
390
418
30
ANSI
436
472
25
ANSI
490
535
20
ANSI
554
608
10
ANSI
890
1003
TDM Card Latency

The table below lists TDM plug-in card latency.
l
Figures show averaged latency from front panel trib port to/from the INU
backplane bus.
The figures can be used in conjunction with the above link latency data to
estimate end-end trib circuit latency.
Table 1-27. TDM Plug-in Card Latency

Card
DAC 16xV2
DAC 3xE3/DS3M
Mode
E1
33 us
DS1
43 us
E13 Mux (E3)
46 us
M13 Mux (DS3)

DAC 155oM
NCM front ports
Latency: Front Trib Port

to Backplane Bus
27 us
SDH VC3
118 us
SDH VC4
118 us
SONET
172 us
E1
35 us
DS1
45 us
NCM Loopswitch Latency

NCM Loopswitch latency is nominally 50 us.
l
260-668139-001
This is the latency added by an NCM pairing per looped circuit i.e. from source
NCM switch to destination NCM switch.
JULY 2014
69
This latency is switch-to-switch. It does not include NCM front port latency
or the latency added by an external DAC 16x trib card.
To estimate the total latency of a looped circuit the latency of trib ports plus
intermediate links and devices must be added to the NCM loopswitch latency.
Example Latency Calculations

For an ACM profile the data required to calculate an end-end trib latency includes Ch
BW, payload encryption yes/no, hop distance, trib card type and mode.
For a fixed-only profile the data required includes Ch BW, modulation, XPIC capable
yes/no, payload encryption yes/no, hop distance, trib card type and mode.
Example 1: 23 GHz ETSI link, ODU 600, RAC 60E, ACM 27.5 Ch BW, 64 QAM max
throughput, no payload encryption, 10 km hop distance, DAC 16x to DAC 16x.
Radio link latency:
382 + 10x3.3 = 415 us
DAC 16xV2 E1 latency:
33x2 = 66 us
TOTAL:
481 us
Example 2: U6 ANSI link, ODU 600, RAC 60E, ACM 30 MHz Ch BW, 256 QAM
max gain, payload encryption, 12 mile hop distance, optical trib, DAC 1550M to DAC
1550M.
Radio link latency:
DAC 155oM SONET latency:
472 + 12x5.4 = 537 us

172x2 = 344 us
TOTAL:
881 us
Example 3: NCM loopswitch network, 7 GHz ANSI links, ACM 20 MHz Ch BW, 16
QAM max throughput, payload encryption.
Figure 1-29. Example Loopswitch Topology
The following calculation is for primary path latency, with tribs connected via
NCM+DAC 16x at Site A, and NCM front trib ports at Site C.
70
AVIAT NETWORKS
A-B radio link latency:
608 + 20x5.4 = 716

us
B-C radio link latency:
608+ 18x5.4 = 705

us
NCM to NCM loopswitch latency:
50 us
NCM 8xDS1 front port latency at Site C
45 us
DAC 16xV2 latency at Site A:
43 us
TOTAL:
260-668139-001
1.56 ms
JULY 2014
71
Licensing
Node-based capacity licensing of Eclipse INUs applies. Feature licenses additionally
apply on selected operational features.
l
Node-based licensing replaces RAC-based licensing, which was the only

capacity licensing option prior to SW release 5.0.
DPP operation and most feature licenses only apply under node-based capacity
licensing.
You can upgrade to SW release 5.0 and still continue to use RAC-based
licensing but you will not have access to the benefits provided under node-based
licensing.
Al l new nodes ordered are defaul t i nstal l ed wi th a node-based
capaci ty l i cense.
Wi th the i ncrease i n capabi l i ti es and compl exi ty of some new
pl ug-i n modul es, such as RAC 60E/6XE, DAC GE3, and NCM,
compact fl ash cards wi th i ncreased capaci ty are requi red.
When upgradi ng I NUs ensure the compact fl ash card i s sui tabl e. Refer to C omp act Flash C ard on p age 81.
Node-based Capacity Licensing

Node based licensing includes the DPP and the backplane in a single allocation of
licensed capacity across all installed RACs.
l
Capacity is allocated for active traffic only. RACs installed for protected
operation are not subject to capacity licensing.
Flexible license capacity allocation over the backplane and/or DPP. A capacity
license is auto-allocated or user-allocated between installed RACs.
Licenses installed prior to SW release 5.0 are upgrade-able to the node-based
licenses. This process is simplified with the ProVision license upgrade utility.
Operati on wi th node-based l i censes does not affect over-ai r
i nter-operati on wi th nodes usi ng RAC-based l i censes, or wi th
I DUs.
Exi sti ng users can upgrade nodes to SW rel ease 5.0 but stay
wi th RAC-based l i censi ng unti l a node needs to be updated to
DPP and/or feature-l i censed operati on.
The following node-based license breaks are applicable to total radio payload (airlink
capacity total).
l
72
Licenses are up-to licenses. For example, a 200 Mbit/s license supports all
capacities up t0 200 Mbit/s.
AVIAT NETWORKS
Field upgrades from a lower to higher capacity are available.
Capacity Licenses
l
EZE-08001 50 Mbit/s
EZE-08002 100 Mbit/s
EZE-08008 1.2 Gbit/s
Feature Licensing
Feature licenses provide access to extended Eclipse functionality.
l
A feature license is a node-based license - it applies across all relevant cards

installed in the node.
When a feature is required on a new node it is ordered together with the
capacity license for the node.
Feature licenses can be separately ordered as upgrades on existing nodes.
Feature Overview
Feature Licenses:
EZF-01: Layer 1 Link Aggregation (DAC GE3)
L1 link aggregation (L1LA) splits traffic between links on a byte-segment basis.
It supports higher burst capacities compared to L2 link aggregation - throughput can
burst to the aggregated total capacity, unlike L2 link aggregation.
L1LA (like L2 link aggregation) supports redundancy - data from a failed link is directed onto the remaining link, or links.
L1LA on DAC GE3 is modulation-aware; load re-balancing occurs on modulation
change under adaptive modulation.
See Link Aggregation on page 168.
EZF-02: Adaptive Modulation (RAC 60E/6XE)
Modulation is automatically and dynamically switched between modulation selections.
See Adaptive Coding and Modulation (ACM) on page 48.
260-668139-001
JULY 2014
73
EZF-03: Secure Management (NMS)

Secure Management applies to Eclipse NMS access over the network, and to local
access via the Portal craft tool.
l
l
Provides secure management access to Eclipse over an unsecured network.

Protects Eclipse configurations from accidental or intentional modification by
unauthorized personnel.
Keeps track of all events for accountability.
Based on FIPS 140-2 validated algorithms.
See Secure Operation on page 253.

EZF-04: Payload Encryption (RAC 60E/6XE)
Payload Encryption encrypts payload and management data on the wireless link to
prevent eavesdropping.
l
Checks integrity of each data frame in the wireless link to ensure that received
data has been sent by the intended transmitter.
Provides the same level of security as Wi-Fi and WiMAX.
FIPS-197 compliant.
Can be enabled/disabled independently for each wireless link.
Meets US federal and commercial requirements.

EZF-05: Ethernet over TDM (DS3, DS1, E1)
Enables mapping of Ethernet data to DS3, DS1, or E1 PDH interfaces using the DAC
3xDS3M or DAC 16xV2. Applies where a customer wishes to transport Ethernet data
over existing DS3 or NxE1/DS1 radio or leased-line circuits.
l
Ethernet data from the Eclipse backplane is mapped into a DS3 frame as DS1
(1.544 Mbps) multiples to a maximum 28xDS1, to support a maximum data
rate (available bandwidth for Ethernet) of 43 (43.232) Mbps per DS3. The DS3
connection must support unframed/transparent DS3.
Ethernet data is mapped into NxDS1 frames at 1.544 Mbps per DS1 to a
maximum 16xDS1 on the DAC 16xV2, to support a maximum data rate
(available bandwidth for Ethernet) of 24 (24.7) Mbps.
Ethernet data is mapped into NxE1 frames at 2.048 Mbps per E1 to a
maximum 16xE1 on the DAC 16xV2, to support a maximum data rate
(available bandwidth for Ethernet) of 32 (32.768) Mbps.
EZF-06: RADIUS Client

Enables connection validation to a RADIUS server for centralized account management.
EZF-09: Synchronous Ethernet
Enables Synchronous Ethernet operation on DAC GE3 cards.
See Synchronous Operation on page 179.
74
AVIAT NETWORKS
EZF-10: Ethernet OAM

Enables access to Ethernet OAM capabilities.
See Ethernet OAM on page 190.
EZF-14 and EZF-1408: TDM Loop Switch
l
EZF-14 supports up to 50xE1 or 63xDS1 trib circuits (the max number of

drop/insert tribs supported on an INU/INUe - requires NCM together with DAC
16xV2 plug-ins for trib access).
EZF-1408 supports up to 8xE1/DS1 NCM front-panel tribs (the max number of
drop/insert tribs supported on the NCM front panel).
See Ring Protection - E1/DS1 Loop-switch on page 200.

EZF-42: FIPS 140-2 Secure Operation
l
l
l
Enables secure management of Eclipse in compliance with the Federal

Information Processing Standard (FIPS) Publication 140-2.
Applies to the INUe only.
Installation and operation data is provided in the Aviat publication: Eclipse
User Manual Addendum for FIPS 140-2.

EZF-43: IPv6
l
Enables IPv6 operation. Includes OSPF IPv6 and RIPNG.
EZF-51 to EZF-56
Enables flexible power mode (FPM) on ODU 600 and ODU 600sp.
FPM unlocks an additional 3dB of transmit power. Applies to all modulations, on all
bands. It also increases the manual and ATPC transmit power control range by 3dB.
l
EZF-51: High power option 1 x ODU
EZF-52: Nodal High power option 2 x ODU
EZF-61 to EZF-66
IRU 600v3 high Tx power. Unlocks an additional 3dB of transmit power over standard power. Applies on all modulations, on all IRU 600v3 bands. It also increases the
manual and ATPC transmit power control range by 3dB.
l
EZF-61 EZG-61 IRU 600 High power option 1 x RFU
EZF-62 EZG-62 IRU 600 Nodal High power option 2 x RFU
260-668139-001
JULY 2014
75
Upgrade Licenses
A simple file download mechanism is used for field upgrades.
l
To convert from RAC-based to node-based licensing an EZA down-loadable SW

license is used. Nodes must first be at SW release 5.0 or later.
For capacity upgrades the price charged is the difference between the current
license and the new, upgraded license.
For more information contact Aviat Networks or your supplier.
76
AVIAT NETWORKS
Plug-in Cards
This section introduces the function and application of the plug-in card options for
Eclipse Packet Node. See:
l
Overview on page 77
NCC Plug-In on page 79
FAN Plug-In on page 81
RAC Plug-Ins on page 82
DAC Plug-Ins on page 86
AUX Plug-In on page 127
NPC Plug-In on page 131
PCC Plug-In on page 132
Overview
The following table overviews the plug-in types and their function. For more information go to the individual plug-ins.
Table 1-28. Eclipse Plug-in Cards
Unit
Description
NCC
Node Control Card
The NCC is a mandatory plug-in for each INU/INUe. It performs key node
management and control functions, and provides various dc rails from the 48Vdc input. It also incorporates a plug-in flash card, which holds node
configuration and license data.
FAN
Fan Card
To provide cooling one 1RU FAN is fitted in an INU; one 2RU FAN in an INUe.
Each FAN is fitted with two long-life axial fans plus monitoring and control
circuits. For NEBS compliance the fan filter option must be installed.
AUX
Auxiliary Card
AUX provides synchronous and asynchronous auxiliary data channels, NMS

porting, and alarm inputs and outputs. Sync data at 64 kbps and async to
19.2 kbps.
NPC
Node Protection Card
NPC provides redundancy for the NCC TDM bus management and power
supply functions.
PCC
Power Conversion
Card
PCC accepts a +24 Vdc power supply input and converts it to a -56 Vdc
output for connection to an NCC or NPC.
260-668139-001
JULY 2014
77
Unit
Description
RAC
Radio Access Card
An INU may be populated with a maximum of three RACs. Six for the INUe.
For split-mount operation each RAC interfaces to a companion ODU via a
single 50 ohm coaxial cable. For all-indoor operation each RAC (RAC 60E/6XE
only) interfaces with an RFU in the companion IRU 600.
l
RAC 30v3 interfaces to ODU 600, ODU 600sp, or 300hp/ep for

channel bandwidths to 27.5/30 MHz and capacities of 5x to 75xE1,
4x to 100xDS1, 1x to 3xDS3, or 1xSTM1/OC3.
RAC 60E interfaces to ODU 600, ODU 600sp, ODU 300hp or IRU
600 for fixed or adaptive modulation on channel bandwidths of 7,
14, 27.5, 40 or 56 MHz (ETSI), or 3.75, 5, 10, 20, 25, 30, 40, 50, &
80 MHz (ANSI). Ethernet data is accessed via the DPP or backplane.
TDM data is accessed via the backplane.
RAC 6XE supports identical RAC 60E functionality, with the
addition of co-channel XPIC operation.
The same RAC type must be installed at both ends of a link. For
example ODU 300hp may be installed at one end, and ODU 600 at
the other, but both must be supported from the same RAC type,
either a RAC 30v3 or RAC 60E.
Unit
Description
DAC
Digital Access Card
DACs provide customer line interface options for E1, E3, DS1, DS3,
STM1/OC3, or Ethernet:
l
78
DAC 4x supports up to 4xE1 or DS1 tributaries. DAC 4X also supports

STM1+1E1 configurations for access to the E1 wayside trib.
DAC 16xV2 additionally supports hot-standby protection, and
Ethernet over E1s or DS1s.
DAC 3xE3/DS3 supports up to three DS3 tributaries. E3 airlink profiles
are no longer supported. Where E3 trib transport is required, use the
DAC 3xE3/DS3M E13 mode to mux E3 to/from 16xE1, and select
NxE1 link options.
DAC 3xE3/DS3M supports three DS3 tributaries (as for DAC
3xE3/DS3) plus a 2xE13 or M13 multiplexer mode, a 2x34 Mbit/s
transparent E3 mode for E3 video (MPEG) transport, or DS3 Ethernet
mode.
DAC 2x155o supports two STM1/OC3 optical tributaries.
AVIAT NETWORKS
Unit
Description
l
DAC 155oM multiplexes one STM1/OC3 optical tributary to/from an

Eclipse backplane configured for NxE1 or DS1, to support concurrent
SDH and PDH tributary access. A TVT (transparent virtual tributary)
mode supports Ethernet data to 130 Mbit/s.
DAC 155eM provides equivalent functionality to the DAC 155oM,
except that the STM1/OC3 connection is electrical (coax on M1.0/M2.3
connectors).
DAC 2x155e supports two STM1 electrical tributaries.
DAC GE3 supports three 10/100/1000Base-T electrical ports plus two
SFP ports for 1000Base-LX optical or 1000Base-T electrical, plus six
transport channels. Channels are configured for Nx2 Mbit/s, or x1.5
Mbit/s, capacities. High capacity DPP operation is supported in
conjunction with RAC 60E, RAC 6XE. DAC GE3 also supports
Synchronous Ethernet, 1+1 protection, and VLAN tagging.
NCM
NCM is used to provide an E1/DS1 loop-switch capability.
Network Convergence
Module
NCC Plug-In
The NCC plugs into a dedicated INU/INUe slot. Although field replaceable, it is not
hot swappable unless an NPC is installed.
Figure 1-30.
The NCC supports:

l
TDM bus clock and signaling distribution
Microprocessor control and management
DC/DC converter
Boot (start-up) flash
License and configuration flash
260-668139-001
JULY 2014
79
Network management access
Voltage and temperature levels management

In-band NMS options are provided in conjunction with DAC GE3 to transport Eclipse
NMS within the Ethernet payload, rather than in link overheads. See Networking and
Management Tools on page 266
NCC User Interfaces

User access is provided on the right side of the PCB for the Compact Flash card.
Figure 1-31. NCC Front Panel Layout
No
Item/Label
Description
Plug-in fastener
Finger-grip screw-type fastener and card pull (2).
-48Vdc
2-pin polarized D-series 2W2C power connector with captive screw

fasteners.
NMS
10/100Base-T
The four RJ-45 connectors provide Ethernet network management

access. Portal login to these ports requires entry of the IP address
for the INU/INUe, or use of the DHCP connection option. Ports may
also used to provide NMS connectivity to co-located Eclipse
INU/INUes and other Aviat Networks and third party radios. Ports
auto-resolve for straight or cross-over cables.
Ethernet port
orange LED
For NCCv2 the orange LED indicates connection status. It is on for a

valid connection, off for no connection or an invalid connection.
(Fitted to each
RJ-45 NMS
connector)
For NCCv1 the orange LED indicates traffic activity.
Ethernet port
green LED
For NCCv2 the green LED is the activity LED, it flashes to indicate
Ethernet traffic on the port. LED does not flash (is solid on) when
there is no traffic activity. (Activity LED is off when the connection
status LED is off).
(Fitted to each
RJ-45 NMS
connector)
For NCCv1 the green LED indicates connection status.
Maint V.24
RJ-45 connector provides a V.24 serial interface option for Portal

access. Includes a default IP address, which means knowledge of
the INU/INUe IP address is not required at login.
Test LED
Provides indications of:

Off
INU/INUe power off.
Green
Normal operation.
Orange flashing INU/INUe is in a test/diagnostic mode, for

example, loopbacks are set.
Status LED
80
Status LED provides indications of:

Off
INU/INUe power off
Green
Normal operation
AVIAT NETWORKS
No
Item/Label
Description
Orange flashing Configuration not supported or software /
hardware incompatible
Red
Critical alarm
Compact Flash Card

The Compact Flash (CF) card holds configuration, software load, and license data. It
inserts into the side of the NCC plug-in.
Each CF card is identified by a unique serial number; which is the license number for
the terminal.
With the increase in capabilities and complexity of some new plug-in modules, such
as RAC 60E/6XE, DAC GE3, and NCM, CF cards with increased capacity are
required.
l
INUs fitted with RAC 60E/6XE, DAC GE3, NCM, require a CF with an available
capacity of not less than 128 Mbyte.
o
Prior to July 2009, 32 Mbyte was the available capacity, regardless of the
labeled capacity of the card (cards of higher capacity were partitioned to only
make available 32 Mbyte to ensure compatibility with earlier NCC cards).
Since July 2009 all INUs have been shipped with 128 Mbyte CF cards (or
higher capacity), where the labeled capacity is the available capacity for
Eclipse.
These higher capacity CF cards will not operate with NCCs manufactured
before January 2008.
I f you are i ntendi ng to i nstal l RAC 60E/6XE, DAC GE3, i n an
exi sti ng I NU, fi rst check to see i f a hi gher capaci ty CF card i s
needed, and i f so, that the NCC wi l l support the hi gher capaci ty
CF . F or detai l ed i nformati on, refer to Compact F l ash under
' I nstal l i ng the I NU and I NUe' i n the Ecl i pse User Manual .
FAN Plug-In
One 1RU FAN card is required for an INU.
One 2RU FAN or two 1RU FAN cards are required for an INUe.
l
The IDCe (INUe chassis) supports both 1RU and 2RU FANs. It is supplied
standard with one 2RU FAN.
The FAN is field replaceable and can be hot swapped. Its removal will not interrupt
user traffic.
For NEBS compliance the fan filter option must be installed. It is supplied as a kit
comprising a filter frame, filter element, and fastening screw, and is installed in an
INU/INUe to the right side of the FAN. Kits are separately available for the INU and
INUe.
260-668139-001
JULY 2014
81
The FAN plug-in holds two long-life axial fans. Fan operation is temperature controlled and is performance monitored by the NCC. Under normal conditions one fan
operates, cycled between the two fans. Both fans will operate if the first fan fails to
keep the temperature below a preset threshold.
The LED is off (no illumination) for normal operation. Red indicates a critical FAN
alarm.
Figure 1-32. 1RU Fan Plug-in
RAC Plug-Ins
Different RAC versions provide support for capacity and bandwidth options up to 366
Mbit/s, 106xE1, 127x DS1, 4xDS3, 2xSTM1/OC3.
A RAC acts as the intermediary between the digital baseband and its ODU or IRU 600
(RAC 6X/6XE is required for IRU 600).
Up to three RACs can be fitted in the INU universal slots, and six in the INUe. Power
consumption limits apply on the INUe - see Power Consumption and INU Load Maximums on page 34.
Paired RACs/ODUs are used for protected operation.
l
Protected RACs are interconnected by a backplane diversity bus to support the

errorless Rx path switching (voting) capability.
The diversity bus is not capacity dependent.
Paired RACs/ODUs are used for CCDP/XPIC operation.

l
Front panel ports on XPIC RACs support XPIC cabling between the RACs.
RACs are field replaceable and hot swappable. They are not frequency dependent.
An INU/INUe can be installed with a mix of RAC versions.
Refer to:
82
RAC 30v3 Plug-In on page 83
RAC 60E/6XE Plug-Ins on page 84
AVIAT NETWORKS
RAC 30v3 Plug-In

RAC 30v3 is used for channel bandwidths to 27.5/30 MHz. Fixed modulation only.
With ODU 600 or ODU 300hp/ep, it supports airlink capacities to 150 Mbit/s,
75xE1, 100xDS1 or 1xSTM1/OC3. Depending on the selected capacity and
modulation option, channel bandwidths range from 7 to 28 MHz ETSI, or 5 to
30 MHz ANSI.
RAC 30v3 incorporates FEC 1 with interleaving, and adaptive equalization.
On ETSI bands only RAC 30v3 supports enhanced PDH capacities of 5x, 10x,
20x, 40x and 52xE1, plus standard 16xE1, 64xE1 and 75xE1 capacities.
RAC 30v3 does not support E3 rates. Where E3 data transport is required, use
the DAC 3xE3/DS3M in E13 mode to multiplex the E3 data stream to NxE1 on
the backplane bus.
Figure 1-33. RAC 30
RAC 30v3 Front Panel Layout

Figure 1-34. RAC 30v3 Front Panel Layout
No
Item/Label Description
Plug-in
fastener
1Incorporates Reed Solomon FEC encoding and depending on the mod-
ulation/bandwidth selected, also incorporates Viterbi encoding.
260-668139-001
JULY 2014
83
No
Item/Label Description
On-Line LED
LED provides indications of:

Off
INU is off-line
RAC may be removed safely. Traffic will not be
affected.
RAC is on a ring link that is wrapped. RAC is
operating error-free but waiting for the error-free
timer or time-of-day timer to time out before
unwrapping.
Green
RAC is online with transmit or receive active.

Removal may affect traffic.
Red
Status LED
No receive signal from the ODU

Off
INU power off
Green
Normal operation
Orange flashing Configuration not supported, or software /

Red
3
Critical RAC or ODU alarm
ODU connector SMA type for ODU jumper cable connection
RAC 60E/6XE Plug-Ins

RAC 60E/6XE support direct data packet-plane (DPP) connection to a DAC GE3.
With each RAC supporting airlink capacities to 366 Mbit/s, and with up to six RACs
installable in one node, aggregate airlink1 wireless capacity extends to 2.2 Gbit/s, and
L1 throughputs to 2.7 Gbit/s (64 byte port utilization speed).
RACs also connect to the backplane to support native mixed-mode Ethernet+TDM
links.
l
Ethernet traffic via the DPP (or DPP and backplane)
TDM traffic via the backplane
The RACs support Adaptive Coding and Modulation (ACM) for most efficient use of
channel bandwidth.
RAC 6XE additionally supports CCDP/XPIC with aggregate co-channel airlink capacities to 732 Mbit/s. XPIC RAC pairs may be located in the same or adjacent INUs.
Both incorporate LDPC (Low Density Parity Check) FEC encoding, and adaptive equalization.
1Airlink capacity is the link capacity available for Ethernet and/or TDM.
84
AVIAT NETWORKS
Figure 1-35. RAC 60E
Figure 1-36. RAC 6XE
Features include:
l
Front panel data packet port for direct connection to a DAC GE3 switch
Backplane access to TDM and/or IP for hybrid mixed-mode transport
Fixed or adaptive modulation
ETSI link capacities to 366 Mbit/s (56 MHz, 256 QAM)
ANSI link capacities to 320 Mbit/s (50 MHz channel, or 365 Mbit/s (80 MHz
channel)
Ethernet throughputs to 465 Mbit/s (L1, 64 byte frames)
TDM capacities to 2xSTM1, OC3, 100xE1, 127xDS1
Fully redundant 1+1 hot-standby or space/frequency diversity operation using

paired RACs
The front panel for RAC 60E is identical to RAC 6XE - minus the XPIC connectors.
260-668139-001
JULY 2014
85
Figure 1-37. RAC 6XE Front Panel
No
Item/Label
Description
Plug-in fastener
Finger-grip screw-type fastener and card pull (2)
On-Line LED

Off
INU is off-line
ODU transmit is muted
RAC is on a ring link that is wrapped. RAC is operating
error-free but waiting for the error-free timer or timeof-day timer to time out before unwrapping.
Status LED
Green
RAC is online with transmit or receive active.

(Supports all configurations including diversity where
one RAC is transmitting and receiving and the other
receiving only).
Red
No receive signal from the ODU

Off
INU power off
Green
Normal operation
Orange
flashing
Configuration not supported, or software / hardware

incompatible
Red
Critical RAC or ODU alarm
To DAC
RJ-45 connector for DPP connection to a DAC GE3
XPIC In/Out
SMB type for XPIC cross-connect cables
ODU connector
SMA type for ODU jumper cable connection
DAC Plug-Ins
DACs provide the intermediary between customer interfaces and the digital backplane.
Different DACs support different circuit rates and formats. Refer to:
86
DAC 4x Plug-In on page 87
DAC 16xV2 Plug-In on page 88
DAC 3xE3/DS3 Plug-In on page 93
DAC 3xE3/DS3M Plug-In on page 94
DAC 1x155o, DAC 2x155o Plug-Ins on page 98
DAC 155oM and DAC 155eM Plug-Ins on page 99
DAC 2x155e Plug-In on page 110
DAC GE3 Plug-in on page 111
AVIAT NETWORKS
DACs can be installed in any of the universal slots in an INU or INUe, and in restricted slots in the INUe. The exceptions are the DAC 155oM and DAC 155eM where NMS
access is required (NMS in RSOH or MSOH), in which case universal slots 1 - 6 in the
INUe must be used.
DACs are field replaceable and hot-swappable.
Most DACs can be protected. The protectable DACs are DAC GE3, DAC 16xV2, DAC
3xE3/DS3, DAC 3xE3/DS3M, DAC 1x155o, DAC 2x155o, DAC 155oM, DAC 2x155e,
DAC 155eM. Not protectable is DAC 4x. For information on DAC protection, refer to
DAC/Tributary Protection on page 211.
For data on trib cable wiring and connector pin-outs, refer to Appendix D, Eclipse
User Manual.
For information on DAC Loopback Points, PRBS Generation, and AIS/PRBS Auto
Insertion, refer to Diagnostics on page 277.
DAC 4x Plug-In
DAC 4x supports up to 4xE1 or 4xDS1 tributaries. It also supports up to two E1 waysides for STM1+1xE1 operation. See STM1+1E1 Operation on page 249.
l
l
E1 options are 75 ohm unbalanced or 120 ohms balanced.

DS1 encoding options are AMI or B8ZS. Line impedance is fixed at 100 ohms
balanced.
Each tributary is accessed via an RJ-45 connector, and cable sets are available, as
accessories, to provide:
l
RJ-45 to BNC male unbalanced.
RJ-45 to RJ-45 balanced, straight or crossover.
RJ-45 to unterminated for balanced wire wrap or punch-down insulation

displacement connection.
Figure 1-38. DAC 4x front panel layout
No
Item/Label
Description
Plug-in fastener
Status LED
Trib. connector
assembly
260-668139-001
Off
INU power off
Green
Normal operation
Orange
flashing
Configuration not supported, or software /

Red
Critical alarm: Trib LOS or SW/HW failure
4xRJ-45 type connectors for tributary cable connection
JULY 2014
87
DAC 16xV2 Plug-In

DAC 16xV2 supports up to 16xE1 or 16xDS1 tributaries with:
l
l
E1 options of 75 ohm unbalanced or 120 ohms balanced.

DS1 encoding options of AMI or B8ZS. Line impedance is fixed at 100 ohms
balanced.
Individual line code selection for AMI or B8ZS on DS1 tribs.
Tributary protection.
Ethernet over E1/DS1 unframed tribs.
Compact interface connectors and cable sets.
Provision of AIS Out and AIS In alarms.

o
An AIS Out warning alarm is raised when AIS is detected on a tributary

going out from on a DAC 16xV2 trib port (from the backplane bus).
An AIS In warning alarm is raised when AIS is detected on a tributary

coming into the DAC 16xV2.
Figure 1-39. DAC 16xV2
DAC 16xV2 plugs into INU slots 1-4 or INUe slots 1-9.
Tributary Protection
l
88
DAC 16xV2 is installed in pairs for hot-standby protection. The two protection
partners are installed in slots 1 to 4 in the INU, or slots 1 to 9 in the INUe. One
is configured as primary, the other as secondary. The primary is the default
DAC for online Rx and Tx.
Protection switching applies to standard E1/DS1 tribs or to Ethernet enabled
E1/DS1 tribs.
Protection switching operates on all Tx and/or all Rx tribs. If one Tx trib fails all
Tx tribs are switched. Similarly for Rx. But as Rx and Tx are switched
independently, it is possible for one of the DACs to be the online Tx, and the
other online Rx.
AVIAT NETWORKS
When a switch occurs, all Tx and/or Rx tributaries are switched to the

protection partner.
The figure below illustrates a 1+1 DAC 16x V2 application using Y-cabled Tributary
Protection. An alternative to Y-cables is Tributary Always On where separate cables
connect each DAC to the customer equipment.
For information on Tributary Protection and Tributary Always On, refer to DAC/Tributary Protection on page 211.
For information on trib switching criteria and restoration times, refer to DAC Protection Switching Criteria on page 228.
Figure 1-40. DAC 16xV2 1+1 Tribs
Ethernet Over E1/DS1 Tribs

When configured for Ethernet mode, Ethernet data from a DAC GE3 can be mapped
to one or more DAC 16xV2 E1 or DS1 tributaries. It enables transport of Ethernet data
over legacy E1 or DS1 radio or unframed1 leased-line circuits.
l
Ethernet data is mapped into E1 tribs at 2.048 Mbit/s per E1. The maximum
16xE1 capacity provided for Ethernet is 32 Mbit/s (32.768).
Ethernet data is mapped into DS1 tribs at 1.544 Mbit/s per DS1. The maximum
16xDS1 capacity provided for Ethernet is 24 Mbit/s (24.7).
An Ethernet over TDM feature license (EZF-05) is required. See Licensing on
page 72.
This requires a node-based license - feature licenses can only be installed with
node-based licensing.
On a new node the feature license must be ordered with the node-based capacity
license. On an existing node a feature license is separately ordered as an
upgrade, which must include an upgrade to Node-based licensing if not already
installed.
A G.703 unframed i nterface (unstructured G.703) i s requi red
on the l egacy radi o or l eased-l i ne CTU.
The tables below show typical L2 (RFC 2544) throughputs and latencies on a DAC
GE3 - DAC 16xV2 - DAC 16xV2 - DAC GE3 link2 with 16x Ethernet tribs.
1E1 or DS1 interfaces on NxE1/DS1 radios present an unframed interface, but some
leased line CTUs may present a framed interface. The interface must be unframed.
2DAC 16xV2 cards are cabled trib-to-trib.
260-668139-001
JULY 2014
89
Table 1-29. Throughputs and Latencies for a 16xE1 Link

Frame Size
Throughput Mbit/s
Latency uS
64 bytes
30.5
100
256 bytes
31.5
150
512 bytes
32
215
1024 bytes
32
340
1518 bytes
32
450
Table 1-30. Throughputs and Latencies for a 16xDS1 Link

Frame Size
Throughput Mbit/s
Latency uS
64 bytes
23
140
256 bytes
24
205
512 bytes
24
285
1024 bytes
24
450
1518 bytes
24
600
When a DAC 16xV2 is configured for Ethernet mode, unused tributaries are not available for standard E1/DS1 trib traffic.
When multiple tribs are configured for Ethernet they do not need to be adjoining / in
sequence.
The figure below illustrates the DAC 16xV2 in Ethernet mode to support a maximum
32 Mbit/s over 16xE1, or 24 Mbit/s over 16xDS1. Ethernet traffic from the DAC GE3 is
backplane connected to the DAC 16xV2 and mapped to E1 or DS1 tribs.
Figure 1-41. DAC 16xV2: 32/25 Mbit/s over Legacy TDM Radio
The figure below illustrates connection between a RAC and a DAC 16xV2. Ethernet
traffic from a RAC is backplane connected to the DAC 16xV2 and mapped into E1 or
DS1 tribs for transport over the legacy TDM radio.
Figure 1-42. DAC 16xV2: Eclipse Ethernet Link to Legacy TDM Radio
The figure below illustrates the two DAC 16xV2 cards in Ethernet mode to support a
maximum 64 Mbit/s over 32xE1, or 48 Mbit/s over 32xDS1.
90
AVIAT NETWORKS
Figure 1-43. DAC 16xV2: 64/50 Mbit/s over 16xE1/DS1
The figure below illustrates two DAC 16xV2s in Ethernet mode with Tributary Protection. Y-cables interface the paired cards to a common interface on the TDM radio. If
the radio has separate 1+1 E1/DS1 interfaces, each DAC 16xV2 is directly cabled to its
radio interface using the Tributary Always On option.
Figure 1-44. DAC 16xV2:Protected Ethernet-over-TDM Interface
The figure below illustrates a simple DAC 16xV2 network application for Ethernetover-TDM.
At INU A, Ethernet customer traffic is captured on the DAC GE and transported over
the Eclipse link as native Ethernet.
At INU B, Ethernet traffic from the Eclipse Ethernet link, and from the local DAC GE,
is mapped in the DAC 16xV2 to Ethernet-over-E1/DS1, for transport over the legacy
PDH link.
At INU C, E1/DS1 circuits from the PDH link are captured on the DAC 16xV2 and
their content returned to Ethernet for backplane connection to the DAC GE.
Figure 1-45. Simple DAC 16xV2 Network Application 1
260-668139-001
JULY 2014
91
The figure below illustrates an alternative configuration at INU B. Rather than separate connections from the RAC and DAC GE to the DAC 16xV2, the RAC traffic is
backplane connected to DAC GE channel 1, and DAC GE channel 2 is connected to
the DAC 16xV2. This provides a local Ethernet bridge/switch function, meaning traffic
from this site is addressed directly to INU A rather than through the DAC GE at INU
C.
Figure 1-46. Simple DAC 16xV2 Network Application 2
Line Code Selection

E1 options are 75 ohm unbalanced or 120 ohms balanced. A selection applies to individual tribs.
DS1 encoding options are AMI or B8ZS. A selection applies to individual tribs. Line
impedance is fixed at 100 ohms balanced.
Trib Connectors and Cables

High density 50 way HDR-E50 connectors are used for trib access.
Compact trib cable sets for non-protected and protected operation are available to connect 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
HDR-E50 to 24AWG free end 3m, 10m, 15m, 32m
HDR-E50 to 16xBNC 2m, 5m
HDR-E50 to RJ45 straight cable 2m, 5m
2x HDR-E50 Y-cable to 24AWG free end 3m, 15m, 32m
2x HDR-E50 Y-cable to 16xBNC 2m
Refer to the Eclipse User manual, Appendix D, for cable pin-outs.
Front Panel Layout

Figure 1-47. DAC 16xV2 Front Panel Layout
92
AVIAT NETWORKS
No
Item/Label
Description
Plug-in fastener
Status LED
3, 4
Trib. connector
Off
INU power off
Green
Normal operation
Orange
flashing

Red
HDR type connectors for tributary cable connection
DAC 3xE3/DS3 Plug-In

DAC 3xE3/DS3 supports one to three E3 or DS3 tribs. The INU/INUe backplane bus is
set to DS3.
Where E3 l i nk transport i s requi red, use the DAC 3xE3/DS3M i n
E13 mode to mul ti pl ex the E3 data stream to NxE1 on the backpl ane bus.
The trib interfaces are paired 75 ohm, unbalanced, mini BNC female connectors.
Trib cables are available, as accessories, to provide:
l
Mini BNC male to mini BNC male; two required per trib.
Mini BNC male to standard BNC male; two required per trib.
DAC 3xE3/DS3 plugs into slots 1-4 on an INU or slots 1-9 on an INUe.
DACs are installed in pairs for hot-standby protection. The two protection partners
are installed in slots 1 to 4 in the INU, or slots 1 to 9 in the INUe. One is configured
as primary, the other as secondary. The primary is the default DAC for online Rx and
Tx.
l
other online Rx.
protection partner.
Tributary Protection (Y-cable) or Tributary Always On (straight cables) are used to connect to customer equipment. For more information, refer to DAC/Tributary Protection
on page 211.
260-668139-001
JULY 2014
93
Figure 1-48. DAC 3xE3/DS3
Front Panel Layout

Figure 1-49. DAC 3xE3/DS3 Front Panel Layout
No
Item/Label
Description
Plug-in fastener
Status LED
Trib connectors
Off
INU power off
Green
Normal operation
Orange
flashing

Red
Three mini-BNC Tx/RX female connector pairings for 75 ohm

unbalanced tributary connection.
E3 format is HDB3, and the electrical interface meets
requirements defined in ITU G.703.
DS3 format is B3ZS, and the electrical interface meets
requirements defined in ITU G.703 and ANSI T1.102.
DAC 3xE3/DS3M Plug-In

DAC 3xE3/DS3M may be configured for:
l
94
3xDS3 tribs. (RAC/Link options do not support E3 rates. To transport E3 tribs

use the E13 mux option).
E13 or M13 multiplexer operation to multiplex 1x/2x E3 or 1/2x DS3 customer
interfaces to/from an E1 or DS1 backplane.
AVIAT NETWORKS
Transparent (unframed) 1x/2xE3 34 Mbit/s.
Ethernet over DS3 (Node based licensing and feature license required).
The operational functions provided include:

l
Equivalent functionality to DAC 3xE3/DS3. In 3xDS3 mode DAC 3xE3/DS3M is

end-end compatible with a DS3 configured DAC 3xE3/DS3. Requires a DS3
backplane setting.
E13 multiplexer, where one or maximum two E3 tributaries (Tx/Rx 1 and Tx/Rx
2) are multiplexed to an E1 backplane bus, each as 16xE1, in accordance with
G.703, G.742 and G.751. Operation is compatible with industry standard E13
multiplexers, meaning that at the E3 destination a 3rd party E13 multiplexer
can be used. Allows side-by-side transport with other E1 traffic over an Eclipse
link.
M13 multiplexer, where one or maximum two DS3 tributaries (Tx/Rx 1 and
Tx/Rx 2) are multiplexed to a DS1 backplane bus, each as 28xDS1, in
accordance with T1.102 and T1.107. Operation is compatible with industry
standard M13 multiplexers, meaning that at the DS3 destination a 3rd party
M13 multiplexer can be used. Allows side-by-side transport with other DS1
traffic over an Eclipse link
E3 transparent, unchannelised transport for ATM and video (e.g. MPEG2 video)
E3 streams. Each of the two transparent E3 interfaces (Tx/Rx 1 and Tx/Rx 2)
provides a 34.368 Mbit/s connection for transport as 17xE1 over an Eclipse
NxE1 network. Allows side-by-side transport with other E1 traffic over an
Eclipse link.
DS3 Ethernet to support transmission of Ethernet data over an unframed
(transparent) DS3 connection. It is used to transport Ethernet over legacy TDM
radio or leased line circuits.
The three E3 or DS3 tribs are presented as paired 75 ohm, unbalanced, mini BNC
female connectors.
Trib cables are available, as accessories, to provide:
l
Mini BNC male to mini BNC male; two required per trib.
Mini BNC male to standard BNC male; two required per trib.
DAC 3xE3/DS3M plugs into slots 1-4 on an INU or slots 1-9 on an INUe.
Figure 1-50. DAC 3xE3/DS3M
260-668139-001
JULY 2014
95
DACs are installed in pairs for hot-standby protection. The two protection partners
are installed in slots 1 to 4 in the INU, or slots 1 to 9 in the INUe. One is configured
as primary, the other as secondary. The primary is the default DAC for online Rx and
Tx.
l
other online Rx.
protection partner.
Tributary Protection (Y-cable) or Tributary Always On (straight cables) are used to connect to customer equipment. For more information, refer to DAC/Tributary Protection
on page 211.
Ethernet over DS3 Applications

An Ethernet over TDM feature license (EZF-05) is required. See Licensing on page 72.
l
l
l
This requires a node-based license - feature licenses can only be installed with
node-based licensing.
On a new node the feature license must be ordered with the node-based capacity
license. On an existing node a feature license is separately ordered as an
upgrade, which must include an upgrade to Node-based licensing if not already
installed.
The figure below illustrates a solution for provisioning 130 Mbit/s Ethernet over
a 3xDS3 radio.
One DAC 3xDS3M (3xE3/DS3M) card supports three DS3 WAN connections.
The DS3 interface on the radio must support transport of unframed DS3.
At the far end of the TDM connection (one or more links), the DS3 from the
radio must be terminated on an NTU using a DAC 3xDS3M card.
Two of the four 1RU NTU option slots are used.
Note that NxDS1 tribs can be included alongside the Ethernet data on a DS3
connection to the TDM radio - the available 43 Mbit/ is shared between
Ethernet and DS1 tribs in 1.544 Mbit/s / DS1 steps.
Ethernet data i s mapped i nto a DS3 frame as DS1 (1.544
Mbi t/s) mul ti pl es to a maxi mum 28xDS1, to support a maxi mum data rate (avai l abl e L1 bandwi dth for Ethernet) of 43
(43.232) Mbi t/s per DS3. Thi s equates to a nomi nal l ayer 2
(RF C 2544) throughput of 41 Mbi t/s (1518 byte frames).
I t requi res an unframed/transparent DS3 i nterface on the connected TDM radi o or l eased l i ne CTU.
96
AVIAT NETWORKS
Figure 1-51. Ethernet over 3xDS3
The DS3 Ethernet option is used with the NTU application (Network Transition Unit)
of the Eclipse platform for the North American market. For more information on the
NTU, and on Eclipse Ethernet over TDM applications, refer to the NTU datasheet or
to the NTU Applications Guide.
Front Panel Layout

Figure 1-52. DAC 3xE3/DS3M Front Panel
No
Item/Label
Description
Plug-in fastener
On-Line LED
Status LED
Trib Connectors
Off
INU power off
Green
DAC is online communicating with a remote DAC

3xE3/DS3M
Red
DAC is off-line

Off
INU power off
Green
Normal operation
Orange
flashing

Red
Three mini-BNC Tx/RX female connector pairings for 75 ohm

For E13/M13 Mux and E3 Transparent the two trib interfaces are
provided on Tx1/Rx1 and Tx2/Rx2. Tx3/Rx3 is not used - is not
active.
The standard E3 format is HDB3, and the electrical interface
meets requirements defined in ITU G.703.
The standard DS3 format is B3ZS, and the electrical interface
meets requirements defined in ITU G.703 and ANSI T1.102.
260-668139-001
JULY 2014
97
DAC 1x155o, DAC 2x155o Plug-Ins

DAC 1x155o supports one STM1/OC3, 155Mbit/s optical tributary.
DAC 2x155o is identical except it supports two 155 Mbit/s tribs for twice the capacity.
l
l
Operation is transparent to SDH or SONET frame information:

They incorporate a transparent, non-regenerative architecture; there is no
internal clock source / re-synchronization implementation. They are intended
for ADM-to-ADM linking where the ADMs provide the clock recovery and signal
re-sync options.
DAC 1x155o and DAC 2x155o should not installed back-to-back (trib
interconnected) over more than 2 hops of Eclipse (not more than one DAC-DAC
repeated hop).
Not more than 16 radio hops (RAC-to-RAC) should be used between the DACs.
(Clock should be regenerated using back-to-back DACs at or before 16 hops to
ensure G.825 wander limits are not exceeded).
DAC 155o behaves much l i ke fi ber - i t does not i nspect or
respond to the si gnal i ng bi ts i n the STM1/OC3 overhead.
DAC 1x155o and DAC 2x 155o require an STM1/OC3 INU/INUe backplane bus setting.
They plug into slots 1-4 on an INU or slots 1-9 on an INUe.
The connectors are SC type, and cable options are available, as accessories, for extension to SC to FC types. SC-SC attenuator cables options are also available.
The receive-level range is -31 dBm (max sensitivity) to -7 dBm (max input power).
The transmit level range is: Min -15 dBm to Max -8 dBm.
The SDH optical line code is Binary Scrambled NRZ (Non Return to Zero).
Figure 1-53. DAC 155o Plug-in
98
AVIAT NETWORKS
DACs are installed in pairs for hot-standby protection. The protection partners are
installed in slots 1 to 4 in the INU, or slots 1 to 9 in the INUe. One is configured as
primary, the other as secondary. The primary is the default DAC for online Rx and Tx.
For the DAC 2x155o protection switching operates on both Tx and/or both Rx
tribs. If one Tx trib fails both Tx tribs are switched. Similarly for Rx. But as Rx
and Tx are switched independently, it is possible for one of the DACs to be the
online Tx, and the other online Rx.
When a switch occurs, both Tx and/or Rx tributaries are switched to the

protection partner.
Tributary Protection (optical Y-cable) or Tributary Always On (optical straight cables)

are used to connect to customer equipment. For more information, refer to DAC/Tributary Protection on page 211.
Front Panel Layout

Figure 1-54. DAC 1x155o Front Panel Layout
No
Item/Label
Description
Plug-in fastener
Status LED

Off
INU power off
Green
Normal operation
Orange Configuration not supported, or software

flash/ hardware incompatible
ing
Red
3
Trib. connector
Critical alarm: Trib LOS or SW/HW

failure
SC type single mode optical connector
DAC 155oM and DAC 155eM Plug-Ins

The DAC 155oM is an optical STM1/OC3 multiplexer; the DAC 155eM is the electrical
equivalent (STM1/STS3). They function as a terminal multiplexers; they terminate or
originate the SDH/SONET frame. They do not support interconnection of ADMs as
there is no provision to transport the STM1/OC3 overheads nor ADM to ADM synchronization over the NxE1 or NxDS1 link transport circuits. For ADM interconnection, refer to DAC 1x155o, DAC 2x155o Plug-Ins on page 98.
260-668139-001
JULY 2014
99
The primary applications are:

l
Connection of an Eclipse Super-PDH network to an SDH core network.
Ring closure on an Eclipse Super-PDH ring using optical cable (DAC 155oM).
Transport of Ethernet data over legacy STM1/OC3 radio or leased line circuits.
DAC 155oM/eM multiplexes one line-side STM1/OC3, 155Mbit/s tributary to/from an

Eclipse backplane configured for NxE1 or NxDS1.
l
On the line side the they support interoperability with external SDH or SONET
multiplexers.
Options are provided for VC3 or VC4 mapping of lower-order backplane E1/DS1
traffic streams to/from STM1. SONET mapping is fixed.
SDH with VC3 framing: Three VC3s are mapped into an STM1 signal, each
containing up to 21xVC12 or 28xVC11. In turn each VC12 contains 1xE1, and
each VC11 1xDS1.
SDH with VC4 framing: VC4 directly maps up to 63xVC12 or 84xDS1 into an
STM1 signal. In turn each VC12 contains 1xE1, and each VC11 1xDS1.
SONET with STS1 framing: Three STS1s are mapped into a SONET signal, each
containing 28xVT1, or 21xVT2. In turn each VT1 contains 1xDS1, and each VT2
1xE1.
Trib port numbering within the STM1/OC3 frame is selectable between ITU-T
(G.707), and 'KLM'.
Mapping options are provided for bit asynchronous or transparent virtual
tributary (TVT) modes. Bit asynchronous is selected on all circuits except those
carrying Ethernet data, where TVT mode is required.
Clocking options are provided for recovered-clock and internal. These options
apply to the external line-side connection of the DAC 155oM/eM to another
DAC 155oM/eM or to an ADM.
Configuration options for the DAC 155oM include optical port shut-down or the
sending of an AIS signal on radio link failure.
Eclipse NMS may be transported within the MSOH or RSOH, access to which is
provided within the NMS bytes on the INU backplane.
F or more i nformati on on DAC 155oM, i ncl udi ng operati on,
appl i cati ons, di agnosti cs, and tri b mappi ng refer to the Avi at
Networks DAC 155oM whi te paper.
100
AVIAT NETWORKS
Figure 1-55. DAC 155oM Plug-in
The DAC 155oM connector assembly is an LC type on an SFP (small form-factor pluggable) transceiver module. Cable options are available, as accessories, for extension to
SC or FC types. LC-LC attenuator cable options are also available.
The DAC 155eM connectors are coaxial M1.0/M2.3 on an SFP (small form-factor pluggable) transceiver module. Cable options are available, as accessories, for extension to
M1.6/M5.6, and to M1.o/M2.3.
Where protection of the DAC is required (line protection), two DAC plug-ins are
installed.
l
DAC 155oM supports optical Y-cable (TT) and straight-cable protection (TA)
options.
DAC 155eM supports straight-cable only; each DAC 155eM is separately cabled
to the external equipment.
The DACs can be installed in slots 1 to 4 in an INU. For the INUe, they must be
installed only in slots 1 to 6 when NMS transport over the DACs is required (NMS
over MSOH or RSOH). If NMS access is not required (no NMS transport over the
DACs), they may also be installed in slots 1 to 9.
E1/DS1 Backplane
The INU backplane operates as a Digital Cross Connect Switch (DCS) for the E1 or
DS1 tributaries.
l
260-668139-001
Individual E1 or DS1 circuits multiplexed to the INU backplane from the

SDH/SONET frame are cross-connected for transport to a remote site via a RAC
(or another DAC 155oM fiber link), or are locally dropped via a DAC 16x or DAC
4x.
The mapping of individual E1 or DS1 circuits to/from the backplane bus is
configured in the Portal Circuits screen. Bus timeslots (ports) allocated to such
circuits do not need to be in sequence.
The SONET/SDH frame does not have to be fully populated. While STM1/OC3
supports 63xE1 or 84xDS1, only circuits in use need to be mapped.
JULY 2014
101
A signal label option supports selection of bit asynchronous or transparent

virtual tributary (TVT) modes on the E1 or DS1 circuits. Bit asynchronous
should be used for all traffic types except Ethernet, where TVT must be used.
Clocking Options
Two SDH/SONET clocking options are provided, recovered and internal:
l
Recovered clock selects the clock source from the incoming STM1/OC3 signal
(loop timing) and would normally be used where the DAC 155oM/eM is
operating within a wider SDH/SONET network. In the event the clock source is
lost, clocking falls back to the internal clock.
The internal option selects an internally generated clock source. It is typically
used where the DAC is deployed within a simple fiber or coaxial connection
between DACs, or where DAC 155oM is used as a fiber closer in an Eclipse
Super-PDH ring. One end is set to internal clock and the other to recovered.
NMS Transport
Eclipse NMS may be transported within the SDH/SONET MSOH or RSOH Data Communication Channel (DCC) bytes. Selection is made in the DAC 155oM/eM Plug-ins
screen.
l
l
The three bytes (D1 - D3) in the RSOH support a 192 kbps connection.
The nine bytes (D4 - D12) in the MSOH support a 576 kbps connection, though
the maximum used on an Eclipse NMS channel is 512 kbps.
Where the MSOH and RSOH are not being used by other network applications, the
higher speed MSOH should be used.
For an INUe, the DAC must be installed in slots 1 to 6 (NMS connection to the backplane is supported only on these slots).
Co-located INU/INUe Interconnection

At sites where two INUs must be interconnected for E1/DS1 traffic and NMS, the DAC
155oM provides an efficient solution.
l
l
A DAC 155oM is installed in each INU, with an interconnecting optical cable.

One interconnection supports 63xE1 or 84xDS1. A second DAC 155oM can be
installed in each INU to provide more capacity.
MSOH supports the NMS interconnection.
The interconnection can be protected using paired DACs
Interconnection can be extended to additional INUs.
Protection
The DAC 155oM/eM is installed in pairs for hot-standby protection. The protection
partners are installed in slots 1 to 4 in the INU, or slots 1 to 9 in the INUe (except
where NMS access is needed, in which case use slots 1 to 6). One DAC is configured as
102
AVIAT NETWORKS
l
l
Protection switching applies to all modes of operation.

Rx and Tx are switched together so that one DAC or the other is online for Tx
and Rx.
Automatic Protection Switching (APS) in the SDH/SONET environment using Multiplexer Section Protection (MSP) is not supported.
Tributary Protection (optical Y-cable, DAC 155oM only) or Tributary Always On
(straight cables, DAC 155oM, DAC 155eM) are used to connect to customer equipment. For more information, refer to DAC/Tributary Protection on page 211.
The figure below illustrates protected DAC 155oM interconnection together with link
and NPC protection options at a PDH spur in a cellular network. A single INUe supports the protected DAC 155oM and link functions at site A. Similarly one INUe supports the 4xRAC/ODUs and a DAC 16x at site B.
l
At site A the DAC 155oM function is hot-standby protected using two DAC
155oMs with optical Y splitter cables to its Tx and Rx ports.
Paired RAC 30s and ODUs support hot-standby or diversity links, and an NPC
protects the NCC bus clock and power supply functions. One INUe supports up
to 6xRAC/ODUs for 6 non-protected links, or up to 3 protected links.
Figure 1-56. Example Use of 1+1 DAC 155oM
Ethernet over STM1/OC3

Ethernet data is mapped into an STM1 frame in VC-12 (E1 /2.028 Mbit/s) multiples
to a maximum 63x VC-12, to support a maximum data rate (available L1 bandwidth
for Ethernet) of 129 (129.024) Mbit/s.
Ethernet data is mapped into an OC3 frame in VT-1.5 (DS1 / 1.544 Mbit/s) multiples
to a maximum 84x VT-1.5, to support a maximum data rate (available L1 bandwidth
for Ethernet) of 130 (129.696) Mbit/s.
These capacities equate to a nominal L2 throughput of 125 Mbit/s for 1518 byte
frames.
The figure below illustrates provisioning for Ethernet and NxDS1 over anOC3 radio.
260-668139-001
JULY 2014
103
The DAC 155oM/eM card maps 130 Mbit/s / 84xDS1 to 1xOC3.

The available 130 Mbit/s on the NTU data bus is apportioned between Ethernet and
DS1s in 1.5 Mbit/s / 1xDS1 steps.
Ethernet enabled DS1 s together with standard DS1 tributaries, are Link-side connected to an OC3 radio or leased line.
The DS1s within an OC3 are mapped to Ethernet (to the DAC GE3) and to DS1 tributaries (to the DAC 16x) using different bus tributary modes (Transparent Virtual Tributary mode for Ethernet DS1s, and Bit Asynchronous mode for standard DS1s). For
Ethernet, the DS1 tributaries must be configured as one block of DS1s and mapped in
number-order, both locally, and at the remote-end DAC 155oM/eM.
The OC3 interface on the radio can be for unframed/transparent, or framed/channelized OC3.
If more than 16xDS1 is required at the customer interface, another DAC 16x is
installed.
While the DAC 155oM/eM card is a full-featured OC3 terminal multiplexer, meaning
it can connect to 3rd party ADMs, this only applies to the OC3 hierarchy. Where Ethernet data is sent from a DAC 155oM/eM, it must be terminated at the far end with an
DAC 155oM/eM.
For more information on the Ethernet operation over STM1/OC3, refer to the Aviat Networks NTU datasheet or to the NTU Applications Guide.
Figure 1-57. Ethernet and DS1 tributaries over an OC3 Radio
Front Panel Layout

Figure 1-58. DAC 155oM, DAC 155eM Front Panel Layout
No
Item/Label
Description
Plug-in fastener
On-Line LED

Off
104
INU power off
AVIAT NETWORKS
No
Item/Label
Status LED
Line (tributary) Tx
and Rx ports
Description
Green
DAC is online communicating with a remote DAC

155oM
Red
DAC is off-line

Off
INU power off
Green
Normal operation
Orange
flashing

Red
Tributary ports are on an SFP (Small Form-factor Pluggable)

transceiver.
Optical SFP Transceivers: DAC 155oM

Three different transceivers are available; short range or long range 1310nm single
mode, or 850nm multi-mode. All have LC connectors and are designed to meet Class
1 eye safety. See the table for details.
Figure 1-59. Optical Transceiver Modules
For single-mode operation the DAC 155oM is ordered as a long-range or short-range

card. Long range includes the long-range SFP; short range includes the short-range
SFP
For 850nm multi-mode operation the SFP is ordered as an addition. Either the longrange or short-range DAC 155oM is ordered plus the multi-mode SFP option. See DAC
155oM SFP Options on page 105.
Table 1-31. DAC 155oM SFP Options
Optical SFP:
Single Mode
Short Range
S1.S
Single Mode
Long Range
L1.L
Multi Mode
Center Wavelength
1310 nm
1310 nm
850 nm
Maximum launch power
-8 dBm
0 dBm
-4 dBm
Minimum launch power
-15 dBm
-5 dBm
-10 dBm
Maximum optical input

power (saturation)
0 dBm
0 dBm
0 dBm
Minimum optical input

power (sensitivity)
-34 dBm
-35 dBm
-24 dBm
Link distance
To 15 km (9 miles)
with 9/125 m
optical fiber.
To 40 km (23
miles) with 9/125
m optical fiber.
To 2 km / 1.2
miles.
260-668139-001
JULY 2014
105
Optical SFP:
Single Mode
Short Range
S1.S
Single Mode
Long Range
L1.L
Multi Mode
Supply
Included with
short-range DAC
155oM: Part
Number EXD-156001
Included with
long-range DAC
155oM: Part
Number EXD-153001
Multi-mode SFP is
an optional extra.
Part Number 079422661-001.
Electrical SFP Transceiver: DAC 155eM

Interface is compatible with G.703, ES1, CMI encoded signal.
Connector type is coaxial DIN 1.0/2.3, 75 ohm, according to CECC 22230 or DIN
47279.
Typical maximum cable length, 100m (attenuation at 78 MHz must be less than 13.7
dB).
The SFP is included with the DAC 155eM. SFP part number is 079-422663-001.
Figure 1-60. DAC 155eM Transceiver Module
Mapping Modes
Two mapping modes are supported; ITU-T, and KLM; ITU-T for E1 or DS1 mapping,
KLM for E1 mapping only. The tables below list the bus mapping within an
STM1/OC3 frame based on SDH with VC4 or VC3 framing, and for SONET with STS1
framing.
The data applies to all framing options. For TU12/VT-2 (NxE1), bus ports 1 to 63
apply. For a TU11/VT-1.5 selection (NxDS1), bus ports 1 to 84 apply.
Table 1-32. DAC 155oM/eM Bus Tributary Mapping: ITU-T Mode (E1 or DS1 Bus Ports)
106
Eclipse Port (Bus

Trib)
TUG3
TUG2
TU*
SPE
GROUP
VT**
10
AVIAT NETWORKS
Eclipse Port (Bus

Trib)
TUG3
SPE
GROUP
VT**
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
260-668139-001
JULY 2014
TUG2
TU*
107
Eclipse Port (Bus

Trib)
TUG3
TUG2
TU*
SPE
GROUP
VT**
57
58
59
60
61
62
63
(E1)
3
(TU12/VT-2)
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84 (DS1)
4 (TU11/VT-1.5)
Table 1-33. DAC 155oM/eM Bus Tributary Mapping: KLM Mode (E1 Bus Ports)
108
Eclipse Port (Bus

Trib)
TUG3
TUG2
TU12
10
11
12
13
AVIAT NETWORKS
Eclipse Port (Bus

Trib)
TUG3
TUG2
TU12
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
260-668139-001
JULY 2014
109
Eclipse Port (Bus

Trib)
TUG3
TUG2
TU12
60
61
62
63
DAC 2x155e Plug-In

DAC 2x155e supports one or two STM1/STS3, 155Mbit/s electrical tributaries. The trib
interfaces are paired, 75 ohm, unbalanced, BNC female connectors.
Operation is transparent to SDH or SONET frame information:
l
It incorporates a transparent, non-regenerative architecture; there is no internal

clock source / re-synchronization implementation. It is intended for ADM-toADM linking where the ADMs provide the clock recovery and signal re-sync
options.
DAC 2x155e should not installed back-to-back (trib interconnected) over more
than 2 hops of Eclipse (not more than one DAC-DAC repeated hop).
Not more than 16 radio hops (RAC-to-RAC) should be used between the DACs.
(Clock should be regenerated using back-to-back DACs at or before 16 hops to
ensure G.825 wander limits are not exceeded).
BNC male to BNC male tributary cables are available, as accessories; two required per
trib.
DAC 2x155e plugs into slots 1-4 on an INU or slots 1-9 in an INUe.
The SDH electrical line code is CMI (Coded Mark Inversion) as defined in G703.
Figure 1-61. DAC 2x155e
DACs are installed in pairs for hot-standby protection. The protection partners are
installed in slots 1 to 4 in the INU, or slots 1 to 9 in the INUe. One is configured as
110
AVIAT NETWORKS
Protection switching operates on both Tx and/or both Rx tribs. If one Tx trib

fails all Tx tribs are switched. Similarly for Rx. But as Rx and Tx are switched
other online Rx.
When a switch occurs, both Tx and/or Rx tributaries are switched to the

protection partner.
Tributary Always On (straight cables) are used to connect to customer equipment. Ycable protection is not supported. For more information, refer to DAC/Tributary Protection on page 211.
Front Panel Layout

Figure 1-62. DAC 2x155e Front Panel Layout
N- Item/Label
o
Description
Plug-in fastener
Status LED
Trib connectors
Off
INU power off
Green
Normal operation
Orange flashing

Red
Two BNC Tx/RX female connector pairings for 75 ohm

DAC GE3 Plug-in

DAC GE3 is an extended-feature Gig-Ethernet switch.
260-668139-001
JULY 2014
111
Figure 1-63. DAC GE3 Plug-in
Capabilities include:
l
1+1 card protection options
Extended buffering and queuing options
Traffic policing
VLAN tagging
L1 and L2 link aggregation
Ring/ladder network protection with ERP or RSTP
Service OAM
It is particularly suited to:

l
Applications requiring synchronization via Ethernet
Applications requiring highest levels of redundancy
Applications characterized by excessively bursty traffic
Applications requiring link aggregation
Refer to:
112
DAC GE3 Description on page 113
Basic Port Settings on page 116
Advanced Switch Settings on page 116
VLANs on page 117
QoS on page 118
Policing on page 120
Link Aggregation on page 121
Ring Protection on page 122
Synchronous Ethernet on page 123
Ethernet OAM on page 123
Link Status Propagation on page 124
Transport Channel Mode on page 125
AVIAT NETWORKS
Redundancy/Stacking on page 125
DAC GE3 Front Panel on page 125
DAC GE3 Description

The figure below illustrates basic operational blocks. Three RJ-45 10/100/1000Base-T
electrical ports and two SFP (Small Form-factor Pluggable) ports for optical or electrical transceivers connect to an Ethernet switch, which provides bridge/switch and
queuing functions between the user ports and six backplane transport channel ports,
C1 to C6.
The user ports also support direct data packet plane (DPP) connection to a RAC 60E
or RAC 6XE.
l
DPP connections are for RAC 60E/6XE only.
Backplane port connections can be directed to all RAC types.
Backplane port connections can also be directed to DAC 155oM, DAC 155eM,
DAC 3xE3/DS3M, or DAC 16xV2 for Ethernet over TDM applications.
Traffic capacity on backplane ports is configured in multiples of 1.5 or 2 Mbit/s.
The gate array (FPGA) provides signal framing and the bus interface for backplane connection to a link (RAC or DAC). It also enables IFG and Preamble suppression for
backplane connections. On DPP connections IFG and Preamble suppression is performed in the companion RAC 60E/6XE.
The switch analyzes the incoming Ethernet frames for source and destination MAC
addresses and determines the output port/channel over which the frames will be
delivered. The MAC address register supports 16k entries.
Transport channel capacity for Ethernet traffic is enabled in multiples of 1.5 Mbit/s or
2 Mbit/s for selections to a maximum 200 Mbit/s on one channel, or 200 Mbit/s total
using two or more channels.
DPP Ethernet throughputs are not constrained by the backplane bus. Throughputs
can be realized in multiples of 1.5, 2, 45, or 155 Mbit/s.
l
Each DPP connection supports airlink capacities up to the maximum

configured on its RAC60E/6XE, which extends to:
o
366 Mbit/s (55 MHz Ch), ETSI.
320 Mbit/s (50 MHz Ch) or 365 Mbit/s (80 MHz Ch), ANSI.
Multiple RAC links can be supported from one DAC GE3. With the DPP,
these links can be on the same or different INUs.
Ethernet traffic throughputs are frame-size dependent and optimized by IFG and Preamble suppression. For example, a 366 Mbit/s link enables L1 throughputs to 465
Mbit/s for 64 byte frames.
Dynamic frame shaping shapes Ethernet data to available radio link bandwidth to
ensure data bandwidth is always optimally matched to the airlink capacity.
Ethernet traffic can be configured to ride side by side with TDM traffic (mixed mode),
or the full capacity of a link can be dedicated to Ethernet.
In-band NMS options support Eclipse NMS transport within the Ethernet payload,
rather than in link overheads. See Networking and Management Tools on page 266
260-668139-001
JULY 2014
113
DAC GE3 plugs into slots 1-4 on an INU or slots 1-9 on an INUe.
Figure 1-64. DAC GE3 Block Diagram
Features Supported
l
Three RJ-45 10/100/1000Base-T ports
Two ports for optional SFP plug-ins:

o
Optical LC 1000Base-LX 1310 nm single-mode (IEEE 802.3z compliant)
Optical LC 1000Base-ZX 1550 nm single-mode (IEEE 802.3z compliant)
Optical LC 1000Base-SX 850 nm multi-mode (IEEE 802.3z compliant)
Electrical RJ-45 1000Base-T (IEEE 802.3ab compliant)
Six transport channels (backplane ports)
Configurable switch fabric (port-port-channel interconnection)

o
Quality of Service (QoS):

o
802.1p mapping
DiffServ mapping (IPv4, IPv6)
MPLS Exp bits mapping
Priority scheduling for Strict, Deficit Weighted-Round-Robin (DWRR), or

Hybrid (Strict + DWRR)
Eight transmission queues
VLANs
o
VLAN tagging IEEE 802.1Q and IEEE 802.1ad Q-in-Q
VLAN filtering and translation
Port isolation options for private switch instances
Ingress policing, TrTCM color blind
Flow control
Storm control, broadcast and multicast
Frame and burst handling

o
114
Port/channel isolation option enables easy switch partitioning
Flexible allocation of 1500 Kbytes of buffer memory:

n
Guaranteed memory allocated per queue to all enabled ports
Shared memory provided from a pool when guaranteed memory is

insufficient
Memory allocations tunable for high-priority, inverse priority, uniform
AVIAT NETWORKS
o
l
Redundancy
o
1+1 protection using 'dual-feed' or optical Y-cable connections
o
Jumbo frames up to 10 Kbytes bi-directionally
ART (Airlink Recovered Timing) or EDS (Eclipse Distributed Sync) clock

transport over radio links
n
ART clock quality meets G.8262 limits. Requires RAC 60E/6XE.
EDS clock quality meets G.823/824 limits. Supported by all RAC types.
SSM supported clock protection options
Stratum 3 clock hold-over performance
Ring and mesh network protection

o
RSTP, IEEE 802.1w
ERP, ITU-T G.8032v2
Service OAM: 802.1ag connectivity fault management, Y.1731 fault management

and performance monitoring
In-band NMS - support for internal NCC to DAC GE3 NMS bridging/routing
Monitoring
Port and channel status
Performance graphs (RX and TX throughputs and discards per port and
channel)
RMON-1 statistics per port, channel, queue
Diagnostics
o
Port mirroring
Port shutdown
Phased Release of New Features

For information on features targeted for future release, contact Aviat Networks or your
supplier.
Table 1-34. SFP Optical Port Specifications
SFP Type:
Single Mode
1000Base-LX
Single Mode
1000Base-ZX
Multimode
1000Base-SX
Center Wavelength
1310 nm
1550 nm
850 nm
Maximum launch power
-3 dBm
+5 dBm
-4 dBm
Minimum launch power
-9.5 dBm
0 dBm
-9.5 dBm
Maximum optical input

power
-3 dBm
-3 dBm
0 dBm
Minimum optical input

power (sensitivity)
-20 dBm
-24 dBm
-18 dBm
Link distance
To 10 km / 6 miles with
To 70 km /40 miles with
9/125 m optical fiber;
9/125 m optical fiber.
550m / 600 yards with
50/125 m or 62.5/125 m
fiber.
260-668139-001
JULY 2014
Less than 500m. Intended

for local switch-to-switch,
bus extension and
multiprocessing
applications.
115
SFP Type:
Single Mode
1000Base-LX
Single Mode
1000Base-ZX
Multimode
1000Base-SX
Connectors
LC
LC
LC
Supply
SFP is an optional extra,

part number 079-422656001
SFP is an optional extra,

SFP is an optional extra, part
part number 079-422665- number 079-422662-001
001
Safety
Class 1 laser product complies with EN 60825-1
Table 1-35. SFP Electrical Port Specifications

SFP Type:
10/100/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.

NOTE: The electrical SFP does not support SyncE.
Basic Port Settings

User parameters for front-panel and backplane ports include:
l
A port naming field.
A port usage field with options of Normal, DPP, L1LA, Disabled.
l
l
l
l
The setting of a Group ID on DPP ports to ensure correct DPP port matching
with its companion RAC 60E/6XE.
Speed-Duplex settings of auto or manual for speed, and half or full duplex.
A Channel Mode to provide selection of a fast-link-failure detection mechanism
on transport channel (backplane) connections to a RAC. Operation is end-toend over a DAC GE3 link, regardless of the number of radio hops traversed.
Port status to show detection of a valid Ethernet connection with valid framing.
Indication of auto-resolution of speed and duplex for an Auto or 1000 Mbit/s
selection.
Advanced Switch Settings

Parameters include:
l
l
l
Maximum Frame Size setting. Minimum 64 bytes, maximum 10,000 bytes, bidirectional.
Flow Control option to implement use of IEEE 802.3x pause frames.
MAC Address Learning. Address learning is default enabled. A disable option is
provided.
Storm Control option to suppress disruption from broadcast and/or multicast
traffic storms. See Storm Control on page 165.
Buffer Memory Management to provide flexible management of the 1500
kilobytes (kB) of global (total nominal) memory.
o
116
Instead of a fixed buffer size per port there is managed access to the global
memory.
AVIAT NETWORKS
Global memory is split as guaranteed and shared. Guaranteed is provided

per queue for each enabled port (user, DPP, backplane). Shared is a available
as a pool to all enabled ports - for use when guaranteed memory is
insufficient. See Buffer Memory Management on page 166.
Shaper Mode for Ethernet traffic shaping.

o
Shaper maps Ethernet traffic to radio link bandwidth. Options are Maximum
Throughput and Static. Maximum Throughput is the default selection.

but at the expense of up to 3% to 4% lower throughput.
VLANs
The VLAN screen is used to set port cross-connects and advanced VLAN tag options.
l
An internal tagging mechanism is used manage all traffic within the DAC GE3
switch, from switch ingress to egress.
All ingressing traffic (untagged or tagged), whether from a port or channel, is
VLAN tagged for internal management purposes. The internal tag becomes the
outer tag, the tag immediately following the MAC headers.
The internal tag carries standard 802.1Q information, with a tag protocol
identifier (TPID) value of 0x8100 (used to distinguish tagged frames from
untagged).
This tagging mechanism can be used to simply set the cross-connects, or under
Advanced mode, to configure VLAN tagging on frames carried beyond the
switch.
Cross-Connects
The cross-connects determine the association of ports with ports, and ports with channels.
A port/channel isolation option provides a user-friendly alternative to VLANs for isolating port groupings (partitioning for private switch operation).
l
The isolation feature applies to user traffic only. It does not apply to protocol
generated packets (OAM, ERP, RSTP, LACP) where implementation supports
only a single switch-wide context.
VLAN-based cross-connects are established using the VLAN Port VID and membership settings of the switch.
l
260-668139-001
Graphics display the cross-connects established.

Pre-configured (menu-selected) cross-connection modes are provided for easy
user selection.
New modes can also be established by modifying the pre-configured modes, or
by using an Advanced mode screen.
Advanced mode enables a wide range of ingress and egress combinations,
including:
JULY 2014
117
The setting of user-specific port/channel isolation groups and VLAN

transport options.
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.
The tagging of untagged frames only, or the tagging of all frames except
frames with an 8100 or 88a8 TPID.
VID (VLAN ID) replacement, whereby the VID of an incoming 8100 or 88a8
frame is replaced by the DAC GE port VID.
VID translation, whereby the VID of an ingressing customer VLAN is

replaced by a user-specified VID.
The pushing of frames that have been tagged by the DAC GE3 into an
external network.
For general information on VLANs see VLANs on page 178
QoS
Options are provided to prioritize traffic at ingress and to schedule transmission
order.
Ingress Truth and Tag Mapping
Traffic prioritization options are provided for MPLS Exp, DiffServ Code Point (DSCP),
and VLAN Tag 802.1p.
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 truth table illustrates the sequencing.
Figure 1-65. 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.
118
AVIAT NETWORKS
Table 1-36. Default Priority Mapping Table

Traffic Class
Internal Priority Queue 802.1p Tag IP DSCP MPLS EXP
Network Control Q7
56-63
Voice
Q6
48-55
Video
Q5
40-47
Controlled Load Q4
32-39
Excellent Effort Q3
24-31
Spare
Q2
16-23
Background
Q1
8-15
Best Effort
Q0
0-7
Limit Egress
An option is provided to limit (shape) the egress bandwidth (speed) on ports. It sets
the maximum speed from a port. It is used where transmit rate-limiting is desired on
the network transporting Ethernet traffic from the port.
Port Default
Allows traffic on one port or channel to be prioritized over that on other ports or channels. This has relevance where two or more ports (or channels) share a common channel (or port).
Scheduler
The scheduler is responsible for selecting traffic queues for dequeuing (forwarding).
Operation applies on ports that have multiple traffic classes enqueued for transmission.
l
260-668139-001
Queued traffic is forwarded using scheduling options of Strict Priority (SP),

Deficit Weighted Round Robin (DWRR), or a combination of SP with DWRR
(Hybrid).
With Strict priority the scheduler serves a lower priority queue only if all higher
priority queues are empty.
With DWRR the scheduler operates as a weighted round-robin (WRR) with a
deficit counter.
o
The deficit counter mechanism measures and adjusts for packet sizes per
queue.
A deficit counter is maintained per queue such that only packet sizes lower
than the count size are serviced (forwarded) during the round-robin
scheduler visit.
A fixed 'quantum' number is added to the queue counter on each round robin
visit.
A packet or packets are only forwarded when their size is less than the deficit
count number. Packets that exceed the count are held back until the next
visit of the scheduler.
When packet(s) are forwarded, their size is subtracted from the deficit count.
Compared to WRR, it enables fairer treatment of traffic flows that have

different packet sizes.
JULY 2014
119
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.
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.
The scheduler option selected default applies to all traffic classes on the port
(all eight internal priority queues, 0 to 7).
This can be user-configured (customized) to be a mix of any of the three

options, in any order.
Colored icons indicate by size/segment the relative weighting applied to each

traffic class within a queue.
n
Strict is shown with a solid circle, and colored from purple for Q7 to gray
for Q0.
DWRR is shown with a segmented circle, with segment size and color
proportional to the weighting.
Hybrid shows the mix of Strict with DWRR.
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.
Portal default applies highest weighting to the highest traffic class (Q7).
With a customized setting, the resulting configuration can be saved onto

your PC for forwarding to other users.
Figure 1-66. Example Scheduler Windows from the Portal QoS Screen
For general information on QoS, see QoS on page 163
Policing
Traffic policing meters a traffic flow at ingress based on a user-configured traffic profile, and acts on frames that are out-of-profile. Essentially, when the traffic rate
reaches a configured maximum rate, excess traffic is dropped, or remarked with a
lower priority. It is typically used to support Service Level Agreement (SLA) enforcement.
120
AVIAT NETWORKS
The DAC GE3 policer profile uses the RFC 2698 TrTCM meter model (Two rate,
Three Color Metering with marker options). TrTCM meters a traffic stream and
marks its packets according to four parameters-Committed Information Rate
(CIR), Committed Burst Size (CBS), Peak Information Rate (PIR), and Peak
Burst Size (PBS).
The three colors are green, yellow, red:
o
Green, conforming, (not subject to enforcement action) if its rate is at or

below the CIR.
Yellow, partially conforming, if its rate is above the CIR but at or below the
PIR. Typically yellow traffic is forwarded under best-effort using remark
options.
Red, non-conforming, if its rate is above the PIR. Typically red traffic is
dropped, but options are provided to remark.
CBS and PBS are chosen to determine the burst size permitted under CIR and
PIR respectively. They determine the ability to receive a short term burst of
traffic and must be set to a value (bytes) not less than the largest frame size to
be transported.
TrTCM is especially useful where a peak rate must be enforced separately from a
committed aggregate rate.
The enforcement options include the dropping of frames, the remarking (reprioritizing) of frames using QoS 802.1p tagging, or no-change (forward
unmodified).
o
Remarking options support local or preserved. Local applies only within the
DAC GE3 switch; preserved retains the 802.1p remarking beyond the switch.
DAC GE3 policing applies on:

l
A port, to apply on all the traffic entering a user port. One or more ports can be
selected.
On a VLAN tag, or range of tags.
Port-based and/or VLAN based policing can be selected per port.

Operation is 'color-blind' whereby metering is performed without regard to whether or
not frames were metered and marked at a previous step.
Link Aggregation
Layer 1 link aggregation (L1LA), and layer 2 IEEE 802.1AX link aggregation group
(LAG) options are provided.
DAC GE3 L1 link aggregation (L1LA) operates at the physical layer to aggregate the
capacity provided on DPP-connected RAC 60E/6XE member links.
l
260-668139-001
One DAC GE3 supports a maximum 4 member links. DAC GE3s can be
stacked/protected to provide additional member links.
Member links can be configured for adaptive or fixed modulation.
JULY 2014
121
Loading (the distribution of traffic between member links) is automatically rebalanced when a modulation change occurs on a member link. This operation is
hitless/errorless.
Convergence and recovery from individual link failures is superior carrier-grade
- typically less than 5 msec.
Aggregation management overheads apply.
Operation is feature licensed. See Licensing on page 72.

For more information see Ethernet Operation on page 163
Static L2 Link Aggregation
DAC GE3 static link aggregation is IEEE 802.1AX compliant.
l
l
l
It aggregates the capacity provided on DPP and/or backplane connected RAC

60E/6XE member links.
Fixed modulation is required - adaptive modulation is not supported.
Up to 4 front panel ports and 6 backplane (TC) ports can be included in an
aggregation group.
A 'hash' algorithm is used to distribute (load balance) traffic between links. This is
selected from a LAG Hashing menu of:
l
TCP/UDP (Src/Dst UDP or TCP port value) (L4)
IP (SIP/DIP) (L3)
MPLS (MPLS label)
MAC (SA/DA)
Operation is not feature licensed.

For more information see Layer 2 Link Aggregation on page 170.
Dynamic L2 Link Aggregation
LACP (Link Aggregation Control Protocol) is available to provide negotiated end-end
set-up of link members.
l
Operation is IEEE 802.1AX - 2008 compliant to ensure a standardized

information exchange between partner systems
LACP is intended for use between DAC GE3(s) and external LACP compliant
devices to enable higher aggregate user port capacities and protected/stacked
operation on Ethernet ports/modules.
A 'hash' algorithm, as for static L2 link aggregation above, is used to distribute
(load balance) traffic between links.
For more information see Layer 2 Link Aggregation on page 170.
Ring Protection
Two Ethernet ring protection mechanisms are supported, ERP (Ethernet Ring Protection, ITU-T G.8032v2) and RSTP (IEEE 802.1w).
l
122
Under ERP the APS (Automatic Protection Switching) protocol is used to

coordinate protection actions on the ring(s), through which every node in a ring
AVIAT NETWORKS
participates in building adjacency with its neighboring node. To prevent a loop,

one node is declared the ring protection link (RPL).
l
RSTP uses the Spanning Tree Protocol (STP) to provide path redundancy while
preventing loops. It creates a tree that spans all switches in a ring network in
which one ring path is forced into a standby, or blocked state.
For more information see Ring Protection - Ethernet on page 208.
DAC GE3 supports Synchronous Ethernet. Over Eclipse radio links the sync clock is
transported using ART or EDS.
l
ART (Airlink Recovered Timing) requires RAC 60E or RAC 6XE links.
EDS (Eclipse Distributed Sync) is supported on all Eclipse RAC types.
Clock source options are:

l
Port, to source the clock from a DPP-connected RAC or an external source.

o
SyncE-capable ports are RJ-45, and SFP with optical transceiver. The
electrical SFP does not support SyncE.
Multicast Clock, to source the clock from a backplane-connected E1/DS1 trib

from a DAC or RAC.
Master/slave options of auto, manual or local provide selection of the clock
action; Master for sending the clock, Slave for sourcing.
SSM is supported on DAC GE3 and over RAC 60E/6XE ART links.
l
SSM is used to carry information about the quality level (QL) of the source clock
from clock-to-clock within the network.
Where multiple clock sources are available it assists the clock selection process,
with higher quality clocks having precedence.
Should the selected clock-source(s) fail the internal Stratum 3 clock provides
high quality holdover at the clock rate established immediately prior to loss of
the source clock(s).
Two industry-standard SSM option types are supported, Option I, and Option
II. Each supports a defined set of quality levels.
Synchronous operation requires a license; see Feature Licensing on page 73.

For more information on Synchronous Ethernet options and operation, see Synchronous Operation on page 179.
Ethernet OAM
Ethernet OAM (Operation, Administration, and Maintenance) provides a standardized mechanism to detect network faults and provide measures of network performance. It is particularly useful for service operators to secure end-to-end overviews
of the status and health of provided services. Such capabilities can be considered
essential to the policing of service level agreements, and to measure compliance
against MEF Carrier Ethernet guidelines.
For more information see Ethernet OAM on page 190.
260-668139-001
JULY 2014
123
Operation requires a license; see Feature Licensing on page 73
Link Status Propagation

Link Status Propagation (LSP) is used to force a port shutdown at both ends of a DAC
GE3 link in the event of a failure, and to restore port operation at both ends when normal operation returns. Its purpose is to enhance rapid detection of link status by
externally-connected equipment, which rely only on port status (up/down) to itself
respond to changed link status.
l
It is typically used where external 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 is enabled on DAC GE3 at both ends of the link. Applies to DPP and backplane
connected RAC links.
l
Operation is selected per user port. 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.
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.
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.
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 on LACP bundles is not supported.
Timers are provided for LSP operation to avoid frequent switching when a radio link is
working at or close to threshold.
l
124
Link Hold Timer specifies a time to keep a link up after a link failure event. Any
link up event during this time will reset the timer.
o
It is used to limit/prevent frequent switching under transient link failure

events. It holds back the normal fast-switching on protection switch events.
Timer range is 0 to 60 seconds in 1 second increments.
Link Restore Timer specifies a time to wait to declare a link is restored (the link
is kept down until expiry of the timer). Any link failure during this time will
reset the timer.
o
It is used to avoid frequent switching when the link is operating towards the
BER boundary (e.g. 10E-5).
Timer range is 0 to 3600 seconds in 1 second increments.
AVIAT NETWORKS
Transport Channel Mode

These modes optimize the fast-link-failure detection mechanism on backplane-connected (transport channel) links. Operation is end-to-end over a DAC GE3 link, regardless of the number of radio links traversed.
No Failure Detection (ES Compatibility). Used where DAC GE3 is linked to a
legacy DAC ES or IDU ES.
Rapid Failure Detection. Signals a failure condition on the channel if just one
errored 2/1.5 Mbps container is detected. Used for Link Status Propagation. See
above.
Rapid Failure Detection and Protection. Supports continuation of service in the

presence of one or more errored containers. It is used for L1LA when operated
using one transport channel to two physical links. See Ethernet Operation on
page 163
Adaptive Modulation. Similar in operation to Rapid Failure Detection and

Protection, but with the inclusion of pre-notification to signal the onset of a
modulation change.
Redundancy/Stacking
Two DAC GE3 cards can be configured for protected/stacked operation.
The cards are configured for protected operation and interconnected via a
bridging cable installed between ports P5.
Together they provide a switch stack of 8 independently configurable frontpanel ports (4 on each card), and up to 12 backplane transport channels.
Protected operation is provided for user and link connections.
User connections are protected using dual-feed or optical Y-cable options.
Link connections are protected using hot-standby or diversity options via

DPP or backplane connections.
For application and operational data refer to DAC/Ethernet Protection on

page 213.
DAC GE3 Front Panel

Figure 1-67. DAC GE3 Front Panel
Item/Label
Description
Online LED
Indicates which of the two cards in a protected (1+1) configuration

is carrying customer traffic. It applies to transport channel
(backplane) protection only - it indicates which DAC GE3 is online
via the backplane bus.
Status LED
260-668139-001
JULY 2014
125
Item/Label
RJ-45 Ports,
1-3
Description
Off
INU power off
Green
Normal operation
Orange flashing

Red
Critical alarm
Provide 10/100/1000Base-T access. Supports DPP RAC connection

and Synchronous Ethernet input/output.
Each RJ-45 connector includes Activity and Connection LEDs:
Orange LED: Activity LED. LED flashes to indicate Ethernet traffic on
the port. LED does not flash (is solid on) when there is no traffic
activity. (LED is off when the connection status LED is off).
Green LED: Connection status LED. On indicates a valid Ethernet
connection. Off indicates no connection or an invalid connection.
This LED operation is only valid for a 1000 Mbit/s (Gigabit)
connection. For 10/100Base-T, the connection status LED is not
activated.
SFP Ports, 4-5
Small Form-factor Pluggable optical transceiver ports (cages).

SFP transceivers are plugged in for optical or electrical connection.
Only the optical SFP transceivers support Synchronous Ethernet.
For 1+1 optical Y-cable protected operation port 4 is used on each
DAC GE3 (requires optical SFP on each DAC GE3 and 2x optical Ycable).
For protected /stacked operation an interconnection cable is
installed directly into port 5 on both DAC GE3s - no SFP transceiver
required. The cable is available in lengths of 0.5m or 1m.
NCM Plug-in
The NCM (Network Convergence Module) is used to provide an E1/DS1 loop-switch
capability.
Each node in the loop has access to two redundant traffic streams, one for data input
(insert) and one for output (drop).
l
Similarly data is received on both redundant streams and a local selection is

made on which direction to use.
Operation is 'low latency'.
Switching is not hitless.
Revertive or non-revertive operation is configurable.
126
User data inserted into the drop tributary is transmitted on both redundant
streams.
Input stream data can come from any of the Eclipse RAC/Link or tributary DAC
modules, including the DAC E3/DS3M, DAC 155oM, and DAC 155eM mux
cards.
Drops can be made from any of the Eclipse E1/DS1 DAC modules, or the NCM's
front panel tributary ports (8). One Eclipse INUe can support up to 5oE1/63DS1
drops.
AVIAT NETWORKS
mux card links.
NCM cards can be 1+1 protected.
For more information see Ring Protection - E1/DS1 Loop-switch on page 200.
NCM Front Panel

Figure 1-68. NCM Front Panel
Item/Label
Description
Online LED
Indicates which of the two cards in a protected (1+1) configuration is carrying customer
traffic.
Status LED

Off
INU power off
Green
Normal operation
Orange flashing
Configuration not supported, or software / hardware

incompatible
Red
Critical alarm
Trib 1-8
HDR type connector for one to eight E1/DS1 tributary connections.
RJ-45 Ports
10/100/1000Base-T access. Not used with the loop switch option.
AUX Plug-In
The AUX plug-in provides user-configurable auxiliary data channels, and alarm input
and output (I/O) options.
l
l
260-668139-001
Up to three AUX plug-ins may be installed in an INU; six in an INUe.

For an INUe, the AUX must only be installed in slots 1 to 6 when NMS access is
required. If NMS via AUX is not required, the AUX may also be installed in slots
7 to 9.
AUX data circuits cannot be configured on STM1+1E1 links.
JULY 2014
127
Figure 1-69. AUX Plug-in
Auxiliary Interfaces
Three auxiliary interfaces are provided. Each may be 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).
Asynchronous conforms to TIA/EIA-562 (electrically compatible with RS-232 /
V.24 but via a DB-15 connector rather than a DB-9)
Asynchronous baud rates are 1200, 2400, 4800, 9600, or 19200bps with the
following format options:
1 start, 7 data, 1 parity, 2 stop
1 start, 8 data, no parity, 2 stop
Refer to:
l
Auxiliary Applications on page 128
Auxiliary Data and NMS Functions on page 129
Installation and Operation on page 129
Auxiliary Applications
Intended applications are:
128
AVIAT NETWORKS
l
l
Transport of 3rd party NMS (or other data) over an Eclipse network.
Transport of Eclipse NMS over a 3rd party network to a remote Eclipse node or
network.
Auxiliary Data and NMS Functions

Two data function options are provided on a per-port basis, Data and NMS:
Data Option
Customer auxiliary data is transported within one of up to six discrete 64 Kbps link
overhead ports (channels) on each link (RAC or DAC 155oM/eM).
Data type can be configured for asynchronous V.24/RS-232, or synchronous V.11/RS422.
The channels share the same overhead as the NMS and INU-INU internal communication.
At intermediate sites, each channel must be re-directed to the next RAC, DAC 155oM,
or DAC 155eM. (An AUX is not required at intermediate sites).
At the destination site, each channel is directed to the required port on the AUX plugin.
NMS OPtion
l
Eclipse NMS is provided for transport over a 3rd party network to a remote
Eclipse node/network, where it must be ported back in via an AUX.
The data type is default configured for synchronous V.11/RS-422, 64 kbps.
Note that for an STM1+1E1 RAC modulation setting, AUX data or NMS circuits cannot be configured if a wayside circuit is configured, and vice versa.
l
AUX circuits can be configured on an STM1+1E1 link providing no wayside

circuit is configured.
If a wayside circuit is configured, AUX circuits cannot be configured.
Installation and Operation

For all RACs the maximum radio link overhead capacity is 512 kbps, of which a minimum 128 kbps is required for NMS transport. This leaves a maximum 384 kbps (6x
64 kbps) available for auxiliary data transport.
Each end of the l i nk auto-negoti ates on the l i nk overhead to
assi gn the maxi mum avai l abl e capaci ty to NMS. When no auxi l i ary traffi c i s present, the ful l overhead i s assi gned to NMS;
when one channel i s used 448 kbps i s assi gned to NMS; for two
channel s 384 kbps i s assi gned to NMS, and so on to a mi ni mum
128 kbps.
For a DAC 155oM or DAC 155eM, the maximum overhead capacity is 512 kbps, but is
only available when the MSOH (Multiplexer Section Overhead) NMS option is selected. If NMS data is assigned to the RSOH (Regenerator Section Overhead), the total
NMS overhead is 192 kbps, meaning just one auxiliary data channel can be configured.
260-668139-001
JULY 2014
129
Alarm I/O Interfaces

The AUX plug-in provides up to 6 TTL alarm inputs and up to 4 Form C relay outputs. Individual alarm inputs and relay outputs can be named. A severity level can
also be assigned to alarm inputs.
The configuration options are:
l
2 TTL alarm inputs and 4 Form C relay outputs
4 TTL alarm inputs and 2 Form C relay outputs
6 TTL inputs only (default configuration)
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 nominal alarm polling rate is 1 second. Fleeting changes are ignored.
l
l
Input state changes are captured in the event log as an alarm.

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: 60 Volts DC. (Voltage must be restricted to not more than
60 Volts DC to maintain SELV compliance).
Maximum Current 2 Amps on voltages up to 30 Volts DC.
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.
Alarm Application
Events are mapped to outputs:
l
l
l
130
Individual AUX alarm inputs or internal alarm events may be mapped to any
output within the network.
Multiple input or internal events may be mapped to a common output.
Mapping is achieved using IP addressing for the destination node, plus a slot
location and output number for the AUX plug-in.
AVIAT NETWORKS
See Alarms Action Operation on page 261.
AUX Front Panel

Figure 1-70. AUX Front Panel Layout
No
Item/Label
Description
Plug-in
fastener
Status LED

Off
INU power off
Green
Normal operation
Orange flashing

Red
Critical alarm
Alarm I/O
connector
DSUB 15 connector. For pinout and alarm I/O cable data refer to
Appendix D, Eclipse User Manual.
Auxiliary
connector
DSUB 26 connector. For pinout and AUX cable data refer to Appendix
D, Eclipse User Manual.
NPC Plug-In
The NPC provides a protection option for the NCC with backup for TDM bus management (bus clock), and power supply. One NPC can be installed per INU/INUe.
The NPC protects tributary and auxiliary traffic. Alarm I/O is not protected.
l
Protection switching is not hitless for a TDM bus clock failure. Restoration is
within 100 ms, during which time all traffic on the node will be affected.
Protection is hitless for a power supply failure. If the NCC converter or one of its
supply rails fails, the NPC will take over without interruption. And vice versa.
When the TDM bus clock has switched to NPC control, it will not automatically revert
to NCC control on restoration of the NCC. Return to NCC control requires either withdrawal/failure of the NPC, or use of diagnostic commands in the System Controls
screen.
There i s no operati onal need to revert to NCC for bus cl ocki ng.
I f the cl ock i s wi th the NPC, and the NPC cl ock subsequentl y
fai l s, bus cl ocki ng wi l l swi tch to the NCC.
260-668139-001
JULY 2014
131
Figure 1-71. NPC Plug-in
The NPC is field replaceable and hot-swappable (providing the NCC is on line). It
plugs into slot 4 of an INU, or slot 10 of an INUe.
An INU/INUe must always start with a valid NCC installed; the NPC will provide protection only after a node has been powered up.
Figure 1-72. NPC Front Panel Layout
No
Item/Label
Description
Plug-in fastener
Protect LED
Status LED
-48Vdc connector
Unlit
Off-line
Green
On-line (providing the bus clock)

Unlit
INU/INUe power off
Green
Ready to protect
Red
Critical alarm
2-pin polarized D-series 2W2C power connector with captive screw fasteners.
PCC Plug-In
The PCC (Power Converter Card) is used where the site power is +24 Vdc. It converts
+24 Vdc to -56Vdc for connection to the NCC or NPC. I
The PCC is fitted into any option slot in an INU - there is no backplane connection to
the INU backplane.
132
AVIAT NETWORKS
If an NPC is installed, two PCCs are required, one for the NCC, one for the NPC (INUe
is required).
The PCC accepts +24 Vdc, and converts it to -56 Vdc, which is the typical float
voltage for a -48 Vdc battery bank.
Input range: +19V to +36V, with reverse polarity protection
l
Output voltage / current: -56V / 3.6A
Fused input protection: 20A (PCB-mounted fuse)
Output over-current protection < 4.8A
Output over-voltage protection < -59.9V
Thermal protection is included
l
l
Load rating is 200 Watts in an air-conditioned room (max 25oC). This should
be de-rated to 150 Watts for non-air-conditioned. See Power Consumption and
INU Load Maximums on page 34 for nominal card and ODU/IRU 600 power
consumption figures.
When installed in an INUe the INUe should be fitted with the 2RU FAN module
as it provides almost double the air flow of the 1RU FAN modules.
The PCC should be installed next to the FAN to get best air flow cooling.
The PCC can be plugged into any INU/INUe option slot. It is not connected to
the backplane and is its function is not monitored within Portal.
The PCC i s for use wi th standard +24Vdc (-ve grounded) battery-backed power suppl y systems.
The PCC +ve and -ve i nput termi nal s are i sol ated from chassi s
(ground). The -ve i nput i s grounded by the -ve grounded power
suppl y connecti on.
The PCC fuse i s fi tted i n the +ve i nput.
Figure 1-73. PCC
260-668139-001
JULY 2014
133
Figure 1-74. PCC Front Panel
134
No
Item/Label
Description
Plug-in fastener
V Out
2-pin polarized D-series 2W2C power connector with captive

screw fasteners.
Status
LED is on for normal operation. LED is off (not illuminated) if the

output fails or the output voltage is below normal range.
V In
2-pin polarized D-series 2W2C power connector with captive

screw fasteners.
AVIAT NETWORKS
ODUData
Eclipse ODUs are frequency-band specific, but within each band are capacity independent up to their design maximums.
Refer to:
l
ODU Overview on page 135
ODU Accessories, Cables and Cable Kits on page 138
Lightning Arrestor on page 139
Waveguide Flange Data on page 140
Construction and Mounting on page 140
ODU Overview
All ODUs support ATPC.
All ODUs 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.
All ODUs include an internal lightning surge suppressor at their ODU cable connection, compliant to IEC-61000-4-5, Class 5.
All ODUs are warranted to operate to specification over a temperature range of -33 to
+55C (-27o to +1310F), and down to -50 (-580F) non-warranted.
The same RAC type must be installed at both ends of a link. The exception to this
rule is RAC 60E with RAC 6XE for non-CCDP link operation.
ODU 600
l
l
l
ETSI bands 5 to 42 GHz, ANSI bands 5 to 38 GHz, and FCC/Industry Canada

5.8 GHz unlicensed (ISM) band. Fixed or adaptive modulation.
High Tx power with licensed flexible power mode (FPM) to extend maximum Tx
power by 3dB. See FPM feature license EZF-51/56 at Licensing on page 72. (Not
applicable to 5.8 GHz).
Operates with RAC 60E/6XE or RAC 30v3.
Over-air compatible with ODU 600sp or ODU 300hp, when supported from
RAC 60E/6XE or RAC 30v3.
Over-air compatible with IRU 600, which requires RAC 60E/6XE.
ODU 600sp
l
l
260-668139-001
ETSI bands 6 to 23 GHz, fixed or adaptive modulation.

Standard Tx power with licensed flexible power mode (FPM) to extend
maximum Tx power by 3dB. See FPM feature license EZF-51/56 at Licensing on
page 72.
JULY 2014
135
Over-air compatible with ODU 600 when supported from RAC 60E/6XE or
RAC 30v3.
ODU 600T
ODU 600T is purpose-designed for use with the OBU. See Outdoor Branching Unit on
page 142.
ODU 300hp
l
l
ETSI and ANSI bands 6 to 38 GHz, fixed or adaptive modulation.

Over-air compatible with ODU 600, when supported from RAC 60E/6XE or
RAC 30v3.
Over-air compatible with IRU 600, which requires RAC 60E/6XE.
General Data
l
5.8 - 42 GHz
o
Applies to ODU 600 (5.8-42 GHz), ODU 600sp (6-23 GHz), and ODU
300hp (6-38 GHz).
ODUs have a waveguide antenna port designed for direct antenna

attachment via an Eclipse-specific mounting collar. The collar is supplied
with Eclipse antennas.
ODU polarization is determined by the position of a polarization rotator

fitted within the mounting collar.
ODUs are fixed for Tx Hi or Tx Lo.
Two ODUs are connected to a single antenna for hot-standby or frequency

diversity configurations using a direct-mount coupler.
n
For CCDP/XPIC operation an XPOL Direct Mount (XDM) is available for use
with Eclipse Edge series antennas.
n
136
Couplers are available for equal or unequal loss operation. Equal loss is
nominally 3.5/3.5 dB, unequal nominally 1.5/6.5 dB. For more
information see Nominal Losses for ODU Equal and Unequal Couplers
on page 198
The XDM direct-mounts onto the antenna, and the two ODUs directmount onto the XDM. See Co-path Operation on page 232.
A remote ODU mounting kit option is available to flex-link connect to a

standard antenna.
5 GHz
o
Applies to ODU 600.
Antenna connector is Type N female.
Requires remote mounting - the ODU installation kit includes a pole-mount

support bracket. Coax jumper cables for antenna connection are ordered
separately or made up.
ODU is fixed for Tx Hi or Tx Lo.
Two ODUs are connected to a single antenna for hot-standby or frequency

diversity configurations using a coax coupler. They are available for equal or
AVIAT NETWORKS
unequal loss operation. Equal loss is nominally 3.5/3.5 dB. Unequal is

nominally 1.5/6.4 dB.
Table 1-37. Summary ODU Capabilities
Item
ODU 600
ODU 600sp
ODU 300hp
Frequency Bands
5 to 42 GHz ETSI
6 to 23 GHz ETSI
6 to 38 GHz ETSI and

ANSI
10 to 366 Mbps
10 to 366 Mbps
10 to 366 Mbps
5 to 106xE1
5 to 106xE1
5 to 106xE1
4 to 127xDS1
4 to 127xDS1
4 to 127xDS1
1 to 4xDS3
1 to 4xDS3
1 to 4xDS3
2xSTM1/OC3
2xSTM1/OC3
2xSTM1/OC3
RAC 60E, RAC 6XE, for

adaptive or fixed
modulation.

adaptive or fixed
modulation.

adaptive or fixed
modulation.
RAC 30v3 for fixed

modulation.
RAC 30v3 for fixed

modulation.
RAC 30v3 for fixed

modulation.
Fixed: QPSK, 16QAM,

32QAM, 64QAM,
128QAM, or 256QAM
Fixed: QPSK, 16QAM,

32QAM, 64QAM, 128QAM,
or 256QAM
Fixed: QPSK, 16QAM,

32QAM, 64QAM, 128QAM,
or 256QAM
Adaptive: ACM QPSK to

256 QAM.

256 QAM.

256 QAM.
3.5 to 56 MHz ETSI
3.5 to 56 MHz ETSI
3.5 to 56 MHz ETSI
5 to 38 GHz ANSI
5.8 GHz ISM band (USA
& Canada
Airlink Capacity
RAC Compatibility
Modulation Options
Bandwidths
Supported
3.75 to 80 MHz ANSI
3.75 to 80 MHz ANSI
3.75 to 40 MHz ISM

Tx Power
High power and licensed Standard power and

FPM to extend max Tx
licensed FPM to extend
power by 3dB.
max Tx power by 3dB.
High power
Internal lightning
surge suppressor
Yes
Yes
Yes
Nominal Power
Consumption
40W to 50W
30W to 40W
40W 6-11 GHz, 30W 13

to 38 GHz
Mechanical
265 mm (10.5 in) x

265 mm (10.5 in) x
125 mm (5 in)
5 kg (11 lb.)
265 mm (10.5 in) x

265 mm (10.5 in) x
125 mm (5 in)
5 kg (11 lb.)
287mm (11.3 in) x

287mm (11.3 in) x
119mm (4.7 in)
HxWxD
6.4 kg (14 lb.)
More Information
For data on capacity, bandwidth and modulation options by RAC type, refer to Link
Capacity, Throughput and Latency on page 42, and DPP and Backplane Traffic
Assignment on page 42.
For data on power consumption see Power Supply on page 33.
For data on Tx power and control range, Rx threshold, system gain, tuning range and
T/R spacings, refer to the Eclipse datasheets.

5.8 GHz unlicensed band operation with ODU 600 supports easy and fast deployment. With a suitable antenna installation can be 'immediate'.
260-668139-001
JULY 2014
137
Eclipse operation is 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 as the system does not employ DFS - it cannot be
deployed within Europe or any country where DFS is a regulatory requirement for protection of radars.
Unlicensed band operation means sharing the air-space with other operators of unlicensed band links. This may result in a deterioration of operational performance over
time with the introduction of other links in the same geographical area.
l
l
l
IRU 600 5.8 GHz operation is narrow-band, high power; it competes/shares

spectrum with other narrow-band links and with spread-spectrum links.
Transmit power is restricted (max 28 dBm) at the antenna port to ensure
compliance with the FCC 1 Watt rule.
Channel bandwidths 5 to 40 MHz, fixed or adaptive modulation.
Antennas must be approved (FCC or Industry Canada) for 5.8 GHz unlicensed
band. Parabolic antennas must have a maximum gain of not more than 45.9
dBi; flat panel antennas not more than 28 dBi.
ODU Accessories, Cables and Cable Kits

Accessories
Accessories supplied with each ODU include:
l
Earth strap with M6 stainless steel lug
Type-N right angle adapter
Silicone grease, 10z sachet
For 5 GHz ODUs the kit also includes a remote-mount kit.

ODU Cables
Coax cables are available in run lengths from 50 to 300+ meters. Nominal cable
impedance is 50 ohms. Two cable types are available:
l
138
CNT-300
o
Maximum IDU - ODU cable run: 150m.
Center conductor: solid copper
Insulation: foam polyethylene
Shield: aluminum tape + tinned copper braid
Jacket: Polyethylene
Overall diameter: 7.62 mm (0.3)
Minimum bend radius: 22.2 mm (0.88)
Available in lengths of 50, 75, 100, 150, 600m.
CNT-400
o
Maximum IDU - ODU cable run: 300m
Center conductor: solid BCCAI (copper-coated aluminum)
AVIAT NETWORKS
Insulation: foam polyethylene
Shield: aluminum tape + tinned copper braid
Jacket: Polyethylene
Overall diameter: 10.29 mm (0.405)
Minimum bend radius: 25.4 mm (1)
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.
l
It is primarily intended for use at building entry.

o
It can be either bulkhead-mounted on the wall-feed-through plate, or located

just inside the building.
It is also for use at the ODU end when specified by the site owner or operator.
o
All ODUs include an internal arrestor, however in regions that experience

severe lightning strikes an external ODU arrestor should be considered.
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.
Figure 1-75. ULA Kit
260-668139-001
JULY 2014
139
Waveguide Flange Data

Waveguide Flange Data on page 140table below lists antenna port flange types used
with ODU 600 and ODU 300, plus their mating flange options and fastening hardware for remote mount installations.
On 6-38 GHz ODUs the flange styles used 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.
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.
PBR. 4-hole flange with a gasket groove and clear holes.
UDR/PDR flanges are rectangular; UBR/PDR flanges are square.

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 wavegui de attachment i s requi red i n a cascaded i nstal l ati on.
Table 1-38. Waveguide Flange Data
Freq Band
GHz
Radio
Flange
Waveguide
Mating
Flange
Waveguide
Type
Spring
Washers
Reqd
Bolts
Reqd
Bolt
Type
Thread
Spec
Hole
Depth
mm
Bolt Length Required
UDR70
PDR70
WR137
8 x M5
M5x0.8
6H
10
Flange thickness + Hole depth - 2mm
7/8
UDR84
PDR84
WR112
8 x M4
M4x0.7
6H
10/11
UDR100
PDR100
WR90
8 x M4
M4x0.7
6H
13
UBR120
PBR120
WR75
4 x M4
M4x0.7
6H
15
UBR140
PBR140
WR62
4 x M4
M4x0.7
6H
18/23/26
UBR220
PBR220
WR42
4 x M3
M3x0.5
6H
28/32/38
UBR320
PBR320
WR28
4 x M3
M3x0.5
6H
42
UG-383/U
UG-383/U
WR22
4 x M3
M3x0.5
6H
Construction and Mounting

ODU construction comprises:
l
140
Cast aluminum components: alloy 380/ADC-12. Applies to:

o
Base and cover of ODU 600, ODU 600sp
Base only of ODU 300hp
Pressed aluminum cover for ODU 300hp: sheet grade alloy 1050.
Base and cover are passivated, and polyester powder coated.
AVIAT NETWORKS
A compression seal ensures base-to-cover weatherproofing.
SS screws for base-to-cover fastening are A2-50 or A2-70 as per ISO 7045.
SS mounting bolts are A4 70 as per ISO 4017.
ODUs include a carry handle.

ODUs meet the ASTME standard for a 2000 hour salt-spray test, and relevant IEC
(60529/IPX6) standards for wind-driven rain.
Antenna mounting collars are designed for attachment to industry-standard 112 mm
OD (4.5) pipe mounts.
260-668139-001
JULY 2014
141
Outdoor Branching Unit

The OBU provides a trunking solution for split-mount links.
l
One OBU enables 4+0 co-path links through direct attachment of four ODUs
(ODU 600T).
Two OBUs are installed to provide up to 8+0 or 4+4 SD (space diversity)
operation. Four are installed for 8+8 SD.
Each ODU 600T can be configured to provide airlink capacities to 366 Mbit/s.
L1LA (DAC GE3) is used to aggregate the capacity of the co-path links.
o
L1LA on 4+0 operation provides trunk capacities to 1.5+ Gbit/s.
L1LA on 8+0 operation provides trunk capacities to 3+ Gbit/s.
User access to the trunk capacity provided can be on be stacked/protected

DAC GE3s to provide a resilient L2 LAG or LACP connection to external
devices.
The benefits of OBU split-mount trunking compared to traditional all-indoor trunking

radios include:
l
Significantly reduced costs. The cost of installing expensive waveguide and

associated accessories is eliminated. This coupled with the lower-cost radio
hardware can enable savings of many thousands of dollars.
Significantly reduced demands on equipment room real estate and air
conditioning.
Feeder losses are minimized for improved system gain.
The OBU/ODU 600T spl i t-mount trunki ng sol uti on i s known as
Avi at' s STR 600.
I t bri dges the gap between dedi cated hi gh capaci ty N+0 or
N+N al l -i ndoor trunked radi os, and the 2+0 or 2+2 confi gurati ons tradi ti onal l y provi ded wi th coupl er-based spl i tmount i nstal l ati ons.
The tower-mounted OBU incorporates passive circulator and filter-based coupling in a

waterproof enclosure.
l
Narrow-band filters with circulator combining are used to provide low loss (see
below) with good frequency selectivity, T/I performance, and channel reuse.
Band elimination filters (BEF) are included where the required channel plan
puts the highest Tx channel is too close to the lowest Rx channel.
Flexible waveguide (6-11 GHz) or coax (5 GHz) is used to connect the OBU to
its antenna, or antennas.
o
142
For 6-11 GHz OBUs a single WG port is provided on units intended for a
single antenna feed. Two are provided on units intended for dual-pol twoantenna, or dual-pol single antenna working.
AVIAT NETWORKS
For 5 GHz OBUs a single Type-N female connector is provided on units

intended for a single antenna feed. Two are provided on units intended for
dual-polarity links.
Each OBU is factory built and tuned for its intended function. Field adjustment
is not supported.
OBUs meet the ASTME standard for a 2000 hour salt-spray test, and relevant
IEC (60529/IPX6) standards for wind-driven rain.
Unused ODU ports on an OBU must be terminated with a 50 ohm load (Rx and
Tx). A weather-protected termination unit is available from Aviat Networks.
The following end-end OBU insertion losses apply.

l
They apply from an ODU 600T Tx port on the near side OBU to the
corresponding ODU 600T Rx port on the far end OBU, and vice-versa.
These losses must be included in the path calculations for an OBU link.
Figure 1-76. Losses for 4+0 CCDP or ACAP

Frequency Band GHz
Insertion Loss dB
L6
U6
7.7
6.8
6.8 7.4 7.6
11
9.1
Figure 1-77. Losses for 4+0 ACCP

Frequency Band GHz
Insertion Loss dB
L6
U6
8.5
7.8
7.8
11
8.4 8.6 10.5
The ODU 600T is purpose designed for use with the OBU. It is physically identical to
the ODU 600, except it has no waveguide port and no diplexer. Instead the ODU
600T has separate Tx and Rx BMA connectors to engage with matching connectors on
the OBU.
l
No diplexers means one variant of ODU 600T covers each band (single spareable unit per frequency band).
It also means less loss, which translates to higher system gain.
ODU 600T radio channels can be aligned under ACCP, ACAP, CCDP/XPIC, or a
mix of these.
o
RAC 60E (or RAC 6XE in non-XPIC mode) is used for ACCP or ACAP.
RAC 6XE is required for CCDP/XPIC links.
The bands and channel sizes supported are:

o
ETSI: 5, L6/U6, 7/8, 10/11 GHz, with channel sizes of 27.5, 29.65, 40 and
55 MHz.
Selected ANSI bands will be supported at a later SW release.
ACM or fixed-only modulations are supported.
Co-channel and adjacent channel interference performance is within ETSI

specifications.
For more information on the OBU and ODU 600T refer the STR 600 datasheets.
For information on supported channel plans per band and advice on any BEF requirement, contact Aviat Networks or your supplier.
260-668139-001
JULY 2014
143
Figure 1-78. Eclipse OBU with ODUs
The following table illustrates some of the many channel arrangements supported by
the OBU with ODU 600T.
Table 1-39. Example OBU Channel Arrangements
Example
Channel Arrangement
4+0 Adjacent Channel, Co-Polar (ACCP). Channels are arranged on the

same polarity in immediately adjacent channels. Channels can also be
spaced as second-adjacent, such as f1, f3, f5, f7, or as a mix, such as
f1, f2, f5, f6 etc.
4+0 Adjacent Channel, Alternate Polarity. Channels are arranged so
each immediately adjacent channel is on the alternate polarity. A dualpol antenna is required.
8+0 Co-Channel, Dual-Polarity (CCDP) for double-density channel

usage, using two OBUs. Each frequency channel is occupied by two
links, one on the vertical polarity, the other on horizontal. CCDP channels
can also be spaced as second-adjacent, such as f1, f3, f5, f7, or as a
mix, such as f1, f2, f5, f6 etc. XPIC (Cross-Polar Interference Cancellation) is used to eliminate any adverse interference between the V
and H signals.
7+0 over two OBUs using a mix of the above traditional arrangements,
with f1, f3 and f6 on vertical, and f5 and f7 on both pols. Unused ODU
ports on an OBU must be terminated with a 50 ohm load (Rx and Tx).
The following figure illustrates a 4+0 CCDP configuration. For more examples see
OBU Configurations on page 242.
144
AVIAT NETWORKS
Figure 1-79. Example 4+0 CCDP/XPIC Configuration
260-668139-001
JULY 2014
145
IRU 600 Data

The IRU600 is an all-indoor transceiver for North American frequency bands 5.8 to 11
GHz. It includes an RF Section consisting of one or two Radio Frequency Units (RFU)
and an Antenna Coupling Unit (ACU). Refer to:
l
IRU 600 Features on page 146
Frequency Bands on page 147
Radio Frequency Units (RFU) on page 149
Antenna Coupling Unit (ACU) on page 150
Version Compatibility on page 151
RFU Tx Power Calibration on page 152
Power Supply on page 152
ACU Losses on page 153
ACU Waveguide Flange Data on page 154
IRU 600 Features

IRU 600 co-locates with an INU to provide an extremely compact and versatile allindoor radio.
Features and capabilities include:
l
L6 to 11 GHz ANSI licensed frequency bands
5.8 GHz unlicensed frequency band; USA and Canada only
l
l
146
Common RFU for 5.8 GHz unlicensed and L6 licensed for easy transition and
sparing
3.75 to 40 MHz channel bandwidths with adaptive and fixed modulation
options
High system gain with support for both paired and unpaired frequencies with
filter based ACU
1+1 / 2+0 optimized chassis
Expandable to N+N using co-located radios for scalability to ultra high
capacities
Over-air compatible with Eclipse ODU 600 and ODU 300hp (RAC 60E/6XE are
required on both sides of the link)
Two different bands may be used in the same chassis (such as 6 & 11 GHz in a
1+0 repeater)
Lowest power consumption (for an all-indoor radio)
High and standard power options
Tx coaxial switch for hot standby and space diversity configurations
Multiple ACU options
AVIAT NETWORKS
Expansion port in filter-based ACU accommodates parallel paths
Tx monitoring port
Compact dimensions: 2 RU for IRU 600v3; 3 RU for IRU 600v2
NEBS compliant (GR-63-CORE and GR-1089-CORE)
Figure 1-80. IRU 600v3
Frequency Bands
Comprehensive solutions are provided on ANSI licensed bands L6 to 11 GHz, and on
the USA and Canada unlicensed 5.8 GHz (ISM) band.
L6 to 11 GHz Licensed Bands

IRU 600 complies with relevant FCC and Federal (USA), and SRSP (Canada) requirements for frequency bands 6 to 11 GHz.
l
IRU 600v2 is used on licensed bands 7/8 and 10 GHz.
IRU 600v3 is used on 5.8 GHz unlicensed, and L6/U6, 11 GHz licensed.
Features include:
l
l
Adaptive or fixed modulation options.

Ethernet and/or NxDS1 payloads. See Link Capacity, Throughput and Latency
on page 42 for RAC 60E and RAC 6XE.
ACU filter bandwidths:
o
L6/U6 bands: 30 MHz
7/8/11 GHz bands: 40 MHz
10 GHz band: 15 MHz
Filters are spot tuned on a center frequency within the band (within the
filter/band boundaries)
Extensive protection and diversity options. See IRU 600 Configurations on page
154.
For Tx power and system gain figures refer to the Eclipse Packet Node ANSI Datasheets.

IRU 600v3 5.8 GHz unlicensed band operation supports easy and fast deployment.
With a suitable antenna installation can be 'immediate'. Coupled with this is the common 5.8 and L6 RFU design; an installation at 5.8 GHz can be subsequently converted to L6 licensed operation by simply replacing the ACU.
260-668139-001
JULY 2014
147
Eclipse with IRU 600v3 is 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 cannot be
deployed within Europe or any country where DFS is a regulatory requirement for protection of radars.
Features include:
l
l
l
30 MHz wide ACU filters.

o
Filters are spot tuned (pre-tuned) on 5740.5/5805.5 MHz or 5769.5/5834.5

MHz.
With 30 MHz filters just two Tx/Rx pairs are used to provide full coverage of
the band.
Channel bandwidths of 5, 10, 20, or 30 MHz.

Tx and Rx can be paired on different sub-bands (Tx on one 30 MHz sub-band,
RX on the other).
Adaptive or fixed modulation options.
Supports Ethernet and/or NxDS1 payloads with air-link capacities to 189
Mbit/s (30 MHz Ch BW). See Link Capacity, Throughput and Latency on page
42 for RAC 60E and RAC 6XE.
Common 5.8 GHz and L6 RFU supports easy migration from one band to the
other (from unlicensed to licensed and vice-versa).
o
l
l
Extensive protection and diversity options.

Output power is limited to 29 dBm at the antenna port to ensure compliance
with the FCC 1 Watt rule.
When operated as a co-channel (CCDP) pair to a common XPOL antenna,
output power is reduced by 3 dB to comply with the requirement that total
output power to the antenna (ports) does not exceeded 1 Watt (30 dBm).
o
RFUs are retained during migration, but ACU must be replaced (not
retuned).
Co-channel (CCDP) operation enables doubled payload capacity.
Operation can be paired with licensed band links over the same path.
o
Where an existing licensed band link becomes capacity limited, and an

extended or new license is unavailable, new capacity can be provided using a
co-path 5.8 GHz link.
IP/Ethernet traffic can be link aggregated to provide an aggregate link

capacity (single virtual link).
For Tx power and system gain figures refer to the Eclipse Packet Node ANSI
Datasheet.
Operational Limitations and Restrictions

Unlicensed band operation means sharing the air-space with other operators of unlicensed band links. Interference is possible.
l
148
IRU 600 5.8 GHz operation is 'narrow-band'; it competes/shares spectrum with

other narrow-band links and with spread-spectrum links.
AVIAT NETWORKS
Performance could deteriorate over time with the introduction of other links in
the same geographical area.
Antennas must be approved (FCC or Industry Canada) for 5.8 GHz unlicensed
band.
o
At 5.8 GHz IRU 600 has been certified for use with a parabolic antenna with
a maximum gain of 45.9 dBi, or a flat panel antenna with a maximum gain
of 28 dBi.
Contact Aviat Networks or your supplier for more information.
Radio Frequency Units (RFU)

RFUv2 (IRU 600v2)
l
Frequency bands 7/8, 10 GHz licensed.
Operation is fixed for Tx Hi to Tx Lo.
Supports a Tx coaxial switch for MHSB/SD operation via a DIN5 connector.
A front panel SMA connector supports INU (RAC 60E/6XE) connection. A cable
is included with each RFU.
RSSI access is provided on the front panel as meter test-probe points.
The standard Tx power RFU is powered via the INU cable.
The high Tx power RFU is additionally powered via a front-panel D-Sub M/F
2W2 connector for wide-mouth +/- 21 to 60 Vdc supply. Both +ve and -ve pins
are isolated from ground.
o
The power connector (D-Sub M/F 2W2) and cable is identical to that used for
the INU.
The integral DC/DC converter provides polarity protection, under/over

voltage shutdown, over-current limit, and thermal shutdown.
For operation from +24 Vdc supplies, the associated INU/INUe must be
fitted with a PCC to convert +24 Vdc to - 48 Vdc.
RFU dimensions: 1.5 RU, half-width.
Includes two cooling fans, individually alarmed.
RFUv3 (IRU 600v3)

l
Frequency bands 5.8 GHz unlicensed, and L6/U6, 11 GHz licensed.
Operation is SW configurable for Tx Hi or Tx Lo.
Supports a Tx coaxial switch for MHSB/SD operation via a DIN5 connector.
l
l
A front panel SMA connector supports INU (RAC 60E/6XE) connection. A cable
is included with each RFU.
RSSI access is provided on the front panel as meter test-probe points.
Standard and high Tx power operation is supported from the same RFU under
software/license control. See Licensing on page 72.
Both standard and high Tx power operation is powered via the INU cable.
Power consumption is reduced when Tx power output is lowered. Applies to
260-668139-001
JULY 2014
149
ATPC and manual control of Tx power.

RFU dimensions: 1 RU, half-width.
l
l
Four SW-controlled cooling fans, individually alarmed.

A mechanical conversion kit is available to support installation (sparing) into
an IRU 600(v1) or IRU 600v2 chassis.
o
Kit increases height to 1.5 RU to match V1 and V2 mounting points.
Figure 1-81. RFUv3
Tx Coaxial Switch
A Tx coaxial switch is employed on HSB and HSB/SD Tx ACU configurations to support reduced power loss and faster Tx protection switch times.
l
It avoids the losses associated with a Tx coupler/combiner. See ACU Losses

below.
The average recovery time for full MHSB is 50 ms.
o
Full MHSB has the standby Tx on, and connected into a dummy load via
the Tx switch.
MHSB mode increases power consumption as both transmitters are fully active - both
online and offline Tx status is captured in real time. Where lower power consumption
is the priority, a Tx mute option is provided to mute the offline Tx. See Power Consumption and INU Load Maximums on page 34.
l
l
With MHSB operation both A-side and B-side transmit are fully monitored.
With a Tx mute configured on the offline Tx, its Tx status can be monitored
though a health monitoring facility whereby the Tx is turned on, checked and
turned off again. The turn-on period is adjustable between 0 (no health
monitoring) and 240 in 1 hour increments.
Antenna Coupling Unit (ACU)

The ACU filters and routes RF signals between the IRU 600 antenna port(s) and the
RFU module(s). Depending on the application its componentry includes:
l
Isolators and circulators.
Tx and Rx filters.
o
150
On most bands the Tx filter incorporates a Tx monitoring port (SMA

connector) to provide a 30 dB attenuated (nominal) sample for test and
measurement purposes. A label shows the measured ex-factory insertion loss
AVIAT NETWORKS
of the port.
A Tx coaxial switch with Rx coupler for or HSB and HSB/SD configurations.
Diagrams on the back of the ACU cover panel show ACU cabing options.
Labels on the chassis show filter and circulator losses and the total loss (filters, circulators, switch and cables combined).
An optional expansion port allows other co-located radios to connect to the same
waveguide/antenna.
l
Care is needed when multiple carriers are deployed on a common branching

network (same antenna). Intermodulation products resulting from the
combining of two or more Tx frequencies on a common feeder should be 48 MHz
or more above or below each of the Rx frequencies present on the same feeder.
Where the Tx frequencies have the potential to cause intermodulation products
within the 48 MHz specified, the system must be designed and installed to
mitigate the effects of any resulting intermodulation products.
Female SMA connectors are used on the interface to RFU Tx and Rx ports. Antenna
ports and expansion ports utilize standard waveguide flanges - refer to the Eclipse
user manual.
F or 1+1 HSB and HSB/SD confi gurati ons unequal -l oss Rx
coupl ers are standard. I f equal -l oss i s requi red, i t must be speci fi ed at ti me of order.
Version Compatibility
IRU 600v2 and the discontinued IRU 600v1 share a common 3RU chassis. Dimensions and mounting points for V1 and V2 RFUs and ACUs are identical.
IRU 600v3 is housed in a compact 2RU chassis. While the ACU is unique to the V3,
the V3 RFUs can be used in V1 and V2 chassis using a conversion kit (Part No. 179530112-001) .
The following use guidelines apply:
l
260-668139-001
V1 and V2 RFUs are compatible sparing partners EXCEPT for HSB

configurations where the ACU incorporates a coaxial relay Tx switch (IRU
600v2/v3 ACUs). RFU V1 cannot control the Tx coaxial switch. This means
that:
o
V1, V2 RFUs are interchangeable for configurations not using a Tx switch eg.
FD, 2+0, SD split Tx, 1+0. Applies to V1 and V2 ACUs.
In protected HSB or HSB-ready systems with a V1 ACU, a V2 RFU can spare

for a V1.
On V2 ACUs configured to use a Tx switch, the V1 RFU cannot spare for a

V2 RFU.
V3 RFUs can be installed in IRU 600(v1) or IRU 600v2 chassis using a

conversion kit, which increases RFU unit height to match the mounting points
provided for V1 and V2 RFUs.
JULY 2014
151
The V3 RFU (with conversion kit installed) can be used in non-protected and
MHSB or MHSB/SD V1 and V2 chassis.
V1 or V2 RFUs cannot be installed in a V3 chassis.
V1 and V2 ACUs are interchangeable. The V3 ACU is not.

o
A V1 ACU can be installed in a V2 chassis, and vice-versa.
V1 and V2 ACUs cannot be installed in a V3 chassis. Similarly a V3 ACU

cannot be installed in a V1 or V2 chassis.
All IRUs are over-air compatible. For example, a 1+0 IRU 600(v1) may be
linked to a 1+0 IRU 600v2 or IRU 600v3. Similarly, 1+1 MHSB IRU 600(v1)
may be linked to a 1+1 MHSB IRU 600v2 or IRU 600v3. Hybrid configurations
are also supported, such as FD linked to SD split Tx.
RFU Tx Power Calibration

IRU 600s (RFUs and ACU) are normally supplied spot tuned and labeled with a specific Tx insertion loss.
l
During factory alignment, the calibration of the Tx output power control

function is performed at a specified frequency.
A field calibration function for RFU Tx power is provided as a user option.

l
It is a intended 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 (RFU Tx power output is not absolutely flat
across its frequency band).
The aim of this procedure is to recalibrate RFU Tx power setting so that the set
power matches the Tx power measured by precision test equipment.
Power Supply
Power supply options are -48Vdc (+ve ground) or +24 Vdc (-ve ground).
IRU 600v2
l
152
Standard power RFUs are powered by the INU only.

o
-48 Vdc operation is standard; no additional equipment is required.
+24 Vdc operation requires installation of a PCC in the INU. Two are
required if an NPC is also installed.
High Power RFUs are powered by INU plus direct DC input. The direct DC
input is wide-mouth: +/- 21-60 Vdc.
o
AVIAT NETWORKS
IRU 600v3
l
RFUs are powered by the INU only. Applies to both standard and licensed high
power operation.
o
For more information, see Power Supply on page 33.
ACU Losses
The following tables list ACU losses for IRU 600v2 and IRU 600v3.
HSB Configurations use a Tx Switch (relay) and embedded Rx Coupler.
Table 1-40. Additional Tx ACU Loss (Relative to 1+0 Configuration)
Band
5.8 GHz
6L/6H GHz
7/8 GHz
10 GHz
11 GHz
NP (1+0 Loss Reference)
0.0
0.0
0.0
0.0
0.0
MHSB or HSB Ready, Unequal Rx, A Path
0.4
0.4
0.45
0.7
0.7
MHSB or MHSB Ready, Unequal Rx, B Path
0.4
0.4
0.45
0.7
0.7
MHSB or MHSB Ready, Equal Rx, A Path
0.4
0.4
0.45
0.7
0.7
MHSB or MHSB Ready, Equal Rx, B Path
0.4
0.4
0.45
0.7
0.7
MHSB/SD, A Path
0.4
0.4
0.45
0.7
0.7
MHSB/SD, B Path
0.4
0.4
0.45
0.7
0.7
2+0 1 Ant or FD 1 Ant, A Path
0.0
0.0
0.0
0.0
0.0
2+0 1 Ant or FD 1 Ant, B Path
0.3 Typ
0.5 Max
0.3 Typ
0.5 Max
0.4 Typ
0.7 Max
0.4 Typ
0.7 Max
2+0 1 Ant or FD 1 Ant, Expansion, Aexp Path*
0.6 Typ
1.0 Max
0.6 Typ
1.0 Max
0.7 Typ
1.2 Max
0.7 Typ
1.2 Max
2+0 1 Ant or FD 1 Ant, Expansion, Bexp Path*
0 .9 Typ
1.3 Max
0.9 Typ
1.3 Max
1.0 Typ
1.5 Max
1.0 Typ
1.5 Max
1+0 Repeater SD Split Tx 2 Ant, FD/SD (Hybrid)

2 Ant
0.0
0.0
0.0
0.0
0.0
Table 1-41. Additional Rx ACU Loss (Relative to 1+0 Configuration)

Band
5.8 GHz
6L/6H GHz
7/8 GHz
10 GHz
11 GHz
NP (1+0 Loss Reference)
0.0
0.0
0.0
0.0
0.0
MHSB or MHSB Ready, Unequal Rx, A Path
1.15
1.0
1.0
1.2
1.2
MHSB or MHSB Ready, Unequal Rx, B Path
7.35
7.1
7.1
7.3
7.3
MHSB or MHSB Ready, Equal Rx, A Path
3.05
3.0
3.0
3.2
3.2
MHSB or MHSB Ready, Equal Rx, B Path
3.05
3.0
3.0
3.2
3.2
MHSB/SD, A Path
0.0
0.0
0.0
0.0
0.0
MHSB/SD, B Path
0.0
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
0.0
2+0 1 Ant or FD 1 Ant, B Path
0.3 Typ
0.5 Max
0.3 Typ
0.5 Max
0.4 Typ
0.7 Max
0.4 Typ
0.8 Max
260-668139-001
JULY 2014
153
Band
5.8 GHz
6L/6H GHz
7/8 GHz
10 GHz
11 GHz
2+0 1 Ant or FD 1 Ant, Expansion, Aexp Path*
0.6 Typ
1.0 Max
0.6 Typ
1.0 Max
0.7 Typ
1.2 Max
0.7 Typ
1.2 Max
2+0 1 Ant or FD 1 Ant, Expansion, Bexp Path*
0.9 Typ
1.3 Max
0.9 Typ
1.3 Max
1.0 Typ
1.5 Max
1.0 Typ
1.6 Max
1+0 Repeater SD Split Tx 2 Ant, FD/SD (Hybrid)

2 Ant
0.0
0.0
0.0
0.0
0.0
* Expansion Shelf losses include all losses (to/from RFU to Antenna Port) when unit is deployed in the intended field application.
ACU Waveguide Flange Data

The following table provides information on required waveguide flanges, and recommended waveguide type. Data shows flange type for Main, Expansion and Extension
Kit ports.
Table 1-42. ACU Flange Data
Flange screw-fastener data is as follows (no. of screws and screw thread):

l
l
l
l
l
l
CPR137 = 8x #10-32
CMR137 = 8x #6-32
CPR112 = 8x #8-32
CMR112 = 8x #6-32
CPR90 = 8x #8-32
UG39 = 4x #8-32
For IRU 600v2 the thread length is 1/2" for 5.8/6 GHz; 7/16" for 7/8/10/11 GHz.
l
l
The length assumes a flex twist mating flange thickness of 1/4.

This data does not apply to IRU 600v3 as antenna port circulators are not
used.
Flange screw kits for IRU 600v2 are available as an option.
IRU 600 Configurations

The following configurations summarize the wide range of applications supported by
IRU 600.
154
AVIAT NETWORKS
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/route redundancy is available.
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.
1+0 Repeater
Two non-protected RF paths each over its own antenna. This configuration is commonly used in ring network topologies.
HSB (1+1)
An HSB terminal provides two redundant transmission paths using a common
antenna. Only one transmitter is on-air active at any one time. Both Tx/Rx pairs operate on the same frequency.
l
A Tx coaxial switch and Rx coupler is used. The offline Tx can be set to active
(into a dummy load), or Tx muted. On a Tx muted RFU an option allows
periodic, momentary, activation for health monitoring purposes.
On 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.
HSB/SD
Space Diversity is used to reduce the adverse effects of multi-path fading. Two antennas, spatially separated (vertically) are used. The better quality Rx signal is selected
errorlessly between the RACs.
l
260-668139-001
A Tx coaxial switch is used. Associated Tx losses are not more than 0.5 dB per
side. The offline Tx can be set to active (into a dummy load), or Tx muted. On a
JULY 2014
155
Tx muted RFU an option allows periodic, momentary, activation for health

monitoring purposes.
The receive direction does not suffer any additional loss compared to 1+0 receive.
SD (Split Tx)
A Space Diversity Split Transmitter is a variation of HSB/SD where no Tx coaxial
switch is required. Each antenna is connected to its own transmitter/receiver.
FD
Frequency Diversity (FD) provides protection against multi-path fading using a single
antenna. The main and redundant radio paths operate on different frequencies, with
errorless path selection made between the two received signals. There is no transmitter
switch. When operating in the same RF band, Tx high RFUs should be at one end of
the link, Tx low at the other.
2+2 FD
An FD system can be expanded to 2+2 using Main and Expansion operation. Two
IRU 600 chassis are connected via their ACUs to provide two FD systems over a
single antenna. The expansion ACU is connected to the main ACU, which in turn connects to the antenna.
FD/SD
FD/SD (also known as Hybrid diversity) provides additional path fading protection
for special conditions and equipment failure protection.
156
AVIAT NETWORKS
2+0 Single Antenna

Two separate non-protected RF links, on different frequencies, operate over the same
path using a common antenna at each end. A single IRU 600 is used at each end.
Links may be configured as ACCP, ACAP or CCDP.
N+N Adjacent Channel Operation
Links may be operated on adjacent channels (first adjacent) using ACAP (Alternate
Channel Alternate Polarization).
Links operated on non-adjacent channels are polarization agnostic; ACCP may be
used (Alternate Channel Co-Polarization).
N+N Co-Channel Operation (CCDP / XPIC)
CCDP (Co-Channel Dual Polarization) permits installation of two links over the same
path, on the same frequency channel. One link is operated on the vertical polarization,
the other on the horizontal. Requires the XPIC (Cross Polarization Interference Cancellation) capable RAC 6XE plug-in.
2+2 Operation
2+2 (protected 2+0) uses 'Main and Expansion operation. Two IRU 600 chassis are
connected via their ACUs to provide two 1+1 systems over a single antenna. The
expansion ACU is connected to the main ACU, which in turn connects to the antenna.
260-668139-001
JULY 2014
157
ATPC Operation
Automatic Transmit Power Control (ATPC) is an optional Eclipse RAC setting - except
for RAC 60E or RAC 6XE when configured 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
Benefits of ATPC on page 158
ATPC Operation on page 158
Interference and ATPC on page 159
Setting ATPC on page 160
FCC Implementation on page 160
Benefits of ATPC
ATPC supports greater re-use of radio channels in a network. If a given link can still
operate within suitable receive thresholds with a lower transmitted power level, that
link will pose less risk of interference to other links running in co or adjacent channels. This enables a higher level of channel reuse. For ATPC to be effective, all links in
the same geographic area must be running ATPC.
In areas that have high link densities, a license authority (regulator) may include
within an operating license the requirement for ATPC and the maximum transmit
power permitted under ATPC control.
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 partner terminal. The terminals analyze this information, and each adjusts its Tx power to
maintain the target fade margin settings.
158
AVIAT NETWORKS
ATPC calculates the remote terminal's fade margin based on current RSL and receiver/modulation specifications. If a path fade reduces the fade margin on the remote terminal, 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.
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.
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.
ATPC power changes can occur at a rate of 6 dB/second to provide
compensation for rapid fading conditions.
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 interference. 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 terminal 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.
When both RSL and SNR are within range, no ATPC action is taken.
260-668139-001
When the RSL is within range but the SNR is below range, SNR will initiate an
increase in remote Tx power.
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.
JULY 2014
159
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 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
antenna discrimination (beamwidth) and good frequency planning will exclude co and
adjacent channel RSL interferers.
ATPC should not be selected for co-channel XPIC operation. The exception is RAC
6XE XPIC operation with adaptive modulation (ACM): ATPC is a required setting for
ACM.
ATPC shoul d not be used on CCDP/XPI C l i nks where the V+H
antenna cross-pol di scri mi nati on (XPD) i s l ess than 25 dB, or
the l i nk path i s l ong/di ffi cul t. Si mi l arl y, adapti ve modul ati on
(whi ch defaul t requi res ATPC) shoul d not be used on such
l i nks. (Li nk XPD i s shown i n the Portal l i nk performance
screen).
ATPC shoul d not be used where there i s a measurabl e RSL (an
i nterferi ng si gnal ) when the remote-end Tx i s muted.
Setting ATPC
When setting ATPC parameters, the objective is to check that Remote Fade Margin
and Detected Tx Power are within +/- 3 dB of the planned figures for the link, and
that there is appropriate Tx Power headroom for correct ATPC operation.
Prevailing path conditions must be typical during setup, that is, not subject to rain
fade or other fade conditions, and assumes the Target Fade Margin is the primary
driver for establishing the settings.
Where a link license specifies a maximum Tx power, the maximum Tx power setting
for ATPC must be set no higher than the licensed maximum.
FCC Implementation
Eclipse supports selection of FCC compliant ATPC for use when a coordinated Tx
power less than the maximum Tx power under ATPC is appoved.
1RSSI filter bandwidth is not a function of, nor does it affect receiver adjacent channel
C/I performance. Eclipse complies with relevant ETSI and FCC co and adjacent channel requirements.
160
AVIAT NETWORKS
F CC Compl i ant ATPC sel ecti on appl i es onl y to l i nk operati on

under F CC j uri sdi cti on where the coordi nati on noti ce permi ts a
coordi nated Tx power l ess than the maxi mum Tx power under
ATPC.
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 victim 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.
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.
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.
At least a 10 dB fade must occur before the Coordinated Transmit Power is exceeded.
In order to claim a coordinated Tx power less than the maximum Tx power, certain
restrictions 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.
l
l
l
The annual restrictions set out the time permitted (as an annual percentage)
above the coordinated Tx Power.
These time percentages are determined using applicable reliability calculations.
The process determines the lowest permitted coordinated Tx power (within a
range of 0 to 10 dB below maximum Tx power).
The timer function ensures Tx power under ATPC control is not sustained at
maximum power for more than five continuous minutes so as to prevent a
condition from holding Tx power at the maximum for an extended period of
time without advice to the link/network operator.
ATPC operation must be RSL based only.
Within Eclipse this process is supported by an FCC Compliant option, which is

made available whenever ATPC is enabled. When selected it enables:
l
A five minute timer function. When maximum Tx power is sustained for 5

continuous minutes, Tx power is momentarily reduced by 10 dB and an
informational event of "ATPC Pwr temporarily reduced by 10 dB" is logged in
the management system Events Browser.
o
260-668139-001
If operating conditions continue to cause the link to operate at maximum Tx

power for 5 consecutive minutes, the process of reducing maximum Tx power
by 10dB and logging an informational event is applied again.
JULY 2014
161
If the Tx power is reduced from maximum during a 5 minute countdown,

the timer function is reset.
RSL-only ATPC.
Note that:
l
l
l
FCC Compliant need only be selected when a coordinated power less than
max power has been approved for the link.
If the coordinated power = max power, ATPC is not required.
If coordinated power = max power and you still wish to use ATPC, you do not
need to select FCC Compliant.
Where fading events, such as rain fading, can cause maximum Tx power periods
much longer than five continuous minutes, the path might best be coordinated at
maximum Tx power.
Refer to the Eclipse User Manual for operating guidelines and examples.
162
AVIAT NETWORKS
Ethernet Operation
This section provides data additional to that provided under DAC GE3 Plug-in on
page 111 for QoS, storm control, buffer management, link aggregation, VLANs, synchronous operation, and Ethernet OAM. Refer to:
l
QoS on page 163
Storm Control on page 165
Buffer Memory Management on page 166
Link Aggregation on page 168
VLANs on page 178
Synchronous Operation on page 179
Ethernet OAM on page 190
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 customer'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.
Generally, where throughput is restricted traffic is buffered. It is how traffic in a buffer
is queued and prioritized for transmission that concerns QoS congestion management
and avoidance. The most common Ethernet tools for this purpose are prioritization
and scheduling, where priority tagged traffic is queued and scheduled for transmission using one or more priority management schemes such as strict or weightedround-robin (WRR).
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 Ecl i pse confi gurati ons where l i nk capaci ty i s modi fi ed by adapti ve modul ati on, or by redundancy wi thi n a l i nk aggregated group.
Queuing
Traffic is typically queued within port buffers using port and tag prioritization techniques.
260-668139-001
JULY 2014
163
With simple port prioritization, traffic on one physical port is prioritized over that on
another. It is typically used where two or more ports share a common radio channel.
It acts on all ingressing traffic, whether tagged or untagged.
Tag prioritization prioritizes ingressing Ethernet traffic 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 eightlevel prioritization (0 to 7, with 7 the highest). The use of the prioritization bits
is defined in IEEE 802.1p.
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.
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).
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.
Advanced L2 switches 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.
DAC GE3 can be configured to prioritize on CoS, DSCP, or MPLS Exp tagged traffic
using eight levels of prioritization. Incoming tagged frames are read and each frame is
queued and forwarded according to its tag priority level, and on the prioritization
mapping (scheduling) applied.
Scheduling
Scheduling is about how traffic within a queue is managed for forwarding over a link.
Scheduling can be strict or weighted, or a mixture of both.
l
The scheduler is responsible for selecting traffic queues for dequeuing

(forwarding). Operation applies on ports that have multiple traffic classes
(priorities) enqueued for transmission.
With DAC GE3, queued traffic is forwarded using scheduling options of Strict
Priority (SP), Deficit Weighted Round Robin (DWRR), or a combination of SP
with DWRR (Hybrid).
o
Strict priority serves a lower priority queue only if all higher priority queues
are empty.
DWRR operates as a weighted round-robin (WRR) with a deficit counter.
Hybrid enables a combination of strict with DWRR.
For more information see QoS on page 118
164
AVIAT NETWORKS
Flow Control
Flow control is a mechanism to throttle back data from sending devices to reduce
demands on available Ethernet bandwidth.
Under flow control a "high water" point is established in the buffer. When triggered,
an 802.3x pause frame is sent back towards the source Ethernet address to force the
sending device to reduce the rate at which it is forwarding traffic. This supports graceful reduction of traffic and results in bandwidth being used more efficiently. For it to
be fully effective, all devices in the end-to-end path must support flow control.
Figure 1-82. Flow Control Mechanism
Storm Control
A storm occurs when traffic floods the available bandwidth, thereby degrading network performance. The storm control function suppresses such degradation when
caused by broadcast, multicast and/or unknown unicast storms. (Unknown unicast
traffic consists of unicast packets with unknown destination MAC addresses).
It operates by monitoring the ingressing rate of all selected traffic type(s) per
port/channel. When the rate total reaches the storm traffic rate % (control threshold),
such traffic is dropped until the rate falls below the threshold. Storm control % is
gauged against the total available bandwidth of the port/TC.
l
l
l
The storm traffic rate % setting is switch-wide, it applies to all enabled DAC
GE3 ports and transport channels (TC). The % per is gauged against its total
available port/TC bandwidth.
The default setting is 100%, which equates to no storm control.
For user ports the available BW is the negotiated or fixed port speed; 1000
Mbps, 100 Mbps, or 10 Mbps.
For DPP ports the available bandwidth is modified by the capacity for DPP
traffic on the RAC 60E/6XE link.
For TC (backplane) ports the available bandwidth is modified by the configured
transport channel capacity.
This means that for link applications the control threshold is always established on
the lesser of the BW available on the DPP/TC and the negotiated/fixed user port
speed.
l
260-668139-001
For a 1000 Mbps user port, the DPP or TC capacity will always determine the
control BW.
For a 100 or 10 Mbps user port, it will be lesser of the port BW and the
configured DPP/TC capacity.
JULY 2014
165
Where storm control is to be used, an appropriate % setting can be gauged by looking

at your network and determining a normal percent max of broadcast and multicast
traffic (RMON stats), and setting a comfortable margin above that.
Buffer Memory Management

On DAC GE3 a buffer management capability is provided to all switch ports to enable
flexible management of a nominal 1500 kilobytes (kB) global memory.
Availability of memory for egress port queues and the tail-drop profile determines how
a queue is forwarded during burst conditions. (Pre-allocated buffers are provided for
ingress processing, from which frames are pushed immediately into an egress queue).
Using Portal, buffer memory is allocated using per-queue and per-port options. The following rules and usage recommendations apply:
l
166
Instead of a fixed buffer size per port there is managed access to total available
memory using concepts of guaranteed and shared memory.
o
Guaranteed ensures there is always a set minimum amount of memory

available per queue (traffic class), Qo to Q7, for all enabled ports (user, DPP,
backplane).
Where this per-queue guaranteed memory is insufficient to support a traffic

burst, more memory is assigned from the shared memory pool.
The guaranteed and shared capability is designed to maximize use of the

buffers while providing user-flexibility to select the amount of buffering per
port.
The amount of shared memory is primarily dependent on the number of enabled

ports the more ports in use, the less memory available from the shared pool.
For each enabled port (user, DPP, and backplane) there is guaranteed access to
a minimum amount of memory by traffic class (Q0 to Q7).
o
When there is no traffic for a particular queue, its guaranteed memory

allotment is made available within the shared memory pool (subject to a
global buffer share limit).
Ingressing class-less traffic is assigned a queue (Q0 to Q7) based on the

default priority setting for the port. Port default is set in the QoS screen.
There are two mechanisms within Portal for tuning memory resource, Buffer
Size Profile, and Per Queue Guaranteed Buffer.
The Buffer Size Profile establishes the amount of guaranteed memory available
to a port, and a port limit a port maximum for combined guaranteed and
shared memory.
o
The profile options are Large (most guaranteed memory per queue and
highest port limit), Medium, and Small (least memory per queue and lowest
port limit).
The port limit (guaranteed + shared) is dependent on the buffer size profile,
and also on the number of enabled ports.
Additionally, using the Per Queue Guaranteed Buffer, the distribution of

guaranteed resources across the queues is tunable based on three profiles;
AVIAT NETWORKS
Priority, Uniform, Inverse Priority. These are configured on a per switch basis
(profiles apply to all ports, user, DPP, backplane) to provide additional
flexibility on buffer resource allocation.
o
It enables modification of the distribution of per-port guaranteed memory

between the queues (Q0 to Q7).
Priority gives more weight (more memory) to higher priority traffic; Uniform
applies equal weighting (equal memory) to all traffic classes; Inverse Priority
gives more weight to lower priority traffic. The figure below illustrates perqueue distribution of guaranteed memory.
With Uniform each queue is allocated 1/8th (12.5%) of the available total.
For Priority, Q0 is allocated 6.3% of the total, rising to 18.8% for Q7; for
inverse priority Q0 is allocated 18.8% of the total, falling to 6.3% for Q7.
Figure 1-83. Buffer Resource Allocation to Queues
260-668139-001
The options of Buffer Size Profile and Per Queue Guaranteed Buffer are used to
differentiate for burst accommodation (congestion management), and latency:
o
The more memory, the higher the latency but least dropped frames during
periods of congestion.
The less memory, the lower the latency but the higher the potential for
dropped frames during congestion.
The Per Queue Guaranteed Buffer priority setting (all ports) is used to tailor
the switch for majority traffic priority type or left as uniform (default).
n
Use Priority if the higher traffic classes carry relatively latency-tolerant

traffic, for which burst absorption is a primary requirement.
Use Inverse Priority if the lower traffic classes carry relatively latencytolerant traffic, for which burst absorption is a primary requirement. Less
guaranteed memory, and hence lower latency, is provided for the higher
traffic classes.
The Buffer Size Profile is used to tune per-port for best burst accommodation.
Large is the default setting.
Ethernet throughput is typically limited by the radio link capacity. Ethernet

user ports on the other hand can accept rates to 1 Gbit/s. Therefore to best
accommodate bursts when two or more user ports are enabled, maximum
buffer memory (Large or Medium) should be assigned to DPP and/or
backplane ports, and less (Medium or Small) to the user ports.
JULY 2014
167
Buffer management opti ons are i ndependent of the DAC GE3

QoS opti ons. F or opti mal traffi c forwardi ng both must be consi dered.
Link Aggregation
Link aggregation provides a solution where more traffic capacity is needed than can be
transported over one physical link. Two or more links are aggregated to provide one
logical link with a capacity that is the sum of the individual member links. This feature is particularly useful for wireless transmission systems where multiple radio links
must be used in parallel to achieve capacities to 1 Gbit/s.
Link aggregation also supports data redundancy. If one member link fails, its traffic is
recovered on the remaining link(s). If the remaining link(s) do not have sufficient data
bandwidth to transport all incident traffic demands, traffic (frames) will be dropped.
However, traffic prioritization options can be used to ensure all priority traffic continues to get through. This link aggregation redundancy feature is sometimes termed
n+0 protection.
With the DAC GE3 the Eclipse Packet Node uniquely supports link aggregation
options for Layer 2 (L2) and Layer 1 (L1). A primary difference is that with L2 all packets associated with a particular end-end session are sent over just one of the member
links, whereas with L1 the packets are split across all member links.
Operational Overview:
l
168
L1 link aggregation (L1LA) is Eclipse radio-link specific. One L1LA instance can
be established per DAC GE3 or protected/stacked DAC GE3 pair. The DPP is
used to connect to partner RACs.
Static L2 link aggregation (LAG) is supported over Eclipse radio links and on
front-panel connections to external LAG-compliant devices. RAC connection can
be DPP and/or channel. Multiple instances (trunks) can be established ber DAC
GE3.
Dynamic L2 link aggregation employs LACP (Link Aggregation Control
Protocol). It is intended for use on link connections to external LACP-compliant
devices. Multiple instances (trunks) can be established ber DAC GE3.
The segment-based traffic splitting of L1 link aggregation supports optimum
load balancing regardless of the throughput demands of individual user
connections. Whether there is one, a few, or many concurrent sessions, the
traffic is always split accurately between member links based on the configured
capacity of the links.
The session-based splitting of L2 link aggregation onto member links generally
provides good load balancing.
L1LA supports higher burst speeds than L2 as session throughputs can burst to
the aggregated total.
L1LA has higher overheads compared to L2 (more payload capacity is used in
the management of L1 link aggregation).
L1LA is sympathetic to adaptive modulation changes. Operation is
hitless/errorless on modulation change.
AVIAT NETWORKS
If an L1 member link is lost its traffic is directed onto the remaining link(s)
within the group, whereupon all traffic is momentarily affected. When the failed
link is restored to service, all traffic is again momentarily affected.
If an L2 member link is lost its sessions are directed onto the remaining link(s)
within the group, whereupon only the redirected sessions are momentarily
affected. When the failed link is restored to service, existing sessions are not
affected.
Diagrams:
Where example link aggregation diagrams include references to Airlink and Effective
capacity, these have the following meaning:
l
Airlink capacity represents the user-configured radio link capacity. All capacity
may be dedicated to Ethernet, or to Ethernet and Nx E1/DS1.
Effective capacity represents the aggregate capacity available for Ethernet
transport at the user port before application of IFG and Preamble Suppression.
Split-mount or All-indoor
The diagrams show split-mount operation; RACs with ODUs. All-indoor operation
with the IRU 600 also applies, though ACAP or ACCP operation may be preferred over
CCDP/XPIC as they permit use of a common waveguide feeder (CCDP/XPIC requires
two waveguide installations - one for each polarization).
References to ACAP, ACCP, CCDP/XPIC have the following meaning:
ACAP: Alternate Channel Alternate Polarization (V and H). ACAP should be used
where links are configured on 1st adjacent channels.
l
ODUs: Use XDM (XPOL Direct Mount) with Edge series antenna. XDM Tx and
Rx losses are nominally 0 dB.
IRU 600: ACU configured for two 1+0 links. Requires separate waveguide runs
to dual-pol antenna V and H feeds. ACU Tx and Rx losses are nominally 0 dB.
ACCP: Alternate Channel Co-Polar (V or H). ACCP can be used on 2nd adjacent and
wider channel spacings.
l
ODUs: Use equal-loss OCU (ODU Coupler Unit) with Eclipse direct-mount
antennas. OCU losses are nominally 3.5 dB per Tx and Rx side.
IRU 600: ACU configured for 2+0 operation to one antenna (single waveguide
run). ACU Tx and Rx losses are minimal; nominally 0 dB on A path and 0.3 dB
on B path.
CCDP/XPIC: Co-Channel Dual Polarization (V and H) with Cross Polar Interference

Cancellation
l
260-668139-001
ODUs: Use XDM (XPOL Direct Mount) with Edge series antenna. XDM Tx and
Rx losses are nominally 0 dB.
IRU 600: ACU configured for two 1+0 links. Requires separate waveguide runs
to dual-pol antenna V and H feeds. ACU Tx and Rx losses are nominally 0 dB.
JULY 2014
169
Frequency Diverse Operation

The 'n+0 protection' afforded under link aggregation may be enhanced by using a frequency diverse configuration to help minimize the impact of fading. Under normal
conditions all links within the link aggregated group are traffic carrying. When one
member link fails, the other(s) remain online to provide connection protection. This
mechanism can be used to advantage on paths subject to fading by configuring the
links on channels with sufficient separation to provide a frequency diverse element.
Unlike normal diversity link operation, path switching is not hitless/errorless, but you
do get 2x the Ethernet capacity of a standard diversity link for +99.5% over time.
Link hold and restore timer settings on the DAC GE3 can be used to avoid frequent
switching when the link is operating towards the BER boundary (e.g. 10E-5).

Under a common interface, multiple Ethernet interfaces (links) are grouped together
as a link aggregation group (LAG).
l
Static (fixed) assignment or dynamic (negotiated) assignment of LAG (member)

links and their capacity are supported.
Layer 2 link aggregation is not feature licensed.
DAC GE3 supports 802.1AX-compliant static LAG and dynamic LAG options.
Static LAG
Static LAG operation is intended (primarily) for use over Eclipse links - it aggregates
the capacity provided on multiple co-path links. DAC GE3 is required at both ends of
the LAG.
l
170
Each Eclipse link must have the same airlink capacity

(modulation/bandwidth). The capacity assigned to Ethernet on each of the
links can be different, but this may affect load balancing.
Adaptive modulation on the member links is not supported.
Up to 4 front panel ports and 6 backplane (TC) ports can be included in an
aggregation group.
Load balancing ensures traffic on the aggregate port is distributed as evenly as
possible over the member links.
A 'hash' algorithm is used to distribute (load balance) traffic between links - it
controls the distribution of traffic on LAG ports.
The hash algorithm (user selectable) takes one or more of the following modes
into account. These determine the data value(s) to be used by the algorithm.
o
IP (SIP/DIP) (L3)
MPLS (MPLS label)
MAC (SA/DA)
The L4 and L3 components of the hash algorithm mean that load balancing is
supported on traffic streams between routers.
AVIAT NETWORKS
Typical hash mode selections are:

o
IP
IP add TCP/UDP
IP add MAC
IP add TCP/UDP add MAC
MPLS
MPLS add MAC
The diagram below illustrates aggregation of four Eclipse links configured as two
CCDP/XPIC pairs.
l
All RACs are DPP-connected. One or more backplane connections can also be
used, though total Ethernet capacity via the backplane cannot exceed 200
Mbit/s.
Two XPOL antennas are used. Insertion losses on the XPOL couplers are
nominally zero. Use of a single XPOL antenna is an option in conjunction with
externally-mounted combiners, though insertion losses are nominally 3.5 dB per
side (equal-loss combiner) for a 7 dB total per link.
All four member links are configured for same channel bandwidth and fixed
modulation.
E1/DS1 traffic (DAC 16x/4x) can also be sent over one or more member links.
Figure 1-84. DAC GE3 Static LAG: 4+0, 2x CCDP/XPIC
Dynamic LAG
LACP (Link Aggregation Control Protocol) is employed to provide negotiated end-end
aggregation of link members between devices.
LACP provides a standardized means for exchanging information between partner systems on a link to allow their Link Aggregation Control instances to reach agreement
on the identity of the link aggregation group to which the link belongs, move the link
to that link aggregation group, and enable its transmission and reception functions in
an orderly manner (IEEE 802.1AX - 2008).
LACP is intended for use between DAC GE3(s) and external LACP compliant devices
to enable higher aggregate user port capacities and protected/stacked operation on
Ethernet ports/modules.
All member links must have the same data rate i.e. a physical port speed setting of
10, 100, or 1000Base-T.
260-668139-001
JULY 2014
171
LACP negotiates automatic bundling of links through transmission of LACP frames

called Link Aggregation Control Packet Data Units (LACPDUs).
l
LACPDUs sent by the initiating (Actor) end advises what it knows about its
own state and that of its intended Partner. From this the Actor and Partner
determine the action to take on combining multiple links into a single logical
link.
LACP can be configured in active or passive modes. In active mode it will
always send LACPDUs over the member links. In passive mode it acts as "speak
when spoken to".
o
Periodic transmissions occur if either Actor or Partner is configured for active

LACP.
Periodic transmissions occur at either a slow or fast transmission rate

depending on the configured LACP timeout preference (long or short) of the
Partner system.
The protocol also transmits LACPDUs when there is a Need To Transmit

(NTT) something to its partner, such as when the Actors state changes or
when it is apparent from the Partners LACPDUs that it does not know the
Actors current state.
Machine functions control the grouping of links (ports) onto an aggregator port,
the de-selection of failed links, and the re-establishment of links returned to
service. They also control the distribution and collection of frames to/from
member links.
Load balancing ensures traffic on the aggregate port is distributed as evenly as
possible over the member links.
o
A 'hash' algorithm is used to distribute (load balance) traffic between links.
The hash algorithm (user selectable) takes one or more of the following
modes into account. These determine the data value(s) to be used by the
algorithm.
n
IP (SIP/DIP) (L3)
MPLS (MPLS label)
MAC (SA/DA)
The figure below illustrates use of LACP between an external switch/router and paired
(stacked) DAC GE3s to derive link aggregation, and associated path and Ethernet
module protection.
l
172
The DAC GE3 cards are configured as a protected/stacked pair, with a

protection/stacking cable installed between ports P5. For more information on
DAC GE3 protected operation see DAC/Ethernet Protection on page 213
Under LACP, link aggregation is established via the cabled connections between
the DAC GE3s and the external device.
o
A cable failure, or port phy failure on either side will cause session traffic on
the failed user connection to be directed onto the remaining connection.
On restoration, traffic is automatically restored on both connections.
Link aggregation is also shown on the CCDP/XPIC radio paths.
AVIAT NETWORKS
A second instance of link aggregation is established on the DAC GE3s. This

operates independently of the link aggregation established via LACP to the
external switch/router.
It may be configured as L1LA or L2 static LAG.
A path (member link) failure on an external LACP connection does not impact
link aggregation operation over the radio links - and vice-versa.
Note that a maximum user port speed of 1000 Mbit/s (L1) sets the upper limit
on the data supported on a port when traffic from a failed link or links is
directed to it.
Figure 1-85. DAC GE3 LACP
Layer 1 Link Aggregation (L1LA)

DAC GE3 supports L1 link aggregation (L1LA) on fixed or adaptive modulation member links.
Operation is proprietary. A DAC GE3 is required at both ends of the link aggregated
group.
Operation is feature licensed. See Licensing on page 72.
L1LA member l i nks must provi de a capaci ty (VC si ze) of not
l ess than 50 Mbi t/s for ETSI , and 38 Mbi t/s for ANSI .
L1LA aggregates the capacity provided on Eclipse RAC 60E/6XE member links.
l
l
RACs are DPP connected to DAC GE3(s).

One DAC GE3 supports a maximum 4 member links. DAC GE3s are
stacked/protected to provide up to four additional member links (total of eight).
L1LA operation requires a 2 Mbps or 1.5 Mbps bus connection size setting on the
INU/INUe.
Member links can be configured for adaptive or fixed modulation.

l
l
260-668139-001
Member links must have same RF channel bandwidth.

ETSI member links must use a bandwidth/modulation that provides a capacity
of not less than 50 Mbit/s.
JULY 2014
173
ANSI member links must use a bandwidth/modulation that provides a capacity

of not less than 38 Mbit/s.
Loading (the distribution of traffic between member links) is automatically re-balanced when a modulation change occurs on a member link. This operation is hitless/errorless.
l
L1LA employs Ethernet frame segmentation to achieve uniform, balanced

distribution.
Segment lengths are automatically determined based on available member link
radio capacity.
Segments are individually encapsulated and then distributed across all
available member links.
Adaptive modulation changes trigger instant adjustment of segment lengths
and traffic re-distribution.
o
A downshift to a lower modulation translates into an aggregation capacity

decrease (hitless for priority traffic).
An upshift to a higher modulation translates into an aggregation capacity

increase (hitless).
As a result, uniform load balancing and maximum aggregation gain is always

achieved on the capacity mix made available on member links.
Convergence and recovery from individual link failures is superior carrier-grade; typically less than 5 msec.
Aggregation management overheads apply. These are inversely proportional to member link data rates, and frame size.
4+0 L1LA on Two CCDP/XPIC Pairs
The figure below illustrates 4+0 L1LA over two CCDP/XPIC link pairs.
l
One DAC GE3 supports up to four DPP-connected RACs/Links.
Links configured for fixed or adaptive modulation.
combiners, though insertion losses are nominally 3.5 dB per side (equal-loss
combiner) for a 7 dB total per link.
Figure 1-86. DAC GE3 4+0 L1LA CCDP/XPIC
174
AVIAT NETWORKS
6+0 L1LA on CCDP/XPIC Pairs

The figure below illustrates 6+0 L1LA over three CCDP/XPIC link pairs.
l
Two DAC GE3 cards are configured as a protected/stacked pairing to support

six DPP-connected RACs/Links.
o
l
l
When protected, the DAC GE3s behave as one stacked switch.
Links can be configured for fixed or adaptive modulation.

Three XPOL antennas are used. This could be reduced to two, using two
combiners at each end to bring four links onto a common XPOL antenna,
though insertion losses of nominally 3.5 dB per side (equal-loss combiner) for a
7 dB total would apply to each of the combiner-connected links.
Note that each DAC GE3 is supporting three links - the center XPIC pairing has
one RAC/link connection to the upper DAC GE3, the second to the lower.
Ethernet user connections are made to each DAC GE3.
o
Under normal conditions data on both user connections is link aggregated

across all six L1LA member links.
On failure of one member link, data is aggregated across the remaining five
member links.
On failure of one external user connection or DAC GE3 phy port, data on the
remaining user connection is aggregated across all six member links.
On failure of one DAC GE3 card, data on the remaining DAC GE3 is
aggregated across its three directly supported member links.
Figure 1-87. 6+0 Operation using Protected/Stacked DAC GE3s
4+0 L1LA with 2+0 LACP

The figure below illustrates use of stacked DAC GE3s to provide L1LA over Eclipse
links, plus LAG/LACP on the user connections.
l
Two DAC GE3 cards are configured as a protected/stacked pairing.

o
260-668139-001
When protected, the DAC GE3s behave as one stacked switch.
4+0 L1LA is configured on the DAC GE3s.

2+0 LAG with LACP is configured between the DAC GE3s and external
switch/router.
JULY 2014
175
LACP-negotiated L2 link aggregation operates on the user connections. For

information on LACP see Dynamic LAG on page 171.
The two separate link aggregation instances provide comprehensive data

protection.
o
Under normal conditions data is L2 link aggregated on the user connections,

and L1 link aggregated across all four radio links.
On failure of one radio link, data is aggregated across the remaining three
member links.
On failure of one user connection or DAC GE3 phy port, data on the failed
connection is directed to the remaining user connection, which is L1
aggregated across all four member links.
On failure of one DAC GE3 card, data on the remaining DAC GE3 is
aggregated across its two directly supported member links. Capacity for
Ethernet data is halved.
A member link failure on the external L2 aggregation group does not impact
operation of the L1 aggregation group - and vice-versa.
combiners, though insertion losses are nominally 3.5 dB per side (equal-loss
combiner) for a 7 dB total per link.
Figure 1-88. DAC GE3 4+0 L1LA with 2+0 LAG/LACP
2+2 L1LA with 2+0 LAG/LACP

In the figure below, protection is extended through incorporation of L1 link aggregation on two space diversity CCDP/XPIC links.
176
AVIAT NETWORKS
Figure 1-89. DAC GE3 2+2 L1LA with 2+0 LAG/LACP
Simple Backplane L1LA

Physical links can be aggregated through circuit assignments applied on the backplane bus.
l
l
l
There is no specific Portal screen for this L1LA feature. Data on one DAC GE3
transport channel is split between separate RAC links by assigning individual 2
Mbps, 1.5 Mbps, or 150 circuits to/from the links.
With an 2/1.5 Mbps backplane two physical links can be configured to support
aggregate totals to 200 Mbps (204 Mbps).
With a 150 Mbps backplane two links can be configured to support an aggregate
total of 300 Mbps (310 Mbps).
Each link must be configured for equal capacity.
The circuits must be assigned in correct sequence, for example circuits 1 to 8
over one link, and 9 to 20 over the other.
Rapid Failure Detection and Protection must be selected as the Transport
Channel Mode on the DAC GE3 at each end of the links.
Ethernet traffic is split equally between the link timeslots on a byte-based basis meaning data within an Ethernet frame is transported across both links. Load balancing is
optimal.
The figure below illustrates basic INU L1LA with DAC GE3. 200 Mbps is made available to the DAC GE3 from two 100 Mbps links, which may be operated (as shown) on
the same frequency channel using CCDP/XPIC links.
Figure 1-90. Simple Backplane L1LA
260-668139-001
JULY 2014
177
VLANs
VLANs (Virtual LANs) are used to segregate 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, workgroup 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.
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 bandwidth 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 Ethernet frame taggi ng.
VLANs are established by grouping 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 and a priority/class setting.
Switches within the network use the VLAN ID tag to maintain VLAN
membership/segregation over common trunk links.
The priority/class setting determines the priority assigned for QoS purposes.
802.1Q
IEEE 802.1Q addresses VLAN identification and quality of service (QoS) levels.
Typically, when VLAN tagging is configured on a switch port:
l
Ingressing untagged frames are tagged with a port VLAN ID (PVID). Ingressing
tagged frames from the customer network (CVID) are not touched.
If an 'untagged' option is selected at egress, the PVID is stripped off. Frames
with a different VLAN ID (CVID) are not affected.
If a 'push' option is selected at egress, the PVID tag is retained into the
connected network.
The tag format, defined in 802.1Q, uses 4 bytes, which are added to the normal
Ethernet frame.
o
178
The first 2 bytes specify the Ethernet type (Ethertype), which is used to
detect tagged 'Q Ethernet' frames.
AVIAT NETWORKS
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.
n
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.
The CoS bits are defined in 802.1p and support 8 different priority
settings, 0 to 7, with 7 the highest.
Q-in-Q
Q-in-Q operation is addressed under IEEE standard 802.1ad, which grew out of the
802.1Q-in-Q protocol. It specifies use and application of multiple VLAN tagging.
Typically, when Q-in-Q tagging is configured on a switch port:

l
Ingressing frames have a PVID added even if they are CVID tagged - frames are
double-tagged.
If an 'untagged' option is selected at egress, the PVID (one VLAN level) is
stripped off.
If a 'push' option is selected at egress, the double tagging (CVID and PVID) is
retained into the connected network.
The tag format is similar to that specified under 802.1Q. 4 bytes are added to
the Q-tagged Ethernet frame, for a total of 8 added bytes.
DAC GE3 VLAN Options

DAC GE3 has extensive and flexible VLAN capabilities. VLAN configuration is used
not only to set VLAN tagging and filtering, but to also select and where required customize cross-connections between front panel and backplane ports. It provides a
means to manage all traffic within a DAC GE3 switch, from switch port ingress to
egress, and to establish VLANs for use beyond the switch.
l
All traffic ingressing the switch, whether from a port or channel, is VLAN
tagged, but the tagging is only carried beyond the switch where:
o
VLAN segregation of traffic streams is required over a common Ethernet

path.
A user-specific VID is added to an ingressing frame.
The VID of an ingressing frame is replaced by a different VID.
For more information, see VLANs on page 117.
Synchronous Operation
Standard Ethernet (IEEE 802.3) is asynchronous - it contains no provision for transferring a clock reference - which becomes an issue where clocking must be maintained
when migrating to an all-IP network.
260-668139-001
JULY 2014
179
The situation particularly applies to mobile backhaul networks where TDM clocking
(E1/DS1) has been the norm and there is a need maintain base station synchronization when migrating to IP/Ethernet.
l
Mobile base stations are 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.
For GSM / UMTS nodes on a TDM wireless backhaul network, required
frequency synchronization has typically been provided by an E1/DS1 clock.
For CDMA nodes requiring a time-referenced phase sync source, clocking has
typically been provided by a GPS receiver installed at the site.
For next generation 4G/LTE base stations, frequency and phase synchronization
solutions are required.
For all-IP networks there are currently two network-based solutions; Synchronous Ethernet and IEEE 1588v2. (For mixed-mode networks clocking can be maintained via
the TDM circuits).
l
l
Synchronous Ethernet supports frequency synchronization only.

IEEE 1588v2 has the capability to support phase (and frequency)
synchronization.
Eclipse supports Synchronous Ethernet together with SSM (Synchronous Status Messaging) to provide information about the quality level (QL) of source clocks, and
employs unique mechanisms to transfer the clock over radio links; ART (Airlink
Recovered Timing) and EDS (Eclipse Distributed Sync). ART may also be used to
provide enhanced quality clock transfer for selected E1/DS1 trib circuits. For mixedmode links the E1/DS1 clock can be used to provide clocking for Ethernet.
SyncE is supported on Eclipse non-protected and protected links, and on L2 and L1
link-aggregated links.
SyncE is supported on protected/stacked DAC GE3s (clock sourcing on optical Ycables is not supported).
Refer to:
l
l
Synchronous Ethernet on page 180

IEEE 1588v2 on page 181
Eclipse Clock Management for Synchronous Ethernet on page 181
Eclipse Clock Transport over Radio Links on page 184
Enhanced PDH Clock Transport: ART Re-Timing on page 189
Eclipse Native Mixed Mode Links on page 190
Synchronous Ethernet (SyncE) transports timing information using the physical layer
clock. Each device in the network recovers, cleans, and then distributes the clock to its
downstream neighbor. It means every intervening node (switch/router) within the network must support SyncE.
180
AVIAT NETWORKS
Multiple clock sources can be installed to provide fallback should the primary source
fail or become impaired. SSM (Synchronous Status Messaging), is used to provide
information about the quality level (QL) of clocks throughout the network. The QL
assists in determining the clock selection process, with higher quality clocks having
precedence.
A particular feature of SyncE is that clocking is unaffected by data delivery impairments in the higher packet-plane layers, such as the delays caused by queuing and rerouting on heavily loaded networks. However, transporting the clock over a radio link
is not straight forward. Unlike a cabled connection, a radio link cannot support transport of the bit-stream clock within the payload - other mechanisms are needed.
Uniquely Eclipse provides two solutions; Airlink Recovered Timing (ART), and Eclipse
Distributed Sync (EDS).
Note that Ethernet data transport (the data plane) is oblivious to the Ethernet mode
of operation; standard Ethernet or Synchronous Ethernet. For example Ethernet traffic
(standard Ethernet) is transportable over SyncE network connections, and data on a
SyncE link is transportable over standard Ethernet connections minus the SyncE
clock.
IEEE 1588v2
1588v2 is a Precision Timing Protocol (PTP) for phase and frequency synchronization.
Dedicated timing packets are transmitted within the data packet stream to maintain
a Master-Slave synchronization relationship.
l
Time-stamped PTP packets are sent from the master clock to the slave clocks,
and from the slave clocks back to the master. A timing recovery algorithm uses
these packets to calculate and offset the delays and differences in delay (packet
delay variation or PDV) across a network.
PDV represents the most significant impairment factor synchronization
accuracy can be affected on heavily loaded networks.
Because it works in the IP data path it does add a small amount of additional
traffic to the network.
Aviat Networks offers comprehensive 1588v2 packet-based solutions in conjunction

with Symmetricom. Contact Aviat Networks or your supplier for details.
1588v2 frames are transported transparently by Eclipse Packet Node.
Eclipse Clock Management for Synchronous Ethernet

Eclipse employs SSM (Synchronous Status Messaging to transport information about
the quality level (QL) of source clocks from clock-to-clock within the network. The QL
assists in determining the clock selection process, with higher quality clocks having
precedence.
SSM is delivered via the Ethernet Synchronization Messaging Channel (ESMC), which
is provided on dedicated low-data-rate (heartbeat) Ethernet frames within the payload.
260-668139-001
JULY 2014
181
l
l
Each DAC GE3 in a SyncE network has an internal equipment clock, which is
clocked in turn from the source clock. Such internal clocks are referred to as
Ethernet Equipment Clocks (EEC).
The source clock for a network can be a Primary Reference Clock (PRC), or lesser
quality 'secondary' clock sources.
Other clock sources such as Synchronization Supply Units (SSU) may be
included in a network to reduce the incidence of accumulated jitter and wander
over multiple hops, and to provide a fall-back source should the primary source
become corrupted or lost.
Synchronization can also be captured from TDM clock sources.
The quality levels (QL) advised by the SSM are used to determine the clock fallback order when multiple clock sources are provided, and to enable transparent,
non-blocking transfer of the clock.
Two industry-standard SSM option types are supported, Option I, and Option
II. These option types are selected based on the clock source hierarchy used
within the network. Generally Option I is aligned with SDH/ETSI operation,
and Option II with SONET/ANSI.
o
182
Under Option I clock quality is defined in G.871 as:

n
QL-PRC: The synchronization trail transports a timing quality generated

by a primary reference clock defined in G.811.
QL-SSU-A: The synchronization trail transports a timing quality

generated by a type I or V slave clock defined in G.812.
QL-SSU-B: The synchronization trail transports a timing quality

generated by a type VI slave clock defined in G.812.
QL-SEC: The synchronization trail transports a timing quality generated

by a synchronous equipment clock (SEC) defined in G.813 or G.8262,
option I.
QL-DNU: The signal should not be used for synchronization.
Under Option II clock quality is defined in G.871 as:

n
QL-PRS: PRS traceable, G.811.
QL-STU: Synchronized traceability unknown.
QL-ST2: Traceable to stratum 2, G.812, type II.
QL-TNC: Traceable to transit node clock, G.812, type V.
QL-ST3E: Traceable to stratum 3E,G.812, type III.
QL-ST3: Traceable to stratum 3, G.812, type IV.
QL-SMC: Traceable to SONET clock self timed, G.813 or G.8262, option

II.
QL-ST4: Traceable to stratum 4 free-run (only applicable to 1.5 Mbit/s

signals).
QL-PROV: Provisionable by the network operator.
QL-DUS: The signal should not be used for synchronization.
A priority can be user-set for multiple clock sources to assist the fall-back
process when SSM is not enabled, or the clock signal has failed.
AVIAT NETWORKS
In SSM enabled mode the clock fall-back process auto selects on:
o
Quality level. The highest QL is selected. If the QL of the existing clock

degrades, the next highest QL source is selected, which may be the existing
or an alternate source.
Clock signal failure, via QL-failed. QL-failed is an internally held value for
clock signal failure.
Priority. If two or more inputs have the same QL, the highest priority is
selected.
n
In SSM disabled mode the process auto selects on clock signal failure and
priority.
o
l
l
260-668139-001
All front ports plus two TDM (multicast) ports are available for syncsource prioritization.
A maximum of three front ports plus two TDM (multicast) ports are
available for sync-source prioritization. Front selection is restricted to one
SFP (optical) and two electrical.
Holdover mode selection is provided for use when the selected clock source(s)
fail. If SSM is enabled, the QL advised under internal Stratum 3 clock operation
(all holdover modes) is SEC (Option I), or ST3 (Option II). The mode options
are:
o
Infinite; the clock will be maintained at the rate immediately before failure,
assisted by the internal Stratum 3 clock.
Immediate free run; clocking is immediately provided by the internal

Stratum 3 clock.
Delayed free run; clocking is maintained at the rate immediately before

failure for a user-specified time, thereafter it is free run.
With SSM enabled hold-off and wait-to-restore timers are added. These are used
to ensure fleeting/intermittent failure/restore conditions are not acted on. A
selection applies to all enabled clock sources.
o
The hold-off timer ensures that short signal-fail conditions are not acted on.
The set-able range is 300 to 1800 ms. In the meantime the previous QL level
is maintained.
The wait-to-restore timer ensures that a previously failed clock source has
been fault-free for a specified time before becoming available for selection.
The set-able range is 0 to 86400 seconds. In the meantime the QL-failed
status is maintained.
A forced quality level option is provided under Option I or Option II. This forces
the selected SSM QL value on the clock signal received on the selected source
port. It is primarily for use where no QL is associated with the source clock such
as from equipment/interfaces that do not support SSM or are SSM disabled. A
TDM clock source is one example. The forced QL option can also be used to
override (replace) a received QL.
Timing loops are prevented.
Master/Slave selection options of Auto, Master, Slave, Local are provided on
enabled clock-source ports:
JULY 2014
183
If SyncE is enabled (SSM not enabled), ports in the priority table are forced
to Slave; other ports are configurable.
If SyncE and SSM are enabled, the SSM selected clock port is forced to Slave;
other ports in the priority table are forced to Master.
With SSM enabled per-port selection (front ports and TDM/multicast) is

provided for SSM enable, SSM disable, Rx only, or Tx only. Rx only or Tx only
are intended for diagnostic purposes.
Eclipse Clock Transport over Radio Links

Ethernet data (Ethernet frames) are captured into transport channel framing for transmission over radio links, which means the Synchronous Ethernet physical layer (L1)
clock reference cannot be transported as part on the link payload. With Eclipse two
solutions are provided, ART and EDS.
l
ART (Airlink Recovered Timing) transports a high quality clock reference.

o
Clock quality meets G.8262 limits over a radio link, and G.8261 limits over a
network of up to 10 ART-connected tandem links.
Requires RAC 60E or RAC 6XE.
EDS (Eclipse Distributed Sync) transports a TDM quality clock reference.

o
Clock quality meets G.823/824 limits over a radio link.
Intended for use with RAC 30v3 and legacy RACs.
ART provides superior clock stability and should always be used where
supported.
ART can also be used to transport the clock on an E1/DS1 link circuit to provide
near-G.8262 clock quality over the radio link. See Enhanced PDH Clock
Transport over Radio Links below.
ART and EDS require a Synchronous feature license. See Licensing on page 72.
ART
ART transports the clock using radio link (symbol rate) clocking. The link clock is
locked to a clock source at the transmit end of a link, and recovered at the far end of
the link to provide highest synchronization accuracy and reliability. There is no
impact on traffic payload.
l
l
184
ART clock transport requires RAC 60E or RAC 6XE links.

The clock input to an Eclipse ART network is sourced from a SyncE input to a
DAC GE3 port, or from an E1/DS1 circuit to a DAC 16xv2 or DAC 4x.
Multiple clock sources are permitted with their quality and prioritization for
fall-back supported under SSM.
The SyncE input is distributed to a RAC 60E/6XE (one or more links) using the
DPP or the backplane-connected multicast clock option.
At the transmit end the RAC is configured to enable an ART Tx clock, which
locks the link (symbol rate) clock to the SyncE clock.
AVIAT NETWORKS
At the far end the RAC is configured to source the ART Rx clock, which is
delivered with the SyncE payload to a DAC GE3 via the DPP, or via a Sync
Multicast circuit to relevant cards.
Within the DAC GE3 the clock is cleaned and made available to SyncE
connections on local user ports, and/or via the DPP to RAC 60E/6XE link (or
links) for next hop connection(s).
o
When the clock is distributed via the DPP, clock quality meets G.8262
limits.
When distributed via the backplane bus clock quality meets G.823/824
limits.
A Stratum 3 (S3) clock on the DAC GE3 provides high quality holdover on clock
source interruption.
ART operation is supported on 1+1 protected or space diversity links.
ART operation is not supported on 1+1 frequency diversity links.
ART operation is not supported from protected DAC GE3s that use an optical
Y-cable connection to the sync source.
ART provi des superi or frequency synchroni zati on sol uti ons on
Ecl i pse networks.
NOTE: DAC GE3 10/100/1000Base-T front-panel ports and SFP ports equipped with
an optical transceiver are SyncE capable. SFP ports equipped with an electrical
10/100/1000Base-T transceiver do not support SyncE.
SyncE Clock Capture and ART Transmission at Network Source
The figure below illustrates clock source options provided to a DAC GE3, and its DPP
distribution to 1+1 protected RAC 60Es.
l
With SSM enabled on the DAC GE3, clock selection is made automatically
based on the quality level (QL) of the clock source. In this example the primary
clock source provides the highest QL, followed by the secondary sources. For
SyncE sources that are SSM enabled the QL will be automatically captured on
the DAC GE3. Otherwise a QL can be forced. For the E1/DS1 source a QL must
be forced.
Source clock priority on the DAC GE3 is also set to reflect the clock QL; 1
(highest) for P1, 2 for P2, and 3 for the multicast clock input from the E1/DS1
source.
The RAC 60Es are configured for ART mode Tx and ART source DPP.
Figure 1-91. SyncE Clock Capture and ART Transmission at Network Source
260-668139-001
JULY 2014
185
Link Sync Capture and Distribution

The figure below illustrates receipt of an ART-transported clock, its DPP connection
(with payload) to its DAC GE3, and distribution to upstream links and local connections.
l
l
l
l
RAC 60E cards are configured for ART mode Rx and ART output DPP.
SSM is enabled on the DAC GE3 for ports P1 and P2. The QL of the received
clock on both ports will reflect the QL of the clock sent over the link.
For the P1 connected primary RAC 60E, the DAC GE3 sync source clock priority
is set to 1 (highest), P2 priority is set to 2.
SyncE is forwarded on a DPP connection to a next-hop RAC 60E using ART.
SyncE is also forwarded to a next hop RAC 30 link using EDS. A sync multicast
circuit on the backplane bus provides the clock connection.
o
When the DAC GE3 is not in clock holdover mode PRBS is inserted on the
E1/DS1 sync multicast circuits established via the backplane from the DAC
GE3. When in holdover mode PRBS is replaced by AIS.
An E1 or DS1 trib for sync purposes only is provided on a DAC 4x, using a
multicast circuit on the backplane bus.
Figure 1-92. Link Sync Capture and Distribution
Bi-directional (Auto) Clock Capture

The figure below illustrates incorporation of a secondary clock source at a location
remote from the primary source. Both link ends must be configured to accept a local
or remote clock source. Under normal conditions the primary-end clocks the network.
Clocking is switched to the remote clock on failure of the primary clock.
l
186
The RAC 60E cards at both ends are configured for ART mode Auto, ART
output DPP, and ART input DPP.
SSM is enabled on the DAC GE3 cards. Clock selection is made automatically
based on the quality level (QL) of the clock sources. In this example the primary
clock source provides the highest QL. If the SyncE sources are not SSM enabled
a QL can be forced.
AVIAT NETWORKS
At the primary clock end the DAC GE3 is configured for a source clock priority
of 1 on P1, 2 on P3, and 3 on P2. At the secondary clock end it is configured for
priority 1 on P2, 2 on P2, and 3 on P5.
Figure 1-93. Bi-directional (Auto) Clock Capture
Backplane ART-Bus Clock Transfer

The figure below illustrates a link where the backplane bus is used at both ends to
provide RAC 60E - DAC GE3 interconnection. Unlike DPP connections, SSM is not
supported on the backplane.
l
At the clock-source end of the link SSM is enabled to support clock selection
between primary and secondary clocks - providing the sources are SSM enabled.
For a single clock source SSM is not applicable.
o
The DAC GE3 source clock priority is configured for priority 1 on P1, and 2
on P3.
The 1+1 RAC 60E module is configured for ART mode Tx, and ART source
Art Bus.
A Sync Multicast circuit is used to transfer the clock from the DAC GE3 to
the 1+1 RAC 60E module.
At the remote (receive) end SSM is not enabled - SSM is not supported on
backplane connections.
o
The 1+1 RAC 60E module is configured for ART mode Rx, and ART output
Art Bus, and the clock transferred via a Sync Multicast circuit to the Sync
tab on the DAC GE3.
Figure 1-94. Backplane ART-Bus Clock Transfer
EDS
An enhanced versi on of EDS i s avai l abl e for use wi th the l egacy RAC 60 and RAC 60X to provi de cl ock transport meeti ng
G.8262 l i mi ts. F or more i nformati on refer to the Ecl i pse User
Manual for SW rel ease 08.00.
EDS multicasts an E1 or DS1 circuit throughout the network to maintain existing
TDM clock accuracy and stability. EDS is supported on all RAC types.
260-668139-001
JULY 2014
187
Instead of a dedicated circuit per destination, one E1/DS1 is used throughout

the network for all destinations for sync purposes only.
At intermediary network nodes the E1/DS1 is captured from the incoming link,
and included on required outgoing links.
Protection for EDS operation is provided at source and over the network:
o
At input the source can be protected using 1+1 protected DAC GE3 cards (for
a SyncE input), or 1+1 protected DAC 16xV2 cards (for an E1/DS1 input).
Over radio links protection is provided by standard Eclipse link redundancy

options.
The Portal Sync Multicast screen is used to map the EDS clock between
compatible cards.
The clock output can be delivered on SyncE from a DAC GE3 port, or as an EDS
E1/DS1 clock on a DAC 16x or DAC 4x tributary connection.
Clock quality meets G.823/824 limits.
SSM is not supported.
It is primarily for use on Eclipse Packet Node networks where G.823/824 clock
accuracy is sufficient, or on networks that do not have RAC 60E/RAC 6XE
cards installed.
While an E1/DS1 is included alongside the Ethernet data on each link, the
effective cost of this usage is small compared to implementing generic IEEE
1588v2 or Synchronous Ethernet solutions.
The figure below illustrates a SyncE connection to a DAC GE3 at source, and distribution of the clock to a 1+1 protected RAC link.
l
EDS clocking is supported on all Eclipse link/RAC types configured for Nx2 or
Nx1.5 Mbit/s.
The sync clock from the DAC GE3 is directed to the RACs via the backplane
bus. Each connection uses one 2/1.5 Mbits circuit on the backplane bus.
Ethernet payload is interconnected in the normal way (TC to RAC via the
backplane bus) .
Figure 1-95. SyncE Clock Capture and EDS Transmission at Network Source
The figure below illustrates receipt of the EDS clock, and its backplane connection to
its DAC GE3.
l
l
188
A SyncE local user connection is configured on P1.

The clock is forwarded to a next-hop EDS link using a sync multicast circuit on
the backplane bus.
An E1 or DS1 trib for sync purposes only is provided on a DAC 4x, using a
multicast circuit on the backplane bus. Applications include provision of a clock
to a pseudowire terminal.
AVIAT NETWORKS
Ethernet payload is directed between the cards in the normal way (backplane
bus circuits).
Figure 1-96. Downstream EDS Clock Capture and Distribution
Enhanced PDH Clock Transport: ART Re-Timing

ART retiming can be used to transfer the clock signal on an Eclipse E1/DS1 radio circuit to provide a superior clock quality (clock transfer performance) compared to a normal circuit, where the E1/DS1 clock is transported within the traffic stream (byte/bit
rate clocking). RAC 60E or RAC 6XE cards are required.
This option has application on a selected E1/DS1 circuit end-to-end within the network.
l
On the selected circuit ART retiming (unidirectional) is used over each hop to
transport the clock. It is also available to transport normal E1/DS1 traffic in the
same direction (uni-directional).
o
Any traffic on the E1/DS1 trib circuit selected for ART retiming will be passed
over the link in the same direction as the clock. This has application in
instances where the E1/DS1 is used to transport SSM data.
Bi-directional E1/DS1 traffic can be established on a link hop by setting a

unidirectional circuit on the same circuit from the opposite end of the link
using the Sync Multicast function.
Other E1/DS1 circuits in use over the same hop(s) retain their standard E1/DS1
clock quality (G.823/G.824).
With ART retiming, jitter and wander are reduced to provide near-G.8262 clock
quality over a radio link.
Thi s opti on i s appl i cabl e on E1/DS1 l i nks where a superi or
cl ock transfer qual i ty i s requi red on the sel ected ci rcui t. F or
SyncE (or hybri d SyncE wi th E1/DS) l i nks, use the standard
SyncE ART opti ons above.
The figure below illustrates use of ART retiming on an E1/DS1 link.

At the clock source (transmit) end:
260-668139-001
JULY 2014
189
The 1+1 RAC 60E is set for ART mode Transmit and ART source Multicast
Clock.
A Sync Multicast circuit is used to transfer the clock from the DAC 16x to the
RAC 60E.
At the receive end:

l
l
The 1+1 RAC 60E is set for ART mode Receive and ART output Multicast Clock.
The next-hop 1+0 RAC 60E is set for ART mode Transmit and ART source
Multicast Clock.
A Sync Multicast circuit is used to transfer the clock from the 1+1 RAC 60E to
the 1+0 RAC 60E.
Figure 1-97. ART Retiming on an E1/DS1 Trib
Eclipse Native Mixed Mode Links

In instances where both Ethernet and TDM connections must be maintained on a network, such as during the migration from TDM to Ethernet, Eclipse mixed mode operation provides an elegant solution for maintaining TDM-based timing.
l
It is fully user-scalable from 100% native TDM to 100% native Ethernet in 2

Mbit/s or 1.5 Mbit/s steps.
There are no overheads data transport efficiency is not impacted.
There is no additional cost its built-in.
Synchronization integrity is maintained using TDM clocking.
It can be retained up until the point of going all-IP, when one of the above
solutions, ART or EDS, can be implemented to provide required sync clock
transport.
There is no de-installation or redundancy on achieving all-IP.
Ethernet OAM
Ethernet OAM (Operation, Administration, and Maintenance) is used to detect network faults and provide measures of network performance. It operates through use of
OAM messaging (OAM PDUs [Ethernet frames]) sent alongside user traffic whereby
the frame content defines the message type and function.
Eclipse supports Service OAM which addresses end-to-end Ethernet connectivity fault
management (CFM) and performance monitoring (PM) as defined within IEEE
802.1ag, and ITU-T Y.1731.
190
AVIAT NETWORKS
802.1ag and Y.1731 specifications overlap/converge on CFM (the terminology

used by IEEE and ITU-T to define managed services is currently not fully
converged)
PM is only defined in Y.1731.
Link-level OAM is not supported.
Fault Management
Connectivity Fault Management operates by partitioning a network into service levels
- up to eight. Each level is assigned a unique number ranging from 0 to 7 with default
levels of 5-7 for customers, 3-4 for providers, and 0-2 for operators.
l
l
l
Customers have visibility of their service connection(s) end-end over the

provider network.
Providers have end-end service responsibility to the customer.
Operators provide service transport across a sub-network within the provider
network.
Users at the higher levels are not afforded visibility of operation at the lower
levels.
OAM frames belonging to higher levels are transparently transported by devices
(bridges) at the lower levels.
The ITU-T terminology (IEEE in brackets, where different) used to describe managed
services includes:
l
ME: Maintenance Entity - a unique entity (service) that requires management.

A unique VLAN ID identifies each service instance.
MEG: Maintenance Entity Group (MA: Maintenance Association) - one or more
MEs on the same service level and belonging to the same service provider
VLAN.
o
For a point-to-point Ethernet/VLAN connection a MEG contains a single

ME.
For a multipoint connection the MEG contains multiple MEs.
MEP: MEG (MA) End Point - used to establish (provision) the end points of an
ME. A MEP initiates and terminates Ethernet OAM messages, including
responses to diagnostic messages.
o
A discovery mechanism enables identification of service OAM capable

network elements at and within MEP end-points.
MIP: MEG (MA) Intermediate Point - used to establish an intermediate point

between MEPs for maintenance purposes. A MIP simply responds to OAM
diagnostic messages - it does not initiate.
The figure below shows simple end-end transport within a provider domain (network)
that includes two operator domains. In practice each bridge in the domain(s) will
have multiple ports in use, each with multiple VLAN-based sessions.
l
260-668139-001
A MEP is established at the end point of each maintenance domain. MIPs may
be established to provide responses to relevant maintenance requests.
JULY 2014
191
At the customer level it shows only a MEP at each end, though a MIP might
also be included on the connection point to the provider network.
At the provider and operator network levels MEPs are established to define the
ends of their maintenance domains, and MIPs on relevant intermediate ports.
Multiple MEP and MIP instances (VLAN based) can be configured on a common
bridge port, though for a given level/VLAN a MIP cannot be established if a
MEP is configured. Similarly, a MIP cannot be established on a port at a level
below that of a MEP.
At the operator level each Eclipse link is shown with both input and output
DAC GE3 bridge ports set with a MIP or MEP. This particularly applies where
the DAC GE3 is providing a nodal function (multiple input/output service
connections). On the other hand a simple Eclipse link with one user port
enabled at each end may be treated as a single bridge element.
When link aggregation is configured, a MEP or MIP can be established to
monitor the aggregated link, but not for the individual ports of the aggregated
link.
Figure 1-98. Ethernet Service OAM Domains
CFM Message Types

Eclipse CFM supports five OAM message types; Continuity Check Message (ETH-CC),
Loopback Message (ETH-LB), Link-trace Message (ETH-LT), Alarm Indication Signal
(ETH-AIS), and Remote Defect Indication (ETH-RDI).
l
ETH-CC, and ETH-AIS are proactive in operation to support network status

notification.
ETH-LB and ETH-LT are on-demand. Their selection is supported on the DAC
GE3 System/Controls screen.
ETH-CC
Used to detect loss of continuity or incorrect network connections.
192
MEPs periodically exchange CCMs.
The transmission interval is configurable.
AVIAT NETWORKS
CCMs are also used in support of round-trip frame loss measurements, and to
initiate ETH-AIS and ETH-RDI messages.
ETH-LB
Used to verify connectivity to a particular MIP or MEP for fault verification purposes.
A reply to a loopback messages indicates a destination is reachable. Operation is similar to the Ping protocol.
ETH-LT
Used to discover remote MEPs and MIPs at the same maintenance level. Mostly used
for fault isolation purposes. Operation is similar to the Traceroute protocol.
ETH-AIS
Used to provide fault notification and alarm suppression.

l
On MEP detection of a connectivity failure on a particular service level it

multicasts AIS away from the detected failure at a configured the client service
level (usually next highest) , on each VLAN affected by the failure. AIS can be
propagated up in this way (MEP-to-MEP) to the highest service level
(customer) to ensure all clients are notified of the service instance failure.
An alarm suppression function helps ensure an NMS is not swamped with an
excessive number of alarms for a particular fault by arranging that a client level
MEP, on receipt of AIS, suppresses loss of connectivity alarms associated with
all its peer (same service level) MEPs.
ETH-RDI
Used to provide fault notification back to other devices. When a downstream MEP
detects a defect condition, such as receive signal failure, it sends an RDI in the
upstream direction to its peer MEP(s) to inform a downstream failure.
Performance Monitoring
Eclipse Ethernet OAM performance monitoring supports three message types, Frame
Loss Measurement (ETH-LM), Frame Delay Measurement (ETH-DM), and Frame
Delay Variation measurement (ETH-DVM). All are defined under Y.1731.
Performance parameters are initiated and terminated on MEP-configured ports, and
apply per port and VLAN instance, per maintenance level.
ETH-LM
Used to measure frame loss rate as a percentage of undelivered frames divided by the
total number of frames sent during the time interval. Single and dual-ended operation
is supported.
l
260-668139-001
Single-end operation is on-demand and provides near-end and far-end LM at

the end that initiated the LM request.
Dual-end operation enables proactive measurement of both near end and far
end LM at each end of a MEG.
JULY 2014
193
ETH-DM
Used to measure round-trip delay (latency) between MEPs. Measurement is ondemand.
ETH-DVM
Used to measure delay variations - the variation occurring between consecutive ETHDM measurements. Supports collection of minimum, average, and maximum roundtrip delay times and provision of an average delay variation.
Performance monitoring is enabled under Diagnostics > System/Controls. See System/Controls: OAM on page 295
194
AVIAT NETWORKS
Protected Operation
Eclipse includes options for protection of hardware, radio path, tributary, and NCC
functions. Refer to:
l
Hardware and Radio Path Protection on page 195
Ring Protection - E1/DS1 Loop-switch on page 200
Ring Protection - Super PDH (SPDH) on page 202
Ring Protection - Ethernet on page 208
DAC/Tributary Protection on page 211
DAC/Ethernet Protection on page 213
Protection Switching Criteria on page 220
NCC Protection with NPC Option on page 231
For additional information on protection, refer to Eclipse User Manual.

Protected operati on between an I NU and I DUs i s not supported.
Hardware and Radio Path Protection

RACs and ODUs/RFUs are used in pairs to support hot-standby, space diversity, or
frequency diversity.
Adapti ve modul ati on i s not supported on frequency di versi ty
l i nks.
Path protection is about providing protection against changes in radio-path variables,
such as anomalies caused by ducting or signal reflection. Such protection demands hitless (errorless) receive switching between the alternate (protected) radio paths.
l
Space or frequency diversity are used for path protection. They also provide
hardware protection.
Hardware/equipment protection is about providing backup hardware that can be

switched into service in the event of a failure. Protection is typically not hitless.
l
Hot-standby is used for hardware protection.
Eclipse also supports dual-protection whereby a master protection option protects two
subordinate protected links. Options are:
l
Frequency diversity over hot-standby
Frequency diversity over space diversity
260-668139-001
JULY 2014
195
Ri ng protecti on opti ons provi de hardware protecti on, and

through thei r i nherent route di versi ty al so provi de protecti on
agai nst l ocal i zed (si ngl e l i nk) path fai l ure events. See ri ng protecti on opti ons bel ow.
RAC Protection - Fixed Modulation
All RACs support hot standby or diversity (space or frequency) protection. Rx path
voting is hitless; Tx switching is not hitless.
CCDP/XPIC links can be hot standby or diversity (space or frequency) protected. Rx
path voting is hitless. Tx switching is not hitless.
RAC Protection - Adaptive Modulation
Adaptive modulation can be configured on hot standby or space diversity RAC
60E/6XE links. Frequency diversity is not supported.
Adaptive modulation can be configured on hot standby or space diversity RAC 6XE
CCDP/XPIC links.
Most DACs can be paired to provide hot-standby tributary protection. Protected
options are provided for Ethernet, E1/DS1 E3/DS3 and STM1/OC3.
For more information, see DAC/Tributary Protection on page 211.
NCC Protection
The NPC plug-in provides protection for the NCC bus management and power supply
functions:
l
Bus management switching is not hitless.
Power supply protection is hitless.
For more information on the NPC and its protection function, see NPC Plug-In on
page 131
Link Protection Options

Radio link options are hot-standby, space diversity, frequency diversity, dual
diversity.
Hot Standby and Diversity

The INU supports three non-protected links, or one protected plus one non-protected
link. The INUe supports up to three protected links.
Two RACs and two ODUs or two RACs and one IRU6001 are used for protected operation.
For hot-standby single-antenna operation:
1IRU 600 is 1+1 optimized.
196
AVIAT NETWORKS
Two ODUs are direct-mounted onto a coupler, which in turn is direct or remote
mounted to its antenna.
IRU 600 (v3 and v2) ACUs incorporate a Tx coaxial switch and an Rx coupler.
The Tx switch all but eliminates Tx losses associated with HSB operation.
Equal or unequal loss couplers are available:
o
Equal-split has a nominal 3.5/3.5 dB loss per side.
Unequal-split has a nominal 1.6 /6.4 dB insertion loss.
The table below lists nominal ODU coupler losses (Tx and Rx). For IRU 600
Rx coupler losses see ACU Losses on page 153.
For space diversity operation:

l
Each ODU is direct-mounted onto its antenna. The top antenna is normally
assigned to the primary RAC/ODU.
The IRU 600 supports hot-standby/space diversity and split-Tx space diversity
operation. See IRU 600 Configurations on page 154.
For frequency diversity operation (single antenna):

l
Two ODUs are direct-mounted on a coupler, which in turn is direct or remote

mounted to its antenna. An equal loss coupler should be used; nominal losses
are 3.5 dB per side.
Alternatively two ODUs can be direct-mounted onto an XDM, which in turn is
direct mounted onto an Edge-series antenna. Coupler losses do not apply with
the XDM - insertion losses are nominally zero. One link operates on the vertical
polarity, the other on the horizontal.
The IRU 600 ACU incorporates a circulator to combine the primary and
secondary RFUs onto one waveguide feed. The ACU losses are nominally zero on
the A path and 0.5 dB on the B path. See ACU Losses on page 153.
Frequency diversity can be combined with hot-standby or space diversity to provide a

form of hybrid diversity. See Dual Protection on page 198.
Adaptive modulation is not supported on frequency diversity links.
Errorless Receive Path Switching
Receive path switching (voting) is hitless/errorless between the two receiving RACs;
the least errored data stream from the two RACs is selected on a frame-by-frame basis
by the online designated Rx RAC.
l
l
l
260-668139-001
Protected RACs are backplane interconnected by a diversity bus to support the

errorless Rx path switching (voting) capability.
The diversity bus is not capacity dependent.
On an INU the diversity bus spans all four option slots, any two of which can
be used for protected RACs (INU supports one protected link).
On an INUe the diversity buses are fixed between slots 1&4, 2&5, and 3&6.
Hence the need to locate protected RACs using these pairings.
JULY 2014
197
Receive Path Switching with Adaptive Modulation (ACM)

Receive path switching (voting) remains hitless/errorless between the two onlinereceiving RACs configured for protected operation (hot standby or space diversity)
with ACM.
l
Under ACM the RAC with the best receive signal (best SNR) determines the
modulation step-down threshold (the point where the modulation rate on the
remote Tx is forced down).
Similarly, the RAC with the best receive signal (best SNR) determines the
modulation step-up threshold (the point where the modulation rate on the
remote Tx is forced up).
Transmit switching for hot-standby and space diversity is not hitless.

See Hot-standby and Diversity Switching Criteria on page 221.
Table 1-43. Nominal Losses for ODU Equal and Unequal Couplers
Frequency Bands Primary Arm Insertion
GHz
Loss dB
Secondary Arm Insertion

Loss dB
37.0 - 40.0
4.0 (Equal), 2.0 (Unequal)
31.9 - 33.4
27.5 - 31.3
24.25 - 26.5
21.2 - 23.6
17.7 - 19.7
14.4 - 15.35
12.75 - 13.25
10.7 - 11.7
7.11 - 8.5
5.925 - 7.11
4.0 - 5.0
Dual Protection
Dual protection using ODUs enables master protection of two subordinate protected
links.
The dual protection options are:
l
Frequency diversity over hot-standby
Frequency diversity over space diversity
The table below summarizes the dual link protection options; two protected (HSB or
SD) subordinate links are in turn protected by a higher, frequency diversity master. All
RACs must be located in the same INUe. Except for the Space Diversity pairings
where two vertically separated antennas are required, a single dual-polarized antenna
can be used. Traffic must be backplane-connected.
198
AVIAT NETWORKS
Table 1-44. Dual Protection Options

Master Protection
Frequency
Diversity
Subordinate Protected Link Pairings

Link A
Link B
Hot Standby
Hot Standby
Space Diversity
Space Diversity
The figure below illustrates the action of a frequency diversity master with subordinated space diversity links.
l
The two space diversity links are on different frequencies, F1/F1and F2/F21.
Both space diversity links are online transmitting.
At any one time only one of the space diversity links is sending received data to
the INUe backplane bus.
Master protection controls which of the two space diversity links is sending
data to the INUe backplane bus; default the secondary link under master
(frequency diversity) configuration.
Figure 1-99. Dual Diversity (Frequency over Space) Tx and Rx Partnering
Each of the subordinated links are first configured for the protection option required
and both must be configured for the same capacity. Subsequently the dual (master)
switch protection is applied.
Normally all RACs would be of the same type (RAC 30v3 or RAC 60E) but while each
of the subordinated protected links must have the same RACs one protected pair may,
for example, use RAC 30s, the other RAC 60Es.
Each subordinated link may operate on different channel bandwidths, and/or different
frequency bands.
Each of the subordinated links operates as a normal link of that configuration and
under dual protection only one link of the two is sending received data to the INUe
backplane bus at one time.
1F1/F1 and F2/F2 denotes Tx high and Tx low and its corresponding Rx.
260-668139-001
JULY 2014
199
With frequency diversity master protection both subordinated links are online transmitting. Subordinated links (hot-standby / space diversity) must be configured on different frequency channels.
With a frequency diversity master switch it is possible to operate with Rx from one
protected link, and Tx to the other.
Dual protection master switching is not hitless. Each of the two subordinated protected links incorporate hitless (errorless) Rx path switching in the normal way, but
the master switch between the two subordinated links is not hitless. See Dual Protection Switching Criteria on page 225.
For more information refer to Additional Rules for Dual Protection in Eclipse User
Manual.
Ring Protection - E1/DS1 Loop-switch

The Eclipse E1/DS1 loop-switch function uses the NCM to configure a redundant ring.
At each ring node the NCM is configured to access two redundant traffic streams for
data input (insert) and output (drop).
l
A local trib is sent in east and west directions around the loop to create a bidirectional (redundant) ring.
Traffic from its destination NCM partner is received back from both east and
west directions and a local selection is made on which to use.
o
The selection is made per trib based on user preference under no-fault
conditions, and to the redundant path under fault conditions.
At a particular node the user-preference can be to select tribs all from one
direction or the other, or a mix from both directions.
Trib failure is signaled by LOF or AIS. Each trib drop is switched

independently.
Operation applies on either framed or unframed E1/DS1 tributaries.
The operational mode is low latency, non-hitless.

o
Revertive operation is configurable. A preferred input from east or west is

nominated per trib such that whenever it is available it is selected as the active
input, even if it means causing a (revertive) switching hit.
o
Revertive switching is most relevant where one input, the preferred input,
provides lowest latency.
The preference direction is restored on return to service after a user-set

period.
One Eclipse INUe can support up to 5oE1/63DS1 drops.

o
200
A switch will result in a hit on traffic and synchronization. The interrupt

time is dependent on the number of nodes in the loop. For a 6 node loop the
interrupt is typically less than 10 ms for framed traffic and 20 ms for
unframed.
The NCM provides access for 8 tribs directly via a front-panel HDR-50
connector.
AVIAT NETWORKS
o
l
Additional tribs are accessed using DAC 16xV2 or DAC 4x plug-ins.
The ring hops (links) can be established using any of the Eclipse RAC or
tributary DAC modules, including the DS3M and 155o/eM mux cards.
mux card links.
NCM cards can be 1+1 protected. Protection switching is not hitless
(switch/recovery time is less than 50 msec).
Similarly, DAC 16xV2 cards can be 1+1 protected.
The diagram below illustrates Eclipse E1/DS1 loop-switch operation. In a typical ring
the links will be made using RACs, and the drop/inserts by NCM front panel trib
ports and/or DAC 16xV2 ports. However, one or more of the link connections can also
be established using wire/leased-line connections via the DAC E3/DS3M, or DAC
155eM, or on a fiber connection using the DAC 155oM.
Figure 1-100. Bi-directional Loop-switched Ring
Loop Capacity Maximums

The following rules determine node backplane bus usage, and hence loop maximum
capacities.
l
Each east and west loop switch connection to an NCM uses 1xE1/DS1 for a
2xE1/DS1 total per drop. This applies to a drop through an NCM front panel
port, and to a drop through an external module such a DAC 16xV2.
o
260-668139-001
An exception to this rule is where the east and west connections to/from the
NCM are to the same module i.e. to the same RAC, where 3xE1/DS1 is used
per drop.
Where the NCM is used as DAC trib module for point-to-point circuit
connections between NCM front trib ports and a link module i.e. RAC, 1xE1/DS1
is used per trib.
Each pass-through circuit uses 1xE1/DS1.
JULY 2014
201
These loading rules mean that for a master node where all circuits on the loop
are sourced and sunk (to/from separate east and west input modules), the
maximum number of circuits/drops supported on the node is 63xDS1 or 50xE1.
This then represents the maximum number of circuits supported on the loop.
o
Higher loop capacities are possible where a master-node does not apply
(loop/node loading is distributed).
Ring Protection - Super PDH (SPDH)

Eclipse directly supports RAC-based ring protection on NxE1 or NxDS1 traffic. See:
l
SPDH Rings on page 202
SPDH Ring Operation on page 204

Adapti ve modul ati on i s not supported on SPDH ri ng l i nks.
Where ri ng protecti on of E3/DS3 or STM1/OC3 traffi c i s
requi red an external add/drop mux must be used.
SPDH Rings
Eclipse supports RAC-based PDH ring configurations for capacities to 75xE1 or
100xDS1. The rings are implemented by east/west facing RAC and ODU or RAC and
IRU 600 combinations from a single node (INU/INUe). A closed loop is formed when
each node is connected to two adjacent nodes, the east and west nodes. Ring switching is not hitless - recovery times are nominally 100 ms.
North Gateway or Any-to-Any Ring Topology is supported.
Within the protected ring there are two traffic rings, one nominated as clockwise, the
other anti-clockwise. Under normal no-fault conditions, all traffic is passed on the
clockwise primary ring.
East, west, cl ockwi se and anti -cl ockwi se descri ptors are conventi ons used to descri be and confi gure ri ng operati on. The
physi cal i mpl ementati on of a ri ng may be qui te di fferent.
In the event of a fault the secondary, anti-clockwise ring, provides the protection capacity needed. Traffic is looped onto the secondary ring at one side of the break point,
and off at the other side, to bypass the break. This process is called wrapping.
One or more radio paths can be replaced by a fiber span using the DAC 155oM.
Hot-standby or diversity protection options are available for ring links. The diversity
options have particular application on long and difficult paths (paths subject to fading). For more information refer to the Eclipse user manual.
SPDH ri ng protecti on protects the payl oad and al arm I /O
addressi ng between nodes; i t does not protect auxi l i ary data.
CCDP/XPIC can be applied on a SPDH ring operation. It operates as two concentric
rings within one frequency channel, one on the vertical polarization, the other on the
horizontal. CCDP/XPIC ring links can also be 1+1 hot-standby or diversity protected.
202
AVIAT NETWORKS
North Gateway or Any-to-Any Ring Topology

Super-PDH rings support North Gateway or Any-To-Any topologies. With North Gateway, one of the nodes operates as the gateway, through which all traffic on the ring is
sourced and sent. For any-to-any operation, traffic can be routed from any node in the
ring to any other node. In both modes, the E1 or DS1 circuits involved are unique on
the ring (cannot be re-used within the ring).
Most ring topologies use a single gateway where all circuits are sourced and sunk. For
such rings 64xE1 or 84xDS1 is the nominal ring maximum because of backplane capacity limitations at the gateway, but where a ring incorporates a number of gateways,
up to 75xE1 or 100xDS1 can be ring-protected1.
Backplane Capacity Rules for Super PDH Rings

At ring network nodes, backplane capacity usage is modified by the number of dropinsert circuits configured:
Each drop-insert circuit uses three bus timeslots. This may also be stated as:
each drop-insert circuit uses the equivalent of one-and-one-half backplane bus
circuits.
Pass-through circuits use the standard two-timeslots, one for Tx and one for Rx
(one circuit on the backplane bus).
Ring node capacity rules may therefore be stated as:
Ring Type
Rule Based on Number of Rule Based on Number of

E1 or DS1 Circuits
E1 or DS1 Timeslots
NxE1
R + d/2 100
2R + d 200
NxDS1
R + d/2 128
2R + d 256
Where:
l
l
R = The ring capacity (total number of circuits on the ring)

d = The drop-insert circuit capacity (number of circuits dropped and inserted at
the node)
This is shown below for a 64xE1 ring node with a 16xE1 drop-insert.
1Higher link capacities can be configured, such as 93xE1 or 100xE1, but with a
100xE1 backplane maximum such capacities are not practical in a Super-PDH ring.
260-668139-001
JULY 2014
203
Figure1-1.Ring Node Bus-Capacity Example
From this it may be seen that:

l
Where all traffic on the ring is ring-protected, the number of E1/DS1 circuits
used on the backplane equates to the number of circuits on the ring plus half
the number of circuits drop-inserted on the backplane. The total must not
exceed 100 or 128 respectively.
Such circuits may be dropped to a DAC as local tribs, and/or to a RAC to go to
remote tribs.
For a north-south gateway ring, through which all circuits on the ring are
sourced, 64xE1 or 84xDS1 is the usable maximum. For example, a 90xDS1
north-south capacity is not possible as 135xDS1 would be needed on the
backplane bus at the gateway. Working backwards, the maximum that can be
north-south sourced is nominally 64xE1 or 84xDS1.
Where there are two or more gateways on the ring, a full 75xE1 or 100xDS1 ring
capability can be used, providing the backplane capacity formula is not
infringed for any node on the network.
For more information on ring capacity maximums, refer to Eclipse User Manual,
Appendix F.
SPDH Ring Operation

Topics include:
204
Ring Protection Operation on page 205
Ring Delay Times on page 206
Double Break Operation on page 207
Point-to-Point Traffic Overlay on a Ring on page 207
Fiber Ring Closing on page 208
AVIAT NETWORKS
Ring Protection Operation

The figure below represents normal, no-fault operation for a super-PDH ring. It shows
two circuits in a 64xE1 ring routed clockwise around the primary ring. Data sent to
the ring on an E1 interface exits after travelling around the ring.
The secondary ring circuits are not being used, and carry pseudo-random data.
Figure 1-101. Normal No-fault Operation
When a break occurs, the ring protection mechanism applies loopbacks at each end of
the failed E1 circuits, 'wrapping' primary ring traffic onto the secondary ring, and
wrapping secondary back onto primary on the other side of the break. See below. In
this example all circuits are restored.
260-668139-001
JULY 2014
205
Figure 1-102. Ring-break Operation
Providing the ring only experiences a single fault, all traffic is deliverable once the ring
has completed the wrapping operation.
When wrapped, the ring is left unprotected against a further failure. For this reason,
when the condition(s) that caused the wrap are removed, the ring reverts to normal
operation (restorative switching).
The reverti ve swi tch command for return to normal servi ce i s
i ni ti ated after the rel evant al arms on the fai l ed l i nk have been
cl eared for a peri od set by the Error-F ree Ti mer (defaul t 5
mi nutes), or by the opti onal Del ay Ri ng Unwrap Ti mer, whi ch
sets a ti me of day for an unwrap. F or more i nformati on refer
to Unwrap Timers on p age 228.
Ring wrapping and restoration is not hitless. Refer to E1/DS1 Ring Protection Switching Criteria on page 226.
Ring Delay Times

There is no practical limit on the number of hops in a ring providing the delay times
do not become an issue. The delay is a function of ring capacity and the number of
hops on the ring; the higher the capacity, the lower the delay for the same number of
hops. To avoid most instances of unacceptable delays for equipment connected to an
Eclipse ring, the number of hops should not exceed sixteen.
Table 1-45. Typical RAC 30 Ring Delay Times
206
Ring Capacity
20xE1
40xE1
75xE1
Delay Per Hop
0.45 ms
0.3 ms
0.25 ms
Delay for 16 Hops
7.2 ms
4.8 ms
4 ms
AVIAT NETWORKS
Double Break Operation

In the event there are two or more link failures on the ring, (adjacent, or non-adjacent
links), the traffic will wrap up to each side of the failed points to provide limited service restoration. The node or nodes between the break points will be isolated, but
where there is an sub-ring of isolated nodes (two or more hops), traffic will wrap up
to their node break points in the same way, to provide normal service on all circuits
that have been configured between them.
In Sub-ring A:
l
Circuits are wrapped at nodes A and E.
All circuits configured to/from other nodes on the ring are lost.
All circuits configured between nodes A and E are maintained.
In sub-ring B:
l
Circuits are wrapped at nodes B and D.
All circuits configured between nodes B and D are maintained.
All circuits configured to/from other nodes on the ring are lost.
Figure 1-103. Double-break Operation
Point-to-Point Traffic Overlay on a Ring

Point-to point overlay operation is illustrated below. The additional capacity needed
for overlay is required only on the overlaid links. Overlaid traffic is not ring protected.
260-668139-001
JULY 2014
207
Figure 1-104. Example of a Ring Network with Point-to-Point Traffic Overlay
In this example the links between nodes C, D and E are carrying 32xE1 point-to-point
non-protected traffic as well as 32xE1 ring-protected traffic.
Fiber Ring Closing

One or more radio links in a ring can be replaced with a span of fiber optic cable using
the DAC 155oM. It maps 63xE1 or 84xDS1 from the backplane directly to a single
STM1/OC3 frame, to enable fiber closures without need for external SDH/SONET
muxes.
DAC 155oM uses SFP (small form-factor pluggable) short-range or long range optic
transceiver sub-assemblies to support fiber spans to 15 km or 40 km respectively.
Ring Protection - Ethernet

Eclipse DAC GE3 supports two ring protection mechanisms, Ethernet Ring Protection
(ERP, ITU-T G.8032v2) and RSTP (IEEE 802.1w).
ERP
ERP operation, defined in ITU-T G.8032v2, is an industry-standard fast-acting automatic protection switching (APS) protocol for Ethernet ring topologies. Features
include:
l
l
208
Sub-50 ms reconvergence times on link failure.

Use of standard Ethernet bridging and OAM protocols - as distinct from STP
and RSTP protocols.
Operation on single and interconnecting (multiple) rings.
Support for revertive and non-revertive modes.
AVIAT NETWORKS
ERP provides a highly reliable and stable protection mechanism for ring networks.
Every node participates in building adjacency with its neighboring node and uses
heart-beat messaging to determine the status of its neighbor. When a break occurs, it
is immediately determined through LOS or through heart-beat messaging whereupon
all forwarding tables on nodes are readjusted to use an alternate path on the ring.
l
Loop avoidance is achieved by guaranteeing that at any time traffic may flow on
all but one of the ring links. This link is the ring protection link (RPL), whose
status is controlled by a designated node, the RPL owner.
Under normal conditions the RPL owner blocks the RPL port. Under a ring
failure condition it unblocks the RPL port, allowing the RPL to be used for
traffic.
An APS (Automatic Protection Switching) protocol is used to coordinate
protection actions on the ring(s).
o
A failure on the ring triggers an R-APS(SF) (Ring-APS Signal Fail) message

in both directions from the nodes adjacent to the failed link. These adjacent
nodes also block the ports facing the failed link. On receipt, the RPL owner
unblocks the RPL port.
When a failed link is restored an R-APS No Request message alerts the RPL
owner to start its wait-to-restore (WTR) timer. On timer expiry (revertive mode)
R-APS messaging is used to re-block the RPL port, and advise relevant nodes to
flush their learning table, unblock blocked ports, and return to idle state.
o
Revertive or non-revertive modes can be selected, which apply to the action

to be taken on clearance of a ring link failure.
Configuration begins with the setting of OAM functions (to support R-APS) on the
ring ports. Y.1731 is used as the OAM Mode.
l
Diagnostic intervention is provided for forced and manual switch commands.

The forced switch action is always performed whereas the manual switch is
performed only if there are no existing failures in the ring.
ERP is supported on adaptive modulation ring links. No network reconvergence action will occur with a change of modulation.
ERP on protected/stacked DAC GE3s is supported from from SW release 08.00.
ERP operation requires installation of OAM license EZF-10.
RSTP
RSTP operation is IEEE 802.1w compliant and additionally incorporates Eclipse
Rapid Failure Detection (RFD) and Protection to deliver carrier-class RSTP reconvergence times on an Eclipse radio link failure and subsequent restoration.
The primary configuration parameters used to establish and maintain RSTP on networked switches are Bridge ID, Cost, and Priority.
Bridge ID is used to establish the root (root switch) in an RSTP network, and to support port state selection on other switches in the network.
The bridge ID consists of the bridge-priority + MAC address.
260-668139-001
JULY 2014
209
Bridge priority is user-configurable.
The MAC address is not configurable and is unique to every L2 switch.
For example, with a bridge priority of 300, and a MAC address of

10:6A:05:66:13, the bridge ID is 300-00:10:6A:05:66:13.
The root switch is the logical center of the network. For a typical single gateway
ring (all traffic on the ring is sourced and sunk at one gateway site) the
gateway switch should be elected as the root switch.
The switch with the lowest bridge ID is elected as the root switch. In the event
this switch fails or is withdrawn, the switch with the next lowest-value bridge
ID is elected as the root switch.
o
The root switch is configured to have the lowest bridge priority number.
The switch best positioned to act as the root switch if the root switch fails, is
configured to have the next highest bridge priority number.
If two or more switches are configured with identical bridge priorities, their
MAC addresses determine which switch has the lowest bridge ID.
Cost is set to represent data bandwidth (speed) available on the path connected to a
port, and is assigned a value such that the higher the available speed, the lower the
cost.
l
A lower cost path is always elected over a path with a higher cost. Highest
priority is given to highest speed = lowest value cost.
Costs are added through the network. The cost to root seen from one switch
channel/port is the cost assigned to the channel/port of the switch it is
connected to, plus the path costs on the subsequent links towards the root
switch.
Costs should always be assigned symmetrically on a link/path. For example, if
a cost of 500 is assigned to a transport channel at one end of a link, the same
cost should be assigned to the transport channel at the far-end. The cost (path
cost) for this link is 500 - not 1000. As noted above the cost of a path as seen
from one switch is read from the cost assigned to the path from the switch it is
connected to - it does not add in the cost assigned to its local channel.
Priority determines the port/channel priority and is set to represent how well a
port/channel is located within a network to pass traffic back to the root switch.
Priority only comes into play when cost and bridge ID cannot assist RSTP to decide
which port to elect as the route (forwarding) port, and which to blocking, at a blocking switch. This situation requires costs from the root switch to the blocking switch to
be equal, and likewise the bridge ID on both uplink paths to be the same.
l
l
l
210
Port priority is contained within a Port ID, which comprises the port priority
setting, and the port number.
If port priority is set to the same value, the port with the lowest port number is
selected as the forwarding port.
The figure below illustrates an example ring network.
The root switch (A) is configured with the lowest bridge priority value. (Lowest
value = highest priority). If the root switch fails, the lower-left switch will
become the root switch.
AVIAT NETWORKS
Data bandwidths are equal (150 Mbit/s) on all ring links, and therefore costs
(path costs) have been set to the same value, in this case 300 on all RSTP ports.
This means that from the root switch costs are equal (600) to the top-left
switch. While this determines that switch C is to be the blocking switch, RSTP
costs alone do not help to elect a preferred route, clockwise or anti-clockwise,
from the root switch.
RSTP next looks at the bridge ID on the switches each side of the blocking
switch to determine its preferred route towards the root switch. As switch B has
a lower value than switch D (as determined by the bridge priority settings), the
switch port connected to B is elected as the forwarding port. The switch port
connected to D is set to blocked.
Priority settings have no part to play in electing the root switch and paths from
root in this example. Priority settings can be left as default (0).
Bri dge I D i s used to establ i sh the root DAC GE3 (root swi tch)
Costs (path costs) are used to determi ne a preferred route to/from the root swi tch, fol l owed by Bri dge I D, and fi nal l y Port
I D. At a bl ocki ng swi tch they determi ne whi ch port/channel i s
set to forwardi ng and whi ch to bl ocked.
Figure 1-105. Example Ring with RSTP Settings
Adaptive modulation can be used on RSTP networks. No network re-convergence

action will occur with a change of modulation.
RSTP is supported on single and protected/stacked DAC GE cards.
DAC/Tributary Protection
TDM DACs are used in pairs to provide hot-standby redundancy. The protection partners are installed in slots 1 to 4 in an INU, or slots 1 to 9 in an INUe, except that:
l
260-668139-001
If NMS access is required, which for a DAC only applies to the DAC 155oM or
DAC 155eM, the protection partners must only be installed in slots 1 to 6. (NMS
access is only supported on slots 1 to 6).
If the NPC option is required, it can only be installed in slot 4 in an INU. Slot
10 is dedicated for the NPC option in an INUe.
JULY 2014
211
The protectable TDM DACs are:

l
DAC 16x V2
DAC 3xE3/DS3
DAC 3xE3/DS3M
DAC 1x155o
DAC 2x155o
DAC 155oM
DAC 155eM
DAC 2x155e
Paired DACs are configured as primary and secondary. The primary is the default
DAC for online Rx and Tx.
When a switch occurs, all Tx and/or Rx tributaries/ports are switched to the protection partner.
l
For all protectable DACs except DAC 155oM and DAC 155eM, the Tx and Rx are
switched independently.
For DAC 155oM and DAC 155eM, Tx and Rx are switched together; a Tx switch
switches Tx and Rx, and vice-versa.
Interface protection switching is not hitless. See DAC Protection Switching Criteria on
page 228.
Two protection configurations are supported, tributary protection, and always-on:
Tributary Protection (all protectable TDM DACs except DAC 155eM)
l
A Y-cable assembly connects paired DACs to customer equipment.

o
Optical for DAC 2x155o, DAC 155oM
Electrical for DAC 16xV2, DAC E3/DS3, DAC 3xE3/DS3M, DAC 2x155e
In the Rx direction (from the customer) both DACs receive data, but only the
online Rx DAC sends this data to the TDM bus.
In the Tx direction, the online Tx DAC sends data to customer equipment, the
other mutes its Tx line interface.
Tributary Always-On (all protectable TDM DACs)

l
l
Separate cables connect each DAC to customer equipment.

In the Rx direction (from the customer) both DACs receive data, but only the
online Rx DAC forwards the data.
In the transmit direction both DACs send data to customer equipment, and the
customer equipment switches between these two always-on connections.
Always-on protection is also an option where two Eclipse INU/INUes are to be interfaced using protected DACs.
212
AVIAT NETWORKS
DAC/Ethernet Protection
DAC GE3 supports 1+1 port/module protection plus protected connections (DPP or
backplane) to hot-standby or space diversity RAC 60E or RAC 6XE links.
l
For protected DAC GE3 operation a protection/stacking cable is installed

between ports P5 and the partner DACs set for protected operation
Under protection/stacking the two DAC GE3s behave as a single switch with
independently configurable front panel and backplane ports. Any pairing of
front panel DPP or backplane ports, across one or both DAC GE3s, may be used
to connect to hot-standby or diversity protected RACs. Similarly front panel
ports may be selected to provide protection on user connections.
DPP Protection
This protection mode protects the radio path and DPP ports on the DAC GE3. Two
ports on the DAC are protected and DPP cabled to protected RACs (hot-standby or
space diversity). The figure below illustrates a DAC GE3 with 1+1 RAC 60 cards.
l
l
The primary RAC is default online for Tx and Rx.

An online DPP port failure (P1 in this example), DPP cable disconnection, or
RAC/RFU failure will cause a switch to the standby (secondary) RAC 60.
Switching is not hitless/errorless.
Rx path protection (path voting) is maintained. The online RAC (default the
primary) selects the least errored data stream from both RACs (via the RAC Rx
diversity bus) and forwards it to its DPP port. This path selection/switching
process is hitless/errorless.
Figure 1-106. Basic DPP Protection
Protected/Stacked Operation
Two DAC GE3 cards are interconnected using a protection/stacking cable installed
between ports P5, and configured for protected operation.
l
260-668139-001
The electrical protection/stacking cable installs directly into the P5 SFP cage no SFP transceiver is required.
This cable connection supports data rates to 2.5 Gbit/s (connection bandwidth
between the switches).
Protection/stacking interconnection can also be established using an optical
cable with optical transceivers installed in the P5 SFP cages. This is a
JULY 2014
213
requirement for SyncE, however the resulting connection bandwidth is limited

to a maximum 1 Gbit/s.
o
SyncE clock transport is not supported on the protection cable - for clock
transport between protected DAC GE3s optical SFP transceivers must be
installed in the protection ports and an optical cable set used as the
interconnect.
DAC GE3 1+1 protection switching is not hitless. See DAC GE3 on page 230.
Under protected operation the cards operate as a bridged/stacked switch pair, providing access to eight front panel ports and up to 12 backplane ports.
Each of the front panel ports are independently configurable - the same range of configuration options available on the ports of one DAC GE3, apply to the ports of the
stacked DAG GE3s, except for SyncE using the electrical protection/stacking cable.
SyncE support requires an optical interconnection between ports P5.
Two mechanisms are supported to provide protection on the user connections(s) to
protected DAC GE3s, dual feed and optical Y-cable.
Dual Feed
Redundancy on dual or multiple feed connections between protected DAC GE3s and
an external switch/router can be supported under L2 link aggregation (L2 LAG), or
under a protection protocol such as OAM Continuity Check Messaging (CCM) or
Bidirectional Forwarding Detection (BFD).
L2 Link Aggregation
As well as providing a data aggregation function, link aggregation supports data
redundancy, such that if one member link fails, its traffic is recovered on the remaining link(s). For information on link aggregation see Link Aggregation on page 168.
The following diagrams illustrate traffic paths for normal and fault conditions where
L2 LAG is used as the connection/protection protocol between the protected DAC
GE3s, and an external switch/router. Traffic paths are illustrated by the green and
blue lines, green on the connections to the external device, blue on the DPP connections to RACs.
Under normal no-fault conditions, L2 LAG is established using LACP (Link Aggregation Control Protocol) between the DAC GE3s and the external device.
l
214
Traffic on the connections from the external device is aggregated on the primary
(upper) DAC GE3.
o
For a 1+1 hot-standby or space diversity protected link (DPP protected links)
the aggregated traffic is directed onto the TX online RAC.
For link-aggregated RAC links (L1 LAG or L2 LAG) the traffic is directed to
both RACs.
Traffic protection is provided on the connections to the external device, on the

DAC GE3 cards, and on the RAC links.
AVIAT NETWORKS
Figure 1-107. Normal Operation
The following diagram illustrates example failure scenarios. For a DAC GE3 card failure, the aggregation function established on the primary DAC GE3 is mirrored on the
secondary (lower) DAC GE3.
The redundancy provided is extensive; it address a failure on the external device, the
external connections, a DAC GE3 port or card failure, and a RAC/Link.
260-668139-001
JULY 2014
215
Figure 1-108. Example Failure Scenarios
BFD Protocol
Using a protection protocol such as OAM-CCM or BFD, the connected equipment
determines a preferred transmission path (active and standby) and uses its protection
protocol to detect a failure and redirect traffic onto its standby Ethernet switch card,
and the standby path supported by Eclipse.
In the case of the BFD protocol, BFD hello packets are sent over both the active and
standby ports (cards), and the router selects which port to use as its active port for
traffic. A failure event will cause a switch to the standby path, and traffic is re-routed
through what was the standby port. Failover times are primarily defined by the recurring interval of the BFD hello packets, and typically range in the order of 1 to 2
seconds.
The figure below illustrates operation.
l
216
The DAC GE3s are protected and configured to support two VLANs, one on the
primary DAC GE3, the other on the secondary.
AVIAT NETWORKS
The external switch/router sends traffic and BFD packets over its active path,
but just BFD packets over its standby path. This active and standby data is
captured onto VLANs by the DAC GE3s, and DPP connected by the online DAC
GE3 to its RAC.
A DAC GE3 online user port failure or an Ethernet card failure within the
external equipment will cause the external equipment to switch traffic to its
standby path. This is received on the secondary DAC GE3 and bridged via the
protection cable to the online DAC GE3 module. The primary DAC GE3 module
remains the online DAC GE3, and the online user port is now on the secondary
DAC GE3.
A DAC GE3 module failure, will cause the external equipment to switch traffic
to its standby path, and DAC GE3 operation to the secondary module. The
secondary DAC GE3 is now the online DAC GE3, for port and module, which
also forces a RAC switch. When a DAC GE3 module is switched the online user
and DPP ports follow the DAC GE3.
With an online RAC failure, the switch to the standby RAC also forces an online
DPP port switch, but the online DAC GE3 module and online user port do not
change. DPP traffic from the secondary RAC is directed via the protection cable
to the primary DAC GE3 and to its online user port (Y-cable port). The online
DPP port is now on the offline (secondary) DAC GE3, and the primary DAC
GE3 remains online for module and user port.
The traffic switching process within the external equipment operates independently of
the intervening link operating parameters - it treats the end-end Eclipse link simply
as a transport pipe that supports two independent paths from the forwarding engines,
an online (active) path and the standby path, which are transported over the Eclipse
link as VLANs.
Figure 1-109. Dual-Feed Using BFD Protocol
Optical Y-cable Protection

Optical Y-cable protection applies where protected DAC GE3s must interface to a
single port on an external device. When deployed with protected RACs (hot-standby
or space diversity), it provides full end-end redundancy on Eclipse DAC GE3s and
RAC links.
l
260-668139-001
Y-cable protection is used where redundancy on the connected equipment

(router/switch) is not required or not supported.
JULY 2014
217
A protection/stacking cable is installed between SFP port P5 on both DAC GE3s.

This protection cable plugs in directly SFP transceiver plug-ins are not
required.
An optical plug-in is installed in SFP port P4 on both DAC GE3s.
o
Two optical Y-cables are installed; one for Tx/Rx, one for Rx/Tx).
The figures below illustrate operation.

l
Under normal no-fault conditions both DAC GE3 cards are online to receive
traffic from the connected equipment but only the online RAC forwards traffic
over the link.
Only the online DAC GE3 is transmitting to the connected equipment. The laser
on the standby DAC GE3 is muted.
The external equipment is not involved in the protection process. Failure
detection and service restoration is controlled entirely by Eclipse.
With this mode (DPP cabled) it is possible for the DAC GE3 protected pair to physically reside in another INU; an INU separate from that housing the protected RAC
protected pair.
The protection mechanism considers the DAC GE3 user port(s), DPP port, and DAC
GE3 module separately. The example below illustrates cabling between the modules
for basic protected operation, and the default traffic path.
l
The primary DAC GE3 and its optical Y-cable port are default online to the
external equipment, and is default online to its DPP-connected RAC.
Figure 1-110. Protected DAC GE3 Modules DPP Connected to 1+1 RAC 60
Modules
The figure below illustrates protection behavior for example failure modes.
l
218
An online user port failure will see external traffic redirected to the Y-cable port
on the secondary (offline) DAC GE3, and via the protection cable to the primary
DAC GE3; the online port is now on the offline (secondary) DAC GE3, and the
primary DAC GE3 module remains the online DAC GE3.
With an online DAC GE3 module failure, both port and module online status is
transferred is to the standby DAC GE3, which also forces a RAC switch. (When
a DAC GE3 module is switched the online user port follows the DAC GE3).
With an online RAC/RFU failure, the switch to the standby RAC also forces an
online DPP port switch, but the online DAC GE3 module and online user port
do not change. DPP traffic from the secondary RAC is directed via the
protection cable to the primary DAC GE3 and to its online user port (Y-cable
port). The online DPP port is now on the offline (secondary) DAC GE3, and the
primary DAC GE3 remains online for module and user port.
AVIAT NETWORKS
Figure 1-111. Example Protection Switch Traffic Paths
Y-cable Protection with Backplane-connected RACs

The DAC GE3 modules are transport-channel-connected via the backplane to their protected RAC partners. The figure below illustrates cabling between the modules.
l
260-668139-001
Both DAC GE3 modules are online to receive traffic from the connected
equipment but only the online RAC forwards traffic over the link.
The primary DAC GE3 and its optical Y-cable port are default online to the
external equipment.
The primary DAC GE3 is default online to the 1+1 protected RACs via the
backplane.
An online port failure will see external traffic redirected to the Y-cable port on
the secondary (offline) DAC GE3, and via the protection cable to the primary
DAC GE3; the online port is now on the offline (secondary) DAC GE3, and the
primary DAC GE3 module remains the online DAC GE3 to the backplane.
With an online DAC GE3 module failure, both port and module online status is
transferred is to the standby DAC GE3. (When a DAC GE3 module is switched
the online port follows the DAC GE3). This does not force a RAC switch.
An online RAC failure does not affect DAC GE3 protection status.
JULY 2014
219
Only the online DAC GE3 is transmitting to the connected equipment. The laser
on the standby DAC GE3 is muted.
The external equipment is not involved in the protection process. Failure
detection and service restoration is controlled entirely by Eclipse.
Figure 1-112. Protected DAC GE3 Modules TC Connected to 1+1 RAC 60 Modules
Protection Switching Criteria

For switching criteria and service restoration times, refer to:
l
Switching Guard Times on page 220
Revertive Switch Mode on page 221
Hot-standby and Diversity Switching Criteria on page 221
Dual Protection Switching Criteria on page 225
E1/DS1 Ring Protection Switching Criteria on page 226
DAC Protection Switching Criteria on page 228
Switching Guard Times

To prevent protection switch oscillation a switch oscillation guard time mechanism
applies to all forms of online1 protection switching. The mechanism is described
below.
1.
A period of guard time begins immediately after each protection switch

occurs.
2.
No protection switches are permitted during the guard time. Protection

switching may resume once the guard time has elapsed.
3.
To damp possible oscillations in the system the guard time is adjusted, using
the following rules:
l
l
The guard time doubles after each switch (up to the maximum).
The guard time halves after each period of guard time during which no
switching occurs (down to the minimum).
1It does not apply to diversity-bus (hitless) Rx path switching.
220
AVIAT NETWORKS
When the guard time decays to its minimum, subsequent switch requests are
actioned immediately.
4.
There are two independent guard timers for each protection context, one
associated with TX switching and one associated with RX switching.
5.
The switch guard time has a minimum period of 5 seconds and a maximum
period of 320 seconds (5 x 26 events).
6.
The guard time mechanism is disabled in protection diagnostic modes.
Revertive Switch Mode

Revertive transmitter switching is a feature that favours the primary transmitter over
the secondary transmitter. If the secondary transmitter is online and the primary
transmitter has been free of alarms for a user configurable period, then a transmitter
switch occurs to the primary transmitter. This Tx switch is not hitless. See Transmitter Switching on page 222.
The user configurable revertive switch modes are:
l
l
No Revert. Revertive switching is disabled.

Normal. A revertive switch will occur if the primary transmitter has been free of
all alarms that may trigger a transmitter switch, for a period configured by the
user. The minimum alarm-free period allowed is 20 seconds. Maximum is 24
Hours. A Wait Timer counts down to the switch time. Should an alarm occur
during the programmed alarm-free period, the alarm-free period will restart
only after the alarm has cleared.
Time Of Day. A revertive switch will occur at a user configurable time of day,
providing the requirements of Normal mode are met. The Wait Timer counts
down to the switch time.
Revertive transmitter switching from the secondary transmitter to the primary
transmitter is not subject to the Switch Oscillation Guard Time. See Switching
Guard Times on page 220. This is to avoid possible confusion caused when the
Wait Timer has expired but a switch does not occur due to the guard time.
However, should an oscillation occur, switches from the primary transmitter to
the secondary transmitter will be subject to the Switch Oscillation Guard Time.
Reverti ve Tx swi tchi ng wi l l not occur i f the onl i ne transmi tter
has been manual l y l ocked to the secondary RAC usi ng the
Portal di agnosti c functi ons.
Hot-standby and Diversity Switching Criteria

The Tx and Rx paths are independently switched, except for RAC 60E and RAC 6XE
when configured for DPP operation.
l
260-668139-001
Ethernet DPP data must be received and transmitted on the same port on the
DAC GE3, meaning Tx and Rx online paths must be switched together.
This means that when the DPP is enabled, Tx switch criteria are also Rx Switch
criteria, and vice versa.
JULY 2014
221
If the DPP data cable is removed from the front of a RAC 60E or RAC 6XE when
the DPP is enabled, a protection switch will occur on both the Tx and Rx to the
protecting partner. A DPP Cable Break alarm will also be raised and will remain
until the fault is cleared.
Protection criteria are similar for all RACs, unless otherwise stated. Refer to:
l
Transmitter Switching on page 222
Transmit Switching Criteria, Hot-standby and Space Diversity on page 222
Transmit Switching Criteria, Frequency Diversity on page 223
Silent Transmitter Switching on page 223
Receiver Switching on page 224
Receiver Switching Criteria on page 225
Service Restoration Times for Hot Standby and Diversity on page 225
Transmitter Switching
Transmit switching for hot-standby and space diversity is not hitless. Transmit
switching for frequency diversity is hitless providing the online Tx RAC is not
removed.
The online Tx RAC manages the Tx protection switch function, and is transferred
between RACs to always be with the online Tx RAC.
For hot-standby and space/frequency diversity the default protection configuration
has the primary RAC online Tx and the secondary RAC online Rx.
l
l
Only the online Tx is operational for hot-standby and space diversity.

Both online Tx and standby Tx are operational for frequency diversity. The
online Tx is managing Tx traffic synchronization.
Switching from the online to standby transmitter will not be initiated if the
standby transmitter has failed, or the standby Tx RAC has been removed or
replaced by an incorrect plug-in. Similarly, a switch will not be initiated if the
RFU associated with the RAC has failed or is disconnected.
When a Tx switch from primary to secondary occurs, online Tx status is
transferred to the secondary RAC, and remains with the secondary RAC unless
revertive switching is selected. If not selected, the primary-designated RAC
(default online Tx) is not automatically returned to online transmit on repair or
replacement. Applies to hot-standby and space diversity operation.
The switch of online Tx status is not hitless.
Transmit Switching Criteria, Hot-standby and Space Diversity

Transmitter switching to the alternate transmitter is initiated for the following local
alarm conditions:
l
RAC plug-in is missing or incorrect
RAC software load failure
Transmitter failure, Hot-standby and Space Diversity:

o
222
Tx synthesizer not locked
AVIAT NETWORKS
Tx transceiver failure
Tx power failure
Tx IF synthesizer not locked
Tx RAC IF synthesizer not locked
Modulator not locked
ODU cable unplugged (except RAC 30v2 rev.A)
DPP cable unplugged. (Only applies to DPP-enabled RAC 60E/6XE).
Transmitter switching is also remote-end initiated in the event of an undetected transmitter failure. See Silent Transmitter Switching on page 223.
F or hot-standby i nstal l ati ons usi ng an unequal coupl er the
onl i ne Tx functi on shoul d be returned to the RAC assi gned to
the l ow-l oss si de, normal l y the pri mary desi gnated RAC.
Si mi l arl y, for space di versi ty spl i t-Tx i nstal l ati ons the onl i ne
Tx functi on shoul d be returned to the top ODU/RF U (normal l y
supported from the pri mary desi gnated RAC).
Thi s can be done usi ng the reverti ve swi tch opti ons i n the Protecti on screen, or the manual control s provi ded i n the System/Control s screen.
Transmit Switching Criteria, Frequency Diversity

Both transmitters are operational. A switch only affects the online status of the RACs,
which for frequency diversity is the RAC controlling transmit synchronization.
Online RAC Tx switching is initiated for the following conditions:
l
Silent Transmitter Switching

Silent transmitter switching1 is a feature designed to force a local transmit switch
when both far-end RACs in a hot-standby or space diversity protection pairing 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.
A silent Tx switch command is initiated when both receivers have lost frame synchronization (demodulator not locked alarm).
For RAC 30v3, the switching command is returned to the local-end transmitter via
the NMS channel in the link overhead.
l
The switching command is prompted after a 5 second delay to ensure no

unwanted switching occurs due to momentary path fades or other switching
1Silent transmitter switching is also referred to as RIPS (Remote Initiated Protection
Switching).
260-668139-001
JULY 2014
223
events.
For RAC 60E/6X, the switching command is returned as control bits within the airlink bitstream.
l
The switching command is returned immediately on loss of frame

synchronization (demodulator not locked) on both receive RACs. The switch
oscillation guard timer is employed to minimize the effects of unwanted switch
action due to momentary path fades or other switching events.
Where both RACs 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.
Receiver Switching
Receiver path switching (voting) between the two receiving RACs is hitless (errorless)
for hot-standby and diversity configurations. The least errored data stream is selected
on a frame-by-frame basis within the online RAC, which forwards the stream to the
backplane bus and/or the DPP port on a RAC 60E/6XE.
The online Rx RAC manages the Rx protection switch function, and is transferred
between RACs to always be with the online Rx RAC.
The RAC assigned as the secondary RAC in a protected primary/secondary pairing is
the default online RAC.
In the event of RAC/RFU receive equipment failure:
l
224
If the designated offline RAC/RFU (default primary) receiver fails or is removed,

the receive data stream will not be errored as the RAC designated as online is
controlling the switching and driving the TDM bus.
If the designated online RAC/RFU (default secondary) receiver fails, the receive
data stream will not be errored if the failure occurs prior to the RAC Rx
diversity bus (between RFU antenna input and the RAC Rx diversity bus).
If the designated online RAC/RFU (default secondary) receiver fails after the
diversity bus (between RAC Rx diversity bus and the TDM bus) or is removed,
the offline (primary) RAC/RFU is switched to become the online bus-driving
RAC. This switching is not hitless, and the primary RAC remains as the online
bus-driving RAC until changed within Portal or ProVision, or a subsequent busdrive switch event.
Switching from the online to offline Rx RAC will not be initiated if the offline Rx
RAC has failed, or the offline Rx RAC has been removed or replaced by an
incorrect plug-in. Similarly, a switch will not be initiated if the RFU associated
with the offline RAC has failed or is disconnected.
AVIAT NETWORKS
One gate-array i s empl oyed between the Rx di versi ty bus and

the TDM bus. I t provi des a functi on that i s di rectl y equi val ent
to a recei ve protecti on swi tch.
Correct operati on i s moni tored, and i n the event of an al arm
(software corrupti on) a RAC swi tch command i s i ni ti ated. A
software auto-rel oad to the al armed gate array (from the
embedded software set hel d i n the NCC CompactF l ash) i s al so
i ni ti ated to attempt to cl ear the al arm.
Receiver Switching Criteria

An online RAC receive switch is triggered by one or more of the following conditions:
l
RAC plug-in is missing
RAC plug-in incorrect
RAC FPGA software load failure
Service Restoration Times for Hot Standby and Diversity

Service restoration times (detection, switching and recovery) for a switch event are:
Transmit Switch - Local Alarm
l
RAC 30v3: 200 ms maximum, typically less than 150 ms.
RAC 60E/6XE: Typically less than 50 ms.
Transmit Switch - Silent Transmitter Alarm (Remote Initiated Protection Switch - RIPS)
l
RAC 30v3: 20 seconds maximum (typically less than 7 seconds).
Receive Switch, all RACs

Switching is hitless/errorless for all alarm events except for a failure at the bus-drive
protection switch within the online designated RAC.
The following times are applicable to a bus-drive switch:
l
RAC 30v3: 200 ms maximum, typically less than 150 ms.
Dual Protection Switching Criteria

Dual protection is offered with a frequency diversity master, which means that only
Rx (to the backplane bus) is switched; both subordinate protected links are online
transmitting (transmit protection criteria do not apply).
260-668139-001
JULY 2014
225
Receive Switching Criteria, Frequency Diversity Master

RAC bus-drive switching is initiated between the two subordinate links under the following conditions:
l
RAC component failure:
EEPROM failure
Rx path failure:
o
Rx synthesizer not locked
RF IF synthesizer not locked
Demodulator not locked
ODU/RFU Tx cable IF synthesizer not locked
Service Restoration Times for Dual Protection

For the subordinate links their service restoration times as individual protected links
are unaltered from those stated above for hot-standby and space diversity.
For the frequency diversity master switch only a receive time is applicable (there is no
frequency diversity master Tx switch event; both transmitters are online transmitting).
The master Receive Switch restoration time is 200 ms maximum. It applies for a
switch between a protected link to a protected link.
E1/DS1 Ring Protection Switching Criteria

Data is provided for the NCM based E1/DS1 loopswitch, and for the RAC based SPDH
ring.
E1/DS1 Loop-switch Criteria

These criteria apply to NCM switching between east and west inputs to the loop
switch.
l
l
Switching applies per trib.

If revertive switching is enabled on the NCM, the preferred direction will be
restored on recovery of the failed input after expiry of the loop switch Revert
Wait Timer.
Framed E1/DS1
For framed operation a switch will occur:
226
On receipt of AIS.
On loss of frame (LOF) detection.
AVIAT NETWORKS
For an E1 or DS1 loop an LOF threshold of 1, 2, 3, or 4 is set. It specifies the

number of consecutive mismatches of the frame alignment sequence (FAS)
used to detect the loss of frame. The lower the value the more aggressive.
n
For DS1 framed operation loops only an FAS Detect Size and Multiframe
Type are prompted.
o
FAS Detect Size identifies the number of bits in the Frame

Alignment Sequence (FAS) that the framer looks to match at a time.
Options are Default, or selection of a bit size from 1 to 6.
Multi Frame Type prompts for Automatic Multiframe Detection,

Superframe (SF)/D4, or Extended Superframe (ESF)/D5.
Entries for LOF, FAS Detect Size and Multiframe Type are made in the MCM >
Plug-ins > Loop Switch screen.
Unframed E1/DS1
For unframed E1/DS1 circuits a switch will occur only on receipt of AIS.
Switch Recovery Time
Protection switching on the NCM loop switch is not hitless. The recovery time is nominally 50 ms (typically less than 10 ms for framed, and less than 20 ms for
unframed).
SPDH Criteria
Super-PDH protects the payl oad and al arm I /O addressi ng
between nodes; i t does not protect auxi l i ary data.
Radio Wrap Conditions
Conditions for ring wrapping:
Tx path failure:
l
Tx synthesizer not locked
Tx transceiver failure
Tx power failure
Tx ODU/RFU IF synthesizer not locked
Tx RAC IF synthesizer not locked
Modulator not locked
Rx path failure:
l
Rx synthesizer not locked
Rx IF synthesizer not locked
Demodulator not locked
ODU/RFU Tx cable IF synthesizer not locked
10-6 BER (user-selectable wrap and/or unwrap options)
RAC plug-in is missing

260-668139-001
JULY 2014
227
Fiber (DAC 155oM) Wrap Conditions

For ring-wrap switching conditions, refer to DAC 155oM and DAC 155eM on page 230.
Wrap and Unwrap Times
The wrapping process is performed without any participation of the alarmed RAC or
DAC 155oM, or potentially failed RAC/DAC in the instance of a silent transmitter failure.
Ring wrapping and unwrapping is not hitless:
l
100 ms maximum service restoration time (detection, switching and recovery)

for a ring wrap based on a 16-hop ring, which is the maximum recommended
ring size. It will typically be between 40 and 100 ms, depending on the number
of hops and ring capacity; the higher the capacity, the lower the ring delay.
The revertive switch command for return to normal service is initiated after the
relevant alarms on the failed link have been cleared for a period set by the ErrorFree Timer (default 5 minutes), or by the optional Delay Ring Unwrap Timer,
which sets a time of day for an unwrap. Full restoration of normal traffic
(unwrapped) on the ring occurs within 100 ms of receipt of the revertive switch
command.
Unwrap Timers
An Error-free Timer in the Protection configuration screen sets the period of errorfree operation needed prior to initiation of an unwrap. When a wrap has occurred this
timer counts down towards an unwrap as soon as all wrap conditions are cleared. The
count begins anew should a wrap condition re-occur during the countdown. The time
options are 10 seconds, or 1, 5, or 10 minutes. 5 minutes is default (recommended)
time, providing a balance between ensuring the alarm(s) that precipitated the wrap
are cleared, and returning the ring to its normal unwrapped state.
A Delay Ring Unwrap timer in the Protection configuration screen allows setting of
a time of day when an unwrap will occur providing all wrap conditions have been
cleared for a period not less than that set in the Error-free Timer. This timer has a 1hour window; if the conditions which caused the wrap are not cleared by the Errorfree Timer during this window, then Delay Ring Unwrap resets for the same time the
following day.
The System/Controls screen provides a countdown timer to indicate the time to go
before the ring will unwrap. Applies to both the Error-free Timer and Delay Ring
Unwrap Timer. (Counts down to zero).
DAC Protection Switching Criteria

Trib/card protection is available for E1/DS1, E3/DS3, and STM1/OC3 DACs (including
DAC 155oM and DAC 155eM).
Port/card protection is available for DAC GE3.
228
AVIAT NETWORKS
TDM DACs
Switch criteria are common for all protectable TDM DACs, except DAC 155oM and
DAC 155eM where Tx and Rx tribs are not independently switched.
Protection switching is not hitless.
Refer to:
l
DAC Protection Switching Criteria on page 228
DAC 155oM and DAC 155eM on page 230
DAC GE3
Tx and Rx (traffic ingress/egress) are switched together. Applies to DPP and transport
channel (backplane) RAC connections.
Refer to DAC GE3 on page 230
Swi tchi ng wi l l not occur to a standby DAC i f a bl ocki ng condi ti on exi sts to prevent a swi tch, such as an al arm on the
standby card, or an onl i ne DAC l ocked onl i ne usi ng di agnosti cs.
All Protectable TDM DACs except DAC 155oM and DAC 155eM
Applies to DAC 16xV2, DAC 3xE3/DS3, DAC 3xE3/DS3M, DAC 1x55o, DAC 2x155o,
DAC 2x155e.
Tx and Rx tribs are switched independently. Protection switching is not hitless - the
maximum restoration time for a Tx or Rx trib switch is 200 ms.
Tx Trib Switching
Transmitter switching to the alternate DAC transmitter is initiated for the following
local alarm conditions:
l
SW/HW failure:
o
Plug-in missing or incorrect
FPGA software load failure
LIU failure
Clock generator failure
Rx Trib Switching
Receiver switching to the alternate DAC receiver is initiated for the following local
alarm conditions:
l
260-668139-001
SW/HW failure:
o
Plug-in missing or incorrect
LIU failure
Clock generator failure
Tributary LOS
JULY 2014
229
DAC 155oM and DAC 155eM

The switch criteria for these two cards are identical for hot-standby tributary line protection (DAC 155oM and DAC 155eM) and for ring protection switching (DAC 155oM
only).
When a switch occurs, both Tx and Rx are transferred to the standby DAC 155oM/eM.
Protection switching is not hitless - the maximum restoration time is 200 ms.
A switch occurs on one or more of the following events:
l
Plug-in is missing from a slot configured for a DAC 155oM/eM, or an incorrect

plug-in is inserted
Loss of signal on the STM1/OC3 tributary
RDI in (Remote Defect Indication event)
Signal fail BER (BER below 10-3 threshold)
One or more regenerator section alarms: OOF, LOF, LOS

DAC 155oM/eM swi tchi ng i s i ni ti ated on OOF , LOF , LOS and Si gnal Degrade condi ti ons. Swi tchi ng i s not performed i n RDI
(Remote Defect I ndi cati on) condi ti ons when usi ng Y cabl es
due to the presence of RDI on both DACs. Contai ner protecti on
(nei ther at the hi gh or l ow l evel contai ners) i s al so not supported, as the DAC 155oM/eM swi tches the ful l frame.
DAC GE3
Typical (current) protection switch times for 1+1 protected DAC GE3 cards are as follows.
Table 1-46. Typical Traffic Recovery Times
TC Protection
DPP Protection
Traffic Recovered
Traffic Recovered
Online RAC 60E/6XE removed
Within 50 ms
Within 50 ms
Online DPP port shut down
N/A
Within 50 ms
DPP cable for online port disconnected
N/A
Within 50 ms
Online DAC GE3 removed
Within 50 ms
Within 50 ms
Online optical-Y port shut down
Within 50 ms
Within 50 ms
Online optical-Y port disconnected
Within 500 ms
Within 500 ms
Action
Straight cables are for 'dual-feed' protected operation. See DAC/Ethernet

Protection on page 213.
Optical Y-cables (2) are used to connect to a single/common user interface.
o
230
When a switch occurs, both Tx and Rx are transferred to the standby DAC.
AVIAT NETWORKS
Switch criteria for protected DAC GE3 cards:

DPP Port Protection
l
RAC 60E/6XE failure
Online RAC 60E/6XE removed
Online DPP cable disconnected
Online DPP port shut down (diagnostic command)
DAC GE3 Module Protection

l
Online DAC GE3 card removed
Component/software failure
o
FPGA load failure
EEPROM failure
Memory failure
DPLL failure
PHY 0/1 sub-module failure
DPP 0/1 sub-module failure
User Port Protection with Optical Y-cable

l
Optical Y-cable unplugged
Optical Y-cable port shut down (diagnostic command)
NCC Protection with NPC Option

The NPC plug-in provides protection for NCC backplane bus management (bus clock),
and power supply functions. One NPC can be installed per INU/INUe.
Bus protection protects all tributary and auxiliary traffic; Alarm I/O is not protected.
l
Switching is not hitless for a bus clock failure; restoration is within 200 ms,
during which time all traffic on the node will be affected.
Protection is hitless for a power supply failure. If the NCC converter or one of its
supply rails fails, the NPC will take over without interruption. And vice versa.
When the bus clock has switched to NPC control, it will not automatically revert to
NCC control on restoration of the NCC. Return to NCC control requires either withdrawal/failure of the NPC, or use of diagnostic commands in the System/Controls
screen.
260-668139-001
JULY 2014
231
Co-path Operation
This section provides data on co-path operation using Eclipse co-channel dual polarization (CCDP) options, and STR 600 multi-channel CCDP, ACAP, or ACCP options
using the OBU with ODU 600T.
l
Where two co-path links are required, CCDP provides a solution to operate both
on the same frequency channel, one on the vertical polarization, the other on
the horizontal. A single dual-pol antenna is used.
Where more than two co-path links (split-mount) are required, the OBU
provides an efficient solution to operate four links on two, three, or four
frequency channels. Paired OBU installations are used to support up to 8 copath links.
o
Depending on the channel arrangements one single-pol antenna, or one

dual-pol antenna is used for non-protected configurations.
Two antennas, each supported by one or two OBUs, are used for protected
(space diversity) 4+4 or 8+8 configurations.
References to CCDP/XPIC, ACAP, ACCP have the following meaning:

CCDP: Co-Channel Dual Polarization (V and H). Two links of identical capacity and
modulation operate over the same path, on the same frequency channel, by operating
one link on vertical polarization, the other on horizontal.
XPIC: Cross Polarized Interference Cancellation. Used with CCDP to eliminate residual interference between V and H signals.
ACAP: Alternate Channel Alternate Polarization (V and H). Two or more links operate
over the same path using adjacent frequency channels, with alternating links on vertical and horizontal polarizations.
ACCP: Alternate Channel Co-Polarized (V or H). Two or more links operate over the
same path using adjacent frequency channels, with both/all links on the vertical OR
horizontal polarization.
CCDP Versus ACCP and ACAP
For split-mount links CCDP/XPIC operation provides particularly efficient operation,
both in terms of channel usage and hardware.
l
232
For single-channel CCDP operation the XDM (XPOL Direct Mount) on an Edge
series antenna supports a compact installation with Tx and Rx losses of
nominally 0 dB.
For CCDP operation on multiple adjacent channels the OBU with ODU 600T
provides a compact installation with Tx+Rx system losses (end-end link loss) of
nominally 8 dB. See Outdoor Branching Unit on page 142.
AVIAT NETWORKS
For all-indoor IRU 600 links CCDP/XPIC operation requires separate waveguide runs
to dual-pol antenna V and H feeds. For this reason single-run ACCP may be preferred,
however minimum T-T and R-R spacings and minimum T-R separations must be
strictly maintained. For information on IRU 600 ACCP operation and limitations as it
applies to two or more links on a common waveguide feed, contact Aviat Networks or
your supplier.
For split mount links ACCP is not an efficient solution as it requires use of an ODU
coupler, with inherent losses of nominally 3.5 dB per Tx and Rx side (equal-loss
coupler) for a 7 dB total.
ACAP is another option. It is particularly applicable on split mount links where the
two channels must be located first-adjacent, as the V and H polarization isolation virtually eliminates any interference that would otherwise apply. As for CCDP operation,
the XDM with an Edge series antenna should be used, though XPIC is not used meaning the RACs do not need to be XPIC capable. Note that use of the XDM in this manner is not just limited to first-adjacent operation.
The figure below below shows the relative difference between CCDP, ACAP, and ACCP
for co-path operation.
l
The CCDP/XPIC RACs are on the same frequency channel, with one configured
for vertical polarization, and the other for horizontal.
ACAP should be used for links on first adjacent channels to minimize inter-link
interference. RAC 30v3 or RAC 60E can be used for ACAP links (XPIC is not
relevant).
When links are on second adjacent or wider channel spacings ACCP (alternate
channel co-polarized) can generally be used - both links on the V or H
polarization. But before considering this option contact Aviat Networks or your
supplier for guidance on minimum T-T and T-R requirements.
Figure 1-113. Illustration of ACCP, ACAP and CCDP (28 MHz Channels)
On CCDP/XPIC links RAC 6XE is required. Operation is supported on all Eclipse frequency bands (is band agnostic).
l
ETSI operation is supported on 7, 13.75, 27.5, 40, and 55 MHz channels.
ANSI operation is supported on 30, 40 and 50 MHz channels.
XPIC is supported on all ACM modulations plus selected fixed-only

modulations. See Link Capacity, Throughput and Latency on page 42
OBU operation (with ODU 600T) for CCDP, ACAP, and/or ACCP is available on ETSI
bands and is scheduled for ANSI.
260-668139-001
JULY 2014
233
ETSI bands 5, L6/U6, 7, 8, 10/11 GHz, for channel sizes 27.5, 40, 55 MHz.
ANSI bands 5, L6/U6, 7, 8, 10/11 GHz, for channel sizes 30, 40, 50 MHz.
ACM or selected fixed-only modulations are supported.
Refer to:
l
Antennas for CCDP on page 234
XPIC RAC Operating Guidelines on page 235
Example Co-Path Configurations on page 239
Antennas for CCDP

Split-Mount Single-Channel Installations
The recommended antennas for CCDP (or ACAP) operation are the Eclipse Edge series
antennas from Aviat Networks.
l
These shielded high-performance antennas have a circular waveguide feed-point

to accept an Eclipse XDM (XPOL Direct Mount), which supports direct
mounting of the two ODUs needed for CCDP operation. See XDM below.
They are available for bands 7 to 42 GHz, and in sizes from 0.3m to 1.2m,
depending on the frequency band.
High performance dual polarized antennas with separate feedheads for each polarization may also be used. These require remote mounting of the ODUs and flex waveguide connection (or coax at 5 GHz) to the antenna V and H feeds.
l
Such antennas are required where 1+1 protected or space diversity CCDP
operation is needed. Each ODU pairing for 1+1 operation (one pair for V, one for
H) is installed on a remote-mounted coupler, which is flex waveguide (or coax)
connected to its respective V and H feed.
Split-Mount OBU Installations

For OBU installations employing CCDP (or ACAP), high performance dual polarized
antennas with separate feedheads for each polarization are required. OBUs are flex
waveguide connected (or coax at 5 GHz) to antenna V and H feeds.
All-Indoor Installations
For IRU 600 installations, high performance dual polarized antennas with separate
feedheads for each polarization are required (requires separate V and H waveguide
runs).
XDM
The XDM is installed onto an Edge-series antenna, and the two ODUs, one for vertical, the other for horizontal, are installed onto the XDM.
l
234
The XDM bolts directly onto the back of the antenna - there is no ODU
mounting collar.
AVIAT NETWORKS
The XDM is supplied as a kitset with a mount kit and an OMT (orthogonal
mode transducer) element. The mount supports +/- 4 degrees of rotational
(skew angle) adjustment for XPD optimization purposes.
Insertion losses are nominally 0 dB on both V and H feeds.
Figure 1-114. Eclipse XDM Assembly
Figure 1-115. XDM with ODU 600s
XPIC RAC Operating Guidelines

With CCDP operation XPIC is used to provide any additional cross polarization discrimination needed to avoid unacceptable co-channel interference.
l
Standard high performance shielded antennas typically exhibit 30 dB cross

polarization discrimination (XPD) whereas 40 dB is typical for purposedesigned, high polarization discrimination antennas.
Correct end-end polarization alignment is essential to achieve a path XPD to
closely match the antenna XPD.
The path XPD may reduce dramatically during fading conditions, which is
when the XPIC function provides maximum benefit.
XPIC is used to improve the XPD when needed. It provides up to an additional 20 dB

of XPD, which is achieved by canceling interference caused in the wanted signal by
taking a sample of the unwanted signal received on the opposite polarization.
l
260-668139-001
In a non-XPIC 155 Mbit/s system, ETSI specifies that a co-channel interfering

signal 37 dB below the wanted signal (37 dB C/I) shall not degrade Rx
JULY 2014
235
threshold by more than 1 dB. In an XPIC system ETSI specifies a 17dB C/I for a
1 db threshold degradation.
Each XPIC RAC 6XE operates with an ODU or RFU (IRU 600).
l
l
XPIC RACs can be hot-standby or diversity protected.

Eclipse XPIC operation complies with ETSI EN 301 127 requirements for cochannel operation. This document specifies the performance of a system in the
presence of cross polarization interference (XPI).
The following data introduces DPP-connected and bus-connected operation for

CCDP/XPIC links, plus CCDP settings, protection options, and the use of ATPC on
CCDP links. See:
l
DPP Operation on page 236
XPIC RAC Operating Guidelines on page 235
CCDP Settings, Protection, and ATPC on page 237
DPP Operation
With DPP-connected RACs capacity for Ethernet traffic is restricted only by the 1000
Mbit/s port maximums (L1) on a DAC GE3, and by the maximum of six RACs (RAC
60E or 6XE) that can be supported on one INUe.
l
l
Just one INUe is required to support up to three CCDP/XPIC link instances.

If required, CCDP partner links can be installed across different (co-located)
INUs.
On DPP connected RACs, one co-channel (or adjacent channel) link pair
supports airlink capacities to 2x 366 Mbit/s ETSI (55 MHz channel), or 2x 365
Mbit/s ANSI (80 MHz channel) for total over-air capacities of 732 Mbit/s or 730
Mbit/s respectively. The equivalent nominal L1 port speed maximum is
nominally 900 Mbit/s (64 byte frames).
Two instances of co or adjacent channel link pairs supports combined airlink
totals to 1460 Mbit/s. A minimum of two user ports are required to access the
link aggregated total (a single user port has useable L1 maximum of not more
than 1000 Mbit/s).
For mixed-mode Ethernet plus NxE1, or NxDS1 operation, Ethernet traffic is
connected via the DPP, and E1/DS1 circuits via the backplane. For each E1 or
DS1 transported, the over-air capacity for Ethernet is reduced by 2 or 1.5 Mbit/s
respectively.

When RACs are bus-connected one INU supports a maximum capacity of 100xE1/204
Mbit/s, 128xDS1/198 Mbit/s, or 2xSTM1-OC3/300 Mbit/s. This sets the maximum
combined capacity supported by a co-channel or adjacent channel configuration.
Bus operation is required for TDM connections. Bus or DPP can be used for Ethernet
data.
236
AVIAT NETWORKS
F or Ethernet data the capaci ty l i mi tati ons of bus operati on are

avoi ded by usi ng DPP-connected RAC 6XE cards.
While one INU can be configured with two RAC 6XEs with combined over-air capacities that exceed the bus capacity, the number of Ethernet/E1/DS1/STM1-OC3 circuits that can be terminated on the bus is limited by the bus maximums. For
example, RAC 6XEs can be configured for 64xE1 for a combined 128xE1 total, but
only 100xE1 of this can be used (terminated on the bus).
Two co-located INUs are used to support higher-capacity co or adjacent channel
operation.
l
RAC CCDP partners are installed across the INUs as shown in Example CoPath Configurations on page 239.
More information:
l
For capacity, modulation and channel bandwidth data, refer to Link Capacity,
Throughput and Latency on page 42.
For backplane bus capacity rules, refer to the Eclipse User Manual, Appendix F.
CCDP Settings, Protection, and ATPC

For fixed modulation RAC 6XE operation both RACs must be configured for the same
frequency, Tx power, and capacity/modulation. Not doing so can impact the effectiveness of the XPIC function. The one exception to this rule is a 75xE1/STM1 pairing one link on 75xE1, the other STM1.
For RAC 6XE adaptive modulation both RACs must operate using the same Tx power/frequency/channel bandwidth. The two links operate their ACM stepping independently.
For optimum RSL balance on the V and H links, and hence optimum XPIC effectiveness, ATPC should be OFF on both RAC co-channel links, and ACM should not be
used. (ATPC is fixed to ON on adaptive modulation links).
ATPC shoul d not be used on CCDP/XPI C l i nks where the V+H
antenna cross-pol di scri mi nati on (XPD) i s l ess than 25 dB, or
the l i nk path i s l ong/di ffi cul t. Si mi l arl y, adapti ve modul ati on,
whi ch defaul t requi res ATPC, shoul d not be used on such l i nks.
CCDP links may also be hot-standby or diversity protected. The protection partners must be installed in the same INU and slot-located according to INU RAC protection rules. The XPIC partners can be installed in same or different INUs.
260-668139-001
JULY 2014
237
l
l
Where co-channel links are to be 1+1 protected, both must be 1+1 protected1.
For hot-standby or frequency diversity protection using dual polarized antennas
equal-loss couplers2 should always be used.
Similarly, for space diversity operation all four antennas should be of the same
size (have the same gain).
Protected V and H links operate as two independent links - the standard
protection switch criteria for protected links apply. Refer to Hot-standby and
Diversity Switching Criteria on page 221.
Similarly, Remote Tx mute functions apply where both RACs of a protected pair
fail, are withdrawn, or have their XPIC cables removed or incorrectly connected.
RAC 6XE can be operated i n a non-XPI C mode to provi de an
upgrade path to CCDP/XPI C operati on wi thout hardware
changes.
Remote Tx Mute
This function applies under an Rx failure condition to ensure continued operation of
the remaining link.
l
XPIC interference cancellation cannot function if one of the RACs is withdrawn,

its XPIC cables are removed or are incorrectly installed, or there is a RAC
hardware failure.
Under these conditions the Tx signal (remote transmitter) on the failed link is
muted to prevent unwanted interference to the remaining RAC Rx.
The following table lists conditions under which the remote Tx is muted.
Table 1-47. Tx Mute Request Conditions
Remote Tx Mute Request Alarms
NCC:
RAC missing.
RAC hardware failure: Synthesizer RX LO failure, or synthesizer RX IF

failure.
Path failure:
ODU/RFU cable unplugged, RX synthesizer not

locked, or RX IF synthesizer not locked.
Path warning:
XPIC cable unplugged or XPIC failure.
Where both XPIC cables are removed at the local end, the request to mute will be sent
to both remote transmitters. This mute contention situation is resolved by applying a
bias to the vertical RAC; the remote horizontal RAC Tx is muted, the remote vertical
RAC Tx is not muted.
1If just one of the co-channel links is 1+1 protected, a failure of XPIC cross-connect
between the 1+0 RAC and its 1+1 XPIC partner may cause both V and H receive
streams to error as the discrimination provided under XPIC would be lost. An unlikely
double-failure event would be needed to cause the same error if both co-channel links
are 1+1 protected.
2Optimum XPIC interference cancellation performance requires equal, or near equal V
and H receive signal levels under normal path conditions.
238
AVIAT NETWORKS
Example Co-Path Configurations

Examples are shown for CCDP operation using single and multiple link pairs.
Examples are also shown for ACCP, and CCDP channel arrangements using the OBU.
See:
l
CCDP Configurations on page 239
OBU Configurations on page 242
CCDP Configurations
Example RAC 6XE configurations are shown for Ethernet, Mixed-mode Ethernet with
TDM, TDM only, and protected CCDP operation.
For Ethernet-only operation the DPP is used (is recommended) to connect a RAC 6XE
to its DAC GE3.
l
DPP connection supports link pairings and link capacities to platform

maximums.
o
One INU supports one CCDP/XPIC link pair. Each link can be configured up
to a 366 Mbit/s airlink maximum for a combined capacity of 732 Mbit/s.
One INUe supports up to three CCDP/XPIC links pairs, each link to a 366
Mbit/s airlink maximum, for a combined capacity (3x CCDP pairs) of 2196
Mbit/s.
For link aggregation L1LA should be used in preference to L2 LAG. L1LA

must be used where adaptive modulation is used on member links.
While each front panel port on a DAC GE3 is speed limited to 1 Gbit/s (L1),
the switch throughput is rated at 10 Gbit/s, meaning two or more user
ports/groups can be configured to access link/trunk traffic greater than 1
Gbit/s.
While one INUe supports up to three CCDP/XPIC links with all links
configured to their airlink maximums, where preferred, CCDP link partners
(RAC 6XEs) can be split across two co-located INUs.
For hybrid mixed mode Ethernet+TDM operation use the DPP to connect a RAC 6XE
to its DAC GE3, and the backplane bus to connect to one or more TDM DACs.
l
l
RAC capacity not sent via the backplane bus is auto-assigned to the DPP.
For each configured bus-connected TDM circuit, Ethernet capacity on the link is
reduced by the equivalent Mbit/s.
For TDM operation (bus only) the combined link capacity is restricted to the bus maximums.
l
260-668139-001
One INU/INUe supports one CCDP/XPIC link pair, each to a maximum of 100
Mbit/s (2 or 1.5 Mbit/s bus connection size), or to 150 Mbit/s (155 Mbit/s bus
size).
JULY 2014
239
Higher operational capacity can be achieved by using two co-located INUs to

provide doubled bus capacity. Each is fitted with one RAC of the CCDP/XPIC
pair.
Adaptive modulation can be used on the CCDP/XPIC links providing the native link
XPD is greater than 25 dB.
l
Where link aggregation for Ethernet traffic is to be used under adaptive

modulation use DAC GE3 L1LA.
o
DAC GE3 L1LA auto load balances on modulation/capacity change - L2 LAG

does not re-balance.
CCDP/XPIC links can be 1+1 protected using hot-standby, space diversity, or frequency diversity 1.
Example 1: Ethernet + PDH Terminal

The figure below illustrates mixed-mode Ethernet and NxE1 on a 56 MHz channel.
Ethernet data is DPP-connected and L1 link aggregated; E1 circuits are bus-connected.
For each E1 configured, Ethernet capacity is reduced by 2.048 Mbit/s.
l
On a 56 MHz channel airlink capacity extends to 366 Mbit/s per link to provide
a combined capacity for Ethernet and PDH traffic of 732 Mbit/s.
ODUs are mounted on an XDM, which is direct-mounted onto an Eclipse Edge
series antenna.
16xE1 is sent via the backplane bus, meaning the combined capacity available
on the DPP for Ethernet is 732 less 33 Mbit/s = 699 Mbit/s. The 16xE1 circuits
can be sent over one of the links or split over both links.
Ethernet data on the DPP connections is link aggregated on the DAC GE3 to
provide a capacity for Ethernet of 699 Mbit/s. This equates to a nominal L1LA
throughput of 800 Mbit/s (L1, 64 byte frames).
Figure 1-116. Link Aggregated Mixed Mode CCDP/XPIC Terminal
1ACM is not supported under frequency diversity.
240
AVIAT NETWORKS
Example 2: CCDP/XPIC Ethernet Ring Node

The figure below illustrates CCDP/XPIC operation on L1 link aggregated Ethernet
ring node links.
l
One frequency channel in each direction supports two links to an aggregate

airlink capacity of 732 Mbit/s (56 MHz channel).
ODUs are mounted on an XDM, which is direct-mounted onto an Eclipse Edge
series antenna.
The DAC GE3 is configured for L1 link aggregation, ERP or RSTP ring
protection, and local user interface(s).
An NPC is installed to provide NCC redundancy.
Figure 1-117. Link Aggregated CCDP/XPIC Ring Node
Example 3: Hot Standby CCDP/XPIC Terminal + DAC GE3 Redundancy

The figure below illustrates CCDP/XPIC operation on L1 link aggregated 1+1 hotstandby RAC 6XE links, plus redundant DAC GE3 operation.
l
260-668139-001
One frequency channel supports two 1+1 links to an aggregate airlink capacity
of 732 Mbit/s (56 MHz channel).
ODUs are remote-mounted on a combiner and flex wave guide connected to a
high-performance dual-pol antenna. The combiners must be equal-loss.
Two DAC GE3s are installed as a protected/stacked pair. DPP protection is used
on the RAC 6XE connections.
The protected links are L1 link aggregated on the DAC GE3s. If adaptive
modulation is used, L1 must be selected.
Link aggregation and redundancy is provided on the DAC GE3 user connections
using LACP (external device must be LACP compliant). If the external device
requires single-user-port connection, optical Y-cables are installed from DAC
GE3 ports (P4).
An NPC is installed to provide NCC redundancy.
JULY 2014
241
Figure 1-118. Link Aggregated Hot-Standby CCDP/XPIC Terminal with 1+1

DAC GE3s
Example 4: 2x STM1/OC3 CCDP/XPIC Terminal

The figure below shows a single INU configured as a terminal node for 2x STM1/OC3
operation.
l
It has application where 2x STM1/OC3 must be transported within a 27.5 MHz

channel bandwidth.
o
While 2x STM1 can be sent over a single link, it requires a channel

bandwidth of 55 MHz (128 QAM). With CCDP/XPIC the two STM1/OC3
links occupy the V and H polarizations within a single 27.5 MHz frequency
channel (128 QAM).
Each STM1/OC3 trib is terminated on a DAC 2x155o plug-in.
Figure 1-119. Co-Channel STM1 Terminal
OBU Configurations
OBU configurations are shown for co-path 4+0, 4+4, and 8+0 channel arrangements.
242
AVIAT NETWORKS
Other channel arrangements extend usage to 8+8 space diversity.

Where an OBU is not fully populated e.g. 3+0, the unused ODU port (Rx and Tx)
must be terminated. A weather-protected termination is available from Aviat Networks.
l
Part-population may be by design or result from an in-service withdrawal for

maintenance/repair.
Operation is shown for DPP-connected RACs only. RAC 60E is used for non-CCDP
links, RAC 6XE for CCDP links.
o
Links can be configured up to a 366 Mbit/s airlink maximum.
One INUe supports up to six non-protected links, or 3 protected links. Space

diversity is used (is required) for link/path protection. The OBU does not
support hot-standby operation.
Co-located INUes are used provide capacity for additional RACs.
L1LA should be used in preference to L2 LAG for link aggregation. L1LA

must be used where adaptive modulation is configured on member links.
While each front panel port on a DAC GE3 is speed limited to 1 Gbit/s (L1),
the switch throughput is rated at 10 Gbit/s. This means two or more user
ports/groups can be configured to access link/trunk traffic greater than 1
Gbit/s.
Example 1: 4+0 ACCP Terminal

L1LA is used to aggregate four ACCP links.
l
260-668139-001
256 QAM Max Throughput modulation on 56 MHz channel BWs provides an

airlink capacity of 366 Mbit/s per link, for a total 1464 Mbit/s.
Total throughput using L1LA on the protected/stacked DAC GE3s is nominally
1790 Mbit/s (L1 64 Byte frames).
Two user ports are configured for LACP connection to a L3 switch or similar. Up
to four user ports can be enabled (1 Gibt/s is the nominal L1 maximum per user
port).
Modulation can be adaptive or fixed.
JULY 2014
243
Example 2: 4+0 CCDP Terminal

Four co-path links are arranged as two CCDP link pairs to occupy just two channels.
The channels can be 1st adjacent (as shown) or spaced N-adjacent.
l
244
Using 256 QAM Max Throughput modulation on 56 MHz channel BWs, each
link has an airlink capacity of 366 Mbit/s for a total 1464 Mbit/s.
Total throughput using L1LA on the protected/stacked DAC GE3s is nominally
1790 Mbit/s (L1 64 Byte frames).
Two user ports are configured for LACP connection to a L3 switch or similar. Up
to four user ports can be enabled (1 Gibt/s is the nominal L1 maximum per user
port).
Modulation can be adaptive or fixed.
AVIAT NETWORKS
Figure 1-120. 4+0 Configuration
Example 3: 4+4 Space Diversity Terminal

Space diversity is enabled on two pairs of CCDP links. The channels can be 1st adjacent (as shown) or spaced N-adjacent.
l
260-668139-001
Protected DAC GE3s provide the L1LA function on the co-path links, and an
LACP function on connections to an external switch.
JULY 2014
245
Figure 1-121. 4+4 CCDP Space Diversity Configuration
Example 4: 4+0 CCDP Repeater

Four co-path links are connected east and west on an RSTP ring.
l
246
In each direction the links are arranged as two CCDP link pairs to occupy just
two channels.
One DAC GE3 in each INUe provides the L1LA function. The trunk port on each
is connected to a protected DAC GE3 pair, which provides the RSTP function
and LACP connections to an external switch.
AVIAT NETWORKS
Figure 1-122. 4+0 Repeater Configuration
Example 5: 8+0 CCDP Terminal

8+0 is enabled using two 4+0 OBU configurations. Each OBU has four co-path links
arranged as two CCDP link pairs to occupy just four channels. The channels can be
1st adjacent (as shown) or spaced N-adjacent.
l
256 QAM Max Throughput modulation on 56 MHz channel BWs provides an

airlink capacity of 366 Mbit/s per link, for a total 2928 Mbit/s.
L1 throughput using L1LA on protected/stacked DAC GE3s is nominally 1790
Mbit/s (64 Byte frames) per OBU/INUe, for a total 3580 Mbit/s.
User ports are configured for LACP connection to a L3 switch or similar.
Modulation can be adaptive or fixed
260-668139-001
JULY 2014
247
Figure 1-123. 8+0 Quattro Configuration
248
AVIAT NETWORKS
STM1+1E1 Operation
RAC 30v3 and RAC 60E/6XE support STM1+1E1 operation.
RAC 60E/6XE supports 2xSTM1+E1 operation.
Operation applies to 1+0 or 1+1 hot-standby or space diversity links.
RAC 30v3
l
STM1+1E1: 27.5 MHz, 128 QAM
RAC 60E/6XE
l
STM1+E1: 27.5 MHz, 128 QAM: RAC 60E
STM1+E1: 27.5 MHz, 128 QAM, CCDP/XPIC: RAC 6XE
2xSTM1+E1: 56 MHz, 128 QAM: RAC 60E
2xSTM1+E1: 56 MHz, 128 QAM, CCDP/XPIC: RAC 6XE
DAC 155o, 2xDAC 155o, or 2xDAC 155e plug-ins are used for STM1 trib access. Paired
plug-ins are used for 1+1 hot-standby STM1 trib protection.
The DAC 4x is used for E1 wayside trib access.
To set STM1+E1 operation the INU/INUe backplane bus size is configured for 155
Mbit/s and the relevant modulation profile selected in the RAC under Bandwidth/Modulation.
A maximum of two STM1+xE1 links, or one 2xSTM1+E1 can be configured from one
INU/INUe.
The E1 wayside is transported in the link overhead, and can be dropped and inserted
at intermediate sites independently of the STM1 traffic.
E1 trib cross-connections on the INU backplane use the same 512 kbit/s slots as the
NMS. Ten such slots are provided per backplane. Four are used per E1. With two
STM1+E1 links per INU, all ten slots are used; eight for the two E1s, and two for the
NMS connections to the RACs.
The E1 should not be transported over more than one link hop if the E1 is to be used
for clock reference purposes.
l
l
l
The E1 wayside is transported within the radio overhead; it is not subject to the
clock jitter and wander grooming (clock regeneration) applied within the RACs
for payload traffic.
Clock integrity is important for connection to an E1 sub-rate mux.
Clock integrity is not important where the E1 is used for Ethernet-over-E1, or
for clock-agnostic data transfer on a SCADA network. Multiple hops can be
transversed.
NOTE:
l
260-668139-001
AUX data or NMS circuits cannot be configured if a wayside circuit is

configured, and vice versa.
JULY 2014
249
AUX circuits can be configured on a link using an STM1+1E1 modulation

setting providing no wayside circuit is configured.
If a wayside circuit is configured, AUX circuits cannot be configured.
The waysi de E1 must not be used beyond one radi o hop i f i t i s
to be used for cl ock reference purposes.
RAC 60E or RAC 30 1+0 Operation

The figure below illustrates 2xSTM1+E1 and STM1+E1 operation for:
A.
Simple 2xSTM1 +E1 link using RAC 60E.
B.
Separate STM1+E1 links from one INU to separate sites. 2xSTM1 is the
maximum supported on the INU/INUe backplane. Links can be RAC60E or
RAC 30.
C.
2xSTM1+E1 link to an intermediate node where one STM1 and the E1 wayside
is dropped. The second STM1 is forwarded to the end terminal, to which an
E1 wayside can be included - as shown. Note that at the intermediate site ten
512 kbit/s backplane slots are used (the maximum), eight for the E1 waysides,
and two for the RACs.
Figure 1-124. RAC 30v3 1+0 STM1+1E1 Example Link Configurations
250
AVIAT NETWORKS
RAC 6XE CCDP 1+0 Operation

The figure below illustrates RAC 6XE CCDP/XPIC operation for:
D.
A simple link. The two STM1 tribs at each end are accessed using one DAC
2x155o. Similarly, the two E1 tribs are accessed using a DAC 4x.
E.
Repeater for two STM1+E1 links. Two INUs are required at the repeater site to
provide the total of twelve 512 kbit/s backplane slots needed: eight for the two
E1 waysides directed to the remote site, and four for the RACs (one per RAC).
F.
Two 2xSTM1+E1 links with a 2xSTM1+E1 drop at the intermediate site, and
2xSTM1+E1 to the end site.
260-668139-001
Two INUs are required at the local site as 2xSTM1 is the backplane
maximum for one INU/INUe.
Two INUs are required at the intermediate site for the same reason as above,
plus two INUs are also required to provide the total of eleven 512 kbit/s
backplane slots needed: eight for the two E1 waysides, and three for the
RACs (one per RAC).
JULY 2014
251
Figure 1-125. RAC 6XE 1+0 STM1+1E1 Example Link Configurations
1+1 Hot-Standby or Space Diversity Operation

The figure below illustrates RAC 60E hot-standby operation for a 2xSTM1+E1 link.
l
Where STM1 trib protection is required (as illustrated) two DAC 2x155o plug-ins
are used.
The E1 wayside tribs cannot be trib protected.
Figure 1-126. RAC 60E 1+1 2xSTM1+E1 Link
252
AVIAT NETWORKS
Secure Operation
In many networks user access to configuration and monitoring tools is not considered
a problem because the network management Data Communication Network (DCN) is
isolated from the Internet. However, security breaches can be just as threatening from
within private networks as they are over public networks that give hackers an ability
to access network devices, change settings, and cause malicious service interruptions.
Eclipse security options are designed to meet market requirements for secure access to
network equipment, and secure delivery of customers traffic. They are designed to prevent unauthorized access and interference from hackers.
These options address control of local user access, centralized management of user
authentication, and payload encryption:
l
Secure Management to secure management access, configuration, and

control.
o
Three levels of security are provided, Basic, Strong, or FIPS 140-2.
Strong and FIPS are licensed features.
FIPS requires installation of both Strong and FIPS feature licenses.
RADIUS Client (Remote Authentication Dial In User Service) to support

centralized access control to Eclipse radios.
o
RADIUS Client is a licensed feature.
Payload Encryption to encrypt all traffic carried over a radio link.

o
Payload encryption is a licensed feature.
When login security (Basic, Strong, FIPS) has been set, a window is displayed immediately after Portal Start-up, in which username and password are prompted.
Refer to:
See Secure Management on page 253.
See RADIUS Client on page 258.
See Payload Encryption on page 259
Secure Management
Eclipse supports three levels of user access authentication, Basic, Strong, or FIPS 1402.
l
260-668139-001
Under Basic security the user login process is held secure through simple
password protection.
Under Strong and FIPS, access is held secure from unauthorized access using
advanced encryption protocols. Additionally, under FIPS, internal components
are concealed from external viewing and anti-tamper labels are applied.
JULY 2014
253
Eclipse secure management is about Strong and FIPS security. Implementation

requires co-operation between the equipment under management (Eclipse devices)
and the management equipment, in this case the Portal craft tool and the ProVision
EMS (or other authenticated management system). This is achieved through use of
secure, encrypted communication protocols, a requirement for complex passwords,
and protection against mechanized attacks.
l
Within Eclipse, secure access is achieved on an NMS port by securing all

protocols that use the port.
It secures access & control of the terminal so no one can temper with it locally
or remotely. It does not include a RADIUS capability, therefore user accounts
can only be managed locally. A separate RADIUS client license must be
purchased in order to perform remote user account authentication and
management.
When secure management is active:
o
Only secure versions of the protocols are allowed to access NMS ports.
Eclipse configuration files held on the compact flash card are stored
encrypted.
The configuration state saved to a Portal PC for backup and restore

functionality is encrypted. A restore requires an encrypted backup.
FIPS 140-2 Security

The Federal Information Processing Standard (FIPS) Publication 140-2 is a U.S. government computer security standard used to accredit cryptographic modules.
Eclipse FIPS operation meets verified compliance with Level 2 of this standard.
l
Operation and implementation is independently validated by an accredited lab

under the Cryptographic Algorithm Validation Program (CAVP). The CAVP was
established by NIST (National Institute of Standards and Technology) and the
CSE (Communications Security Establishment) in July 1995.
FIPS verified operation applies to the INUe only. The INUe is the cryptographic
module; it applies to the INUe chassis and its plug-in cards.
The physical installation of the INUe for FIPS compliance requires concealment of
internal components from external viewing, and installation of tamper-evident labels.
l
Louvers are fitted over the side ventilation grills to prevent viewing of internal
components. To accommodate the width with louvers fitted, the rack into which
the INUe is to be installed must have an opening between the posts of not less
than 451 mm (17.75 inches).
Tamper-evident labels are fitted on completion of commissioning tests such
that any removal or attempted removal of plug-in cards or louvers is made
obvious.
RADIUS Client and Payload Encryption are supported under FIPS operation.
I nstal l ati on and operati on data for F I PS i s provi ded i n the
Avi at publ i cati on: Ecl i pse User Manual Addendum for F I PS 1402.
254
AVIAT NETWORKS
Strong Security
Eclipse Strong security encompasses the majority of the operational requirements specified under FIPS, with support for standardized protocols based on FIPS. However
unlike FIPS, operation is not independently validated, and it omits some of the self
tests and integrity checking demanded by FIPS.
FIPS Versus Strong Security
Compared to Eclipse Strong security, FIPS additionally provides:
l
FIPS 140-2 approved/certified operation.
Provision of only FIPS approved cryptographic algorithms for:
Secure management interfaces
Payload encryption key exchange and traffic encryption/decryption
SNMPv3
Power-up self tests for:

o
Software integrity
Known Answer Tests (KATs)
Payload encryption bypass tests
Manual key entry tests
Operation of the INUe in safe-mode when power-up self tests fail, and in RAC
safe-mode when the RAC power-up self test or a bypass test fails.
Manual and automatic key zeroization capabilities.
Specific FIPS alarms and events for:
Power-up self test pass/fail
Payload encryption bypass test pass/fail
Integrity checking of new software during upgrades using a FIPS approved

algorithm.
Prevention of accidental turning-off of FIPS mode.
FIPS operation provides highest levels of secure management.
User Management
User management options enable you to add, delete, or modify local user accounts
and permissions for Basic, Strong, or FIPS security. Under Strong and FIPS it additionally supports SNMPv3 user accounts, mechanized attack prevention, and session
timeouts.
l
Starter accounts are supported to gain access to a terminal that has been newly
configured. These are designed to be admin-user changed to new user
names/passwords on re-start.
Permissions are assigned to a user name for local users. Permissions are
categorized by admin, crypto, engineer, or operator.
o
260-668139-001
Permissions determine what access rights you have to view and change
settings under secure login.
JULY 2014
255
Mechanized attack prevention monitors the number of failed login attempts

over a user-configurable attack window.
o
It locks out users if the number of failed logins exceeds a configurable

threshold.
It locks out locked-out users for a configurable blocking period.
Session timeouts can be applied under Strong and FIPS security.

o
Timeout counters are provided for a lost Portal PC connection, and for Portal
PC inactivity.
When a session has been timed out (closed), users are returned to the Portal
login screen with advice that their session has been timed out.
SNMPv3 accounts apply where management access is via clients utilizing the
SNMPv3 protocol. Crypto-level access permissions are required. ProVision is an
example of a client that can be SNMPv3 connected.
o
Access levels are used to indicate the account access permissions supported
under SNMPv3 connection.
The algorithms used are those recognized by the FIPS 140-2 security
standard.
When a new user is added, an authentication password, privacy password,

and access level are entered.
n
The authentication password protects against access or control by

unauthorized users.
The privacy password prevents eavesdropping. SNMP packets are

encrypted based on the privacy protocol and password assigned to a
user.
Security and Log Management

Options address access security and control, the security of stored data, logging into a
syslog collection server, authentication of OSPF messaging, warning banners, and
SNMPv3 Traps.
Access Security
FIPS or Strong Security is required.
Options are used to secure the login process, the management connections
(Portal/NMS), and the data stored for secure management administration, event
recording/reporting, and terminal configuration. Settable features include:
l
Security type selection.
Security setting on all or selected NMS ports.
SNMP mode selection with options of None, All Supported, SNMPv3 Only.
Selection of encryption cipher suites for Portal or web login using SSL/TLS
negotiation.
Access Control
FIPS or Strong Security is required.
256
AVIAT NETWORKS
An Access Control List (ACL) is used to ensure only address-registered devices have
access to the terminal. Entry options are provided for Portal PCs, and separately for
SMNP-connected remote clients. Each supports a maximum six entries.
An IP address entry can be used to apply to specific user, or a network address
entered to permit a range of IP addresses (users) defined by the netmask.
l
The Portal ACL entry is applicable to both local and remote (NMS network)
connection of Portal PCs.
An SNMP entry is applicable on network connections to a ProVision server or
other NMS, RADIUS, or log collection server. Applies to all supported SNMP
versions: v1/v2c/v3.
Logging
Selectable under FIPS, Strong, Basic or No login security. The logging function is used
to register one or more (max three) syslog collection servers. Servers are identified by
their IP address.
l
Syslog forwards Eclipse Event Browser information to a syslog collection server.

o
With Basic or no login security, browser data is forwarded using the UDP
distribution mode.
With FIPS or Strong security enabled, browser data includes FIPS/Strong

security events and a secure TLS distribution mode.
More than 1000 records can be stored for a radio, with latest events replacing
oldest (FIFO).
The format follows RFC-5424.
The FIPS and Strong security events captured and held secure by the Eclipse Events
Browser, and made available to a syslog collection server, include:
l
Successful login
Unsuccessful login attempt
Logout
Encryption key changes
Encryption suspension
Incorrect license entered
Secure configuration changed
Additionally, where applicable, the following information is collected for each logged
event:
l
Username of user triggering the event
IP address from which the user triggering event is accessing the secured device
Timestamp of the event
Event name/message
OSPF Message Authentication

Under FIPS and Strong security, authentication of OSPF (Open Shortest Path First)
messaging can be set on an Eclipse OSPF-enabled NMS network. OSPF messages
(packets) without the correct Key ID and Key will not be accepted. It is designed to
prevent malicious network routing/disruption through OSPF message attacks.
260-668139-001
JULY 2014
257
Authentication is achieved through use of a Tx Key with matching Rx Key ID and Rx

Key.
Warning Banners
Warning Banners (FIPS and Strong security only) are used to display a security
related posting to a user attempting to login, and another posting after access has
been granted. The banners may be used to display policy regarding use of the equipment and/or legal warnings regarding unauthorized use of the equipment.
l
The pre and the post-access banner messages are independently configurable.
Configuration of the banner messages requires Admin level permissions.
Example entry for pre-login:
WARNING: You are about to access Terminal 12.3 operated by Aviat Networks.
You are required to have a personal authorization from the system administrator
before you access this terminal.
Unauthorized access to this terminal and associated network devices is prohibited.
Example entry for post-login:
WARNING: You have accessed Terminal 12.3 operated by Aviat Networks.

You are required to have a personal authorization from the system administrator
before you operate this terminal and you are strictly limited to the operations set out
in that written authorization.
Unauthorized operation of this terminal and associated network devices is prohibited.
SNMPv3 Traps
SNMPv3 traps can be sent to one or more management devices via the management
network. It is only configurable by Crypto users with FIPS or Strong security enabled.
l
Up to five destination IP addresses (the users) can be established, along with

UDP port number, and user name.
o
Matching secure (crypto level) configuration is required on the user(s) server

for trap receipt.
UDP port number 162 is normally assigned for trap receipt.
A trap rate limit option is provided to limit the maximum number of unique
traps that can be sent per minute.
RADIUS Client
RADIUS management supports authentication and authorization from a centralized
RADIUS Server - it allows a user to maintain user account authentication & management in a central location rather than in each individual terminal. It is implemented according to RFC-2865.
RADIUS Management is licensed. While it is an independent feature, it can only be
enabled with Basic, Strong, or FIPS security, and requires Admin level permissions
(Admin login).
258
AVIAT NETWORKS
l
l
A RADIUS client is loaded into an Eclipse terminal to allow it to interface with

a user's RADIUS server.
The RADIUS server provides centralized management of authentication data for
user names, passwords, and access permissions.
It ensures secure and controlled access to Eclipse devices from Portal and
ProVision, or other authenticated management platforms.
It also ensures that NOC and field users have consistent access privileges
throughout the network, using a common set of user credentials.
When a user attempts to login to a RADIUS client, such as an Eclipse terminal,
the terminal sends the authentication request to the RADIUS server.
Communication between the RADIUS client and the RADIUS server is
authenticated and encrypted.
The RADIUS server function is provided within the ProVision server or from a
dedicated RADIUS server.
RADIUS client can be used with or without Eclipse secure management.
For backup purposes, RADIUS management on an Eclipse terminal can be
configured to work with up to three RADIUS servers. If it fails to access the first
server on an enabled list, it will proceed to the next server.
Note that the permissions for each user (client account) are defined on the RADIUS
server, which requires installation of a 'dictionary' on the RADIUS server (a text file
defining numerical values that correspond to each permission). For information and
guidance on setting up this capability on a server, contact your Aviat Networks representative, or an Aviat Networks help desk.
Figure 1-127. Example RADIUS Server Application
Payload Encryption
Payload encryption is available on RAC 60E and RAC 6XE radio links to prevent
eves-dropping and man-in-the-middle attacks. All payload data is encrypted (all user
traffic and all management overheads).
260-668139-001
JULY 2014
259
It is an independent, licensed feature. It does not depend on the activation of other

security options except that when enabled on a terminal set for Basic, Strong, or FIPS
security, configuration requires Crypto-level permissions.
Operation is FIPS-197 compliant, and can be enabled/disabled independently for each
wireless link from an INU.
Traffic can include Ethernet, DS1/E1, DS3, OC3/STM1, or any mix up to the max capacity allowed by the capacity license.
Under payload encryption the integrity of each data frame sent over the link is
checked to ensure received data has been sent by the intended transmitter. Received
data is replaced with AIS if it detects it has been modified (man-in-the-middle
attack). It provides the same level of security as Wi-Fi and WiMAX.
Encryption selection and cipher key management features include:
l
AES-CCM cipher suite with AES counter mode data encryption and CBC-MAC
data integrity validation.
The encryption scheme is selectable from AES 128 CCM, AES 192 CCM, AES
256CCM.
Each link has a randomly generated encryption key.
o
With Basic or Strong security Diffie-Hellman is used for key agreement

between each side of the link.
With FIPS, keys are exchanged through a DTLS tunnel (Datagram Transport
layer Security).
A user configurable key change option specifies the maximum time a particular
key can be used. Key change is errorless.
A user-configurable Group ID for key generation ensures that only radios that
belong to the group can negotiate an encryption key.
Operation is applicable on most modulation profiles (fixed or adaptive) and on selected CCDP/XPIC options. Contact Aviat Networks or your supplier for details.
260
AVIAT NETWORKS
Alarms Action Operation

An Alarm Actions configuration screen enables the mapping of local alarms (alarm
events) to local and/or remote outputs, and the mapping of TTL alarm inputs to local
and/or remote outputs.
Alarms are mapped to/from an AUX card, or to a DAC 155oM card:
l
Internal alarms can be mapped to a relay output on any AUX in an Eclipse

network.
Internal alarms can be mapped to a DAC 155oM to trigger an optical port shutdown, or raise AIS (Multiplexer Section AIS) transmission.
TTL alarm inputs to an AUX card can be mapped to an output on the same
AUX or to another AUX within an Eclipse network.
See Alarm I/O Interfaces on page 130.

Alarm mapping is achieved by identifying an alarm from the Diagnostic > Alarms list
and configuring the destination terminal though its IP address, followed by the destination AUX card and a relay output port.
l
Alarm on/off actions at destination terminals are initiated by alarm events

configured on sender terminal(s).
Under normal conditions, change of alarm state is signaled by definitive on/off
message send and receipt.
In between such on/off action, keep-alive messages are used to confirm the
continuing status of each alarm action.
If keep alive messages are not received for a period of 3 minutes (nominal), an
alarm action is de-activated (returned to normal) at the destination device. Link
failure is one example where such action can occur.
Al arm Acti ons operati on i s not sel ectabl e (i s not permi tted) as
a confi gurati on opti on when Strong Securi ty i s enabl ed.
Al arms from mul ti pl e termi nal s can be mapped to a si ngl e,
common output on any Ecl i pse termi nal i n the network.
260-668139-001
JULY 2014
261
Orderwire Options
Eclipse 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
provided by Eclipse L2 switch plug-ins. 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 Eclipse an orderwire network can be supported on the Eclipse NMS, a
routed network, or on the L2 LAN payload connections established via an Eclipse Ethernet switch plug-in (DAC GE3) .
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.
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 DACs 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 connection.
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 supported. It uses Session Initiation Protocol (SIP) for establishing call sessions. 1
1 SIP is an RFC standard (RFC 3261) from the Internet Engineering Task Force (IETF).
262
AVIAT NETWORKS
The LP-201 may be ordered from Aviat Networks or Welltech. A user manual is supplied 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
leagacy radio networks, refer to the Aviat Networks paper: Orderwire Interoperability
Between Eclipse and Legacy radios. A user manual is supplied with each Raven
product.
260-668139-001
JULY 2014
263
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 protection 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

XP, Vista, 7).
Files for analysis on PCR are downloaded to a PC from the Portal RAC History
screen, using the Export PCR tab.
RAC 30v3, RAC 60E and RAC 6XE have this PCR export capability.
Downloaded PCR files are opened in the PCR application.
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.
The graph can be scrolled and the period shown on one screen view can be
adjusted from months, to weeks, days, hours, or minutes.
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: RACs on page 281.
PCR is also available to support legacy Eclipse RACs and Aviat Networks legacy
radios: Megastar, Constellation, TRuepoint 5000, TRuepoint 6400.
264
AVIAT NETWORKS
Figure 1-128. Example Eclipse PCR Viewer Screen
260-668139-001
JULY 2014
265
Networking and Management Tools

This section provides an introduction to networking and to the configuration and network management tools, Portal and ProVision.
l
Portal is the Eclipse configuration (craft) tool. It features an auto-versioning

capability so that once installed on a PC, it automatically downloads support
from the radio as needed to ensure Portal always matches the version of system
software supplied, or subsequently downloaded in any radio upgrade.
ProVision is the Aviat Networks element management system (EMS). It is
installed on a Windows or Solaris server, typically at a network operating
center, and communicates with network elements using standard SNMP
UDP/IP addressing and routing.
Ethernet is the primary NMS connection medium. On radio links NMS data is
normally transported in the radio overheads, though in-band (payload)
transport is an option.
Refer to:
l
Networking and Management Tools on page 266
Portal on page 269
ProVision on page 273
Addressing and Routing

Each Eclipse node functions as a router to manage the routing of NMS between nodes,
and from nodes to other management connected devices.
Static and dynamic routing options are supported.
l
Static routing is suitable for simple networks and for networks where no
significant change in routing is expected. A default gateway option is provided.
Dynamic routing makes use of routing protocols OSPF (Open Shortest Path
First), or RIP (Routing Internet Protocol), which dynamically update the
routing tables held within each router through a mutual exchange of messages.
Normally the NMS is transported in link overheads (radio or SDH/SONET), but

options are provided for in-band NMS where the NMS is carried within the IP payload.
IPv4 and IPv6 addressing is supported. CIDR (Classless Inter-Domain Routing) notation is used.
l
IPv6 implementation is dual-stack; either or both IPv4 and IPv6 can be

configured.
o
266
Where both are configured their operation is independent of each other. They
are designed to run independently on the same network infrastructure.
AVIAT NETWORKS
Address translation between IPv4 and IPv6 is not provided.
Dynamic routing of IPv6 packets is enabled through RIPng or OSPFv3.
IPv6 operation is a licensed feature. License EZF-43.
With CIDR a routing prefix is used to identify the network and host portions of
an address.
Address Representation
IPv4 addresses are 32-bit (4 bytes). They are displayed in quad-dotted notation as
decimal values of four octets i.e. as nnn.nnn.nnn.nnn, where nnn can range from 0 to
255. Leading zeros are omitted.
l
The address comprises a network and a host portion. Under class-full

addressing the classes are defined through use of an address mask as A, B, C for
unicast addresses, plus D for multicast, which identify the network and host
portions of the address. Class-less (CIDR) addressing provides superior
granularity on the division of the network and host portions and is represented
by a routing prefix, which appends as a slash character to the address e.g.
192.168.2.0/28.
IPv6 addresses are 128-bit (16 bytes), represented as 8 groups of 16 bits each. Each
group is written as 4 hexadecimal digits and the groups are separated by colons (:),
such as 2001:0db8:0000:0000:0000:ff00:0042:8329. This notation can be abbreviated by application of the following rules:
l
One or more leading zeroes from any groups of hexadecimal digits are removed,
for example, the group 0042 is converted to 42.
Consecutive sections of zeroes are replaced with a double colon (::). The double
colon may only be used once in an address.
For example:
o
Initial address: 2001:0db8:0000:0000:0000:ff00:0042:8329
After removing all leading zeroes: 2001:db8:0:0:0:ff00:42:8329
After omitting consecutive sections of zeroes: 2001:db8::ff00:42:8329
The network and host portions of the address are identified through use of a
routing prefix, which appends as a slash character to the address e.g.
2001:db8::ff00:42:8329/64.
Overhead Transport of NMS

Routed (L3) interconnection applies over Eclipse radio and SDH/SONET links using a
proprietary PPP protocol. Terminals at each site are identified with a unique network
address - the network portion of the IP address must be unique. This separate site network identity means there are many networks in an Eclipse management network.
LAN (L2) interconnection rules apply where two or more terminals are hosted on the
same LAN (same site) - they are configured to have a common network address (the
network portion of the IP address is the same), and a unique host address (the host
portion of the IP address is unique).
260-668139-001
JULY 2014
267
A router function with dynamic and static routing options is provided within each terminal where each is hosted behind its Ethernet NMS port IP address: the terminal
address is the Ethernet port address.
Normally all other ports, such as the Link NMS ports assume the Ethernet port
address, but if required can be configured to have a unique IP addresses. Unique IP
addressing may be used in instances where:
l
l
There is a requirement to partition a network between OSPF and RIP routing.

There is a wish to adopt an IP address structure, which dictates use of unique
IP addresses for each network interface, and to treat the radio link as a
separately identifiable network.
NMS Transport on Radio Link Overheads

On Eclipse radio links a 512 kbit/s overhead is provided for NMS and auxiliary channel (AUX) data.
l
Where no AUX is configured, the full 512 kbit/s is available for NMS.
o
Up to six AUX channels can be configured, with each reducing the overhead
available to NMS by 64 kbit/s. If all six channels are configured, 128 kbit/s
remains available to NMS.
A 512 kbit/s connection supports up to 400 Eclipse terminals.
A 256 kbit/s connection supports 300 Eclipse terminals.
A 128 kbit/s connection supports 175 Eclipse terminals.
NMS Transport on SDH/SONET Overheads

On Eclipse SDH/SONET links (DAC 155oM, DAC 155eM) the RSOH or MSOH is configurable for NMS transport.
l
The MSOH supports 576 kbit/s, of which a maximum 512 kbit/s is used if
dedicated to Eclipse NMS.
The RSOH supports 192 kbit/s.
Note that the use of the MSOH or RSOH for Eclipse NMS means this overhead cannot
be used to support NMS for other devices, such as for ADMs and cross-connects on
the same network.
In-band Transport of NMS

SW enabled in-band (payload) transport of NMS is supported on internal bridged or
routed connections between the NCC Ethernet ports and installed DAC GE3s.
l
268
An internal NCC-to-DAC GE3 connection is provided for in-band NMS, which

conserves all user ports for user data. This connection can be configured to
operate in a bridged mode (L2), or routed mode (L3).
When set for bridged mode the NCC acts as a host on a L2 network that extends
from the NCC front port to the DAC GE3 port, and beyond.
o
An NMS port is auto configured on the DAC GE3 with a user-editable VLAN
identity.
Configuration of static or dynamic routing is not required.
AVIAT NETWORKS
When set for routed mode the NCC acts as a router between the front panel
NCC ports and the DAC GE3 NMS port. The network that the NCC port is
connected to, and the network that the DAC GE3 NMS port is connected to, are
on separate L2 networks and therefore require different network addresses.
o
Each interface (NCC, DAC GE3) hosts an IP address, and static routing is
used to route to a node in the destination network, which similarly requires
configuration of in band NMS.
On the DAC GE3 an NMS port is auto configured with a user-editable VLAN
identity.
Router mode has application at sites providing a connection to the NOC

LAN, and where segmenting of the NMS network is desired.
n
To prevent NOC LAN broadcasts from getting into the radio network, the
NOC LAN should be separated from the radio network using a router.
This router function can be provided by configuring the gateway Eclipse
terminal to router mode. This will require entry of a static default route
in each radio to refer to the NOC LAN via the gateway INU/router.
Similarly, Portal or Provision PCs connected on the NOC LAN will
require a static route to the radio network via the gateway.
For very large radio networks using in-band NMS it may be preferable to
divide the network into multiple L2 segments linked by routers. Router
mode at segment junctions can be used for this purpose. Static routes
will be needed in the routers to refer to each segment, and default routes
will be needed in the bridged radios, or dynamic routing (OSPF) can be
used. Static routes will also be needed in the Portal/Provision PCs to
access the multiple L2 segments.
NMS Transport over 3rd Party Links

Various options can be used to transport Eclipse NMS over intermediary 3rd party
radio or wireline links. These include:
l
Use of a dedicated Ethernet NMS channel provided on the 3rd-party terminal.
In-band transport of NMS (as above).
NMS via a V.11 / RS-422 service channel. Eclipse AUX cards are used to port
Eclipse NMS to a 64 kbit/s sync RS-422/V11 interface.
NMS via an E1/DS1 trib. Eclipse NMS is interconnected to a DAC GE3, then via
a backplane connection to a DAC 16xV2 configured for Ethernet over E1/DS1.
Alternatively, a stand-alone IP-over-TDM converter can be used.
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.
260-668139-001
JULY 2014
269
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 supplied, or subsequently downloaded in any radio upgrade.
Portals connection to an Eclipse INU/INUe 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 270
Portal TCP and UDP Port Usage on page 271
Portal Auto Version on page 271
Portal PC to Eclipse Connection Options on page 271
Log-in Security on page 272
Eclipse Online Help on page 272
Portal Features on page 272
PC Requirements
Hardware Requirements
The minimum PC hardware requirements are:
l
Pentium 4 or later
o
1 GB RAM
250 Mb free hard disk space
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 RJ45 connector for Ethernet local connection.
1280x768 screen resolution
2 or 3-button Mouse
101-key US keyboard
Software Requirements
To run Portal Microsoft Windows XP, Vista, or Windows 7 is required. Earlier operating systems may operate, but are no longer supported/tested.
Both 64-bit and 32-bit versions of Windows 7 are supported.
270
AVIAT NETWORKS
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. 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 software set. This means that:
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.
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-connected 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.
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.
DHCP connection, where the Eclipse node is the server and your Portal PC the
client.
V.24/RS-232 is required in the absence of a DHCP connection option where the

address of a Node/Terminal is unknown. It is typically only used to load an IP
address into a new, unconfigured node, from which point Ethernet is used.
260-668139-001
JULY 2014
271
Log-in Security
Basic, Strong, or FIPS log-in security options can be set.
Basic requires username and password entry at log-in. Options are prompted for
administrator, engineer, or operator log-in permissions.
Strong and FIPS are licensed options and use secured communication protocols.
Options are prompted for administrator, crypto, engineer, or operator log-in permissions. See Secure Operation on page 253.
Eclipse Online Help

Eclipse Online Help provides access to the Eclipse User Manual from Portal for general and context-sensitive viewing. It is a web-based (html) helpset of the Eclipse User
Manual.
It is installed from an installation file on the Eclipse Software Setup CD - the Installer
installs both Eclipse Online Help and Portal application software.
l
l
It displays using the default Web browser on your PC.

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. Portal Diagnostic Features on page
273 introduces diagnostic features. For more information see Diagnostics on page 277.
For detail information, refer to Eclipse User Manual.
Table 1-48. Portal Configuration Overview
272
Configuration
Feature
Function Summary
Information
Terminal name, location and relevant contact details are entered.
Plug-in/module
setup
Screens prompt for all configuration actions relevant to the selected

plug-in.
Protection
settings
Plug-in pairings are configured for protected operation.
Circuit crossconnects
Screens prompt for traffic, auxiliary, and sync multicast crossconnections between relevant plug-ins.
Networking
Screens enable IP addressing and routing for NMS. Also selection of a

DHCP server option, trap destinations, and in-band NMS.
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.
AVIAT NETWORKS
Configuration
Feature
Function Summary
Security and Log

management
Screens prompt actions for secure management access,

configuration, and control.
Licensing
Shows licensed capacity and licensed features, and prompts for the
up-loading of a new license.
Software
management
Supports loading of system software.
Table 1-49. Portal Diagnostic Features

Diagnostic
Feature
Function Summary
System summary
Screen provides an overview of the installed plug-ins, their status,

and traffic interconnections. 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 RACs and Ethernet DACs.
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 Ethernet DACs it presents throughput, discards and errors and
RMON performance data per port and channel.
System controls
Screens present relevant diagnostic menus for setting loopbacks, AIS,

protection locks, Tx mute, and BER testing.
Security/Controls Provides a mechanism to open secure ports (under strong security) for
diagnostic purposes.
Circuit Loopbacks
Supports activation of a both-way loopback on the backplane bus.
Parts
Provides serial number, part number, and time in service for the
selected plug-in.
Advanced
Management
Provides software reset and history-clear functions.
ProVision
ProVision is a manager of network elements; Eclipse terminals and Aviat Networks
partner products. It is installed on a Windows or Solaris server, typically at a network
operating center, and communicates with network elements using standard
LAN/WAN IP addressing and routing.
ProVision provides both management and configuration functions.
260-668139-001
JULY 2014
273
Topics are:
l
Network Management on page 274
Element Configuration on page 274
ProVision Feature Summary on page 274
Network Management
The management application is SNMP based; SNMPv1/2, or SNMPv3 with Secure Management configured. All elements on the network are polled and their responses
checked to determine current 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 operator is dependant on the significance of the change
(event severity), and any event filtering 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 servicelevel 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.
A circuit tracing function automatically discovers the routing of traffic circuits
through the Eclipse network, and the remote download feature supports software
upgrades to selected terminals simultaneously.
Element Configuration
ProVision uses Portal to configure Eclipse terminals. On operator command a Portal
session 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.
Table 1-50. ProVision Feature Summary
274
Feature
Description
Circuit
Diagnostics
Allows you to diagnose problems within a circuit and isolate faulty

equipment.
Circuit Trace
Circuit trace initiates the tracing of all circuits that originate or terminate
from a selected terminal.
Circuit
Provisioning
Provisions / adjusts circuits end-end through a network.
AVIAT NETWORKS
Feature
Description
Device Craft
Tools
Enables you to connect any craft tool to a device to manage, troubleshoot and
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.
Database
Backup
Enables you to enter a backup description and to indicate what the system
should include in the backup, as well as the frequency of the scheduled
backup and any backup purges.
Diagnostic
Tools
Automatically logs into a terminal to retrieve and display its diagnostic data
and settings.
Ethernet BW
Utilization
Presents the Ethernet bandwidth use for a selected part of the network,
which can be set by region, devices or circuit.
Ethernet
Packet Type
and Size
Presents in graphical formats the packet size and type per port and channel
over time.
Ethernet
Throughput
Discards and
Errors
Presents in a graphical format, the Ethernet throughput discards and errors

per port and channel.
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
Notification
Notifies you via email, pop-up message, or audio signal whenever selected
events occur within the network. You can also instruct ProVision to run a
shell script for a batch file whenever selected events occur.
Event PreFilter
Events that match the pre-filter values are blocked before reaching the
system. Filtering events at input reduces the number of events being fully
processed and increases performance.
Event Severity
Each event is color-coded to indicate its severity level. The levels and their
color codes are critical (red), major (orange), minor (yellow), warning
(cyan), normal (green) and informational (white).
Generic SNMP
Devices
Allows you to monitor and manage non-Aviat Networks devices deployed in a

network. Load and edit devices yourself or use one of Aviat Networks' predefined Generic Device Packages.
NBI
Configuration
Management
Collects all information relevant to the configuration of an Eclipse network in

XML format.
NBI Event
Management
Converts ProVision events, as displayed in the event browser, into a

consistent format for porting to the Network Management layer.
NBI
Performance
Data
Management
Converts the collected performance data from the managed network devices
into ASCII text files so that it can be integrated with the Network Management
layer.
NBI Topology
Management
Collects all information on the network topology such as object name, object
type, object container information, device IP address, SNMP community
strings, object coordinates (on the map viewer).
Network Events 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
Interface
(NBI)
260-668139-001
Provides the connection between the ProVision application and the higher
management level functions.
JULY 2014
275
Feature
Description
Performance
Thresholds
Screens enable an alarm function to be associated with one or more RMON

performance statistics, which are captured within 5 minute, 15 minute or
daily bins for each port and channel.
Performance
Trends
Enables you to monitor network performance to help identify bottlenecks

created by problem devices in the network.
Scoreboard
Groups
Provides a summary of the status of a network in a graphical (pie-chart or

bar 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
Capability
Search your network using parameters such as IP address, object container,

location, object type or data collection type, or search the Tree View to find
specific devices.
Security for
Devices
Allows you to set up secure access where a valid user name and password
must be provided to access terminals.
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
Password
Each user has a login and a password set by the system administrator to
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
Devices
Allows you to put a device to sleep. The device is active, but ProVison
ignores all events from the device. This can be useful to prevent
unnecessary events from being collected. A wake command reverses the
sleep command.
Software
Loading
Update and activate operating software for terminals throughout the network
on a scheduled or manual basis.
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.
276
User Accounts
The network administrator can create separate user accounts for each user.
A security access level is assigned based on user permissions.
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
Icons in both the tree viewer and the map viewer indicate changes in the
radios status.
View Submap
View and drill down into the elements of a selected device using a submap.
View via
Physical Map
Viewer
Displays the network as icons with lines representing the links between
radios. Individual containers and radios can be placed anywhere on the
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.
AVIAT NETWORKS
Diagnostics
This section introduces diagnostics provided by Portal for Eclipse. For detailed information see the Eclipse User Manual.
Refer to:
l
System Summary on page 277
Event Browser on page 278
Alarms on page 279
History: RACs on page 281
History: Ethernet on page 282
Performance on page 283
System/Controls on page 289
Parts Screen on page 300
Advanced Management on page 301
System Summary
The System Summary screen provides a real time overview of system status.
It illustrates:
l
Plug-in type, function, location, and status.
Protected function and status.
Configured link capacities.
Backplane cross-connects and status.
Maximum trib capacity for TDM DACs.
Configured Ethernet capacity for Ethernet DACs.
IP address, terminal name, and site name.
260-668139-001
JULY 2014
277
Figure 1-129. Example 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 1000 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 informational). 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 location), 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 (highlighted) 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 plugin.
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.
278
AVIAT NETWORKS
Online Help is automatically opened to the relevant alarm page when the Help
for Event is selected.
Portal automatically opens Online Help when the tab is first clicked, and it will
remain open until closed from within Help.
Figure 1-130. 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
260-668139-001
Tabs indicate an active alarm point, and the color its severity. Colors used
reflect the international severity standard.
Alarm Management options support quick identification of, and navigation
between active alarms.
With Reset History historical events can be removed to display only currently
active alarms and subsequently any new alarms, or change in alarm status.
Help for Alarm provides access to the Online Help alarm files for alarm
description, probable cause and recommended action.
Online Help is automatically opened to the relevant alarm page when the Help
for Alarm is selected.
JULY 2014
279
Figure 1-131. Alarms Screen
Alarms Action
An Alarm Actions screen (configuration screen) supports mapping of alarms to/from
an AUX card or module, or to a DAC 155oM card:
l
TTL alarm inputs can be mapped to an output on the same AUX or to another
AUX within an Eclipse network.
Internal alarms can be mapped to a relay output on any AUX in an Eclipse
network.
Internal alarms can be mapped to a DAC 155oM to trigger an optical port shutdown, or raise AIS (Multiplexer Section AIS) transmission.
Alarm mapping is achieved by identifying an alarm and configuring the destination

Node/Terminal though its IP address, followed by the destination card/module and a
relay output port.
NOTE:
l
280
Alarm on/off actions at destination terminals are initiated by alarm events

configured on sender terminal(s).
Under normal conditions, change of alarm state is signaled by definitive on/off
message send and receipt.
In between such on/off action, keep-alive messages are used to confirm the
continuing status of each alarm action.
If keep alive messages are not received for a period of 3 minutes (nominal), an
alarm action is de-activated (returned to normal) at the destination device. Link
failure is one example where such action can occur.
AVIAT NETWORKS
Alarms from multiple Nodes/Terminals can be mapped to a single, common output

on any Node/Terminal in the network.
History: RACs
The RAC History screen supports graph, report, and combined graph and report
screen views of link-based operational status. For a protected link, the path data (RSL
and G.826) is duplicated.
A resolution option provides 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.
l
l
l
The Graph screen provides a histogram of 15 minute or daily (24 hour) data
bins of RSL, G.826 statistics, event detected, and configuration changes.
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.
Report and Graph screen data can be combined and shown on the same screen.
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 264
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.
260-668139-001
JULY 2014
281
Figure 1-132. Example History Graph Screen
History: Ethernet
The Ethernet History screens support graph, report, and combined graph and report
screen views for DAC GE3.
A resolution option provides 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. Both are captured from power-on.
The data captured includes Ethernet Rx and Tx statistics, events, and configuration
changes. The period of time displayed is user selected. Start and finish times can be
separately set.
The Detail window presents high resolution data and the ability to select a report
range.
l
Statistical data is displayed for a selected bin using mouse-over.
A report range can be selected for display in the Report window.
282
Data is separately displayed for Tx and Rx traffic and for events. Throughputs,
frame types, discards and errors are graphed. Each bin is presented as a vertical
segment, with the width of the segment dependent on the period selected.
Markers at the bottom of a bin indicate that an event (alarm or informational)

has occurred during the bin period. This can be viewed from the Events report
option.
AVIAT NETWORKS
The Report screen provides a summary view of operational status for a selected
period.
Figure 1-133. History Report Screen
Performance
Performance screens support:
l
Link Performance on page 284
NCC Performance on page 285
260-668139-001
JULY 2014
283
E1 Trib Performance on page 285
Ethernet Performance on page 286

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 a selected link.
For RAC 6XE it also provides a measure of received-signal cross-polarization discrimination.
Data is shown in two tables, Status Monitors and G.826 Monitors. For a protected
link, relevant data is displayed for the primary and secondary links.
Status Monitors captures RSL, Remote Fade Margin, Detected Tx power, ODU/RFU
Temperature, -48Vdc ODU/RFU Supply Voltage, Cross-polarization Discrimination,
and Current BER Reading. The cross-polarization discrimination data only applies to
XPIC RACs, and is as measured at the input to RACs (before XPIC discrimination
improvement). All 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.
For RAC 60E and RAC 6XE adaptive modulation the field includes data on the current modulation state being used on the link (modulation rate and coding) for Tx and
Rx. (Tx and Rx are not synchronized - it is possible for a RAC to be transmitting using
one state, and receiving from its remote partner that is transmitting on a different
state).
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.
For RAC 60E and RAC 6XE this field includes data on:
l
Available Rx time (demod locked time - no sync loss).
Sync loss time (demod unlocked).
Time spent on each modulation state.
Where the data packet plane is in use a DPP field captures good/bad packet counts.
284
AVIAT NETWORKS
Figure 1-134. Link Performance Screen
NCC Performance
The NCC Performance screen presents NCC temperature and -48Vdc supply voltage to
the NCC. Screen presentation and navigation is identical to the Link Performance
screen.
E1 Trib Performance
Buffer slip and tributary CRC error performance is available on E1 rates using the
DAC 16x or DAC 4x.
Buffer Slip Warning enables buffer slip events to be captured as warnings (informational events) in the Event Browser screen for the DAC 16x and DAC 4x.
Buffers are used to absorb any small fluctuations between the frequency of the incoming 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
l
260-668139-001
Data is written into the buffer at its arrival rate and read at the local frequency.
The buffer absorbs any small random zero-mean-frequency fluctuations, but
frequency offsets will make the buffer empty or overflow, sooner or later.
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 16x/4X. A trib output
event records a buffer slip on the trib input from the backplane bus, which is in
the trib output direction.
JULY 2014
285
E1 Error Performance enables a cyclic redundancy check (CRC) on DAC 16x and
DAC 4x plug-ins, 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 16x/4x or IDUs
must be operational for user traffic to provide the multiframe needed for the
monitoring process.
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 DAC 16x/4x or IDUs.
Separate monitoring options are provided for upstream and downstream traffic
directions.
The Line Facing option monitors CRC error counts on the E1 stream from the
trib interface.
The Bus Facing option monitors counts on the E1 stream from a link (RAC or
other DAC) via the backplane bus.
Ethernet Performance
Ethernet performance screens support three views; Statistics, Graphs, ERP.
For Ethernet ITU-T Y.1731 service OAM performance see Ethernet OAM on page 190.
Statistics Screen
The Statistics screen provides RMON-1 performance statistics for each port and channel. DAC GE3 stats include per-queue traffic monitoring.
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.
286
AVIAT NETWORKS
Figure 1-135. Ethernet Statistics Screen: DAC GE
Graphs 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 interval.
In the detail (main) window data per capture interval is viewed using your mouse
pointer.
260-668139-001
JULY 2014
287
Figure 1-136. Ethernet Graphs Screen: DAC GE3
ERP Screen
The ERP screen presents summary diagnostic data for each ERP ring.
Figure 1-137. DAC GE3 ERP Performance Screen
288
AVIAT NETWORKS
System/Controls
System/Controls presents diagnostic menus for plug-in cards. See:
l
Safety Timers on page 289
Link Options on page 289
DAC Options: PDH and SDH on page 291
DAC Options: Ethernet on page 294
AUX Menu on page 298
Loopback Points on page 299
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
On for a user-set time
Always on (until manually turned off)
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.
The NCC Test LED flashes orange.
Link Options
For a 1+0 non-protected link the options are:
l
Tx Mute: Mutes the ODU/IRU 600 transmitter. Tx power output under Tx Mute
is less than -50 dBm.
Digital Loopback: Applies a bus facing digital loopback.
IF Loopback: Applies a bus facing IF loopback. IF Loopback forces a Tx Mute.
For a 1+1 protected link the options include:

l
An indication of which Tx and Rx is online.
Controls to lock a Tx and/or Rx online.
An ability to switch to an online secondary from primary, and vice-versa. This

has application in the event a failed RAC/Terminal is restored to service. For
instance, if the primary designated RAC has failed (or is withdrawn), it is not
auto-restored to online transmit, on repair or replacement.
A graphical indication of protection status.
Tx mute and digital or IF loopbacks per RAC.
260-668139-001
JULY 2014
289
The screen below shows System/Controls for a protected link.

Figure 1-138. Link System/Controls Screen: Protected Link
SPDH Ring Link Options

Views and options are displayed for the ring node and for the individual East and
West RACs and or DAC 155oM:
Protection. Status graphic of the ring node, with lock options for East and West
Online and Offline operation.
l
Online locks the selected RAC/DAC online; ring wrapping is disabled by the
selection. It is used for situations where ring wrapping is not wanted, such as
during link testing and alignment. May also be used to return a link from a
wrapped state.
Offline forces a ring wrap at the selected west or east RAC. Forcing a wrap has
the same affect as a path/signal loss, so will also force a wrap at the remote
Node for the affected link (providing the link is not already wrapped).
RAC East. Locks for East RAC Tx Mute, digital and IF loopbacks, and transmit AIS.
RAC West. Locks for West RAC Tx Mute, digital and IF loopbacks, and transmit
AIS.
For a DAC 155oM the East / West tabs provide access to:
l
Line-facing or bus-facing Line Interface (optical trib) loopbacks.
Transmit AIS on the optical Line Interface.
Line-facing or radio-facing Bus Ports (NxE1/DS1)loopbacks.
Locks include a safety timer on all On selections.
290
AVIAT NETWORKS
Figure 1-139. Ring System/Controls Screen
DAC Options: PDH and SDH

Screen-based options support trib-by-trib selection of:
l
Line facing loopback
Radio facing (bus facing) loopback
Transmit AIS
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.
An On selection of loopback or AIS brings up Safety Timer options.
The figure below illustrates application of PRBS, loopbacks, and safety timers.
260-668139-001
JULY 2014
291
Figure 1-140. DAC 16xV2 System Controls Screen
F or STM1/OC3 DACs, the AI S sel ecti on i nserts a PRBS15 pattern (15 bi t pseudo-random bi t sequence).
DAC 155oM/eM support l oopback and AI S opti ons, but do not
i ncl ude a PRBS generator (i nternal BER measurement) functi on.
PRBS Generation
E1/DS1, E3/DS3, and STM1/OC3 DACs (except DAC 155oM/eM) include a PRBS generator and G.821 receiver to 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, a 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 functi ons.
Auto Insertion of AIS or PRBS on Tribs

Auto insertion of AIS/PRBS occurs when:
292
A demodulator unlock occurs
Loopbacks are set
AVIAT NETWORKS
Demodulator Unlock
When a RAC/radio demodulator-unlock occurs, it inserts an alarm signal (AIS or
PRBS15) on all traffic circuits towards the bus/customer. All cross-connected circuits
from this RAC/radio, which for a Node may be to DAC and/or other RAC plug-ins,
will carry this AIS/PRBS. At a DAC/trib, the affected tributaries will carry AIS/PRBS
on the outgoing customer connection. Demodulator unlock may occur under severe
fading or an equipment fault.
l
For all E1, DS1, E3, DS3 DACs/IDUs, AIS is inserted on the affected data-out
tributaries (towards the customer).
For all STM1/OC3 DACs/IDUs, a PRBS15 pattern (15 bit pseudo-random bit
sequence) is inserted on the affected data-out tributaries (towards the
customer).
An on-board master clock within DACs/IDUs maintains customer-facing clocking references 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
For a PDH radio-facing tributary loopback, AIS is transmitted on the affected

tributary towards the customer.
For an SDH radio-facing tributary loopback, PRBS is not transmitted on the
affected tributary towards the customer (an external BERT will indicate a loss of
frame alarm).
For a line-facing tributary loopback, and for a digital loopback, AIS/PRBS 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).
For an IF loopback traffic from the customer is looped back to the customer,
and at the remote end the resultant demodulator-unlock initiates AIS or
PRBS15 on all traffic circuits towards the remote bus/customer. All crossconnected circuits from the remote RAC/radio, which for a Node may be to DAC
and/or other RAC plug-ins, will carry this AIS/PRBS.
AI S/PRBS15 may al so be forced onto a DAC tri butary usi ng the
System Control screen.
Protected DAC Screens

The opening protection window identifies online Tx and Rx status for primary and secondary RACs and supports:
l
Application of Tx and Rx locks.
Online status change.
The DAC (primary) and DAC (secondary) windows include the same loopback, AIS
and PRBS functionality displayed in System/Controls on page 289 for a non-protected
DAC.
260-668139-001
JULY 2014
293
DAC Options: Ethernet

For DAC GE3 the System/Controls screen presents options for Diagnostics, Synchronization, OAM, ERP, STP, LAG, Packet Capture, and MAC Address Table. A Protection tab option is also displayed for 1+1 protected DAC GE3s.
System/Controls: Protection
A protection screen is provided for selection when DAC GE3s are configured for 1+1
protection. It shows primary and secondary status and online locks for each, with a
safety timer.
System/Controls: Diagnostics
The figure below shows the Diagnostic screen for 1+1 protected/stacked DAC GE3
cards with DPP connected RACs. Traffic on RACs in slots 1, 2 and 4 is link aggregated
on the DAC GE3s.
l
294
Control and status modules are shown for all RACs, and for DAC GE3 ports
and channels. Only all enabled ports and transport channels are addressable.
For DPP connections each RAC module provides information on link status.
Mouse-over for more information.
Each port module includes information on negotiated speed, link up, and
Tx/Rx activity. Mouse-over the ports for more information. A 'Shaped Rate'
indicates current transport rate, which with adaptive modulation configured
will adjust to the rate supported by the current modulation in use. A 'Max Rate'
indicates the rate supported by the maximum configured modulation rate.
A diagnostics tab on the DAC GE3 ports/channels provides port shutdown, port
mirror, MAC Flush, and reset options. Reset restores normal port/channel
operation.
With port mirror selected, options are provided to select a mirror port (port for
data analyzer connection), and to set the option to always on, or on only for a
preset time.
AVIAT NETWORKS
Figure 1-141. System/Controls Diagnostics Screen, Protected/Stacked DAC

GE3s
System/Controls: Synchronization
The Sync screen indicates the current sync source for a SyncE configuration (set in the
Plug-ins screen), and the port Master/Slave setting. A port selected as the sync source
is a Slave port for sync purposes. Master indicates it is providing or is available to
provide the clock source from the port. The screen below is for 1+1 protected DAC GE3
cards
Figure 1-142. System/Controls Synchronization Screen, Protected/Stacked
DAC GE3s
System/Controls: OAM
OAM diagnostics of loopback, link trace, frame loss, frame delay, and frame
delay variation are enabled from MEPs configured in the DAC GE3 OAM
screen.
l
260-668139-001
Loopback (ping) and Link Trace (trace route) operation are supported
under 802.1ag and Y.1731 modes.
JULY 2014
295
Frame Loss Statistics and Frame Delay Statistics are supported only under
Y.1731.
Mode selection is made in the DAC GE3 OAM screen.
Note: When Enable Loopback or Link Trace Start is selected, a Send action is
committed meaning any other pending configuration change will also be committed at this time.
The following screens illustrate Loopback and Link Trace operation. Operation
mode is set to Y.1731.
Table 1-51. System/Controls OAM Screen
System/Controls: ERP
ERP diagnostics provide a snapshot of ERP node status, plus provision of commands
for a forced or manual switch.
Table 1-52. System/Controls ERP Screen
System/Controls: RSTP
Data is provided on DAC GE3 RSTP bridge and port/channel designations and status.
296
AVIAT NETWORKS
Table 1-53. System/Controls STP Table for Protected/Stacked DAC GE3
System/Controls: LAG
Data is provided on the discovered trunk and link/port parameters and operational
status with an LACP-compliant partner.
The screen illustrates one LACP instance (1 Trunk) via two ports, P1 and P3.
Table 1-54. System/Controls LACP Table for Protected/Stacked DAC GE3s
System/Controls: Packet Capture

Packet capture is used to capture control (CPU-bound) packets and to download the
pcap (packet capture) file using Portal. The file can then be loaded in Wireshark to
inspect the packets. This capability means capture can be performed remotely,
without a direct Wireshark connection to the user ports.
l
Capture only applies to CPU-bound traffic, which includes DPP packets, and
protocol packets, such as for CFM, CCM, ESMC etc. User traffic is not trapped
to the CPU, hence it is not captured.
Up to 200 packets (across one, some, or all ports) can be captured. Only one capture
can be performed at a time, and starting a new capture will override any previous capture.
l
Packets on the user-selected ports are captured simultaneously and aggregated

into a single file.
A filter can be applied to capture CFM, CCM, RAPS, ESMC, LACP, and/or RSTP
packets.
The packet capture file is auto deleted 5 minutes after creation.

The following screen illustrates operation. It shows that a capture has been completed, and is available to save to your Portal PC.
l
260-668139-001
MAC address data is displayed to aid port/channel identification within the

capture.
JULY 2014
297
The packets captured provide a guide only and may differ slightly from packets put
on the wire or captured by an external device. This is only expected to be an issue in
the Tx direction for frames modified immediately prior to egress, such as for ETHOAM DMM frames (internal time-stamping), and undersized frames (padding
applied).
Figure 1-143. DAC GE3 System/Controls Screen: Control Packet Capture
System/Controls: MAC Address Table

The screen lists the addresses held in the MAC register, with filter options to sort by
MAC Address, Port Members, Status, and VLAN ID.
l
l
An address can be entered to check its presence within the table.

Port Member provides a port-based filter on the MAC address listing. One or
more ports (P1 to P4), can be selected.
Status provides a filter on address type: dynamic, static or invalid.
VLAN ID provides a filter on the VLAN ID range: 0 to 4095.
Figure 1-144. DAC GE MAC Address Table
AUX Menu
The AUX System/Controls screen supports line and radio facing loopbacks on each of
the available communications channels; three for an AUX plug-in. Safety timers are
not supported.
298
AVIAT NETWORKS
Loopback Points
Ethernet Loopbacks
Loopbacks (ETH-LB) are enabled on DAC GE3 under Ethernet OAM. See Ethernet
OAM on page 190.
RAC Link, TDM DAC, AUX, and Circuit Loopbacks

Eclipse supports loopbacks on links, TDM DACs and a selected backplane circuit.
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).
RAC / Radio / Line loopbacks affect all traffic on a link.
A Circuit loopback only affects traffic on the selected circuit.
Loopback timers are provided.
The figure below shows loopback application points for all RACs and TDM DACs
(except DAC 155oM/eM).
AUX supports line and radio facing loopbacks; as for trib DACs.
Note:
l
RAC digital and IF loopbacks (bus facing) are disabled (not selectable) when
Payload Encryption is enabled. (Loopbacks within the secured path are not be
permitted).
An IF loopback forces a Tx mute.
Figure 1-145. Eclipse INU/INUe Plug-in Loopbacks
DAC 155oM, DAC 155eM

DAC 155oM and DAC 155eM support both line side and bus facing loopbacks.
260-668139-001
JULY 2014
299
Figure 1-146. DAC 155oM/eM Loopbacks
The line-facing loopbacks support troubleshooting from the STM1/OC3 line side:
l
l
l
A line facing line-side loopback may be used to verify the integrity of the line
connection at the STM1/OC3 level, including optical transceiver and clock
recovery (for a recovered clock setting).
A line facing bus-side loopback supports BER checks from a remote site on
individual E1/DS1 (VC-12, VC-11, VT-2, VT-1.5) circuits.
The radio facing loopbacks support troubleshooting from the Eclipse radio
network side:
A radio facing line-side loopback loops all E1/DS1 circuits configured on the
DAC 155oM/eM.
A radio facing bus-side loopback supports loops on individual E1/DS1 circuits.
Loopbacks can also be applied on the backplane bus using the Circuit
Loopbacks screen.
Circuit Loopbacks
A circuit loopback places a both-way loopback on the selected circuit on the backplane. Selection applies to all backplane circuit rates. Auxiliary data circuits are also
supported.
l
Only one Circuit Loopback can be applied at a time and only traffic on the
selected circuit is affected by loopback activation.
In conjunction with the built-in PRBS Generator in DACs, circuit loopbacks
provide a user-friendly tool for tracing and checking a circuit through an Eclipse
network.
Parts Screen
The Parts screen presents:
l
Part number
Part revision
Serial number
Time -in-service
This data is provided for:
300
AVIAT NETWORKS
All plug-ins except the FAN
ODUs and IRU 600.
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, the
NCC, ODUs, IRU 600, DAC GE3, NCM.
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
260-668139-001
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.
JULY 2014
301
Index
3
34 Mbps transparent E3
95
A
advanced management
AIS
auto insertion on tribs
alarm I/O interfaces
ATPC
interference of
RAC 40
RAC 4X
auto version
Portal
AUX
system/controls menu
AUX plug-in
data and NMS functions
front panel
interfaces
Node alarm I/O interfaces
auxiliary applications
AUX plug-in
applications
auxiliary data and NMS functions
auxiliary interfaces
301
292
130
159
237
237
271
298
127
129
131
128
130
128
129
128
B
backplane bus capacity
co-channel links
BER testing of tribs
built-in BER tester
236
292
292
C
capacity and bandwidth
Node PDH and SDH
260-668139-001
42
31/07/2014
CCDP
XDM
circuit loopbacks
co-channel
backplane bus capacity
example configurations
operation
remote Tx mute
settings, protection, ATPC
XPOL direct mount
configuration features
Portal
Configurations
1+0 Repeater
FD
FD/SD
HSB
HSB/SD (Split Tx)
N+N Co-Channel Operation (CCDP)
N+N Non-Protected Adjacent Channel
Operation
CRC trib error monitoring
cross-connects
Node
234
300
236
239
232
238
237
234
272
154
155
156
156
155
156
157
157
285
28
D
DAC
DAC 155oM
loopbacks
DAC 155oM front panel
DAC 16x
DAC 16x front panel
DAC 16x/4x
E1 trib error monitoring
DAC 1x155o
DAC 1x155o front panel
DAC 2x155e
plug-ins
DAC 2x155e 110
DAC 2x155e front panel
DAC 2x155o
DAC 3xE3/DS3
DAC 3xE3/DS3 front panel
DAC 3xE3/DS3M
DAC 4x
DAC 4x front panel
99
299
104
88
92
285
98
99
111
98
93
94
94
87
87
302
DAC ES
performance screen
DAC GE
basic port settings
front panel
plug-ins
protection
switching criteria
variants
DAC 155oM
DAC 2x155e
DAC 2x155o
DAC 3xE3/DS3
DAC 3xE3/DS3M
DAC 4x
DAC GE3 Plug-in
diagnostic features
Portal
diagnostics
advanced management
event browser
history
Ethernet
link performance
NCC performance
performance
DAC ES
IDU ES Ethernet
system/controls
AUX menu
PRBS generator
trib error performance
diff files
286
116
125
86
211
228
86
25
22
22
21
21
21
111
273
301
278
281
282
284
285
283
286
286
298
292
285
271
303
286
282
208
278
F
FAN
fiber ring closing
81
208
G
G.821
trib statistics
guard times
292
220
H
history screen
281
I
installation
ODU
waveguide flange data
140
L
licensing
feature licenses
link performance
loopbacks
testing tribs using PRBS generator
73
284
292
E
E3 transparent
Eclipse
diff files
INU
INUe
Eclipse Node
INUs
element configuration
ProVision
Ethernet
DAC ES and IDU ES performance
screen
history screen
ring
Ethernet ring solutions
event browser screen
95
271
15
15
15
274
Modules
ACU
RFU
multiplexer
E13
M13
150
149
95
95
N
naming conventions
Portal
271
AVIAT NETWORKS
NCC
front panel
maintenance V.24 port
NMS 10/100Base-T assembly
performance
protection
NPC
status LED
test LED
user interfaces
network management
Node
capacity and bandwidth
PDH and SDH
cross-connects
plug-ins
protected operation
slot assignments
NPC
front panel
NPC protection option
79
80
80
80
285
231
80
80
80
274
42
28
77
195
27
131
132
231
O
ODU
waveguide flange data
ODUs
data
140
135
P
PC
Portal PC hardware requirements
Portal PC software requirements
performance
DAC ES
link
NCC
trib error monitoring
performance screen
plug-in
DAC 155oM
DAC 2x155e
DAC 2x155o
DAC 3xE3/DS3
DAC 3xE3/DS3M
DAC 4x
260-668139-001
31/07/2014
270
270
286
284
285
285
283
25
22
22
21
21
21
RAC 30
plug-ins
AUX
DAC
DAC 155oM
DAC 16x
DAC 1x155o
DAC 2x155o
DAC 3xE3/DS3
DAC 3xE3/DS3M
DAC 4x
FAN
NCC
NPC
RAC
RAC 30 and RAC 3X
Portal
auto version
configuration features
diagnostic features
diagnostics
Ethernet history
event browser
history screen
performance screen
naming conventions
PC hardware requirements
PC software requirements
power supply
requirements
PRBS generator
setting of
protection
DAC
DAC switching criteria
equipment and radio path
NCC
NPC option
NCC protection
Node
ring
double break operation
fiber closing
point-to-point traffic overlay
unwrap timers
wrap and unwrap times
19
77
127
86
99
88
98
98
93
94
87
81
79
131
82
83
271
272
273
282
278
281
283
271
270
270
33
292
211
228
195
231
196
195
202
207
208
207
228
228
304
service restoration times

dual protection
hot standby and diversity
Super PDH ring delay times
switching criteria
dual protection
ring
switching guard times
trib protection
ProVision
element configuration
feature summary
network management
S
226
225
206
220
225
226
220
196
273
274
274
274
R
RAC
plug-ins
RAC 30
RAC 3X
RAC 40
operating guidelines
RAC 4X
operating guidelines
RAC 30
front panel
Radio Frequency Unit
ring
delay times
Ethernet traffic
fiber closing
operation
protection
north gateway or any-to-any
point-to-point traffic overlay
super PDH
wrap and unwrap times
ring protection
protection
Super PDH ring operation
ring switching criteria
305
82
83
83
service restoration times

dual protection
hot standby and diversity
slot assignments
Node
super PDH rings
switching criteria
system/controls
AUX menu
239
235
19
83
149
27
202
220
298
T
trademarks
transparent E3
trib
error performance monitoring
1
95
285
U
unwrap timers
239
235
226
225
228
W
waveguide
flange data
140
206
208
208
204
202
203
207
202
228
204
226
AVIAT NETWORKS
260-668139-001
WWW.AVIATNETWORKS.COM

Eclipse Platform Product Description Rev - 011

Uploaded by

Copyright:

Available Formats

Eclipse Platform Product Description Rev - 011

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Eclipse Platform Product Description Rev - 011

Uploaded by

Copyright:

Available Formats

ECLIPSE PLATFORM

Copyright & Terms of Use

ECLIPSE PLATFORM PRODUCT DESCRIPTION

North Carolina, USA

Aviat Networks, Inc.

Aviat Networks (S) Pte. Ltd.

5200 Great America Parkway

17, Changi Business Park Central 1

Honeywell Building, #04-01

Fax: + 65 6496 0999

Fax: +1 408 567 7001

Service and Technical Support:

ECLIPSE PLATFORM PRODUCT DESCRIPTION

Americas Technical Help

EMEA Technical Help Desk

Asia Pacific Technical Help

5200 Great America Parkway

Bldg 10, Units A&B

Philexcel Industrial Park

Blantyre, Glasgow, Scotland

Clark Freeport Zone

Phone: +63 45 599 5192

Hamilton: +44 (0) 1698 717 230

Fax: +63 45 599 5196

Phone: 210 561 7400

Paris: +33 (0) 1 77 31 00 33

Fax: 210 561 7399

Fax: +44 (0) 1698 717 204

ECLIPSE PLATFORM PRODUCT DESCRIPTION

ECLIPSE PLATFORM PRODUCT DESCRIPTION

RAC 60E/6XE Capacity, Throughput, Latency

ECLIPSE PLATFORM PRODUCT DESCRIPTION

Outdoor Branching Unit

ECLIPSE PLATFORM PRODUCT DESCRIPTION

ECLIPSE PLATFORM PRODUCT DESCRIPTION

ECLIPSE PLATFORM PRODUCT DESCRIPTION

Eclipse Packet Node Product Description

Introduction To Packet Node on page 10

Platform Elements on page 15

Link Capacity, Throughput and Latency on page 42

Plug-in Cards on page 77

ODUData on page 135

Outdoor Branching Unit on page 142

IRU 600 Data on page 146

ATPC Operation on page 158

Ethernet Operation on page 163

Protected Operation on page 195

Co-path Operation on page 232

STM1+1E1 Operation on page 249

Secure Operation on page 253

Alarms Action Operation on page 261

PCR Operation on page 264

Orderwire Options on page 262

Networking and Management Tools on page 266

Diagnostics on page 277

Avi at Networks i s I SO90001:2008 and TL9000 Certi fi ed. F ul l

ECLIPSE PLATFORM PRODUCT DESCRIPTION

Introduction To Packet Node

Unique Operational Features on page 10