sw release notes - comark telecom rel 1 03 00... · an encrypted enabled fpga device ... 9....

PRODUCT RELEASE NOTES

Horizon Quantum IDU REL 1.03.00

Issue: 1.0

This document contains confidential information which is proprietary to DragonWave. No part of its contents may be used, copied, disclosed, or conveyed to

any party in any manner whatsoever without prior written permission from DragonWave.

Note that the original signed off document is held in Documentation Control. When printed this document is uncontrolled. ©

DragonWave Inc.

Horizon Quantum IDU Release Notes

for

Software Version 1.03.00

Last revised November 18, 2013

Status: Released



Issue: 1.0




DragonWave Inc.

HISTORY

Status Date Reason

1.0 November 18, 2013 Initial Release



Issue: 1.0




DragonWave Inc.

Rel5 Radio FW

(Quantum

Radio)

6.00.03 (Quantum Radio, PIC24 series)

VDD-67-001190-01-06-00.doc

Supported

Frequency Files

frequencyFileHzQtm_2.12.00.txt (67-001301-01-06-00, VDD-67-001301-01-06-00.doc) & higher

NOTES:

Frequency file versions 1.00.xx are not supported with Quantum Rls 1.2.5 software.

Frequency file versions 1.00.00 to 1.00.14 are not supported with Quantum Rls 1.1.5.x software

& higher due to changes in the ATPC algorithm.

Quantum Omni Version Frequency File Compatibility 1.00.00 1.00.00 to 1.00.03

1.00.01 1.00.04 to 1.00.14

1.01.00 1.00.04 to 1.00.141

1.01.05.00 1.00.15 & higher

1.01.05.01 1.00.15 & higher

1.02.00 1.00.15 & higher

1.02.05 2.01.00 & higher

1.02.06 2.06.00 & higher

1.03.00 2.12.00 & higher

Note 1: Frequency file versions up to 1.00.19 can also be used with Omni version 1.01.00.

Note 2: Frequency file versions 2.12.00 & higher have modem settings optimized for 512 QAM, 1024

QAM & 2048 QAM operation supported in Quantum Release 1.03.00.



Issue: 1.0




DragonWave Inc.

SNMP MIB definition

file

a. HORIZON-QUANTUM-MIB_1.3.0.mib (VDD-67-001198-01-06-00.doc)

b. Horizon-MIB_1.02.00.mib

c. DwAgEcfm_mib_1.01.00.mib

d. DwEOAM_mib_1.01.00.mib

e. IEEE P802.1ag Draft 8 std ECFM mib, revision ” 200701240000Z”

f. DwLLDP_MIB_1.01.00.mib (VDD-67-001239-01-02-00.doc)

g. IEEE 802.1AB LLDP mib, revision ” 200505060000Z”

DESCRIPTION OF NEW FEATURES:

REL 1.03.00

1. 512 QAM mode support (28 – 56MHz channel bandwidths)

2. 1024 QAM and 2048 QAM HAAM modes ( 28/30MHz channel bandwidth only)

3. 256AES Data Path Encryption

4. 1+1 IDU Hot Standby (HSB)

5. Link Layer Discovery Protocol (LLDP)

6. Cisco ECFM support (Bandwidth Vendor Specific Messaging)

7. Terminal Access Controller Access-Control System Plus (TACACS+)

REL 1.02.06

8. Multi-Carrier XPIC bug fixes

REL 1.02.05

9. Multi-Carrier XPIC (Cross-polarization Interference Cancellation)

10. HAAM mode range settings

11. New system modes to allow for future improvements in system gain

12. Support for download of frequency file into the active bank.

13. Support for Quantum All-outdoor modem.



Issue: 1.0




DragonWave Inc.

REL 1.02.00

14. Packet Cut-Through

15. Bandwidth Doubling

16. Synchronous Ethernet (SyncE)

17. Ability to disable MAC-learning

18. Merlin compatible diagnostic command

19. Radius Authorization feature enhancement

20. DSCP management VLAN priority tagging

REL 1.01.05.01

1. ECFM improvements for ring topology and operation with RSTP/MSTP.

REL 1.01.05

1. Rapid Spanning Tree Protocol (RSTP).

Note: configuration is only available in CLI in this release.

2. Multiple Spanning Tree Protocol (MSTP).

Note: configuration is only available in CLI in this release.

3. 2-step save/delete mib sequence to save or erase configuration regardless of Layer 2 Feature license status.

save/delete mib” saves wireless link configuration, IP address, subnet mask, default gateway. NOTE:

“delete mib” does not delete/change the IP address, subnet mask, default gateway settings

save/delete l2swmib” saves/deletes switch configuration (VLAN, port characteristics, IPG, default port

priority)

4. Support for mixed radio types (R4 & R5) at opposite ends of a link.

Note: for a dual radio link, both radios at one end must be the same type.

5. Support for mixed IDU types (Quantum IDU & Duo IDU) at opposite ends of a link via Peer Link Compatibility

(PLCM)

Note: Requires Duo release 1.3

6. Duo Port Configuration option via PLCM feature. Configures ports to behave like a Duo link but in a Quantum-to-



Issue: 1.0




DragonWave Inc.

Quantum link.

7. Critical, Major, Minor Alarms summary

8. Control Queue (QC) visibility & limited access

REL 1.01.00

1. Cross-Polarization Interference Cancellation (XPIC)

REL 1.00.01

1. Support added for new radio bands.

REL 1.00.00

1. Dual and single modem operation

2. Bandwidth Acceleration

3. Hitless Automatic Adaptive Modulation (HAAM)

4. AirPair Radio and Quantum Radio support

5. Licensed Feature Groups

6. Eight Ethernet switch ports, including 2 SFP connectors

7. QPSK to 256 QAM

8. 14 MHz to 56MHz channel bandwidths

9. 256 QAM operation across 14-56 MHz

10. ½ Rack width mechanical housing

Supported HW Assembly

IDU Assemblies:

60-000471-07 / -08 / -09 must be used with omni Release 1.2.5 or higher

0-000471-10 / -11 / -12 must be used with omni Release 1.3.0 or higher



Issue: 1.0




DragonWave Inc.

RF Assembly Assembly # Description

RH-HP-L6-B1 Radio Assembly, High Power Lower 6 GHz Band 1 TxH

RL-HP-L6-B1 Radio Assembly, High Power Lower 6 GHz Band 1 TxL

RH-HP-L6-B2 Radio Assembly, High Power Lower 6 GHz Band 2 TxH

RL-HP-L6-B2 Radio Assembly, High Power Lower 6 GHz Band 2 TxL

RH-HP-U6-B3 Radio Assembly, High Power Upper 6 GHz Band 3 TxH

RL-HP-U6-B3 Radio Assembly, High Power Upper 6 GHz Band 3 TxL

RH-HP-U6-B4 Radio Assembly, High Power Upper 6 GHz Band 4 TxH

RL-HP-U6-B4 Radio Assembly, High Power Upper 6 GHz Band 4 TxL

RH-EP-H7-B8 Radio Assembly, High Power High 7 GHz Band 8 TxH

RL-EP-H7-B8 Radio Assembly, High Power High 7 GHz Band 8 TxL

RH-EP-L7-B1 Radio Assembly, Extended Power Lower 7 GHz Band 1 TxH

RL-EP-L7-B1 Radio Assembly, Extended Power Lower 7 GHz Band 1 TxL



RH-EP-U8-B1 Radio Assembly, Extended Power Upper 8 GHz Band 1 TxH

RL-EP-U8-B1 Radio Assembly, Extended Power Upper 8 GHz Band 1 TxL



RH-HP-11-B1 Radio Assembly, High Power 11 GHz, FCC Band 1 TxH

RL-HP-11-B1 Radio Assembly, High Power 11 GHz, FCC Band 1 TxL

RH-HP-11-B2 Radio Assembly, High Power 11 GHz Band 2 TxH

RL-HP-11-B2 Radio Assembly, High Power 11 GHz Band 2 TxL

60-000301-01 Radio Assembly, High Power 11 GHz, FCC Band A TxH

60-000301-02 Radio Assembly, High Power 11 GHz, FCC Band A TxL



Issue: 1.0




DragonWave Inc.

60-000301-03 Radio Assembly, High Power 11 GHz, FCC Band B TxH

60-000301-04 Radio Assembly, High Power 11 GHz, FCC Band B TxL









60-000301-07 Radio Assembly, High Power 13 GHz, Band A TxH

60-000301-08 Radio Assembly, High Power 13 GHz, Band A TxL



RH-HP-15-B3 Radio Assembly, High Power 15 GHz Band 3TxH


RH-HP-15-B4 Radio Assembly, High Power 15 GHz Band 4TxH








60-000261-01 Radio Assembly, High Power 18 GHz, FCC Band B TxH

60-000261-02 Radio Assembly, High Power 18 GHz, FCC Band B TxL

60-000261-07 Radio Assembly, High Power 18 GHz, FCC Band C TxH



Issue: 1.0




DragonWave Inc.

60-000261-08 Radio Assembly, High Power 18 GHz, FCC Band CTxL

60-000280-01 Radio Assembly, Standard Power 18 GHz, FCC Band B TxH

60-000280-02 Radio Assembly, Standard Power 18 GHz, FCC Band B TxL

60-000280-07 Radio Assembly, Standard Power 18 GHz, FCC Band C TxH

60-000280-08 Radio Assembly, Standard Power 18 GHz, FCC Band C TxL

60-000280-11 Radio Assembly, Standard Power 18 GHz, ETSI Band A TxH

60-000280-12 Radio Assembly, Standard Power 18 GHz, ETSI Band A TxL







60-000262-05 Radio Assembly, High Power 23 GHz, FCC Band D TxH

60-000262-06 Radio Assembly, High Power 23 GHz, FCC Band D TxL

60-000279-02 Radio Assembly, Standard Power 23 GHz, FCC Band D TxH

60-000279-03 Radio Assembly, Standard Power 23 GHz, FCC Band D TxL

60-000279-04 Radio Assembly, Standard Power 23 GHz, ETSI Band A TxH

