CUSTOMER TRAINING

TECHNICAL TRAINING STUDENT HANDBOOK

Eclipse IRU600 Installation, Operation and Maintenance

SHB-IRU600-E2.3

SHB-IRU600-E2.3
Revision History
Issue No. Issue Date ECO Description of Change / Revision
01 2/09/12 E2.0 Revision and Update to Modularized Eclipse Training platform

02 01/25/13 E2.1 Update

03 06/14/13 E2.2 Update

04 08/06/13 E2.3 Update, Add IRU 600v3 and V.24 setup instructions

Part Number SHB-IRU600-E2.3

Copyright 2013 Aviat Networks, Inc. All rights reserved
Data subject to change without prior notice

Aviat Networks, Inc. www.Aviatnetworks.com

5200 Great America Parkway TAC US/Canada 800-227-8332
Santa Clara, CA 95054 EMEA UK +44(0)1698 717 230
United States France +33 (0) 1 77 31 00 33
Tel: 408 567 7000 Asia/Pacific +63 45 599 5192

SHB-IRU600-E2.3
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 1
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 2
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 3
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 4
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 5
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 6
 Basic Microwave Parameters:

Frequency
The center frequency of the signal to be transmitted, expressed in MHz or GHz
Channel Bandwidth
The amount of spectral space the modulated signal occupies, usually expressed in MHz
T/R Spacing
The difference between the TX and RX frequencies
TX High/Low
States which end of the link transmits the higher or lower frequency of the pair
Tx Power
The output power of the transmitter antenna port, expressed in Watts or dBm
dBm is a logarithmic ratio of power referenced to 1mw. 0dBm = 1mw, Power levels less
than 1mw are expressed as a negative number
RSL (Receive Signal Level)
The power of the signal at the receiver after transmission over the path. Expressed in
Watts or dBm
RX Threshold (or Sensitivity)
A specification of the receiver which states the minimum RSL needed to be above a
certain Bit Error Rate (BER), usually 10-6 or 10-3 .
System Gain
The difference between the maximum TX power and the Threshold of a radio terminal

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 7
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 8
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 9
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 10
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 11
 INU supports up to 3 non-protected links or 1 protected and 1 non-protected link.

INUe supports up to 6 non-protected links, up to 3 protected links, or a combination of

the two.

Each protected link counts the same as 2 non-protected links.

Terminals:
• Single units with fixed Data Rates (Many Legacy options)
• Interfaces with single RFU
• Protected operation requires Paired Units with interconnecting protection cable
• IDU GE3 16X supports 16DS1/E1 plus GigaBit Ethernet in ½ rack space unit
• Only IDU GE3 16x supports IRU 600

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 12
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 13
 Bare chassis is called an IDC, or IDCe.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 14
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 15
 DAC 155oM and AUX plug-ins must only be installed in slots 1 to 6 where access to NMS is
required in its configuration. (NMS cross-connects are only provided on slots 1 to 6). If no NMS
access is required, then these plug-ins can also be installed in slots 7 to 9.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 16
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 17
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 18
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 19
 2x 1RU fan cards can be placed in a INUe if no 2RU fan is available

Portal Tip: There are no configuration options for the fan.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 20
 From SW release 5.0:
• Flexible Node-based Licensing applies for Eclipse Node and Packet Node to
replace/complement RAC-based licensing.
• Node-based licensing requires SW release 5.0 or later. (SW 5.0 or later must be installed in a
Node before installing or upgrading to Node-based licensing).
• Node-based licensing is required for DPP operation and for feature licensing.

•EZF-01: Layer 1 Link Aggregation (DAC GE). Traffic is between the links on a byte-by-byte basis, based
on the capacity of the links. Unlike L2, it is fully effective for just one active session, such as between
routers, or where there are only a few concurrent sessions.
• EZF-02: Adaptive Modulation (RAC 60, RAC 6X). Packet Node adaptive coding and modulation (ACM)
dynamically switches between QPSK, 16 QAM, 64 QAM, or 256 QAM. Code settings additionally provide
two sets of rates for each modulation; one for maximum-throughput, the other for maximum-gain, to provide
eight modulation states in total.
• EZF-03: Secure Management (NMS). Applies to Eclipse NMS access over the network, and to local
access via the Portal craft tool. It also enables secure management access to Eclipse over an unsecured
network, and protects Eclipse configurations from accidental or intentional modification by unauthorized
personnel.
• EZF-04: Payload Encryption (RAC 60, 6X). Encrypts payload data and the management channel in the
wireless link to prevent eavesdropping.
• EZF-05: Ethernet over TDM (DS3, E1, DS1). Enables mapping of Ethernet data to DS3, E1, or DS1 PDH
interfaces using the DAC 3xDS3M or DAC 16xV2. Supports transport of Ethernet data over existing DS3 or
NxE1/DS1 radio or leased-line circuits.
• EZF-06: Radius Server. Enables connection validation to a radius server for centralized account
management.
•EZF-051 – 056: ODU600 High Power (ODUx) States the number of ODU600 units that can be configured
in High Power Mode
•EZF-061 – 066: IRU600v3 High Power (IRUx) States the number of IRU600v3 units that can be
configured in High Power Mode

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 21
 RAC 60 / 6X Information
