Ceragon Manual

FibeAir® IP-10G and IP-10E
6.9 Release Notes

November 2012
Hardware Release: R2 & R3
Software Release: i6.9.2
Document Revision 1.3
Copyright © 2012 by Ceragon Networks Ltd. All rights reserved.

®
FibeAir IP-10G and IP-10E 6.9 Release Notes
Contents
Contents ................................................................................................................. 2
1. Introduction ...................................................................................................... 4
1.1 IP-10 Introduction ........................................................................................................... 4
1.2 6.9.2 Version Introduction .............................................................................................. 4
1.3 Project Release History.................................................................................................. 6
1.4 Synonyms and Acronyms .............................................................................................. 6
2. Supported Systems and Configurations......................................................... 8

2.1 Supported Radio Configurations .................................................................................... 8
2.2 Supported Configurations ............................................................................................ 13
3. Software and Hardware Configurations and Compatibility ......................... 14

3.1 Supported Hardware Configurations ............................................................................ 14
3.2 Supported Licensing Configurations ............................................................................ 14
3.3 IDU-ODU/RFU Compatibility ........................................................................................ 15
3.4 Hardware-Software Compatibility in a Link .................................................................. 15
3.5 Software Compatibility in a Nodal Configuration ......................................................... 16
3.6 HW-SW Compatibility Limitations ................................................................................ 16
3.7 Configuration File Compatibility ................................................................................... 16
3.8 PolyView Version Compatibility ................................................................................... 16
4. NSV Content ................................................................................................... 17

5. New Features .................................................................................................. 19
6. Features with Limited Support ...................................................................... 20
7. Modified Features ........................................................................................... 22
8. Notes and Limitations .................................................................................... 23
9. Corrected Bugs............................................................................................... 38
10. Open Bugs ...................................................................................................... 39
Ceragon Proprietary and Confidential Page 2 of 56

®
Notice
This document contains information that is proprietary to Ceragon Networks Ltd. No part of this
publication may be reproduced, modified, or distributed without prior written authorization of
Ceragon Networks Ltd. This document is provided as is, without warranty of any kind.
Registered Trademarks
Ceragon Networks® is a registered trademark of Ceragon Networks Ltd. FibeAir® is a registered
trademark of Ceragon Networks Ltd. CeraView® is a registered trademark of Ceragon Networks
Ltd. Other names mentioned in this publication are owned by their respective holders.
Trademarks
CeraMap™, ConfigAir™, PolyView™, EncryptAir™, and CeraMon™ are trademarks of Ceragon
Networks Ltd. Other names mentioned in this publication are owned by their respective holders.
Statement of Conditions
The information contained in this document is subject to change without notice. Ceragon
Networks Ltd. shall not be liable for errors contained herein or for incidental or consequential
damage in connection with the furnishing, performance, or use of this document or equipment
supplied with it.
Open Source Statement

The Product may use open source software, among them O/S software released under the GPL or
GPL alike license ("GPL License"). Inasmuch that such software is being used, it is released under
the GPL License, accordingly. Some software might have changed. The complete list of the
software being used in this product including their respective license and the aforementioned
public available changes is accessible on http://www.gnu.org/licenses/.
Information to User
Any changes or modifications of equipment not expressly approved by the manufacturer could
void the user’s authority to operate the equipment and the warranty for such equipment.
Revision History
Rev Date Editor Description
1.0 23/9/2012 Alex Yufit Primary document.
Describes the IP-10G I6.9.2 Release
1.1 1.11.2012 Alex Yufit Updated release version numbers
1.2 8.11.2012 Erez Aviv Final review
1.3 11.11.2012 Alex Yufit Updated corrected bugs

®
1. Introduction
1.1 IP-10 Introduction

This New Software Version (NSV) release introduces the eighth release of the
IP-10 series, Ceragon's High Capacity Wireless Network Solution for IP
networks.
This release includes new software, meant to provide additional capabilities.
FibeAir IP-10G is Ceragon’s next generation carrier-grade wireless Ethernet
backhaul product. Combining advanced TDM and Ethernet networking,
FibeAir IP-10G facilitates cost effective, risk-free migration to IP and can be
integrated in any TDM, hybrid or pure IP/Ethernet network. This versatile
solution supports the entire licensed spectrum – from 6GHz up to 38GHz – and
offers a wide capacity range of 10Mbps - 500Mbps along with enhanced
Adaptive Coding & Modulation for maximum spectral efficiency in any
deployment scenario. With FibeAir IP-10G, Ceragon offers risk-free migration
with the highest possible capacities at the lowest overall cost.
FibeAir IP-10E is an Ethernet-only wireless Ethernet backhaul product
providing the same capacity and feature set as the IP-10G without TDM
functionality.
FibeAir IP-10G and IP-10E feature a powerful, integrated Ethernet switch for
advanced networking solutions. IP-10G also features an optional TDM cross-
connect for nodal site applications. With advanced service management and
Operation Administration & Maintenance (OAM) tools, this first-of-its-kind
solution simplifies network design, reduces CAPEX and OPEX and improves
over-all network availability and reliability to support services with stringent
SLA.
FibeAir IP-10G and IP-10E cover the entire licensed frequency spectrum and
offer a wide capacity range, from 10Mbps to 500Mbps over a single radio
carrier, using a single RF unit. The solution easily serves the capacity
requirements of a single base-station as well as those of traffic-intensive hub
sites, and leaves ample headroom for future capacity enhancements.
Additional functionality and capacity are enabled via software upgradable
licenses while using the same hardware.
FibeAir IP-10G and IP-10E employ the most advanced available Adaptive
Coding & Modulation (ACM) technique. This unique feature enables users to
maximize spectrum utilization and capacity over any given bandwidth and
changing environmental conditions.
1.2 6.9.2 Version Introduction

This release includes new software (referred as version I6.9.2 in this
document) that is meant to run in IP-10G and IP-10E hardware only.
Attempting to install this software version in previous IP-10 hardware
releases may make the system inoperative, requiring the hardware to be sent
to the manufacturer for replacement.
In addition, note that IP-10G and IP-10E systems with software version 3.0.34
(an earlier version loaded in production for some systems) must be upgraded

®
to an officially released version while in standalone mode rather than in a

nodal configuration.
This software release introduces enhancements to the following features:
Frequency diversity is now available also with ACM adaptive mode.
This kind of configuration allows exploiting the advantages of both ACM and
Frequency diversity features.
It will minimize the probability of outage and will maximize link availability.
Revertive HSB protection mode allows maximization of link radio budget
resources to ensure that primary path with higher gain will be used on both
sides of the link whenever possible.
SNMP IP forwarding feature provides SNMP access to NE stacked in a shelf by
using separate IP address for each NE rather than using a community string.
This feature is mostly relevant to users who have a 3rd party NMS server
which is not capable of SNMP addressing by community string.

®
1.3 Project Release History

The following table shows the IP-10G product line release history:
# NSV SW Version & Date Main Features Notes

Package
1 3.0.97 Sept 2009 IP-10G product release I6.5ca1 + nodal solution
2 3.0.99 Oct 2009 Improved wander, Longer system name, Patch version
management frames marking
3 6.6.0.0.1.40 Jan 2010 IP -10G product release I6.6ca1
4 6.6.0.0.1.41 Jan 2010 New version for backwards compatibility with Patch version
3.0.99
5 6.6.0.0.2.51 March 2010 IP -10G product release I6.6GA E1s only
6 6.6.0.0.2.53 March 2010 IP -10G product release I6.6GA
7 6.6.1.0.0.71 August 2010 IP -10G product release I6.6.1
8 6.6.1.0.0.22 October 2010 IP -10G product release I6.6.2
9 6.7.0.0.0.93 February 2011 IP -10G product release I6.7
10 6.7.1.0.0.4 April 2011 IP -10G product release I6.7.1 Scripts only
11 6.7.2.0.0.3 June 2011 IP -10G product release I6.7.2 NeraTel support

and bugs only
12 6.8.0.0.0.58 October 2011 IP -10G product release I6.8
13 6.9.0.1.0.41 May 2012 IP-10G product release I6.9
14 6.9.0.1.0.42 August 2012 IP-10G product release I6.9 Correction of FCS

errors on GbE
electrical ports
15 6.9.2.0.0.14 November 2012 HSB revertive mode, SNMP IP forwarding,

Frequency diversity with ACM
1.4 Synonyms and Acronyms
AIS Alarm Indication Signal

ACM Adaptive Coding and Modulation
AES Advanced Encryption Standard
BER Bit Error Rate
BPDU Bridge Protocol Data Unit
CA Certificate Authority
CFM Connectivity Fault Management (Protocol)
CN Customer Network (Port)

®
DST Daylight Saving Time

EFM Ethernet in the First Mile (Protocol)
EOW Engineering Order Wire
EXC BER Excessive BER
FD Frequency Diversity
FE Fast Ethernet
FTP (SFTP) File Transfer Protocol (Secured File Transfer Protocol)
GbE / GBE Gigabit Ethernet
GMT Greenwich mean time
IDC Indoor Controller
IFG / IPG Inter Frame/Packet Gap
HTTP (HTTPS) Hypertext Transfer Protocol (Secured HTTP)
LAG Link Aggregation Group
LOC Loss Of Carrier
LOF Loss Of Frame
LOS Loss Of Signal
LTM Link-Trace Message (CFM)
LTR Link-Trace Response (CFM)
MA Maintenance Association (CFM)
MAC (Ethernet) Media Access Control
MAC (Security) Message Authentication Code
MAID Maintenance Association (MA) Identifier (ID)
MEP Maintenance End Point (CFM)
MHC MAC Header Compression
MIB Management Information Base
MIP Management Intermediate Point (CFM)
MSE Minimum Square Error
NTP Network Time Protocol
NSV New Software Version
OAM Operation Administration & Maintenance (Protocols)
PIRL Port Ingress Rate Limiting
PM Performance Monitoring
PN Provider Network (Port)
PV PolyView
QoS Quality of Service

®
RSL Received Signal Level

SD Space Diversity
S/N Serial Number
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
STP / xSTP Spanning Tree Protocol
SSH Secured Shell (Protocol)
UC User Channel
UTC Universal Time Coordinated
WSC Wayside Channel
XPIC Cross Polarization Interference Cancellation
2. Supported Systems and Configurations
2.1 Supported Radio Configurations

The following table lists supported system MRMC (Multi-Rate-Multi-
Constellation) configurations (determined by modem configuration scripts):
# Modem Script Bit Rate Channel Spacing Modulation ETSI/FCC

[Mbps] ETSI/FCC
(Occupied BW)
[MHz]
1. 10Mbps-3.2MHz 10 3.5 (3.2) 16QAM ETSI
(1035)
2. 10Mbps-6.5MHz 10 7 (6.5) QPSK ETSI
(0107)
3. 15Mbps-3.2MHz 15 3.5 (3.2) 64QAM ETSI
(1535)
4. 20Mbps-6.5MHz 20 7 (6.5) 16QAM ETSI
(0207)
5. 39Mbps-6.5MHz 39 7 (6.5) 256QAM ETSI
(0407)
6. 39Mbps-26MHz 38 28 (26) QPSK ETSI
(0428)
7. 47Mbps-9MHz 47 10 (9) 64QAM FCC
(4410)

®

[Mbps] ETSI/FCC
(Occupied BW)
[MHz]
8. 155Mbps-26MHz 155 28 (26) 128QAM ETSI
(1528)
9. XPIC-155Mbps- 155 28 (26) 128QAM ETSI
26MHz
(XPIC-1528)
26.6MHz
(XPIC-1828)
11. 181Mbps-26MHz 181 28 (26) 256QAM ETSI
(1828)
12. XPIC-198Mbps- 198 30 (29) 256QAM FCC
26MHz
(XPIC-2030)
13. XPIC-260Mbps- 260 40 (36.2) 256QAM ETSI/FCC
36.2MHz
(XPIC-2636)
14. XPIC-337Mbps- 337 50 (46.8) 256QAM FCC
46.8MHz
(XPIC-3346)
15. 350Mbps-48MHz 350 50 (48) 256QAM FCC
(3548)
52MHz
(XPIC-3656)
17. ACM-40Mbps-6.5MHz 10 – 40 7 (6.5) QPSK – 256QAM ETSI
(ACM-7M) (1)
18. ACM-42Mbps-6.5MHz 10 – 42 7 (6.5) QPSK – 256QAM ETSI

(ACM-7M) (1)
19. ACM-59Mbps-9MHz 13 - 59 10 (9) QPSK – 256QAM FCC

(ACM-10M) (2)

