Ceragon FibeAir IP-20 Split-Mount Release Notes 10.0 Rev B.10 PDF

Release Notes
FibeAir® IP-20 CeraOS 10.0

All-Indoor and Split-Mount
Products:
FibeAir IP-20F, FibeAir IP-20G,
FibeAir IP-20GX, FibeAir IP-20N,
FibeAir IP-20A, FibeAir IP-20LH,
and Evolution IP-20LH
June 2018 | Revision B.10
© Copyright 2018 by Ceragon Networks Ltd. All rights reserved.
Release Notes for CeraOS 10.0: FibeAir® IP-20 All-Indoor and Split-Mount Products
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.
Trademarks
Ceragon Networks®, FibeAir® and CeraView® are trademarks of Ceragon Networks Ltd., registered in
the United States and other countries.
Ceragon® is a trademark of Ceragon Networks Ltd., registered in various countries.
CeraMap™, PolyView™, EncryptAir™, ConfigAir™, CeraMon™, EtherAir™, CeraBuild™, CeraWeb™, and
QuickAir™, 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 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 ("Open Source License"). Inasmuch that such software is being used, it is released
under the Open Source License, accordingly. The complete list of the software being used in this
product including their respective license and the aforementioned public available changes is
accessible at:
Network element site: ftp://ne-open-source.license-system.com
NMS site: ftp://nms-open-source.license-system.com/
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.
Intended Use/Limitation
Fixed point-to-point radio links for private networks.
Authorized to Use
Only entities with individual authorization from the National Regulator to operate the mentioned
radio equipment.
The equipment can be used in the following EU countries:
Austria (AT) - Belgium (BE) - Bulgaria (BG) - Switzerland/Liechtenstein (CH) - Cyprus (CY) - Czech Republic (CZ) -
Germany (DE) – Denmark (DK) - Estonia (EE) - Finland (FI) - France (FR) -Greece (GR) - Hungary (HU) - Ireland (IE)
– Iceland (IS) – Italy (IT) – Lithuania (LT) - Luxembourg (LU) – Latvia (LV) - Malta (MT) - Netherlands (NL) - Norway
(NO) - Portugal (PT) - Romania (RO) - Sweden (SE) - Slovenia (SI) - Slovak Republic (SK) – United Kingdom (UK) –
Spain (SP) – Poland (PL)
Page 2 of 129
Ceragon Proprietary and Confidential

Table of Contents
1. Introduction.............................................................................................................. 6
1.1 Product Overview ........................................................................................................................ 7
1.1.1 FibeAir IP-20F ............................................................................................................................... 7
1.1.2 FibeAir IP-20G .............................................................................................................................. 7
1.1.3 FibeAir IP-20GX ............................................................................................................................ 8
1.1.4 FibeAir IP-20N .............................................................................................................................. 8
1.1.5 FibeAir IP-20A .............................................................................................................................. 8
1.1.6 FibeAir IP-20LH............................................................................................................................. 9
1.1.7 Evolution IP-20LH ......................................................................................................................... 9
1.2 CeraOS 10.0 Introduction and Highlights ................................................................................... 10
1.3 Release History .......................................................................................................................... 11
2. Software Package ................................................................................................... 27

2.1 MIB File Names and Versions .................................................................................................... 28
3. New Products and Features ..................................................................................... 29

3.1 FibeAir IP-20F ............................................................................................................................. 29
3.2 FibeAir RFU-D ............................................................................................................................. 29
3.3 FibeAir RFU-D-HP ....................................................................................................................... 30
3.4 FibeAir RFU-E ............................................................................................................................. 30
3.5 FibeAir RFU-S ............................................................................................................................. 31
3.6 RIC-D .......................................................................................................................................... 31
3.7 Configurable Timeout for Trap Generation ............................................................................... 33
3.8 Radio Traffic PM Threshold Configuration via SNMP ................................................................ 33
3.9 No Reset after Changing the Minimum or Maximum ACM Profile ............................................ 33
4. Feature Release Notes ............................................................................................ 34

5. Radio Scripts ........................................................................................................... 40
5.1 Supported ETSI Microwave MRMC Scripts for FibeAir Products ............................................... 40
5.1.1 ETSI MRMC Scripts Supported with RMC-A in FibeAir IP-20N and IP-20GX .............................. 40
5.1.2 ETSI MRMC Scripts Supported with FibeAir IP-20N (RMC-B only), IP-20G, and IP-20GX........... 41
5.1.3 ETSI MRMC Scripts Supported with FibeAir IP-20F or FibeAir IP-20N (RIC-D only) and RFU-D,
RFU-D-HP, and RFU-S ................................................................................................................. 42
5.2 Supported FCC Microwave MRMC Scripts for FibeAir Products ................................................ 43
5.2.1 FCC MRMC Scripts Supported with RMC-A in FibeAir IP-20A and IP-20GX ............................... 43
5.2.2 FCC MRMC Scripts Supported with FibeAir IP-20A (RMC-B only), IP-20G, and IP-20GX ........... 43
5.2.3 FCC MRMC Scripts Supported with FibeAir IP-20F or FibeAir IP-20A (RIC-D only) and RFU-D,
RFU-D-HP, and RFU-S ................................................................................................................. 44
5.3 Supported MRMC E-Band Scripts for FibeAir IP-20F, IP-20N, or FibeAir IP-20A and RFU-E ...... 45
5.4 Supported SRMs and Frequency Bands for Evolution IP-20LH Systems .................................... 45
5.5 Radio Options for FibeAir IP-20 Products .................................................................................. 48
Page 3 of 129

5.6 Radio Options for Evolution IP-20 Systems................................................................................ 49

5.6.1 Supported XCVRs ....................................................................................................................... 49
5.6.2 Supported ODUs ........................................................................................................................ 49
6. Interoperability with other Ceragon Products .......................................................... 50

6.1 FibeAir IP-20N and IP-20A Interoperability with other Ceragon Products ................................ 50
6.2 Evolution IP-20LH Interoperability with other Ceragon Products ............................................. 50
6.3 IP-20F Interoperability with other Ceragon Products ................................................................ 51
6.4 IP-20G Interoperability with other Ceragon Products ............................................................... 51
6.5 IP-20GX Interoperability with other Ceragon Products ............................................................. 51
7. Version Upgrade Compatibility ................................................................................ 52

7.1 Version Upgrade Compatibility for Chassis-Based Products ...................................................... 53
7.2 Version Upgrade Compatibility for IP-20F ................................................................................. 55
7.3 Version Upgrade Compatibility for FibeAir IP-20G .................................................................... 56
7.4 Version Upgrade Compatibility for FibeAir IP-20GX .................................................................. 58
8. NMS Version Compatibility ..................................................................................... 59

8.1 NMS Version Compatibility for Chassis-Based Products ............................................................ 59
8.2 NMS Version Compatibility for IP-20F ....................................................................................... 60
8.3 NMS Version Compatibility for IP-20G ....................................................................................... 60
8.4 NMS Version Compatibility for IP-20GX..................................................................................... 61
9. Resolved Issues ....................................................................................................... 62

9.1 Ethernet ..................................................................................................................................... 62
9.2 Platform ..................................................................................................................................... 62
9.3 Radio .......................................................................................................................................... 62
9.4 Synchronization ......................................................................................................................... 62
9.5 TDM – Native ............................................................................................................................. 62
10. Notes and Limitations ............................................................................................. 63

10.1 Ethernet ..................................................................................................................................... 63
10.2 Platform ..................................................................................................................................... 71
10.3 Radio .......................................................................................................................................... 87
10.4 Synchronization ......................................................................................................................... 96
10.5 TDM – Native ............................................................................................................................. 99
10.6 TDM – Pseudowire ...................................................................................................................101
11. Open Bugs ............................................................................................................ 102

11.1 Ethernet ...................................................................................................................................102
11.2 Platform ...................................................................................................................................102
Page 4 of 129

11.3 Radio ........................................................................................................................................103

11.4 Synchronization .......................................................................................................................104
11.5 TDM – Native ...........................................................................................................................104
11.6 TDM – Pseudowire ...................................................................................................................104
12. Synonyms and Acronyms ...................................................................................... 105

13. Annex A - System Configurations ........................................................................... 108
13.1 FibeAir IP-20N and IP-20A System Configurations ...................................................................108
13.1.1 Configurations based on RMC with RFU-C, RFU-A, and 1500HP/RFU-HP................................108
13.1.2 Configurations based on RIC-D with RFU-D, RFU-D-HP, RFU-E, and RFU-S .............................109
13.2 Evolution IP-20LH System Configurations ................................................................................110
13.3 FibeAir IP-20F System Configurations ......................................................................................111
13.4 FibeAir IP-20G System Configurations .....................................................................................112
13.5 FibeAir IP-20GX System Configurations ...................................................................................112
13.6 Hardware Options for Chassis-Based Systems .........................................................................113
13.6.1 TCC Options..............................................................................................................................114
13.6.2 RMC and RIC-D Options ...........................................................................................................115
13.6.3 FibeAir IP-20N and IP-20A 1RU and 2RU Scalability ................................................................115
13.6.4 Evolution IP-20LH 1RU and 2RU Scalability .............................................................................116
13.6.5 Card Types Allowed Per Slot – 1RU/2RU .................................................................................116
13.6.6 TCC GE Interface Limitations ....................................................................................................117
13.6.7 Adjacent Pair Guidelines ..........................................................................................................117
13.6.8 Slot Sections and 2.5 Gbps Mode ............................................................................................118
13.6.9 Additional Slot Guidelines ........................................................................................................120
13.7 Hardware Assembly Options for FibeAir IP-20F .......................................................................121
13.8 Hardware Assembly Options for FibeAir IP-20G ......................................................................122
13.9 Hardware Assembly Options for FibeAir IP-20GX ....................................................................123
13.9.1 IP-20GX Hardware Assemblies .................................................................................................123
13.9.2 IP-20GX Expansion Slot Options...............................................................................................123
13.10 Approved SFP Modules for IP-20 IDUs .....................................................................................124
14. Annex B – Supported Ciphers for Secured Communication Protocols ...................... 126
15. Annex C: Main IP-20F Features in Release 10.0 ...................................................... 128
Page 5 of 129

1. Introduction
This Release Notes document describes CeraOS 10.0, which significantly expands
the FibeAir IP-20 product portfolio and provides customers with a greater and
more diverse palette from which to select the elements of their network. CeraOS
10.0 makes MultiCore technologies available in split-mount nodes by introducing
two new MultiCore RFUs, the RFU-D and the high-power RFU-D-HP. CeraOS 10.0
also enables the use of E-Band radio technology in split-mount nodes, and opens
up the possibility of building Multiband nodes by combining Microwave and E-
Band radios in a single IP-20N or IP-20A aggregation node.
The FibeAir and Evolution IP-20 series includes a variety of high-capacity wireless
backhaul products. The IP-20 series provides backhaul solutions that can be used
separately or combined to form integrated backhaul networks or network
segments.
The IP-20 series can be categorized by the following general node configuration
types:
• All-Indoor – An all-indoor node consists of an Indoor Unit (IDU) and one or
more Radio Frequency Units (RFUs), both of which are placed in an indoor
location. Each radio interface on the IDU is connected to an RFU via a Radio
Modem Card (RMC) or Radio Interface Card (RIC), and each RFU is connected
to an antenna via a flexible waveguide.
• Split-Mount – A split-mount node consists of an IDU and one or more RFUs,
where the RFUs are located outdoors and connected to their antennas using
either a direct mount or a remote mount via a flexible waveguide.
• All-Outdoor – An all-outdoor node consists of a unit in which the IDU and RFU
functionality is combined in a single unit. This unit is located outdoors and is
connected to one or more antennas, using either a direct mount or a remote
mount via a flexible waveguide.
This Release Notes document covers the IDU-based IP-20 products used in all-
indoor and split-mount nodes. These products are:
• FibeAir IP-20F
• FibeAir IP-20G
• FibeAir IP-20GX
• FibeAir IP-20N
• FibeAir IP-20A
• Evolution IP-20LH
The all-outdoor IP-20 products (IP-20C, IP-20C-HP, IP-20S, IP-20E, and IP-20V) are
covered in a separate Release Notes document.
For purposes of brevity, the following abbreviations are sometimes used in this
document to indicate applicability to certain products or groups of products:
• All – All of the IP-20 products covered in this document, as listed above.
• Chassis-based products – FibeAir IP-20N, IP-20A, and Evolution IP-20LH.
• FA – FibeAir.
• Evo – Evolution IP-20LH.
Page 6 of 129

1.1 Product Overview

This section provides a brief overview of the IP-20 products described in this
document. A separate Technical Description is available for each product,
providing a full description of the individual product and its specifications.
1.1.1 FibeAir IP-20F

FibeAir IP-20F is a split-mount edge node that delivers multi-Gbps radio capacity
to the transport network. It provides operators with the simplicity that comes
with deploying a very compact, fixed configuration node, helping operators to
meet their operational efficiency targets.
An IP-20F IDU contains:
• 4 x 1 GbE combo interfaces (GbE 1-4/SFP 1-4)
• 1 x 2.5/1 GbE combo interface (2.5GE6/SFP6)
• Two combo (RJ-45 or SFP) radio interfaces (RFU1 and RFU 2)
• 1 x radio or 2.5/1 GbE combo interface (RFU3/SFP5, RFU3/2.5GE5)
Notes: In CeraOS 10.0, only one radio interface can be used per IP-20F unit.
When used with a MultiCore RFU (RFU-D or RFU-D-HP), this interface
can support two radio carriers. However, the second carrier must
part of a Multi-Carrier ABC group in order to be utilized.
Also, in CeraOS 10.0, up to four Ethernet interfaces can be used (GbE

1-4/SFP 1-4).
For TDM traffic, IP-20F includes a 16 x E1/DS1 interface. IP-20F is hardware-ready
for future support of two STM-1/OC-3 interfaces via a rear-mounted module.
IP-20F can be used with MultiCore RFU-D, MultiCore high-power RFU-D-HP,
E-Band RFU-E, and single core RFU-S.
1.1.2 FibeAir IP-20G

FibeAir IP-20G is a compact, split-mount hauling solution for edge and ring nodes.
Its fixed configuration and low power consumption make it simple to install and
maintain. Hosting the common capabilities of the IP-20 platform, it provides a
cost-effective, reliable, and flexible hauling solution. IP-20G provides one or two
radio interfaces, six Ethernet interfaces, and optionally a 16-channel E1/T1
interface.
IP-20G can be used with RFU-C, 1500HP/RFU-HP, and RFU-A.
Page 7 of 129

1.1.3 FibeAir IP-20GX

FibeAir IP-20GX is based on the same architecture and technology as FibeAir
IP-20N and IP-20G, and supports essentially the same feature set. IP-20GX takes
the compact form factor of IP-20G, sized to fit in a single rack unit, and adds two
slots for additional TDM line cards or radio modem cards. IP-20GX includes a dual-
feed power interface which can be connected to separate power supplies for
power redundancy.
IP-20GX can be used with RFU-C, 1500HP/RFU-HP, and RFU-A.
1.1.4 FibeAir IP-20N

FibeAir IP-20N is a highly modular and flexible cellular backhaul product that is
optimized for nodal deployment, with a small footprint, high density, and a high
degree of scalability and availability. An IP-20N product is based on a chassis,
which is provided in sizes that fit a single rack unit or two rack units, and which
contains five or ten slots for any mix of Ethernet, TDM, and radio cards.
With RIC-D, the new Radio Interface Card released in CeraOS 10.0, IP-20N can be
used with MultiCore RFU-D, MultiCore high-power RFU-D-HP, E-Band RFU-E, and
single core RFU-S.
With RMC-B and RMC-A, IP-20N can be used with RFU-C and 1500HP/RFU-HP.
IP-20N can be used in configurations that combine microwave RFUs with the E-
Band RFU-E in the same node.
IP-20N is suitable for both short-haul and long-haul applications. Long-haul
networks can easily be built by deploying nodes consisting of IP-20N IDUs using
RFU-D-HP, RFU-HP, or 1500HP high-power RFUs to achieve high-capacity multi-
carrier networks.
1.1.5 FibeAir IP-20A

Designed uniquely for the North American market, FibeAir IP-20A enables
operators to deploy high capacity, long-haul microwave systems in locations
where rack space and shelter real-estate are limited. IP-20A is based on the IP-
20N hardware and software package, customized to operate according to ANSI
(FCC) standards.
With RIC-D, IP-20A can be used with MultiCore RFU-D, MultiCore high-power
RFU-D-HP, E-Band RFU-E, and single core RFU-S.
With RMC-B and RMC-A, IP-20A can be used with RFU-C, RFU-A, and 1500HP/RFU-
HP.
IP-20A can be used in MultiBand configurations that combine microwave RFUs
with the E-Band RFU-E in the same node.
IP-20A is suitable for both short-haul and long-haul applications. Long-distance
networks can easily be built by deploying nodes consisting of IP-20A IDUs using
RFU-D-HP, RFU-A, RFU-HP, or 1500HP high-power RFUs to achieve high-capacity
multi-carrier networks.
Page 8 of 129

1.1.6 FibeAir IP-20LH

FibeAir IP-20LH is a versatile and cost-effective microwave radio solution for long
distance, high capacity multi-carrier telecommunication networks using the RFU-
HP and 1500HP High Power radios. Offering superior quality and fast deployment
capabilities, it is ideal for rapid and economical network rollouts. FibeAir IP-20LH
is based on the IP-20 hardware and software package, customized for multi-
carrier long-haul networks.
From CeraOS 10.0, FibeAir IP-20LH is integrated into FibeAir IP-20N, and supports
the same feature set as FibeAir IP-20N.
1.1.7 Evolution IP-20LH

Evolution IP-20LH combines the IP-20N IDU with one or more RMC-E radio
modem cards and Evolution LH transceivers (XCVRs), to provide a versatile and
cost-effective microwave radio solution for long distance, high capacity
telecommunication networks. The Evolution XCVR is a high transmit power
transceiver designed for long-haul applications with multiple carrier traffic.
Evolution’s patented dynamic biasing technology enables it to deliver high
transmit power with low power consumption and low heat dissipation.
Page 9 of 129

1.2 CeraOS 10.0 Introduction and Highlights

CeraOS software version 10.0 is a General Availability (GA) release that introduces
a significantly expanded set of capabilities to the FibeAir IP-20 line of products.
CeraOS 10.0 introduces a new family of RFUs that significantly increase the
versatility of the FibeAir IP-20 split-mount solution, including E-band coverage,
enhanced channel spacing of up to 112 MHz for microwave frequencies and 250
MHz for E-band frequencies, modulation up to 4096 QAM, and MultiCore feature
support:
• FibeAir RFU-D – MultiCore RFU that operates in the 6-42 GHz frequency
range, supporting channel bandwidth of 14-112 MHz and modulations of BSPK
to 4096 QAM.
• FibeAir RFU-D-HP – High-Power MultiCore RFU that operates in the 4-11 GHz
frequency range, supporting channel bandwidth of 14-112 MHz and
modulations of BSPK to 4096 QAM.
• FibeAir RFU-E – Operates in the E-band frequency range, supporting 71-76
GHz and 81-86 GHz frequencies, channel bandwidth of 14, 28, 62.5, 125, and
250 MHz, and modulations of BSPK to 1024 QAM.
• FibeAir RFU-S – Operates in the 6-42 GHz frequency range, supporting channel
bandwidth of 14-112 MHz and modulations of BSPK to 4096 QAM.
These RFUs can be used with FibeAir IP-20N, FibeAir IP-20A, and the newly
introduced FibeAir IP-20F IDUs. A new Radio Interface Card (RIC), the RIC-D, is also
introduced with CeraOS 10.0. RIC-D provides the interface between the IP-20N or
IP-20A and the new RFUs. RIC-D includes two electrical and two optical interfaces
to the RFU (RFU interface).
Note: In CeraOS 10.0, a single radio interface (RFU interface) can be used
per RIC-D.
In addition, Version 10.0 introduces the following CeraOS features:
• Configurable Timeout for Trap Generation
• Radio Traffic PM Threshold Configuration via SNMP
• No reset after changing the minimum or maximum ACM profile
For further details about the new RFUs, IP-20F, and RIC-D, see New Products and
Features on page 29.
CeraOS 10.0 does not support:
• IP-20 Assured platform
• FIPS 140-2
Page 10 of 129

1.3 Release History

The following table shows the software version release history for all-indoor and
split-mount products:
Table 1: Product Line Release History

Software Version Date Main Features/ FA FA Evo FA FA FA
and Applicability Changes IP-20N IP-20A IP-20LH IP-20G IP-20GX IP-20F1
10.0.0.0.162 May 2018 FibeAir IP-20F N N N N N Y

(GA)
FibeAir RFU-D Y Y N N N Y
FibeAir RFU-D-HP Y Y N N N Y
FibeAir RFU-E Y Y N N N Y
FibeAir RFU-S Y Y N N N Y
FibeAir RIC-D Y Y N N N N
Configurable Timeout for Trap Y Y Y Y Y Y
Generation
Radio Traffic PM Threshold Y Y Y Y Y Y
Configuration via SNMP
No reset after changing the minimum or Y Y Y Y Y Y
maximum ACM profile
9.7.0.0.0.144 January 2018 Link Aggregation Control Protocol Y Y Y Y Y
(CA) (LACP)
Current BER Level Display in Web EMS Y Y Y Y Y
New 5 GHz/14 MHz Scripts for Evolution N N Y N N
IP-20LH
9.5.0.0.0.192 November 1588 Boundary Clock Y Y Y Y Y
(CA) 2017
ASP Enhancements and Link Loss Y Y N Y Y
Forwarding (LLF)
Software Download via HTTP and HTTPS Y Y Y Y Y
Free Text User Comment Field in Unit Y Y Y Y Y
Parameters Page of Web EMS
G.8032 Ethernet Ring Protection with Y Y Y N N
Multiple Multi-Carrier ABC Groups
9.2.5.0.0.203 October 2017 1588 Boundary Clock Y Y N N N
(CA)
1
For features supported in the release of FibeAir IP-20F, see Annex C: Main IP-20F Features in
Release 10.0 on page 130.
Page 11 of 129


9.2.0.0.0.422 August 2017 New GA build for FibeAir IP-20E, Y Y Y Y Y

(GA) released for all IP-20 products to
preserve version unity.
9.2.0.0.0.417 June 2017 Unit & Radio Summary Page in Web Y Y Y Y Y
(GA) EMS
Alarm Statistics Page in the Web EMS Y Y Y Y Y
Quick Platform Setup Y Y Y Y Y
CeraPlan Service for Creating Pre- Y Y Y Y Y
Defined Configuration Files
10GE Interface Protection Y Y Y N N
Activation Key Reclaim Y Y Y Y Y
1588 Transparent Clock for FibeAir IP- N N N N Y
20GX
LAG Group Shutdown in Case of Y Y Y Y Y
Degradation Event
Enhanced LAG Distribution Y Y Y Y Y
RSL Threshold Alarm Y Y Y Y Y
2 X 2+2 HSB with BBS Space Diversity Y Y N N N
9.0.0.0.0.300 May 2017 Bug Fixes Y Y Y Y Y
(GA)
9.0.0.0.0.295 January 2017 10GE Ethernet Line Interface Card (LIC): Y Y Y N N
(GA) LIC-X-E10
Y.1731 Connectivity Fault Management Y Y Y Y Y
(CFM) Enhancements
FCC (ANSI) scripts and ANSI mode (DS1 N N N N Y
and OC-3) for FA IP-20GX
ATPC Override Timer Y Y N Y Y
1588 Transparent Clock with Multi- Y Y N N2 N
Carrier ABC
1+1 HSB protection with BBS Space N N N N Y
Diversity (SD) for FA IP-20GX
Configurable FTP/SFTP Port Y Y Y Y Y
Egress CoS Statistics in Web EMS Y Y Y Y Y
Asymmetrical Maximum Profile Y Y Y Y Y
2
Already supported.
Page 12 of 129


HSO enhancements – Improved Y Y Y N N

performance with TDM cards
8.7.0.0.0.166 December Resolves issue affecting SD and eMMC Y Y Y Y Y
(GA) 2016 cards in units that operate in Multi-
Carrier ABC mode
Improves the LAG distribution function Y N N N N
8.7.0.0.0.160 November N N N Y Y
(GA) 2016
8.7.0.0.0.155 October 2016 Support for LIC-STM1/OC3-RST cards Y Y Y N N
(GA) and LIC-STM1/OC3-RST interfaces in
RMC-E cards in multiple Multi-Carrier
ABC groups (Group 1 and Group 3)
Additional ping parameters Y Y Y N N
Quick Configuration Wizard for 2+2 Y Y N N N
HSB-SD links.
Unit Redundancy. N N N Y N
1588 Transparent Clock is supported N N N Y N
with Multi-Carrier ABC and XPIC scripts.
Hot Switchover (HSO) with TCC N N Y N N
Redundancy.
Ability to configure up to four Multi- N N Y N N
Carrier ABC groups in a single unit using
a TCC-B2-XG-MC.
Carrier ABC mode.
(GA) 2016
8.5.5.0.0.110 July 2016 Minimum ACM profile. Y Y N Y Y
(GA)
1+1 HSB card protection for LIC- Y Y N N N
STM1/OC3-RST cards
LAG redistribution in the event of RX Y Y N N N
failure
T3 as sync source. N N N N Y
Support for 2048 QAM (Profile 10) N N N N Y
modulations
External alarm output. Y Y Y Y Y
T3 as sync source (ETSI-only). N N N Y N
Page 13 of 129


8.5.0.0.0.288 July 2016 Y.1731 Connectivity Fault Management Y Y Y Y Y

(GA) (CFM)
Timeout for Trap Generation Y Y Y Y Y
Ethernet Line Protection for GB Y Y Y N N
interfaces with TCC Redundancy
Ability to configure up to four Multi- Y Y N N N
Carrier ABC groups in a single unit using
a TCC-B2-XG-MC (GA)
Hot Switchover (HSO) with TCC Y Y N N N
Redundancy (GA)
Russian-language option for Web EMS N N Y N Y
GUI.
Support for 5 MHz channels (ANSI/FCC). N N N N Y
Support for RMC-A in expansion slots N N N N Y
Support for Multi-Carrier ABC in fixed N N N N Y
(main board only) radio interfaces
Link ID mismatch blocking mode Y Y N Y Y
TDM 1+1 HSB Card Protection for LIC- N N Y N N
T16
8.3.7.0.0.120 May 2016 Ability to configure up to four Multi- Y Y N N N
(CA) Carrier ABC groups in a single unit using
a TCC-B2-XG-MC.
Hot Switchover (HSO) with TCC Y Y N N N
Redundancy.
TDM 1+1 HSB card protection for LIC-
T16
Support for electrical FE traffic Y Y N N N
interfaces with TCC Redundancy.
Russian-language option for Web EMS Y Y N Y N
GUI
Link ID mismatch blocking mode Y Y N Y N
Support for 5 MHz channels (ANSI/FCC). N Y N Y N
Carrier ABC mode.
(GA) 2016
Page 14 of 129


8.3.0.0.0.483 March 2016 Radio Payload encryption using AES- Y Y N Y Y

(GA) 256.
FIPS 140-2 (Available in IP-20 Assured N Y N Y Y
platforms)
XPIC support for 14 MHz channels Y N N Y Y
(MRMC 1209).
Web EMS wizard for creating Multi- Y Y Y Y N
Carrier ABC groups.
Web EMS wizard for creating 1+1 HSB- Y Y N Y N
SD links.
Support for 4 and 5 GHz frequency N N Y N N
bands by the following SRMs: 68, 69, 85,
128, 129, 132, 135, 139.
8.2.5.0.0.22 (GA) November Extends the capacity of the TCC-B2-XG- Y Y Y N N
2015 MC card to support a Multi-Carrier ABC
group with a capacity up to 2.5 Gbps.
1588-TC can be used together with Y Y N Y N
ACM.
1588-TC can be used in mixed radio Y Y N Y N
links with an IP-20G at one end of the
link and an IP-20N or IP-20-A unit at the
other end.
1588 Transparent Clock flows can be N N N Y N
configured on both radio ports of a
dual-radio IP-20G unit.
1588 Transparent Clock can be used N N N Y N
with LAG configurations; 1588 packets
can be passed via either radio carrier in
a dual-carrier unit.
8.2.0.0.0.342 January 2017 Resolves issue affecting SD and eMMC Y Y Y Y Y
(GA) cards in units utilizing the Multi-Carrier
ABC or Ethernet ring protection
(G.8032) functionality.
8.2.0.0.0.335 September Header de-duplication Y Y Y Y Y
(GA) 2015
Support for ACM Adaptive Transmit Y Y N Y Y
Power with RFU-A and with RFU-HP
New CLI commands for Y Y Y Y Y
adding/removing untagged VLANs to or
from service points
Miscellaneous bug fixes Y Y Y Y Y
Page 15 of 129


New TCC-B2-XG-MC card Y Y Y N N