60-000279-05 Radio Assembly, Standard Power 23 GHz, ETSI Band A TxL

60-000279-08 Radio Assembly, Standard Power 23 GHz, FCC Band C TxH

60-000279-09 Radio Assembly, Standard Power 23 GHz, FCC Band C TxL

60-000279-25 Radio Assembly, Standard Power 23 GHz, FCC Band B TxH

60-000279-26 Radio Assembly, Standard Power 23 GHz, FCC Band B TxL

60-000279-10 Radio Assembly, Standard Power 24 GHz, DEMS TxH

60-000279-11 Radio Assembly, Standard Power 24 GHz, DEMS TxL



Issue: 1.0




DragonWave Inc.





60-000279-29 Radio Assembly, Standard Power 28 GHz, Band C TxH

60-000279-30 Radio Assembly, Standard Power 28 GHz, Band C TxL

60-000279-25 Radio Assembly, High Power 28 GHz, Band C TxH

60-000279-26 Radio Assembly, High Power 28 GHz, Band C TxL





Quantum IDU

Circuit Card

Assembly

61-000256-01

61-000256-03

61-000256-05

Applicable User Manual REL 1.03.00 83-000074-01-01-05 Product Manual, Horizon Quantum - Vol 1 83-000075-01-01-05 Product Manual, Horizon Quantum - Vol 2 83-000076-01-01-06 Product Manual, Horizon Quantum - Vol 3 83-000093-01-01-02 Product Manual, Horizon Quantum - Vol 4 83-000078-01-01-05 Horizon Quantum SNMP Documentation 83-000071-01-01-04 Quantum Quick Reference Guide 83-000100-01-01-00 Quantum Layer 2 Switching Quick Reference Guide

REL 1.02.06 No changes to User Product documentation from previous release.



Issue: 1.0




DragonWave Inc.

REL 1.02.05 83-000074-01-01-04 Product Manual, Horizon Quantum - Vol 1 83-000075-01-01-04 Product Manual, Horizon Quantum - Vol 2 83-000076-01-01-04 Product Manual, Horizon Quantum - Vol 3 83-000093-01-01-01 Product Manual, Horizon Quantum - Vol 4 83-000078-01-01-04 Horizon Quantum SNMP Documentation 83-000071-01-01-04 Quantum Quick Reference Guide 83-000100-01-01-00 Quantum Layer 2 Switching Quick Reference Guide

REL 1.02.00 83-000074-01-01-04 Product Manual, Horizon Quantum - Vol 1 83-000075-01-01-04 Product Manual, Horizon Quantum - Vol 2 83-000076-01-01-04 Product Manual, Horizon Quantum - Vol 3 83-000093-01-01-01 Product Manual, Horizon Quantum - Vol 4 83-000078-01-01-03 Horizon Quantum SNMP Documentation

REL 1.01.05.01 No changes to User Product documentation from previous release.

REL 1.01.05 83-000071-01-01-04 Quantum Quick Reference Guide 83-000100-01-01-00 Quantum Layer 2 Switching Quick Reference Guide 83-000074-01-01-02 Product Manual, Horizon Quantum - Vol 1 83-000075-01-01-02 Product Manual, Horizon Quantum - Vol 2 83-000076-01-01-02 Product Manual, Horizon Quantum - Vol 3 83-000093-01-01-00 Product Manual, Horizon Quantum - Vol 4 83-000078-01-01-02 Horizon Quantum SNMP Documentation

REL 1.01.00 83-000071-01-01-02 Quantum Quick Reference Guide 83-000074-01-01-01 Product Manual, Horizon Quantum - Vol 1 83-000075-01-01-01 Product Manual, Horizon Quantum - Vol 2 83-000076-01-01-01 Product Manual, Horizon Quantum - Vol 3



Issue: 1.0




DragonWave Inc.

83-000078-01-01-01 Horizon Quantum SNMP Documentation

REL 1.00.01 No changes to User Product documentation from previous release.

REL 1.00.00 83-000071-01-01-01 Quantum Quick Reference Guide 83-000074-01-01-00 Product Manual, Horizon Quantum - Vol 1 83-000075-01-01-00 Product Manual, Horizon Quantum - Vol 2 83-000076-01-01-00 Product Manual, Horizon Quantum - Vol 3 83-000078-01-01-00 Horizon Quantum SNMP Documentation

Known fatal bugs REL 1.03.00

None

REL 1.02.06

None

REL 1.02.05

None

REL 1.02.00

None

REL 1.01.05.01

None

REL 1.01.05

None

REL 1.01.00

None



Issue: 1.0




DragonWave Inc.

REL 1.00.01

None

REL 1.00.00

None

New CLI commands

(compared to previous

release)

REL 1.03.00

1. Data Path Encryption commands. Refer to Product Manual, Volume 2, for details.

2. 1+1 Hot Standby commands. Refer to Product Manual, Volume 2, for details.

3. Link Layer Discovery Protocol (LLDP) commands. Refer to Product Manual, Volume 4, for

details.

4. Cisco ECFM support (Bandwidth Vendor Specific Messaging) commands. Refer to Product

Manual, Volume 2, for details.

5. Terminal Access Controller Access-Control System Plus (TACACS+) commands. Refer to

Product Manual, Volume 2, for details.

6. save all command to save all 3 mib files in one step (l2swmib, ecfmmib, mib)

REL 1.02.06

None

REL 1.02.05

7. Multi-Carrier XPIC commands. Refer to Product Manual, Volume 2, for details.

8. set haam mode range [highest mode] [lowest mode]

REL 1.02.00

9. Packet Cut-Through commands. Refer to Product Manual, Volume 2, for details.

10. Bandwidth Doubling commands. Refer to Product Manual, Volume 2, for details.

11. Synchronous Ethernet commands. Refer to Product Manual, Volume 2, for details.

12. MAC learning commands. Refer to Product Manual, Volumes 2 & 4, for details.



Issue: 1.0




DragonWave Inc.

13. diag1 command for use with Merlin

REL 1.01.05.01

None

REL 1.01.05

1. Layer 2 Switch related commands for RSTP/MSTP & switch configuration.

a. Use “l2sw” to enter configuration domain for RSTP/MSTP.

b. VLAN, port configuration, IPG, network management interface configuration can also

be implemented in l2sw domain.

c. Refer to Product Manual, Volumes 1 & 4, for details.

2. save/delete l2swmib (to save/delete port & management configuration). This is required

regardless of l2switchFeature license status.

3. New behavior with “reset system” command. When user enters “yes” to save mib before the

system resets, then both the “mib” & “l2swmib” are saved.

4. get diagnostics (for Critical, Major, Minor alarms summary)

5. Peer Link Compatibility Mode (PLCM) commands. Refer to Product Manual, Volumes 1 & 2,

for details.

6. QC queue mapping commands. Refer to Product Manual, Volumes 1 & 2, for details.

7. Commands for Packet Cut-through Processing are included but not functional (CLI, Web &

SNMP). Available in release 1.2

REL 1.01.00

1. XPIC related commands. Refer to Product Manual, Volumes 1 & 2, for details.

REL 1.00.01

None

REL 1.00.00



Issue: 1.0




DragonWave Inc.

First release

Known minor bugs,

limitations and

workarounds

Limitations & Workarounds:

1. Releases 1.02.05 & higher over-air protocol is not compatible with previous releases (1.02.00 or earlier). Both ends of a link must be running same omni version if Rls 1.02.05 or higher for traffic to flow properly.

2. Narrow channel bandwidth (20 MHz, 14 MHz, 10 MHz & 7 MHz) support is generally discontinued in Release 1.02.05 & higher by removal of these bands & corresponding modes in Frequency File version 2.6.0. There will be some exceptions for narrow channel radio bands & modes, which will be supported by inclusion in future frequency file releases.

3. HAAM with Multi-carrier XPIC configuration is not supported. 4. RSL accuracy specification is increased to ±3 dB when deployed with short IF cable length

where cable loss is <1 dB at 1600-1900 MHz. 5. In rare cases of particular IF frequencies and with a significant IDU ambient temperature

change of ~30°C-40°C from hot to cold, a synthesizer unlock alarm can be triggered resulting in traffic loss (need to reset system to recover).

6. Do not power cycle during commit process. If a power cycle has occurred before a commit has completed, do not switch banks. Re-issue the commit process and ensure successful completion before switching banks.

7. Interoperation of certain features is not permitted: a. Any combination of the following features is not currently supported: HAAM, RLS,

ATPC, Radio Redundancy b. The following features are not supported with Bandwidth Doubling: RLS, ATPC,

Radio Redundancy, asymmetric system modes. c. SyncE is not supported with asymmetric system modes.



Issue: 1.0




DragonWave Inc.

8. HAAM is not supported for adjacent channel operation in 50 MHz channel bandwidths over a single radio in this release. Revised 50 MHz HAAM modes based on the hz50_322ac_256qam mode are required.

9. Management traffic should not be exposed to the far end through dp1 to dp4 unless it is managed over the air. Either of the following configurations are recommended:

a. Protect all dp1 to dp4 ports from management traffic using IPGs. For Example, if P3 is a management port, it should not be part of an ipg group that contains either of dp1, dp2, dp3 or dp4.

b. Isolate the management traffic through an IPG. For example, if P3 and P4 are management ports, place them into ipg5.

10. Dual channel operation (in system capacity 2) in QPSK for 6-8 GHz links is not supported. Note: dual channel HAAM operation for 6-8 GHz is okay since Tx power is backed off to 256 QAM levels for all lower modulations.

11. Dual channel operation (in system capacity 2) is supported only with radio bands for FCC/IC/ITU and 28/30/40/50/56 MHz channel bandwidths.

12. XPIC operation requires IF cable length difference between H and V radio connections to be ≤5.0 meters.

13. XPIC should be disabled if hot swapping radios and then re-enabled after the radios have been connected.

14. In Release 1.1.5 & higher, to save or delete the full configuration all of the following commands must be issued:

a. save mib; delete mib [newest | both] – ALWAYS REQUIRED b. save l2swmib; delete l2swmib [newest | both] – ALWAYS REQUIRED c. save ecfmmib; delete ecfmmib [newest | both] – applicable when running ECFM