(ACM-10M) (2)
21. ACM-87Mbps- 21 – 87 14 (12.5) QPSK – 256QAM ETSI

12.5MHz
(ACM-14M) (3)

®

[Mbps] ETSI/FCC
(Occupied BW)
[MHz]
22. ACM-87Mbps- 21 – 87 14 (13) QPSK – 256QAM ETSI
12.5MHz
(ACM-14M) (3)
23. ACM-124Mbps-18MHz 27– 124 20 (18) QPSK – 256QAM FCC

(ACM-20M)
24. ACM-181Mbps-26MHz 38 - 181 28/30 (26) QPSK – 256QAM ETSI/FCC
(ACM-28M) (4)
25. ACM-181Mbps- 38 - 181 28/30 (26.5) QPSK – 256QAM ETSI/FCC

26.5MHz
(ACM-28M) (6)(*)

(ACM-28M) (4)

(ACM-28M) (4)
28. ACM-198Mbps-28MHz 39- 198 30 (28) QPSK – 256QAM FCC

(ACM-30M)
29. ACM-255Mbps-36MHz 55- 255 40 (36) QPSK – 256QAM ETSI/FCC
(ACM-40M)
(ACM-50M)
31. ACM-367Mbps-52MHz 76 – 367 56 (52) QPSK – 256QAM ETSI/FCC
(ACM-56M)
32. ACM-367Mbps- 76 – 367 56 (52.5) QPSK – 256QAM ETSI/FCC
52.5MHz
(ACM-56M) (6)(*)
33. XPIC-ACM-180Mbsp- 40-180 28/30 (26.6) QPSK – 256QAM ETSI/FCC

26.6MHz
(XPIC-ACM-28M)
34. XPIC-ACM-181Mbsp- 40-181 28/30 (26.5) QPSK – 256QAM ETSI/FCC
26.5MHz
(XPIC-ACM-28M) (6)(*)
35. XPIC-ACM-192Mbps- 43-192 30 (29) QPSK-256QAM FCC
29MHz (7) (*)
36. XPIC-ACM-259Mbps- 55 - 259 40 (36.2) QPSK – 256QAM ETSI/FCC
36.2MHz
(XPIC-ACM-40M)

®

[Mbps] ETSI/FCC
(Occupied BW)
[MHz]
37. XPIC-ACM-367Mbps- 76 - 367 56 (52) QPSK – 256QAM ETSI/FCC
52MHz
(XPIC-ACM-56M)
38. XPIC-ACM-367Mbps- 76 - 367 56 (52.5) QPSK – 256QAM ETSI/FCC
52.5MHz
(XPIC-ACM-56M) (6)(*)
39. Asymmetric downlink(5) TX = 132 28MHz 256QAM ETSI
TX = 21M, RX=7M RX = 42
40. Asymmetric uplink (5) TX = 42 28MHz 256QAM ETSI
TX = 7M, RX=21M RX =132
41. Asymmetric downlink(5) TX=270 56MHz 256QAM ETSI
TX = 42M, RX=14M RX=85.5
42. Asymmetric uplink (5) TX=270 56MHz 256QAM ETSI
TX = 14M, RX=42M RX=85.5
* New script
(1) Two ACM-7M scripts appear in the MRMC table.
 The first ACM radio script that appears in line 16 is a low-latency script for
channel spacing of 7MHz. It has a slightly lower throughput than the
second script.
 The second script that appears in line 17 in the table above is the ACM
radio script for channel spacing of 7MHz that was released in previous
IP-10 versions 6.1.x, 6.2.x, for backwards compatibility.
 The first ACM radio script that appears in line 18 is a low-latency script for
channel spacing of 10MHz. It has a slightly lower throughput than the
second script. It was released in version 6.6.2.
 The second script that appears in line 19 in the table above is the ACM
radio script for channel spacing of 10MHz that was released in previous
IP-10 versions 6.1.x, 6.2.x, for backwards compatibility.
 The first script that appears in line 20 in the table above is the ACM radio
script for channel spacing of 14MHz that was released in previous IP-10
versions 6.1.x, 6.2.x, for backwards compatibility.
 The second ACM radio script that appears in line 21 is an enhanced latency
script for channel spacing of 14MHz. It was released in version 6.6.2.
(4) Three ACM-28M scripts appear in the MRMC table.
 The first script that appears in line 23 in the list above is the ACM radio
script for channel spacing of 28MHz that was released in previous IP-10
versions 6.1.x, 6.2.x, for backwards compatibility.

®
 The second ACM radio script that appears in line 24 is an enhanced

capacity and latency script for channel spacing of 28MHz. It was released
in version 6.6.2.
 The third ACM radio script that appears in line 25 provides even higher
capacity and lower latency for channel spacing of 28MHz.
(5) Asymmetrical scripts come in pairs. The downlink script is wide and the
uplink script is narrow. For each downlink script its adjacent uplink script
must be loaded on the remote side.
 Script 34 at the downlink must work with script 35 at the uplink.
 Script 36 at the downlink must work with script 37 at the uplink.
Asymmetrical scripts require a capacity license for the TX side of the link.
The number of TDM trails is determined by the capacity of the uplink (narrow
script).
To avoid loss of management while upgrading the scripts, it is recommended
to upgrade the remote side first.
(6) ACM radio scripts with resistance to ultra-fast channel variations.
(7) This radio script was included in previous releases but it is supported only
from release 6.9.2 and above.
Note: Only some scripts may be available on the system
depending on licensing.

®
2.2 Supported Configurations
# Configuration Supported Notes

[Yes/No]
1. RFU support Yes 1500P/HP/SP, RFU-C
2. 1+0 Yes
3. Nodal configuration Yes
4. 1+1 HSB – External Protection Yes Also in revertive HSB mode
(6.9.2 and above)
5. 1+1 HSB – In nodal configuration Yes
6. 1+1 space diversity (SD) Yes
7. 1+1 frequency diversity (FD) Yes Also with adaptive ACM (6.9.2
and above)
8. 2+0 Multi-Radio Yes
9. 2+0 Multi-Radio with line protection Yes
10. ACM Yes
11. ACM Enhanced capabilities: Yes
 Adaptive TX Power
12. Auxiliary channels (User-Channel, EOW, External Yes
alarms).
13. Switch Applications (Switch modes): Yes
 Single Pipe.
 Managed Switch (802.1Q)
 Metro Switch (802.1AD)
14. Wireless Carrier Ethernet Fast Ring Yes
(RSTP)
15. XPIC Yes
16. 2+2 protected XPIC/Multi-Radio Yes
17. Pseudowire T-card support Yes IP-10G only
18. Yes Requires R3 hardware on both
Multi-Layer header compression
sides of the link

®
3. Software and Hardware Configurations and

Compatibility
3.1 Supported Hardware Configurations

The following IP-10G IDU assembly options are supported:
 IP-10G-Ethernet-only
 IP-10G-16E1-T-card
 IP-10G-16E1-T-card-SyncU-AUX
 IP-10G-16E1-T-card-SyncU-AUX-XPIC ready
 IP-10G-16E1-T-card-SyncU-AUX-XPIC ready-Dual Feed
 IP-10G-16DS1-T-card-SyncU-AUX
 IP-10G-16DS1-T-card-SyncU-AUX-XPIC ready
 IP10G(R3)- 16E1-T-card-SyncU-AUX
 IP10G(R3)- 16E1-T-card-SyncU-AUX-Dual Feed
 IP10G(R3)-16E1-T-card-SyncU-AUX-XPIC ready-Dual Feed
 IP10G(R3)-16DS1-T-card-SyncU-XPIC ready-Dual Feed
 IP10E(R3)-SyncU (Ethernet only)
The following T-cards are supported:
 IP-10-TCard-16E1
 IP-10-TCard-16DS1
 IP-10-TCard-ch-STM-1/OC-3
 IP-10 –PWC T-card
Both terminal and nodal configuration (with up to six IDUs) are supported.
Note: The IP-10E (Ethernet-only) assembly can be inserted into a
node and can carry TDM traffic, but it does not contain TDM
line interfaces or a T-card slot.
3.2 Supported Licensing Configurations

The following features require a special software license:
 ACM (IP-10 IDU SW license: ACM)
 Switch (IP-10 IDU SW license: Managed Switch, Metro Switch)
 Capacity (IP-10 IDU SW license: Capacity x)
 TDM-only capacity (IP-10 IDU SW license: TDM Capacity x)
 Network resiliency (IP-10 IDU SW license: Network resiliency)
 Synchronization Unit license (IP-10 IDU SW license: SyncU license)
 Per-usage license (IP-10 IDU SW license: per-usage license)
 Enhanced QoS license (IP-10 IDU SW license: Enhanced QoS license)
 Asymmetrical Scripts license (IP-10 IDU SW license: Asymmetrical Scripts)
 Multi-Layer Header compression (IP-10 IDU SW license: Enhanced Multi
Layer header compression)
Every IDU is delivered with a basic capacity rate of 10Mbps, and with all other
licenses disabled.

®
Systems with previous software versions which had already been deployed
prior to version 6.6.1, which introduced the new licenses for existing features
(network resiliency), will not be affected upon upgrading to version 6.9.2.
In other words, customers already making use of capabilities that require a
license will be able to continue using these features in their existing systems
without a license upgrade.
3.3 IDU-ODU/RFU Compatibility

The following table shows the compatibility of IP-10G and IP-10E IDUs with
Ceragon ODU/RFU types:
IDU ODU/RFU
FibeAir 1500P 1500HP 1500SP RFU-HS 1500SP Wide RFU-C RFU-A RFU-HP
IP-10G and No Yes Yes** Yes** Yes** Yes*** Yes Yes Yes
IP-10E
Notes:
 The compatibility table refers to RFUs connected to IDUs loaded with this
release.
 MRMCs (radio scripts) on both sides of the link need to have the same
“Grade”.
 (**) 1500HP, 1500SP and RFU-HS support scripts up to 30.5MHz occupied
bandwidth.
 (***) 1500SP Wide supports scripts with occupied bandwidth (24MHz ≤
BW ≤ 56MHz).
 All RFU software versions are supported unless stated otherwise.
3.4 Hardware-Software Compatibility in a Link
3.4.1 RFU-C compatibility for 256QAM

 Operation with RFU-C using 256QAM modulation scripts depends on the
RFU-C hardware version, and some limitations may apply. Contact Ceragon
support for further details and RFU-C upgrade instructions.
 ACM-56MHz: If you are using this script with an RFU-C, the RFU must be
running version 1.97 or higher for proper functionality of the script.
3.4.2 RFU-C Compatibility with Adaptive TX Power

 RFU-C must be running version 2.01 or higher for proper functioning of
the Adaptive TX Power feature. If a lower RFU-C software version is being
used, this feature should be disabled.
3.4.3 IDU Compatibility in a Link

 An IP-10G or IP-10E IDU should only be used with another IP-10G or IP-
10E IDU across the link.
 IP-10G and IP-10E are not compatible with 1500P IP-MAX/IP-MAX2 IDUs.

®
 IP-10G and IP-10E with software version i6.9.2 are not compatible with IP-
10 (old hardware version).
 IP-10G and IP-10E with software version I6.9.2 are not compatible with an
IP-10G running software version I6.5ca1
3.4.4 IP-10 Software Release Compatibility for Upgrade, Downgrade,

and Configuration
 IP-10G and IP-10E IDU software release I6.9.2 is compatible with other IP-
10G supported software releases (I6.5ca1, I6.6ca1, I6.6ga, I6.6.1, I6.6.2,
I6.7, I6.7.1, I6.7.2, I6.8, I6.9).
 IP-10G and IP-10E software release I6.9.2 is not compatible with IP-10
releases I6.2, I6.1, I6.1.1, and I6.0.
3.4.5 ODU/RFU Compatibility in a Link

 ODU/RFU compatibility in a link depends on the ODU/RFU’s software
release.
3.5 Software Compatibility in a Nodal Configuration

All IP-10 IDUs in a node should have the same software version. An alarm will
be raised if this is not the case.
3.6 HW-SW Compatibility Limitations

 Release I6.9.2 can be installed only in IP-10G and IP10-E IDUs.
 Previous IP-10 hardware versions cannot be upgraded to software version
I6.9.2.
Attempting to install software version I6.9.2 in the wrong hardware
may render the unit unusable.
 IP-10G and IP-10E IDUs with hardware release 3 (R3) can only use
software versions I6.7 and later.
In standalone IDUs and main IDUs in a nodal enclosure, this is actively
enforced.
It is technically possible to downgrade hardware release 3 extension
units in a nodal enclosure with a software version earlier than I6.7.
Doing so will render the unit unusable.
3.7 Configuration File Compatibility