Support for optical Ethernet ports on Y Y Y N N
TCC using an optical Y-splitter cable with
TCC Redundancy
Support for T3 clock input using Y- cable Y Y Y N N
with TCC Redundancy
Web EMS wizard for quick link setup of Y Y N Y Y
1+0 and 1+1 radio configurations
Support for RMC-A with 30 and 40 MHz N Y N N N
scripts (FCC)
Support for 1+0, 1+1 HSB, and 2+0 LAG Y Y N N N
links between IP-20N/IP-20A units using
RMC-A, and IP-10G R3 and IP-10E R3
units
Support for 1500HP N N N N Y
Support for 1+0 IP-20G/IP-20S radio N N N Y N
links, for specific scripts and
configurations
8.0.5.0.0.157 September IEEE-1588v2 – Transparent Clock Y Y Y
(GA) 2015
FA IP-20N
FA IP-20A
8.0.5.0.0.158
(GA)
FA IP-20G
8.0.5.0.0.157 August 2015 XPIC recovery response time Y Y Y Y Y
(GA): improvements
FA IP-20N
Additional OIDs for ifXtable Standard Y Y Y Y Y
FA IP-20A
MIB
Evo IP-20LH
8.0.5.0.0.158 Power Supply Unit (PSU)failure alarms Y Y Y Y Y
FA IP-20G (GA) Native TDM service alarms’ origin to Y Y Y Y Y
FA IP-20GX (CA) indicate the VC (Virtual Container)
number
PING command in CLI Y Y Y Y Y
ACM Adaptive Transmit Power Y Y N Y Y
MRMC ETSI script 3.5MHz ACM Y Y N Y Y
MRMC FCC script 25Mhz ACM
Note: For chassis-based products, these
scripts require RMC-B.
Page 16 of 129


RMC-E, SRM (Diplexer) 25MHz XPIC N N Y N N

ACM
RMC-E, SRM (Diplexer) 25MHz, Fixed
256QAM, Adj. channel
RMC-E, SRM (Branching) 25MHz XPIC
ACM
RMC-E, SRM (Branching) 25MHz, Fixed
256QAM, Adj. channel
External alarms inputs support in TCC Y Y Y N N
redundancy
Support for RMC-B in expansion slots N N N N Y
T4 synchronization interface N N N N Y
8.0.0.0.0.675 May 2015 MEF Certification (CE 2.0 and MEF-18) Y Y Y Y
FA IP-20N
TDM Pseudowire Services Configuration Y Y Y Y
FA IP-20A
Manager
Evo IP-20LH
8.0.0.0.0.677 RADIUS Authentication Y Y Y Y
FA IP-20G HTTPS (IPv4 and IPv6) Y Y Y Y
X.509 Server Authentication (SA) (part Y Y Y Y
of HTTPS implementation)
ifTable/ifXtable standard MIB counters Y Y Y Y
Support for 2048 QAM (Profile 10) Y Y Y Y
modulations (already supported in Evo
IP-20LH)
Alarms for synchronization source Y Y Y N
failure
New TDM LIC (16 x E1/DS1) option with Y Y Y N
no synchronization interface
Modem CW mode Y Y Y N
TCC-B2 card Y Y N N
TCC Redundancy – Added support for Y Y N N
LIC-STM1/OC3-RST (1 x STM-1)
TCC Redundancy – Added support for Y N N N
RMC-A
Multi-Carrier 2+0 radio configuration N N N Y
using Multi-Carrier ABC
Space diversity 1+1 radio configuration N N N Y
using Multi-Carrier ABC
TCC Redundancy N N Y N
Page 17 of 129


• MRMC FCC script 40Mhz XPIC ACM Y Y N Y

(Adjacent Channel)
• MRMC FCC script 10Mhz ACM
• MRMC FCC script 20Mhz ACM
• MRMC FCC script 25Mhz XPIC ACM
• MRMC FCC script 50MHx XPIC ACM
• MRMC FCC script 60MHx XPIC ACM
Note: For chassis-based products, these
scripts require RMC-B.
8.0.0.0.0.677: May 2015 • Two radio interfaces supporting up to Y