15. With the “reset system” command, if the user enters “yes” to save mib before the system resets then both the “mib” & “l2swmib” are saved.

16. To erase the switch configuration perform the following commands: a. “delete l2swmib both”



Issue: 1.0




DragonWave Inc.

b. “reset system” c. Enter in no when asked to save mib d. NOTE: In a Bandwidth Doubling link, if only the l2swmib is deleted the software

will block setting the previously configured bandwidth doubling port even though it is no longer configured (see Bug 4431).

17. In Release 1.1.5 & higher, behavior of the switch configuration commands has changed. The following commands only have the option to take effect immediately or to not apply:

a. set ipg config b. set enet config c. set vlan config d. set network management interface

18. User should only enable/configure the quantity of VLANs required. The quantity of VLANs configured impacts execution times during & after upgrade. Example: if most ports are configured with all 4096 VLANs, it will take ~9 minutes to complete the upgrade. After upgrade, execution times increase for configuring (save l2swmib) and restoring more VLANS. Examples: ~2 minutes to save with 4094 VLANs vs ~1 minute with 2048 vs ~25 seconds with 1024. Similarly, with restoring the configuration on boot-up.

19. For optimum performance, RLS should be enabled with RSTP/MSTP. 20. ECFM with RSTP/MSTP: Any ECFM ports must be part of the default IPG (IPG0). Also if the

wireless path is to be included in ECFM, then dp1 must also be part of the default IPG (IPG0).

21. After upgrade to Release 1.1.5 or higher, cos queue cbs values will have 1% allocated to QC and the queue with the highest percentage will be reduced by 1%.

22. For mixed radio (R4 & R5) links, the hz50_322_256qam mode is not supported. 23. The following commands have been removed:

a. get/set maximum frame size b. get/set optical transmitter state

24. HAAM is not supported for links running the hz50_371_256qam mode.



Issue: 1.0




DragonWave Inc.

25. Quantum 38 GHz & 28 GHz radios need to operate with application omni 1.1.5 or higher and radio firmware 5.00.50 or higher. The Quantum IDU must be running Rls 1.1.5.x or higher before a Quantum 38 GHz or 28 GHz radio is connected to the IDU unit.

26. For a Quantum IDU or all-outdoor modem connected to 2 radios, both radios at the same end of a link must be the same type.

27. The following features are not supported in a mixed IDU link: AAM, HAAM, BAC, XPIC, RSTP, MSTP.

28. Mixed IDU link operation (Quantum IDU & Duo IDU at opposite ends of a link) is not supported in Releases 1.02.00 & higher. Configuring the peer link compatibility mode to “DUO” is not blocked; however, Release 1.02.00 software will keep the management & port configurations but revert to peer link compatibility mode setting of “QTM”.

29. For operation with Quantum 7 GHz and 8 GHz radios, indoor unit modem assembly part numbers of 60-000471-04 or higher are required to be used (Part numbers 60-000471-01/-02/-03 should not be used in combination with Quantum 7 GHz and/or 8 GHz radios).

30. RSL accuracy issue with 7/8 GHz radios: RSL accuracy spec with 7/8 GHz radios is increased to ±3 dB.

REL 1.03.00

Bug

ID

Short Description Applicable

to Previous

Release(s) 5283 Occasional dribbling block errors during haam down/up switching activity on

higher QAM modes (≥ 512 QAM) √ (1.03.00)

5282 Occasional HAAM switching at steady-state with max mode configured as 2048 QAM with 28M & 30M modes

√ (1.03.00)

5224 HAAM at max modulation of 512 QAM in 40, 50, 56 MHz channels may exhibit occasional HAAM event (bouncing) at steady state.

√ (1.03.00)

5285 SNR reading in HAAM modes vs non-HAAM modes can differ by 1-2 dB. √ (1.02.05)



Issue: 1.0




DragonWave Inc.

5281 Incorrect system up time in SNMP after sntp server time change. √ (1.00.00)

5279 Bandwidth Doubling: ECFM VSM-BW message for bandwidth does not reflect the correct bandwidth

√ (1.03.00)

5271 RSTP/MSTP long outage (Up to 45sec in a 8node ring) after reset the shortest path radio redundancy link while encryption enabled

√ (1.03.00)

5252 First attempt of radius login after failed attempt does not work. Subsequent attempt of the correct login credentials will work.

√ (1.00.xx)

5247 Encryption with OOB management: data path blocked while network management connection is lost or removed during reset system the txhigh unit. Traffic recovers when management connection restored.

√ (1.03.00)

5245 Failed to retain encryption key exchange configured as auto mode from manual mode after reset system. First disable crypto then reconfigure mode.

√ (1.03.00)

5239 Increase in steady-state latency of approximately 10% from 1.2.6 to 1.3.0. √ (1.03.00)

5214 Bandwidth doubling secondary unit wrongly shows control frames being counted.

√ (1.02.00)

5204 In-band management loss of SSH server connection to the far end after losing any network access recovery reset system.

√ (1.00.xx)

5196 Port level statistics not showing Tx Unicast counts when framesize is greater than 1522.

√ (1.00.xx)

5255 Creation of DWI permanent license file not needed in log entries. √ (1.03.00)

5217 VLAN config with ID of 0 or 4095 allows but config status missing or unexpected.

√ (1.00.xx)

4899 The port remains up while the admin state is set to off while HSB enabled and the port configured as part of user port

√ (1.03.00)

REL 1.02.06

Bug

ID Short Description Applicable

to Previous

Release(s)



Issue: 1.0




DragonWave Inc.

5194 BAC record sometimes shows default time stamp of 01/01/1970 00:00:00 for its uncompressed ratio.

√ (1.00.xx)

5192 Bandwidth Doubling: Incorrect MAC address displayed in partner information table.

√ (1.02.00)

5180 ATPC wrongly toggling max/min power when auto-disabled at coordinated power.

√ (1.02.05)

5177 Occasional loss of modsync in IF loopback for 50MHz & 56 MHz 256 QAM modes.

√ (1.02.05)

5172 No traffic egress in one direction after release of radio loopback (~1 in 10 attempts). Recovery with mute/unmute of radio transmitter.

√ (1.02.05)

5171 IF loopback: failure to recover from loopback with R4 radios. √ (1.02.05)

5170 IPG configuration not retained after upgrade from 1.1.0 to 1.2.6. Fixed for direct upgrades to 1.3.0.

√ (1.02.05)

5169 Software licenses not retained after upgrade from 1.1.0 to 1.2.6. Fixed for direct upgrades to 1.3.0.

√ (1.02.05)

5166 HAAM switching at a steady-state with 56 MHz 256 QAM (hx56_379_256qam).

√ (1.02.05)

5165 Loss of modsync txL-Slave wrongly discovering txH-Master after resest system multi-carrier XPIC. (rare)

√ (1.02.05)

5158 HAAM not recovering after deep attenuation removed (rare). √ (1.02.05)

5157 VLAN config modification not prompting for save of l2swmib. √ (1.01.05.xx)

5156 ATPC not functioning with R4 radios with multi-carrier XPIC. √ (1.02.05)

5138 SW inventory items appear as “Not Validated” if not enough RAM available. If ftp download reports back as successful, then file can still be used.

√ (1.01.xx)

5127 R4 radio multi carrier XPIC slave not showing RSL in cli/snp/web. √ (1.02.05)

5123 Radio power off alarm shows no such index for SNMP wp2 multi-carrier XPIC.

√ (1.02.05)

4673 Traffic drop if 9600 byte frame treated as untagged using trunk port default ID not as 1.

√ (1.00.xx)



Issue: 1.0




DragonWave Inc.

REL 1.02.05

Bug

ID

Short Description Applicable

to Previous

Release(s) 5100 Multi-carrier XPIC with haam not recovering with mid-high-mid XPI fade. √ (1.02.05)

4776 XPIC & HAAM - Failed to raise working link path in QPSK when other link is down.

√ (1.01.xx)

5129 R4 radio with multi carrier XPIC not maintaining max transmit power upon reset.

√ (1.02.05)

5128 R4 radio + multi-carrier XPIC slave unit not detecting radio loss of comms. √ (1.02.05)

5126 Set haam mode range while haam is currently disabled causes raise/clear loss of modsync.

√ (1.02.05)

5125 Repeating “Set Tx Power request failed” logs when mode range changed on multi-carrier XPIC slave.

√ (1.02.05)

5124 Attempt to set haam on/off via web causes raise/clear loss of modsync. √ (1.02.05)

5122 Radio loss of comms alarm not incrementing counter for slave units with multi-carrier XPIC.

√ (1.02.05)

5121 Traffic drop for 20 min 4chXPIC bandwidth doubling after radio mute with MAC learning disabled.

√ (1.02.05)

5119 ATPC targets vs sensitivity for some 23G modes differ by 11 instead of 15 dB. √ (1.00.xx)

5118 ATPC targets vs sensitivity for 6G modes hx10_43m1_64qam and hx10_63m1_256qam differ by 23 dB.

√ (1.01.xx)

5117 Radio bands for 6GU are missing the qpsk test mode required for radio loopback.

√ (1.01.xx)

5116 Occasional non recovery from reset system ATPC on multi-carrier XPIC. √ (1.02.05)

5115 ATPC not at correct max attenuation for syscap3 wp2 after removal of radio loopback.

√ (1.02.05)

5114 Removal of IF loopback may result in continuous wireless RxFrameErrors √ (1.01.xx)



Issue: 1.0




DragonWave Inc.

HAAM enabled (~1 in 100 attempts).

5113 Radio loopback syscap3 shows raise/clear loss of sync for the loopback port. For proper operation, the other local end wireless port radio needs to be muted.

√ (1.02.05)

5107 Non-recovery from reset radio multi carrier XPIC with ATPC enabled - rare. √ (1.02.05)

5104 Event log for haam mode range via web shows source as unknown. √ (1.02.05)

5103 Event log for admin state on via set enet config via CLI shows blank parameter.

√ (1.01.xx)

5102 Multi-carrier XPIC dribbling errors hx56_373_256qam and hx50_352_256qam after some re-acquisitions with -20 XPI present.

