Ecli ipse Cus stome er Sof ftware e Rele ease Notes N

Softwar re Version 05.01.44 0 RELEAS SE DATE 17 7th May 2010 0 P/N 260 0-668060-00 01, Rev. 040 DocReg g Ref 5161

WW WW.AVIATN NETWORKS. .COM

RELEASE NOTES

White Paper

Copyright 2010 by Aviat Networks. 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. DISCLAIMER 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. TECHNICAL SUPPORT If you require technical assistance or if you have discovered a product issue, please contact the Technical Help Desk nearest to you as soon as possible. Their contact details are shown below: USA
Aviat Networks 120 Rose Orchard Way San Jose, CA 95134 -1358 Phone: +1 800 227 8332 free within US only Aviat Networks 4 Bell Drive Hamilton International Technology Park Blantyre, Scotland, G72 0FB Aviat Networks 5727 Farinon Drive San Antonio, TX 78249 Phone: +1 866 882 5381 free within US only Aviat Networks Centrale Parc, Btiment 4 Pasteur Avenue Sully Prud'homme E-mail: Americas.Help@aviatnet.com TAC.AM@aviatnet.com 92298 Chtenay-Malabry Cedex France Phone : 33-1-55-52-80-00 TAC.APAC@aviatnet.com E-mail: Asia.Help@aviatnet.com United Kingdom Phone : +44 1698 714 073

Europe, Middle East & Africa

Asia/Pacific
Aviat Networks Bldg 10 Unit B, Philexcel Industrial Park Clark Special Economic Zone Clark Field Pampanga Philippines Phone: +63 45 599 5192

E-mail: EMEA.Help@aviatnet.com TAC.EMEA@aviatnet.com

2 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

MAY 25, 2010

RELEASE NOTES

White Paper

Table of Contents Scope and Purpose New Features Closed Field Issues Known Issues Closed Significant Issues Software Upgrade Considerations Eclipse Hardware Supported Operating Systems Supported Computer Hardware Supported Regional Settings Supported Network Time Protocol (SNTP) Servers Supported Important Notes

4 4 8 6 9 10 13 15 15 15 17 17

3 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

MAY 25, 2010

RELEASE NOTES

White Paper

Scope and Purpose

This document provides software release information on supported functionality, compatibility, and known customer affecting issues, relating to the released software versions. The intended users of this document are: Aviat Networks Customers Aviat Networks Value Added Resellers Aviat Networks Value Added Service Providers Aviat Networks Product Support staff Aviat Networks Field Service staff

New Features
This software has been made available for general release to all customers. In addition to previously supported hardware and functionality this Eclipse release provides support and enhancements for: RAC 60 ANSI Static Modulation profiles for North America including reduced latency performance and system gain enhancements for selected profiles RAC 30v3 ANSI 7MHz Profile release RAC 60 ETSI ACM Profile enhancements including reduced latency performance RAC 60 ETSI 51xE1 28MHz Profile release RAC 30v3 ANSI 21xDS1 7MHz Profile release RAC 60 Enhancements to the data packet plane configuration & fragmentation flexibility

The following bandwidth/modulation capacities are supported on the RAC 60/6X: RAC 60/6X Update to all Modem Profiles used with ODU 300hp & IRU 600

Note: 5.1 is not over-the-air compatible with the previous 5.0 version for the RAC 60/6X profiles, please refer to the Software Upgrade Considerations section.
4 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

ETSI 75xE1 128QAM 28MHz ETSI 51xE1 32QAM 28MHz 7MHz ETSI Adaptive Modulation (8 44 Mbps) 4/5/8/10/14/15/20/21xE1 (each also operable as a Static profile) 14MHz ETSI Adaptive Modulation (17 88 Mbps) 8/10/16/20/28/31/39/42xE1 (each also operable as a Static profile) 28MHz ETSI Adaptive Modulation (36 181 Mbps) 17/21/35/43/58/64/82/88xE1 (each also operable as a Static profile) 56MHz ETSI Adaptive Modulation (74 366 Mbps) 36/44/71/88/100xE1 (each also operable as a Static profile) ANSI 8xDS1 32QAM 3.75MHz ANSI 16xDS1 128QAM 5MHz
MAY 25, 2010