FA IP-20GX (First 1024 QAM modulation with ACM
CA release for IP- using ETSI radio scripts.
20GX) • 1+1 Radio Hot Standby (HSB)
Protection (fixed interfaces only)
• Cross Polarization Interference
Cancellation (XPIC).
• Link Aggregation (LAG)
• Frame Cut-Through.
• Ethernet: Point-to-Point and
Multipoint services.
• Carrier grade advanced QoS and
traffic management capabilities.
• Automatic State Propagation, LLDP,
G.8032, MSTP,
• Any combination of up to two LIC-T16
(16 x E1and/or LIC-T155 (1 x ch-STM-
1) cards are supported in the
expansion slots.
• Wizard for provisioning Native TDM
trails.
• Wizard for provisioning TDM
pseudowire services.
• Cascading is supported on ports
GbE1/CS1 and GbE2/CS2.
• TDM path protection and SOAM.
• Native Sync Distribution using
GbE/FE/E1/STM-1 input and
GbE/FE/E1 output, with SSM support
to prevent loops and enable use of
most reliable clock source, and user-
defined clock source priority and
quality level.
Page 18 of 129


7.9.0.0.0.345 March 2015 Fixes bug 129237: Extracting an RMC-E Y

(GA): that belongs to a Multi-Carrier ABC
Evo IP-20LH group and an XPIC group causes
continuous LOF events and traffic loss in
the unit.
7.9.0.0.0.341 November • Support Multi-Carrier ABC group Y
(GA) 2014 consisting of 8 x RMC-E channels: 8 x
Evo IP-20LH radio members and 8 x STM-1 RST
members
• External Alarms inputs
• Radio PM (Performance Monitoring)
of Multi-Carrier ABC group
• Revertive mode for Native TDM trail
protection
• TDM services –support for Cascading
ports
• Ethernet line interface loopback
(ingress only)
• Support for VLAN IDs 4091-4094
• Ethernet line PMs (Performance
Monitoring)
• LLDP – Statistics, Web EMS support
• Increased total number of Ethernet
and TDM services to 1025+512
• ifTable/ifXtable standard MIB
counters
• Dual-stack management IPv4/IPv6
• Security – SFTP, SNMPv3, SSH,
Security-Log
• Secured management protocols: SSH,
SFTP and SNMPv3
• Multi-Carrier ABC 1 x 8+0
• “Smart Pipe” L1 ASP over ABC group
• Support for Evolution ODUs for 5 to
11 GHz
7.9.0.0.0.339 November • Main Card (TCC) redundancy Y Y
(GA) 2014 • External alarm inputs
FA IP-20N
FA IP-20A • Revertive Mode in 1+1/2+2 HSB/HSB-
SD for RMC-B
• RMC-B w/ABC 1x8+0 (TCC-B-MC only)
• RMC-B Mixed Nx1+0/1+1 & 1xABC
(4+0)
Page 19 of 129


• Radio PM (Performance Monitoring)

of Multi-Carrier ABC group
• RMC-B, MRMC ETSI script 28Mhz XPIC
ACM (Adjacent Channel)
• RMC-B, MRMC ETSI script 56Mhz XPIC
ACM
• RMC-B MRMC ETSI/FCC script
56/60MHz ACM (non-XPIC)
• RMC-B, MRMC FCC script 50MHz ACM
(non-XPIC)
• Revertive mode for Native TDM trail
protection
• Native TDM services – support for
cascading ports
• Ethernet line interface loopback
(ingress only)
• Support for VLAN IDs 4091-4094
• Ethernet line PMs (Performance
Monitoring)
• LLDP – Statistics, Web EMS support
• Increased total number of Ethernet
and TDM to 1025+512
• ifTable/ifXtable standard MIB
counters
• Security-Log
SFTP and SNMPv3
• STM-1 RST LIC (TCC-B-MC only)
• RFU-Aep support (IP-20A only)
7.9.0.0.0.316 December • Cross Polarization Interference Y
(GA) 2014 Canceller (XPIC)
FA IP-20G • Hybrid services using cascading
interfaces – GbE1 and GbE2 can be
configured as GE traffic interfaces or
as cascading interfaces. When
operating in cascading mode, these
interfaces can handle hybrid Ethernet
and Native TDM traffic, enabling
operators to create links among
multiple IP-20G units in a node for
multi-carrier and multi-directional
applications based on hybrid Ethernet
Page 20 of 129


and Native or pseudowire TDM
services.
• Automatic State Propagation (ASP) for
smart pipe services
• Support for various types of RFUs:
RFU-HP, RFU-A, RFU-Aep, RFU
1500HP
• IF combining with 1500HP RF unit for
1+0, 1+1 and 2+0 XPIC radio
configurations
• New radio scripts: 50MHz with ACM
and 60MHz with ACM
• Synchronization State Messages
(SSM) over the radio with G.781
option II quality levels for North
America.
• DS1 TDM trails for North America
• Revertive protection of TDM trails
• Full support of IfTable from standard
SNMP MIB
SFTP and SNMPv3
• External alarm inputs
• Support of VLANs 4091 to 4094 for
user traffic
• PM on RMON counters
• Ethernet OAM loopback toward the
line with optional swapping of MAC
addresses
• Enhancements of MSTP feature:
support for mesh topologies and
support of interoperability with legacy
IP-10 platforms in RSTP mode.
• Enhancements of G.8032 feature:
Support for sub-rings
• Modifications of Unit info
• Display input voltage indication from
CLI command
• Support Web EMS configuration for
unmuting remote radio
• Enforcement of license on 2nd
modem activation.
Page 21 of 129


• Support for Ethernet-only units

7.7.7.0.0.9 (GA): July 2014 • 1+1 radio configuration with Hot- Y
FA IP-20G standby protection
• MSTP
• G.8032
• Support for a new hardware assembly
with a single radio interface
7.7.5.0.0.23 May 2014 • 802.3ad Link Aggregation Y
FA IP-20G (First • Activation of second radio carrier
CA release for IP-
20G) • Synchronization unit / SyncE
• LLDP
• Full set of RMON counters on radio
ports
• Support for up to 64 Ethernet services
• Range of TDM service IDs increased to
512 for compatibility with other
platforms
• Ability to mask under and over
voltage alarms
• New radio scripts: 30MHz (FCC) and
40MHz (ETSI & FCC) channel spacing
7.7.5.0.0.22 (GA) June 2014 • Support Multi-Carrier ABC groups up Y Y
FA IP-20N to 4+0 / 2+2 using TCC-B-MC
FA IP-20A • Support mix of Multi-Carrier ABC
group and multi-directional links
(1+0/1+1 HSB) using TCC-B-MC
• SyncE regenerator
• 8032 sub ring
• TDM Services – protection switches
• LLDP
• Automatic state propagation without
port shutdown between IP-20 peers
• Configuration Log
• CLI scripts
Page 22 of 129


7.7.5.0.0.22 June 2014 • RMC-E Y

Evo IP-20LH • Radio Utilization and Radio Ethernet
(First GA Release PMs
for Evo IP-20LH)
• XPIC
• MC-ABC up to 4+0
• Space Diversity IF Combining
• Ethernet Electrical and Optical LICs
• Ethernet Services
• LAG
• MSTP
• G.8032
• Smart TDM
• E1/DS1
• 1xCh-STM-1/OC-3
• TDM Services
• TDM Path Protection
• E1, STM-1 PM support
• TDM dual-homing support
• Hybrid Multi-Carrier ABC – STM1/OC3
RST (clear channel) over Multi-Carrier
ABC group
• Ch-STM-1 1+1 MSP
• Licensed Advanced TDM configuration
(TDM Pseudowire services)
• PWE: support MPLS encapsulation
• Synchronization (T3 2MHz, STM-1
sync import, ESMC, SSM)
• SyncE regenerator
• Licensing
• Unit name display, slot-level user
description
• DSCP support
• SNMP support
• Dual TCC support (HW ready for TCC
redundancy)
• LLDP
• Configuration Log
• CLI scripts
Page 23 of 129


7.7.0.0.0.46 (GA) March 2014 • TDM path protection – Trail Y Y

FA IP-20N protection over Radio & STM1
FA IP-20A interfaces
• TDM service - bug fix.
• Fix case #82320 Hutch Austria:
Software upgrade T7.2 to T7.5.5
causes continuous node reset
7.7.0.0.0.42 (GA) February • Miscellaneous fixes of field issues Y Y
FA IP-20N 2014
FA IP-20A
7.7.0.0.0.39 (GA) February • TDM Services support ch-OC3 Y
FA IP-20A 2014 • Ch-OC3 1+1 HSB
• Dual TCC support (HW ready for TCC
redundancy)
• 40M XPIC and non-XPIC script
7.7.0.0.0.27 • Single radio interface supporting up to Y
IP-20G (First CA 1024QAM modulation with ACM
release for IP- using ETSI radio scripts
20G) • Ethernet: Point-to-Point and
Multipoint services
• Carrier grade advanced QoS and
Traffic management capabilities
• TDM services
• TDM services provisioning wizard
• TDM services Path Protection (1:1,
1+1)
• Frame Cut-Through
• Licensing
7.6.0.0.0.58: November • ABC support Y
FA IP-20A (CA 2013 • ABC HSB+SD
release for North
America only)
7.6.0.0.0.50: October 2013 • 30 MHz FCC scripts for RMC-B Y
FA IP-20A (First • MC-ABC (up to 4+0 and 2+2 HSB/SD)
CA release for
North America • XPIC, HSB, SD, IF combining support
only) for MC-ABC
• DS1
• Smart Pipe Services with ASP
• Extended Web supporting features
above
• SNMP support
Page 24 of 129


• RFU-Ae, RFU-HP and 1500HP RFUs

support
• Automatic State Propagation (ASP)
7.5.5.0.0.19 (GA) January 2014 • Ability to configure the VC12 V5 signal Y
FA IP-20N label bit to support non-specific-
payloads in addition to already
supported asynchronous payloads
7.5.5.0.0.16 (GA) November • STM-1 1+1 HSB card protection Y
FA IP-20N 2013 • Native TDM – dual homing support
• Radio utilization and Radio Ethernet
PMs
• Licensed Advanced TDM configuration
(TDM Pseudowire services)
• TDM services - add trail description
• TDM services - Dual Homing support
• TDM services - Ch-STM-1 1+1 MSP
support
7.5.1.0.0.2 (GA): September • Additional radio scripts for RMC-B Y
FA IP-20N 2013 • XPIC scripts support up to profile 9 (1k
QAM)
7.5.0.0.0.28 August 2013 • XPIC (only with RMC-B) Y
(GA): • G.8032 (rings only)
FA IP-20N
• Ethernet Optical LIC
• Frame Cut-Through
• Synchronization (T3 2MHz, STM-1
sync import, ESMC, SSM)
• TDM services
• RMC-B (1+1 HSB, Sync distribution)
• Web GUI: 1+1 HSB, Sync, LAG
• Ethernet: Point-to-Point services
• E1, STM-1 PM support
• Unit name display, slot-level user
description
• DSCP support in additional code
points
• LAG on radio ports
7.2.0.0.0.30 May 2013 • RMC-B Y
(CA): • TDM support for Native TDM and
FA IP-20N TDM pseudowire services
• 1xCh-STM-1/OC-3
Page 25 of 129


• LAG
• MSTP
• TDM Services Management
• TDM Path Protection
• Licensing
7.0.0.0.0.76: December Y
FA IP-20N (First 2012
IP-20N CA
release)
Page 26 of 129

2. Software Package
The IP-20 IDU software is released as a zipped file.
CAUTION! Do not modify the zipped software package in any way! The system
will not be damaged, but the ZIP file will be unusable if changed.
The following software packages can be viewed via the Web-based Element
Management System (EMS) after software installation.
Note: The software package for FibeAir IP-20N, IP-20A, and Evolution IP-
20LH, on one hand, and FibeAir IP-20F, IP-20G, and IP-20GX on the
other, are different and cannot be used interchangeably. Make sure
to use the correct software package for the product type you are
using.
Table 2: IP-20 Software Component Versions for CeraOS 10.0

Package Name Version for IP-20N, IP-20A, Version for IP-20F, IP-20G, and
and Evolution IP-20LH IP-20GX
Gnss 10.0.0.0.0.162 10.0.0.0.0.162

gnss-evo-radio-sw 1 NA
gnss-fpga-fw-elic 1.8.4 NA
gnss-fpga-fw-rmc 2.4 NA
gnss-rmc-b 3.10.65 3.10.65
gnss-fpga-fw-rmc-e 4.12 NA
gnss-fpga-fw-tcc 1.53.26 NA
gnss-fpga-fw-hrzn NA 5.34
gnss-atp 1.40.4 NA
gnss-management 1.10.0.14 1.10.0.14
gnss-mctl 10.0.0.0.0.162 10.0.0.0.0.162
gnss-mrmc-scripts 7.16 7.16
gnss-mrmc-b-scripts 2.57 2.57
gnss-rfu 3.0.11 3.0.11
gnss-rfu-tables 6.48 6.48
gnss_tcc-config 1.0 NA
gnss_tcc-kernel v2.6.34.8 NA
Nxs_hc-kernel NA v2.6.34.8
Nxs_hc_config NA 1.0
gnss-modem-fw 3.40.2 NA
gnss-pwc 6.24 6.24
gnss-pwc-stm1 6.25 6.25
Page 27 of 129

Package Name Version for IP-20N, IP-20A, Version for IP-20F, IP-20G, and
and Evolution IP-20LH IP-20GX
gnss-vm-control 1.0.2.12 1.0.2.12

Lighttpd 1.4.35 1.4.35
2.1 MIB File Names and Versions

Table 3: IP-20 MIB File Names and Versions for CeraOS 10.0
File name Version
Network MIB 1.10.0.1

PM-MIB 1.10.0.1
Radio-MIB 1.10.0.2
Unit-MIB 1.10.0.2
MWRM-DEFS.MIB
Page 28 of 129

3. New Products and Features

This section describes products and features introduced or modified in CeraOS
10.0.
3.1 FibeAir IP-20F

CeraOS 10.0 is the first CeraOS release that supports FibeAir IP-20F.
FibeAir IP-20F is a split-mount edge node that delivers multi-Gbps radio capacity
to the transport network. It provides operators with the simplicity that comes
with deploying a very compact, fixed configuration node, helping operators to
meet their operational efficiency targets. The IP-20F’s fixed configuration
simplifies installation, spare part management and maintenance. What’s more, its
passive cooling design suits harsh environments, increases reliability and
minimizes ambient noise.
Only the first RFU interface (RFU1) can be used in CeraOS 10.0. When used with a
MultiCore RFU (RFU-D or RFU-D-HP), this interface can support two radio carriers.
However, the second carrier must part of a Multi-Carrier ABC group in order to be
utilized.
IP-20F also supports 1+0 configurations with any of the new RFUs introduced in
CeraOS 10.0, including the E-Band RFU-E.
For a complete description of IP-20F, including detailed specifications, refer to the
Technical Description for FibeAir IP-20F.
For configuration instructions, refer to the User Guide for FibeAir IP-20F, IP-20G,
and IP-20GX, CeraOS 10.0.
3.2 FibeAir RFU-D

FibeAir RFU-D brings MultiCore features and capabilities to split-mount
configurations. RFU-D incorporates two modems, which are connected to the IDU
via a single baseband interface.
RFU-D operates in the frequency range of 6-42 GHz. RFU-D supports low to high
capacities for traditional voice and Ethernet services, as well as PDH/ or hybrid
Ethernet and TDM interfaces.
With RFU-D, traffic capacity throughput and spectral efficiency are optimized with
the desired channel bandwidth. For maximum user choice flexibility, channel
bandwidths from 14-112 MHz can be selected together with a range of
modulations. RFU-D provides a range of modulations from BPSK to 4096 QAM.
For further information, refer to the Technical Description for IP-20N, CeraOS
10.0.
Page 29 of 129

3.3 FibeAir RFU-D-HP

FibeAir RFU-D-HP is a MultiCore RFU that provides high transmit power for long-
haul applications. Like RFU-D, RFU-D-HP incorporates two modems, which are
connected to the IDU via a single baseband interface. Because of RFU-D-HP’s
MultiCore design, operators can use it to overcome backbone deployment
limitations by using the advance features supported by RFU-D-HP.
RFU-D-HP’s usage mode is scalable, enabling operators to limit initial costs by
purchasing the basic single core mode, then expanding to MultiCore mode with
no additional hardware or installation required when network expansion requires
additional capacity.
RFU-D-HP offers a flexible and modular branching system that enables the
combination of different bands for different carriers. For example, the same link
can be used for both L6 and U6 or 7 and 8 GHz channels.
RFU-D-HP can be used with wide diplexer-based branching, enabling direct mount
installation. Diplexers can be used for direct mount configurations of up to 4+0.
RFU-D-HP can also be used with channel filter-based branching, enabling
configurations of up to 8+0 per polarization in remote mount configurations.
To maximize operational flexibility, both diplexers and channel filters are provided
separately for the radio units, enabling the diplexers or filters to be changed in the
field with minimal downtime and no risk of impairing the RFU’s sealing.
RFU-D-HP operates in the frequency range of 4-11 GHz. RFU-D-HP supports low to
high capacities for traditional voice and Ethernet services, as well as PDH/ or
hybrid Ethernet and TDM interfaces.
With RFU-D-HP, traffic capacity throughput and spectral efficiency are optimized
with the desired channel bandwidth. For maximum user choice flexibility, channel
modulations. RFU-D-HP provides a range of modulations from BPSK to 4096 QAM.
3.4 FibeAir RFU-E

FibeAir RFU-E is a compact and versatile single-core RFU that operates in the E-
Band frequency range (71-86 and 81-86 GHz). Thanks to its small footprint, low
power consumption, and simple installation, RFU-E can be installed in many
different types of remote locations.
In CeraOS 10.0, RFU-E operates over 14, 28, 62.5, 125, and 250 MHz channels to
deliver up to 1.6 Gbps of Ethernet throughput in several system configurations.
RFU-E is connected to the IDU via a single radio interface. RFU-E supports low to
high capacities for traditional voice and Ethernet services, as well as PDH/ or
hybrid Ethernet and TDM interfaces.
RFU-E provides a range of modulations from BPSK to 1028 QAM.
10.0.
Page 30 of 129

3.5 FibeAir RFU-S

FibeAir RFU-S is a state-of-the-art single-carrier RFU that supports a broad range
of capacities. RFU-S operates in the frequency range of 6-42 GHz. RFU-S supports
low to high capacities for traditional voice and Ethernet services, as well as hybrid
Ethernet and TDM interfaces
With RFU-S, traffic capacity throughput and spectral efficiency are optimized with
the desired channel bandwidth. For maximum user choice flexibility, channel
modulations. RFU-S provides a range of modulations from BPSK to 4096 QAM.
10.0.
3.6 RIC-D
RIC-D provides interfaces between the IP-20N or IP-20A IDU and any of the
following RFUs:
• RFU-D
• RFU-D-HP
• RFU-E
• RFU-S
The 1RU model of IP-20N and IP-20A can accommodate up to five RIC-Ds. The 2RU
model of IP-20N and IP-20A can accommodate eight RIC-Ds.
The RIC-D has two combo interfaces to the RFU (optical or electrical). In CeraOS
10.0, only the first interface (RFU1) can be used.
RFU-D, RFU-E, and RFU-S receive PoE power from the IDU via the electrical
interfaces. If they are connected to the IDU via the optical interfaces, a separate
power cable must be used.
RFU-D-HP must always be used with a separate power cable.
RICs can be placed in any slot except the TCC slot (In a 1RU chassis: slot 1; in a 2RU
chassis, slots 1 and 11).
From CeraOS 10.0, the IP-20N and IP-20A chassis is divided into sections for
purposes of slot configuration. If no specific radio is intended to be used at a
capacity greater than 1 Gbps, no special configuration is necessary. However, if
capacity greater than 1 Gbps is desired, the card must be inserted in a section of
the chassis that is configured to 2.5 Gbps mode.
Note: To set the section capacity using the Web EMS, go to Platform >
Management > High Capacity Configuration, select the relevant slot
section, click Edit, set the Configured Capacity Mode to 2.5Gbps and
click Apply. When you are finished, click Reset Chassis.
Page 31 of 129

For example, to use an RFU-E with greater than 1 Gbps capacity, the RIC-D
interfacing with the RFU-E must be placed in a slot section configured for 2.5 Gbps
mode. It is important to note that:
• Ethernet and TDM cards, and RMCs not being used in Multi-Carrier ABC
configurations, cannot be used in a slot section configured for 2.5 Gbps mode.
This must be taken into account in system planning, so that RIC-D cards
intended for greater than 1 Gbps are placed in a separate slot section.
• Unit reset is required after changing the capacity configuration of a slot
section. Chassis reset is also required after configuring the Expected Card
Type for a LIC-X-E10. Therefore, these operations should be performed during
low traffic periods or maintenance windows. Only one reset needs to be
performed for these operations, so if more than one such configuration
change is planned, the configurations should be performed at the same time,
followed by a single unit reset.
For further information, refer to the Technical Description for FibeAir IP-20N or
the Technical Description for FibeAir IP-20A, CeraOS 10.0.
For RIC-D installation instructions, refer to the Installation Guide for FibeAir IP-
20N, Rev E or later or the Installation Guide for FibeAir IP-20A, Rev F or later.
For RFU installation instructions, refer to the Installation Manual for the relevant
RFU.
For configuration instructions specifically relevant for RIC-D and the new RFUs,
see the following sections in the User Guide for FibeAir IP-20N and IP-20A:
• Section 1.2.2, IDU Overview and Slot Population Guidelines
• Section 1.2.4, Slot Sections and 2.5 Gbps Mode
• Section 1.2.5, Additional Slot Guidelines
• Section 1.2.7, Radio Interface Cards (RIC)
• Section 1.2.15, IDU-RFU Connection and Power Supply
• Section 2.14, Configuring the IDU-RFU Connection (RIC-D only)
• Section 2.15, Configuring Slot Section Capacity Mode
• Section 2.16, Enabling the Interfaces (Interface Manager)
• Section 28.2, RIC-D LEDs
Page 32 of 129

3.7 Configurable Timeout for Trap Generation

A 30-second timeout for trap generation was introduced in CeraOS 8.5. CeraOS
10.0 extends this feature by enabling users to configure the timeout to any value
between 0 and 120 seconds.
This timeout provides a wait time after an alarm is cleared in the system before
the alarm is actually reported as being cleared. This prevents traps from flooding
the NMS in the event that something causes the alarm to be raised and cleared
continuously.
The timeout for trap generation can be configured via CLI. By default, the timeout is 10
seconds.
Note: If the unit is upgraded from an earlier version to CeraOS 10.0 or
higher, the timeout retains its previous value until it is changed. That
means if it was never configured, it retains its previous default value
of 0. If the unit is set to its factory default configuration, the timeout
is set to 10 seconds.
For configuration instructions, refer Configuring a Timeout for Trap Generation
(CLI), in the relevant User Guide for CeraOS 10.0:
• User Guide for FibeAir IP-20N and IP-20A, and Evolution IP-20LH: Section 24.4.
• User guide for FibeAir IP-20F, IP-20G, and IP-20GX: Section 25.4.
3.8 Radio Traffic PM Threshold Configuration via SNMP

CeraOS 10.0 adds three objects to the private MIB that enable configuration of
the following radio traffic PM thresholds:
• Capacity – genEquipRadioCompNGCfgCapacityPmThreshold, OID
1.3.6.1.4.1.2281.10.7.5.4.1.1.6
• Throughput – genEquipRadioCompNGCfgThroughputPmThreshold, OID
1.3.6.1.4.1.2281.10.7.5.4.1.1.7
• Utilization – genEquipRadioCompNGCfgUtilizationPmThreshold, OID
1.3.6.1.4.1.2281.10.7.5.4.1.1.8
These objects are located in the file MWRM-RADIO-MIB.mib.
For details, refer to Section 3.6.2, Setting the traffic PM thresholds, in the MIB
Reference Guide for FibeAir IP-20, CeraOS 10.0.
3.9 No Reset after Changing the Minimum or Maximum ACM

Profile
From CeraOS 10.0, users can change the minimum or maximum ACM profile
without a unit reset. This is applicable to all IP-20 products.
Page 33 of 129

4. Feature Release Notes

This section describes significant feature requirements and limitations relevant to
CeraOS 10.0. For a full description of supported features, refer to the Technical
Description for the specific IP-20 product.
Table 4: Feature Requirements and Limitations for CeraOS 10.0

Feature Notes Applicability
IP-20F • Only the first RFU interface (RFU 1) can be used in CeraOS 10.0. When IP-20F
used with a MultiCore RFU (RFU-D or RFU-D-HP), this interface can
support two radio carriers. However, the second carrier must part of a
Multi-Carrier ABC group in order to be utilized.
• Up to four Ethernet interfaces can be used (GbE/SFP 1-4)
• IP-20F does not support 1588-TC and 1588-BC.
• IP-20F does not support AES-256 Radio Payload Encryption.
• IP-20F does not support unit redundancy.
RIC-D • 1588-TC and 1588-BC are not supported with RIC-D. FA IP-20N
• HSB radio protection and Space Diversity are not supported with RIC-D. FA IP-20A
• TCC hot switchover (HSO) is not supported with RIC-D.

• Multi-Carrier ABC with RIC-D is only supported between the two radio
carriers of a single MultiCore RFU (RFU-D or RFU-D-HP). It is not
supported between separate RFUs.
• XPIC with RIC-D is only supported between the two radio carriers of a
single MultiCore RFU (RFU-D or RFU-D-HP). It is not supported between
separate RFUs.
• RIC-D does not support AES-256 Radio Payload Encryption.
LACP • LACP is only supported with Ethernet interfaces. All
• LACP is not supported on the TCC Ethernet ports with TCC redundancy
• LACP is not supported with IP-20G unit redundancy.
• LACP cannot be used with Enhanced LAG Distribution or with the LAG
Group Shutdown in Case of Degradation Event feature.
IEEE-1588v2 PTP • 1588 BC cannot be configured on interface groups, such as LAG and FA IP-20N
Optimized Transport Multi-Carrier ABC. FA IP-20A
–Boundary Clock • 1588 BC can only be used in a chain or star topology. It cannot be used FA IP-20G
in a ring topology. FA IP-20GX
IEEE-1588v2 PTP • 1588 BC can only be used on an IP-20GX with no cards enabled in the FA IP-20GX
Optimized Transport expansion slots.
–Boundary Clock
Page 34 of 129


IEEE-1588v2 PTP • 1588 TC and 1588 BC cannot be used with the 10GE interface on a LIC-X- FA IP-20N
Optimized Transport E10 (Bug ID 152266). FA IP-20A
– Transparent Clock • 1588 TC and 1588 BC are not supported with TCC Redundancy. FA IP-20F
and Boundary Clock
• 1588 TC and 1588 BC cannot be used on units with multiple Multi-
Carrier ABC groups.
• 1588 TC and 1588 BC cannot be used in 2.5 Gbps mode
• 1588 TC and 1588 BC cannot be used with RIC-D
• 1588TC and 1588 BC cannot be used with IP-20F
IEEE-1588v2 PTP • 1588 TC and 1588 BC are not supported when Master-Slave FA IP-20N
Optimized Transport communication is using the IPv6 transport layer. FA IP-20A
– Transparent Clock • 1588 TC and 1588 BC cannot be used on 1+1 or 2+2 HSB links. FA IP-20G
and Boundary Clock FA IP-20GX
• 1588 TC and 1588 BC are not supported with Frame Cut-Through
IEEE-1588v2 PTP • Users should not rely on classification of 1588 PTP packets according to FA IP-20N
Optimized Transport VLAN p-bits to ensure classification of 1588 packets to a high CoS. When FA IP-20A
– Transparent Clock configuring an Ethernet service to carry 1588 PTP packets, users should FA IP-20G
set the CoS mode of either the service or the service points to Default FA IP-20GX
CoS, with a default CoS value of 7.
ASP and LLF • If the Controlled Interface is a LAG, and the physical interfaces that FA IP-20F
belong to the LAG are set to Admin = Down in the Interface Manager, FA IP-20N
ASP is triggered. FA IP-20A
FA IP-20G
FA IP-20GX
ASP and LLF • Extracting an RMC or Ethernet LIC triggers ASP on the remote unit but FA IP-20N
not the local unit. FA IP-20A
FA IP-20GX
LLDP • LLDP cannot be used for more than two IP-20 units that are connected All
to each other via a simple switch or hub.
LIC-X-E10 • In order for a LIC-X-E10 to work in Slot 12, the Expected Card Type for FA IP-20N
Slot 2 must be empty or LIC-X-E10. FA IP-20A
• If the user changes the Expected Card Type to or from LIC-X-E10, the Evo IP-20LH
unit must be manually reset. A hardware mismatch alarm is raised until
the reset has been performed.
• When a LIC-X-E10 is placed in Slot 12, the same TCC port limitations
apply as those that apply with other Ethernet LICs. See TCC GE Interface
Limitations on page 117.
• To use the 10GE interface, Auto Negotiation must be off.
• Requires TCC-B2-XG-MC.
NTP • NTP is only supported over IPv4. All
Page 35 of 129


ATPC Override Timer • For FibeAir IP-20N, IP-20A, and IP-20GX expansion slots, requires RMC- FA IP-20N
B. Not supported with RMC-A or RMC-E. FA IP-20A
FA IP-20GX
IP-20G Unit • The following protocols cannot be used with IP-20G unit redundancy. FA IP-20G
Redundancy MSTP
G.8032
LLDP
Service OAM (SOAM)
• When using a Y-cable with Electrical Splitter mode and Auto Negotiation
enabled, there is a traffic disruption of approximately two seconds upon
switchover for Ethernet traffic passing through this cable.
• For Ethernet Line Protection mode, a unit reset is required when
changing the interface mode to or from LACP. It is recommended to
perform copy-to-mate immediately after changing the Interface Mode
to or from LACP, then to reset the active unit only after the standby unit
is back up after the copy-to-mate operation.
T3 Synchronization • T3 synchronization is only supported in ETSI mode. FA IP-20F
FA IP-20G
FA IP-20GX
Multiple Multi- • Requires TCC-B2-XG-MC on both sides of the link. TCC Redundancy can FA IP-20N
Carrier ABC Groups be used with multiple Multi-Carrier ABC groups. FA IP-20A
with RFU-C, RFU-A, • MSTP is not supported with multiple Multi-Carrier ABC groups. Evo IP-20LH
and 1500HP/RFU-HP
• When using more than one Multi-Carrier ABC group, LIC-STM1/OC3-RST
cards and STM1/OC3-RST interfaces on RMC-E cards can only be
assigned to Multi-Carrier ABC Groups 1 and 3.
• Only radio carriers with RMC-B or RMC-E can be used.
• 2.5 Gbps mode is not supported with multiple Multi-Carrier ABC groups.
• Multi-Carrier ABC Group 1 can include up to eight members. Groups 2,
3, and 4 can each include up to four members.
• When multiple Multi-Carrier ABC groups are configured, certain slots
can only be populated with cards that are assigned to a Multi-Carrier
ABC group. For details, see Additional Slot Guidelines on page 120.
TCC Hot Switchover • G.8032 and MSTP are not supported with HSO and must be disabled. FA IP-20N
(HSO) • SyncE PRC Pipe Regenerator Mode is not supported with HSO. FA IP-20A
Evo IP-20LH
AES-256 Radio • Not supported with RIC-D FA IP-20N
Payload Encryption • Not supported with IP-20F FA IP-20A
FA IP-20F
• Not supported with RMC-A. FA IP-20GX
TCC-B2-XG-MC • The TCC-B2-XG-MC cannot be used with software versions prior to T8.2. FA IP-20N
• By default, the TCC-B2-XG-MC is configured in 1 Gbps mode, which FA IP-20A
enables it to support a Multi-Carrier ABC group with a capacity of up to Evo IP-20LH
1 Gbps. From CeraOS 8.2.5, the capacity can be set to 2.5 Gbps by user
Page 36 of 129


configuration. Changing the Multi-Carrier ABC capacity supported by the
TCC-B2-XG-MC results in a system reset.
• When the TCC-B2-XG-MC is set to 2.5 Gbps mode, certain slots must be
dedicated to Multi-Carrier ABC and cannot be used in any other mode of
operation. These slots should be populated with cards that can be used
in Multi-Carrier ABC mode (RMC-B, RMC-E, and LIC-STM1/OC3-RST (Bug
ID 137124)). For details, see Additional Slot Guidelines on page 120.
• 2.5 Gbps mode is only supported with Multi-Carrier ABC Group 1.
• Header De-Duplication cannot be used with a Multi-Carrier ABC group in
2.5 Gbps mode.
• When configuring a unit with a TCC-B2-XG-MC, it is recommended to
configure a radio card in Slot 3 before configuring any other cards.
TCC-B2 • The TCC-B2 cannot be used with software versions prior to T8.0. FA IP-20N
FA IP-20A
Header De- • Requires RIC-D, RMC-B, or RMC-E (for Evolution IP-20LH). Not supported FA IP-20N
Duplication with RMC-A. FA IP-20A
Evo IP-20LH
FA IP-20GX
Configuration • Before upgrading to a newer software version, save the current All
Management configuration to any unused Restore Point. In the event that after
upgrading, you want to downgrade to the software version you were
originally using, make sure to place the saved configuration from the
original version in Restore Point 1 before downgrading to that version. If
no configuration from the original software version or earlier is in
Restore Point 1 when you downgrade to the original software version,
the unit will be set to its default configuration.
Support for Optical • If an optical port cable is disconnected from the TCC in Slot 11, the FA IP-20N
Ports on TCC with resulting Loss of Carrier alarm displays the Origin of the alarm as Slot 1 (2RU)
TCC Redundancy rather than Slot 11. FA IP-20A
• The Media Type of the optical ports must be set to SFP and not Auto. (2RU)
Evo IP-20LH
(2RU)
TDM LIC (16 x • This TDM LIC cannot be used with software versions prior to T8.0. FA IP-20N
E1/DS1) option with FA IP-20A
no synchronization Evo IP-20LH
interface (Part FA IP-20GX
Number: 24-L004-0)
Main Card (TCC) • The same TCC type must be populated in Slot 1 and Slot 11. FA IP-20N
Redundancy • The same software version must be running on both TCCs. (2RU)
FA IP-20A
• T4 synchronization output is not supported with TCC redundancy. (2RU)
• Configuration alignment between the TCCs can only be performed by Evo IP-20LH
manually issuing “copy to mate” which aligns the configuration between (2RU)
the TCCs. A dynamic configuration alignment is not available, meaning,
any configuration change at the active TCC should be manually aligned
by issuing “copy to mate”.
Page 37 of 129

• When TCC redundancy is provisioned, all configurations should be

performed via the active TCC, excluding activation key installation. For
more details, see Section 3 of the IP-20N, IP-20A, and IP-20LH User
Guide, Configuring TCC Redundancy.
• For cold switchover (not HSO), switchover issues chassis cold reset.
1+1 HSB-SD There is a specific process for adding and deleting 1+1 HSB-SD groups. This FA IP-20N
process is described in the IP-20 User Guides and must be followed in the FA IP-20A
correct sequence. Failure to do so may render the unit inoperable and FA IP-20G
require reset to the unit’s factory default configuration.
In the IP-20N, IP-20A, and IP-20LH User Guide, see Section 3.8.3.,
Configuring 1+1 HSB with Space Diversity and Section 3.8.8, Deleting an
HSB Radio Protection Group with Space Diversity.
In the IP-20G and IP-20GX User Guide, see Section 3.7.3., Configuring 1+1
HSB with Space Diversity and Section 3.7.8, Deleting an HSB Radio
Protection Group with Space Diversity.
2+2 HSB-SD To successfully delete a 2+2 HSB-SD Multi-Carrier ABC group, you must FA IP-20N
first remove both 1+1 HSB-SD groups from the Multi-Carrier ABC group, FA IP-20A
then delete at least one of the 1+1 HSB-SD groups from the system
entirely.
• To delete a 1+1 HSB-SD group using the Web EMS, go to Radio > Groups
> Radio Protection, select the group, and click Delete.
• To delete a 1+1 HSB-SD group using the CLI, use the following
command:
root>radio protection delete group <group#>
Failure to follow this procedure will cause the Multi-Carrier ABC page in
the Web EMS to become blank, requiring chassis reset and disruption of
traffic.
2048 QAM LIC-STM1/OC3-RST is not supported when the radio profile is set to 2048 FA IP-20N
QAM. FA IP-20A
ACM • The ability to set a minimum profile greater than 0 is not supported for FA IP-20F
Multi-Carrier ABC groups, 1+1 HSB groups, and 1+1 HSB-SD groups. FA IP-20N
FA IP-20A
FA IP-20G
FA IP-20GX
ACM Adaptive • Working with RFU-C requires RFU-C software version 2.17 and above. FA IP-20N
Transmit Power • When working with RFU-HP or RFU-A, requires RFU software version FA IP-20A
5.14 or above FA IP-20G
FA IP-20GX
• When working with 1500HP, requires RFU software version 8.13a2 or
above.
• Not supported with RMC-A FA IP-20N
FA IP-20A
FA IP-20GX
• Not supported with RMC-E (Evolution IP-20LH). Evo IP-20LH
Page 38 of 129


Gigabit Ethernet • The automatic media detection option on Gigabit Ethernet ports is not FA IP-20G
interfaces supported but also is not blocked by the software. Make sure automatic FA IP-20GX
media detection is disabled on all GE traffic interfaces (102941).
Radio • Some radio MRMC scripts are not supported but also are not blocked by FA IP-20N
the software. Users should be careful not to configure unsupported FA IP-20A
radio scripts. For a list of all supported radio scripts, see Radio Scripts on FA IP-20F
page 34. FA IP-20G
FA IP-20GX
Ethernet Services • Link Aggregation (LAG, IEEE 802.3 clause 43) is only supported on GE FA IP-20F
interfaces or on two radio interfaces. Mixing radio and GE interfaces in FA IP-20G
the same LAG group is not supported. FA IP-20GX
TDM • Front panel clock mode for TDM trails is not supported but is also not All
blocked.
• For PWE3, only SAToP MEF8 encapsulation is supported. Other
encapsulations are not supported but are not blocked by the software.
Page 39 of 129

5. Radio Scripts
Designated ETSI System Class Explanation:
ACCP ACAP CCDP
(Adjacent Channel Co (Adjacent Channel (Co Channel Dual
Polarization) Alternate Polarization) Polarization)
H H
V V
Note that:
Certain modulations above 256 QAM require specific RFU models.
For details, refer to the relevant Technical Description.
LIC-STM1/OC3-RST (available in FibeAir IP-20N and IP-20A systems) is
not supported when the radio’s profile is set to 2048 QAM profile 10.
XPIC scripts (all scripts with Script ID 12XX) are not supported in 1+1
HSB radio protection mode.
Although in some cases it may be possible to configure higher
profiles, the maximum supported profiles are those listed in the
tables below.
5.1 Supported ETSI Microwave MRMC Scripts for FibeAir Products

The tables in this section list supported ETSI-compliant system MRMC (Multi-Rate-
Multi-Constellation) configurations (determined by modem configuration scripts).
5.1.1 ETSI MRMC Scripts Supported with RMC-A in FibeAir IP-20N and IP-20GX
The MRMC scripts listed in the following table are supported in FibeAir IP-20N and
IP-20GX units only, and require RMC-A. The highest modulation supported by
these scripts is 256 QAM.
Table 5: MRMC Scripts with RMC-A, IP-20N and IP-20GX

Script ID Channel BW Occupied System Class Highest ACM XPIC
BW Spectral (CCDP)
Efficiency
Class
33 7 6.5 ACCP 5B Yes No

23 14 13 ACCP 2,4,5B Yes No
22 28/30 27 ACCP 5B Yes No
16 40 36 ACAP 5B Yes No
13 56 52 ACAP 5B Yes No
Page 40 of 129

5.1.2 ETSI MRMC Scripts Supported with FibeAir IP-20N (RMC-B only), IP-20G,
and IP-20GX
The MRMC scripts listed in the following table are supported in FibeAir IP-20N,
IPIP-20G, and IP-20GX. When used in FibeAir IP-20N and IP-20GX expansion slots,
these scripts require RMC-B.
Table 6: MRMC Scripts, IP-20N, IP-20G, and IP-20GX

Script ID Channel Occupied RFU-C RFU- XPIC Highest Max Profile Max
BW BW System HP/1500HP (CCDP) Spectral (ACM) Profile
Class System Efficiency (Fixed)
Class Class
1023 3.5 3.267 ACCP ACAP No 6L 5 (256 QAM) 4 (128

QAM)
1008 7 6.5 ACCP ACAP No 7B 9 (1024 QAM) 8
1009 14 13.3 ACCP ACAP No 7B 9 8
1209 14 13.3 ACCP ACAP Yes 7B 9 8
1004 28 26.5 ACCP ACAP No 8B 10 (2048 QAM) 9
1204 28 26.5 ACCP ACAP Yes 7B 9 8
12143 28 26 - ACCP Yes 7B 9 8
1005 28 28 ACAP ACAP No 8A 10 9
1205 28 28 ACAP ACAP No 7A 9 8
12174 40 33.5 - ACCP Yes 7B 9 8
1007 40 37.4 ACCP ACAP No 8B 10 9
1207 40 37.4 ACCP ACAP Yes 7B 9 8
1003 56 53 ACCP ACAP No 8B 10 9
1006 56 55.7 ACAP ACAP No 8A 10 9
1203 56 53 ACCP ACAP Yes 7B 9 8
1206 56 55.7 ACAP ACAP No 7A 9 8
3
MRMC script 1214 provides smaller bandwidth than MRMC script 1204. Script 1214 can be
used for interoperability with existing equipment in the field. It is an Adjacent Channel script,
for use with RFU-HP and 1500HP only.
4
MRMC script 1217 provides smaller bandwidth than MRMC script 1207. Script 1217 can be
used for interoperability with existing equipment in the field. It is an Adjacent Channel script,
for use with RFU-HP and 1500HP only.
Page 41 of 129

5.1.3 ETSI MRMC Scripts Supported with FibeAir IP-20F or FibeAir IP-20N (RIC-D
only) and RFU-D, RFU-D-HP, and RFU-S
The MRMC scripts listed in the following table are supported in FibeAir IP-20F or
FibeAir IP-20N working with RFU-D, RFU-D-HP, and RFU-S.
Note: Profile 12 (4096 QAM) is not supported for 112 MHz channels. For
detailed specifications of maximum profile per frequency and
channel bandwidth, consult your Ceragon representative.
XPIC is only supported with RFU-D and RFU-D-HP.
Table 7: MRMC Scripts, IP-20F or IP-20N with RFU-D, RFU-D-HP, and RFU-S
Script ID Channel Occupied System XPIC Highest Spectral Max Profile (ACM) Max Profile
BW BW Class (CCDP) Efficiency Class (Fixed)
4509 14 13.3 ACCP Yes 7B 11 (2048 QAM) 10 (1024 QAM)

4504 28 26.5 ACCP Yes 8B 12 (4096 QAM) 11
4505 28 28 ACAP No 8A 12 11
4507 40 37.4 ACCP Yes 8B 12 11
4502 56 53 ACCP Yes 8B 12 11
4506 56 55.7 ACAP No 8A 12 11
4511 112 106 ACCP Yes 8B 11 10
Page 42 of 129

5.2 Supported FCC Microwave MRMC Scripts for FibeAir Products

The tables in this section list supported FCC-compliant system MRMC (Multi-Rate-
Multi-Constellation) configurations (determined by modem configuration scripts).
5.2.1 FCC MRMC Scripts Supported with RMC-A in FibeAir IP-20A and IP-20GX
The MRMC scripts listed in the following are supported in FibeAir IP-20A and IP-
20GX, and require RMC-A. The highest modulation supported by these scripts is
256 QAM (RMC-A does not support modulations higher than 256 QAM).
Table 8: MRMC Scripts with RMC-A, IP-20A, IP-20GX

Script ID Channel BW Occupied BW ACM XPIC (CCDP)
22 30 27 Yes No
16 40 36 Yes No
5.2.2 FCC MRMC Scripts Supported with FibeAir IP-20A (RMC-B only), IP-20G,
and IP-20GX
MRMC scripts listed in the following are supported in FibeAir IP-20A, IP-20G, and
IP-20GX. When used in FibeAir IP-20A and IP-20GX expansion slots, these scripts
require RMC-B.
Table 9: MRMC Scripts IP-20A, IP-20GX (RMC-B) and IP-20G

Script ID Channel BW Occupied BW XPIC (CCDP) Max Profile (ACM) Max Profile (Fixed)
1023 5 3.267 No 5 (256 QAM) 4 (128 QAM)

1020 10 9.11 No 9 (1024 QAM) 8
1021 20 18.57 No 10 (2048 QAM) 9
1222 25 23.4 Yes 9 8
1025 25 23.4 No 10 9
1005 30 28 No 10 9
1205 30 28 Yes 9 8
1217 40 33.5 Yes 9 8
1007 40 37.4 No 10 9
1207 40 37.4 Yes 9 8
1010 50 47.2 No 10 9
1210 50 47.2 Yes 9 8
1006 60 55.7 No 10 9
1206 60 55.7 Yes 9 8
Page 43 of 129

5.2.3 FCC MRMC Scripts Supported with FibeAir IP-20F or FibeAir IP-20A (RIC-D
only) and RFU-D, RFU-D-HP, and RFU-S
Note: For detailed specifications of maximum profile per frequency and
channel bandwidth, consult your Ceragon representative.
The MRMC scripts listed in the following table are supported in FibeAir IP-20F or
IP-20A working with RFU-D, RFU-D-HP and RFU-S.
Note: XPIC is only supported with RFU-D and RFU-D-HP.
Table 10: MRMC Scripts, IP-20F or IP-20A with RFU-D, RFU-D-HP, and RFU-S
Script ID Channel BW Occupied BW XPIC (CCDP) Max Profile (ACM) Max Profile (Fixed)
4525 25 23.4 Yes 12 11

4505 30 28 Yes 12 11
4507 40 37.4 Yes 12 11
4510 50 47.2 Yes 12 11
4506 60 55.7 Yes 12 11
Page 44 of 129

5.3 Supported MRMC E-Band Scripts for FibeAir IP-20F, IP-20N, or

FibeAir IP-20A and RFU-E
The MRMC scripts listed in the following table are supported for FibeAir IP-20F, IP-
20N, or IP-20A units working with RFU-E.
Table 11: MRMC Scripts with IP-20F, IP-20N, or IP-20A and RFU-E
Script ID ETSI/FCC Channel BW Occupied BW Maximum Profile Maximum Profile
(ACM) (Fixed)
4509 ETSI 14 MHz 13.3 MHz 2 (8 QAM) 2 (8 QAM)

4504 ETSI 28 MHz 26.5 MHz 8 (512 QAM) 4 (32 QAM)
4701 ETSI/FCC 62.5 MHz 57 MHz 9 (1024 QAM) 7 (256 QAM)
4700 ETSI/FCC 125 MHz 115 MHz 8 (512 QAM) 7 (256 QAM)
4702 ETSI/FCC 250 MHz 230 MHz 7 (256 QAM) 6 (128 QAM)
5.4 Supported SRMs and Frequency Bands for Evolution IP-20LH

Systems
Note that in contrast to MRMC scripts in FibeAir IP-20 systems, scripts (SRMs) in
Evolution IP-20LH systems implement ACM as follows:
• ACM mode – Each SRM includes predefined minimum and maximum ACM
profiles. If you want a different maximum profile, you must select a different
SRM.
• Fixed mode – Each SRM works in a predefined profile. If you want a different
profile, you must select a different SRM.
Table 12: SRMs and Frequency Bands, Evolution IP-20LH Systems

SRM LH ODU ETSI/ Adjacent Modulation XPIC Channel BW Frequency Bands (GHz)
MRMC MRMC ANSI Channel (MHz) 4 5 L6 U6 7 8 10 11
13.75 
60 3060 2060 ETSI ACAP Fixed: 64 QAM No 14 
15 
13.75 
61 3061 2061 ETSI ACAP Fixed: 128 QAM No 14 
15 
28      
68 3068 2068 ETSI ACAP Fixed: 128 QAM No 29.65  V
30 
69 3069 2069 ETSI ACAP Fixed: 256 QAM No 28      
Page 45 of 129

29.65  
30 
75 3075 2075 ETSI ACAP Fixed: 128 QAM No 40    
76 3076 2076 ETSI ACAP Fixed: 256 QAM No 40    
81 3081 2081 ETSI ACAP Fixed: 256 QAM No 56        
ACAP 56      
82 3082 2082 ETSI and Fixed: 256 QAM Yes
ACCP
28      
ACM: 4-256
85 3085 2085 ETSI ACAP No 29.65  
QAM
30 
ACM: 4-256 40    
86 3086 2086 ETSI ACAP No
QAM
ACM: 4-256 56       
87 3087 2087 ETSI ACCP Yes
QAM
106 3106 2106 ANSI ACAP Fixed: 128 QAM No 30        
107 3107 2107 ANSI ANSI Fixed: 256 QAM Yes 30        
114 3114 2114 ANSI ANSI Fixed: 256 QAM Yes 40        
ACM: 4-256 30        
123 3123 2123 ANSI ANSI Yes
QAM
ACM: 4-256 40        
124 3124 2124 ANSI ANSI Yes
QAM
28      
128 3128 2128 ETSI ACCP Fixed: 128 QAM Yes 29.65  
30 V
28      
129 3129 2129 ETSI ACCP Fixed: 256 QAM Yes 29.65  
30 
130 3130 2130 ETSI ACCP Fixed: 128 QAM Yes 40    
131 3131 2131 ETSI ACCP Fixed: 256 QAM Yes 40    
28      
ACM: 4-256
132 3132 2132 ETSI ACCP Yes 29.65  
QAM
30 
ACM: 4-256 40    
QAM
Page 46 of 129

28     
ACM: 4-1024
135 3135 2135 ETSI ACCP Yes 29.65  
QAM
30 
ACM: 4-1024 40   
QAM
ACM: 4-256 25       
134 3134 2134 ANSI Yes Yes
QAM
28     
ACM: 4-1024
139 3139 2139 ETSI ACAP No 29.65  
QAM
30 
ACM: 4-1024 40   
140 3140 2140 ETSI ACAP No
QAM
ACM: 4-1024 30       
143 3143 2143 ANSI ACAP No
QAM
ACM: 4-1024 40       
144 3144 2144 ANSI ACAP No
QAM
152 3152 2152 ANSI Fixed: 128 QAM No 25       
Notes: When the user assigns an SRM to a radio carrier, the modulation
mode and maximum profile are determined by the SRM itself and are
not configured separately.
ACM SRMs function in adaptive mode, with no option to select the
minimum or maximum modulations other than the minimum or
maximum modulation enabled by the SRM itself.
Fixed SRMs provide a fixed modulation, which cannot be changed by
the user.
ODUs SRMs are supported on 5 to 11 GHz only. 4 GHz is not
supported with ODUs.
Page 47 of 129

5.5 Radio Options for FibeAir IP-20 Products

A FibeAir IP-20 split-mount or all-indoor system consists of an indoor unit (IDU)
and any of the following radio frequency units (RFUs):
• For IP-20F, and IP-20N or IP-20A with RIC-D, the following RFUs can be
connected to the IDU via optical fiber or electrical CAT-5/6 cables:
FibeAir RFU-D – MultiCore RFU that operates in the 6-42 GHz frequency
range, supporting channel bandwidth of 14-112 MHz and modulations of
BSPK to 4096 QAM.
FibeAir RFU-D-HP – High-Power MultiCore RFU that operates in the 4-11
GHz frequency range, supporting channel bandwidth of 14-112 MHz and
modulations of BSPK to 4096 QAM..
FibeAir RFU-E – Operates in the E-band frequency range, supporting 71-76
GHz and 81-86 GHz frequencies, channel bandwidth of 14, 28, 62.5, 125,
and 250, and modulations of BSPK to 1024 QAM.
FibeAir RFU-S – Operates in the 6-42 GHz frequency range, supporting
channel bandwidth of 14-112 MHz and modulations of BSPK to 4096 QAM.
• For IP-20G, IP-20GX, and IP-20N or IP-20A using RMC-A or RMC-B, the
following RFUs can be connected to the IDU via coaxial cables:
RFU-C – Operates in the 6 to 42 GHz frequency range, supporting channel
bandwidth of 3.5-60 MHz and modulations from QPSK to 2048 QAM.
RFU-C and RFU-Ce require RFU-C software version: 2.17.
1500HP and RFU-HP – FibeAir 1500HP and RFU-HP are high transmit
power RFUs designed for long-haul applications with multiple carrier
traffic. Together with their unique branching design, 1500HP/RFU-HP can
chain up to five carriers per single antenna port and ten carriers for dual
port, making them ideal for Trunk or Multi Carrier applications. The
1500HP/RFU-HP can be installed in either indoor or outdoor
configurations.
RFU-HP requires RFU software version: 5.14.
1500HP requires RFU software version 8.13a2.
RFU-A (including RFU-Ae/Aep) – Supported with FibeAir IP-20A, IP-20G,
and IP-20GX. FibeAir RFU-A is a high transmit power RFU designed for
compact long-haul applications. RFU-A offers a low scale trunk solution
with up to four radio carriers and operates in the frequency range of 5.8,
6, 7, 8, and 11 GHz.5
RFU-A requires RFU software version: 5.14.
Note: IP-20 software and firmware releases are provided in a single bundle
that includes software and firmware for all components and card
types supported by the system, including RFUs. For instructions on
software installation and upgrade, see Section 4.6 of the User Guide,
Upgrading the Software.
5
For the exact frequency bands supported by RFU-Aep, contact your Ceragon representative.
Page 48 of 129

5.6 Radio Options for Evolution IP-20 Systems
5.6.1 Supported XCVRs

An Evolution IP-20LH system consists of an IP-20N indoor unit (IDU) and any of the
following transceivers:
• Transceiver ACM, High Power (PN FLxxAAB0B, FLxxAAB0C, FLL6AAB0E,
FLU6AAB0E)
• Transceiver High Power, Space Diversity, XPAND IP/ACM compatible (PN
FLxxABB0B, FLxxABB0C, FLL6ABB0E, FLU6ABB0E)
5.6.2 Supported ODUs

The following ODUs are supported:
• ODUs ACM, High Power (PN FUxxAEByz-xxLA), where:
◦ xx: 05, 06, 07, 08, 11
◦ y: 0, 2, 4
◦ z: A, B
◦ L: L, U
Page 49 of 129

6. Interoperability with other Ceragon Products
6.1 FibeAir IP-20N and IP-20A Interoperability with other Ceragon

Products
The following table lists the radio cards that must be used in the FibeAir IP-20N
and IP-20A to provide interoperability between these products and other Ceragon
products. For IP-20 products, it is recommended to use the same software version
on both sides of the link. Interoperability with limited functionality is provided
between units using CeraOS 10.0 and units using older CeraOS versions, as shown
in the following table, only for the sake of upgrading from the remote side of the
link.
Table 13: FibeAir IP-20N and IP-20A Interoperability

Product FA IP-20N and IP-20A RMC Software Release on the Remote Side
IP-10G and IP-10E Using RMC-A (IP-20N and IP- I7.0, I7.1, I7.2
20A only)
IP-20N and IP-20A RMC-B T9.0, T9.5, T9.7, T10.0
IP-20G RMC-B G9.0, G9.5, G9.7, G10.0
IP-20GX RMC-B G9.0, G9.5, G9.7, G10.0
IP-20E RIC-D with RFU-E (IP-20N and C10.0 only (channel bandwidth of
IP-20A only) up to 250 MHz)
Note: FibeAir IP-20N and IP-20A are not interoperable with IP-10 R1.
6.2 Evolution IP-20LH Interoperability with other Ceragon Products

Evolution IP-20LH is not interoperable with other Ceragon products.
Page 50 of 129

6.3 IP-20F Interoperability with other Ceragon Products

IP-20F is interoperable over the radio link with IP-20N and IP-20A using RIC-D and
the RFUs and configurations shown in Table 14. IP-20F cannot be used with any
CeraOS version lower than CeraOS 10.0.
Table 14: Interoperability with Other Ceragon Products

Site 1 Site 2 Link Configuration
IDU RFU IDU RFU
IP-20F RFU-S IP-20N or IP-20A RFU-S 1+0

IP-20F RFU-D IP-20N or IP-20A RFU-D 1+0, 2+0 MC-ABC
IP-20F RFU-D-HP IP-20N or IP-20A RFU-D-HP 1+0 , 2+0 MC-ABC
IP-20F RFU-E IP-20N or IP-20A RFU-E 1+0
IP-20F RFU-E IP-20E 1+0
6.4 IP-20G Interoperability with other Ceragon Products

IP-20G is interoperable over the radio link with IP-20GX, and with IP-20N and IP-
20A aggregation nodes using RMC-B cards. The units on both sides of the link
must use the same CeraOS version. Interoperability with limited functionality is
provided between units using CeraOS 9.2 and units using CeraOS 9.2 and 9.2.5,
only for the sake of upgrading from the remote side of the link.
In addition, this release supports 1+0 links between IP-20S and IP-20G units on 10,
20, 28, and 30 MHz channels using non-XPIC scripts without ATPC, and without
Multi-Carrier ABC.
6.5 IP-20GX Interoperability with other Ceragon Products

IP-20GX is interoperable over the radio link with IP-20G, and with IP-20N and IP-
20A aggregation nodes using RMC-B cards. The units on both sides of the link
must use the same CeraOS version. Interoperability with limited functionality is
provided between units using CeraOS 9.2 and units using CeraOS 9.2 and 9.2.5,
only for the sake of upgrading from the remote side of the link.
With an RMC-A in an expansion slot, IP-20GX is also interoperable over the radio
link with IP-10G and IP-10E units, using software release I7.0, I7.1, or I7.2.
Page 51 of 129

7. Version Upgrade Compatibility

The following tables indicate software upgrade compatibility. In some cases, you
cannot upgrade directly from one version to another. Rather, you must upgrade
to an intermediate version, and then to the higher version. In general, the
following rules apply:
• Software versions can be upgraded directly to versions that are within two
versions of the current version. In some cases, direct upgrade is supported
between a larger number of versions. For upgrade compatibility between
specific versions, consult the compatibility matrixes in the following sections.
• Software versions 7.9 and higher can be upgraded directly to versions 8.5.5
and higher.
The same rules apply for backward compatibility.
Note: Direct upgrades between other versions may be possible in specific
circumstances. Do not perform such upgrades without first
consulting with and getting approval from Ceragon Customer
Support.
It is recommended to perform each upgrade on all units in the link and then to
perform the additional upgrade on all units in the link.
If it is planned to upgrade an IP-20N, IP-20A, IP-20LH, or IP-20G unit to 8.3 or
higher, and the unit currently runs or at one time ran versions 7.7, 7.7.5, or 7.7.7,
the following steps must be performed:
1 Upgrade first to release 8.2, according to the steps listed in the compatibility
matrixes below.
2 For IP-20N, IP-20A, and IP-20LH only: While the unit is running release 8.2, run
the following CLI command for each slot with a single radio carrier, i.e., each
radio carrier not assigned to a Multi-Carrier ABC group:
root> platform shelf-manager admin set slot <slot> state
disable
3 While the unit is running release 8.2, run the following CLI command for each
single radio carrier, i.e., each radio carrier not assigned to a Multi-Carrier ABC
group:
root> platform shelf-manager abc mode admin set slot <slot>
port <port> state disable
So, for example, to run these commands on RMCs in slots 3 and 4 of an IP-20N
unit, run the following commands:
root> platform shelf-manager admin set slot 3 state disable
root> platform shelf-manager admin set slot 4 state disable
root> platform shelf-manager abc mode admin set slot 3 port 1
state disable
root> platform shelf-manager abc mode admin set slot 4 port 1
state disable
4 Continue the upgrade process to version 8.3 or higher.
Page 52 of 129

7.1 Version Upgrade Compatibility for Chassis-Based Products

Note: Evolution IP-20LH was first released with version 7.7.5.
Table 15: Upgrade Compatibility for Chassis-Based Products
Release Y
7.2 7.5 7.5.5 7.7 7.7.5 7.9 8.0 8.0.5 8.2.5 8.3 8.3.7 8.5 8.5.5 8.7 9.0 9.2 9.2.5 9.5 9.7 10.0
7.2 – Y Y N N N N N N N N N N N N N N N N N
7.5 Y – Y Y N N N N N N N N N N N N N N N N
7.5.5 Y Y – Y Y N N N N N N N N N N N N N N N
7.7 N Y Y – Y Y N N N N N N N N N N N N N N
7.7.5 N N Y Y – Y Y N N N N N N N N N N N N N
7.9 N N N Y Y – Y Y Y Y N N N Y Y Y Y Y Y Y
From Release X
8.0 N N N N Y Y – Y Y Y Y N N Y Y Y Y Y Y Y
8.0.5 N N N N N Y Y – Y Y Y Y N Y Y Y Y Y Y Y
8.2.5 N N N N N Y Y Y – Y Y Y Y Y Y Y Y Y Y Y
8.3 N N N N N Y Y Y Y – Y Y Y Y Y Y Y Y Y Y
8.3.7 N N N N N N Y Y Y Y – Y Y Y Y Y Y Y Y Y
8.5 N N N N N N N Y Y Y Y – Y Y Y Y Y Y Y Y
8.5.5 N N N N N N N N N N Y Y – Y Y Y Y Y Y Y
8.7 N N N N N Y Y Y Y Y Y Y Y – Y Y Y Y Y Y
9.0 N N N N N Y Y Y Y Y Y Y Y Y – Y Y Y Y Y
Page 53 of 129

Release Y
7.2 7.5 7.5.5 7.7 7.7.5 7.9 8.0 8.0.5 8.2.5 8.3 8.3.7 8.5 8.5.5 8.7 9.0 9.2 9.2.5 9.5 9.7 10.0
9.2 N N N N N Y Y Y Y Y Y Y Y Y Y – Y Y Y Y
9.2.5 N N N N N Y Y Y Y Y Y Y Y Y Y Y – Y Y Y
9.5 N N N N N Y Y Y Y Y Y Y Y Y Y Y Y – Y Y
9.7 N N N N N Y Y Y Y Y Y Y Y Y Y Y Y Y – Y
10.0 N N N N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y –
The following are supported upgrade paths to version 10.0:

• From version 7.2: 7.2 > 7.5.5 > 7.7.5 > 8.0 > 10.0
• From version 7.5: 7.5 > 7.7 > 7.9 > 10.0
• From version 7.7: 7.7 > 7.9 > 10.0
• From version 7.7.5: 7.7.5 > 8.0 > 10.0
Versions 7.9 and higher can be upgraded directly to version 10.0.
Page 54 of 129

7.2 Version Upgrade Compatibility for IP-20F

No version below 10.0 is supported for IP-20F. Installing an older version will cause critical loss of functionality requiring RMA at the
customer’s expense.
Page 55 of 129

7.3 Version Upgrade Compatibility for FibeAir IP-20G

Table 16: Upgrade Compatibility for FibeAir IP-20G
Release Y
7.7 7.7.5 7.7.7 7.9 8.0 8.0.5 8.2 8.2.5 8.3 8.3.7 8.5 8.5.5 8.7 9.0 9.2 9.2.5 9.5 9.7 10.0
7.7 – Y Y N N N N N N N N N N N N N N N N
7.7.5 Y – Y Y N N N N N N N N N N N N N N N
7.7.7 Y Y – Y Y N N N N N N N N N N N N N N
7.9 N Y Y – Y Y Y Y N N N Y Y Y Y Y Y Y Y
8.0 N N Y Y – Y Y Y Y N N Y Y Y Y Y Y Y Y
8.0.5 N N N Y Y – Y Y Y Y N Y Y Y Y Y Y Y Y
8.2 N N N Y Y Y – Y Y Y Y Y Y Y Y Y Y Y Y
From Release X
8.2.5 N N N Y Y Y Y – Y Y Y Y Y Y Y Y Y Y Y
8.3 N N N N Y Y Y Y – Y Y Y Y Y Y Y Y Y Y
8.3.7 N N N N Y Y Y Y Y – Y Y Y Y Y Y Y Y Y
8.5 N N N N N N Y Y Y Y – Y Y Y Y Y Y Y Y
8.5.5 N N N Y Y Y Y Y Y Y Y – Y Y Y Y Y Y Y
8.7 N N N Y Y Y Y Y Y Y Y Y – Y Y Y Y Y Y
9.0 N N N Y Y Y Y Y Y Y Y Y Y – Y Y Y Y Y
9.2 N N N Y Y Y Y Y Y Y Y Y Y Y – Y Y Y Y
9.2.5 N N N Y Y Y Y Y Y Y Y Y Y Y Y – Y Y Y
Page 56 of 129

Release Y
7.7 7.7.5 7.7.7 7.9 8.0 8.0.5 8.2 8.2.5 8.3 8.3.7 8.5 8.5.5 8.7 9.0 9.2 9.2.5 9.5 9.7 10.0
9.5 N N N Y Y Y Y Y Y Y Y Y Y Y Y Y – Y Y
9.7 N N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y – Y
10.0 N N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y –
The following are supported upgrade paths to version 10.0:

• From version 7.7: 7.7 > 7.7.7 > 8.0 > 10.0
• From version 7.7.5: 7.7.5 > 7.9 > 10.0
• From version 7.7.7: 7.7.7 > 8.0 > 10.0
Versions 7.9 and higher can be upgraded directly to version 10.0.
Page 57 of 129

7.4 Version Upgrade Compatibility for FibeAir IP-20GX

Table 17: Upgrade Compatibility for FibeAir IP-20GX
Release Y
8.0 8.0.5 8.2 8.2.5 8.3 8.5 8.5.5 8.7 9.0 9.2 9.2.5 9.5 9.7 10.0
8.0 – Y Y Y Y N Y Y Y Y Y Y Y Y
8.0.5 Y – Y Y Y N Y Y Y Y Y Y Y Y
8.2 Y Y – Y Y Y Y Y Y Y Y Y Y Y
8.2.5 Y Y Y – Y Y Y Y Y Y Y Y Y Y
8.3 Y Y Y Y – Y Y Y Y Y Y Y Y Y
8.5 N N Y Y Y – Y Y Y Y Y Y Y Y
From Release X
8.5.5 Y Y Y Y Y Y – Y Y Y Y Y Y Y
8.7 Y Y Y Y Y Y Y – Y Y Y Y Y Y
9.0 Y Y Y Y Y Y Y Y – Y Y Y Y Y
9.2 Y Y Y Y Y Y Y Y Y – Y Y Y Y
9.2.5 Y Y Y Y Y Y Y Y Y Y – Y Y Y
9.5 Y Y Y Y Y Y Y Y Y Y Y – Y Y
9.7 Y Y Y Y Y Y Y Y Y Y Y Y – Y
10.0 Y Y Y Y Y Y Y Y Y Y Y Y Y –
Version 8.0 was the first supported version for IP-20GX. No version below 8.0 is supported for IP-20GX. Installing an older version, such as
IP-20G release 7.9, may cause critical loss of functionality.
All versions can be upgraded directly to version 10.0.
Page 58 of 129

8. NMS Version Compatibility

Note: There is no need to upgrade the NMS version to support a newer
CeraOS version unless there is a specific requirement for new
features or alarms that are only supported with the newer CeraOS
release. Older NMS versions will function properly with network
elements running newer CeraOS versions. The following tables
indicate the oldest NMS versions that support the new IP-20 device
features and alarms per CeraOS version.
8.1 NMS Version Compatibility for Chassis-Based Products
Table 18: NMS Version Compatibility for Chassis-Based Products
IP-20N, IP-20A, or IP-20LH Version Minimum PolyView Version Minimum NetMaster Version
Up to 7.6.0.0.0.58 N7.0 R13C01

7.7.0.0.0.42 N7.1 R14A
7.7.5.0.0.22 N7.1.1.1.0.1616 R13C01 b910, R14A
7.9.0.0.0.341 N7.1.1.1.0.1616 R14A02
8.0.0.0.0.675 N7.2.2 R14A02
8.0.5.0.0.157 N7.2.2 R14A02
8.2.0.0.0.335 N7.2.2 R14A02
8.2.5.0.0.22 N7.2.2 R14A02
8.3.0.0.0.483 N7.2.3 R14B00
8.3.7.0.0.120 N7.2.3 R14B02
8.5.0.0.0.288 N7.2.3 R15A00
8.5.5.0.0.110 N7.2.6 R15A00
8.7.0.0.0.166 N7.2.6 R15A00
9.0.0.0.0.300 N7.2.6 R15A00
9.2.0.0.0.422 N7.2.6 R15A01
9.2.5.0.0.203 R15A01
9.5.0.0.0.192 R15B00
9.7.0.0.0.144 R15B00
6
10.0.0.0.0.162 R16A00
6
PolyView 7.2.6 can manage IP-20N, IP-20A, and Evolution IP-20LH nodes running CeraOS
10.0.
Page 59 of 129

Note: TCC-B2 requires NetMaster version R14A04 or higher. TCC-B2-XG-MC

requires NetMaster version R14B00 or higher. PolyView supports
TCC-B2 and TCC-B2-XG-MC.
8.2 NMS Version Compatibility for IP-20F

Table 19: NMS Version Compatibility for IP-20F
IP-20F Version Minimum NetMaster Version
10.0.0.0.162 R16A00
8.3 NMS Version Compatibility for IP-20G

Table 20: NMS Version Compatibility for IP-20G
IP-20G Version Minimum PolyView Version Minimum NetMaster Version
8.0.0.0.0.661 N7.2.2 R14A02

8.0.5.0.0.158 N7.2.2 R14A02
8.2.0.0.0.335 N7.2.2 R14A02
8.2.5.0.0.22 N7.2.2 R14A02
8.3.0.0.0.483 N7.2.3 R14B02
8.3.7.0.0.120 N7.2.3 R14B02
8.5.0.0.0.288 N7.2.3 R15A00
8.5.5.0.0.110 N7.2.6 R15A00
8.7.0.0.0.166 N7.2.6 R15A00
9.0.0.0.0.300 N7.2.6 R15A00
9.2.0.0.0.422 N7.2.6 R15A01
9.2.5.0.0.203 R15A01
9.5.0.0.0.192 R15B00
9.7.0.0.0.144 R15B00
7
10.0.0.0.0.162 R16A00
7
PolyView 7.2.6 can manage IP-20G nodes running CeraOS 10.0.
Page 60 of 129

8.4 NMS Version Compatibility for IP-20GX

Table 21: NMS Version Compatibility for IP-20GX
IP-20GX Version Minimum PolyView Version Minimum NetMaster Version
8.2.0.0.0.335 N7.2.2 R14A04

8.2.5.0.0.22 N7.2.2 R14A04
8.3.0.0.0.483 N7.2.3 R14B02
8.5.0.0.0.288 N7.2.3 R15A00
8.5.5.0.0.110 R15A00
8.7.0.0.0.166 R15A00
9.0.0.0.0.300 R15A00
9.2.0.0.0.422 R15A01
9.2.5.0.0.203 R15A01
9.5.0.0.0.192 R15B00
9.7.0.0.0.144 R15B00
8
10.0.0.0.0.162 R16A00
8
PolyView 7.2.6 can manage IP-20GX nodes running CeraOS 10.0.
Page 61 of 129

9. Resolved Issues
This section lists bugs and limitations that were resolved in CeraOS 10.0.
9.1 Ethernet
No resolved issues for Ethernet in this release.
9.2 Platform
Table 22: Resolved Issues – Platform
# ID Subject Severity Description Applicability
1. 153920 RMC-E High Radio LOF occurs and the clock unit fails to lock when using an Evo IP-20LH
SyncE Pipe RMC-E with SyncE Pipe Regenerator Mode enabled.
Regenerator
2. 154238 TCC Redundancy High A protection configuration mismatch alarm is raised when the TCC FA IP-20N
in slot 11 is active. FA IP-20A
Evo IP-20LH
3. 153460 Under Voltage Medium In 1RU units, an under voltage alarm is not triggered on PDC-1 in FA IP-20N
Alarm low voltage conditions. FA IP-20A
Evo IP-20LH
4. 119261 Under-Voltage Medium There is no under-voltage alarm when PDC#1 is disconnected in a FA IP-20N
Alarm 1RU chassis. FA IP-20A
Evo IP-20LH
5. 155260 Cable Short Medium Occasional cable short events occur on RMC-B cards following FA IP-20N
Events upgrades from CeraOS 8.0.x to 8.3.x and higher. FA IP-20A
RMC-B
6. 154657 User Accounts Medium User account creation fails due to illegal expiration date. All
9.3 Radio
No resolved issues for Radio in this release.
9.4 Synchronization
No resolved issues for Synchronization in this release.
9.5 TDM – Native

Table 23: Resolved Issues – TDM - Native
# ID Subject Severity Description Applicability
1. 154079 LIC- Medium STM-RST fails when the radio RSL is approximately 7dB above the FA IP-20N
STM1/OC3- threshold. FA IP-20A
RST cards Evo IP-20LH
Page 62 of 129

10. Notes and Limitations
10.1 Ethernet
Table 24: Notes and Limitations – Ethernet
# ID Subject Severity Description Workaround Applicability
1. 110289 LLDP High LLDP does not work on LAGs. Do not enable LLDP on a LAG. All
2. 109637 Ethernet GE High Ethernet port on TCC in Slot 1 may Reset the chassis. FA IP-20N
not be active after software upgrade. FA IP-20A
Evo IP-20LH
3. 106713 G.8032 High Flapping Excessive BER on the link None All
causes the ring ports to be in pending
state.
4. 131332 LLDP High Upon activating Ethernet loopback Always enable swapping of MAC All
without swapping MAC addresses, addresses upon activating
LLDP remote table may add wrong Ethernet loopback.
entries.
5. 153922 LLDP in LAG Medium Changing the LLDP configuration of a None All
specific port in a LAG, may affect the
LLDP state of other members of this
LAG.
6. 152465 Media Type Medium Ethernet port may stay down when Set the Media Type explicitly All
with Auto the Media Type is set to Auto while when Auto Negotiation is set to
Negotiation Auto Negotiation is set to Off. Off.
Off
7. 149094 QoS Medium Policer CIR/EIR and Shaper CIR/PIR None FA IP-20N
LIC-X-E10 rates are limited to 1 Gbps per FA IP-20A
service. Evo IP-20LH
8. 150790 10G LIC and Medium When a 10G interface is part of the None FA IP-20N
MSTP protocol ring topology, and connected with FA IP-20A
card/line protection, a short down Evo IP-20LH
event may cause an MSTP topology
change.
9. 149613 CFM-SOAM Medium If a MEP is defined on an untagged When defining a MEP on a All
service point and it belong to a service with a MEG level of 0, if
service with MEG level = 0, the the VLAN for the service point
Y.1731 PDUs (CCM, Loopback) are on which the user is defining the
dropped. This means that loopback MEP is defined ambiguously (for
and continuity check will fail. example PIPE, Bundle-C, Bundle-
S, or All-to-One), the service
point’s C-VLAN/S-VLAN
parameter should not be set to
N.A.
Page 63 of 129

10. 145668 CFM-SOAM Medium 64 MEP pairs are supported for None All
IP20G and IP-20GX and 128 MEP
pairs are supported for IP20N, IP-
20A, and IP-20LH.
11. 148776 LAG Medium Although LAG should not be Do not configure LAG between a FA IP-20N
LIC-X-E10 configured between a 10GE and 1 GE 10GE port and a 1 GE port. FA IP-20A
Ethernet port, the system does not Evo IP-20LH
block such a configuration.
12. 140238 1588TC Medium 1588TC over MPLS is not supported. None FA IP-20N
MPLS FA IP-20A
Evo IP-20LH
FA IP-20G
13. 125670 MSTP Medium Changing the setting of a Multi- None All
Multi-Carrier Carrier ABC group can cause an MSTP
ABC topology change and a traffic hit.
14. 129466 Port Auto Medium If a port's configured speed is Changing the port admin state All
Negotiation changed to "100", while the port to Down and then Up may
speed is resolved on "1G" (with its minimize the time. This
peer), it may take ~90 seconds until operation is traffic-affecting.
the port is up again.
Note: For chassis-based systems,
this is only relevant for units using
TCC-B2-XG-MC.
15. 120029 MIB Medium The ifInDiscards and ifOutDiscards None FA IP-20G
columns of the IfTable standard MIB
are not functional.
16. 141360 LAG Medium If the user attempts to add an Ethernet ports must be disabled All
Ethernet port to a LAG when the port before adding to LAG.
is enabled, the LAG configuration will
fail.
Note: For chassis-based systems,
this is only relevant for units using
TCC-B2-XG-MC.
17. 110071 MSTP Medium Adding an NE to an MSTP ring where When adding an NE to an MSTP All
the new NE is in a different region ring, verify that the correct
than the ring can result in a traffic MSTP region is configured for
disruption. the new NE.
18. 120678 MSTP Medium The Bridge MSTI time since the last None FA IP-20G
Topology Change is always displayed FA IP-20GX
as 0 in the Web EMS and the CLI.
19. 109966 G.8032 Medium In 8032 Ring and Sub-Ring None All
Sub-Ring configurations, excessive BER
occasionally might not trigger a
topology change.
Page 64 of 129

20. 129516 Ethernet Ports Medium Ethernet port speed of 1G is fully Configure autoneg on the All
supported only if Auto Negotiation is interface and its peer.
enabled.
21. 107355 LLDP Medium When changing Ethernet ports from Reset the chassis. FA IP-20N
Slot 1 to Slot 12 (TCC to ELIC) or vice FA IP-20A
versa, LLDP tables may not adapt Evo IP-20LH
correctly.
22. 108511 G.8032 Medium There is a long convergence time on None All
ETH/Cascading ports when the
chassis is reset.
23. 129489 Physical Medium When configuring Ethernet physical Avoid configuring a port speed All
Interfaces port speed, the following options that is not supported by the
appear, even though not every port port. Doing so will generate an
supports such speeds:(1) 10, (2) 100, error message.
(3) 1000, (3) 2500, (4) 10000.
24. 71657 Jumbo Frames Medium The Management interface does not Use only standard frame sizes All
on MGT port support jumbo frame sizes above for the management interface.
1518 bytes.
Using jumbo sized packets on the
management interface may cause
loss of management.
25. 109995 LLDP Medium The Remote Table is not updated None All
with a new LLDP remote agent after
sending a changed LLDP frame
(different MAC, Chassis ID, Port ID)
before ageout.
26. 89870 LAG Medium LAG configuration requires that the Disable then enable the ports FA IP-20N
user disable and then re-enable before you create the LAG FA IP-20A
group members if they previously group. FA IP-20G
belonged to an HSB radio protection FA IP-20GX
group.
27. 115302 Automatic Medium Automatic state propagation is not None FA IP-20N
State supported on HSB protection groups. FA IP-20A
Propagation FA IP-20G
28. 143275 HSO and ASP Medium When ASP is enabled on both sides To avoid unwanted ASP trigger, FA IP-20N
of the link (local and remote units) configure a trigger delay via CLI. FA IP-20A
and a manual switchover is See Configuring Automatic State Evo IP-20LH
performed with HSO, a ~1 second Propagation (CLI) in the User
traffic hit occurs. Guide for FibeAir IP-20N, FibeAir
IP-20A, FibeAir IP-20LH, and
Evolution IP-20LH.
Page 65 of 129

29. 119263 G.8032 Medium When a LAG group is configured on a None FA IP-20G
radio interface and then a FA IP-20GX
convergence event occurs due to
shutting down of the radio interface,
the traffic disruption time may
exceed 50 msec.
30. 124791 CFM-SOAM Low The only available MEG name format None All
is charString.
31. 148061 CFM-SOAM Low The minimum interval between tx None All
frames is 1 second despite the ability
to set lower values.
32. 147339 Ethernet Low Setting the loopback duration time Set the duration value before All
Loopback while loopback is enabled will not set enabling the loopback.
the new duration value.
33. 133662 Y.1731 Low When untagged CCM frames are Avoid using untagged CCMs, All
Untagged CCM used, remote MEP MAC addresses since it is not standard.
may fail to be discovered.
34. 141484 Automatic Low The user interface allows Do not configure LAG as an ASP All
State configuration of a LAG as an ASP monitor interface.
Propagation monitor interface, even though this is
LAG not supported.
35. 143953 CFM Low Only one MD type, None, is None All
supported. Other MD types can be
created (operation not blocked) but
are not supported. According to
Y.1731.
36. 100280 Physical Low In the Web EMS, the "Physical In the Web EMS, relate to the All
Interfaces interfaces" table, Media type Media Type column as
column, displays the detected Media displaying the Detected Media
Type and not the configured Media Type. Both configured and
Type. detected media types can be
displayed using the CLI.
37. 113163 MSTP Low When a loopback to a root bridge is None All
in progress, 'TC in progress' is
indicated for the duration of the
loopback.
38. 89862 MRU Low Setting the MRU to a value lower Avoid setting the MRU to lower All
In-Band than standard Ethernet MRU=1518 values than the standard or use
Management may cause loss of in-band out of band management
management. instead.
39. 110086 G.8032 Low When configuring a G8032 sub ring Manually flush all nodes in the All
RPL, traffic stops for the WTR period sub-ring immediately after RPL
of time. configuration.
Page 66 of 129

40. 120090 Ethernet Low Loopback on an Ethernet port toward Disable LAG before performing All
Loopback the line does not work on LAG the loopback.
LAG groups.
41. 111258 In-band Low In-band management does not work For S-Tag service points, All
Management with an S-Tag service point and configure the in-band
management encapsulation management as tagged traffic.
"untagged".
42. 118118 Loopback Low Configuring the in-band management When setting a service to All
In-band service to "reserve" state may cause "reserve" state from the Web
Management loss of management to the remote EMS, make sure to avoid
site. In the EMS Web interface, the reservation of the management
user has an option to select "all" service.
services and set them to "reserve"
state.
43. 84738 QoS Low The Shaper profile ID is limited to 1 Use shaper profile IDs within the All
to 250 although the range is range 1 to 250.
indicated to be 1 to 256.
44. 77837 Ethernet Low The VLAN CoS-override option does None All
Services not work for PIPE service points.
45. 120463 Ethernet Low Auto detection of media type mode None All
Interfaces is only supported when auto-
negotiation is enabled.
46. 126473 RMON Low etherStatsOversizePkts counts the The internal MIB has the OIDs FA IP-20F
Counters total number of packets received that provide OversizePkts and FA IP-20N
that were received with total length Jabbers that count for packets in FA IP-20A
of 1522 bytes and not packets with total length of 1519-1522. Evo IP-20LH
length of 1518 bytes as required by FA IP-20G
the rmon.statistics MIB.
etherStatsJabbers counts the total
number of packets received that
were longer than 1522 bytes that
had bad FCS, and not packets with
length of 1518 bytes as required by
the rmon.statistics MIB.
Page 67 of 129

47. 119303 Ethernet Port Low Activation of Ethernet port loopback Use a short timer for loopback. All
119304 Loopback toward the line in Ring or Sub-ring
MSTP network topologies using MSTP
and/or G.8032 protocols may cause
traffic loss during the time when
loopback is active.
Network convergence to the
alternative path will not be triggered
due to activation of the loopback.
The network will return to normal
operation after expiration of the
loopback timer.
48. 118189 RMON Low When working with a 1+1 HSB Ignore RMON counters of the FA IP-20N
Counters configuration, RMON counters of the standby radio, which does not FA IP-20A
standby radio interface continue pass traffic. Evo IP-20LH
counting received packets. FA IP-20G
FA IP-20GX
49. 117445 Ethernet Low When working with Ethernet packets None All
Services using 802.3 format "Packet length"
instead of Ethernet II "Ethertype"
field, the packet length of the frame
will not be updated upon push/pop
VLAN operation.
50. 117129 LLDP Low The LLDP Remote system/Remote Ignore the redundant entry. All
119061 MNG table displays an unnecessary
entry after cold restart of the
remote peer.
51. 116367 G.8032 Low Unidirectional failure on the Establish ASP between the All
interconnect node (between ring interconnect node and its peer
and sub-ring) is not recovered by the
on the sub-ring.
sub-ring (according to the protocol).
52. 112622 MSTP Low Reconvergence is triggered in a fiber None All

LAG member when another member
is copper and is set to Admin - Down.
53. 112320 LLDP Low StatsRxPortTLVsUnrecognizedTotal Ignore this counter. All

counts all TLVs.
54. 110430 RMON Low Multicast and broadcast packets are None All
Counters counted as unicast packets in RMON
counters if the packet size is larger
than 1518 bytes.
55. 109463 LLDP Low TX frames are always counted even Refer to port RMON counters All
though if no LLDP frames are sent. instead of LLDP statistics
counters.
56. 109374 LLDP Low LLDP Re-init delay does not work Ignore re-init delay. All
properly.
Page 68 of 129

57. 109366 LLDP Low The maximum value of the TX Use LLDP TX intervals of up to All
interval is 3600 seconds rather than 3600 seconds.
32768 seconds (as incorrectly
indicated in the CLI).
58. 108340 RMON Low RMON counters for a LAG group and Ignore RMON counters of All
LAG an Ethernet port which is a member disabled Ethernet interfaces.
of the LAG group continue to be
counted even if the Admin status of
both the port and the LAG group are
disabled by user configuration.
59. 107463 LLDP Low In the LLDP local management table None All
and in MNG TLV, Mng-Addr-If-ID is
indicated as 0, instead of the IfIndex
of the management port.
60. 89312 G.8032 Low The G.8032 Destination MAC Use the CLI to change the All
address change requires system G.8032 Destination MAC
reset.
address; the change requires
system reset.
61. 87712 LAG Low After creating a LAG group, set all None All
Ethernet attributes. Otherwise, the
system will use the default values
rather than inheriting the first
member's attributes.
62. 86850 G.8032 Low The G.8032 convergence time in None All
88616 cases of 8 or more nodes may
sometimes slightly exceed 50 msec.
63. 84747 G.8032 Low If you clear a G.8032 Forced Switch The Clear command should be All
on a ring node after performing a issued between the Manual
Manual Switch on another ring node, Switch and Forced Switch
the second ring node remains in commands.
Forced Switch state.
64. 82787 MSTP Low Changing port priority configuration Configuration should be All
in region boundaries (or affecting performed before traffic is
region boundaries) causes a traffic started.
hit on all instances (including 4095).
65. 75903 GE Ports Low Half duplex mode is not supported Do not use half duplex mode. All
for the GE ports.
66. 73994 Ethernet Low When the management service point Set the C-Vlan Preservation field All
Services is S-Tag, the user will get an inner tag to Disable when creating an S
encapsulation of C equals 4095 due Tag service point in a
to the default state of the Preserve Management service.
C-tag parameter.
Page 69 of 129

67. 69704 Ethernet Low VLAN CoS override is not supported The user can override the CoS All
88753 Services in the Web EMS unless the service on the service point level for all
point is classified to C-Bundle or S service points that do not have a
Bundle. Bundle classification. If the user
must configure VLAN CoS
override, it can be configured
via the CLI.
68. 68252 SNMP Low It is not possible to attach a policer This operation can be All
profile to an Ethertype port policer performed via CLI or the Web
using SNMP. Therefore, this EMS.
operation cannot be performed via
NMS.
69. 66081 Ethernet Low VLAN CoS override is not supported None All
Services for All-to-One service points.
70. 58544 SFP Modules Low When using SFP of model type Other SFP models do not cause All
"finisar 1550mm 80km": If a fiber is this problem.
extracted from the SFP, traffic on the
neighbor RJ-45 port may be
interrupted for a short period.
71. 110020 MSTP Low A radio protection switch triggers an In case of G.8032, configure a All
114633 G.8032 MSTP topology change. In the case of holdoff of 100msec.
G.8032, a radio protection switch
triggers a ring protection switch. If
ERPI is revertive, upon switching to
protecting radio, the WTR is
triggered for switch back.
72. 87482 WFQ Low The valid WFQ weight range is 1 to Entering a value that is outside All
67016 20. of the range will fail.
73. 116296 G.8032 Low In the event of disconnection or None All

116350 failure or shutting down of a copper
119197 Ethernet line interface, the traffic
disruption time may exceed one
second. Convergence time due to
similar events on fiber Ethernet line
interface may exceed 50msec.
Page 70 of 129

10.2 Platform
Table 25: Notes and Limitations – Platform
1. 120499 1+1 HSB High Revertive switchover can be Configure the option of 1+1 FA IP-20N
revertive initiated even if the primary radio HSB to switchover upon FA IP-20A
carrier has excessive BER. Excessive-BER to "enable". FA IP-20G
FA IP-20GX
2. 137626 TCC High Manual TCC switchover generates a None Evo IP-20LH
Redundancy service disruption time higher then
HSO 500msec.
RMC-E
3. 137691 Software High The software download and None All

Download upgrade process can take
significantly longer when the target
version is 8.3 or higher and the
source version is lower than 8.3.
The download time depends on
bandwidth. The installation time
can be up to 20-30 minutes.
4. 137592 TCC High ASP alarms are cleared on the None FA IP-20N
Redundancy standby TCC regardless of the ASP FA IP-20A
Automatic state.
State
Propagation
5. 148533 Unit Info High When generating a Unit Info file, a Before generating a Unit Info All
Configuration configuration file is not file, back up the unit’s
File automatically generated. This configuration.
means that the Unit Info file will use
the latest configuration file to have
been backed up to a restore point,
or if no configuration file has been
backed up, will not include a
configuration file.
Note: For troubleshooting, it is
important that an updated
configuration file be included in
User Info files that are sent to
customer support.
Page 71 of 129

6. 125536 TCC High In rare cases, when the TCC in Slot While the active TCC is the TCC FA IP-20N
Redundancy 11 is the active TCC, resetting to the in Slot 11, TCC FA IP-20A
standby TCC in Slot 1 causes traffic extraction/insertion, Evo IP-20LH
drop for RMC-E and LIC-STM1/OC3- configuration changes, and
RST cards. copy to mate operations
should be performed only
during maintenance windows
to avoid traffic hits on the
RMC-E or LIC-STM1/OC3-RST
card.
7. 156017 LIC-X-E10 LEDs Medium Although LIC-X-E10 cards support Active/Standby interface FA IP-20N
interface protection, their LEDs do indication is available via the FA IP-20A
not indicate active/standby status Web EMS and CLI.
like other traffic LICs.
8. 151506 TCC Medium Protection Mismatch remains after None FA IP-20N

Redundancy copy-to-mate when the software FA IP-20A
download path is changed. Evo IP-20LH
9. 151372 HSO and card Medium An unusually high disruption time Do not perform manual TCC FA IP-20N
protection may occur when combining TCC HSO switchover within ten minutes FA IP-20A
with card protection. If TCC of a previous switchover. Evo IP-20LH
switchover is repeated within a 10-
minute span, a traffic hit may take
place arising from the card
protection group or groups.
10. 151436 Auto Medium In case the SFP TX direction is muted It is recommended to set Auto All
Negotiation or disconnected, the RX path may be Negotiation to Off on SFP
with SFP Port disrupted when Auto Negotiation is ports.
enabled.
11. 151247 REST Medium A REST command may return "OK" Make sure the command All
Commands status even if the user profile does succeeded by checking the
not have privileges. Even though the status.
command returned with "OK", no
change will take place.
12. 151222 SNMPBulk Medium When one or more of the OIDs in the Delete unsupported OIDs or All
SNMPBulk request are not read them separately.
supported, the entire request will
fail. All OIDs will be marked
noSuchInstance/noSuchObject.
Page 72 of 129

13. 148057 TCC Medium When inserting a new, unconfigured Before inserting the new TCC, FA IP-20N
Redundancy TCC without using lockout, a make sure that either: FA IP-20A
protection switch may occur. • The new TCC has the same Evo IP-20LH
configuration as the
installed TCC.
• Set TCC Lockout to On
before installing the TCC.
Set Lockout to Off after
performing copy-to-mate.
Note: It is always good
practice to use TCC lockout
before performing
maintenance on the standby
TCC.
14. 148679 TCC Medium It is not supported to use different Use TCCs with identical TCC FA IP-20N
Redundancy TCC types in the same chassis. This P/Ns when enabling TCC FA IP-20A
includes a FIPS-compliant TCC and a redundancy.
non-FIPS-compliant TCC.
15. 147380 HSO Medium Cannot enable or disable MNG port The user must disable HSO in FA IP-20N
2 when HSO is enabled. order to enable or disable FA IP-20A
MNG port 2. Evo IP-20LH
16. 145851 Unit Medium An active unit does not complete Before performing download FA IP-20G
Redundancy installation of a new software and installation procedures,
Software version if there is no connection to verify that the protection
Installation the mate unit. cable is connected.
17. 142508 SNMP Medium The first SNMPv3 user created after Either: FA IP-20N
reset is not enabled until either • From the Web EMS or CLI, FA IP-20A
SNMP is restarted or the user is disable then re-enable the Evo IP-20LH
deleted and added again. SNMP agent, OR FA IP-20G
FA IP-20GX
• Add an additional SNMPv3
user, OR
• Delete the SNMPv3 user
that was created after reset,
then re-add the user.
18. 143888 TCC Medium In units with TCC enabled, an Perform lockout before FA IP-20N
Redundancy unexpected switchover occurs in downgrading to a version FA IP-20A
the following scenarios: older than 8.3.7 or inserting a Evo IP-20LH
• Downgrading from version 8.3.7 TCC in Slot 11 with a version
or higher to a version older than older than 8.3.7.
8.3.7.
• Inserting a TCC with a version
older than 8.3.7 into Slot 11 when
the TCC in Slot 1 is running
version 8.3.7 or higher.
Page 73 of 129

19. 130842 HSB Lockout Medium In protection lockout state, a Release the lockout for proper FA IP-20N
request to change the remote HSB operation. FA IP-20A
transmitter is not sent to the FA IP-20G
remote unit.
20. 139619 Overvoltage Medium Overvoltage alarms are raised None FA IP-20N
Alarm without a PDC slot indication. FA IP-20A
Evo IP-20LH
21. 141465 X.509 Medium When creating an X.509 certificate, None All141471
Certificate make sure that (i) the Country
Name is exactly two letters long,
and (ii) the Common Name and
Email Address are no longer than 64
characters.
22. 135126 HSB Medium With respect to HSB interfaces, The HSB interface's speed FA IP-20N
MIB ifSpeed and ifHighSpeed standard should be related as half of FA IP-20A
MIBs return the interface's capacity the returned speed. FA IP-20G
multiplied by 2. FA IP-20GX
23. 136806 TCC Medium TCC ports on Slot 11 are identified The relevant active TCC ports FA IP-20N
Redundancy as Slot 1 (including service and can be identified by the Active FA IP-20A
alarms). slot identifier in the Web EMS. Evo IP-20LH
24. 128423 TCC Medium If TCC redundancy is disabled, Slot Just before disabling TCC FA IP-20N
Redundancy #1 must be set to be the active TCC. redundancy, make sure to FA IP-20A
switchover to Slot 1. Evo IP-20LH
25. 123143 Measured Medium Measured input voltage may have None FA IP-20G
input voltage +/- 2V tolerance. FA IP-20GX
has limited
tolerance
26. 63577 Software Medium Performing reset during the Do not reset the system during All
Management software installation process may software installation.
render the system unusable and
unable to re-install a version.
27. 107201 Software Medium Downgrade of the software version If a downgrade is accidently FA IP-20G
Management to release 7.7.0.0.0.27 is not performed, restoring the
supported! Attempting to factory default settings
downgrade the software to version resolves the problem.
7.7.0.0.0.27 will cause malfunction
of the Interface Manager in the
Web EMS.
28. 112167 Access Control Medium Creation of an unauthorized user None FA IP-20G
Security via REST fails but is marked as OK in
REST (bug 112085). Creation of this
user is ignored by the Security Log.
Page 74 of 129

29. 125569 TCC Medium When using SNMPv3 with TCC None FA IP-20N
Redundancy redundancy, traps sent from the FA IP-20A
active TCC have no CONTEXT, while Evo IP-20LH
traps sent from the standby TCC are
sent with CONTEXT = "unit_1".
30. 124882 Multi-Carrier Medium To delete a Multi-Carrier ABC/HSB- None FA IP-20N

ABC SD configuration and reuse the FA IP-20A
carriers as 1+0/1+1, you must
perform the following steps in this
order:
• Delete the HSB-SD protection
group.
• Delete the Multi-Carrier ABC
group.
• Delete Multi-Carrier ABC mode.
31. 119695 Software Medium Upgrading back to 7.9 after having Versions prior to T7.9 do not FA IP-20N
Upgrade with previously downgraded to previous support TCC Redundancy. FA IP-20A
TCC versions while TCC Redundancy was Make sure to disable TCC Evo IP-20LH
Redundancy enabled may render the system Redundancy before
enabled unusable. downgrading.
32. 118448 TCC Medium The Admin state for TCC After the upgrade, manually FA IP-20N
Redundancy Redundancy is down after enable TCC Redundancy and FA IP-20A
upgrading the software from 7.7.5 then perform copy-to-mate. Evo IP-20LH
to 7.9 or higher.
33. 116361 Multi-Carrier Medium When adding a 1+1 HSB-SD group Reset the card of each FA IP-20N
ABC to a Multi-Carrier ABC group, the member of the group. FA IP-20A
1+1 HSB-SD Operational Status of the HSB-SD
group may remain Down, even
though the Operational Status of
the group's members is Up.
34. 127071 CLI Scripts Medium In CLI scripts, when configuring card None FA IP-20N
admin-state, a wait state of at least FA IP-20A
6 seconds should consecutively be Evo IP-20LH
added to make sure the operation is FA IP-20GX
completed successfully.
35. 131468 Alarms Medium An ASP alarm (interface is down due None FA IP-20N
ASP to Automatic State Propagation) FA IP-20A
may be raised even If the port to Evo IP-20LH
which it is attached is disabled.
Page 75 of 129

36. 124906 Software Medium When uploading a new software Make sure the path and file All
Management version, the following limitations name strings are within the
exist for the length of the path and defined limitations.
filename strings:
• With IPv4: Path and File Name
cannot exceed 236 chars.
• With IPv6: Path and File Name
cannot exceed 220 chars (due to
longer IP).
37. 119927 TCC Medium The Standby TCC’s CLI prompt does Use the following CLI FA IP-20N
Redundancy not reflect its slot. commands per TCC slot that FA IP-20A
return the TCC slot activity:
Evo IP-20LH
• platform management
inventory show-info Slot 1
• platform management
inventory show-info Slot 11
38. 112062 SNMP IPv6 Medium No SNMP and REST input None All
validation is performed for the
following IPv6 parameters:
• IPv6 Default Gateway
• IPv6 Sw. Download Server
• IPv6 Config Mgt Server
• IPv6 Trap Manager Server
If the IPv6 command is illegal with
regard to any of these items, it will
not be configured to the interface,
but the user interface will indicate
that it has been configured.
39. 128286 X.509 Security Medium The CSR "generate and upload" None FA IP-20F
Certificate status is only updated for upload FA IP-20N
(CSR) status. FA IP-20A
FA IP-20G
FA IP-20GX
40. 110817 Multi-Carrier Medium When using Multi-Carrier ABC, Slot Any card that does not belong FA IP-20N
ABC #3 must be populated with a card to the Multi-Carrier ABC group FA IP-20A
that belongs to the Multi-Carrier must be placed in a slot other
ABC group. than Slot 3.
41. 127456 Multi-Carrier Medium In a unit using TCC-B-MC or TCC-B2- In a unit using TCC-B-MC or FA IP-20N
ABC XG-MC, if Slot 3 is occupied by an TCC-B2-XG-MC, an RMC in Slot FA IP-20A
RMC that does not belong to a 3 should always be assigned to
Multi-Carrier ABC group, a Multi-Carrier ABC group.
unexpected behavior can occur
affecting the traffic flow.
Page 76 of 129

42. 154311 Activation Low The CLI command "platform Use the new CLI command: All
Keys activation-key show information" is “platform activation-key show
no longer supported, and returns all”.
error 106.
43. 153217 Radio PMs Low Radio PMs and Statistics are None FA IP-20N
updated once every 15 minutes FA IP-20A
even when the Interval Type is set FA IP-20F
to 24 hours. FA IP-20G
FA IP-20GX
44. 151976 SNMP Low genEquipServicesNGPWServiceDs0b None FA IP-20N

undle FA IP-20A
(OID .1.3.6.1.4.1.2281.10.8.4.6.5.1.6 Evo IP-20LH
) contains a wrong value.
45. 153798 Activation Key Low The Activation Key Overview table is Disable Demo mode to view All
not updated in Demo mode, so that the updated status.
if a new activation key is applied
while the unit is in Demo mode, the
user cannot determine the updated
violation status of system features.
46. 152747 TCC Low Changing the software download Update the changed download FA IP-20N
Redundancy path causes a configuration path in both TCCs or perform FA IP-20A
mismatch alarm and degradation of copy to mate. Evo IP-20LH
the switchover performance.
47. 152745 TCC Low Only one reason for a configuration Perform copy to mate. FA IP-20N
Redundancy mismatch is shown. FA IP-20A
Evo IP-20LH
48. 152817 HTTP Software Low If the user attempts to download After the error occurs, simply All
Download the wrong type of software package download the correct software
(e.g., an IP-20C software package package.
for an IP-20N or an IP-20N software
package for an IP-20C), no error
message is displayed until the
download is approximately 80%
complete.
Page 77 of 129

49. 148523 Unit Info Low When generating a Unit Info file, 1. Generate a Unit Info file FA IP-20N
TCC the information for the Standby TCC for the standby TCC. FA IP-20A
Redundancy is not updated. 2. Wait for the Unit Info file Evo IP-20LH
to be successfully
generated.
3. Generate a Unit Info file
for the active TCC.
4. Wait for the Unit Info file
to be successfully
generated.
5. Export the Unit Info file.
6. Verify that the ZIP file
created by the export
contains two archives.
50. 150763 REST Low The REST command does not Paths should be written with All
commands and support the backslash (\) character the forward slash (/).
paths for paths.
51. 149813 HSO Low In an HSO configuration, if the user 1. Wait for the standby TCC FA IP-20N
moves to the Standby tab of the to finish rebooting. FA IP-20A
Web EMS while the standby unit is 2. Close then reopen the Evo IP-20LH
rebooting, the browser may browser, and log back
become frozen until the TCC has into the Web EMS.
finished rebooting.
52. 147799 IP-20G Unit Low A force switch triggers switchover None IP-20G
Redundancy even when the system is in a
Lockout state.
53. 117657 TCC Low No switchover takes place after a Keep the removed TCC out of FA IP-20N
Redundancy Fast Remove & Insert of the Active its slot for more than 10 FA IP-20A
TCC. seconds. Evo IP-20LH
54. 136526 Multi-Carrier Low A Multi-Carrier ABC group can be When deleting a Multi-Carrier Evo IP-20LH
ABC deleted via REST and SNMP even if ABC group via REST or SNMP,
the group contains members. make sure to remove the
members from the group
before deleting the group.
55. 116767 TCC Low User Profiles (user names and When creating a new user FA IP-20N
Redundancy passwords) are not copied to mate. profile, you must create the FA IP-20A
Access Control profile manually in both units. Evo IP-20LH
56. 120738 TCC Low Port PMs can be enabled in the Make sure to enable PMs for FA IP-20N
Redundancy Standby unit for the Ethernet ports. the active unit, not the FA IP-20A
PMs standby unit. Evo IP-20LH
57. 120709 TCC Low The Defective Blocks counter is None FA IP-20N
Redundancy cleared automatically in the FA IP-20A
Standby unit after switchover. Evo IP-20LH
Page 78 of 129

58. 118070 TCC Low Protection Admin is Disabled on the Perform copy-to-mate. FA IP-20N
Redundancy Standby after enabling the FA IP-20A
Protection Evo IP-20LH
59. 120695 Alarms Low The Lockout alarm or event can None FA IP-20N
appear inconsistently on the Active FA IP-20A
or Standby unit. Evo IP-20LH
60. 64415 Configuration Low In the CLI interface there is no Use the Web EMS interface to All
Management progress indication when creating a check progress.
CLI backup configuration file.
61. 119347 Access Control Low Adding a user account via the Web None All
EMS adds the user as required, but
is accompanied by a failure
message.
62. 100335 Access Control Low After reaching the maximum Establish a connection using All
number of failed login attempts, the the admin user account and
user is notified that his or her reset the account.
account has been frozen due to the
number of failed attempts plus 1.
63. 121443 TCC Low After performing copy-to-mate, you Make sure to wait until the FA IP-20N
Redundancy cannot perform copy-to-mate again process is complete. FA IP-20A
until the standby TCC comes back Evo IP-20LH
online.
64. 111629 Software Low While downloading a new software Wait 20 minutes or perform a All
Management version to a unit, the user has no hardware reset.
ability to cancel file transfer upon
failure of the FTP connection. Upon
failure, the unit only identifies the
FTP connection failure after a
timeout period of 20 minutes.
Until the timeout expires, the user
cannot restart the download and
cannot cancel the download
operation.
65. 114849 TCC Low The Web browser may freeze if you Either: FA IP-20N
Redundancy click the "Standby TCC" tab right • Wait several minutes for the FA IP-20A
after extracting the Standby TCC Web browser to return to Evo IP-20LH
from the chassis. normal operation, or
• Reinsert the standby TCC, or
• Issue a power cycle to the
system.
Page 79 of 129

66. 136372 Activation Keys Low Recovery from a second radio In the event of a second radio FA IP-20G
carrier activation key violation carrier activation key violation,
requires the unit to be rebooted. In reboot the unit.
case reboot was not performed,
effective capacity is limited to no
more than 100 Mbps.
67. 136123 Configuration Low Restoring a backup file that was Be careful not to restore a 2RU FA IP-20N
Management generated on a 2RU IP-20N, IP-20A, configuration file on a 1RU FA IP-20A
or IP-20LH chassis on a 1RU unit is unit. Evo IP-20LH
not blocked, and may cause
application failures.
68. 134998 TCC Low A Sync Source can be added, edited Do not add, edit, or delete FA IP-20N
Redundancy or deleted on the standby TCC. Sync sources on the standby FA IP-20A
TCC but rather, perform these
configurations on the active
TCC and use Copy-to-Mate to
copy them, as with other
configurations.
69. 139766 Access Control Low Occasionally, user fails to log in Before configuring Password All
when Password change for first change for first login to Yes,
login is configured to Yes. make sure Failure login
attempts to block user is
configured to a value greater
than 1.
70. 114777 Telnet Low The user should not open more Close unnecessary telnet FA IP-20F
than ten telnet session at the same connections. FA IP-20G
time. When the user does open FA IP-20GX
more than ten telnet sessions, the
system management response
slows down and the Web EMS stops
working.
71. 126137 TCC Low If the user wants to set the unit to Make sure the active TCC is in FA IP-20N
Redundancy its default configuration and TCC Slot #1. FA IP-20A
redundancy is enabled, the user Evo IP-20LH
must make sure the active TCC is in
Slot #1.
72. 139640 Voltage Level Low The voltage level presented can None FA IP-20N
suffer from 1V inaccuracy. FA IP-20A
Evo IP-20LH
Page 80 of 129

73. 108008 Configuration Low Configuration files can only be Use different configuration All
123457 Management copied to the same type of files.
platform:
• The units must have the same
chassis types (1RU or 2RU).
• The same card types (e.g., RMC,
Ethernet LIC, E1/DS1 LIC) must be
inserted in the same slots in both
units.
• The units must have the same
TCC type.
• For IP-20G units, users cannot
save a configuration file from a
unit that supports TDM and
upload it to a unit without a TDM
interface, and vice versa.
74. 120641 TCC Low When downgrading from version Prior to downgrading from FA IP-20N
Redundancy 7.9 or higher to version 7.7.5 version 7.9 or higher to FA IP-20A
(which does not support TCC version 7.7.5, make sure the
redundancy), the system performs active TCC is in Slot 1 and
switchover if the active TCC was in then set Protection Admin to
Slot 11. Disable.
75. 72389 Physical Low Setting the port media type to Be careful to avoid incorrect All
Interfaces unsupported values is not blocked configurations.
by the GUI. For example, an SFP
port can be set to RJ-45.
76. 127160 TCC Low In rare cases, performing copy-to- Perform an additional copy-to- FA IP-20N
Redundancy mate when a "configuration mate. FA IP-20A
mismatch" alarm is raised does not Evo IP-20LH
clear the alarm.
77. 110603 Shelf Low Consecutive activation of 'shelf In CLI scripts or when pasting FA IP-20N
management manager' and 'group creation' CLI CLI commands in bulk, insert a FA IP-20A
and Group commands can result in five second delay between the Evo IP-20LH
configuration configuration failure. following commands when FA IP-20GX
CLI commands used consecutively:
platform shelf-manager
multiplex-traffic-lines set XX
platform shelf-manager
expected-cardtype set XX
platform shelf-manager abc
mode admin XX
pwe3 card-group add id XX
static-lag add lagid XX
radio protection create group
X radio XX
Page 81 of 129

78. 121336 TCC Low An event with the wrong “reason” is None FA IP-20N
Redundancy raised for manual switch FA IP-20A
switchover. Evo IP-20LH
79. 120900 TCC Low Service points can be configured on Make sure to configure service FA IP-20N
Redundancy the Standby unit via CLI. points on the active unit, not FA IP-20A
the standby unit. Evo IP-20LH
80. 120753 TCC Low Physical interfaces can be Make sure to configure FA IP-20N
Redundancy configured on the Standby unit. physical interfaces on the FA IP-20A
Physical active unit, not the standby Evo IP-20LH
Interfaces unit.
81. 120747 TCC Low The user can set loopback for the Make sure to set loopback on FA IP-20N
Redundancy ports on the Standby unit. the active unit, not the FA IP-20A
Loopback standby unit. Evo IP-20LH
82. 120394 Configuration Low The row number instead of port ID None All
Log is written in the Configuration log
when performing a configuration
on a port.
83. 114545 TCC Low Sometimes, chassis reset causes If the TCC in Slot 11 becomes FA IP-20N
121066 Redundancy election of the TCC in Slot 11 as the the active TCC, perform a FA IP-20A
active TCC, even if the TCC in Slot 1 manual switchover to make Evo IP-20LH
is functioning properly. The first to the TCC in Slot 1 the active
boot becomes the Active TCC. TCC.
84. 98569 Unit Info File Low The CLI command platform unit-info None All
file status shows the status of unit-
info file transfer and not the status
of file creation.
85. 97314 Access Control Low Users with read/write level Assign management privileges All
permissions for the Radio group together with the radio.
without Management group access
configured cannot access radio
tables.
86. 117836 Software Low An unnecessary "download-to- Do not use this command. All
Management standby" command is available in
the CLI.
87. 126024 PMs Low Ethernet PMs are not supported on None FA IP-20F
Multi-Radio the Multi-Carrier ABC group level. FA IP-20N
ABC FA IP-20A
Evo IP-20LH
FA IP-20G
Page 82 of 129

88. 121666 TCC Low When changing the MSTP Instance Reset the chassis to clear the FA IP-20N
Redundancy per Service mapping for a Point-to- "configuration mismatch" FA IP-20A
Point service, a "configuration alarm. Evo IP-20LH
mismatch" alarm is raised, and this
alarm is not cleared by performing
copy-to-mate.
89. 117842 TCC Low Attempting to install a software Enable TCC redundancy and FA IP-20N
Redundancy version to the standby TCC using perform copy-to-mate before FA IP-20A
the CLI fails if TCC Redundancy is attempting to install a Evo IP-20LH
not enabled on the standby TCC. software version on the
standby TCC.
90. 127698 CLI Scripts Low Long CLI scripts may fail while being Add several minutes of "wait" All
executed. states at the beginning of the
script.
91. 131671 Software Low In rare cases, after a software It is recommended to refresh All
Management upgrade, when the user tries to log the Web EMS page (F5) after
into the unit, the message <Your completion of a software
session has expired, please login upgrade. If F5 does not help,
again> appears and the user is clear the browser cache (Press
unable to log in. Ctrl+Shift+delete).
92. 129404 Shelf Low Changing the admin state of a card When changing a card's admin FA IP-20N
management takes at least 5 seconds. state via the CLI or CLI script, 5 FA IP-20A
seconds should be allowed for Evo IP-20LH
completion of the operation.
93. 121390 HSB/HSB-SD Low If the primary radio is not defined Define both primary and FA IP-20N
revertive mode by the user, the revertive function secondary radios when FA IP-20A
may not function properly. provisioning HSB/HSB-SD
revertive mode.
94. 117851 TCC Low The Standby TCC reboots itself one None FA IP-20N
Redundancy minute after a copy-to-mate FA IP-20A
operation succeeds. Evo IP-20LH
95. 117557 TCC Low There is no alarm to indicate a Inspect the Software Versions FA IP-20N
Redundancy software version mismatch table to ensure that there is FA IP-20A
between active to standby TCC no software version mismatch. Evo IP-20LH
96. 115310 TCC Low After cold switchover, management Wait approximately one FA IP-20N
Redundancy to the active TCC may be lost for minute for management to be FA IP-20A
approximately one minute when available. Evo IP-20LH
using a Y cable for management.
97. 110714 CLI Low In CLI commands or CLI scripts, In CLI script or when pasting FA IP-20N
Configuration consecutive enabling of TDM LICs bulk of CLI commands, insert a FA IP-20A
and card configuration fails. three-minute delay between Evo IP-20LH
enabling a TDM LIC and card
configuration.
Page 83 of 129

98. 109879 Unit Info File Low The Unit Info file creation progress Use the Web EMS to create a All
is not available via the CLI. Unit Info file, or use the Web
EMS to view the event log and
verify that the Unit Info file
has been created.
99. 70513 Platform Low The system's minimum temperature None FA IP-20N
measurement is limited to -17 FA IP-20A
degrees Celsius. Evo IP-20LH
100. 65342 Configuration Low Resetting the system during If a reset takes place during All
69383 Management configuration backup file creation the backup process, repeat the
may cause the file creation to fail, process.
or the file to be unusable without
any warning, depending on the
exact timing of the reset.
101. 130809 STM1-RST Low STM1-RST PRBS counters may be Ignore the counter. FA IP-20N
PRBS counters counting, but should be ignored in FA IP-20A
live traffic. Evo IP-20LH
102. 121409 HSB-SD Low If you mute the primary radio, the Set protection lockout before FA IP-20N
revertive mode system performs switchover to the muting the radio. FA IP-20A
secondary radio and continues
trying to revert to the original
primary radio at the end of each
wait-to-restore (WTR) period.
103. 117763 Configuration Low When the combination of "File Use strings that are shorter All
Log location path in server" and "Name than 210 characters for the
of the file in server" is longer than name or location of the file on
233 characters, the "zip" suffix is the server.
missing from the file. This also
happens if the "Name of the file in
server" is longer than 210
characters.
104. 114046 CLI Scripts Low Configurations performed by a CLI Cross checking with the event All
script are not indicated as having log provides the missing
been performed by the script. information.
105. 112481 Security Log Low A user with a Viewer profile who None FA IP-20N
opens the Chassis Configuration tab FA IP-20A
is displayed in the Security Log as Evo IP-20LH
trying to reset. The user is set to FA IP-20GX
default to system with no
permission.
106. 112328 Access Control Low The parameter range for password None All
aging days appears as <0-90> in the
Web EMS. The actual range is <0,
20-90>.
Page 84 of 129

107. 112019 Configuration Low Failure of an operation to block a Ignore redundant records. All
Log user is logged several times
sequentially, all with the same time
stamp.
108. 107735 Configuration Low Configuration File upload may be Verify that the file was All
File indicated as "finished upload" while successfully uploaded to the
it is actually still uploading. server.
109. 74872 Alarms Low The system does not mask alarms Disregard these irrelevant All
and events during hardware reset. alarms and events during
hardware reset.
110. 66286 Configuration Low The file name of a configuration file Use only a .zip extension for All
71225 Management must end in ".zip". Otherwise, the configuration file names.
file will be corrupted.
111. 65506 Access Low A logged-in account is not forced to None All
Management log out even if it was blocked.
112. 56501 SNMP Low In the SNMP users should avoid All
"genEquipRadioMRMCConfigTable", setting the wrong
the user may set "fixed ACM" mode configuration.
with the maximum MRMC profile
not equal to the minimum MRMC
profile. Such a configuration will not
be blocked by the system.
113. 110157 CLI script Low No unit reset occurs (as expected) Add "platform shelf-manager All
after modifying the MRMC radio chassis reset" at the end of the
script configuration via a CLI script. CLI script.
114. 96981 Hardware Low It takes a long time for the IP-20G or None FA IP-20G
Reset IP-20GX to initiate after a hardware FA IP-20GX
reset. Wait five minutes after the
reset before attempting to ping the
unit.
115. 104467 EMS Low The device's SNMP response to get Use SNMPv2 for counter64 FA IP-20F
a next column request may take data types. FA IP-20G
long time (up to 40 seconds) when FA IP-20GX
using SNMPv1 and when the
column type is counter64.
116. 109655 Alarms Low The Alarms Configuration table Ignore these irrelevant alarms FA IP-20F
displays and enables users to in the Alarms Configuration FA IP-20G
modify some alarms that are table. FA IP-20GX
irrelevant to the IP-20G/IP-20GX
platform.
117. 110726 Activation Keys Low "Activation key usage" indicates None All
that "service mode" is always "not
used".
Page 85 of 129

118. 85944 Chassis reset Low An incorrect error notification is Ignore the error notification FA IP-20G
106524 given when executing unit reset, when performing a unit reset. FA IP-20GX
even though the unit reset is
executed correctly.
119. 90837 Installation Low Upon starting a timed software The Countdown to Installation FA IP-20G
installation, the Installation Status field displays the correct FA IP-20GX
field is not updated but keeps its information. Use this field to
previous value instead. determine if a timed
installation is in progress.
120. 109044 NTP Low The current time and date acquired If NTP is locked again after FA IP-20G
by NTP are not persistent after reset, it is updated to the FA IP-20GX
resetting the system. correct time and date again.
121. 136418 NTP Low NTP synchronization with Windows It is recommended to use an All
7 NTP takes about 60 minutes. external NTP server
application.
122. 112638 Security Log Low The permission record of an None All
unauthorized user to upload the
Security Log via telnet is not logged
in the Security Log.
123. 113434 Configuration Low Failure in uploading the Security Log None All
Log is not indicated in the Configuration
Log.
124. 118588 HSB Protection Low In case of a configuration mismatch, None FA IP-20N
an alarm is triggered on both the FA IP-20A
Active and the Standby units.
125. 120711 TCC Low The "clear-ethernet-port-counters" Clear the radio counters from FA IP-20N
Redundancy command on radio fails on the the Active TCC. FA IP-20A
Standby TCC. Evo IP-20LH
126. 141204 Web EMS Low Quick link radio configuration When setting the expected FA IP-20N
causes LOF. card type for an RMC and FA IP-20A
enabling the card, wait FA IP-20GX
approximately one minute
until the card is up before
using the wizard.
127. 141497 Payload Low Payload encryption commands are None FA IP-20N
Encryption not supported with CLI scripts. FA IP-20A
CLI Scripts FA IP-20G
FA IP-20GX
Page 86 of 129

10.3 Radio
Table 26: Notes and Limitations – Radio
1. 153395 XPIC High If any of the radio carriers that Disable XPIC before disabling FA IP-20N
belong to an XPIC group is manually any radio carrier which FA IP-20A
disabled while XPIC is enabled, XPIC belongs to the XPIC group. Evo IP-20LH
will not operate after re-enabling the FA IP-20G
radio carrier. FA IP-20GX
2. 152777 Script Limitation High Modulation of 4096 QAM may not be None FA IP-20N
for RFU-D reached in channel bandwidth of FA IP-20A
56 MHz at radio frequency of 18 GHz. FA IP-20F
3. 137703 Multi-Carrier High In a Multi-Carrier ABC group, a Disconnect or disable the FA IP-20N
ABC flapping IF cable to the RFU or faulty radio. FA IP-20A
bouncing RFU failures may cause Evo IP-20LH
continuous traffic loss. FA IP-20G
FA IP-20GX
4. 137719 RMC-E High On rare occasions, a Multi-Carrier Reboot the chassis. Evo IP-20LH
Multi-Carrier ABC group has LOF on both sides of
ABC the link after configuration changes
are applied to the group.
5. 135845 RMC-B High When using old RMC-B cards, the The issue was fixed in card FA IP-20N
alarm indication on “cable open” and versions 24-R002-0/B and FA IP-20A
“cable short” events may not be later. FA IP-20GX
functional.
6. 114704 XPIC High In XPIC, when one carrier's cable is None FA IP-20N
124630 disconnected, recovering to single- FA IP-20A
carrier mode takes 10-15 seconds. Evo IP-20LH
FA IP-20G
FA IP-20GX
7. 134463 Local and High When setting the local and remote Before changing the FA IP-20N
Remote frequency for a radio in HSB or HSB- frequency, perform FA IP-20A
Frequency SD mode, the standby radio may not protection lockout on both Evo IP-20LH
Configuration set its frequency as expected. ends of the link. Then, FA IP-20G
configure the frequency on FA IP-20GX
the local and remote radios.
8. 122548 Multi-Carrier High When configuring a Multi-Carrier Configure the MRMC script to All
ABC ABC group with XPIC while the Fixed profile-0.
MRMC script is adaptive with profile-
0, the ABC group operational status
remains "down" and Multi-Carrier
ABC does not function.
9. 139056 HSB Radio High Extraction of a card that belongs to a None FA IP-20N
Protection 1+1 HSB-SD group may cause a traffic FA IP-20A
hit.
Page 87 of 129

10. 147145 Automatic State Medium When a member of a Multi-Carrier Set a trigger delay for ASP to All
Propagation ABC group is disabled or muted, delay triggering the ASP
traffic is disrupted and causes LOF for mechanism when working
a short period of time on the Multi- with Multi-Carrier ABC.
Carrier ABC group. This triggers ASP,
which in turn can affect operation of
G.8032 and MSTP.
11. 151342 Remote TX Medium The Remote TX output level range is Display the TX output level All
output level displayed incorrectly in both the Web range directly from the
range EMS and the CLI. remote unit.
12. 148833 Multi-Carrier Medium Configuring a Multi-Carrier ABC or When configuring a Multi- FA IP-20N
ABC HSB protection group while one of Carrier ABC or HSB protection FA IP-20A
HSB Radio the members is in an initialization group, make sure all Evo IP-20LH
Protection process can cause the unit to interfaces in the group are
malfunction. The unit will then have either disabled or in
to be rebooted. operational state Up.
13. 145379 IP-20G Unit Medium 2+0 Unit Redundancy with Multi- None FA IP-20N
Redundancy Carrier ABC on an IP-20G cannot be FA IP-20A
used in a link with 2+2 Multi-Carrier FA IP-20G
ABC on an IP-20N.
14. 139014 Header De- Medium After upgrading from CeraOS 8.0 to Use the CLI to display Header FA IP-20N
Duplication CeraOS 8.2.5, Header De-Duplication De-Duplication counters. FA IP-20A
counters are inconsistent. Evo IP-20LH
FA IP-20G
FA IP-20GX
15. 137379 Payload Medium Payload encryption only becomes Reboot the unit after loading FA IP-20N
Encryption available after loading a valid a valid activation key for FA IP-20A
activation key and then rebooting payload encryption to make FA IP-20G
the unit. payload encryption usable. FA IP-20GX
16. 115233 Multi-Carrier Medium Multi-Carrier ABC has the following None FA IP-20N
ABC limitations: FA IP-20A
• Up to 8 radio channels Evo IP-20LH
• Up to 4 STM-1/OC-3 interfaces.
• Up to 8 cards.
For additional details, see TCC
Options on page 114.
Page 88 of 129

17. 139085 HSB-SD Medium To delete an HSB-SD group and re- In order to delete an HSB-SD FA IP-20N
use members as a Multi-Carrier ABC group and re-use members as FA IP-20A
group, a specific procedure must be ABC Multi Carrier, perform FA IP-20G
performed. the following steps:
1. Remove the HSB-SD
group from the Multi-
Carrier ABC group.
2. Delete the HSB-SD
group.
3. Delete the Multi-Carrier
ABC group.
4. Create the group as a
Multi-Carrier ABC group
18. 139176 Multi-Carrier Medium The maximum ACM profile must be None FA IP-20N
ABC greater than 3 in order to work with FA IP-20A
Multi-Carrier ABC for scripts 1023 Evo IP-20LH
and 1008. FA IP-20G
FA IP-20GX
19. 136753 1500HP RFU Medium After connecting an RFU 1500HP that Set the IF Combiner mode to FA IP-20N
supports IF Combining and setting IF Main. FA IP-20A
Combining mode to Combined, if the FA IP-20G
RFU 1500HP is later replaced with an FA IP-20GX
RFU-A that does not supported IF
combining, the RFU configuration will
fail.
20. 132271 Multi-Carrier Medium The same modulation scheme None All
ABC (fixed/ACM) and maximum profile
must be configured for all radio
carriers that are attached to the
same Multi-Carrier ABC group.
21. 103959 Automatic State Medium Occasionally, the Automatic State None. In the case of G.8032, All
Propagation Propagation (ASP) response time can configure a holdoff of
reach up to 500msec. 100msec.
22. 136766 Multi-Carrier Medium Software does not enforce the Before adding or removing a Evo IP-20LH
ABC requirement to set the Admin state radio from a Multi-Carrier
RMC-E of a radio to Disable before adding or ABC group, make sure to set
removing the radio to or from a its Admin state to Disable.
Multi-Carrier ABC group. Adding or
removing a radio from a Multi-Carrier
ABC group without setting its Admin
state to Disable causes a
configuration mismatch and traffic
loss.
Page 89 of 129

23. 121185 RMC-E MRMC Medium Although RMC-E MRMC scripts Do not use the 2048 QAM Evo IP-20LH
cannot be configured to 2048 QAM, configuration for RMC-E.
the MRMC table in the Web EMS
shows a maximum modulation
profile of 2048 QAM.
24. 128660 Multi-Carrier Medium When a Multi-Carrier ABC group is Reset the unit on both sides All
ABC configured from an SNMP interface of the link.
with an incorrect order of members,
the ABC member mismatch alarm
does not clear even after
reconfiguring the group.
25. 132270 Multi-Carrier Medium The MRMC scripts for radio carriers None All
ABC that are attached to a Multi-Carrier
ABC group must be identical.
26. 118296 MSTP Medium In the case of an Ethernet link When working in CSF mode: FA IP-20N
Automatic State connecting an IP-20C to an IP-20N, the services of the payload FA IP-20A
Propagation IP-20A, IP-20LH, IP-20G, or IP-20GX: traffic should use G.8032 FA IP-20G
If ASP is activated on the IP-20C in instances and the in-band FA IP-20GX
default mode (CSF enabled), if a management service should
radio failure (LOG) takes place on the use an MSTP instance.
IP-20C, the IP-20N, IP-20A, IP-20LH,
IP-20G, or IP-20GX MSTP instance
will not recover traffic.
27. 128424 ACM Adaptive Medium The ACM maximum profile for an If Profile 0 is required, ACM FA IP-20F
Power ACM configuration with adaptive mode should be set to Fixed. FA IP-20N
power enabled must be greater than FA IP-20A
Profile 0. FA IP-20G
FA IP-20GX
28. 123466 HSB Protection Medium The hitless diversity mechanism is None FA IP-20N
Space Diversity optimized to cope with channel FA IP-20A
fading or multi-path (notch). FA IP-20G
Disconnecting an IF cable is a FA IP-20GX
"hardware failure" and is handled by
the HSB mechanism (within 50msec).
29. 113919 Radio HSB Medium Traffic disruption period due to HSB When network has tree FA IP-20N
protection with protection switch may exceed topology it is recommended FA IP-20A
MSTP 50msec when MSTP is enabled. to disabled MSTP on FA IP-20G
protected radio ports. FA IP-20GX
30. 112301 RMC-A Medium RMC-A in a link with IP-10 may raise None FA IP-20N
an occasional "remote FA IP-20A
communication failure" false alarm,
which is cleared after several
seconds.
Page 90 of 129

31. 107826 Diversity Medium In case no signal is received by radios None FA IP-20N
configured in a diversity FA IP-20A
configuration, a different RX level is
shown for each radio.
32. 102584 Multi-Carrier Medium Attaching an HSB SD protection Reset the state of the HSB SD FA IP-20N
ABC group to a Multi-Radio ABC group protection group member to FA IP-20A
HSB Protection when one of the protection group Up and re-attach the
members is down causes the ABC protection group to the Multi-
channel operation state to be Radio ABC group.
"Down".
33. 69541 Radio Loopback Medium Radio loopback timeout None All
configuration is volatile (is not saved
to disk and does not survive
hardware reset of the system).
34. 65007 Radio local- Medium A remote IP-10G unit's "Floating IP", Set the IP-10G's floating IP FA IP-20N
78698 remote ATPC admin, and frequencies cannot locally. Configure ATPC and FA IP-20A
79084 interoperability be set via the local-remote channel frequencies through in-band
79235 with IP-10G (neither CLI nor Web EMS nor management.
SNMP).
35. 64998 Radio local- Medium A remote IP-10G unit's "management Set the IP-10G management FA IP-20N
remote VLAN" cannot be set via the local- VLAN locally. FA IP-20A
interoperability remote channel (neither CLI nor Web
with IP-10G EMS nor SNMP).
36. 136512 Remote Medium In IP-20S/IP-20G links, changing To set the Tx and Rx FA IP-20G
136842 Frequency frequency using the "set remote frequencies of a remote unit
Configuration in unit" checkbox functionality is in an IP-20S/IP-20G link, set
IP-20S/IP-20G limited. Only one frequency change one frequency and click
Link with remote init can be performed Apply, then set the other
per action. frequency and click Apply. Do
not set the frequencies in a
single action.
37. 124087 Radio PMs Medium A threshold for radio capacity and for None All
radio throughput PMs cannot be set.
38. 127771 Multi-Carrier Medium A Multi-Carrier ABC group can be Other configurations, such as FA IP-20N
ABC deleted without deleting other ASP, can be deleted even FA IP-20A
configurations that exist on the after the Multi-Carrier ABC Evo IP-20LH
Multi-Carrier ABC interfaces, such as group has been deleted. FA IP-20G
ASP.
39. 142924 Multi-Carrier Medium Switching members between Multi- Avoid switching members FA IP-20N
ABC Carrier ABC groups on a single unit between Multi-Carrier ABC FA IP-20A
causes traffic loss. groups.
40. 70615 Radio Local- Medium Remote unit TX frequency cannot be The remote unit’s TX All
Remote set via SNMP. frequency must be configured
via the Web EMS or the CLI.
Page 91 of 129

41. 153781 XPIC Low Performing RF loopback on the Disable XPIC before FA IP-20N
second RFU-D radio carrier with XPIC performing RF loopback. FA IP-20A
enabled is not supported FA IP-20F
42. 154759 XPIC Low Modifying the frequency of a radio Disable the XPIC group before FA IP-20N
which belongs to an XPIC group is not modifying the frequency of a FA IP-20A
supported. radio that belongs to the FA IP-20F
group.
43. 152350 RFU software Low When upgrading the software for Reset the RMC or chassis. FA IP-20N
upgrade RFU-C, RFU-A, or RFU-HP, the RFU FA IP-20A
part number may not appear in the FA IP-20G
Web EMS or CLI at the end of the FA IP-20GX
process.
44. 148311 RMC-A Low RMC-A will not work after loading an Manually change the Header FA IP-20N
Header De- old configuration file (generated in De-Duplication setting from FA IP-20A
Duplication 7.7.5) because of Header De- "disabled" to "legacy".
Duplication.
45. 140522 MRMC Scripts Low Changing the MRMC script during Do not change the MRMC All
150252 radio initialization causes a script script during radio
load failure. initialization.
46. 139221 LDPC Low Incorrect LDPC “decoder stress” Web None Evo IP-20LH
EMS reporting with RMC-E (this
parameter valid for root user).
47. 125316 Multi-Carrier Low The CLI help wrongly suggests that Multiple Multi-Carrier ABC All
ABC up to four Multi-Carrier ABC groups groups can only be configured
can be created. with certain hardware
configurations. See Feature
Release Notes on page 34.
48. 115654 Multi-Carrier Low When configuring the Multi-Carrier None FA IP-20N
ABC ABC group: the total aggregated FA IP-20A
radio capacity of all the carriers in Evo IP-20LH
ABC group must not exceed 1.4 FA IP-20GX
Gbps. This limitation does not apply
for 2.5 Gbps mode used in a TCC-B2-
XG-MC or with 2+0 RFU-D or RFU-D-
HP.
Note: The maximum Ethernet
capacity in a single Multi-Carrier ABC
group cannot exceed 1 Gbps, except
when operating with a TCC-B2-XG-
MC in 2.5 Gbps mode.
49. 139274 Multi-Carrier Low Adding a member to a Multi-Carrier When adding members to a FA IP-20N
ABC ABC group fails if the higher Multi-Carrier ABC group, the FA IP-20A
numbered slots are added before the lower numbered slots must Evo IP-20LH
lower-numbered slots. be added first. FA IP-20G
Page 92 of 129

50. 109560 HSB radio Low The system allows configuration of Avoid configuring XPIC and FA IP-20N
protection XPIC and HSB groups on the same HSB for the same pair of radio FA IP-20A
XPIC two radio interfaces, and no alarm is interfaces. FA IP-20G
raised. FA IP-20GX
51. 139712 Payload Low A Master Key is not accepted using A Master Key set using REST FA IP-20N
Encryption REST. may not include the following FA IP-20A
chars. \" Double quote \\ FA IP-20G
Backslash character. FA IP-20GX
52. 141769 Multi-Carrier Low If a Multi-Carrier ABC group or an 1 Reset the unit. All
140389 ABC XPIC group has an "LOF" alarm, the 2 Delete the Multi-Carrier
XPIC alarm is not cleared even after the ABC or XPIC group and
group is deleted. only then, set its
members to
Admin=Down.
53. 141348 Payload Low The Payload Encryption Master Key None FA IP-20N
Encryption cannot be read by SNMP. FA IP-20A
SNMP FA IP-20G
FA IP-20GX
54. 136074 ATPC Override Low Remote ATPC Override is not Do not configure ATPC All
supported even though the user Override.
interface includes it as an option.
55. 89820 RMC-B TNC Low An RMC-B card may be reset if the None FA IP-20N
Connector TNC connector is in shortcut. FA IP-20A
Shortcut FA IP-20GX
56. 130378 XPIC Low To disable an XPIC pair, the following Perform the action according All
steps must be performed in the to the procedure.
following order:
1. Disable the XPIC group.
2. Delete the XPIC group.
3. Change the MRMC scripts from
XPIC scripts to non-XPIC scripts.
57. 123096 XPIC Low TX and RX frequencies must be Configure RX & TX All
configured to be identical in both frequencies to be identical
XPIC carriers. Any discrepancy will between the carriers when
cause XPIC to malfunction, without XPIC is configured.
alarms and without automatic
recovery.
58. 113675 RMC-B in Slot 12 Low When trying to delete a predefined Configure a new expected FA IP-20N
RMC-B on Slot 12, the operation may card-type on Slot 12 and then FA IP-20A
fail. delete it.
Note: It is recommended to
avoid placing RMC-B cards in
Slots 2 & 12
Page 93 of 129

59. 99696 Automatic State Low A protection switch may cause ASP to None FA IP-20N
Propagation be triggered. FA IP-20A
FA IP-20G
FA IP-20GX
60. 66158 Radio Local- Low The parameter statuses of the local- If the local-remote All
Remote remote (which can be displayed via communication is down,
the CLI or the Web EMS) are relate to the local remote
incorrect when local-remote parameters as invalid.
communication is down.
61. 110488 Radio Local- Low The remote TX level range displays - Ignore the displayed remote All
Remote 50..34 and is never updated. TX power level range.
62. 103682 1500HP RFU Low When working with 1500HP RFU in a Ignore this incorrect FA IP-20N
HSB Protection 1+1 protected radio configuration, indication. The actual FA IP-20A
the radio TX mute indication on the behavior of the standby radio FA IP-20G
standby radio is incorrectly is TX mute enabled. FA IP-20GX
presented as 'Disabled'.
63. 69091 Radio Protection Low In 1500HP RFUs, TX frequency is not Configure TX frequency FA IP-20N
copied to mate after issuing a "copy manually in the active and FA IP-20A
to mate" command. standby radios. FA IP-20G
FA IP-20GX
64. 105641 Local-Remote Low Local to remote communication None FA IP-20F

channel: The remote radio’s most FA IP-20G
severe alarm indication (from the FA IP-20GX
Local-remote channel) indicates the
most severe alarm on the remote
unit as a whole rather than the most
severe alarm on the remote radio
interface.
65. 98175 Radio Low On the second radio carrier: MSE Use the first radio interface FA IP-20G
performance degradation takes place when using a when an IF cable longer than
long IF cable to connect the IDU and 200m is required.
the RFU. Using a 300m cable, MSE is
degraded by 1.3dB to -39dB. There is
no MSE degradation when using
cables that are 200m or shorter.
66. 107411 RFU-C Low MSE degradation can occur when Use ACM adaptive mode FA IP-20G
using an RFU-C at maximum TX when working with an RFU C FA IP-20GX
power. at maximum TX power.
67. 124506 HSB protection Low When using a 1+1 HSB protected None FA IP-20G
radio interface, several protection FA IP-20GX
switches may occur after a cold
system reset.
Page 94 of 129

68. 108484 1500HP RFU Low The "automatic delay calibration" The "automatic delay FA IP-20N
function does not return the calibration" function returns FA IP-20A
measured delay value. the "pass" status if it FA IP-20G
completes the calibration FA IP-20GX
successfully. Any other status
implies that the delay
calibration has not been
completed successfully.
69. 136919 Multi-Carrier Low A Multi-Carrier ABC group that Do not configure a Multi- FA IP-20G
ABC consists only of radio 2 is not Carrier ABC group that only FA IP-20GX
supported, but is not blocked by the contains radio 2.
software.
70. 138910 CLI Scripts Low When running a CLI script during a After running the script, the FA IP-20F
MRMC configuration restore process, and user must perform a reset: FA IP-20N
Configuration the script includes commands to • For chassis-based products FA IP-20A
configure an MRMC script, the or when configuring an FA IP-20G
MRMC configuration is not expansion slot of an IP- FA IP-20GX
executed.” 20GX, the user should
perform a slot reset.
• For IP-20G or when
configuring a fixed radio
interface on an IP-20GX,
the user should perform a
unit reset.
71. 142125 AES Low The alarm “Key Exchange Protocol in Set the Admin state of the FA IP-20N
Alarms progress, Traffic has been blocked” is radio to Down, then back to FA IP-20A
not cleared. Up. FA IP-20G
FA IP-20GX
72. 142199 Multi-Carrier Low When detaching a member from a To prevent loss of in-band FA IP-20N
ABC Multi-Carrier ABC group on one side management to the remote FA IP-20A
of the link, there is a full traffic loss unit, detach the member
for the group until the matching from the group on the remote
member on the other side of the link side of the link first, then
is also removed. detach the member from the
group on the local side of the
link.
73. 142411 Clearing Header Low If the user clears Header De- None FA IP-20N
De-Duplication Duplication counters for Multi- FA IP-20A
Counters Carrier ABC Group 1, the counters for Evo IP-20LH
Group 2 will also be cleared. If the
user clears Header De-Duplication
counters for Multi-Carrier ABC Group
3, the counters for Group 4 will also
be cleared.
Page 95 of 129

74. 142423 Multi-Carrier Low The CLI does not provide an Use the Web EMS to create FA IP-20F
ABC indication of Multi-Carrier ABC Multi-Carrier ABC groups. FA IP-20N
mismatch. FA IP-20A
FA IP-20G
FA IP-20GX
75. 142779 1+1 HSB-SD Low A short traffic loss of 6-20 ms occurs None FA IP-20N
if the standby radio is set to FA IP-20A
Admin=Down then Admin=Up in the FA IP-20G
Interface Manager.
10.4 Synchronization
Table 27: Notes and Limitations – Synchronization
1. 115859 STM-1/OC-3 High When using STM-1/OC-3 as Change the ‘Outgoing SDH FA IP-20N
Sync source synchronization interface source, the signal clock source’ to ‘rx-sdh’ FA IP-20A
user much configure the outgoing SDH for all STM-1 interfaces used as Evo IP-20LH
signal clock source to RX-SDH. synchronization sources. FA IP-20GX
2. 149877 1588 High 1588-TC will not work when None FA IP-20N
Transparent configuring Multi-Carrier ABC to 2.5G FA IP-20A
Clock mode. Evo IP-20LH
3. 150183 1588 High 1588-TC will get stuck at init when the Make sure the fixed radio FA IP-20G
Transparent fixed radio interfaces are disabled. interfaces are enabled when FA IP-20GX
Clock using 1588-TC.
4. 149148 1588 Medium 1588-TC timestamping is more Users should ensure that the FA IP-20N
Transparent accurate when the PTP service passes PTP service uses the same type FA IP-20A
Clock through the same type of physical of physical connection (SFP or Evo IP-20LH
media on both sides of the radio link. RJ-45) on both sides of the FA IP-20G
radio link.
5. 149300 SyncE Medium SyncE with Electrical SFPs is not Use supported electrical RJ-45 All
supported. interfaces or optical SFP
interfaces for SyncE
configurations.
6. 134638 1588 Medium When using IEEE1588v2 Transparent 1588 packets should be FA IP-20N
Transparent Clock, Frame Cut-Through cannot be mapped to a separate service FA IP-20A
Clock used for IEEE1588 packets. with a CoS that is not assigned FA IP-20G
Frame Cut- the highest QoS priority
Through (Priority 4).
Note: In any case, there is
no purpose to using Frame
Cut-Through for 1588 packets
to reduce PDV since this is
exactly what 1588
Transparent Clock is designed
to cope with.
Page 96 of 129

7. 120536 Sync Medium T3 cannot be used as a Select a different sync source FA IP-20N
107025 configuration synchronization source in ANSI mode. when using ANSI mode. FA IP-20A
Evo IP-20LH
8. 130862 Sync Pipe Medium Synchronization Pipe Regenerator Use clock unit mode when FA IP-20N
Regenerator mode is not supported on radio working with HSB protected FA IP-20A
HSB Protection protection groups. radio.
9. 135133 SyncE Medium A Sync source configured on the T3 None FA IP-20N

port of a TCC in Slot 11 is presented as FA IP-20A
being configured on the TCC in Slot 1.
10. 97837 Sync over Medium Changing the direction of This is due to the electrical GE All
copper GE synchronization distribution over a standard. For better results,
copper GE link causes traffic use the optical GE port for this
disruption of over one second. application.
11. 98271 Clock Medium For clock distribution between IP-20 None FA IP-20N
distribution and IP-10 units: only TDM trail ID 1 FA IP-20A
between IP-20 (channel 1) can be used.
and IP-10
12. 90440 ELIC port #1 Medium LIC-X-E4-Elec and LIC-X-E4-Opt Use either: FA IP-20N
94381 sync source Electrical Port 1 cannot be set as a • Optical GE ports on an FA IP-20A
configuration sync source. Other Electrical ports on optical LIC (X-LIC), or Evo IP-20LH
a LIC-X-E4-Elec (2-4) can be set as sync
• Electrical GE ports on an
sources. Optical Port 1 can be set as a
electrical E-LIC, or
sync source.
• Electrical GE ports on the
TCC as sync sources.
13. 131596 Sync Source Medium If a sync source is deleted while the Make sure that a valid FA IP-20N
second remaining sync source receives alternative sync source exists FA IP-20A
DNU, the clock unit enters “free in the system before removing Evo IP-20LH
running” mode. the sync source.
14. 97928 T4 Sync Medium ANSI mode is not supported on the T4 None FA IP-20N
Interface sync interface. FA IP-20A
Evo IP-20LH
FA IP-20G
15. 97479 T3 Sync Medium When T3 is selected as a sync source, Consider removing T3 as a sync FA IP-20N
Interface it continues to feed the system clock source during maintenance FA IP-20A
even when the Admin state of T3 is set operations on the T3 interface Evo IP-20LH
to Down. or configure it to be a lower
priority source.
16. 69327 Sync Source Medium Sync operation is not supported on Configure each sync interface All
154249 Outgoing Clock interfaces which are configured as and outgoing clock interface
Auto-type. Media-Type explicitly to be RJ-
45 or SFP.
Page 97 of 129

17. 89883 Sync Medium In a ring configuration using logical Use only one of the group's All
configuration interfaces or groups (HSB, LAG) in the physical links to transport
ring links, synchronization cannot be synchronization.
transported through the group.
18. 117026 SSM messages Low There is no CLI command for setting Use the Web EMS to set SSM All
an SSM value for radio interfaces. values for radio interfaces.
19. 69329 Outgoing Clock Low Configuring the outgoing clock as None All
"system clock/local clock" configures
all GE ports.
20. 71677 Extra event Low When sync quality changes, the None All
when sync following extra event appears in the
quality event log: 'T0-quality change-event'.
changes
21. 89991 Interfaces on Low The media type of GE interfaces on an Configure media type as RJ45 FA IP-20N
LIC-X-E4-Elec LIC-X-E4-Elec should be set to RJ45 also for non-combo interfaces FA IP-20A
as sync source before selecting the interface as a sync on E-LICs. Evo IP-20LH
source.
22. 130873 Sync options Low Pipe regenerator synchronization Choose one or the other FA IP-20N
cannot coexist with the Sync Unit synchronization method for FA IP-20A
synchronization on the same unit. the unit. Evo IP-20LH
23. 108882 Sync Low The Web EMS does not allow 1. In the Web EMS, always All
configuration configuration of a sync source with a configure sync sources in the
higher priority than existing sync order of higher to lower
sources. priority.
2. Use the CLI to configure sync
sources.
24. 86759 TDM interface Low Attempting to configure the TDM Use another synchronization All
as sync source interface as a Synchronization source source.
results in an error.
25. 103577 Sync Low The Synchronization outgoing clock Ignore this irrelevant FA IP-20F
option is presented to the user from configuration option. FA IP-20G
the Web EMS and the CLI. This FA IP-20GX
configuration is not relevant for IP-20F
and IP-20G and should be ignored. No
matter what the user configures, the
outgoing clock will always be 'System
Clock'.
26. 107071 Sync Low SyncE on the electrical GE port is not Use port speed of 100 or 1000 FA IP-20G
supported with 10Mbps Half Duplex full duplex for SyncE ports. FA IP-20GX
port speed.
27. 120392 Sync Low Synchronization clock does not Enable one of the radio FA IP-20G
function if both radio interfaces are interfaces. FA IP-20GX
disabled by user configuration.
Page 98 of 129

10.5 TDM – Native

Table 28: Notes and Limitations – TDM – Native
1. 152520 Trace ID Medium When configuring the J0 Trace ID Configure the J0 Trace ID with FA IP-20N
with less than 15 characters while it exactly 15 characters when it is FA IP-20A
is disabled, the actual J0 that is sent disabled or configure it only Evo IP-20LH
after enabling it is padded with when it is enabled. FA IP-20GX
space characters up to the length of
15 characters. A CLI configuration
enables the user can see this
padding to 15 characters while a
Web EMS configuration does not.
2. 151603 E1/DS1 Medium System performance may be The members of an E1/DS1 card FA IP-20N
Protection reduced when using LIC-T16 cards protection group should have FA IP-20A
Group with different part numbers in the the same part numbers. Evo IP-20LH
same protection group.
3. 98766 Path Protection Medium Disabling a 1+1 path protected trail To disable a 1+1 path protected FA IP-20N
fails. trail, the user should first FA IP-20A
disable the STM-1/OC-3 card. Evo IP-20LH
4. 121413 Path Protection Medium Up to 56 1+1 protected trails are Use 1:1 protection, which does All
supported per TDM LIC (Line not have this limitation.
Interface Card).
5. 98325 STM-1/OC-3 Medium Path Protection switch time can None FA IP-20N
Path Protection exceed 50msec when consecutive FA IP-20A
failures occur within 10 seconds. Evo IP-20LH
FA IP-20GX
6. 132229 TDM services in Medium When IF-loopback or RF-loopback None All

loopback are "on", the TDM service
Operational State is Down.
7. 127154 STM-1/OC-3 Medium STM-1/OC-3 card admin is not Enable STM-1/OC-3 card admin FA IP-20N
Admin State raised automatically in Interface via the Interface Manager (IFM). FA IP-20A
Manager (IFM) when admin is Evo IP-20LH
enabled. FA IP-20GX
8. 121029 TDM Medium If the incoming TDM signal strays Make sure incoming TDM All
performance off the central frequency or stability signals comply with the
as defined in ITU-T G.803 there may appropriate standards.
be errors in the traffic.
9. 100227 STM-1/OC-3 Medium Lockout command is not supported. None FA IP-20N

Card Protection FA IP-20A
Evo IP-20LH
FA IP-20GX
Page 99 of 129

10. 120390 TDM Medium Configuring a protected service on Before configuring a protected FA IP-20N
configuration an STM-1/OC-3 interface from the service: FA IP-20A
wizard wizard may fail in the following • Make sure that both cards Evo IP-20LH
cases: have the same configuration. FA IP-20GX
• Due to configuration mismatch • Make sure both interfaces are
between the two STM-1/OC-3 set to Admin - Enabled.
LICs.
• If one of the STM-1/OC-3
interfaces is disabled by user
configuration.
11. 151540 LIC-T155 in Low When installing a LIC-T155 card that Make sure the STM-1 cable is FA IP-20N
Protection is part of the HSB protection group not connected to the card when FA IP-20A
Group with an STM-1 cable is connected to the card is being installed.
the card, a temporary traffic hit Connect the cable after the card
occurs. has been installed and is Up.
12. 109595 Path Protection Low Only the Manual Switch command Use Manual Switch during All
is supported. maintenance operations.
Force Switch and Lockout
commands are not supported but
not blocked.
13. 100248 STM-1/OC-3 Low LOS and AIS can occur for 10 None FA IP-20N
Card Protection seconds if consecutive protection FA IP-20A
switches occur within the same 5 Evo IP-20LH
seconds. FA IP-20GX
14. 75135 J0 mismatch Low J0 mismatch causes AIS injection, as Disable the J0 mismatch alarm FA IP-20N
94107 specified in SDH/SONET standards. or fix the expected/received J0 FA IP-20A
string. Evo IP-20LH
FA IP-20GX
15. 90651 Web EMS Low In the TDM interfaces column, None FA IP-20N
98780 "Absolute Clock reference" is not FA IP-20A
relevant for STM-1/OC-3 cards. Evo IP-20LH
FA IP-20GX
16. 89522 TDM standard Low TDM standard (SONET/SDH) is not The standard should be set All
saved in the configuration file and before starting to configure
does not revert to default if the unit TDM traffic for each unit.
is set to default settings.
17. 117894 Revertive Path Low Revertive switch does not occur if Perform manual switch again. All
Protection manual switch was performed.
18. 105502 Native TDM Low TDM services table refresh can be None All
Services slow.
Page 100 of 129

10.6 TDM – Pseudowire

Table 29: Notes and Limitations – TDM – Pseudowire
1. 87041 Protected Medium Configuration of a second Configure a unique name for All
Pseudowire Maintenance Domain (MD) with the each MD.
Services same name as the first fails.
Configuration of MDs may fail if the
MD's name is not unique.
2. 90722 SOAM Medium SOAM occasionally fails to update Reset the local TDM card. All
the remote MAC address when the
address changes during service
operation.
3. 120390 TDM configuration Medium Configuring a protected service on an Before configuring a FA IP-20N
wizard STM-1/OC-3 interface from the protected service: FA IP-20A
wizard may fail in the following 1. Make sure that both Evo IP-20LH
cases: cards have the same
1. Due to configuration mismatch configuration.
between the two STM-1/OC-3 2. Make sure both
LICs. interfaces are set to
2. If one of the STM-1/OC-3 Admin - Enabled.
interfaces is disabled by user
configuration.
4. 117057 Pseudowire Low The system allows configuration of Refrain from using frame size All
Profiles profiles with frame size 1 even 1.
though the minimum frame size is 2
E1/T1 frames (2x32/24bytes).
5. 102236 Pseudowire Low For ANSI systems, when creating a For ANSI systems, when All
Service new PWE profile the default payload creating a pseudowire profile,
Configuration size is 16 frames. It is recommended change the payload size
to change this manually to 8 frames. manually to 8.
6. 123572 TDM and Low TDM and pseudowire CLI commands Ignore these TDM commands FA IP-20G
pseudowire CLI are available even in units without in units without TDM FA IP-20GX
commands TDM interfaces. These commands interfaces.
are not functional.
7. 87063 SOAM Low Remote MAC addresses discovered Read the remote MAC All
by SOAM are not shown in the Web addresses from the CLI using
EMS. the command 'pwe3 tunnel
status show'.
Page 101 of 129

11. Open Bugs
11.1 Ethernet
Table 30: Open Bugs – Ethernet
1. 155272 LACP High LACP transparent mode may not work when None All
SyncE a Sync Source is configured on an
intermediary unit.
2. 154514 MRU Medium When using asymmetrical MRU values on the Use Symmetrical MRU All
two sides of a radio link, traffic with higher values on both sides of a
CoS may be adversely affected when traffic is radio link.
congested.
3. 147246 CFM-SOAM Medium Y.1731 configuration cannot be performed Perform Y.1731 All
by means of SNMP or REST. configuration using the
Web EMS or CLI.
11.2 Platform
Table 31: Open Bugs – Platform
1. 154694 CLI Scripts Medium CLI script execution, within a configuration Avoid using CLI scripts as FA IP-20N
restore operation, may fail. part of a restore operation. FA IP-20A
Evo IP-20LH
2. 152950 SW Upgrade Medium When upgrading the software in a unit None FA IP-20N
TCC with TCC Redundancy in HSO mode, the FA IP-20A
Redundancy traffic disruption may be larger than Evo IP-20LH
50msec.
3. 140168 X.509 Medium The Certificate Download status does not Before installing the All
Certificate indicate when the download process has certificate, verify that the
been completed. download has been
completed
4. 151267 SSH Medium When opening more than 10 SSH sessions, Close SSH sessions. All
the system response time may degrade on
the SSH session and Web EMS interface.
5. 149575 Chassis Low An operation to set or clear the expected Make sure the size of the FA IP-20N
Configuration card type in the Chassis Configuration page web browser window is FA IP-20A
of the Web EMS malfunctions if the size of maximized, or scroll to the Evo IP-20LH
the web browser window has been top of the window, when
reduced or a scroll bar is present. changing the expected card
type.
Page 102 of 129

11.3 Radio
Table 32: Open Bugs – Radio
1. 141209 HSB-SD High The standby card initialization process None FA IP-20N
causes a traffic disruption of 10 seconds. FA IP-20A
2. 153221 Radio Medium Radio Utilization PM values are not valid None FA IP-20F
Utilization for RFU-D, RFU-D-HP, and RFU-S. FA IP-20N
PMs FA IP-20A
3. 149989 Radio Medium The user can configure a frequency from Users should take care to FA IP-20G
Frequency both the Tx and Rx ranges of the RFU to configure the correct
Configuration both Tx and Rx frequency. frequency.
4. 142846 XPIC Medium Radio LOF is raised when an XPIC group When an XPIC group is All
is created or deleted, even if the radio deleted, the user must reset
condition is normal. the RMC, the TCC, or the
chassis.
5. 149640 ATPC Low The ATPC Override State field in the The ATPC override state is FA IP-20N
ATPC – Edit page of the Web EMS displayed correctly in the FA IP-20A
sometimes displays an incorrect value. ATPC Override State column FA IP-20F
This has no impact on system behavior. of the main Radio ATPC page. FA IP-20G
FA IP-20GX
6. 142399 MRMC Script Low MRMC 1023 (3.5 MHz) is not supported Either: FA IP-20N
1023 when all of the following conditions are • Do not use the script with FA IP-20G
met: (i) ACM Adaptive mode is enabled, AES-256 payload
(ii) the carrier using the script belongs to encryption, OR
a Multi-Carrier ABC group, and (iii) AES-
• Do not use this script with
256 payload encryption is enabled.
Multi-Carrier ABC, but
rather, in a single-channel
carrier, OR
• Use this script with a fixed
ACM profile greater than 0.
7. 142418 MRMC Script Low MRMC 1023 (3.5 MHz) is not supported Either: FA IP-20GX
1023 when AES-256 payload encryption is • Do not use the script with
enabled and the ACM profile is 0 in AES-256 payload
either ACM Fixed or ACM Adaptive encryption, OR
mode.
• Use this script with a fixed
ACM profile greater than 0.
Page 103 of 129

11.4 Synchronization
Table 33: Open Bugs – Synchronization
1. 149803 1588 Medium 1588-TC not supported with in fixed ACM Configure the MRMC script in FA IP-20N
Transparent mode. ACM mode using identical FA IP-20A
Clock minimum and maximum FA IP-20G
profiles. FA IP-20GX
2. 151637 1588 Medium Enabling 1588-TC on a Multi-Carrier ABC If using 1588-TC on a Multi- FA IP-20N
Transparent interface with scripts lower than 14 MHz Carrier ABC interface, make FA IP-20A
Clock and profiles lower than 3 may cause the sure the interface is
Multi-Carrier ABC interface to go down. configured with a script that
is 14 MHz or higher and a
profile of 3 or higher.
11.5 TDM – Native

Table 34: Open Bugs – TDM-Native
1. 154990 STM-1-RST Medium In Multi-Carrier ABC N+0 configurations None FA IP-20N

RMC-B with RMC-B and STM-1 RST traffic, when FA IP-20A
one side of a radio carrier experiences FA IP-20LH
profile degradation that results in a Loss
of Frame (LOF) condition, the STM-1 RST
traffic may experience a traffic hit.
2. 154565 E1/DS1 Medium The E1/DS1 traffic mask is distorted when Do not enable a TDM service All
Traffic Mask a TDM service is configured and enabled, that will not be used.
but left inactive or disconnected.
11.6 TDM – Pseudowire

No open bugs for TDM – Pseudowire.
Page 104 of 129

12. Synonyms and Acronyms

Table 35: Synonyms and Acronyms
Acronym Full Name
ACM Adaptive Coding and Modulation

AIS Alarm Indication Signal
ANSI American National Standards Institute
ASP Automatic State Propagation
ATPC Automatic TX Power Control
BBS Baseband Switching
BER Bit Error Ratio
CA Controlled Availability Release
CCDP Co-channel dual polarization
CE Carrier Ethernet
CFM Connectivity Fault Management
CLI Command Line Interface
CoS Class of Service
CSF Client Signal Failure
DSCP Differentiated Service Code Point
EMS Element Management System
ERPI ERP Instances
ETSI European Telecommunications Standards Institute
Evo Evolution
FA FibeAir
FCC Federal Communications Commission
FE Fast Ethernet
FTP (SFTP) File Transfer Protocol (Secured File Transfer Protocol)
GA General Availability Release
GbE Gigabit Ethernet
GMT Greenwich Mean Time
HSB Hot Standby
HSO Hot Switchover
HTTP (HTTPS) Hypertext Transfer Protocol (Secured HTTP)
IDU Indoor Unit
Page 105 of 129

Acronym Full Name
IEEE Institute of Electrical and Electronics Engineers

LACP Link Aggregation Control Protocol
LAN Local Area Network
LH Long Haul
LIC Line Interface Card
LLDP Link Layer Discovery Protocol
LLF Link Loss Forwarding
LOC Loss of Carrier
LOF Loss of Frame
LOS Loss of Signal
Mbps Million Bits Per Second
MC-ABC Multi Carrier Adaptive Bandwidth Control
MEF Metro Ethernet Forum
Mpps Million Packets Per Second
MPLS Multiprotocol Label Switching
MRU Maximum Receive Unit
MSE Minimum Square Errors
MSP Multiplex Section Protection
MSTP Multiple Spanning Tree Protocol
NMS Network Management System
NTP Network Time Protocol
OAM Operation Administration & Maintenance (Protocols)
OC Optical Carrier
PM Performance Monitoring
PN Part Number
PTP Precision Timing-Protocol
PW Pseudowire
QAM Quadrature Amplitude Modulation
QoS Quality of Service
RFU Radio Frequency Unit
RMC Radio Modem Card
RMON Ethernet Statistics
RPL Ring Protection Link
Page 106 of 129

Acronym Full Name
SD Space Diversity
SFTP Secure FTP
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
STM Synchronous Transport Module
STP Spanning Tree Protocol
SSH Secured Shell (Protocol)
SSM Synchronization Status Messages
SyncE Synchronous Ethernet
TC Transparent Clock
TCC Traffic Control Card
TDM Time-Division Multiplexing
VC Virtual Container
VLAN Virtual Local Area Network
Web EMS Web-Based Element Management System
WFQ Weighted Fair Queue
XCVR Transceiver
XPIC Cross Polarization Interference Cancellation
WTR Wait to Restore
Page 107 of 129

13. Annex A - System Configurations
13.1 FibeAir IP-20N and IP-20A System Configurations

FibeAir IP-20N and IP-20A can be used in the configurations listed in the tables
below. There are two sets of configurations:
• RMC Configurations – Used with RMC-A or RMC-B and RFU-C, RFU-A, and
1500HP/RFU-HP.
• RIC-D Configurations – Used with RIC-D and RFU-D, RFU-D-HP, RFU-E, and
RFU-S.
Note: RMCs and RIC-Ds can be used in the same chassis, subject to certain
slot restrictions. For details, see Slot Sections and 2.5 Gbps Mode on
page 118.
13.1.1 Configurations based on RMC with RFU-C, RFU-A, and 1500HP/RFU-HP

For configurations using an RMC with RFU-C, RFU-A, and 1500HP/RFU-HP, the
following requirements should be taken into account:
• Multi-Carrier ABC configurations with RFU-C, RFU-A, and 1500HP/RFU-HP
require TCC-B-MC or TCC-B2-XG-MC, and RMC-B.
• With TCC-B-MC, one Multi-Carrier ABC group can be configured per unit with
up to 8 carriers aggregated in the group and a total radio capacity of 1 Gbps.
• With TCC-B2-XG-MC, the following is supported:
A single Multi-Carrier ABC group of up to 8+0 with capacity of up to 2.5
Gbps.
Up to four Multi-Carrier ABC groups, with capacity of up to 1 Gbps per
group.
• Multi-Carrier ABC configurations can be combined with non-Multi-Carrier ABC
configurations in the same unit. For example, a single IP-20N unit can support
a 4+0 Multi-Carrier ABC group and, in addition, an N+0 or a 1+1 HSB
protection group that is not part of the Multi-Carrier ABC group.
Note: Multi-Carrier ABC is not supported with RMC-A.
The following radio configurations are available for RMCs with RFU-C, RFU-A, and
1500HP/RFU-HP:
Table 36: FibeAir IP-20N and IP-20A Configurations with RMCs with RFU-C, RFU-A, and
1500HP/RFU-HP
Configuration Notes
N+0 IF Combining Requires RMC-B and 1500HP

N+0 LAG
2+0 Single Polarization Requires Multi-Carrier ABC or LAG
2+0 Dual Polarization (XPIC) Requires Multi-Carrier ABC
N+0 Multi-Carrier ABC (up to 8+0)
Page 108 of 129

Configuration Notes
4 X 2+0 Multi-Carrier ABC Requires RMC-B and Multi-Carrier ABC

4 X 1+1 HSB Protection with BBS Space Diversity Requires RMC-B and Multi-Carrier ABC
2 X 2+2 HSB Protection with BBS Space Diversity Requires RMC-B and Multi-Carrier ABC
2 X 4+0 Multi-Carrier ABC Requires RMC-B and Multi-Carrier ABC
1+1 HSB Protection
1+1 HSB Protection with BBS Space Diversity Requires Multi-Carrier ABC
2+2 HSB Protection with BBS Space Diversity and XPIC Requires Multi-Carrier ABC
13.1.2 Configurations based on RIC-D with RFU-D, RFU-D-HP, RFU-E, and RFU-S
In configurations using RIC-D, Multi-Carrier ABC can be implemented between the
two carriers of a MultiCore RFU-D or RFU-D-HP. This type of Multi-Carrier ABC can
be used with any type of TCC.
The following configurations are available for RIC-Ds:
Table 37: Radio Configuration Options for RIC-Ds

Configuration Supported RFUs Notes
8 X 1+0 RFU-S 6 x 1+0 with 112 MHz channels

4 X 1+0 RFU-E 3 x 1+0 with 250 MHz channels
4 X 2+0 (XPIC optional) RFU-D and RFU-D-HP 3 x 2+0 with 112 MHz channels
Page 109 of 129

13.2 Evolution IP-20LH System Configurations

Evolution IP-20LH can be used in the following configurations. All Evolution IP-
20LH system configurations require Multi-Carrier ABC.
Table 38: Evolution IP-20LH Configurations

Configuration Notes
1+0
N+0 IF Combining Requires 2Rx XCVR
2+0 Single Polarization
2+0 Dual Polarization (XPIC)
4+0 IF Combining Requires 2Rx XCVR
4+0 IF Combining and XPIC Requires 2Rx XCVR
4 X 2+0 Multi-Carrier ABC
2 X 4+0 Multi-Carrier ABC
Page 110 of 129

13.3 FibeAir IP-20F System Configurations

In CeraOS, FibeAir IP-20F can be used in the following configurations. Additional
configurations are planned for future release. For details, refer to the Technical
Description for FibeAir IP-20F, CeraOS 10.0.
Table 39: FibeAir IP-20F Configurations

Configuration Directions RFUs
1+0 1 RFU-D, RFU-D-HP, RFU-E, RFU-S

2+0 1 RFU-D, RFU-D-HP
Page 111 of 129

13.4 FibeAir IP-20G System Configurations

FibeAir IP-20G can be used in the following configurations.
Table 40: FibeAir IP-20G Configurations

Configuration Notes
1+0
1+0 IF Combining Requires 1500HP
2 x 1+0 (East-West)
2+0 Dual Polarization (XPIC) Requires Multi-Carrier ABC or LAG
1+1 HSB Protection
13.5 FibeAir IP-20GX System Configurations

FibeAir IP-20GX can be used in the following configurations.
Table 41: FibeAir IP-20GX Configurations

Configuration Notes
1+0
1+0 IF Combining Requires 1500HP
4 x 1+0 (East-West)
2+0 Dual Polarization (XPIC) Requires Multi-Carrier ABC or LAG
4+0 Requires LAG
1+1 HSB Protection Fixed (main board) radio interfaces only.
Note: Multi-Carrier ABC, 1+1 HSB, and 1+1 HSB with BBS are only supported
for the fixed (main board) radio interfaces.
Page 112 of 129

13.6 Hardware Options for Chassis-Based Systems

Chassis-based IP-20 products are available in 1RU and 2RU versions, each of which
supports a common set of cards for traffic, radio interface, and management:
• Traffic Control Card (TCC)
• Radio Modem Cards (RMCs)
• Radio Interface Cards (RICs)
• Line Cards (LICs), including:
◦ Ethernet – LIC-X-E4-Elec (4x GE), with one GE combo interface one GE
electrical (RJ-45) interface, and two dual mode electrical or cascading
interfaces
◦ Ethernet – LIC-X-E4-Opt (4x GE), with one Gb combo interface, one Gb
optical (SFP) interface, and two dual mode optical or cascading interfaces.
◦ Ethernet – LIC-X-E10 (1x10GE), with a single 10GE optical interface.
◦ TDM – LIC-T16 (16x E1/DS1)
◦ TDM – LIC-T155 (1x ch-STM-1/OC-3)
◦ TDM – LIC-STM1/OC3-RST (1 x STM-1/OC-3)
For FibeAir IP-20N and IP-20A products, the 1RU chassis supports up to five radio
cards, with redundancy options for radio and traffic, and a dual-feed power option
for power redundancy.
For Evolution IP-20LH, the 1RU chassis supports up to four carriers, with
redundancy options for radio and traffic, and a dual-feed power option for power
redundancy.
For FibeAir IP-20N and IP-20A, the 2RU chassis supports up to ten carriers, with
redundancy options for management, radio, traffic, and power.
For Evolution IP-20LH, the 2RU chassis supports up to eight carriers, with
redundancy options for management, radio, traffic, and power.
Page 113 of 129

13.6.1 TCC Options

The following table describes the TCC options for chassis-based IP-20 systems.
Note that:
• All TCC models can be used in both 1RU and 2RU chassis.
• All TCC models include a DB9 external alarms interface.
• All TCC models include a synchronization interface for T3 input and T4 output.
• All TCC models include an RJ-45 serial interface
• TCC-B2 or TCC-B2-XG-MC including 6 GE interfaces, eliminate the need for LIC-
X-E4 if the number of required optical Gb interfaces is two and the number of
required electrical Gb interfaces is four.
• For Evolution and FibeAir IP-20LH systems, only TCCs that support Multi-
Carrier ABC (TCC-B-MC and TCC-B2-XG-MC) are supported.
Table 42: TCC Options

TCC Type Ethernet Traffic Interfaces Multi-Carrier ABC Support
TCC-B 2 x Gb combo (optical or Only with RIC-D and RFU-D or RFU-D-HP

electrical) interfaces
TCC-B-MC 2 x Gb combo (optical or • 1 x up to 8+0 Multi-Carrier ABC9
electrical) interfaces • 1 Gbps per Multi-Carrier ABC group
TCC-B2 2 x Gb electrical interfaces Only with RIC-D and RFU-D or RFU-D-HP
2 x Gb optical interfaces
2 x dual mode electrical or
cascading interfaces
TCC-B2-XG-MC 2 x Gb electrical interfaces • 1 x up to 8+0 Multi-Carrier ABC9
2 x Gb optical interfaces 4 X 2+0 Multi-Carrier ABC
2 x dual mode electrical or • 4 X 1+1 HSB Protection with BBS Space Diversity
cascading interfaces • 2 X 4+0 Multi-Carrier ABC
• 1 or 2.5 Gbps (user-configurable)10
• 2 X 2+2 HSB-SD
9
With RMC-B, a Multi-Carrier ABC group can include up to eight radio and STM1/OC3-RST
members in total. With RMC-E, a Multi-Carrier ABC group can include up to eight radio
members and up to eight STM1/OC3-RST members, for a combined total of 16 members.
With RIC-D, up to four 2+0 Multi-Carrier ABC groups are supported. Each group uses a single
RIC-D connected to a MultiCore RFU (RFU-D or RFU-D-HP).
10
2.5 Gbps mode is not available for configurations that require multiple Multi-Carrier ABC
groups.
Page 114 of 129

13.6.2 RMC and RIC-D Options

The following table describes the RMC options for FibeAir IP-20N, IP-20A, IP-20GX,
and Evolution IP-20LH, and RIC-D options for FibeAir IP-20N and IP-20A.
Table 43: RMC and RIC-D Options

RMC Type Highest Channel BW Multi-Carrier RFU Support Applicability
Modulation Range ABC Support
RMC-A 256 QAM 7-56 MHz No RFU-C, RFU-HP, FibeAir IP-20N, IP-
1500HP, RFU-A 20A11, and IP-20GX
RMC-B 2048 QAM 3.5-60 MHz Yes RFU-C, RFU-HP, FibeAir IP-20N, IP-
1500HP, RFU-A 20A, IP-20GX
RMC-E 1024 QAM 25-56 MHz Yes Evolution XCVR, Evolution IP-20LH
Evolution ODU
RIC-D 4096 QAM 14-250 MHz Yes RFU-E, RFU-S, RFU-D, FibeAir iP-20N and
RFU-D-HP IP-20A
Note: RMC-E includes a 1 x STM-1-RST Clear Channel interface.
13.6.3 FibeAir IP-20N and IP-20A 1RU and 2RU Scalability
Table 44: FibeAir IP-20N and IP-20A 1RU/2RU Scalability

Interface 1RU Chassis 2RU Chassis
Type
Maximum Number Maximum Number of Maximum Number Maximum Number of
of RMCs//RICs/LICs Radio/Line Interfaces of RMCs/RICs/LICs Radio/Line Interfaces
Radio 5 x RMC or RIC 5 x RFU 10 x RMC or 8 x 10 x RFU

(RFU) RIC
Ethernet 1 x LIC-X-E4- 10 X GE/FE12 2 x LIC-X-E4- 10 x GE/FE13
(GE/FE) Elec/Opt (4x GE) or Elec/Opt (4x GE)
LIC-X-E10 (10GE) or LIC-X-E10
(10GE)
TDM – LIC 4 x any combination of LIC-T16 (16x E1/DS1), 8 x any combination of LIC-T16 (16x E1/DS1),
LIC-T155 (1x ch-STM-1/OC-3) and LIC- LIC-T155 (1x ch-STM-1/OC-3) and LIC-
STM1/OC3-RST (1 x STM1/OC-3) STM1/OC3-RST (1 x STM1/OC-3)
11
For IP-20A, RMC-A supports 30-40 MHz (FCC).
12
2 x GE interfaces on the TCC-B/TCC-B-MC or 6 x GE interfaces on the TCC-B2/TCC-B2-XG-MC
and 4 x GE interfaces on the Ethernet LIC, for a total of 6 or 10 GE interfaces per chassis.
13
When an Ethernet LIC is installed in slot 12, two GE interfaces on the TCC-B or TCC-B-MC are
disabled, leaving a total of 8 GE interfaces per chassis. When using a TCC-B2 or TCC-B2-XG-
MC, four GE interfaces on the TCC are disabled, leaving a total of 10 GE interfaces per
chassis.
Page 115 of 129

13.6.4 Evolution IP-20LH 1RU and 2RU Scalability
Table 45: Evolution IP-20LH 1RU/2RU Scalability

Interface 1RU Chassis 2RU Chassis
Type
Maximum Number Maximum Number of Radio/Line Maximum Maximum Number of
of RMCs/LICs Interfaces Number of Radio/Line Interfaces
RMCs/LICs
Radio Units 4 x RMC-E 4 x XCVR 8 x RMC-E 8 x XCVR

4 x RMC-B 4 x RFU-HP/1500HP 8 x RMC-B 8 x RFU-HP/1500HP
Ethernet 1 x LIC-X-E4- 10 X GE/FE14 2 x LIC-X-E4- 10 x GE/FE15
(GE/FE) Elec/Opt (4x GE) Elec/Opt (4x
or LIC-X-E10 GE) or LIC-X-
(10GE) E10 (10GE)
TDM – LIC 4 x any 8 x any combination of LIC-T16
combination of (16x E1/DS1), LIC-T155 (1x ch-
LIC-T16 (16x STM-1/OC-3), and LIC-
E1/DS1), LIC-T155 STM1/OC3-RST (1 x STM1/OC-
(1x ch-STM-1/OC- 3)
3), and LIC-
STM1/OC3-RST (1
x STM1/OC-3)
13.6.5 Card Types Allowed Per Slot – 1RU/2RU
Table 46: Card Types Allowed Per Slot – 1RU

Slot Number Allowed Card Type Notes
1 • TCC
2 • RMC-A, RMC-B, RIC-D Does not include LIC-STM1/OC3-RST (1 x
• Ethernet LIC STM1/OC-3)
• TDM LIC
3-6 • RMC-A, RMC-B, RMC-E, RIC-D Where Multi-Carrier ABC is used, Slot 3
• TDM LIC can be unoccupied or must be populated
with an RMC, which must be part of the
Multi-Carrier ABC group (Bug ID 127456).
14
2 x GE interfaces on the TCC-B-MC or 6 x GE interfaces on the TCC-B2-XG-MC and 4 x GE
interfaces on the Ethernet LIC, for a total of 6 or 10 GE interfaces per chassis.
15
When a second Ethernet LIC is installed, the two GE interfaces on the TCC-B-MC are
disabled, leaving a total of 8 GE interfaces per chassis. When using a TCC-B2-XG-MC, four GE
interfaces on the TCC are disabled, leaving a total of 10 GE interfaces per chassis.
Page 116 of 129

Table 47: Card Types Allowed Per Slot – 2RU

Slot Number Allowed Card Type Notes
1 • TCC
2,12 • RMC-A, RMC-B, RIC-D Does not include LIC-STM1/OC3-RST (1 x
• Ethernet LIC STM1/OC-3)
• TDM LIC
3 - 10 • RMC-A, RMC-B, RMC-E, RIC-D Where Multi-Carrier ABC is used, Slot 3 can
• TDM LIC be unoccupied or must be populated with
an RMC, which must be part of the Multi-
Carrier ABC group.
11 • TCC Only valid when TCC redundancy is enabled.
13.6.6 TCC GE Interface Limitations

When an Ethernet LIC is installed in Slot 12, the two Gb interfaces on the TCC-B or
TCC-B-MC are disabled, leaving a total of 8 Gb interfaces per chassis.
When using a TCC-B2 or TCC-B2-XG-MC, avoid placing any type of traffic cards
(Ethernet LIC, TDM LIC, and RMC) in certain slots. If you place a traffic card in one
of these slots, some interfaces on the TCC cannot be used, as described in the
following table.
Table 48: Slot Limitations When Used with TCC-B2 or TCC-B2-XG-MC

Traffic Card in Slot: TCC-B2/TCC-B2-XG-MC Interfaces Not Available for Use:
9 GbE5
10 GbE6
12 • Ethernet LIC in Slot 12: SFP1, SFP2, GbE3/CS3, GbE4/CS4
• TDM LIC or RMC in Slot 12: GbE3/CS3 only
13.6.7 Adjacent Pair Guidelines

It is recommended to place the same type of cards in adjacent pairs, as follows:
• Slots 3 and 4
• Slots 5 and 6
• Slots 7 and 8 (2RU only)
• Slots 9 and 10 (2RU only)
If you configuring 2+2 HSB with XPIC, you must configure the radio protection
group in non-adjacent channels, e.g., slots 3 and 5 or slots 4 and 6. That is because
the XPIC groups must be configured in adjacent slots. For example:
• XPIC Group #1: Slots 3 and 4
• XPIC Group #2: Slots 5 and 6
• Protection Group #1: Slots 3 and 5
• Protection Group #2: Slots 4 and 6
Page 117 of 129

13.6.8 Slot Sections and 2.5 Gbps Mode

The slots in the chassis are divided into sections, as described below. Each section
can be configured to 1 Gbps mode (default) or 2.5 Gbps mode, and a card cannot
exceed the capacity of the section it is in.
Table 49: Card Type Usage Per Section Capacity

Card Type 2.5 Gbps Mode 1 Gbps Mode
RIC-D No restrictions Supports RFUs with capacity of up to

1 Gbps
RMC-B Must be part of a Multi- Multi-Carrier ABC and 1+0
Carrier ABC group
RMC-A Cannot be used 1+0
RMC-E Must be part of a Multi- Must be part of a Multi-Carrier ABC
Carrier ABC group group
LIC-X-E10 Cannot be used Slot section (B, E, or F) is automatically
configured to 10 Gbps mode when the
Expected Card Type is set to LIC-X-E10.
LIC-X-E4-Elec Cannot be used Slot sections B, E, and F– no restrictions
LIC-X-E4-Opt Cannot be used Slot sections B, E, and F– no restrictions
LIC-T16 Cannot be used No restrictions
LIC-T155 Cannot be used No restrictions
LIC-STM1/OC3-RST Must be part of a Multi- Must be part of a Multi-Carrier ABC
Carrier ABC group group
Figure 1: 1RU Chassis – Slot Sections
Page 118 of 129

Figure 2: 2RU Chassis – Slot Sections

It is important to note that only the following cards can operate in a section
configured to 2.5 Gbps mode:
• RIC-D
• RMC-B, when part of a Multi-Carrier ABC group
• LIC-STM1/OC3-RST, as part of a Multi-Carrier ABC group
• RMC-E, as part of a Multi-Carrier ABC group
If you only need to configure one four-slot section to 2.5 Gbps mode in a 2RU
chassis, it is recommended to use Section D rather than Section C. This is because
of the slot limitations described in Additional Slot Guidelines on page 120.
In 1 Gbps mode, you can mix all types of traffic and radio cards in the same
section, subject to the card population guidelines described in the rest of this
chapter.
Page 119 of 129

13.6.9 Additional Slot Guidelines

When using Multi-Carrier ABC, the ABC mechanism requires one slot on the
chassis as a dedicated Multi-Carrier ABC slot. That means the slot either be
populated with a card that belongs to the ABC group or the slot must be empty.
The identity of this dedicated slot depends on the ID number of the ABC group, as
described in Table 50. For example, if two Multi-Carrier ABC groups are configured
on a 2RU chassis and given Group ID 1 and Group ID 2, Slot 3 and Slot 4 should
both be populated by cards assigned to an ABC group.
Note: The cards do not have to be assigned specifically to the group that
corresponds to the slot. For example, the card in Slot 3 could be
assigned to ABC Group 2.
Table 50: Additional Slot Limitations with Multi-Carrier ABC

Group Number Affected Slot in 2RU Chassis Affected Slot in 1RU Chassis
ABC Group 1 Slot 3 Slot 3

Note: Maximum modulation, ACM, and XPIC support varies for specific
scripts. See the tables in Section 4 for details.
Page 120 of 129

13.7 Hardware Assembly Options for FibeAir IP-20F

Table 51: Hardware Assemblies, FibeAir IP-20F
Part Number Hardware Capabilities
IP-20F-RIT3-E6-T16-C • Three 1 GbE combo interfaces

• Two dual mode GbE or cascading combo interfaces
• Two combo (RJ-45 or SFP) radio interfaces
• An additional interface that can be configured as a combo (RJ-45
or SFP) radio interface or a 1 GbE interface
• 16 TDM interfaces
• Synchronization interfaces T4 output
• IEEE-1588 BC support (planned for future release)
• Dual DC power input feed
• Two management ports 100Base-TX, which connect to a single
RJ-45 physical connector on the front panel (MGMT)
Page 121 of 129

13.8 Hardware Assembly Options for FibeAir IP-20G

Table 52: Hardware Assemblies, FibeAir IP-20G
IP-20G-M2-E6-T16-C-2DC • Hardware supports two radio carriers

• 6 Gigabit Ethernet ports: 2 Optical and 4 Electrical
• IEEE-1588 BC support, 1pps input
IP-20G-M2-E6-T16-2DC • Hardware supports two radio carriers
IP-20G-M1-E6-T16-2DC • Hardware supports a single radio carrier
IP-20G-M1-E6-2DC • Hardware supports single radio carrier
IP-20G-M2-E6-2DC • Hardware supports dual radio carrier
Page 122 of 129

13.9 Hardware Assembly Options for FibeAir IP-20GX
13.9.1 IP-20GX Hardware Assemblies
Table 53: Hardware Assemblies, FibeAir IP-20GX

IP-20GX-M2-E6-T16-C-2DC • Hardware supports two radio carriers

• 16 E1/DS1 interfaces
• IEEE-1588 BC support, 1pps input (planned for future release)
IP-20GX-M2-E6-T16-2DC • Hardware supports two radio carriers
• 16 E1/DS1 interfaces
13.9.2 IP-20GX Expansion Slot Options

IP-20GX includes two expansion slots. These slots can be populated with any
combination of the following cards:
• Radio Modem Cards (RMC):
◦ RMC-A
◦ RMC-B
• TDM Line Cards (LIC):
◦ TDM – LIC-T16 (16x E1/DS1)
◦ TDM – LIC-T155 (1x ch-STM-1/OC-3)
In the Web EMS and CLI, the slot number for interfaces located in an expansion
slot is Slot 2 or Slot 3. The slot number for fixed interfaces is Slot 1.
The following guidelines apply to the expansion slots:
• Activation of expansion Slot 2 disables GbE port 4 on the front panel.
• Activation of expansion Slot 3 disables GbE port 3 on the front panel.
• Ethernet LICs are not supported in the expansion slots.
Page 123 of 129

13.10 Approved SFP Modules for IP-20 IDUs

Table 54: SFP Modules for IP-20 IDUs (GbE)
Part Number Marketing Model Marketing Description Item Description
AO-0058-0 SFP-GE-ZX SFP optical interface XCVR,SFP,1550nm,2.125G,SM,80km,W.DDM

1000Base-ZX
AO-0068-0 SFP-GE-ELC- SFP ELECT INT XCVR,SFP,COOPER 1000BASE-T,RX_LOS ENABLED
RXLE 1000Base-T RX_LOS
enabled
AO-0193-0 SFP-BX-U-OPT SFP SM Fiber, XCVR,SFP,SINGLE FIBER,1310nm TX/1490nm
1310nm TX, 1490nm RX,1.25Gb,SM,10km,W.DDM,COMMERCIAL,SINGLE PACK KIT
RX
AO-0194-0 SFP-BX-D-OPT SFP SM Fiber, XCVR,SFP,SINGLE FIBER,1490nm TX/1310nm
1310nm RX, 1490nm RX,1.25Gb,SM,10km,W.DDM,COMMERCIAL,SINGLE PACK KIT
TX
AO-0226-0 SFP-GE-CWDM- SFP GE CWDM, XCVR,SFP,1510nm,GE,SM,CWDM,120km,W.DDM,COMMERCIAL
120km-1510nm 120Km, 1510nm TEMP
ER-8003-0 SFP-GE-ELC SFP electrical SFP 1000BASE-T 1.25 GBd Small FormPluggable Low Voltage
interface 1000Base-T (3.3 V) ElectricalTransceiver over Category 5 Cable with package
ER-8000-0 SFP-GE-SX SFP optical interface XCVR,SFP,850nm,MM,1.0625 Gbit/s FC/ 1.25 GBE,PACKED
1000Base-SX
ER-1002-0 SFP-GE-LX SFP optical interface XCVR,SFP,1310nm,1.25Gb,SM,10km,W.DDM, SINGLE PACK KIT
1000Base-LX*ROHS
Table 55: SFP Modules for IP-20 IDUs (2.5GbE)

AO-0165-0 SFP-3.7G-SX- SFP-3.7G-SX-EXT- XCVR,SFP,850nm,MM,3.7 Gbit/s, INDUSTRIAL GRADE

EXT-TEMP TEMP
AO-0265-0 SFP-3.7G-LX- SFP-3.7G-LX-EXT- XCVR,SFP,1310nm,SM,10km,3.7 Gbit/s, INDUSTRIAL

EXT-TEMP TEMP GRADE
Table 56: SFP Modules for IP-20 IDUs (10GbE)

AO-0258-0 SFP+10GBASE- SFP+ 10GE optical XCVR,SFP+,1310nm,SM,10 Gbit/s,2km,COMMERCIAL GRADE

LR interface 10GBASE-LR
AO-0224-0 SFP+10GBASE- SFP+ 10GE optical XCVR,SFP+,850nm,MM,10 Gbit/s, COMMERCIAL GRADE
SR interface 10GBASE-SR
Page 124 of 129

Table 57: SFP Modules for STM-1/OC-3

AO-0096-0 SFP-STM-1-Elec- SFP STM-1 Module XCVR,SFP,STM1E-SFP 155Mbps 1.0/2.3

1.0/2.3-75ohm Elec, 1.0/2.3, 75ohm
AO-0073-0 SFP-STM-1-L1.1 SFP STM-1 Module XCVR,SFP,1310nm,OC3,SM,40km,W.DDM
Long Haul 1310nm
AO-0074-0 SFP-STM-1-L1.2 SFP STM-1 Module XCVR,SFP,1550nm,OC3,SM,80km,W.DDM
Long Haul 1550nm
AO-0118-0 SFP-STM-1- SFP STM-1 Module XCVR,SFP,1310nm,OC3,MM,2km,W.DDM
MM_1310 Multi Mode 1310nm
AO-0072-0 SFP-STM-1-S1.1 SFP STM-1 Module XCVR,SFP,1310nm,OC3,SM,15km,W.DDM
Short Haul 1310nm
Note: Ceragon recommends the use of SFP modules certified by Ceragon,

as listed above.
Page 125 of 129

14. Annex B – Supported Ciphers for Secured

Communication Protocols
The following tables list ciphers that are supported for secured communication
protocols in IP-20 products.
Note: Only ciphers marked with an (*) are supported in FIPS mode.
Table 58: Supported Ciphers for SSH and SFTP

Cipher SSH SFTP
3des-cbc ✓ ✓
aes128-cbc ✓ ✓
aes128-ctr ✓
aes192-ctr ✓
aes256-ctr ✓
aes192-cbc ✓ ✓
aes256-cbc ✓* ✓*
arcfour ✓ ✓
arcfour128 ✓
arcfour256 ✓
blowfish-cbc ✓ ✓
cast128-cbc ✓ ✓
Table 59: Supported Ciphers for HTTPS

Cipher SSLv3 TLSv1.0 TLSv1.1 TLSv1.2
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA ✓ ✓ ✓ ✓
TLS_DHE_RSA_WITH_AES_128_CBC_SHA ✓ ✓* ✓* ✓*
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 ✓*
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 ✓
TLS_DHE_RSA_WITH_AES_256_CBC_SHA ✓ ✓* ✓* ✓*
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 ✓*
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 ✓
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA ✓ ✓ ✓ ✓
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA ✓ ✓ ✓ ✓
TLS_DHE_RSA_WITH_DES_CBC_SHA ✓ ✓ ✓ ✓
TLS_DHE_RSA_WITH_SEED_CBC_SHA ✓ ✓ ✓ ✓
Page 126 of 129

Cipher SSLv3 TLSv1.0 TLSv1.1 TLSv1.2
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA ✓ ✓ ✓ ✓
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA ✓ ✓* ✓* ✓*
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 ✓*
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ✓
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ✓ ✓* ✓* ✓*
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ✓*
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ✓
TLS_ECDHE_RSA_WITH_RC4_128_SHA ✓ ✓ ✓ ✓
TLS_RSA_WITH_3DES_EDE_CBC_SHA ✓ ✓ ✓ ✓
TLS_RSA_WITH_AES_128_CBC_SHA ✓ ✓* ✓* ✓*
TLS_RSA_WITH_AES_128_CBC_SHA256 ✓*
TLS_RSA_WITH_AES_128_GCM_SHA256 ✓
TLS_RSA_WITH_AES_256_CBC_SHA ✓ ✓* ✓* ✓*
TLS_RSA_WITH_AES_256_CBC_SHA256 ✓*
TLS_RSA_WITH_AES_256_GCM_SHA384 ✓
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA ✓ ✓ ✓ ✓
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA ✓ ✓ ✓ ✓
TLS_RSA_WITH_DES_CBC_SHA ✓ ✓ ✓ ✓
TLS_RSA_WITH_IDEA_CBC_SHA ✓ ✓ ✓ ✓
TLS_RSA_WITH_RC4_128_MD5 ✓ ✓ ✓ ✓
TLS_RSA_WITH_RC4_128_SHA ✓ ✓ ✓ ✓
TLS_RSA_WITH_SEED_CBC_SHA ✓ ✓ ✓ ✓
Page 127 of 129

15. Annex C: Main IP-20F Features in Release 10.0

The following are the main features supported by FibeAir IP-20F in its initial
release, CeraOS 10.0.
• Radio Features
◦ Frequency: 4-42 GHz (Microwave) and 71-86 GHz (E-Band)
◦ Channel Spacing – Microwave: – 14 – 112 MHz channels
◦ Channel Spacing – E-Band: 50, 100, and 250 MHz channels
◦ Modulation – Microwave: BPSK to 4096 QAM with hitless ACM
◦ Modulation – E-Band: BPSK to 1024 QAM with hitless ACM
◦ ACM adaptive power
◦ Header De-Duplication
◦ ATPC Override Timer
• Ethernet Features
◦ L2 Smart Pipe
◦ L2 Ethernet switch
◦ Ethernet QoS (Classification by P-bit/DSCP/MPLS, Marking, Rate-meter
policing, WFQ, WRED)
◦ Frame Cut Through
◦ LAG
◦ LACP
◦ Y.1731 Connectivity Fault Management (CFM)
◦ LLDP
◦ Automatic State Propagation
◦ Link Loss Forwarding
◦ G.8032 Ethernet Ring Protection Switching (ERPS)
◦ Multiple Spanning Tree Protocol (MSTP)
• TDM Features
◦ 16 x E1/DS1
◦ XC capacity – 256 VCs
◦ Timing options – Loop timing, system clock, recovered clock
◦ 1+1 / 1:1 path protection
• Synchronization
◦ SyncE with SSM/ESMC:
◦ Input: Ethernet and radio traffic interfaces, 2MHz and E1 via T3
input from Sync interface
◦ Output: Ethernet and radio traffic interfaces, 2MHz and E1 via T4
output from Sync interface
• Management
◦ Web EMS with quick configuration wizards, unit and radio summary
pages, and quick platform setup
Page 128 of 129

◦ CLI
◦ SNMP (v1, v2, and v3)
◦ Alarm display, configuration, and alarm statistics page in Web EMS
◦ SFTP
◦ SSH
◦ HTTPS (IPv4 and IPv6)
◦ IPv6, IPv4 for management
◦ SW Download via FTP, SFTP, HTTP, HTTPS
◦ Timed SW installation
◦ Configurable ETSI/ANSI Mode
◦ Activation Key Reclaim
◦ CeraPlan Service for Creating Pre-Defined Configuration File
◦ Ping command in CLI
◦ ifTable & ifXtable MIB
◦ Ethernet line interface loopback
• PMs
◦ Ethernet RMON PMs
◦ Radio Signal Quality PMs
◦ Radio Utilization PMs
• Security
◦ X.509 Server Authentication (SA) (part of HTTPS implementation)
◦ RADIUS Authentication
◦ Security Log
◦ Configuration Log
◦ Password Enforcement
Page 129 of 129

Ceragon FibeAir IP-20 Split-Mount Release Notes 10.0 Rev B.10 PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Ceragon FibeAir IP-20 Split-Mount Release Notes 10.0 Rev B.10 PDF

Caricato da

Copyright:

Formati disponibili

Release Notes

FibeAir® IP-20 CeraOS 10.0

Open Source Statement

Ceragon Proprietary and Confidential

2. Software Package ................................................................................................... 27

3. New Products and Features ..................................................................................... 29

4. Feature Release Notes ............................................................................................ 34

Ceragon Proprietary and Confidential

5.6 Radio Options for Evolution IP-20 Systems................................................................................ 49

6. Interoperability with other Ceragon Products .......................................................... 50

7. Version Upgrade Compatibility ................................................................................ 52

8. NMS Version Compatibility ..................................................................................... 59

9. Resolved Issues ....................................................................................................... 62

10. Notes and Limitations ............................................................................................. 63

11. Open Bugs ............................................................................................................ 102

Ceragon Proprietary and Confidential

11.3 Radio ........................................................................................................................................103

12. Synonyms and Acronyms ...................................................................................... 105

15. Annex C: Main IP-20F Features in Release 10.0 ...................................................... 128

Ceragon Proprietary and Confidential

Ceragon Proprietary and Confidential

1.1 Product Overview

1.1.1 FibeAir IP-20F

Also, in CeraOS 10.0, up to four Ethernet interfaces can be used (GbE

1.1.2 FibeAir IP-20G

Ceragon Proprietary and Confidential

1.1.3 FibeAir IP-20GX

1.1.4 FibeAir IP-20N

1.1.5 FibeAir IP-20A

Ceragon Proprietary and Confidential

1.1.6 FibeAir IP-20LH

1.1.7 Evolution IP-20LH

Ceragon Proprietary and Confidential

1.2 CeraOS 10.0 Introduction and Highlights

Ceragon Proprietary and Confidential

1.3 Release History

Table 1: Product Line Release History

10.0.0.0.162 May 2018 FibeAir IP-20F N N N N N Y

Ceragon Proprietary and Confidential

Software Version Date Main Features/ FA FA Evo FA FA FA

9.2.0.0.0.422 August 2017 New GA build for FibeAir IP-20E, Y Y Y Y Y

Ceragon Proprietary and Confidential

Software Version Date Main Features/ FA FA Evo FA FA FA

HSO enhancements – Improved Y Y Y N N

Ceragon Proprietary and Confidential

Software Version Date Main Features/ FA FA Evo FA FA FA

8.5.0.0.0.288 July 2016 Y.1731 Connectivity Fault Management Y Y Y Y Y

Ceragon Proprietary and Confidential

Software Version Date Main Features/ FA FA Evo FA FA FA

8.3.0.0.0.483 March 2016 Radio Payload encryption using AES- Y Y N Y Y

Ceragon Proprietary and Confidential

Software Version Date Main Features/ FA FA Evo FA FA FA

New TCC-B2-XG-MC card Y Y Y N N

Ceragon Proprietary and Confidential

Software Version Date Main Features/ FA FA Evo FA FA FA

RMC-E, SRM (Diplexer) 25MHz XPIC N N Y N N

Ceragon Proprietary and Confidential

Software Version Date Main Features/ FA FA Evo FA FA FA

• MRMC FCC script 40Mhz XPIC ACM Y Y N Y

8.0.0.0.0.677: May 2015 • Two radio interfaces supporting up to Y

Ceragon Proprietary and Confidential

Software Version Date Main Features/ FA FA Evo FA FA FA

7.9.0.0.0.345 March 2015 Fixes bug 129237: Extracting an RMC-E Y