Version I6.9.2 supports configuration files created from version I6.6ga
onwards. Configuration files from earlier versions are not supported.
3.8 PolyView Version Compatibility

 Network Element release I6.9.2 is supported by PolyView version
N6.9.0.1.0

®
4. NSV Content
The IP-10 IDU software is released as a zipped RPM package (RPM, Red Hat
Package Manager, is the software package file format in Linux).
ODU/RFU versions are packaged separately from the IDU RPM.
The NSV package includes the following components:
Package Name Version

Aidu 6.9.2.0.0.14
aidu-idc 6.9.2.0.0.14
aidu-management 6.9.2.4
aidu-modem-fw 3.40.2
aidu-fpga-fw 50.6.38
XC Main Board FW 4.13
R3 XC Main Board FW 2.38
STM-1 Daughter Board FW 1.117
E1T1 Daughter Board FW 3.2
PWC Daughter Board FW 4.0
pwc 0.28
aidu-mrmc-scripts 7.17
L2protocols 7.5.1.aidc.t183.6.9.0.13
Kernel 2.6.14.7-aidc.3.17
kernel-modules 0.3.16-2.6.14.7_aidc.3.17
aidu-setup 6.9.0.14
aidu-atp 3.3.10
Autoupd 5.5.5
Lighttpd 1.5.0.a
Net-snmp 5.3.2.3-7a
Openssh 4.3p2-3a
nfs-utils 1.0.8.rc2-4.FC5.2_WR
Pam 0.99.4.0-5_1a
Pam_passwdqc 1.0.2-owl1
Perl-Net-SFTP-Foreign 0.1.44-1.pne1.5
Portmap 5
shadow-utils 4.0.14-1.2_WR
Iptables 1.3.4
Redblack 1.3-2

®
MIB versions:
Network MIB 1.0.0.3
PM MIB 1.0.0.2
Radio MIB 1.0.0.3
Unit MIB 1.0.0.8

®
5. New Features
The new features are relative to the previous version, IP-10 version I6.9.1
# Feature Description/Notes
Up to I6.9.1 release Frequency Diversity was supported only in
1. Frequency Diversity with ACM adaptive mode Fixed ACM mode. Starting from I6.9.2 Frequency Diversity is
also supported in Adaptive ACM mode.
Revertive HSB protection is supported in 1+1 HSB mode. It is
2. Revertive HSB protection mode
supported only in shelf configuration.
SNMP IP forwarding provides access to the NE in a shelf by
using a separate IP address for each NE. For more details
3. SNMP IP forwarding
about SNMP addressing refer to IP10-G SNMP management
guide.

®
6. Features with Limited Support

This section lists features that were available in the previous version, IP-10
version I6.9.1 (running in previous HW versions), as well as new features,
which are supported in this version within limited constraints or with reduced
performance.
1. CLI text configuration scripts Extension units cannot be configured using text scripts.
STM-1/OC-3 T-card in 1+1 protected
2. Not supported, but not blocked in the user interface.
extension IDUs in a nodal configuration
Up to 50 MEPs per element are supported. More MEPs can be
3. Ethernet 802.1ag CFM
configured, but false alarms may be raised
CFM is not supported in Single Pipe application but also not
4. Ethernet 802.1ag CFM
blocked by software.
5. RSTP does not support LAG ports in the mesh LAG ports should always be edge ports.
Is supported only with a Single mode SFP. For a detailed list of
supported SFPs, refer to the Product Description.
6. Optical 100Mbps Ethernet interface
Not supported with HSB protection
Not supported with a LAG
7. Enhanced QoS Enhanced QoS is not supported with Flow Control enabled.
Multi-Unit LAG with Electrical RJ-45 interface and Automatic
8. Multi-Unit LAG and ASP
State Propagation (ASP) is not supported.
Software download and configuration file backup tasks will fail
9. NetMaster support
for any NetMaster versions prior to R12A02
FTP will not work unless the server is configured to use
port#20 for the data.
If this is not possible, parameter version-management-admin
10. FTP
should be disabled in the IP-10; however, this will disable a
protection mechanism which ensures that only SW versions
designed for this system can be loaded.
Narrow Wayside channel is not supported. Use Wide wayside
11. Wayside channel
channel instead.
Revertive HSB protection mode is not supported in 2+2
configuration but is also not blocked by software.
12. Revertive HSB protection
Revertive HSB protection is not supported in Stand Alone
mode but is also not blocked by software.

®
IP forwarding in the shelf will be provided only for SNMP
management frames. Shelf IP addresses will also reply ping.
However, CLI and Web management of the shelf are not
supported through new shelf IP addresses. To access shelf
management through CLI and Web user must connect through
13. SNMP IP forwarding the IP address of the main IDU in the shelf.
In each particular shelf all the IDUs must be addressed either
by the main IP address + community string or by separate
shelf addresses. SNMP addressing of the IDUs in the same
shelf by different methods is not supported.

®
7. Modified Features
1. HSB protection Revertive HSB protection mode is supported since 6.9.2

Frequency Diversity is supported with ACM adaptive mode since
2. Frequency Diversity
6.9.2
SNMP forwarding for shelf configuration is supported since 6.9.2.
In previous releases SNMP access to the stacked NE in shelf
was only by addressing the community string. SNMP forwarding
3. SNMP management
provides access to the NE in a shelf by using a separate IP
address for each NE. For more details about SNMP addressing
refer to IP10-G SNMP management guide.
Limitation of in-band management L2 MTU:
L2 MTU of the in-band management frames can be limited by
4. In-band management user in range of 1000 to 1500 Bytes. This feature is useful when
providing in-band management through a segment with a non-
standard small MTU.

®
8. Notes and Limitations
# Subject Limitation Description/Notes

(CQ13228)
When enabling or disabling ATPC in a
remote unit by using a “local-remote”
For proper ATPC functionality, both ends of the
channel, only the remote unit‟s ATPC is
1. ATPC link should be enabled or disabled. Local ATPC
enabled or disabled. Just changing the ATPC should be enabled or disabled as well.
at one end of the link does not automatically
change the setting at the other end of the
link.
LOC on a local Electrical GbE (10/100/1000) port
will NEVER cause shutdown or Tx-Mute on the
(CQ11348)
remote end. This behavior avoids dead-lock:
Automatic State Single pipe application: “Automatic State
2. If the remote end is shut down due to Local-LOC,
Propagation Propagation” (previously called “GbE Tx-
and the remote cable is then disconnected, the
mute”): “Local LOC” is enabled.
local port is shut down, and the Ethernet link will
never be able to recover.
(CQ43376, 43720)
Automatic State Automatic State Propagation is not supported
3. Supported with optical interfaces.
Propagation with Multi-Unit LAG when the Ethernet port
interface is Electrical (RJ45)
(CQ16708 / 17903)
It is highly recommended by the 802.1ag
4. CFM
standard to perform a loopback or ping to the
remote unit before activating Link-Trace.
(CQ17189) When a switchover occurs, the new active IDU
It is highly recommended perform loopbacks introduces a different MAC address into the
5. CFM on IDUs configured for 1+1 HSB protection network. A loopback which was initially
by MEP ID and not by MAC address. addressed to the previously active IDU (which is
now the standby IDU) will not succeed.
(CQ54554) Changing port type will not affect any existing
After changing Ethernet port type from trunk CFM MIP on that port. System will no delete
6. CFM
to access, CFM MIPs on the port will not be them automatically. User shall be aware of it
deleted. while changing port configuration.
(CQ60194, CQ60912)
In the scenarios of mixed customer-provider
network the MEPs on customer tail sites must
use higher levels than the MEPs in the
7. CFM
provider network.
MIPs on the Provider network will not answer
link-trace messages if it was initiated in the
customer network.

®

(CQ60911)
8. CFM In Metro switch MEP on customer network
port can be added only for the port S-VLAN.
Serial connection and Telnet is supported with

(CQ08720/20087)
9. CLI the VT100 protocol. Use of other protocols may
Serial connection and Telnet
cause some lines to be missing.
(CQ12929) A Procomm screen for IP-10 should be 80x24,
10. CLI
Procomm SW definitions while the default is 80x25.
Yes/No confirmation requires typing "yes" or "no"

11. CLI In CLI, Yes/No confirmation (and not ”Y” or ”N”). Any text other than “yes” will
be considered “no”.
(CQ15931)
12. CLI No auto-complete is available for add-trail
command parameters.
Downloaded configuration files from different
nodes should be saved in separate folders.
(CQ14545) However, the configuration file for a nodal
13. Configuration Download
Configuration files have no unique name. configuration contains internally separate files for
each of IDU in the node. These files (RTF
format) can be extracted and individually used.
(CQ24992)
Creating backup configuration files for
selected extension units does not erase If it is desired to only save configuration files for
Configuration
14. configuration files from other units, even if units that are present in the system, use the
Management
these units do not exist. After uploading, all “backup all archives” operation.
configuration files will be sent (even for units
which are absent).
(CQ35616)
Using low capacity scripts (under 40Mbps)
with Diversity is not supported. Performing a Refrain from using low capacity scripts with
15. Diversity
force radio operation may sometimes result diversity hitless switching.
in a traffic hit and signal degrade alarm.
(CQ39653)
In Frequency Diversity mode, the following
remote radio parameters cannot be
configured from the standby IDU: Configure these parameters from the active IDU
16. Diversity
or directly from the remote IDU.
1. Remote force TX max level
2. Remote ATPC reference RX level
3. Remote TX unmute.
(CQ62501) – Internal RN only
This happens due to additional buffering required
17. Diversity Enabling radio diversity baseband switching
for base band switching.
will increase the latency of the radio link.

®

(CQ65873)
18. Diversity In Frequency Diversity BER indication is not
available in the standby unit.
(CQ32333)
19. Enhanced QoS Changing the size of a queue will temporarily
affect traffic
(CQ31759) The user should set the criteria in the opposite
Classification criteria for the enhanced TM order, i.e., more specific criteria before general
20. Enhanced QoS
are evaluated one at a time, and the frame is criteria.
classified upon finding the first match.
(CQ50590) Classifier overrides actual value of the CFI/DEI
The Policer will receive each packet with a bit.
21. Enhanced QoS
color based on classifier decision and not the
original CFI/DEI value.
The system does NOT support automatic
Ethernet crossover (commonly called “Automatic
MDI/MDIX”) for FE ports. The following cables
should be used:
22. Ethernet Ethernet port crossover IP-10 port to IP-10 port – cross cable
IP-10 port to external switch port – cross cable
IP-10 port to external HUB – straight cable
IP-10 port to PC – cross cable
Packet loss when using 100% throughput (of the
port capacity). This is a theoretical case in a
laboratory when there is a difference in the clock
23. Ethernet Ethernet maximum (100%) throughput source of the testing equipment and the IDU (up
to 100 ppm).
When the throughput is at 99.99%, there is no
packet loss.
(CQ10376) Packets with VID=0 are considered un-tagged
24. Ethernet
Packets with VID=0 and pass through access and hybrid ports.
In single-pipe mode, the 4091 tag is removed,

(CQ13017) and the frame will egress untagged at the remote
25. Ethernet
Frames tagged with VID=4091 end. Therefore, users should avoid using VLAN
4091.
(CQ16586 / 21192)
VLAN name text strings should not contain
Avoid using spaces and “%” symbols in VLAN
any spaces.
26. Ethernet name text strings. Underscores “_”can be used
In addition, the “%” symbol will cause name instead.
to be misrepresented in the Web-Based
EMS.

®

This configuration must be similar on the IP-10
and the device connected to it. The default is
27. Ethernet Auto negotiation, speed, and duplex “1000 full” on the optical interface and “auto-
negotiation on" on 10/100 or 10/100/1000
interfaces.
(CQ10564) The switch is capable of learning up to 8K (8192)
28. Ethernet
MAC learning capability random MAC addresses.
(CQ10425) The system broadcasts as if the SA was the DA

Packets with SA of Broadcast (MAC=FF-FF-
29. Ethernet
FF-FF-FF-FF) or Multicast (MAC bit [40] is
set) will be forwarded.
(CQ42851) The following configuration changes may cause
Changing Ethernet port PHY configuration traffic disruption:
30. Ethernet will cause short traffic disruption. Flow control
Learning
Auto-neg
(CQ16586 / 21192)
Avoid using “spaces” characters. The character “_”
The following bridge related free text (underscore) can be used instead.
strings should not contain any spaces:
31. Ethernet 1. VLAN Name
2. Policer Name
3. Association Name
4. Domain Name
(CQ66097)
When Enhanced QoS is disabled, VLAN P-bit
32. Ethernet - QoS overwrite is not available if classifying based
on IP TOS.
SFP modules manufactured by CORETEK