√ (1.02.05)

5101 Multi-carrier XPIC HAAM switching events and/or dribbling errors after some reacquisitions with -20 XPI present.

√ (1.02.05)

5097 Radio not completing boot-up properly - appStartup failure – RARE. √ (1.02.05)

5092 Cut-through queue has higher latency upon the presence of background traffic with jumbo frames to non-cut-through queues, compared with background traffic with frame sizes <1500 bytes to non-cut-through queues.

√ (1.02.xx)

5086 Modem loss of sync upon configuring haam mode range with different minimum modes at each end until the peer end is configured with the same minimum haam mode.

√ (1.02.05)

5084 Radio loopback for wp2 in system capacity 2 shows on for both wp1 and wp2.

√ (1.01.xx)

5083 False Tx Power Detector below Low Threshold alarm with system capacity 2 during radio loopback.

√ (1.01.xx)

5068 False excessive cable loss change alarm with IF loopback enabled. √ (1.02.05)

5066 IF loopback with R4 radios requires muting of far-end for proper functionality.

√ (1.02.05)

5060 Radio redundancy has conflicting results for get link monitor parameters command.

√ (1.02.05)

5058 Upgrade from 1.2.0 to 1.2.5 did not retain same SSL certificate. √ (1.00.xx)



Issue: 1.0




DragonWave Inc.

5029 Occasional dribbling block errors during haam switching following a modem reacquisition event.

√ (1.02.05)

5027 No recovery if system mode change along with partner failure in multi-carrier xpic or with single link and radio loopback turned on before system reset for the system mode change to take effect. Can recover with a reset of both ends for the system mode change to take effect.

√ (1.02.05)

5023 FrameQ code_check or length error results in datapath crash - RARE. √ (1.02.05)

4989 Radio still in loopback after cable loss calculation - RARE. √ (1.02.05)

4986 Unexpected cable loss change variance with multi-carrier XPIC. √ (1.02.05)

4930 Radio replacement of R5 to R4 required reset system to achieve modsync. √ (1.01.xx)

4928 Radio replacement with fcc18_b_30 to fcc18_1_30_R5 fails to auto-configure.

√ (1.01.xx)

4908 User cannot set BAC on cut-through queue even when QoS is set to off √ (1.02.xx)

4907 High latency with bac if the traffic frame size is less than selected bac block size.

√ (1.02.xx)

4906 ECFM trace route packet is not forwarded upon request from the peer device.

√ (1.01.xx)

4903 18 GHz ATPC range not achieving full 20 dB of vva attenuation. √ (1.01.xx)

4795 Quantum 38GHz Radio reporting erratic RF Detector Power √ (1.01.xx)

4667 Configuring SNTP via web shows unexpected results. √ (1.02.05)

4666 SNTP IP addresses not shown in web. √ (1.02.05)

4537 Web error msg not meaningful for unsuccessful save mib due to radio band & system mode configuration mismatch.

√ (1.00.xx)

5069 Occasional set loopback off fails to actually set to off. √ (1.01.xx)

REL 1.02.00

31. Release 1.02.00 over-air protocol is not compatible with previous releases. Both ends of a link must be running Rls 1.02.00 for traffic to flow properly.



Issue: 1.0




DragonWave Inc.

32. Loss of management (bug 4484): With a new system or after l2sw configuration is put to factory default (“delete l2swmib both”), a user needs to configure any one front panel port (typically p5-p8) which is in the same IPG as any one of the DP’s to be trunk port first (with vlan id range 1 to 5). See example configuration for front panel port “p5” below:

->set vlan config #Press 'Ctrl-X' to exit config process #Press 'Enter' to retain previous value Port [ 1 - 8 ] (1) ? 5 Vlan Port Type [ access(1) | trunk(2) ] (1):2 Default Vlan Id [1] (1): Vlan List ():1-5

Bug ID Short Description Applicable to Previous Release(s)

4911 TCP/IP stack timer problem. If using l2switchFeature, this problem can result in loss of access to L2SW shell. System reset is required for recovery.

√ (1.00.xx)

4765 DSCP priority is incorrectly set to 0 with a change of VLAN priority. Work around is to re-issue the “set network management interface” command with exact same parameters.

4674 Traffic drop with combination of large frame inner-VLAN with default-VLAN set to anything other than 1

4659 Changing system capacity from 1 to 2 along with a radio band change requires an extra save mib + reset system.

√ (1.00.xx)

4658 Management port p3 down for 20 minutes after reset system (RARE). √ (1.01.05.xx)

4640 ATPC threshold not always 15 dB above sensitivity specification.

4614 IF loopback actually loops back the data traffic without the network option



Issue: 1.0




DragonWave Inc.

enabled.

4577 Unable to establish Telnet session after power cycle (RARE).

4532 Frequency File 1.00.23 has incorrect ATPC thresholds for 7 MHz system modes. Correct ATPC thresholds are included in Frequency File 1.00.24 & higher.

4484 When configuring a Quantum link for “VLAN trunking” and “in-band management”, it is possible to lose over-the-air management with the far end Quantum unit. (See item 31 above.)

√ (1.01.05.xx)

4337 Wireless port 2 TX and RX frequencies not displaying in Web. √ (1.00.xx)

4417 Ingress traffic dropped at switch if swap source/destination MAC.

4409 IPG configuration change on Bandwidth Doublinig link causes small amount of Rx Frame Errors

4407 SNTP turned on automatically during upgrade 1.0.1 to 1.2.0

4405 Bandwidth Doubling System Summary Alarms shows no with Bandwidth Doubling alarm active

4404 Unable to configure Current System Speed from Web/SNMP

4395 Bandwidth Doubling: Web Bandwidth Doubling Port configuration displays "none"

4380 Rx Cable loss is not always consistent √ (1.00.xx)

4378 Larger frame size (>9000) packet discarded by the switch if the speed is set to 100BaseT

√ (1.00.xx)

4373 Ingress traffic occasionally being dropped at switch upon loss of modsync if duplicate source MAC.

√ (1.01.05.xx)

4368 Occasional temporary loss of modsync upon set QoS on (~1 out of 150)

4364 "cos expedite queue on" help information is incorrect

4359 Telnet session stopped with Rx buffer still working (RARE)

4355 Configuring radio band via SNMP results in unexpected programmed frequencies.

√ (1.00.xx)



Issue: 1.0




DragonWave Inc.

4352 ECFM: CLI command (? set ecfm mep level) help need to be updated with vlan priority configuration.

4320 Dribbling errors with continual haam switching 13G asymmetric mode (hz4214_277_95_256qam).

4313

Enabling "cos expedite queue " command is still showing as old method in WEB and SNMP interface. Queue parameter is not included but in this release only Q4 is valid and is set by default.

4312

Enabling of the "cut through processing" command is still showing as old method in WEB and SNMP interface. Queue parameter is not included but in this release only Q4 is valid and is set by default.

4305 Unable to set partner MAC address & communication port in Web, SNMP for Bandwidth Doubling.

4276 Incorrect block reporting for the secondary wireless port (single modem config only). Statistics reporting issue only; not traffic affecting.

4270 Bandwidth Doubling: No diagnostic for Bandwidth Doubling invalid link configuration alarm

4258 False HAAM mode mismatch alarm with asymmetric modes even with haam off.

4243 Upgrade incompatibility with 1.2.0 and 1.1.0 - drop in traffic and AIM not working.

4187 ATPC: Transmitting at Coordinated Power trap wording is confusing √ (1.00.xx)

4175 Redundancy Alarms Counters updating every 4 seconds √ (1.00.xx)

4160 Change from single/single to dual/single and the modems system modes are programmed differently. Need to program system mode after any system capacity change.

√ (1.00.xx)

4157 Bandwidth Doubling: "get diagnostics" cli command returns as "Diagnostics are not available"

4132 Alarm: Radio Drain Current alarm SNMP Trap flooding √ (1.00.xx)

4130 Alarms: SNTP Server Unreachable counter not incrementing regularly √ (1.00.xx)



Issue: 1.0




DragonWave Inc.

4128 Alarm: HAAM Configuration Mismatch Alarm trap not raised √ (1.00.xx)

4125 Alarm: HAAM Configuration Mismatch Alarm with HAAM not enabled √ (1.00.xx)

4111 Web: Redundancy Switch Radio Results page status is "TODO" √ (1.00.xx)

4108 Web: Radio Power Off wireless_port2 no such object

4050 Additional RSTP/MSTP event logging to "event logs" √ (1.01.05.xx)

3979 Missing entries in SNMP Modem table when XPIC is off. Problematic for NMS.

√ (1.01.00)

3948 Request for Layer 2 switch event log available to the NOC user in the DW CLI. √ (1.01.05.xx)

3817 Sending out a V4 request but the SNTP server is responding with a V3 type. √ (1.00.xx)

3803 Bandwidth record logs can be erased with switch bank and 1000% utilization (due to system speed set to zero).

√ (1.01.05.xx)

3747 ECFM: CCM packets with VLAN priority other than 0 are dropped √ (1.00.xx)

3472 Blocked SyncE from choosing a 10Mbps ethernet port

3372 CLI - get bac command sometimes returns response for other command √ (1.00.xx)

3371 CLI - NAK returned for valid commands √ (1.00.xx)

4429

Bandwidth Doubling: network management not blocking dp4 when bandwidth doubling is enabled and dp4 is already configured as part of the bandwidth doubling port.

4394 Should have a proper error message when enabling ATPC while HAAM is enabled to reflect that feature combination is blocked by software.

√ (1.00.xx)

4393 ATPC should be blocked while bandwidth doubling enabled in Rls 1.2.0.

4356 Haam switching status truncates current mode with 128-to-256 switch. √ (1.00.xx)

4191 SNTP Server first 2 default servers may be no longer in service

REL 1.01.05.01

33. Supported maximum input data rate for bac feature is 1.5 Gbps for release 1.00.00 through to release 1.01.05.01.

Bug ID Short Description Applicable to



Issue: 1.0




DragonWave Inc.

Previous Release(s)

5046 ECFM stopped functioning after reconfiguring management.