RELEASE NOTES

White Paper

ANSI 29xDS1 64QAM 10MHz ANSI 32xDS1 128QAM 10MHz ANSI 36xDS1 256QAM 10MHz ANSI 87xDS1 64QAM 30MHz ANSI 115xDS1 256QAM 30MHz ANSI 87xDS1 32QAM 40MHz ANSI 100xDS1 64QAM 40MHz ANSI 100xDS1 128QAM 30MHz ANSI 115xDS1 64QAM 40MHz ANSI 1xOC3 128QAM 30MHz ANSI 1xOC3 64QAM 40MHz Support for fragmented DPP RAC 30v3 ANSI 21xDS1 64QAM 7MHz Portal Write Access Blocking from Provision ODU 300 SP+ support for 32QAM Release EKS range Part Numbers

Note: The following list is functionality not provided in this release that will be enabled in a future release: RAC 6X XPIC / CCDP support - software and profile release ACM for ANSI Profiles on RAC 60/6X ACM not supported in Super PDH Rings Frequency Diversity on RAC60 and RAC6X is not yet supported

Product Eclipse Embedded Software Eclipse Portal Software

Part Number 275-250219-050144 280-200010-050144

Version 5.1 5.1

Build 44 44

Aviat Reference # 1341 and 5161 5.1.186

This release is supported by ProVision Element Manager System software version 6.4 with the following exceptions: New alarms added to Eclipse 5.x firmware will not be supported (until ProVision 6.5) New capacities added to Eclipse 5.x will not be correctly reported in ProVision Configuration, Inventory and Capacity reporting features (until ProVision 6.5) IRU600 will not display a correct icon until ProVision 6.5

5 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

MAY 25, 2010

RELEASE NOTES

White Paper

Known Issues
The following table lists known issues that have not been fixed in this release. Jira Ref # and GCAS if relevant ES-14632 Issue Description

RAC 60/6X: The BBER Performance counter does not freeze when the Stop button is clicked. Only the BBER Performance counter is affected. All other G.826 counters operate correctly i.e. they freeze when the Stop button is clicked. Circuits: Existing Super PDH ring circuits can be corrupted when new pointto-point circuits are added. This issue appears to be more likely experienced when using release 5.0 or 5.1 given the greater flexibility on circuit configuration and added complexity in circuit re-assignments. An enhancement is expected in a future SW release to solve this issue. RAC 60/6X: High-Priority backplane Ethernet traffic can be corrupted (frame drops) during a step-up from QPSK to 16QAM on 7MHz adaptive modulation profiles. Applies only to: a) Backplane-connected Ethernet traffic where the traffic assigned to the backplane exceeds the capacity that can be supported at QPSK. DPP Ethernet, PDH, and AUX traffic is not affected. b) 7 GHz adaptive modulation profiles. The interim solution is to use the DPP for Ethernet traffic - avoid use of backplane-connected Ethernet for this 7MHz profile when using adaptive modulation. IDU GE 20x: Some types of SFP do not work with LSP when Speed Duplex is set to Fixed 1Gbps. A far-end port shutdown may not occur with some SFP modules when set for Fixed Speed-Duplex, with LSP and RFD. The solution is to set Auto for Speed-Duplex. RAC 60/6X: Extended Rx outages may occur on IRU600 1+1 protected links (DS1 rates) when an off-line RAC 60 is re-inserted. While instances are infrequent, outages up to 59 seconds have been recorded. Ensure new RAC 60s are fitted during a maintenance window. RAC 60/6X: Extended outage times may occur on a DPP 1+1 HS/SD ACM link when the online RAC is removed. Traffic may be disrupted for about 2 seconds if the online RAC 60/6X is withdrawn on a DPP 1+1 link (hot-standby / space diversity) when configured for adaptive modulation. Extended times were noted on: - DPP Ethernet in the TX direction. - TDM Ethernet in both the TX & RX directions. Occurrence is rare/intermittent however to avoid this outage it is recommended that the online RAC is reconfigured offline before removal. RAC 60/6X: Traffic hit upon re-insertion of the primary RAC after a power cycle with the primary RAC removed. Impacts Ethernet traffic minimally; typically one or two dropped frames (applies to DPP and backplane Ethernet traffic). PDH traffic can be disrupted for up to one second.