IF connector SMA[1]
IF interface Transmit 311 MHz, -8.0 to -12.0 dBm
Receive 126 MHz, -8 to -27 dBm
Packet Plane Interface Electrical Interfaces 1x 1000baseT
Connector RJ45
LED Indicators 2x Tri-state ('Online', 'Status')
RFUs supported IRU600, ODU300hp, ODU300ep
Capacities supported 11 - 365 Mbit/s (NxDS1 + Ethernet)
Modulations supported Fixed and ACM QPSK, 16, 32, 64, 128, 256QAM
XPD Improvement RAC 6X only 20 dB
XPIC connectors RAC 6X only 2x SMB
Power consumption RAC 60 / RAC 6X 12 W / 14 W

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 22
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 23
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 24
 • When using CCDP in conjunction with HSBY, Space Diversity, or Frequency Diversity,
both channels will have to switch together if there is any need for a switch of either
transmitter or RAC.

• For CCDP XPIC links, antenna feeds must be correctly aligned to achieve
optimum XPIC performance

• While a dual-feed antenna may be specified with a cross polarization

discrimination of 30 dB, unless the antenna-to-antenna alignment over a link is
correct, the effective discrimination can be significantly less
• The horizontal-to-vertical receive signal discrimination between antenna
feeds must not be less than 25 dB over the link. Ideally it should be up
towards 30 dB.
• High performance shielded antennas typically exhibit 30 dB cross
polarization discrimination whereas 40 dB is typical for purpose-designed,
high polarization discrimination antennas
• Antenna feed alignment between antennas must be checked/set to
maximize the discrimination provided by the antennas. This is done with a
level to verify actual vertical and horizontal alignment of each antenna

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 25
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 26
 Portal Tip: a pair of DAC 16xV2s can be configured for protected operation in the Protection
screen.

Portal Tip: When configured for protection there are options for Y-Cable or Always On in the
DAC 16xV2 Plug-In screen.

• DAC16xV2 can be used for Ethernet over E1/DS1 tributaries (Licensed feature) to transport
Ethernet over legacy DS1/E1 circuits.

•The Ethernet mapping applies to one or multiple E1/DS1 tributaries to a maximum of 16 per card
and may be operated over multiple cards.

Portal Tip: The DAC4x and DAC16xV2 Plug-In screen has DS1 line coding options for AMI and
B8ZS.

•The legacy DAC16x (V1) uses mini RJ21 connectors (2) and is not protectable

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 27
 •E3 data rate is 34.368 Mbps.
•DS3 (T3) data rate is 44.736 Mbps.

•Operational functions supported include:

•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.
•Operation is compatible with industry standard M13
multiplexers.
•Allows side-by-side transport with other DS1 traffic over
an Eclipse link.

•DAC3xE3/DS3 can be used for Ethernet over DS3 tributaries

(Licensed feature) to transport Ethernet over legacy DS3 circuits.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 28
 •STM1/OC3 data rate is 155.52 Mbps.
•DAC 155o and DAC 2x155o tributary cable options provide extension to other optical connector
types.
•DAC 155o and DAC 2x155o can be protected. DAC 2x155e can be protected. Y-cables are fitted
to provide extensions to individual Tx and Rx BNC connectors.

Portal Tip: A pair of DAC155o, 2x155o or 2x155e cards can be protected in the Protection
screen.

Portal Tip: When configured for protection there are options for Y-Cable or Always On in the
DAC Plug-In screen.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 29
 •Applications include:
•Ring closure on an Eclipse Super-PDH ring using optical cable (DAC 155oM to
DAC 155oM).
•Cross-connection of DS1s between two INUs
•Interconnection of an Eclipse Super-PDH network with an SDH core network
(DAC 155oM to external SONET mux.
•DAC 155oMs can be hot-standby protected. Two DAC 1x155oM plug-ins are installed
and Y-cables fitted to provide extensions to individual Tx and Rx LC connectors.

•Options for internal or recovered clocking

Portal Tip: The DAC 155m operates with an E1 or DS1 capable bus which is set in the
circuits screen.

•Mapping options for bit asynchronous or transparent virtual tributary (TVT) modes
•Bit asynchronous is selected on all circuits except those carrying Ethernet data, where
TVT mode must be selected
•Clocking options for recovered-clock or internal
•Eclipse NMS can be transported within the MSOH or RSOH

•SFP = Small Form-factor Pluggable.

•Short range version supports spans to 15 km.
•Long range supports spans to 40 km.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 30
 • When operated as a Trib Module, the PRBS testing diagnostic is not available.

• For more information on ring protection, see Appendix A

• In the current NCM configuration, the two front panel RJ-45 ports are not used.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 31
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 32
 NPC Input Voltage Range -40.5 to -60 VDC
PCC Input Voltage Range 19 to 36 VDC
PCC Output Voltage -56VDC
•Each AUX port can be configured for a DATA or NMS function.
•DATA is configurable for sync or async operation.
•NMS is sync only (provides a V.11/RS442 interface for Eclipse NMS - used to transport Eclipse NMS over a
3rd party 64 kbps data connection)
Portal Tip: Auxiliary channels are configured in the AUX Plug-In screen under the Auxiliary Tab.
Portal Tip: Auxiliary circuits are mapped in the Circuits screen under the Auxiliary Tab.
• The Eclipse has 512kbps of overhead to be shared between the NMS, radio to radio communication, and auxiliary
channels
• The 512kbps overhead is split up into 8 64kbps channels and the NMS/radio to radio communication requires at
least two (128kbps)
• Both the sync and async channels will occupy a 64K channel, even though the async runs at a maximum of 19.2
kbps.
• Auxiliary channels can be AUX to RAC or RAC to RAC cross-connected on the backplane.
• Channels 7 and 8 are reserved for NMS and any other unused contiguous channels, from Ch6 down, will be given
to the NMS. Auxiliary channel mapping should start at ch1 to ensure maximum capacity for the NMS
•See appendix D in the Eclipse user manual for AUX port pin-outs and cable color codes.
• Alarm I/O options for:

• 6x TTL alarm inputs

• 4x TTL alarm inputs & 2x Form C relay outputs

• 2x TTL alarm inputs & 4x Form C relay outputs

Portal Tip: Alarm I/O options are configured in the AUX Plug-In screen under the Alarm I/O Tab.
Portal Tip: Alarm actions can be defined in the Configuration/Alarm Actions screen.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 33
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 34
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 35
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 36
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 37
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 38
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 39
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 40
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 41
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 42
 • The limit of 1 watt means 30dBm, but to account for unit to unit variation
in production Aviat Networks limits the actual power to 29dBm at the
antenna port (exit flange of the ACU) so in no case it can go above
30dBm even with manufacturing variability.
• For XPIC configurations, the power is limited to 26dBm as it is the total
power of all RFU in the antennas that must be limited to 1Watt, so 30-
3dB to cut power in half minus 1dB for variability like about gives
26dBm.

• IRU600, 5.8GHz has been tested and certified for use with a parabolic
antenna with a maximum gain of 46.8dBi. As this product has been
tested and certified as a system with a parabolic antenna, only parabolic
antennas may be used. The maximum gain must also be respected. A
list of suitable antennas has been provided to the FCC for the
certification and the professional installer should refer to this list when
selecting an antenna

• To ensure compliance with the FCC RF exposure requirements, a

minimum distance of 20 meters must be maintained between the
antenna and any persons while the unit is operational. This calculation
is based on the maximum conducted power and maximum antenna
gain.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 43
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 44
 •RSSI - Received Signal Strength Indicator. The raw indicator of signal level at the receiver input
(from the antenna). Usually expressed as a voltage, RSSI is usually converted to dBm and
presented as an RSL. Changes in RSSI voltage are much faster than display screen readings of
RSL, and therefore better for antenna alignment

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 45
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 46
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 47
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 48
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 49
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 50
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 51
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 52
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 53
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 54
 •At each network site, Eclipse terminals must be identified with a unique network
address - the network portion of the IP address must be unique.
Where two or more terminals are co-located (same site) and are Ethernet NMS-
interconnected (on the same LAN) they must be 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).
For Eclipse terminals connected by their Ethernet ports, normal LAN rules apply.
This separate network identity for each site means there are many networks in
an Eclipse management network. Essentially, each network supports just one
host unless other devices, such as other radios, are interconnected via their
Ethernet NMS ports. This is a fundamental difference to a normal network
situation where multiple hosts are almost always LAN-connected under one
network address.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 55
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 56
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 57
 •Logos and icons are used in all screens to assist identification and status.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 58
 •System Summary is a Diagnostics screen. Its function will be covered under ‘Diagnostics’.