3834 Within L2SW prompt, “set network management interface” command does not work with partial entries. Must include all parameter settings. For example, if port list settings are not included in the command, the management port list will be set to none and therefore no remote management will be available.

√ (1.01.05)

3948 Include L2 switch event log availability to NOC user in the DragonWave CLI. √ (1.01.05)

3885 Radio loopback fails to engage occasionally when ATPC is also enabled. √ (1.00.xx)

3830 Tx power inaccuracy difference for wider channel bandwidths due to tx baseband filter roll-off.

√ (1.00.xx)

REL 1.01.05

Bug ID Short Description Applicable to Previous Release(s)

3772 Quantum unit could become unresponsive after reset following FTP omni upgrade (RARE).

√ (1.00.xx)

3766 ECFM mib not properly saved or restored with some configurations (ex. MEP & MIP configured with same level but different ports.)

√ (1.00.xx)

3765 ECFM limitation to a maximum of 4 ECFM hops in the link trace path. √ (1.00.xx)

3764 ECFM: before performing a link trace the user needs to clear CCM-database on all nodes.

√ (1.00.xx)

3763 ECFM: End point (MEP) will not reply to a trace-route request if a MIP is defined at the receiving port.

√ (1.00.xx)

3756 ECFM with RSTP: CFM packets are bypassing the RSTP blocking port when they should not.



Issue: 1.0




DragonWave Inc.

3743 PLCM: Management VLAN ID is not configured properly in Duo compatibility mode with in-band management.

3738 Permanent loss of management with large quantity of VLAN IDs and license 6 l2switchFeature is not licensed. Recovery method is to remove and insert the Ethernet management cable. Then reduce quantity of VLANs provisioned and save l2swmib. NOTE: Configuring up to 1500 VLANs is maximum working range with license 6 l2switchFeature not licensed.

3734 Occasional missing packets with mixed IDU link (Duo-QTM). Degraded RBER performance when this occurs.

3692 Enabling and disabling IPG config causes momentary traffic reroute with RSTP/MSTP enabled

3684 Cal Files: only support a single default cal file for Quantum variants √ (1.00.xx)

3783 Occasional set tx power failure with R4 radio and ATPC on.

3341 Log Files may show odd dates and times √ (1.00.xx)

3319 IPG and DP description insufficient in product manual √ (1.00.xx)

4377 RADIUS Authentication results in all users getting Admin privileges. √ (1.00.xx)

3733 Log entries for SNMP set cos flow has unknown.

3732 Log entries for SNMP set l2swsave mib has unknown.

3731 No modsync after hot-swap replacement of R4 radio with R5 radio. Recovered with reset system.

3730 SNMP LicensedFeatureGroupIndex not showing l2switchFeature description.

3729 VLAN List in CLI does not show current IDs when provisioning or modifying.

3728 VLAN ID 4095 does not show when provisioned in entire range or group.

3727 PLCM: Configuring through CLI interface doesn't work correctly (l2swmib is not saved). Works in WEB & SNMP.

3725 Cannot cancel the PLCM interactive command process.

3724 RLS logs (cfgChange) appear for get commands. √ (1.00.xx)



Issue: 1.0




DragonWave Inc.

3723 False log message - An unexpected condition occurred (1)

3722 Provisioning data for bandwidth record thresholds not retained after upgrade.

3712 If DP ports are grouped in the same IPG and one of those same DP ports is part of Network Management Interface (NMI), then any DP ports moved to a different IPG will still remain part of the NMI.

3709 Save capability for saving ECFM data not in web. √ (1.00.xx)

3708 Could use output message outlining save mib options.

3707 ECFM frames ar discarded, if MEP belongs to non-vlan class or service √ (1.00.xx)

3705 hz50_371_256qam, R5 radio wrong Maximum ATPC attenuation

3702 Over-air management traffic needs special treatment. When managing the far-end through Air Interface, user should assign high priority to management traffic.

3701 Released frequency files 1.00.14 & 1.00.15 have wrong HAAM modes for dems24_a_50

3698 VLAN config shows duplicate event logs with different info.

3687 Post upgrade bac record logging was set to off.

3655 Unable to change SNMP Manager status to "disabled" √ (1.00.xx)

3653 Diagnostic data not showing proper WP info syscap2 loss of modsync.

3650 False radio alarm after hot-swap replacement of R5 radios with R4 radios. Save mib & reset system clears the alarm.

3601 Feature Request - "commit mib"

3569 L2sw configuration commands need to be logged

3511 CRC for frequency file via sw inventory is not unique.

3486 Update Product Manual with Battery Return treatment conditions √ (1.00.xx)

3467 Narrow band HAAM mode receiver offset from center of channel √ (1.01.xx)



Issue: 1.0




DragonWave Inc.

3387 Request "Actual Transmit Power" be added to web GUI √ (1.00.xx)

3370 Unexpected surge in SNR (no radios) - logs several threshold raise/clear. √ (1.00.xx)

3368 11G Bench Test Setups need to be physically separated for appropriate RF isolation

√ (1.00.xx)

3366 Set transmit power fails to change in WEB when invalid value entered √ (1.00.xx)

3365 "set switch default config" should be a Super user level command √ (1.00.xx)

3357 WEB PAGE - Feature Upgrade page should show if features are currently lic nsed.

√ (1.00.xx)

3355 Adding a dp to an ipg sometimes adds all the available physical ports √ (1.00.xx)

3352 Need additional SNMP command for BAC statistics √ (1.00.xx)

3351 Unused ports should default to admin down state √ (1.00.xx)

3344 SNTP help on the WEB GUI has errors in details √ (1.00.xx)

3339 SFP Optical Transmitter Enable Faults √ (1.00.xx)

3338 IPG0 and DP1-4 Configuration(s) need better coverage in product manuals √ (1.00.xx)

3336 Backup/Restore needs to include all switch configuration items √ (1.00.xx)

3333 Ability to remove admin and NOC accounts

3332 Add ability to turn alignment mode on from web GUI √ (1.00.xx)

3330 Source port or IP included as varbind in TTY Session Commenced/Terminated SNMP Traps

3329 Confusing message in FTP upgrades via CLI - (infkbps) √ (1.00.xx)

3326 RSL threshold levels do not work properly √ (1.00.xx)

3324 admin level account has too much permission

3323 RSL Below Threshold alarm not being raised consistently with syscap3. √ (1.00.xx)

3316 Quantum will not pass user data using default configuration. Need to configure ports.

√ (1.00.xx)



Issue: 1.0




DragonWave Inc.

3314 Cannot Use WEB GUI to configure IPG, VLANs √ (1.00.xx)

3281 R5 Radio power detector problem at very low radio output power

3254 Downgrade key might get corrupted if a power reset happens during downgrade

√ (1.00.xx)

3706 ATPC is disabled after R5 radio is replaced by R4 radio or vice versa

3386 Incorrect wire thickness shown for IDU grounding wire in Product Manual √ (1.00.xx)

3335 Quantum web Interface displays invalid BAC compressor sizes as default √ (1.00.xx)

3318 Network Management Interface Type is awkward to configure

3313 Web page support for IPG config and status. √ (1.00.xx)

3222 Additional BWA Compression Ratio and Uncompress d Percentage Logging

REL 1.01.00

From the above list of limitations, items #4-13 & #33 also apply to REL 1.01.00. 34. If using ATPC and not operating the link close to saturation, turn off ATPC before setting

transmit power.

REL 1.1.0 Bugzilla list:

Bug_ID Short Description Applicable to Previous Release(s)

2927 ATPC saturation algorithm fails in HP link (R4 radios) √ (1.00.xx)

2958 Customer must ensure that the FTP server remains up during an omni upgrade. In rare instances, the Quantum application software may terminate, requiring the customer to power cycle the unit. The omni must then be downloaded again, as the FLASH memory may be corrupted.

√ (1.00.xx)

2982 User allowed to switch to corrupt bank (caused by power-cycle during √ (1.00.xx)



Issue: 1.0




DragonWave Inc.

commit). The unit will no longer boot properly and requires a re-download (via serial port) of the IPL/EIPL/omni to proceed.

2931 Wireless port2 cable loss not shown in SNMP/Web for syscap2. √ (1.00.xx)

3177 For IF loopback to function, both the local radio and the far-end transmitter need to be muted (i.e. “set radio transmitter state off”).

√ (1.00.xx)

2682 Radio Loopback – network option is always disabled in REL 1.0.0 & REL 1.0.1 but can be enabled in REL 1.1.0. Enabling the network option can potentially cause a flood in the network, especially if the management port belongs to any IPG/dp group.

2932 Programmed IF frequencies not in SNMP or Web. √ (1.00.xx)

2934 Ethernet management port stuck in loopback post reset - floods network. (RARE)

√ (1.00.xx)

2941 Feature Request: More detailed error message for attempting to enable ATPC with HAAM.

√ (1.00.xx)

2946 SNMP/Web does not show negative for cable loss less than 1. √ (1.00.xx)

2959 set transmit power wireless_port2 blocked until after reset when system capacity changed

√ (1.00.xx)

2961 XPIC equalizer stress alarm not functioning

2962 Feature Request: XPIC half capacity operation with single path loss

2963 Radio Loopback with XPIC not supported

2964 Help Item for reset [system|modem|radio] not correct - “reset modem” not available

√ (1.00.xx)

2966 Event logs for telnet login/logout not clear on description √ (1.00.xx)

2969 ATPC w/ XPIC attenuator (rm x) can exceed available attenuation range limit by small amount (~0.5dB)

2970 XPIC with 14 MHz channels takes long time to gain mod sync

2971 Feature Request: Performance logs to include XPIC info

2979 XPIC cfgChange log entry "Unknown" when XPIC status changed from web



Issue: 1.0




DragonWave Inc.

2983 SNMP stops functioning post-reset (SNMP packets dropped) - RARE √ (1.00.xx)

298 Incorrect log: Optical Transmitter Initialization Error with Admin State off √ (1.00.xx)

2987 Feature Request: include additional log files with "save debuginfo" data

2991 Radio loopback (system capacity 3) needs both far-end transmitters to be muted.