ES-14626/ GCAS 36333

ES-14623

ES-14617

ES-14575

ES-14559 / 14545

ES-14430

6 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

MAY 25, 2010

RELEASE NOTES

White Paper

ES-14234

RAC 60/6X: When configured for 1+1 Adaptive Modulation, the Primary & Secondary TX Modulation & Capacity values can be mismatched. Intermittently, Primary & Secondary TX modulation/capacity can be at different values as displayed in the Portal Performance screen. The On-Line TX displays the true TX modulation/capacity of the path. This is a display (Portal) issue. It can be corrected by forcing TX Off-Line to On-Line. NCCv2: NMS Ethernet Auto Neg fails with certain types of third party equipment (GCAS 37100). NMS port on the NCCv2 card is always set to Auto negotiate for speed and Duplex. IDU GE 20x: Limited pause frame operation on frame sizes larger than 500 bytes (GCAS 37187). With 'Enable Flow Control' selected, pause frame control is not effective on frame sizes greater than 500 bytes, resulting in buffer overload and frame loss on affected ports. An improvement is scheduled for a future SW release. RWPR: RWPR protection may fail when a link is slowly faded and unfaded (GCAS 36587). If a link is slowly faded then un-faded, prescribed RSTP forwarding and blocking action can be unreliable where 'Rapid Failure Detection and Prevention' is selected as the Transport Channel Mode. This can be prevented by selecting 'Rapid Failure Detection' as the Transport Channel Mode. Only use 'Rapid Failure Detection and Protection' for L1LA and Adaptive Modulation operation. DAC 16xV2 in Ethernet NTU Mode: When setting up protection on a DAC 16xV2 configured for Ethernet NTU mode on tribs 1-8 it may raise a remoteend LOS alarm on all tribs with a loss of all trib traffic. This problem occurs intermittently only when setting up the DAC 16xV2 initially for protection. To reset/clear the LOS alarms and restore traffic, remove and re-insert the On-Line DAC 16xV2. RAC 60/6X: A traffic hit may occur on 1+1 protected links when an Off-Line RAC is re-inserted. The hit (errors/sync loss burst) affects all traffic (DPP, backplane). Occurrence is intermittent. RAC 60/6X: Traffic (DS1&Ethernet) hit observed on a RAC30v3 link using slot3 after a RAC60 is inserted in Slot1. A link created with a RAC30v3 located on Slot3 may take a traffic hit (packets dropped) after inserting a RAC60 card in slot 1. Suggested workaround: in case both RAC30 and RAC60 cards are present in the same radio, use slots other than slot 3 for the RAC30. Circuits: Circuits made with SW release 5.0 or later disappear if SW is reverted to 4.6 or earlier. Circuits configured in 4.6 or earlier are carried forward into 5.0 or later, and will be retained if SW is reverted to 4.6 or earlier, but any circuit changes made in 5.0 or later will not be retained if SW is reverted to 4.6 or earlier. No Power Supply Input Failure alarm on the IRU 600 high power RFU. Removing the power supply brings up a TX Power Failure alarm, which may result in an incorrect diagnosis of the real problem. If a TX Power Failure alarm is present, first check the RFU power supply voltage. Max DS1 backplane capacity can be reduced based on AUX circuit connections. When the backplane bus is set to the DS1 rate (1.544Mbps), the max NxDS1 backplane capacity of 128xDS1 can be reduced to 123xDS1, depending on the number of AUX circuits configured and the order in which
MAY 25, 2010