33. Ethernet SFP Use other manufacturer‟s modules.
tend to get mechanically stuck in the cage.
(CQ38552)
The alarm editing feature does not affect Unlike other alarms, external alarms can be
34. External Alarms
external alarms, although this option is not edited from the external alarms page.
blocked by the user interface.

®

(CQ31818)
The following feature combinations are not
supported, but are not blocked in the user
interface:
 Multi-radio and protection
 Multi-radio and hitless switching (SD,
FD)
35. Feature interoperability An invalid configuration will trigger an alarm.
 Hitless switching (SD, FD) and XPIC
 Hitless switching (SD, FD) and 2+2
protection
 Hitless switching (SD, FD) and ACM
 XPIC and protection
 - Hitless switching (SD, FD) and 2+0
protection
(CQ32379)
 Refresh the ARP tables in the external
GARP sent by an IDU after a protection equipment
36. Floating IP address switch may be lost if it takes more than five
 Configure the IDU to perform more GARP
seconds for the Ethernet link to be restored
retries.
in external equipment.
(CQ66730)
When working with FD in ACM adaptive
Frequency Diversity and
37. mode, forcing diversity to the radio with a
ACM
lower MRMC profile will result in loss of
traffic.
Inserting or removing a powered IDU to or from a
IDU insertion and IDUs must be powered off before being
nodal enclosure may cause damage to the IDU‟s
38. removal in a nodal inserted to or removed from a nodal
software, possibly requiring the IDU to be sent to
enclosure enclosure.
the manufacturer for repair.
In order to transmit Ethernet traffic to a main unit,
Ethernet cables must be connected from every
In-band management traffic must physically
extension unit to the main unit.
39. In-band Management reach the main unit‟s Ethernet ports in order
Note that this is necessary for in-band
for management to be provided.
management, even if no user Ethernet traffic is
required.
Setting VLAN 1 as the management VLAN
Do not use VLAN 1 (default traffic VLAN) for in-
40. In-band management will result in packet loss, especially for small
band management.
frame sizes (less than 100 bytes).
(CQ26772)
Two ports in which the same VLANs are “Allow all VLANs” is considered a different group
allowed cannot be part of the same LAG of VLANs, since if the user adds a new VLAN to
41. LAG
group if the VLAN is explicitly defined in one the bridge database, it will be automatically
port and allowed as a result of “allow all” in added to the port.
the second port.

®

(CQ10994 / 11727) When the system is configured to in-band
Management VLAN setting in in-band management, the management VLAN must first
management and protection: For further be configured in the remote standby unit. For
42. Management
details, refer to the section on Management further information, refer to the Product and
Configuration in the Feature Description Features Description and External Protection
document. sections in the Feature Description document.
(CQ8139)
In-band management can experience
Set the Management VLAN to the highest
43. Management disruptions when traffic throughput is priority.
particularly high if the Management VLAN is
not set to the highest priority.
This only happens when the power is off in the
active unit, and can be resolved by the taking the
following steps:
1. Disable the learning feature of the external
(CQ11003 / 12878) switch (or use a hub).
When managing 1+1 units (active and 2. Reduce the aging time of the external
standby) via an external switch, units might switch.
44. Management
not be reachable for ~5 minutes when 3. Issue "flush dynamic entries" in the external
powering off the active unit, or when a
switch, after switchover.
switchover is initiated.
4. Issue "arp" in the PC after switchover.
5. Use an Ethernet splitter cable instead of an
external switch.
6. Use a floating IP address.
(CQ21158)
When managing a protected (1+1) link with
When managing a protected link using out-of-
out-of-band management via the wayside
45. Management & WSC band management via the wayside channel, it is
channel, narrow WSC might be too narrow to recommended to use wide WSC.
manage the link, and management might be
very slow.
(CQ37595 and CQ37962)
The alarm will be initiated only upon a profile
MRMC profile change.
46.
degradation alarm The feature is not supported in ACM fixed
mode, but is not blocked by the user
interface.
(CQ53370)
Multi Layer Header Layer3 and Layer4 headers are not
47.
compression compressed when packet has more than 2
VLAN tags.
(CQ31729)
Multi-Radio requires both sides of the link to be
Management may be lost for a link if Multi-
48. Multi-radio properly configured. Make sure to configure the
Radio is enabled on one end of the link and
far side first in order not to lose management.
disabled on the other end of the link.

®

(CQ49719)
“Shut down link upon radio failure” option will
49. Multi-Radio Shut down link on a radio failure option will
initiate ASP when one of the radios fails.
take effect only when ASP is enabled.
For example, in order to block the radio in slot 1,
(CQ39843)
Multi-radio with line slot1 IDU should be configured to block local
50. The block radio parameter should be
protection radio and slot 2 should be configured to block
configured differently in each IDU.
mate radio.
(CQ42951)
Multi Radio with line protection is not
Multi-Radio with line supported when the remote side is Always use the same configuration on both sides
51.
protection configured as Multi-Radio without protection. of the link.
This improper configuration may result in a
loss of TDM trails on the radio interface.
(CQ43272)
Multi-Unit LAG on slot 2 of a 2+2 protection
Avoid improper configuration of Multi Unit LAG in
52. Multi-Unit LAG and 2+2 configuration is not supported, but is not
slot 2 of a 2+2 protection configuration.
blocked by the user interface.
(CQ16770)
53. PM “Ethernet frame error rate” PM resolution is
1%. 0% means less than 1% error rate.
Trail PM handling is centralized in the main unit,
but the PM measurement database is kept at the
trails‟ end-point interfaces (line interfaces, and
(CQ22753)
radio interfaces with SNCP configuration).
Clearing trail PMs will cause all trails to be Clearing PMs for trails will clear the PMs in
54. PM
cleared in the units holding trails‟ interfaces, whatever units in which the trails have their
not necessarily in the main unit. database.
In addition, in a 1+1 configuration PMs will not be
cleared in the standby unit.
Always read TDM trail PMs from the main active
unit.
TDM trails PMs are only valid when
55. PMs in Protection These PM, as measured in the standby unit,
measured in the active unit.
show incorrect values. The relevant intervals are
not marked as invalid.
Electrical (Copper) Ethernet ports' LOC will not
serve as protection switchover triggers unless
56. Protection Ethernet ports in protection
specifically configured to do so. This is available
in CLI only.

®

When replacing a protected IDU, the new unit
must be inserted after it has already been
configured to protection mode (including all
conditions), and then shut down prior to
insertion.
The necessary conditions for protection are:
 Both IDUs must have identical hardware
(same P/N).
 Both IDUs must be configured to the same
switching mode (Smart Pipe, Managed
Switch, or Metro Switch).
 The management type must be the same in
57. Protection Replacing units in protection mode
each IDU (i.e., both out of band or both in-
band). Otherwise, a “mate communication
error” alarm will be raised.
 If in-band management is used, the
Management VLAN must be the same in
both IDUs.
 If in-band management is used, the
Management VLAN must NOT be used for
traffic.
 Different IP addresses must be configured
for both IDUs.
 Both IDUs must have protection enabled.
(CQ16813)
When upgrading the software version in a
58. Protection protection configuration, both IDUs (local and
mate) must be upgraded to the same
software version.
(CQ15624)
59. Protection “Protection Lockout” and “Protection Force
Switch” do not persist after a cold reset.
In standalone mode, management access to the
standby unit through its IP address is only
possible if a protection cable is properly
Management access to the standby unit is connected.
60. Protection
limited in standalone mode. In a nodal configuration, access is provided via
the actives unit‟s IP address using the
centralized management channels (CLI, Web-
Based EMS).
(CQ22548)
After enabling protection, management may
61. Protection
be lost for up to 60 seconds until system re-
configures itself.
Configuration during "Copy-2-mate" and/or The user should refrain from changing
62. Protection
MRMC change (radio script change) configuration during these two processes.

®

(CQ64582)
Revertive protection counter aggregates the
63. Protection
total number of revertive protection switches.
The counter is zeroed on system reset.
(CQ64942)
In HSB protection passwords and
From security reasons password and
authentication information are not copied to
64. Protection authentication information is not copied to mate
mate IDU. This includes:
IDU in HSB protection.
- SNMPv3 authentication settings
- FTP access password
(CQ34659)
When changing management parameters in
While changing management parameters in HSB
Protection & Hot Standby (HSB) protection mode, the
65. protection mode, the standby IDU must be
management standby IDU must be changed first. changed first.
Otherwise, if slot 2 is active, there may be a
loss of communication to the extension IDUs.
(CQ29647)
STM-1/OC-3 interface in protected extension
Protection – STM-1/OC- Avoid this configuration. If mistakenly configured,
66. units is not supported. If this is configured
3 disable protection and reset the IDU.
(even temporarily), the STM-1/OC-3 card
may malfunction.
Deleting all TDM trails and performing “copy
In order to disable TDM traffic in a standalone
to mate” in a standalone configuration will
67. Protection – Standalone configuration, just disable the line interfaces
cause a “Mate IDU configuration mismatch”
instead of deleting trails.
alarm.
E1s recovered from PW traffic are not a good
(CQ48062) synchronization source .
TDM line E1 recovered from pseudowire Use of a PW-recovered clock as a network
68. Pseudo-Wire
cannot be selected as a synchronization synchronization source can be carried out by
clock source. configuring the system clock reference output to
be taken by the PW recovered clock.
Note that in some cases (such as multi-radio
(CQ54142)
configuration, where only one IDU is connected
The Pseudowire traffic port must be to the radio) this requires extra connections.
69. Pseudo-Wire connected to an Ethernet interface located in
Moreover, the T-card should be in a slot for
the same IDU in which the T-card is
which TDM trails from the desired sources are
inserted..
configurable.
(CQ51045)
Timing for ACR pseudo-wire services fully Jitter/Wander testing should be carried out after
70. Pseudo-Wire
stabilizes after about 10 minutes (no traffic 10 minutes of system stabilization.
slips are experienced)
Pseudowire inherently saves baseband by
(CQ46127)
71. Pseudo-Wire and ABR sending frames only over active paths in flow
Pseudowire trails may not be used for ABR
domain.

®

A separate RFU software version (O5.52g) must
be used for 1500P RFUs operating at 11GHz.
72. RFU 1500P 11GHz RFU
1500P RFUs operating at other frequencies
should use software version O5.52f.
(CQ24409)
73. RMON Collision frames are counted as bad octets in

half-duplex ports even if there is no packet
loss.
(CQ26722)
Avoid using the rollback function. The software
74. Rollback The rollback function will not allow
downgrade function should be used instead.
downgrading to versions earlier than 6.6ga.
The RSTP convergence time is typically less
than 10 seconds as compared to the traditional
(CQ30609) convergence time of 50 seconds introduced by
75. RSTP RSTP convergence time can be up to 10 STP.
seconds, depending on topology. In case of link between switch and a hub that is
called Link-Type "shared", RSTP does not
improve convergence relative to STP.
(CQ33246)
When an FE port is used as a non-edge port
76. RSTP Refrain from using FE ports as non-edge ports.
in a ring RSTP topology, a long disruption
time may be caused upon port failure.
LAG ports are not blocked for use, but illegal
LAG ports are not supported within the RSTP
77. RSTP with LAG configuration changes may take place in the LAG
topology.
and the port will not be shut down properly.
(CQ15536 – 3)
Uploading and downloading files to and from
the IDU requires the following parameters:
host IP, host-path, user name, and
password. Additional parameters are
required for “IDU digital certificate”, or “CA
certificate”: file-name, security file type and
security file format. Due to the fact that the
IDU can be managed simultaneously by a
few connections, some conflicts may occur:
78. Security  One connection configures the
parameters for one purpose and another
connection configures them for another
purpose. The "apply" command of both
connections will probably fail.
 One connection (C1) starts an operation
(upload/download) and another
connection (C2) changes parameters
related to the first connection operation.
The C1 operation might fail without any
alarm or notification.

®

(CQ15826 – 1)
The web-protocol parameter, for determining
the web protocol (HTTP or HTTPS), may not
be included in a “copy to mate” operation in a
system in protection mode, for the following
reasons:
 Applying HTTPS protocol requires the
installation of a digital certificate. IDU
79. Security digital certificates are unique per IDU
(based on IDU key pairs). If the digital
certificate is not installed, setting the
web-protocol parameter will fail.
 Security considerations: Eliminate the