√ (1.00.xx)

3002 ATPC tx power note in web GUI incorrect. Correct note is that tx power is settable while ATPC is enabled.

√ (1.00.xx)

302 3 Radio transmitter state CLI feedback can be incorrect with frequent SNMP queries (≤1 sec)

√ (1.00.xx)

3024 Secu e web (https) still allows non-secure access for same user. √ (1.00.xx)

3037 Redundancy switch causes unexpected algorithm based switch to primary port on far end of link

3038 Cable loss re-calculation can differ up to 2db (varies with Rx power).

3039 Occasional low SNR in 32QAM modes with XPIC on following reset system

3050 WFQ BW allocation with expedite not always as expected. √ (1.00.xx)

3116 Version number of actual running IPL not visible via sw inventory. √ (1.00.xx)

3118 Versionof IPL should read 1.0.0 and not 1.1.0.

2967 CLI alarm for p8 truncated when no eth ports connected. √ (1.00.xx)

3120 Add note in User Manual for Radio Loopback and IF Loopback: to ensure the loopback will perform as expected, the state of the far-end radio(s) should be checked to confirm it is actually muted (i.e. “get radio transmitter state”). Note: enabling the loopback feature automatically mutes the far end radio of the corresponding wireless port, but there may be certain link conditions (modem block errors, loss of modem receiver signal, faulty radio, etc.) when the over-air communication is not possible and signaling to mute the far-end transmitter is not successful.

√ (1.00.xx)

3201 SNR threshold setting is capped by value in frequency file and limit differs for various system modes

√ (1.00.xx)

3218 LED does not indicate radio firmware download. √ (1.00.xx)



Issue: 1.0




DragonWave Inc.

3223 IF Loopback does not function (30M modes & lower). √ ( 1.00.xx)

3224 For correct IF Loopback operation, all IF ports need to be terminated (i.e. connected to a radio or 50 Ω termination). Note: +48V is present on center pin of each IF port.

√ (1.00.xx)

3225 Confusing error message for simultaneous IF Loopback in syscap 2 √ (1.00.xx)

3228 QoS (WFQ with EXP off): bandwidth distributions between queues not always achieving expected values when over-air speed < system speed.

√ (1.00.xx)

3229 SNR threshold with HAAM enabled is always 0. √ (1.00.xx)

2922 Feature Request: Add IP Address to v2 trap varbind list: Trap forwarding by EMS requires this info.

2972 Feature Request: Implement message CRC between Quantum IDU and ODU radio.

2988 Feature Request: Improved boot logging.

2995 Feature Request: PLM-0027: non-reset capability to enable HAAM

2996 Feature Request: PLM-0029: New SNMP trap for modem block errors

2997 Feature Request: PLM-0041: Add actual Tx power being recorded in the performance logs

2998 Feature Request: PLM-0043: Enable user to turn ATPC logging on or off

2999 Feature Request: PLM-0049: SNMP Trap or alarm to be triggered associated with IF cable short

3000 Feature Request: PLM-0059: Create flat .config files (not in BINARY) for Quantum config files to be reviewed & stored in inventory management tool

3003 Feature Request: PLM-0081: Persistent memory to store time when DW device came on air

3117 Omni as packaged contains an unreleased IPL - no affect to customer.

REL 1.00.01

From the above list of limitations, items #4-9 & #33 also apply to REL 1.00.01.



Issue: 1.0




DragonWave Inc.

35. If using SSH to manage the device, ensure that the key exchange option is disabled at the client set-up.

36. If using ATPC and not operating the link close to saturation, turn off ATPC before setting transmit power.

37. RSL accuracy for Quantum radios with T/R spacing ≤300 MHz (13 GHz for example) can exceed the specification. A fix is available in REL 1.1.0.


Bug_ID Short Description

2913 SSH re-connect (dropped from client SSH re-key option) halts management

2892 SNMP stopped functionng post reset due to corrupted snmpHttpd.xnv file

2915 Network management command required post port default priority configuration.

2916 Command for port default priority configuration not retained post reset.

2841 Feature Request: Import HCP management port improvement: queuing

2744 User Manual: Need clear description for sw commit, freq file etc.

2753 Feature Request: CS wants BAC SNMP Oids for monitoring/graphing

2765 WFQ with bac and PRBS data-fill shows less than expected egress.

2793 High latency PDV when input equal to CIR plus random frame sizes.

2794 Wireless port faulty after reset system

2802 Wrong alarms present status through the web with no real alarms

2803 Spelling mistake"Daul Wireless Ports" in web home page.

2804 Tool-tip pop-up dialog for tx power via web not complete.

2806 HAAM switch bouncing (256qam to 128qam) 23 GHz 56M/14M modes & 11 GHz 40M/30M modes with slow fade around switching threshold.

2809 Downloading of corrupted/large omni/freq file not gracefully handled.

2843 SNMP file Horizon-MIB_1.0.0.mib as released does not contain quantum.

2847 No trap, alarm or log entry for Sec. Port Radio Faulty in redundancy



Issue: 1.0




DragonWave Inc.

2853 HAAM continual auto-switch dual capacity show more errors than single capacity.

2860 System speed of 0 could result in loss of far-end inband management (QoS on).

2861 Feature Request: to allow change in tx power while HAAM is enabled.

2862 HAAM always at max tx power even if power previously reduced.

2865 CLI set traffic stats to 0 affects the performance log data for bw %.

2868 SNMP Strict compilers reports warnings and errors. Lenient compilers OK.

2902 Set tx power with ATPC on adds 20db attenuation first to handle running close to saturation case.

2903 Need to apply workaround of re-enabling of ATPC upon band/mode/capacity change.

2907 buffer not cleared during RLS shutdown

2908 HAAM switching 14M shows small bursts of modem errors.

2909 HAAM switching latency higher between QPSK-16QAM than other modes.

2910 False alarm of caltables missing when freq not programmed.

2768 DW DBS debug cmd: nic loopback is not implemented properly

2771 Feature Request: Allow ECFM changes with ECFM process restart rather than full system reset

2888 Redundancy: "switched port: 2 is not working" message following successful manual switch

2911 SNMP trap hzQtmRadioSynthLostLockCleared continually repeating.

REL 1.00.00:

From the above list of limitations, items #4-9, #33 & #35-37 also apply to REL 1.00.00.





Issue: 1.0




DragonWave Inc.

2375 Limitation for Rel 1.0: Inter-operation of certain features is not permitted. Any combination of the following features is not supported in Rel 1.0: HAAM, RLS, ATPC, Redundancy

2550 RSL readings jump up to 40db upon loss of modsync at RX Saturation or RX Sensitivity threshold.

2646 Unexpected lower egress rates with bac Q1-3 and with QoS/WFQ policy under some traffic scenarios.

2660 HAAM switching via link attenuation adjustments occasionally results in data loss. (Ex. 5 data loss events over thousands of modulation switches)

2726 Rx frame errors with bac multi-enet port config. Occurs only on queues with bac enabled and for input data rates >1.5 Gbps.

2491 Port traffic stats fail to show data after continuous web/snmp polling. Occurs under very extensive web/snmp polling, does not affect user data traffic.

2720 HAAM with 30M config showing no HAAM modes & no modsync.

2792 ATPC not adjusting transmit power after initial enabling of ATPC feature. Work-around is to set transmit power & save mib on both ends again for all applicable wireless ports. When transmit power is set after ATPC is enabled, the max ATPC attenuation gets updated correctly and ATPC will operate.

2793 High latency PDV when input equal to CIR with random frame sizes.

2802 Web alarm summary status on home page always shows “yes” even when no alarms are present. Individual alarm status is correct for web, SNMP, and CLI. Summary status only appears in web.

2047 Feature Request: Allow customer to choose the wireless port that will be active in a failure scenario.

2123 Feature Request: Configure radio band on the fly (for OPS)

2212 Feature Request: Improve UI experience for Redundancy.



Issue: 1.0




DragonWave Inc.

2251 "get tempcomp" command does not respond

2302 Feature Request: Link upgrade vs individual node upgrade.

2303 Feature Request: Web page improvements.

2307 During group authentication failure traffic is not blocked.

2308 During unique authentication failure traffic is not blocked.

2324 Both Tx and Rx, Pause flow control not functioning. Flow control not supported in first release.

2343 Feature Request: Separate Warnings page in Web.

2359 CLI "get system summary" has no RLS info.

2428 QTM Web Engine is slow: recommend implementing new engine.

2435 Web: Link Alignment Tool refresh rate leaves the table blank for ~3s in some browsers.

2440 Enabling bac when billing based on bandwidth utilization has neutral benefit when link is running at <100% of current speed.

2441 Bandwidth logging capped at 100%. Need to revisit with respect to bac feature.

2450 Feature Request: Quantum LAG to support LACP or PAgP protocol.

2455 Sysconfig files are different before and after restoring config. This only occurs the first time the user does a “save config”; not after subsequent “save configs”.

2456 Feature Request: List Upgrade/Downgrade information in one location.

2470 Feature Request: Merlin L2 Support

2488 Change Radio Cable Loss definition in SNMP MIB to reflect IF Path

2505 Feature Request: Add LLDP support.

2506 Feature Request: Web page improvement, add Link Management Framework.

2507 Correct the name of message queue.

2531 Config Backup/Restore: include IPG settings.



Issue: 1.0




DragonWave Inc.

2540 FTP of cal file does not recognize name.

2556 Log entry missing for SW download.

2560 Omni size: remove duplicate libs in OS and app;

2565 Logs show enet ports as linkup with enet ports disabled (admin state off). Enet status indicators and alarms are ok, only boot-up logs/traps incorrect.

2583 IF synthesizers not programmed correctly after hot swap of radio types (ex. AP/Duo radio removed and Quantum radio connected).

2584 ATPC sets the power to the lowest level upon radio failure.

2606 FPGA physical memory are mapped multiple times in appMain.

2607 Frequency file version number is not displayed by separate CLI command. It is displayed under “get sw inventory”.

2608 Bandwidth record thresholds not configured with config restore from HZ Duo IDU.

2611 Feature Request: ECFM backup/restore from Horizon Duo IDU to Quantum.