ES-14212 / GCAS 37100

ES-14173 / GCS 37187

ES-14160/ GCAS 36587

ES-14001

ES-13994

ES-13808

ES-13276

ES-13267

ES-13156

7 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

RELEASE NOTES

White Paper

they are configured. A fix has been confirmed for SW Release 05.03. Portal: Ring circuit configurations are deleted during an upgrade from nonprotected to protected operation (GCAS 24815) Circuit configurations can be lost when Super PDH ring network paths are upgraded from non-protected to protected. This requires reconfiguration of all circuits to restore traffic. A fix is expected in a future SW release. RAC: During a SW upgrade load or if a refresh is requested after a configuration change, there may be a delay of up to several minutes before Portal acknowledges completion of the processes. During this time Portal will indicate a busy/pending status (spin-wheel). RAC 30A: Extended demodulator not locked events may affect AM operation On AM links, resumption of normal modulator operation after a long demodulator outage can be delayed. ATPC : On 56MHz channels with 256QAM modulation ATPC may freeze, GCAS 12839. Normal ATPC operation will increase Tx power to achieve a target SNR. On some early produced ODUs (prior to mid 2009) the target SNR may not be achieved when operating 56MHz channel size at 256 QAM, resulting in the Tx power being held at the maximum. Some improvements have been completed in this area, but not all problems have been resolved. Super-PDH ring switching exceeds 100ms For RAC 30v3, RAC 3X and RAC 40 a ring protection switch may result in a traffic outage that exceeds the 100ms specification about 10% of the time. Earlier RAC 30s may have a higher exceeded percentage. RAC 60/6X is not affected. A fix for affected RACs is expected in a future SW release. RAC 30v1 and RAC 30v2: Frequency diversity TX switch exceeds 200ms A manual Tx switch or removal of the online Tx RAC (the RAC that is driving the Tx diversity bus) may result in a Tx switch time in excess of the 200ms specification. Times can extend up to 1.8 seconds. To achieve FD Tx switch times that are within specification, use RAC 30v3. RAC 60/6X: 1+1 Adaptive Modulation Links with Ethernet traffic on the backplane only (not DPP) may experience degraded Ethernet throughputs. When the DPP is not enabled on 1+1 ACM links operating Ethernet over the backplane it is possible for Ethernet traffic in one direction to be degraded due to the Tx and Rx functions on separate RACs (Primary and Secondary) being in different ACM modulation states with different capacities. This situation may occur from power-on, or from a fade/unfade, where the Offline Tx is not stepped up in modulation to match the Online Tx. When DPP is enabled this issue is not present. Interim solutions are: a) Enable the DPP for Ethernet traffic. b) Use the DPP for Ethernet and the backplane for Ethernet and/or PDH.

ES-12063 / GCAS 24815

ES-12052

ES-11578

ES-10225 / GCAS 12837

ES-7843 / ES7859/ ES-7845/ ES-7844/ ES9016 / GCAS 5156

ES-7869

ES-14647

Closed Field Issues

The following table lists field issues that have been resolved since the 05.00.96 release.

8 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

MAY 25, 2010

RELEASE NOTES

White Paper

GCAS # 33974 34217

Issue Description A circuit configuration error when upgrading 1+1 XPIC Rings from 04.06.50 to 05.00.96 RAC 40: Corruption of a register results in momentary Mod alarm

Closed Significant Issues