•For a new or changed configuration the affected module slots will display an option to
accept the new/current status. This function replaces the Layout screen in earlier SW releases.
•Menu bar and Status bar are common to all screens.
•Note the use of the logos and icons to help represent the item, and item status.
•Right click on a module to view a submenu of relevant screens; left click to select.
•Mouse-over for tool-tips.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 59
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 60
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 61
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 62
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 63
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 64
 Enable DPP must be ticked for DPP operation. A DPP Group ID is prompted.
This can be 0, or a number up to 200 (DPP Group ID does not apply to IDU GE3
16x).
The Node-based Capacity License introduced with SW release 5.0 is required for
DPP operation.
The selected number must also be entered for the relevant port in the DPP
Settings of the partner DAC GE/GE3.
If a number 1 to 200 is entered, a DPP cable alarm will be raised if an incorrect
DPP port-port connection is made (Group ID not matched), or the cable is
disconnected.
If 0 is entered, no alarm will be raised for an incorrect port-port cable connection,
but an alarm will be raised for a missing/disconnected cable.

Portal Tip: for protected RAC pairs the Group ID will automatically be set the
same for both RAC DPP Ports in the RAC Plug-in screen

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 65
 Enable the DPP for the port that is connected to the RAC 60/6X and set the Group ID to match
the RAC

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 66
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 67
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 68
 Advanced options for VLAN tagging, including 802.1Q and QinQ 802.3ac
Data packet plane (DPP) and backplane traffic interconnection to RACs
Advanced traffic shaping for fixed and adaptive modulation links
Superior burst management with 136 Kbytes memory per ingress/egress port buffer
pairing
Jumbo frames to 10 Kbytes bi-directional
1+1 card protection with optical Y-cable or dual-feed
Synchronous Ethernet with Stratum 3 hold-over performance on timing subsystem
Inter-frame gap (IFG) and preamble stripping and re-insertion
RMON stats per port and channel

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 69
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 70
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 71
 P1,P2, P3 are electrical 10/100/1000Base-T RJ-45 ports.
P4, P5, are SFP ports.
For protected DAC GE3 operation, a protection cable is installed between ports P5.
C1 to C6 are transport channel (TC) ports for backplane connection to RACs and/or
DACs.
Ports and channels can be re-named.
The Group Id is the entry for DPP value corresponding to DPP Group Id value for RAC
60/6X

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 72
 Channel Mode. Node/card only - applies only to transport channel connections.
Provides selection of a fast-link-failure detection mechanism.
It is used with Link Status Propagation and adaptive modulation to support fast-
switched failure detection and recovery. Note that operation is end-to-end over a
DAC GE3 link, regardless of the number of radio links traversed.
No Failure Detection (ES Compatibility). For use where DAC GE3 is linked to
a 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. Use this mode for Link Status
Propagation.
Rapid Failure Detection and Protection. Supports continuation of service in
the presence of one or more errored containers. Use this mode for L1LA when
operated using one transport channel to two physical links.
Adaptive Modulation. Similar in operation to Rapid failure Detection and
Protection, but with the inclusion of pre-notification to signal onset of a
modulation change event.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 73
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 74
 Flow Control - To be effective, flow control must be established from the
originating source through to the end point, and vice versa, which means
the equipment
connected to DAC GE3 ports and beyond must also be enabled for flow
control.

MAC Address Learning - Address Learning is default enabled to support

efficient
management of Ethernet traffic in multi-host situations. The option to
disable Address
Learning is for use in a ring/mesh network where protection is provided
by an external RSTP
switch. This is to avoid conflict between the self-learning function within
DAC GE3 and the
external RSTP switch during reconvergence.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 75
 •Modes determine the port-to-port & port-to-channel relationships within the L2
switch

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 76
 •Mode selection is about selecting the port-to-channel relationship. Selection is made in the DAC
GE3 plug-ins screen under the VLAN Tab.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 77
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 78
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 79
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 80
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 81
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 82
 • Link aggregation aggregates two or more physical links so they appear as a single, higher-
bandwidth link.
• The resultant traffic capacity is the sum of the individual link capacities.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 83
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 84
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 85
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 86
 •The user manual gives good instructions and examples for setting up various DAC GE3
protection options.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 87
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 88
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 89
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 90
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 91
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 92
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 93
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 94
 •VLAN Mode: The two channels can be assigned on the same path, or used to support east and