2621 Redundancy: Reset system causes switch at other end of link some of the time.

2630 Help gives wrong range for RSL hysteresis (ATPC).

2631 Radius super user authentication help is incorrect.

2647 No log entry for "set radio transmitter state on"

2656 BAC config not restored from backup.

2658 SNMP manager config takes several attempts (post delete mib).

2662 Duplicate log message could impact trouble-shooting (HAAM especially).

2666 SNMP RlsStatusTable needs to be optimized.

2667 Ingress stats not capped at 1000 (shows 1012) multiple ports, 1 IPG.

2669 Security: change DWI access.



Issue: 1.0




DragonWave Inc.

2671 HAAM and redundancy (syscap 4) should be blocked for rel 1.0.

2672 Message for ATPC attempt with HAAM enabled needs improving.

2673 Feature Request: Add Merlin like "diagnostics" command.

2678 Longer RLS trigger time upon setting optical transmitter state off/on

2679 Port not coming up after power cycle when the speed set to 100baseT

2682 Radio Loopback -network option for looping back traffic is disabled in Rel 1.0.

2691 Logs: Modem SNR threshold alarm/cleared fills logs. Observed on stand-alone unit, not in a link.

2704 Not able to clear enet port statics counter through web.

2709 Enet duplex auto is not negotiating with the neighbor device.

2710 Quantum (1002+) Radio loop back is not supported while HAAM enabled in Rel 1.0. Must disable HAAM and reset system before enabling Radio loopback.

2713 Egress via “get traffic statistics” show counts with enet cable removed. In Quantum, the NIC fpga always egresses packets to the switch. If the local Ethernet ports are not connected, packets are dropped at the internal switch.

2716 Feature Request: Context option for Backup/Restore.

2717 Loss of management upon asymmetric IPG configuration.

2721 HAAM modem block error event occurred during hard failure condition with dual modem configuration.

2725 IPL CRC not correctly displayed.

2727 Unexpected spontaneous reset post reset-system (1 occurrence only during entire PV duration).

2730 Feature Request: Full LAG implementation.

2731 BCM sw improvement: binary sem and counter thread

2732 Feature Request: CLI "get SNR threshold" to return SNR of both ports



Issue: 1.0




DragonWave Inc.

1791 1 SSH Session avaialble in first release.

1985 SNMP up-time in traps not accurate.

2085 SNMPv3 Castle Rock auto-detection of engine ID not functioning.

2102 Radius authentication not possible with web.

2116 SNMP Simpletest result: SNMP client returning most of the error messages were NOT matched with standard error messages.

2196 Web and SNMP: Do not display the CLI "system alarm" consistently

2254 “get ecfm running config” cli command returns with 10 extra lines (10 extra CR) before prompt if there were NO ecfm configured

2379 64byte counter SNMP mib variable not accessible through V1

2392 Equalizer Stress alarm not being raised.

2397 NewDesign time sleep() needs to be reviewed.

2418 Web server allows login after system reset without re-authenticating.

2500 Web: Switch radio link available in Algorithm based redundancy.

2510 Too many file descriptors opened for /dev/etfs1.

2558 Need to validate IP address syntax entered from CLI.

2564 Reset system recovery (post new-omni upgrade) takes 4min (instead of 2min).

2600 Non ASCII characters cause NAK response in CLI.

2627 Frequency File: Need more info for each bank: User will not know what version will be used on switch bank.

2636 Frequency File: need more rigorous checking of file prior to writing to flash.

2702 CLI: Confusing response when not applying settings to system. (Ex. “set network management interface” then reply “n” to Apply confirmation.)



Issue: 1.0




DragonWave Inc.

2703 https "invalid certificate" warnings in MSIE, Safari & Chrome browsers.

2705 LED activity indicator is not working when the port is configured to 100BaseT.

1931 Transmit power can be set more than the limit for currently running system mode upon system mode change and before reset system applied for new system mode to actually take effect.

2246 Feature Request: Consolidate alarms for system configuration mismatch.

2332 mdix enet config: the status shows normal for xover cable

2339 SNMP RLS status shows wrong configuration information

2448 Momentarily Traffic is dropped upon lag configuration during incremental MAC address

2449 Occasional longer traffic switch outage during lag configuration

2509 Web: Clean up some pages which extend beyond Quantum banner width.

2544 For dual modem / dual radio configuration and upon RF or IF loopback the far end Radio transmitter state not disabled.

2653 RLS port status remains “down” after removing the port from RLS port group.

2680 RLS & ATPC should be blocked. Combined operation is not supported in Rel 1.0.

2706 LED indicator takes longer time (~1min) to change the status when 100baseT

This release supersedes 1.02.06

Upgrade Rules REL 1.03.00 If upgrading from Release 1.02.00 or lower, need to upgrade both ends at the same time. If upgrading from Release 1.02.05 or 1.02.06 and HAAM is enabled, need to upgrade both ends at the same time or need to disable HAAM before activating the upgrade. In all cases, need to upgrade the frequency file to version 2.12.0 or higher at the same time as the omni upgrade.



Issue: 1.0




DragonWave Inc.

REL 1.02.06 If upgrading from Release 1.02.00 or lower, need to upgrade both ends at the same time. Need to upgrade the frequency file to version 2.6.0 or higher at the same time as the omni upgrade.

REL 1.02.05 Need to upgrade both ends at the same time. Need to upgrade the frequency file to version 2.6.0 at the same time as the omni upgrade.

REL 1.02.00 Need to upgrade both ends at the same time.

REL 1.01.05.xx Supported operation is application omni REL 1.01.05.xx with Quantum frequency file release 1.00.15 or higher. As per upgrade procedure, user can upgrade to both the new frequency file and new application omni with only one system reset required.

REL 1.01.00 Supported operation is application omni REL 1.01.00 with Quantum frequency file release 1.00.04 or higher. As per upgrade procedure, user can upgrade to both the new frequency file and new application omni with only one system reset required.

REL 1.00.01 Supported operation is application omni REL 1.00.01 with Quantum frequency file release 1.00.04 or higher. As per upgrade procedure, user can upgrade to both the new frequency file and new application omni with only one system reset required.

Downgrade Rules A downgrade from one omni release to a lower omni release could lead to an incompatible or invalid configuration and mib/database situation resulting in undesirable behavior. A downgrade should be followed by deleting all relevant mibs and re-entering all configuration parameters.

Backwards Compatibility 1. Release 1.03.00 is not backwards compatible with any previous releases if HAAM is enabled.



Issue: 1.0




DragonWave Inc.

2. Frequency files 2.12.00 and higher are required for use with Quantum omni release 1.03.00.

3. Release 1.02.05/1.02.06 is not backwards compatible with any previous releases due to changes in over-air protocol. Both ends of the link must be running Rls 1.02.05/1.02.06 for traffic to flow.

4. Frequency files 2.xx.00 and higher are required for use with Quantum omni release 1.02.05/1.02.06

5. Release 1.02.00 is not backwards compatible with any previous releases due to changes in over-air protocol. Both ends of the link must be running Rls 1.02.00 for traffic to flow.

6. Frequency files 1.00.14 and earlier are not recommended for use with Quantum omni release 1.01.05.xx. Supported operation is Quantum omni release 1.01.05.xx with Frequency file version 1.00.15 or higher. Frequency file version 1.00.15 is required for changes to ATPC algorithm.

7. Frequency files 1.00.03 and earlier are not recommended for use with Quantum omni release 1.01.00. Supported operation is Quantum omni release 1.01.00 with Frequency file version 1.00.04 or higher.

8. Frequency files 1.00.03 and earlier will operate with Quantum omni release 1.00.01 but are not recommended. Supported operation is Quantum omni release 1.00.01 with Frequency file version 1.00.04 or higher.

9. Frequency file releases 1.00.04 & higher are not recommended for use with Quantum omni release 1.00.00.

Major differences in this

version

REL 1.03.00

1. New application omni and fpga image.

2. New frequency file.

REL 1.02.06

New application omni

REL 1.02.05

3. New application ipl, eipl, omni and fpga image.

4. New frequency file.

REL 1.02.00

5. New application ipl, eipl, omni and fpga image.

REL 1.01.05.01



Issue: 1.0




DragonWave Inc.

1. New application omni.

REL 1.01.05

1. New application omni, frequency file, and fpga image.

REL 1.01.00

6. New application omni and fpga image.

REL 1.00.01

1. New application omni, frequency file, and fpga image.

Minor features None

PTS/Bug fixes REL 1.03.00 List of bug fixes included:


5194 BAC record sometimes shows default time stamp of 01/01/1970 00:00:00 for its uncompressed ratio.

5192 Bandwidth Doubling: Incorrect MAC address displayed in partner information table.

5180 ATPC wrongly toggling max/min power when auto-disabled at coordinated power.

5177 Occasional loss of modsync in IF loopback for 50MHz & 56 MHz 256 QAM modes.

5171 IF loopback: failure to recover from loopback with R4 radios.

5170 IPG configuration not retained after upgrade from 1.1.0 to 1.2.6. Fixed for direct upgrades to 1.3.0.

5169 Software licenses not retained after upgrade from 1.1.0 to 1.2.6. Fixed for direct upgrades to 1.3.0.

5166 HAAM switching at a steady-state with 56 MHz 256 QAM (hx56_379_256qam).

5165 Loss of modsync txL-Slave wrongly discovering txH-Master after resest system multi-carrier XPIC. (rare)

5158 HAAM not recovering after deep attenuation removed (rare).



Issue: 1.0




DragonWave Inc.

5157 VLAN config modification not prompting for save of l2swmib.

5156 ATPC not functioning with R4 radios with multi-carrier XPIC.

5127 R4 radio multi carrier XPIC slave not showing RSL in cli/snp/web.

5126 Set haam mode range while haam is currently disabled causes raise/clear loss of modsync.

5124 Attempt to set haam on/off via web causes raise/clear loss of modsync.

5123 Radio power off alarm shows no such index for SNMP wp2 multi-carrier XPIC.

5119 ATPC target RSL vs sensitivity for some 23G modes differ by 11 instead of 15 dB.