The following table lists significant issues that were discovered during development/testing since the version 05.00.96 release. These issues have been fixed by this release. Ref # ES-11907 Issue Description RAC 30A: TX spectrum can overshoot the ETSI mask when changing from 64QAM to 16QAM This issue is now resolved. RAC 60/6X: DPP cannot utilize unused TDM slots that are between used TDM slots DPP capacity had to be contiguous. It could not include unused backplane capacity between configured blocks of backplane capacity This issue is now resolved. RAC 60/6X : The Modulation change limited to 3 profile jumps. More than 3 ACM profile jump (Up or Down) used to result in a traffic hit. This issue is now resolved. IRU 600 / RAC 60: A Tx switch at one end of a RAC 60/6X link may cause a sympathetic Silent Tx Fail and Tx switch at the remote end of the link, causing a short traffic hit in the opposite direction at the same time as the expected. Now resolved. RAC 60/6X: Errors can be introduced to customer traffic when error- free traffic is actually available from the off-line RAC. If the on-line RAC (the RAC controlling Rx diversity bus operation) has errored traffic, and its off-line partner RAC has error-free traffic, the online RAC is designed to errorlessly select error-free traffic from its partner. This was not operating correctly for the following RAC 60/6X ETSI rates: 64 QAM Max-gain for 7, 14, 28, 56 MHz and 64 QAM Max-throughput for 7 MHz 16 QAM Max-gain for 7 MHz, and Max-throughput for 7 MHz QPSK Max-gain for 7, 14 MHz, and Max-throughput for 7 MHz This issue is now resolved. RAC 30A: The adaptive modulation option covering 5/10/15xE1 capacities could not be used with SW 05.00. This issue is now resolved. RAC 60/6X: 56MHz / 256QAM HG / 344Mb shows intermittent DNL after a quick fade & un-fade & also adversely affects the RX diversity plane An intermittent demodulator not locked alarm for the above capacity and modulation sometimes occurred after a quick fade & un-fade, and also adversely affected the Rx diversity plane for 1+1 protected operation. This issue is now resolved. RAC 60/6X: 1+1 AM - When the off-line Rx RAC has its Demodulator Not Locked, AM stepping can become unpredictable. This issue is now resolved.
MAY 25, 2010

ES-12163

ES-12430

ES-13257

ES-13303

ES-13369

ES-13370

ES-13441

9 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

RELEASE NOTES

White Paper

ES-13537 ES-13650 ES-13678

Closed Field Issue see relevant section above Circuits: Circuit conflicts after upgrading protected ring network to 05.00 from previous releases. This issue is now resolved. Closed Field Issue see relevant section above

The following table lists significant issues that were discovered during development/testing of release 05.01.30 and have been resolved in 05.01.44 Ref # Issue Description DAC 16xV2: LOS on both cards in a protected setup causes indefinite, continuous switching between the cards with the appearance of dribbling errors. Occurs only if the protection Y cable to the customer equipment is unplugged at the customer end or the customer equipment interface has failed. An enhancement to add a blocking condition has been added to avoid this issue. Note that all tribs that do not have live traffic connected should be uncommissioned in portal. RAC 60/6X: DPP Traffic does not recover when the terminal is power cycled with the Primary RAC removed. Using a RAC 60/6X in a DPP protected configuration, DPP traffic is lost if the radio is power cycled with the Primary RAC 60 unplugged. To recover DPP traffic the radio must be power cycled with the Primary RAC inserted. Backplane traffic is not affected. This issue is now resolved. RAC 60/6X 1+1 HS: Receive path protection may be inhibited when a new modulation profile is configured. When a new link capacity (bandwidth/modulation) is set using Portal, the receive path may be held to the Primary or Secondary RX path - it will not automatically select between the RACs for best path performance. The interim solution is to use Portal System Controls to force a manual Rx Online switch to the partner RAC. The same action can be used to force a change back to the original online RAC if desired. This action clears this inhibited state. Note that if DPP is protected, a manual switch will also force a change of the Tx Online RAC. This issue is now resolved.

ES-14183

ES-14179

ES-13969

10 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

MAY 25, 2010

RELEASE NOTES

White Paper

Software Upgrade Considerations