option to override security definitions
from one unit with lower security
privileges to another unit with higher
security privileges.
(CQ15826 – 2)
Due the fact that there are some web
browsers (e.g., Mozilla Firefox) that require a
web server‟s CA certificate (in addition to an
IDU certificate), a new configuration is
required to enable this option.
Security – CA The “web-ca-certificate-admin” parameter
80.
Certificate should be set to enable (the default is
disable) in order to use a CA certificate.
When this option is enabled, a CA certificate
file should already be installed and valid in
the IDU. This parameter will not be copied to
mate when activating a “copy to mate”
operation.
(CQ15340 / 15536 – 1)
When setting up an SFTP connection for file
download and upload operations (e.g.,
81. Security - SFTP software downloads, configuration file
backups, and certificate downloads), the IDU
(client side) will not authenticate the SFTP
server based on the server's public key.
(CQ15536 – 2)
An SFTP server authenticates users based
on user name and password. Public Key
82. Security - SFTP
authentication of the target IDU is not
supported, since it does not require a
password.

®

The mechanism provided for SNMP to access
different IDUs in a shelf (since they all have the
same IP address) is accessing them by use of
Accessing data in an extension IDU requires
83. SNMP the community string or context.
the use of a community string.
The string used is “extension _n” where n is the
slot number of the IDU in the shelf (1 is the
lowest and 6 is the highest).
(CQ26355)
84. SNMP Only standard RMON counters are included
in the MIB.
1. Make sure protection is disabled in the unit
A Unit containing an STM-1/OC-3 T-card before inserting the unit.
should not be inserted in a nodal enclosure
STM-1/OC-3 in or
85. as an extension unit while its protection
extension units 2. Insert the unit without the STM-1/OC-3 T-
mode is “enabled”. Doing so will cause TDM
trails to malfunction. card, set protection to disable, and then
insert the T-card.
(CQ25915) Use this mode only in standalone mode or for
In uni-directional MSP mode, only incoming nodes with only two IDUs.
STM-1/OC-3 uni-
86. trails from main radios (or in standalone If required for larger configurations, use “normal”
directional MSP mode
mode) will be properly transferred through mode; the standby interface will shut down, thus
the standby link. indicating which link to take data from.
(CQ33628)
If the external equipment takes traffic from
STM-1/OC-3 uni- Use radio diversity. Traffic will always be taken
87. the STM-1/OC-3 interface in the standby unit,
directional MSP mode from the proper unit
all traffic may be lost in case of a radio failure
in the standby unit.
(CQ34291)
When the main IDU in the node is R3 Running different software versions in the node
88. SW downgrade hardware, the user cannot downgrade the is not supported. Either use R2 units or install
extension R2 IDUs to software versions software version 6.7 or higher.
earlier than 6.7.
Version 3.0.34 is a previous version which was
Upgrading from version 3.0.34 must be done loaded in some IDUs at production. It does not
in standalone mode. support software upgrade in a nodal
89. SW upgrade
After the upgrade process is complete, the configuration.
web browser should be restarted. In order to upgrade these systems to the current
version, do so while out of the nodal enclosure.

®

1. Update the software version in the new
active unit.
(CQ24994) 2. Updates to extension units can be
When upgrading to a new version in a 1+1 performed from the standby unit as well.
configuration in a nodal configuration, the 3. If the standby unit was updated, the
SW upgrade in 1+1 stored upgrade files in the standby unit are procedure to download the new version to it
90.
configuration not automatically updated (the running is as follows:
version is properly updated). Place the downgrade files of the
In case of a protection switch, the new active desired version in the FTP directory of
unit will have an old version for installation. the FTP server.
Perform download new version and
upgrade normally in the relevant unit.
(CQ37358)
Configuring primary and secondary
Primary and secondary synchronization sources
91. Synchronization synchronization sources from the same line should not come from the same line interface.
interface is not supported, but is not blocked
by the user interface.
(CQ41623)
Creating a synchronization loop by setting
the clock source as an STM-1/OC-3 VC while
the sync source is an STM-1/OC-3 signal
92. Synchronization Avoid synchronization loops.
clock is not supported, but is not blocked by
the user interface.
Such an improper configuration will result in
synchronization loss.
(CQ54251)
When working in ACM adaptive mode, it is Using high channels may result in
93. Synchronization
recommended to use the 1st or 2nd radio synchronization trail loss at low MRMC profiles.
channel for the synchronization trail.
Inserting or removing T-cards to or from an IDU
T-card insertion and T-cards must be inserted to or removed from with its power on may cause damage to the IDUs
94.
removal an IDU while the IDU is powered off. software, requiring the IDU to be sent to the
manufacturer for repair.
TDM and ACM The status of TDM trails and radio links in Trail statuses and ACM links are not monitored
95. statuses, PMs in ACM mode are only valid as reported in the in the standby main unit and their values will be
Protection active main unit. incorrect.
The maximum number of trails in a system is
180. In addition, the number of trails mapped to a
96. TDM trails Up to 180 trails can be configured in a node. certain radio is limited by the bandwidth of the
relevant script.
SNCP trails count as two regular trails.

®

(CQ21270)
If TDM trails are configured towards an
This takes place because the unit is temporarily
97. TDM trails interface in an extension unit, and that unit is
unreachable.
reset, the alarm "Trails mapped to inexistent
interfaces in IDU #n" is temporarily raised
98. TDM trails Trail ID string may not include spaces
(CQ56928)
99. TDM trails TDM trail description must not exceed 49
characters.
(CQ21270)
After deleting all trails in standalone mode,
16 default trails will be re-established after Never delete all trails. If no TDM traffic is
TDM trails in standalone
100. reset. desired, the user should disable the E1/DS1
unit and in protection
Also, in case of standby unit reset the 16 interfaces.
default trails will be configured in the active
unit.
If line LOS is detected at an interface In order to determine whether the trail is properly
mapped to a trail, AIS will be sent along the configured prior to connecting traffic to its
101.TDM trail status
trail. Therefore, the user will get “signal interfaces, use a line loopback towards the
failure” and “trail ID mismatch” indications. system in order to test the trail.
The 1st char can be = a-z, A-Z, 0-9, _
Some characters are not allowed in the user
102.User management The other characters can be: a-z, A-Z, 0-9, _, -
and password settings.
The last char can also be $
It is recommended to use Internet Explorer 6.0-
(CQ20683) 8.0, or Mozilla Firefox 3.0-3.5.
103.Web
Web browser Internet Explorer 5 and all other browsers are not
supported.
(CQ12684)
When using the Mozilla Firefox web browser,
104.Web
the “F5” function does not refresh as it does
in Internet Explorer.
PM graph sizes do not change with browser PM graphs should be viewed with zoom 100% in
105.Web
zoom. the web client.
(CQ15165)
Internet Explorer should be configured to
“Medium-High” or “Low” security level when
Otherwise some web pages may cause the
106.Web/Security using the Web-Based EMS.
browser to prompt for authorization.
If this is not possible, you should add the
network element‟s IP address to the trusted
IPs table in the web browser.
TDM capacity due to “Wide WSC” “WSC Wide”, when activated, consumes 2.048
107.WSC
configuration. Mbps of the radio BW.

®
(CQ11827) “Wide” WSC capacity should not exceed

108.WSC 1.9Mbps. Frames may be dropped if capacity
WSC capacity exceeds this because of bursts.
(CQ19994)
When using WSC in Managed Switch mode,
109.WSC any tagged frame carrying an Ethertype
different than 0x8100 will be stripped upon
egress.
Reported XPI value always refers to the last
(CQ49644)
good channel read. XPI value is not updated
110.XPIC In case of failure in one of the XPIC
when XPIC state machine enters “recovery” or
channels, reported XPI value is not relevant.
“single channel” states.

®
9. Corrected Bugs
The following bugs have been corrected since the I6.8 release:
# Subject Description Severity Workaround

(CQ68133)
Ethernet traffic disruption time period as a result of HSB
1. HSB protection protection switch may exceed 50msec. This happens High
when working with IP10 units in HSB protection
configuration back to back and using optical GbE
interfaces.
Defected blocks in radio script XPIC ACM 192Mbps
2. Radio scripts High
256QAM 30MHz channel spacing
Low MSE at script XPIC ACM 259Mbps 256QAM 40MHz
3. Radio scripts High
channel spacing
(CQ57702)
4. Security Medium
Resolved user password security issues.
(CQ64221)
5. Web Unable to disable PW service from the web management Medium
when using Internet Explorer.

®
10. Open Bugs

(CQ31036)
When configuring a new ABR trail, Ethernet traffic will be
Temporarily set a short timeout
1. ABR affected in the secondary path for the time defined in the Low
when configuring a new trail.
revertive timer. This is because there is a short initial signal
failure at the primary path.
(CQ30134) Check the revertive timer status
2. ABR RDI indication will be received during the revertive timer Low of both end-points in order to
period even if the failure has been corrected. determine if this is the case.
(CQ31123)
3. ABR Upon configuration of an ABR trail, Ethernet capacity in both Low .
links will be reduced for the duration of the revertive timer.
(CQ30764)
A few ES, SES can be counted on the secondary path after Ignore the first few seconds of
4. ABR Low
a failure in the primary path. The errors are only in the PMs; PMs.
there are no errors in the actual traffic.
(CQ42794)
When the STM-1/OC-3 interface for ABR trails is used, it
should always be the primary path. Use STM-1/OC-3 as a primary
5. ABR High
If STM-1/OC-3 is used as a secondary path, upon primary path for ABR trails.
path failure ABR trails may not return to the primary path
after the failure is resolved and the revertive timer expires.
(CQ22948)
Alarms and
6. Very rarely, a false “unexpected signal” alarm is raised at an Medium Reset the system.
events
E1/DS1 port at system boot.
Refer to the alarms list document
The auto-complete feature of the CLI will only show the first
7. Alarms editing Low to determine the name of each
100 alarms for editing.
alarm.
(CQ34288)
It is possible to have a situation in which one side of the link Cancel ATPC override on both
8. ATPC has ATPC enabled and the other does not when using Low
sides of the link.
ATPC override, if an override command is performed on one
side of the link and not the other.
(CQ25568)
Choose a longer time interval or
9. CFM A false "Ethernet services failure" alarm may occasionally Medium reduce the number of MEPs in
be raised and be cleared if more than 50 MEPs are
the system.
configured.
(CQ33974) The standards recommend
10. CFM CFM linktrace works after an RSTP topology change only Medium always performing ping before
after performing a ping. linktrace.

®

(CQ21350/21000)
The automatic linktrace interval is not accurate - the auto
11. CFM Low Adjust the timer accordingly.
actual linktrace timer value is longer than the configured
value.
(CQ20037) Do not use the same level for the
12. CFM Traceroute will fail when two MIPs are configured in two Low same service in Managed Switch
ports in a link where one is CN and the second is PN and Metro Switch mode.
(CQ20037) In a network with 802.1ad

provider bridge sections and
13. CFM Traceroute between MEPs/MIPs at the same domain level Low 802.1Q sections, use different
in network elements operating in Metro Switch or Managed
domain levels for nested
Switch mode will fail.
sections.
(CQ54448) System will return to normal
14. CFM During the creation of Unit Info file, false CFM events Medium operation after finishing the Unit
indicating service failures may appear. Info creation.
(CQ54499) Initial state is not indicative.

15. CFM During CFM configuration, initial state of the service is OK Medium Check the status only after
even though CCM messages have not yet started. completing the configuration.
(CQ22320) By typing "?" after the command,

16. CLI Typing “--help” for a command without arguments will cause Low the help information is displayed
the operation to fail. properly.
(CQ40627) Type the exact option in CLI or

17. CLI CLI auto-completion for the protection-admin parameter Low use Web/SNMP interfaces to set
suggests incorrect options. this parameter.
(CQ25748) File names are case-sensitive.

18. CLI scripts Loading a CLI script with an incorrect uppercase/lowercase Low Actual loading will not be
name from Windows will give false success message. performed.
(CQ26335)
19. CLI scripts The system will allow CLI scripts to run from standby units. Low Run CLI scripts in active units.
Commands will fail, however.
(CQ26439)
Wait for the end of the script. All
20. CLI scripts While running CLI scripts, incorrect trail information is Low
information will be correct then.
displayed in the Web-Based EMS.
To avoid long traffic loss, it is
(CQ66976)
recommended to disable diversity
Resetting the standby IDU during maintenance operation may
21. Diversity Medium revertive mode. Revertive mode
result in long traffic loss when Frequency Diversity is enabled
may be enabled again after the
and ACM adaptive mode is used.
standby IDU wakes up from reset.
(CQ25408)
Dual power In IDUs with dual feed power, a large voltage difference
22. between power sources may cause radio BER. This will not Medium
supply
take place if there is a total power failure in one of the
inputs.