5118 ATPC targets vs sensitivity for 6G modes hx10_43m1_64qam and hx10_63m1_256qam differ by 23 dB.

5117 Radio bands for 6GU are missing the qpsk test mode required for radio loopback.

5115 Occasional non recovery from reset system ATPC on multi-carrier XPIC.

5101 Multi-carrier XPIC HAAM switching events and/or dribbling errors after some reacquisitions with -20 XPI present.

5100 Multi-carrier XPIC with haam not recovering with mid-high-mid XPI fade.

5084 Radio loopback for wp2 in system capacity 2 shows on for both wp1 and wp2.

5023 FrameQ code check or length error results in data path crash - RARE.

4537 Web error msg not meaningful for unsuccessful save mib due to radio band & system mode configuration mismatch.

3733 Log entries for SNMP set cos flow has unknown.

3723 False log message - An unexpected condition occurred (1)

REL 1.02.06

List of bug fixes included:



Issue: 1.0




DragonWave Inc.


5122 Radio loss of comms alarm not incrementing counter for slave units with multi-carrier XPIC.

5128 R4 radio with multi-carrier XPIC, slave unit not detecting radio loss of comms.

5129 R4 radio with multi-carrier XPIC not maintaining max transmit power upon reset.

REL 1.02.05 List of bug fixes included:


2658 SNMP manager config needs several attempts (post delete mib).

2672 Message for ATPC attempt with haam enabled needs improving.

2680 RLS and ATPC should be blocked.

2862 Haam always at max tx power even if power previously reduced.

2941 Need better error message for attempting to enable ATPC with HAAM.

3177 IF loopback requires local radio transmitter to be muted.

3223 IF loopback does not function (30M modes and lower).

4132 Alarm: Radio Drain Current alarm SNMP Trap flooding

4157 BW_X2: "get diagnostics" cli command returns as "Diagnostics are not available"

4191 SNTP Server first 2 default servers may be no longer in service

4305 Unable to set partner MAC address & communication port in Web, SNMP for Bandwidth Doubling.

4393 ATPC should be blocked while X2(bandwidth doubling) enabled

4394 Should have a proper error message when enabling ATPC while HAAM is enabled to reflect that feature combination is blocked by software.



Issue: 1.0




DragonWave Inc.

4395 BWx2: Web Bandwidth Doubling Port Configuration displays "none"

4405 BWx2: System Summary Alarms shows no with BWx2 alarm active

4417 Ingress traffic dropped at switch if swap source/destination MAC.

4420 Continuous frame error counter increments with no data traffic present after momentarily loss of sync.

4425 BWx2: l2swmib changed flag is set when BWx2 link boots up even if no changes to switch configuration.

4426 BWx2: Port configuration dropdown list always initialized to "none"

4429 BWx2: network management not blocking dp4 when bandwidth doubling is enabled and dp4 is already configured as part of the bandwidth doubling port.

4431 BWx2: delete l2swmib only will block configuration of previously set bandwidth doubling port despite no longer actually configured as that port.

4432 l2swmib not restored with "copy ftp: config" command following "delete l2swmib both"

4433 Provisioning data for iqdcoffset overwritten with copy config (restore process).

4435 Command for “get system capacity” is NOC level.

4436 Switch related configuration changes (l2swmib changes) are not saved automatically during a “save config ftp:” command. Must issue “save l2swmib” command before “save config ftp:”.

4439 QoS (Strict): with system speed > air capacity, queue CIRs totaling more than system speed and BAC enabled on higher priority queues but not on lower priority queues, it is possible that a high traffic load on a lower priority queue will be serviced ahead of the higher priority queue. Extreme cases can result in the traffic in the higher priority (bac enabled) queue being dropped. Workaround is to provision a CIR for the lower priority queue such that it limits its ability to take bandwidth from the higher priority queues.

4449 System capacity 4 (single modem redundancy) and System capacity 3 (dual modem-dual radio) when one channel loses mod sync a zero egress condition



Issue: 1.0




DragonWave Inc.

can occur (RARE).

4484 When configuring a Quantum link for “VLAN trunking” and “in-band management”, it is possible to lose over-the-air management with the far end Quantum unit.

4640 ATPC threshold not always 15 dB away from sensitivity for some 14, 28, 56 MHz modes.

4911 TCP/IP stack timer problem. If using l2switchFeature, this problem can result in loss of access to L2SW shell.

5046 ECFM stopped functioning after reconfiguring management.



Fixed previous limitation of maximum input data rate for bac feature capped at 1.5 Gbps.

2646 Unexpected lower egress rates with bac Q1-3 and with QoS/WFQ policy under some traffic scenarios.

3705 hz50_371_256qam, R5 radio wrong Maximum ATPC attenuation

4377 RADIUS Authentication results in all users getting Admin privileges.

2673 Added Merlin like "diagnostics" command.

2765 WFQ with bac and PRBS data-fill shows less than expected egress.

2997 Add actual Tx power being recorded in the performance logs

3050 WFQ BW allocation with expedite not always as expected.

3228 QoS (WFQ with EXP off): bandwidth distributions between queues not always achieving expected values when over-air speed < system speed.

3725 Cannot cancel the PLCM interactive command process.



Issue: 1.0




DragonWave Inc.

3727 PLCM: Configuring through CLI interface doesn't work correctly (l2swmib is not saved).

3772 Quantum unit could become unresponsive after reset following FTP omni upgrade (RARE).

3830 Tx power inaccuracy difference for wider channel bandwidths due to tx baseband filter roll-off.

3834 Within L2SW prompt, “set network management interface” command does not work with partial entries. Must include all parameter settings. For example, if port list settings are not included in the command, the management port list will be set to none and therefore no remote management will be available.

REL 1.01.05.01 List of bug fixes included:


3118 Version of IPL should read 1.0.0 and not 1.1.0

3738 Permanent loss of management with large quantity of VLAN IDs and license 6 l2switchFeature is not licensed. Recovery method is to remove and insert the Ethernet management cable. Then reduce quantity of VLANs provisioned and save l2swmib. NOTE: Configuring up to 1500 VLANs is maximum working range with license 6 l2switchFeature not licensed.

3756 ECFM with RSTP: CFM packets are bypassing the RSTP blocking port when they should not.

3763 ECFM: End point (MEP) will not reply to a trace-route request if a MIP is defined at the receiving port.

3764 ECFM: before performing a link trace the user needs to clear CCM-database on all nodes. *Fixed in REL 1.1.5.1 only with RSTP or MSTP enabled. NOTES:

With RSTP/MSTP and RLS enabled, an ECFM link trace will only reach the previous node when the wireless link goes down because the RLS will bring



Issue: 1.0




DragonWave Inc.

the dp port down and RSTP/MSTP will then trigger the clearing of the CCM database on that node.

If RSTP/MSTP is not enabled and the ECFM configuration changes the user still needs to clear the CCM-database.

3765 ECFM limitation to a maximum of 4 ECFM hops in the link trace path.

3766 ECFM mib not properly saved or restored with some configurations (ex. MEP & MIP configured with same level but different ports.)



2441 Bandwidth logging percentage calculation capped at 100%. With bac it is valid to exceed 100%. NOTE: After upgrade to REL 1.1.5, percentage calculation of existing records will show >100% if raw data reflects such utilization.

2804 Tool-tip pop-up dialog for tx power via web not complete.

2843 SNMP file Horizon-MIB_1.0.0.mib as released does not contain Quantum. NOTE: Fixed in Horizon_MIB_1.02.00.mib file.

2902 Set tx power with ATPC on adds 20dB attenuation first to handle running close to saturation case.

2903 Need to apply work-around of re-enabling of ATPC upon band/mode/capacity change.

2926 Omni too large with L2SW: FTP Download must download in slices

2927 ATPC saturation algorithm fails in HP link (R4 radios)

2958 Customer must ensure that the FTP server remains up during an omni upgrade. In rare instances, the Quantum application software may terminate, requiring the customer to power cycle the unit.

3011 Frequency File 128 band limit must be raised.



Issue: 1.0




DragonWave Inc.

3308 Failed to commit/FTP into the backup bank.

3039 Occasional low SNR in qam32 modes with XPIC on following reset system

3325 HAAM system modes do not update correctly between frequency files.

3462 Commit failure when mismatched radio is connected.

REL 1.01.00



2744 User Manual: Need clear description for sw commit, freq file etc.

2913 SSH re-connect (dropped from client SSH re-key option) halts management.

2915 Network management command needed post default priority config.

2916 Command for port default priority config not retained post reset.

2948 Corrupted Flash when power removed during omni upgrade

2949 Cable Loss Calculation Error/Cable loss not accurate for Quantum/R5 radios with low T/R spacing (ex. 13 GHz, 6 GHz)

2955 EEPROM continuously being written: limited lifespan of device in field

2981 Re-entry of the cpu mac address to the switch with different vlan packets are dropped

REL 1.00.01



2813 Modem configuration failure with override settings in contingency modem register fields within R5 radio bands

2824 Insufficient RF power with Duo (R4) radios



Issue: 1.0




DragonWave Inc.

2720 HAAM with 30M config showing no HAAM modes – no modsync.

2839 HAAM with dual-dual and 28 MHz channels is unstable

2767 BW Utilization performance logs affected by changing system speed, log interval or losing mod-sync

N/A Inconsistent modem acquisition for narrow band (30 MHz & lower) adjacent channel operation.

N/A Modem acquisition not recovering reliably after a Rx saturation event.

N/A Redundancy fix for narrow bandwidth channel operation.

2727 Unexpected spontaneous reset post user reset-system.

N/A System crash when user enters “reset” without including parameter

N/A Modem not recovering occasionally when leaving meter mode in Redundancy

2792 ATPC not adjusting transmit power after initial enabling of ATPC feature since maximum ATPC attenuation not updated.

2914 Modification of the initially configured port VLAN settings (both the VLAN default ID and VLAN range) can cause the internal Ethernet switch to crash.

REL 1.00.00

Not applicable.

sw release notes - comark telecom rel 1 03 00... · an encrypted enabled fpga device ... 9....

Documents