Upgrading Eclipse Software to 05.01.44 or Later with RAC 60 or RAC 6X
Eclipse SW 05.01.44 introduces enhanced profiles (capacity/modulation) for RAC 60/6X to enable lower link latencies for Ethernet and TDM traffic, and improved AM operation. These new profiles are not compatible with the RAC 60/6X profiles provided with SW release SW 05.00.96, which was the first release of software for RAC 60/6X. Over-the-air modem profiles for RAC 60/6X are not compatible between 05.00.96 and 05.01.44 (or later). If RAC 60/6X is in use with SW 05.00.96, the following notes and guidelines are applicable when upgrading to SW 05.01.44, or later. Refer to: Upgrading from SW 05.00.96 to SW 05.01.44 Additionally, for ANSI markets only, there were two intermediate (limited availability) 05.01 SW releases. These are 05.01.01 and 05.01.30. All profiles from these releases, with the exception of two under 05.01.01, are upgradeable to 05.01.44 (or later). Refer to: Upgrading from SW 05.01.01 to 05.01.44 or Later (ANSI) Upgrading from SW 05.01.30 to 05.01.44 or Later (ANSI)

These guidelines apply to RAC 60/6X use with both ODU 300 and IRU 600. During the upgrade process traffic will be lost. Do not use Provision to load and schedule activation of SW 05.01.44 on radios that have RAC 60/6X cards installed. The upgrade process from SW 05.00.96 to 05.01.44 or later, must be manually supervised where RAC 60/6X cards are installed. If no RAC 60/6X cards are installed, this does not apply; ProVision can be used to manage the upgrade process. Where RAC 60/6X cards are not installed, these guidelines do not apply, except that in all instances where SW is to be upgraded from one end of a link, always upgrade the far end first. For SW upgrade and activation procedures, refer to the Eclipse User Manual, Portal Chapter 12.

Upgrading from SW 05.00.96 to 05.01.44 or Later

With the exception of one ANSI modulation profile, all RAC 60/6X profiles supported under 05.00.96 are supported under 05.01.44 or later. Supported profiles can be upgraded to 05.01.44 or later, but during the upgrade process traffic will be lost and an error message may indicate Service is unavailable on this module. Try pressing Refresh after two minutes, in which case wait for not less than two minutes and click Refresh on the Portal toolbar. Wait and click again if the message persists. The unsupported ANSI profile, 10 MHz, 64QAM, 29xDS1 / 45 Mbps max system gain (high coding), cannot be upgraded to 05.01.44 or later. A configuration change to another supported profile is required before a SW upgrade can be attempted.

11 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

MAY 25, 2010

RELEASE NOTES

White Paper

Upgrade Process for Supported Profiles: 1. To upgrade SW from one end of a link1, upgrade the far end first2. Note that as soon as the SW has been loaded and activated on the far end radio, communication with the radio will be lost. 2. Upgrade and activate SW on the local end. If the following error message appears Service is unavailable on this module. Try pressing Refresh after two minutes, wait for not less than two minutes and click Refresh on the Portal toolbar. Wait and click again if the message persists. Upgrade Process for Unsupported Profile: The exception profile of 10 MHz, 64QAM, 29xDS1 / 45 Mbps max system gain (high coding) must be replaced by a profile supported under 05.01.44 (or later). The recommended replacement is 10 MHz, 64QAM, 29xDS1 / 45 Mbps max throughput (normal coding). But to update to this profile from one end of the link1 requires an intermediate step whereby the incompatible profile is first replaced by a compatible profile before the SW upgrade, followed by a change to the new recommended profile. 1. To change to the recommended replacement profile from one end of the link, first change both ends to an intermediate profile that is supported under 05.01.44 (or later), such as 10 MHz, 256QAM, 36xDS1 / 56 Mbps max system gain (high coding)3. Change the far end first. 2. Once normal link operation is returned under the replacement profile, proceed with the SW upgrade. Upgrade the far end first. Note that as soon as the SW has been loaded and activated on the far end radio, communication with the radio will be lost. 3. Upgrade and activate SW on the local end. If the following error message appears Service is unavailable on this module. Try pressing Refresh after two minutes, wait for not less than two minutes and click Refresh on the Portal toolbar. Wait and click again if the message persists. 4. Change to the recommended profile of 10 MHz, 64QAM, 29xDS1 / 45 Mbps max throughput (normal coding). Change the far end first.