west paths on a ring, where C1 is assigned to one direction and C2 the other.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 95
 •Transport channel capacity type is selected in the Circuits screen, E1, DS1 or STM1.
•DAC GE operation with an E1 or DS1 backplane requires SW release 3.6 or later.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 96
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 97
 •The maximum frame size should be larger than the largest datagram you wish to transmit
unfragmented.
•To avoid conflict between the self-learning function within DAC GE and an external RSTP switch
during path failure situations, address learning must be disabled in the DAC GE. Failure to do so
means that in the event of an IP path failure, and subsequent re-direction of IP traffic by the
external switch to the alternate path, the DAC GE will inhibit re-direction of current/recent traffic
until its address register matures and deletes unused/un-responsive destination addresses, which
may take up to 5 minutes.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 98
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 99
 •VLAN tagging is typically used at the edge of a network to segregate traffic into VLANs and to
assign a priority for policing. In this way up to four separate LANs (ports 1 to 4) can be carried as
virtual LANs (VLANs) on a single Eclipse radio trunk; Eclipse acts both as an edge switch and as
the radio trunk link to the core network.
•Multiple virtual LANs (VLANs) are transported on the radio trunk and 802.1p priority assures
consistent traffic handling at all intermediary 802.1p devices. This allows network providers to
provide varying service level agreements for each VLAN
•Adding a VLAN tag does not impact the prioritization/queuing of an ingressing frame on the DAC
GE. The impact applies at downstream 802.1p devices (switches/routers) up to the point where
the tag is stripped.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 100
 •DAC GE supports 802.1q tagging with menus supporting selection of VLAN tagging modes, and
802.1p priority settings for tagged-traffic.
•Diagrams assist understanding of the tagging action for each mode.
•Selections are made on a per-port basis.
•Available tagging modes depend on the operational mode selected in the DAC GE configuration
screen.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 101
 Procedure for DPP connecting DAC GE to 2 protected RACs
1. Install the modules and DPP cables to reflect the example shown
above.
2. Protect the RAC 60/6X modules using the Protection screen.
3. Click Enable DPP in the protected RAC Plug-ins screen, and set a
DPP
Group ID. See figure below.
4. In the DAC GE Plug-ins screen enable DPP for both ports to be
connected
and use the same Group ID as the RACs for both.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 102
 •Where an Eclipse ring network is to include external switches, or Eclipse radios are installed
within an existing network to establish a ring, there are two primary options considering RSTP
functions on external switches cannot be super-imposed on Eclipse RWPR enabled radios:
1: The RSTP function is provided by the DAC GEs using RWPR, and the external
switches are configured for transparent operation (not RSTP enabled). The network
section comprising the external switch or switches is viewed simply as a path between
the DAC GEs at each end of the path.
2: The RSTP function is provided by external switches and RWPR is not enabled on the
DAC GEs.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 103
 •The root bridge is the logical center of the network.
•The bridge with the highest priority (lowest bridge ID) is elected as the root bridge.
•The bridge ID comprises a user-settable priority value and the MAC address. If
switches/bridges are configured for the same priority , or left as default, the switch/bridge
with the lowest MAC address becomes the root bridge.
•Path cost is set to represent data bandwidth (speed) available on the path, and is assigned a
value such that the higher the speed, the lower the cost. Highest priority is given to highest speed
= lowest value cost. Costs are added through the network toward the root. If the path from a
switch has a cost of 100, and the path from it to the next switch towards the root is also 100, the
combined cost up to the second switch is 200. A lower cost route is always elected over a route
with a higher cost.
•Where costs to root are such that they cannot assist spanning-tree to set a priority, the
port with the lowest port ID is used to decide port states, such as forwarding or blocking.
Where ports are set for the same port priority, spanning tree selects the port with the
lowest port number as the forwarding port.
•A port priority can be set to represent how well a port is located within a network to pass
traffic back to the root. Port priority is contained within a Port ID, which comprises a port
priority setting, and the port number. Typically Port Priority is left at default
•If path costs are not assigned spanning-tree uses port ID in its selection of port status.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 104
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 105
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 106
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 107
 MHSB – Monitored Hot Standby applies to IRU 600v2 only (IUR600v1 is HSB)

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 108
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 109
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 110
 • Silent transmitter switching 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).