®

This is the BER that the TDM
(CQ10151) port reflects when the port is
23. E1/DS1 Low
When the E1/DS1 port is disabled, port-current-ber = 1e-10. disabled, since there is no BER
calculation.
(CQ33551) In an MPLS-based network, the
24. Enhanced QoS When MPLS packets are used, DSCP classification is not Medium third hierarchy classifier can be
effective. either VLAN Pbits or MPLS.
(CQ33842)
Configure the required
25. Enhanced QoS After disabling enhanced QoS, port 8 scheduling is always Low
scheduling mode.
“all queues strict”.
(CQ42193 ) Stop Ethernet traffic before
26. Enhanced QoS Changing priority queue size to 0Mbit should be performed High changing the queue size to
without a traffic load. 0Mbit.
(CQ33067)
Some packet loss may take place when transmitting four or
27. Ethernet Medium
more streams with packet size continuously increasing with
time.
(CQ32196)
Switching mode application: Smart Pipe, Managed Switch
If a priority-tagged frame (vlan ID=0) is transmitted to the
28. Ethernet pipe or access port, it is always received at the far end Medium
without the priority tag.
Note: In case of metro (customer port), the priority tag is
preserved on egress.
(CQ11840)
29. Ethernet Whenever auto-negotiation is being changed, PHY power is Low
being set to default which is UP.
(CQ25518)
Limit the VLAN name length to
30. Ethernet Attempting to configure a VLAN name with 16 characters Low
15 characters.
will succeed; however, only 15 characters will be displayed.
A message saying “port is not
(CQ32149) removed due to MEP contained
Removing all ports from a LAG group containing a MEP or in LAG” is given.
31. Ethernet Low
MIP results in removal of all ports except for the highest The proper way to delete a LAG
numbered Ethernet port. is to remove all MEPs or MIPS
first.
(CQ31393) These are two different

mechanisms. Choose the
32. Ethernet Flow control will not work properly in a port with policers Low
mechanism that is appropriate
attached.
for the network.
(CQ39734) Update the radio port type
33. Ethernet After setting “radio disabled” mode, the Ethernet port 8 type Low configuration after leaving “radio
will be reset to default. disabled” mode.

®

(CQ62978) 1. Set port connector type to
When changing Ethernet connector type from 100Base-FX 1000Base-X
to RJ-45, port may malfunction. Follow the steps in the 2. disable port
34. Ethernet Medium
workaround. 3. enable port
4. Set port connector type to RJ-
45
(CQ23892)
When injecting more than 700Mbps Ethernet traffic with
35. Ethernet - QoS Medium
frames smaller than 80bytes, there is some packet loss in
the fourth queue even in strict priority scheduling.
(CQ30358)
Ingress rate limiting of 90Mbps with CBS=1000 will cause  Set a higher CBS
36. Ethernet - QoS Medium
queue starvation when injecting four streams between  Set a different rate limit
90Mbps and 120Mbps.
(CQ29350) Toggle configuration for the port:
Changing port configuration from traffic to management or configure as traffic and re-
37. Ethernet ports Low
wayside very rarely fails, causing ports to malfunction (no configure as management or
WS/management frames are transferred). wayside.
An Ethernet interface cannot

(CQ21083) function in one direction. Testing
Ethernet testing When RX direction of a fiber (towards the Ethernet tester) is equipment is expected to shut
38. Low
equipment in mute, the tester might stop sending traffic in its TX down the egress traffic, while the
direction. carrier is lost on the ingress
direction.
(CQ9497 / 10035) These counter also increment on
39. Ethernet-RMON Medium
RMON 1024 Octets/In FCS errors counters oversize packets.
(CQ13077)
40. Ethernet-RMON RMON “Bad octets received” counts only 1632 “bad octets” Medium
even when ingress frame length is above 1632 bytes.
(CQ27140 , CQ31402)
41. Ethernet-RMON In-discard does not count flooded frames. Only discarded Medium
frames with a known destination MAC address are counted.
(CQ51037)
42. Ethernet-RMON In-discard counts only frames discarded on the radio port. In Medium
some scenarios packets discarded on other Ethernet ports
will not be counted.
Standard RMON MIB is
(CQ26355)
Ethernet-RMON / provided. Use CLI/Web-Based
43. The RMON MIB table does not show all available Medium
MIB EMS to read extra
measurements in the Web-Based EMS and CLI.
measurements.
(CQ24066)
Log time is relative to the current
44. Events log Events and alarm time history are updated according to Low
system time.
system time.

®

(CQ19814)
The optical GbE interfaces (SFP) do not advertise their , The optical GbE interfaces can
45. Flow Control capability to send PAUSE frames (TX PAUSE) during auto Medium generate PAUSE (TX PAUSE) or
negotiation handshake. Only their RX capability (react to react (RX PAUSE) to PAUSE.
PAUSE) is advertised.
(CQ14592)
10/100/1000 and 10/100 Ethernet ports: setting Flow
46. Flow Control Low
Control configuration to enable or disable, might cause a
momentary port shutdown.
(CQ14301)
47. Flow Control There might be loss of frame in the opposite side when Low Avoid 100% traffic load.
heavy bidirectional traffic is injected.
(CQ25365)
48. Flow Control Enabling/disabling flow control in a port may cause Low
temporary traffic loss and an LOC alarm.
(CQ54712)
When configuring FC, first
Endless protection switch will occur on 2+0 HSB or 1+1
49. Flow Control High enable FC on the external switch
HSB Frequency diversity setups when FC is enabled in the
and after it enable FC on IP10.
IDU and is disabled on the external switch.
(CQ22323)
IDUs insertion Removing a powered IDU from a nodal enclosure will cause Low Do not insert or remove IDUs
50.
and removal a traffic disrupt of about 70ms in the remaining IDUs in the with the IDU power on.
node.
(CQ26335)
If a LAG includes a GbE port and the radio port, but Problems can be identified by
51. LAG Medium
automatic state propagation is disabled, the alarm “LAG the radio LOF alarm.
status down” will not be raised.
(CQ30116) Slow protocols are link-level.

Refrain from using slow
52. LAG Unsupported slow protocols will be flooded to all ports in a Medium
protocols unsupported by the
LAG.
system.
(CQ25022) Inherent in the LAG mechanism.
53. LAG LAGs with an odd number of ports may have uneven traffic Low This is because the number of
distribution. flows is always even.
(CQ25748)
54. LAG LAG convergence times after connecting or disconnecting Low
ports may be higher than 50ms.
(CQ24110)
LAG and
55. Protection times for Ethernet ports in a LAG group are Medium
protection
above 50ms.

®

To prevent loss of management
user shall make sure before
(CQ52556)
enabling HSB protection that
56. Management In-band management may be lost while enabling HSB Medium
both IDUs are set to same
protection mode in slot1-slot2.
management type and same in-
band management VLAN.
(CQ14658)
MAC Header
57. Enabling or disabling MAC Header Compression causes a Low
Compression
few frames to be lost.
(CQ34755)
MAC Header In Multi Radio setup MAC header compression will be
58. Low
compression automatically disabled upon a failure of a radio channel in
the master unit.
(CQ54594)
MAC Header Muting slave radio link in 2+0 MR configuration when MAC
59. Low
compression header compression is enabled will cause smaller than
expected link capacity.
(CQ54615)
Disable MAC header
MAC Header In 2+0 Multi Radio configuration: setting TX mute on the
60. High compression before muting
compression master radio while MAC header compression is enabled will
master radio.
cause complete loss of all Ethernet traffic in this direction.
(CQ31486) This is because both sides are

Multi-radio and In a Multi-Radio configuration for single pipes, a failure in aware of the failure. The moment
61. Low
ASP both radios at any side may cause ASP to shut down both the problem is fixed both sides
line ports even though “remote fault” is disabled recover properly.
(CQ31601)
In a Multi-Radio configuration, traffic priority considerations
Multi-radio and
62. between Ethernet and TDM traffic take place in each radio Low
traffic priority
separately. In some cases (such as lowering the profile in
one of the radios), this can cause sub-optimal prioritization.
(CQ53964) Do not leave the IF cable
Multi-Radio with
63. M In 2+0 HSB mode all TDM trails will be lost after resetting Medium disconnected when resetting the
line protection
the active IDU if the IF cable is disconnected. IDU.
If untagged traffic is desired at

an end node of a network with
(CQ25748)
VLANs, the tag should be
In a network with VLANs, a terminal node configured as
64. Networking Medium extracted at the last port by
pipe may be unreachable by management if its link is
configuring it to access. The last
untagged. node should be a managed
switch.
(CQ25736)
65. NTP NTP updates to extension units may take several minutes if Low
performed immediately after the units have undergone
reset.

®

(CQ44575) Use 2 NPS sessions – one for
When Slot1 and Slot2 are in HSB protection and NTP uses the the active and one for the
floating IP address of the shelf, standby IDU clock will not be standby.
66. NTP Medium
updated by NTP. When updating time manually,
When user manually changes time on the active unit, it is both active and standby must be
not copied to mate standby unit automatically. updated.
(CQ42552, CQ62503) Use the Ethernet capacity PM to

Performance
67. In R2 hardware release the Ethernet link utilization PM is Medium estimate link utilization in Multi-
Monitoring
not accurate when Multi-Radio is enabled. Radio.
To measure the ingress

Performance In R3 hardware release radio utilization PM is calculated on utilization of the radio port refer
68. Medium
monitoring the egress traffic rather than on the ingress as expected. to the value of the utilization PM
on the remote side of the link.
(CQ62395) To measure the ingress capacity
Performance Radio Throughput and Capacity PMs are calculated on the and throughput of the radio port
69. Medium
monitoring egress side and not on the ingress (as expected). refer to the value of the PMs on
the remote side of the link.
In 1+1 protected configurations, turning off the active unit

70. Protection Medium
may cause switching times above 50ms. This occurs rarely.
(CQ29827)
71. Protection Protection times for SFP disconnections are sometimes Medium
higher than 50ms.
(CQ12563) Prior to setting frequencies the

on local and remote sides of a
72. Protection Frequency setting for the remote side in protection causes a Low link, enforce protection lockout to
protection switch.
ensure action.
A protection switch due to a cold
(CQ12259) reset command will be described
73. Protection Low
Protection cold reset switch reason as a manual switch in the alarm
log.
Traffic goes back to normal after
the protection switches.
(CQ13622)
Intentionally cold reset should be
Simultaneous cold reset to both active and standby units
74. Protection Low performed in the standby unit
(e.g., site power down) causes several consecutive
and then, when the standby unit
protection switches. is up and running, in the active
unit.

®

(CQ18189, 21520)
The following actions will cause a protection switch:
 Enabling or disabling an E1/DS1 interface which
receives no signal.
Perform a switch lock before
75. Protection  Enabling or disabling an Ethernet interface which Low
enabling new interfaces.
receives no signal.
 Changing the Ethernet connector type for an interface
which receives no signal.
 Defining a new trail to an interface receiving no signal.
(CQ23994) If desired, perform a “forced
76. Protection Attempting to perform a manual switch in a system in which Low switch”, which is the correct
the standby is faulty may cause some Ethernet frame loss. operation in this case.
1. When powering up a
(CQ26769) system for the first time,
In systems with 1+1 configured in both main and extension make sure the main units
units, with trails previously configured in main units, if not undergo protection
77. Protection immediately after powering up the main units, there are two Low switches in succession for
protection switches in quick succession (10-20 seconds), the first minute.
TDM traffic in the extension units may be permanently 2. If the problem occurs,
affected. delete all trails and
reconfigure.
(CQ33130)
78. Protection A “configuration mismatch” alarm is not raised when there Low
are different licenses in two protected systems.
(CQ31639)
RFU-HP and 1500-HP are not compatible in HSB
Always use the same RFUs for
79. Protection protection. Using different RFUs as protection mates in the Medium
both protection mates.
same side of the link will result in a “configuration mismatch
alarm”.
It is recommended not to use
auto-negotiation in a protection
(CQ34751) configuration since the
Protection and
80. The Ethernet link may fail in optical GbE (SFP) ports in Low negotiation process can take up
auto-negotiation
auto-negotiation mode after a protection switch. to a second. Auto-negotiation in
optical (SFP) ports always sets a
link to 1000 Mbps.
(CQ35571)
Protection and Enabling Automatic State Propagation (ASP) with protection Medium It is recommended not to use
81.
ASP may result in a long traffic disruption time upon protection ASP with protection.
switchover (up to 1 second).
(CQ19960)
The criterion is irrelevant. No
Protection and In radio disabled mode, protection switch upon radio
82. Low effect is caused by configuring
radio disabled excessive BER is available to users via the Web-Based this parameter.
EMS.