Upgrading from SW 05.01.01 to 05.01.44 or Later (ANSI)

This only applies to ANSI profiles. Two profiles supported under 05.01.01 are not supported under 05.01.44 (or later). These are: 10 MHz, 64QAM, 29xDS1 / 45 Mbps max system gain (high coding). The recommended replacement profile is 10 MHz, 64QAM, 29xDS1 / 45 Mbps max throughput (normal coding). The recommended intermediate profile to enable a SW upgrade from one end of the link is 10 MHz, 256QAM, 36xDS1 / 56 Mbps max system gain (high coding)3. Follow the Update Process for Unsupported Profile, using 10 MHz, 256QAM, 36xDS1 / 56 Mbps max system gain (high coding) as the intermediate profile, followed by 10 MHz, 64QAM, 29xDS1 / 45 Mbps max throughput (normal coding) as the change profile.

1 SW can be upgraded at each end of the link in any sequence, but until both ends have been updated, communication between the links will not be possible. 2 If the near end is updated first, communication with the far end radio will not be possible. 3 First check that this profile will provide adequate fade margin for the link. If there is potential for the link to be lost because of inadequate margin, upgrade SW locally at each end of the link.

12 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

MAY 25, 2010

RELEASE NOTES

White Paper

30 MHz, 128QAM, 100xDS1 / 155 Mbps max throughput (normal coding). The recommended replacement profile is 30 MHz, 128QAM, 100xDS1 / 155 Mbps max system gain (high coding). Since this recommended replacement profile is supported under 05.01.44 (or later), there is no requirement to first use an intermediate profile. Simply change both ends of the link to the recommended profile (far end first), then follow Upgrade Process for Supported Profiles.

Upgrading from SW 05.01.30 to 05.01.44 or Later (ANSI)

There are no unsupported profiles in 05.01.30. SW can be upgraded to 05.01.44 (or later) using the Upgrade Process for Supported Profiles. The above content is available in a separate bulletin on the intranet entitled Upgrading Eclipse Software to 05.01.44 or Later with RAC 60 or RAC 6X.

Eclipse Hardware Supported

The following table details the hardware that is supported by this software and corresponding part numbers. Hardware with a strikethrough has no support in this issue. It is still possible to software load to a terminal with a non supported INU or ODU attached, but the software in the module will not be updated.

Eclipse Software Product ODU 100 ODU 100 v1.1 (v2) IDU 100 8/16xE1 IDU 100 20xE1 ODU 300 (ODU 300 EP) ODU 500 (ODU 300 HP) ODU 50 (ODU 300 SP Starwave) ODU 50 (ODU 300 SP MTI) ODU SPE IRU 600 IDU 300 8/20xE1 IDU 300 20xE1 v2 IDU 300 ES + 8xE1 IDU 300 SP IDU 300 155o IDU 300 GE 20x IDU 300 SPE INU and INUe, (NCCv1 & NCCV2)
13 AVIAT NETWORKS

Part Number EBS-xx-xxxx-xxx ECS-xx-xxxx-xxx EXB-081-001 EXB-161-001 EDH-xx-xxxx-xxx EAH-xx-xxxx-xxx EFS / EQS-xx-xxxx-xxx EFS / EQS-xx-xxxx-xxx ERC-0xx-001 EXB-201-001 EXG-231-001 EXG-211-001 EXG-xxx-001 EXG-999-001 EXG-261-001 EXG-300-001 EXX-000-xxx