• The messaging to initiate a remote end Tx switch is via the NMS
channel for all RACs except RAC 60/60E/6X/6XE
• The messaging for RAC 60/6oE/6X/6XE is via control bits in the
airlink (RAC to RAC)
• In the event of path fades which effect the link in both directions,
messaging is initiated at both ends of the link but not received by the
other end, so no Tx switch occurs at either end
• Restoration time for RAC 60/60E/6X/6XE is typically less that
200ms
• Restoration time for all other RACs is typically less than 7 sec and
maximum of 20 sec

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 111
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 112
 IRU 600v1, v2, and v3 sparing considerations:

• Chassis dimensions and mounting points for RFUs and ACUs are
identical for IRU 600v1 and IRU 600v2.
• All IRUs are fully over-air compatible with like-for-like configurations. For
example, a 1+0 IRU 600 (V1) may be linked to a 1+0 IRU 600v2. Similarly,
1+1 HSB IRU 600 (V1) may be linked to a 1+1 MHSB IRU 600v2
• The IRU 600v1 and IRU 600v2 RFUs are compatible sparing partners
EXCEPT for HSB configurations where the ACU incorporates a coaxial
relay Tx switch (IRU 600v2 ACU). RFU V1 cannot control the Tx coaxial
switch. This means that:
• V1 and V2 RFUs are interchangeable in non-protected systems
using v1 or v2 ACUs. Applies to single-ended 1+0, and to 1+0
repeater systems.
• In protected HSB or HSB-ready systems with a v1 ACU, the v2
RFU can spare for a v1 RFU.
• In protected HSB or HSB-ready systems with a v2 ACU, the v1
RFU cannot spare for a v2 RFU.
• Because of chassis dimensions, IRU 600v1 and v2 cannot be sparred
into a v3 chassis.
• A mechanical conversion kit is available to support installation (sparing) an IRU 600v3 into
an IRU 600v1 or IRU 600v2 Chassis

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 113
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 114
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 115
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 116
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 117
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 118
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 119
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 120
 •ompared with a traditional single-link commissioning procedure where the link is signed-off as one entity,
for Eclipse INU/INUe a combination node-and-link procedure is required, using the node as the common
reference.
•Eclipse installation and commissioning forms (as Excel worksheets) are available to assist compilation of
an installation datapack and capture of as-built data. Copy is provided on the Eclipse Setup CD.
•General purpose planning, installation and commissioning forms are also available from Aviat Networks as
a part of the Aviat Networks Best Practices Guide. These are provided as user-configurable Excel files.
Typical Commissioning Check Process
1.Physical installation inspection - A physical check prior to antenna alignment and node configuration to
ensure that the physical installation is complete and correct.
2. Antenna alignment confirmation - An antenna alignment procedure is detailed in Antenna Alignment for
Eclipse (Eclipse User manual). Recorded RSLs should be within 2 dB of calculated RSLs.
3. Configuration confirmation - A check, using Portal, to ensure that terminal configurations are complete
and correct and that:
• The link is operating error-free.
• All relevant alarms are extinguished.
• Link performance data is as expected.
• IP addressing and routing is set correctly, which can be confirmed from ProVision,
where installed.
4. Commissioning tests - Tests designed to confirm correct link operation.
5. Capturing as-built data - Recording all relevant installation and performance data for future reference.
6. Final inspection and sign-off - Completion of ‘paperwork’ recording installation hand-over for operational
use, and/or any remedial action needed.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 121
 1. Fit the rack mounting brackets onto the chassis. Brackets can be mounted in either a forward
mount or a flush mount position.
2. Install the chassis. If installing multiple chassis, consider leaving a 3 RU space between to
allow for an expansion or extension kit(s).
3. Locate and secure RFU(s) and ACU in the chassis.
4. Connect the RFU(s) to the ACU using the supplied RF cables.
5. Using the supplied IF cable(s), connect the RFU(s) to the INU/INUe RAC 60 or RAC 6x
card(s). The minimum bend radius of the IF cable is 25mm.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 122
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 123
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 124
 •Standard & High power RFUs are powered over the IF cable from the RAC

•High power RFUs are additionally powered using a separate DC input

•The power connector (D-Sub M/F 2W2) is identical to that used for the INU

•The high power RFU provides a wide-mouth connection for +/- 21 to 60 VDC

•An integral DC/DC converter provides polarity protection, under/over voltage

shutdown, over-current limit, and thermal shutdown

•NEBS compliant EMI filtering is included

•NEBS (Network Equipment-Building Systems) - A U.S.A. government level of compliance

for equipment evaluated for its function in extreme environments/phenomena, i.e., fire,
surge power faults, lightning, earthquakes, airborne contaminants, and temperature
extremes. Eclipse Packet Node and IRU 600 are NEBS Level 3 certified.