®

(CQ19960) Open a new web browser page,
Protection and When managing the active unit using HTTPS protocol, the and enter the URL:
83. Low
Security hyperlink for opening “Mate IDU” (standby) does not https://<IP_Addr-of-the-Standby-
function in the Web-Based EMS. unit>.
(CQ53631) AIS VC signaling is a non-

Protection and Protection switch may cause up to 100msec disruption time Medium standard feature, which should
84.
STM-1/OC-3 on the STM-1/OC-3 when AIS VC signaling is enabled on be used only if needed for
the STM-1/VC-3 port. interoperability purposes.
Manually disable the radio in the

(CQ29870)
Protection and second unit first, and then
85. A copy to mate operation from a unit with its radio disabled Low
radio disabled perform the copy to mate
to a unit with its radio enabled fails.
operation.
When the upgrade is completed,
perform an additional “copy-to-
(CQ18081) mate” operation in the active
Protection and
86. A “Configuration mismatch” alarm might appear when Low unit. For more details, refer to
SW upgrade
upgrading SW in a protection configuration. the External Protection section in
the Feature Description
document.
(CQ33104)
Provider Bridge Configure CN ports as edge
87. CN ports configured as “non-edge” transmit the provider's Medium
RSTP ports
BPDUs.
(CQ56575)
If only clock output is desired,
88. Pseudowire “Loss of Signal (LOS) on PWC card's front panel clock port” High split outgoing signal and feed it
alarm occurs when front panel clock is enabled, even if
into input pins
configured for output only.
Pseudowire (CQ54865) Make sure not to mark PW traffic
89. Any received frames with C-VLAN tag and CFI bit set to „1‟ High as “yellow” for C-VLAN in the
will be dropped and incoming traffic will be lost network
Pseudowire (CQ54865)
Recovery of traffic in ACR mode may take several seconds.
90. In extreme cases, when traffic shaping may cause Medium
temporary packet loss during the service restoration
process, the recovery time may be 25-30 seconds
For SAToP many values can be
The default payload size is N=16 (where N is the number of
91. Medium used; N=32 is a universally valid
E1 frames per packet. 16 is the minimum value for CESoP value required by the standards
with CAS.
Pseudowire (CQ45893) It is assumed that fragmented
Pseudowire traffic port RX fragments RMON counter works frames are very few. Supported
92. Low
properly only for stream of fragmented frames of less than PW standards do not support
100 frames per second fragmentation

®

During boot, “no communication with PWC” card events will This has no implications after the
93. Low
be raised and cleared. These events are logged in the event initial boot
log.
94. Inaccurate name appears in the web in line type selection. Low
Should be “E1 Double Frame” instead of “E1”.
PW T-card transmission RMON counters keep counting
95. Low
even if the port is down. This is because the counting takes
place at the MAC level (before the PHY).
(CQ34289)
There is no visual differentiation between the previous HW Systems can be identified by
96. R3 hardware Medium
version of the IP-10G (R2) and the latest HW version (R3), their functionality.
even though R3 contains some new functionality.
(CQ44407) Choose alternative
97. Radio Disable Radio must not be disabled if it is set as a Synchronization Medium Synchronization source before
source. disabling radio.
The Web-Based EMS displays
the actual maximum and
(CQ32209)
minimum configurable values.
98. RFU configuration The Web-Based EMS and the CLI/MIB display different Low
The values displayed by the
values for minimum and maximum frequency.
CLI/MIB are the RFU absolute
limits according to the RFU type.
(CQ32722)
Setting the cost of a port to 200000 occasionally causes the Medium Change the cost to another
99. Ring RSTP
port and its link mate to intermittently become “designated” value and then back to 200000.
therefore affecting traffic. This is a rare occurrence.
(CQ19589)
Connecting between pipe and switch by radio will limit the
effectiveness of automatic state propagation:
For best results, in addition to
 If line LOC (not copper GbE) appeared in pipe, it
enabling automatic state
propagates the state to the radio, so the switch next to
propagation, create the network
100. Ring RSTP the opposite pipe knows about the LOC. Medium
so that pipes are connected by
 If line LOC (not copper GbE) appeared in the switch, it radio to pipes and switches to
does not propagate the state, so the opposite switch switches.
does not know about the LOC.
 If LOC on copper GbE appeared, not switch nor pipe
forwards the state to the radio.
When a cable is disconnected,
(CQ15731) ignore the path cost of a copper
When an Ethernet cable is disconnected from a “non-edge” GbE and FE port. When cable is
101. Ring RSTP Low
port, a copper GbE interface and FE interface might return a re-connected, the path cost
path cost of 20,000,000, which is not the configured value. values become reliable once
again.

®
(CQ27705) Make sure to enable all local and

remote automatic state
102. Ring RSTP/RSTP An rx uni-directional failure at the root unit will cause Medium
propagation. This will cause all
convergence time of up to several seconds
failures to be bi-directional.
The radio path is preferred to a line path in case of equal
103. Ring RSTP/RSTP Low
cost paths to the root bridge.
(CQ27694)
Ring RSTP/RSTP
104. and 1+1 RSTP port states and status in the standby unit are different Low
than in the active. The values in the standby unit are
protection
irrelevant and will be updated upon protection switch.
(CQ27734)
Ring RSTP and If the root node is 1+1 HSB protected, and a protection
105. Medium
1+1 protection switch takes place, RSTP convergence may take up to a
second (because the root bridge will change).
(CQ33250)
Enable automatic state
Ring RSTP and Uni-directional failures towards the root port may cause a propagation on the remote and
106. traffic loss of several seconds unless automatic state Medium
1+1 protection specifically “tx-mute-on-remote-
propagation on the remote and specifically “tx-mute-on-
LOC”.
remote-LOC” are enabled.
Avoid using automatic state
(CQ25443) propagation when connecting
Ring RSTP and Using automatic state propagation to shut down an SFP link Low back-to-back with 1+1 links (in
107.
1+1 protection following LOS while connected to a 1+1 link will cause traffic such links, automatic state
failure. propagation is automatically
disabled).
(CQ32405) Ignore in-filtered frames in
RMON in When an IDU is in standby mode, traffic ports count all standby units. If desired, reset
108. Medium
protection incoming frames as in filtered Frames. These counters are the counters after the IDU
not automatically cleared when the IDU becomes active. becomes active.
(CQ30613) The port should be disabled

The displayed port state and role are incorrect after a GbE (either by configuration or by
109. RSTP Low
port has been changed from optical (SFP) to electrical (RJ- disconnecting the cable) before
45), or vice-versa. changing the connector type.
(CQ30728)
Upon a failure of a port in a LAG which is non-edge, LAG is only supported in edge
110. RSTP and LAG convergence may take a long time. Medium ports. Refrain from using LAG in
The system will not prevent users from configuring LAG non-edge ports.
ports as non-edge ports.
(CQ31123)
RSTP and Ring Changes in configuration are
111. Upon a Change in STP, configuration convergence can take Low
RSTP treated as initial convergence.
up to 30 seconds.

®

(CQ32382)
When Cisco equipment implementing PVST is connected to
a non-Cisco network, with a trunk port at one end and an See
RSTP access port at the other end, and the network is forwarding Medium http://www.cisco.com/en/US/tech
112.
interoperability PVST+ messages, the Cisco equipment on the access side /tk389/tk621/technologies_tech_
will block the port, as it expects standard BPDU messages note09186a00801d11a0.shtml
and not per-VLAN PVST BPDUs. This will, of course, lead
to a complete traffic loss.
(CQ33223)
The following TCP ports are opened for access:
 705
 2049
 1025
 1026
 2029
 111 Configure DMZ / firewall to
113. Security High
 10000 protect these ports.
 80
 2160
 10002
 22
 950
 23
 11000
(CQ33211)
114. Security log Medium
No indication is given of SNMPv3 authentication failure.
(CQ34420)
115. Security log Changing a password via SNMP will be logged with address Low
0.0.0.0.
(CQ33837)
116. Security log In the security log, all changes performed from either Telnet Low
or terminals are recorded as “CLI”. No distinction is made.
(CQ33835) First user login is recorded. The
117. Security log No record is made of the first time the password is changed, Low password is always changed in
upon first user login. this case.
Security log in extension units will not record the user name
118. Security log in the case of a user changing the system time from the Low Refer to the main unit‟s log.
main unit.
(CQ33131)
119. Security log If the security log is very long, the command prompt will not Low
appear until a few seconds after viewing the log.

®

Units in a nodal configuration
require the operational main unit
to load. A defective T-card
(CQ24061) prevents the main unit from
Nodal being fully operational.
120. A defective T-card in the main board will cause other units in Low
configuration
the node not to boot properly. An indication is given in the
event log: “db init failure” and a
corresponding alarm is given.
In this case, replace the T-card.
(CQ22864)
In a 1+1 configuration which includes end-point interfaces of Switch all trails to their primary
SNCP and 1+1
121. path-protected trails, rebooting the standby unit may cause Low interface before performing a
protection
traffic to be disrupted for about 150ms for trails for which reset to the standby unit.
active interface is the secondary interface.
(CQ25609) Otherwise MIB compilation may
122. SNMP Low
The MIB requires SMIv2 support in the MIB browser. fail.
(CQ26662) Traps will start being sent after

123. SNMP After changing from SNMPv3 to v1, heartbeat traps will not Low full reconfiguration (about 10
be sent for a few minutes. minutes).
(CQ26609)
When changing OID via SNMP, the system will not return a
124. SNMP Low
result before performing the action (the result is sent with
new OID).
(CQ33513)
Invalid option (-1) is available for parameters
125. SNMP genEquipTdmTrailSrcType, genEquipTdmTrailDest1Type Low Ignore the invalid option.
and genEquipTdmTrailDest2Type - invalid option
(Unknown).
(CQ33275)
See the MIB browser reference
126. SNMP In some MIB browsers, the end of line symbol “\n” will be Low
documentation.
displayed in a different way.
(CQ32945)
In Single Pipe mode, the parameter
127. SNMP Low
genEquipEthernetSwitchQoSStaticMacVlanId will take the
value “4091” in the case of untagged MAC addresses.
(CQ41574)
Mismatch between CLI and MIB parameter
genEquipDiversityPrimaryRadio. In CLI, possible options Take into account the
128. SNMP are Local radio and Mate radio. In the MIB the options are Medium differences when configuring this
different: parameter via SNMP.
Lower radio (MIB) = Local radio (CLI)
Upper radio (MIB) = Mate radio (CLI)

®

(CQ20641)
MG-Soft SNMP browser version 11 might fail displaying
SNMP, MG-Soft SNMPv3 heartbeat traps (the probability of this behavior Indications are that this is an
129. Low
Browser increases as the number of elements sending heartbeat MG-Soft version 11 issue.
traps increases). When using the same browser with
SNMPv1, all traps are displayed.
(CQ33451)
130. Space Diversity A traffic hit occurs when the IDU configuration is changed Low
from no diversity to Space Diversity.
(CQ35616) Do not use Space Diversity with
131. Space Diversity In Space Diversity, there can occasionally be errors in one Medium scripts which capacity is lower
of the links when the capacity is lower than 40Mbps. than 40Mbps.
(CQ24350)
If J0 string length is set to one character and the remote
Set both sides of the STM-1/OC-
132. STM-1/OC-3 system sends 15 characters, the first character only is Low
3 link to the same J0 settings.
compared and the received J0 string will show all 15
characters.
In E1/DS1 systems, changing between KLM mapping
Reset the system after changing
133. STM-1/OC-3 modes requires a system reset, even though the system Low
KLM modes.
gives no such prompt.
(CQ25832)
STM-1/OC-3 AIS If TU-AIS is being sent (due to trail signal failure), when VC Enable or disable VC AIS
134. Low
signaling AIS signaling is disabled, the TU-AIS will not be cleared signaling again.
even if the signal failure condition is cleared.
(CQ26717)
135. STM-1/OC-3 sync When synchronized to an outgoing VC, STM-1/OC-3 Medium
frequency may be offset by up to 0.6ppm.
(CQ26740)
Do not use SNCP trails to
When synchronized to an outgoing VC coming from an
136. STM-1/OC-3 sync Low synchronize the STM-1/OC-3
SNCP trail, an “STM-1 clock source signal failure” alarm is
interface.
raised
(CQ25728)
The Web-Based EMS interface will not be shown properly if
137. SW downgrade Medium Upgrade/downgrade using CLI.
the main unit is downgraded to an older software version
(while the extensions remain in the new version).

®

 Download “downgrade”
version to main IDU using
“new version” buttons and
then upgrade normally.
(CQ24958)
 Remove the unit with the
Occasionally, SW updates to the current version in
138. SW upgrade Medium old SW version from the
extension units from SW version 3.0.97, 3.0.99 in a nodal
nodal enclosure, and
configuration will fail.
upgrade it as a standalone
unit. After this has been
done, re-insert the unit in
the nodal enclosure.
Perform the following procedure
using the CLI:
1. 1. „mng-software>verify-
(CQ26323) packages‟ indicates
absence of net-snmp
139. SW upgrade A very rare failure in the RPM mechanism may cause a SW Medium package.
upgrade to fail.
2. 2. „mng-software>package-
install net-snmp-5.3.2.3-
6a.e300c2.rpm' recovers
system completely.
(CQ27034)
Updating the software when the system clock is in the past Update the system clock and
140. SW upgrade may cause a “backup kernel running” alarm to be raised. Medium install a “downgrade” version of
This is caused by the backup kernel having a more recent software.
time than the running kernel.
This happens because versions
Upgrading software from versions earlier than 6.6.1 may 6.6.1 and above, require a
result in a license violation alarm. This may result in a loss license for network resiliency
141. SW upgrade of in-band management, as license violation sets 2 Mbps High features. A possible workaround
policer on the radio port, for a time until the license violation is to set the Management VLAN
alarm is cleared. to the high priority queue before
upgrading.
(CQ34398)
Use a dedicated interface for
Using a TDM trail as synchronization source gives
142. Sync Medium synchronization input whenever
considerably degraded performance relative to using a
possible.
dedicated TDM interface.
In the case of stubs because of
(CQ33190) “Y” cables, test the performance
143. Sync Wander performance may be affected by the use of “Y” Medium and change cables before
cables. starting actual use of the
synchronization signal.
(CQ34750)
Delete all synchronization
144. Sync Removing a T-card or changing its type while there are Low configurations from the T-card
synchronization interfaces defined in it will cause a
before removing it.
permanent alarm.

®

(CQ31896)
It is possible to configure the following unsupported options:
Refrain from configuring the
 Synchronization VC on SNCP/ABR trail.
system in this manner.
145. Sync  Change trail used for synchronization to reserved (there Low Frequency will not be properly
is also no warning). transferred.
 Delete a trail used for synchronization (there is also no
warning).
(CQ35464) Synchronize the carrier 155MHz
When transferring frequency outwards using a STM-1/OC3 signal to the outgoing
146. Sync Low
VC, if the outgoing STM-1/OC-3 signal is not synchronized synchronization VC for best
to the synchronization VC, performance (wander) is poor. results.
(CQ34337)
When a GbE interface is selected as the synchronization An alarm indicating LOC in the
147. Sync High
source, no alarm indicating loss of synchronization source GbE port will be raised.
will be raised upon Loss of Carrier (LOC) in the GbE port.
(CQ22261)
For scripts with a given capacity (x trails), and wide way-
If the wayside channel is wide,
side channel, the system will allow configuration of trail#x
148. TDM trails Low always configure one trail less
even though there is no capacity for it (since it is taken by
than the total capacity per radio.
the wayside channel).
Traffic for that trail will not pass.
(CQ22917)
In standalone mode, deleting all trails and configuring
Ignore this error message or
default trails in CLI (using the command add-def-trails) will
149. TDM trails Low configure the trails using the
cause an incorrect error message to be shown, even though
Web-Based EMS.
the trails are properly configured:
Invalid Trail: Invalid Destination Interface Number
Configure trails in a stable
(CQ25748)
situation, with either both units
150. TDM trails Trail configuration will fail if the standby unit is undergoing a Low
operational, or the standby unit
reset.
off.
(CQ27814) When changing T-card type,
Trail configuration will be corrupted if any trails were make sure no trails are
151. TDM trails Low
configured to a certain T-card type and the T-card type is configured and then reset the
changed. system.
(CQ41532)
When using the traffic priority feature, TDM trails on the
radio interface should be configured from the first VC in TDM trails on the radio interface
152. Traffic priority ascending order. Otherwise, an alarm indicating “Trails Medium should be configured from the
mapped to inexistent interfaces” will be raised, although first VC in ascending order.
there is enough capacity in the radio channel to populate the
configured trails.

®

(CQ54869)
While allocating traffic priority,
153. Traffic priority If wide Wayside channel is enabled, it takes 2Mbps capacity Low
take into account wide WSC.
from the TDM traffic.
(CQ20902)
154. Wayside Low
Changing wayside capacity will cause an E1/DS1 error hit.
(CQ35372) No traffic or management is
Managing a system via out-of-band management using the affected. Refrain from intensively
155. Wayside wayside channel in HSB configurations may cause Low using wayside as a channel for
communications between protection mates to fail management in HSB
intermittently. configurations.
 Upgrade all units in the

node before inserting the
new extension unit.
(CQ34223)
 Downgrade the new
156. Web If an extension unit with version 6.7 or later is inserted and Medium extension unit before
the main unit is running version 6.6GA, Web-Based EMS
inserting it into the node.
display is lost for the main unit.
 Use the CLI to install the
same SW version in all
units.
(CQ32436)
Selecting a certain E1/DS1 interface to take the system‟s Click the Refresh and Apply
157. Web sync source as reference, and then rapidly changing it to Medium buttons and the specific E1/DS1
“local clock” will cause the interface not to be available in interface will reappear in the list.
drop-down lists for a few minutes.
Cable disconnection during RFU upload will display the Another upload will resolve this
158. Web Low
download as if it were continuing. issue.
Creating a unit configuration using the Web-Based EMS
159. Web Low Re-open the Web-Based EMS.
takes 3.5 minutes, and connection to the EMS may be lost.
(CQ11057 / 12684) Instead of using F5 to refresh,
160. Web Using refresh via F5 in Windows Explorer or Mozilla Firefox Low use the refresh button in the
will log out of the Web-Based EMS. Web-Based EMS.
Delete Internet Temp Files

(CQ 15653)
(Clear Cache/Cookie) in the web
161. Web When upgrading or downgrading SW, the Main View page Low
browser, and reopen the Main
might display the older Main View.
View page.
(CQ16436/15845/15845/15957/18202/19523/19574)
WEB response issues:
 Refreshing the browser page by pressing F5 returns an
unexplained error. Close and then reopen the Web-
162. Web  Invalid text appears in the web browser. Low Based EMS, or refresh by
 The unit‟s tree does not appear at the left side of the pressing Ctrl+F5 and re-login.
page.
 The errors message "Cannot open the Internet site"
appears.

®

(CQ19509/19813/20001/20005)
Web browser window size issues that might appear when
window size is less than 100%:
These web issues are related to
 Might not be possible to create an archive
163. Web Low the web browser. Only window
configuration.
size of 100% should be used.
 Might not be possible create archive unit-info.
 Gibberish in the window.
 Improper appearance of tables.
(CQ26556)
164. Web In case of constant protection switches due to link problems, Low Display problem only.
the Web-Based EMS may show both units as active.
(CQ25741)
Press OK when prompted and
165. Web On rare occasions, a user will be logged out after Low
continue normally.
performing a single action.
(CQ26542)
Click on the desired slot
166. Web On rare occasions, two slots are marked as selected at the Low
normally.
same time.
(CQ29745)
On rare occasions, when performing a manual switch from Refresh the page to make sure
167. Web the Web-Based EMS, the message “operation failed” will be Low
the switch was performed.
shown even though the operation actually succeeds and the
system switches.
(CQ34608) This is caused by the browser‟s
168. Web After upgrading the SW version, the web browser shows an Low cache. Refresh the page by
old screen and company logo. pressing <Ctrl> +F5.
(CQ43773)
Refresh solves the problem.
169. Web Synchronization page in the web is sometimes not displayed Medium
Does not happen with IE9.
properly in IE8.
(CQ43353)
In HSB protected link with floating IP, Web management
170. Web & Floating IP Low Internet Explorer works fine.
may not be accessible through the floating IP address when
resetting the active IDU and using Firefox browser.
(CQ28033) If XPI is greater than 45dB,
171. XPIC When XPI in a link is 45-46dB the XPI level shown is inexact Low assume the link‟s XPI is actually
(a normal range is between 20-26dB). worse than that.

Ceragon Manual

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Ceragon Manual

Diunggah oleh

Hak Cipta:

Format Tersedia

FibeAir® IP-10G and IP-10E

6.9 Release Notes

Copyright © 2012 by Ceragon Networks Ltd. All rights reserved.

2. Supported Systems and Configurations......................................................... 8

3. Software and Hardware Configurations and Compatibility ......................... 14

4. NSV Content ................................................................................................... 17

Ceragon Proprietary and Confidential Page 2 of 56

Open Source Statement

Ceragon Proprietary and Confidential Page 3 of 56

1.1 IP-10 Introduction

1.2 6.9.2 Version Introduction

Ceragon Proprietary and Confidential Page 4 of 56

to an officially released version while in standalone mode rather than in a

Ceragon Proprietary and Confidential Page 5 of 56

1.3 Project Release History

# NSV SW Version & Date Main Features Notes

3 6.6.0.0.1.40 Jan 2010 IP -10G product release I6.6ca1

5 6.6.0.0.2.51 March 2010 IP -10G product release I6.6GA E1s only

6 6.6.0.0.2.53 March 2010 IP -10G product release I6.6GA

7 6.6.1.0.0.71 August 2010 IP -10G product release I6.6.1

8 6.6.1.0.0.22 October 2010 IP -10G product release I6.6.2

9 6.7.0.0.0.93 February 2011 IP -10G product release I6.7

10 6.7.1.0.0.4 April 2011 IP -10G product release I6.7.1 Scripts only

11 6.7.2.0.0.3 June 2011 IP -10G product release I6.7.2 NeraTel support

12 6.8.0.0.0.58 October 2011 IP -10G product release I6.8

13 6.9.0.1.0.41 May 2012 IP-10G product release I6.9

14 6.9.0.1.0.42 August 2012 IP-10G product release I6.9 Correction of FCS

15 6.9.2.0.0.14 November 2012 HSB revertive mode, SNMP IP forwarding,

1.4 Synonyms and Acronyms

AIS Alarm Indication Signal

Ceragon Proprietary and Confidential Page 6 of 56

DST Daylight Saving Time

Ceragon Proprietary and Confidential Page 7 of 56

RSL Received Signal Level

2. Supported Systems and Configurations

2.1 Supported Radio Configurations

# Modem Script Bit Rate Channel Spacing Modulation ETSI/FCC

Ceragon Proprietary and Confidential Page 8 of 56

# Modem Script Bit Rate Channel Spacing Modulation ETSI/FCC

18. ACM-42Mbps-6.5MHz 10 – 42 7 (6.5) QPSK – 256QAM ETSI

19. ACM-59Mbps-9MHz 13 - 59 10 (9) QPSK – 256QAM FCC

20. ACM-61Mbps-9MHz 13 - 61 10 (9) QPSK – 256QAM FCC

21. ACM-87Mbps- 21 – 87 14 (12.5) QPSK – 256QAM ETSI

Ceragon Proprietary and Confidential Page 9 of 56

# Modem Script Bit Rate Channel Spacing Modulation ETSI/FCC

23. ACM-124Mbps-18MHz 27– 124 20 (18) QPSK – 256QAM FCC

25. ACM-181Mbps- 38 - 181 28/30 (26.5) QPSK – 256QAM ETSI/FCC

26. ACM-185Mbps-27MHz 39 - 185 28/30 (27) QPSK – 256QAM ETSI/FCC

27. ACM-194Mbps-28MHz 42 - 194 28/30 (28) QPSK – 256QAM ETSI/FCC

28. ACM-198Mbps-28MHz 39- 198 30 (28) QPSK – 256QAM FCC

33. XPIC-ACM-180Mbsp- 40-180 28/30 (26.6) QPSK – 256QAM ETSI/FCC

Ceragon Proprietary and Confidential Page 10 of 56

# Modem Script Bit Rate Channel Spacing Modulation ETSI/FCC

Ceragon Proprietary and Confidential Page 11 of 56

 The second ACM radio script that appears in line 24 is an enhanced

Ceragon Proprietary and Confidential Page 12 of 56

2.2 Supported Configurations

# Configuration Supported Notes

Ceragon Proprietary and Confidential Page 13 of 56

3. Software and Hardware Configurations and

3.1 Supported Hardware Configurations

3.2 Supported Licensing Configurations

Ceragon Proprietary and Confidential Page 14 of 56

3.3 IDU-ODU/RFU Compatibility