Version Removed Removed Removed Removed 05.01.44 05.01.44 05.01.44 05.01.44 05.01.44 00.01.00 04.03.35 04.06.44 04.06.54 04.06.44 04.06.44 05.01.44 05.01.44 05.01.44

Notes Not in 05.01.44 bundle Not in 05.01.44 bundle Not in 05.01.44 bundle Not in 05.01.44 bundle

Including all plug in modules

MAY 25, 2010

AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

RELEASE NOTES

White Paper

14 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

MAY 25, 2010

RELEASE NOTES

White Paper

Operating Systems Supported

The following table details the supported Operating Systems. Operating System Windows XP Pro (SP1, SP2) Windows 2000 Pro (SP3) Windows Vista Notes Refer to Eclipse User Manual for XP support information New Portal Installer with Microsoft Vista Support

Computer Hardware Supported

The following table details the minimum hardware specifications required to operate Portal. Attributes Processor RAM HD space (install and operate) Monitor display resolution Minimum Specifications Pentium 4 or later 1 MB 200 MB 1024 x 768 XGA

Note: ATI video cards installed with a Catalyst driver set earlier than 4.9 will cause the Portal performance page to stop working if the screen-saver activates. The workaround is to install the latest video drivers from the video card manufacturer.

Regional Settings Supported

Portal supports the following locales and there are no known limitations: Albanian, Belarusian, Bulgarian, Catalan, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Icelandic, Italian, Japanese, Korean, Latvian, Lithuanian, Macedonian, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Serbo-Croatian, Slovak, Slovenian, Spanish, Ukrainian. The following table details known regional settings limitations. Locales Arabic Chinese Hindi Swedish Known Limitations The calendar does not display the day of the week correctly The date format is not consistent in event browser, the calendar does not display the day of the week correctly, and the alarms page is larger than 800 x 600 resolution The alarms page is larger than 800 x 600 resolution Commas are displayed instead of decimal points when entering the TR/RX spacing and TX/RX frequency. Portal will accept commas when the user enters TX/RX
MAY 25, 2010

15 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

RELEASE NOTES

White Paper

frequency, however it will not accept commas for the TX/RX spacing. The workaround is to use decimal points. Thai Turkish Alarms page is larger than 800 x 600 resolution Some event log entries in the event browser/link history pages may not be displayed

16 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

MAY 25, 2010

RELEASE NOTES

White Paper

Network Time Protocol (SNTP) Servers Supported

Eclipse software has been successfully tested with the following SNTP time servers. NetTime

Important Notes
1. Traffic may be affected when upgrading software between two specific versions of software. Modules that have updated FPGA software will suffer a momentary loss of traffic. The use of Provision feature Scheduled Activation to preload software, and schedule upgrades at low traffic times of the day will help minimize disruption. Contact an Aviat Networks Technical Help Desk for details, contact details are on page 2 of these release notes. 2. When upgrading software ensure the remote end of a link is upgraded before the local end. 3. Care should be taken not to run OSPF and Static routing within the same internal OSPF routing domain. 4. If Portal loses communication with an IDU 300 SP radio when changing the IP address, restart Portal to restore communication. 5. Disable any PC firewalls before performing a software download. 6. Eclipse Portal Software version 5.0 includes an upgrade to Java version 6.0. This later version of Java provides improved memory management and operational performance. It provides a fix for occasional low memory issues that have been reported on heavily loaded systems. It is recommended that users install Eclipse Portal 5.0 or later from the Eclipse SW Setup CD or from the Aviat Networks Customer Online Support site at www.support.aviatnetworks.com. The note below, seen on Portal screens, relates to this issue.

7. Note that this software includes open source items and as such users have a right to access source code. Contact tony.wood@aviatnet.com for details.

Aviat Networks encourages its customers to report problems so we can resolve them as quickly as possible. If you encounter a technical issue, please contact us using the information on page 2 of these Release Notes.

17 AVIAT NETWORKS AVIAT NETWORKS, INC, ALL RIGHTS RESERVED

MAY 25, 2010