•DC power connector can be shorted inadvertently if applied at an angle. Always insert
with correct alignment

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 125
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 126
 •While the Terminal does not have plug-ins, configuration of relevant Terminal features
is supported under the same Node screen-set.
•Send must be clicked after each step to insure correct options for the next step.
•For protected operation, the protection pairing must first be set in the protection
screen to ensure applicable common settings are applied to both plug-ins.
•When setting Networking parameters, be prepared to re-login under the new
parameters including the possibility of having to change the Portal computer’s Ethernet
adapter settings.
•Portal includes configuration Backup and Restore functions.
•File > Backup saves a current configuration (as set by the most recent Send
action) to a user-selectable folder on your PC.
•File > Restore prompts for selection of the saved configuration from your PC,
and its loading back into a Node/Terminal.
•Other screens that may require configuration include Information (Naming), Date &
Time, Aux Data Channels, Alarm I/O, and Security.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 127
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 128
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 129
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 130
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 131
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 132
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 133
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 134
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 135
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 136
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 137
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 138
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 139
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 140
 Go to the parts screen (right click menu) of the NCC card to determine CF card size

Contact Aviat for more information on upgrading CF card size

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 141
 Depending on the changes in the new software load, traffic and/or the Portal
connection can be momentarily interrupted.
New software is released on a regular basis and it is recommended that the
latest version of software is loaded to the radio as it is release in order of adding
new features and fixing any known bugs.
Before loading software it is recommended that the software release notes are
read carefully.
In the loaded software screen - The green check box indicates the plug-ins
supported by the software load.
• A red X indicates that the plug-in is not supported by the software load.
• Software is always loaded for the plug-ins installed and for likely plug-ins
according to the plug-ins installed.
• If a new module is installed that is not shown as supported by the loaded SW
(has a red X), the software must be reloaded.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 142
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 143
 • This procedure is performed at the factory before shipment and adjustment usually will not
be required on new equipment.

• This procedure should be performed when an RFU is replaced to make up for slight
differences in the frequency response of the transmitter over the wideband range of the unit

• When measuring power at the RFU Tx output port or waveguide port be sure not to overload
the power sensor. If the output power is more than the sensor’s maximum power rating a 10,
20, or 30db fixed attenuator should be used. Ensure the attenuator is rated for the correct
frequency.

• Ensure the power meter and sensor are calibrated and the correct power factors have been
set.

• For Ver1 IRU 600, this test will interrupt traffic. The unit under test will have to be locked
online and there is no monitor port. If the waveguide port is used, the insertion loss should
be added to determine power out of the RFU.

• For Ver2 and 3 IRU 600, the monitor port can be used. The monitor port outputs power of
the online unit in a protected configuration, simply add the offset number on the sticker
below the port to determine power at the RFU Tx output port.

• For Ver2 and 3 IRU 600, the offline unit can also be calibrated by locking the online unit
online and measuring and adjusting the offline unit directly at the RFU Tx output port. This
will not effect traffic except when switching transmitters.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 144
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 145
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 146
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 147
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 148
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 149
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 150
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 151
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 152
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 153
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 154
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 155
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 156
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 157
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 158
 Many diagnostics options are also available as right click module menu options

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 159
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 160
 •All TDM/Sonet DAC plug-ins support line and radio facing loopbacks (DS1, DS3, OC3)
•The AUX plug-in supports line and radio facing loopbacks on the Data channels
•DAC/DATA loopbacks are applied per trib. Multiple loopbacks can be set at the same time.
•Digital and IF loopbacks affect all traffic on the link.
•Circuit loopbacks (Node only) are applied per circuit. Only one circuit loopback can be set at a
time.

•All Loopbacks except Circuit loopbacks are accessible in the system controls screen

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 161
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 162
 All History screens have options to view 7 days worth of 15 minute data
bins or one months worth of 24 hour data bins

•PCR (Paperless Chart Recorder) is a software tool for RF path analysis. It is

used to troubleshoot path performance degradation such as dribbling errors,
intermittent loss of synchronization, and unusually high protection switching
activity.
•PCR Viewer is ordered from Aviat Networks, and installed on a PC
•Using the Export PCR tab, data for analysis on PCR is downloaded to your
Portal PC.
•Downloaded PCR files are opened in the PCR application.
•Used Buffer indicates available buffer remaining to store RAC history and alarm
events. On reaching 100% the buffer operates on a first-in first-out basis. A Clear
PCR buffer capability is provided - click on, followed by Send.
•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.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 163
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 164
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 165
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 166
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 167
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 168
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 169
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 170
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 171
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 172
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 173
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 174
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 175
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 176
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 177
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 178
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 179
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 180
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 181
 • The AviatCare Online Customer Support
Portal offers many new features and
enhancements to improve overall online
user experience

• New Features and Enhancements:

• Faster display and refresh speeds when entering the web site
• Formatted for the latest smart phones and tablets including iPhone and iPad
• Searchable knowledge base for quick and easy answers
• Expanded library of technical information in the knowledge base
• Intuitive knowledge base search functionality displays recommended solutions to
support requests based upon information entered into the case
• New feedback system allows customers to rate and provide feedback on all
knowledge base articles
• New feedback capability allows customers to rate their support requests
• Front end interface will now capture customer information
• New system automations allows us to respond faster to the customer reducing the
response time for escalation, case updates and resolution

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 182
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 183
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 184
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 185
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 186
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 187
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 188
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 189
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 190
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 191
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 192
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 193
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 194
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 195
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 196
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 197
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 198
 • When Revertive switching Mode is used, the preferred side is usually set for the lowest latency
side (least number of hops).

• For a framed selection Advanced Settings apply.

• For framed E1 and DS1 operation set the Loss of Frame Threshold. This specifies the number
of consecutive mismatches of the frame alignment sequence (FAS) to detect the loss of frame.
The range is between 1..4. The lower the value the more aggressive.
• For DS1 only, set DS1 FAS Detect Size. This identifies the number of bits in the Frame
Alignment Sequence (FAS) that the framer will
attempt to match at a time to confirm an LOF instance. The selectable values are:
• Default (0) - specifies the maximum value i.e. the whole FAS: 6 bits for 24 frame
multi-frame (extended superframe) and 12 bits for 12 frame multi-frame
(superframe).
• One Bit (1)
• Two Bits (2)
• Three Bits (3)
• Four Bits (4)
• Six Bits (6)
• The recommended setting for a superframe and extended superframe is two Bits.
• For DS1 only, set DSI Multi Frame Type. This specifies the multiframe detection type. Options
are:
• Automatic Frame Detection
• Superframe (SF)/D4
• Extended Superframe (ESF)/D5

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 199
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 200
 •Minimum 16xDS1 ring capacity
•Maximum 16 nodes recommended.
•Wrapping - nodes that are adjacent to the failure, loop or wrap the traffic received on its ‘outer’
primary ring to its ‘inner’ secondary ring.
•The advantages of wrapping:
•Fast and requires only local nodes to make the switching decision.
•Minimizes the packets lost.
•Straightforward to implement.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 201
 •With north-south gateway rings, one of the nodes in the ring operates as the ‘gateway’ for all
traffic entering and leaving the ring.
•For any-to-any rings, traffic can be routed from any one node in the ring to any other node or
nodes.
•For both gateway and any-to-any operation, DS1 or E1 circuits used on the ring are unique –
they cannot be reused and must remain on the same timeslot throughout the ring.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 202
 •The Error-Free timer is default set to 300 seconds. Other options are 10 seconds, 100 seconds,
and 10 minutes. The timer will restart if an error occurs within the error-free timer period.
•The Delay Ring Unwrap option 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.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 203
 •Diagram illustrates normal, no-fault operation for a super-PDH ring. It shows two circuits within
an NxE1 or NxDS1 ring with both routed from Node A clockwise around the primary ring. One E1
Tx stream drops at Node B Rx, the other at Node D Rx. At Node B and Node D the corresponding
Tx stream routes clockwise around the ring to terminate at Node A Rx – to complete the circuits.
•The secondary ring circuits are not being used, and carry pseudo-random data.
• Note RAC cards are labeled East and West, East has to connect to West at the other end of the
link

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 204
 •Diagram illustrates what happens when a break occurs. The ring protection mechanism applies
loopbacks at each end of the failed E1/DS1 circuits, 'wrapping' primary ring traffic onto the
secondary ring in the clockwise direction, and wrapping secondary back onto primary on the other
side of the break. All circuits are restored.
•For a single break, all traffic is deliverable after wrapping.
•Wrapping is not hitless, max 200ms; typically less than 100ms.
•When conditions that caused the wrap are removed, the ring auto-reverts to normal operation
(restorative switching).
•In the event of two or more breaks, traffic will wrap up to each side of the break points to provide
limited service restoration.
•Number of hops in a ring should be not more than 16 to avoid instances of unacceptable delays
for equipment connected to the ring.

AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 205
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 206
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 207
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 208
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 209
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 210
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 211
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 212
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 213
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 214
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 215
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 216
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 217
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 218
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 219
AVIAT NETWORKS |August 2013 | Company Proprietary | Copyright © 2013 | IRU 600 220