2. Section I: Introduction
1. Introduction
This section includes:
• Configuration Tips
• Product Overview
• System Overview
• The Web-Based Element Management System
• Introduction to the Web EMS
3. 1.1 Configuration Tips
This section describes common issues and how to avoid them.
Ethernet Port Configuration
For RJ-45 ports, it is recommended to enable Auto-Negotiation for both the local port and its peer in order to obtain optimal performance.
For SFP ports, it is recommended to disable Auto-Negotiation.
For instructions, see Configuring Ethernet Interfaces.
Second Radio Interface of a RIC-D
If a RIC-D is connected to a single-carrier RFU, or if the second carrier of a MultiCore RFU is not in use, you should set the Admin status field of the
second Radio interface (Port 2) to Down to disable the Radio interface and prevent unnecessary alarms. See Enabling the Interfaces (Interface
Manager).
SyncE Interface Configuration
When configuring a Sync source or outgoing clock on an Ethernet interface, the Media Type of the interface must be RJ-45 or SFP, not Auto-Type.
See Synchronization.
In-Band Management
It is strongly recommended not to configure ASP on an Ethernet interface that carries in-band management traffic. If you do need to use ASP on this
interface, it is recommended to use it in ASP Management Safe (CSF) mode to avoid loss of management in the event that ASP is triggered. See
Configuring Automatic State Propagation and Link Loss Forwarding.
When inband management is being transmitted via a LAG configuration, it is recommended to enable either LACP or RFI to overcome uni-directional
directional failures:
◦ LACP – See Configuring a LAG Group.
◦ LAG Redistribution (RFI) – See Enabling LAG Redistribution in the Event of RX Failure (CLI).
If you are using 1588 Transparent Clock, make sure the Transparent Clock settings are symmetrical; that is, make sure Transparent Clock is either
enabled or disabled on both sides of the link. To avoid loss of management, make sure to configure Transparent Clock on the remote side of the link
4. Link Aggregation (LAG)
If you are configuring LAG with an external switch, the switch must support LAG.
For instructions on configuring LAG, see Configuring Link Aggregation (LAG) and
LACP.
Software Upgrade
When upgrading software via HTTP, make sure the software package is not
unzipped.
Configuration Management and Backup Restoration
A Configuration file can only be copied to the same IP-20 product type, with the
same chassis type, the same TCC type, and the same card types placed in the same
slots as the unit from which it was originally saved. See Backing Up and Restoring
Configurations.
5. 1.2 Equipment Overview
This section provides a brief overview of the IP-20 systems described in this
presentation. A separate Technical Description is available for each system, providing a
full description of the individual system and its specifications.
6. 1.2.1 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 system is based on a chassis, which is provided in sizes that fit a
a single rack unit or two rack units, and which contains five or ten slots for any mix of Ethernet, TDM, and radio cards.
1.2.2 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,
package, customized to operate according to ANSI (FCC) standards.
1.2.3 FibeAir IP-20LH
FibeAir IP-20LH is a versatile and cost-effective microwave radio solution for long distance, high capacity telecommunication networks.
Offering superior quality and fast deployment capabilities, it is ideal for rapid and economical network rollouts. FibeAir IP-20LH is based
on the IP-20N hardware and software package, customized for long haul networks.
1.2.4 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 lower heat dissipation.
dissipation.
Note: For brevity, this presentation uses RFU to refer to both RFUs and Evolution XCVRs, except where otherwise noted.
1.2.5 FibeAir IP-20 Assured Platform
Ceragon’s FibeAir IP-20 Assured platform enhances network reliability and security, ensuring that mission-critical networks maintain
availability, and protecting the confidentiality and integrity of their users’ data.
The FibeAir IP-20 Assured platform is compliant with FIPS 140-2, including:
• Compliance with FIPS 140-2 specifications for cryptography module.
• FIPS 140-2 Level 2 physical security.
7. • AES-256 encryption (FIPS 197) over radio links.
The FibeAir IP-20 Assured platform also provides:
• Secured communication and protocols for management interface.
• Centralized user authentication management via RADIUS.
• Advanced identity management and password policy enforcement.
• Security events log.
• Secure product architecture and development.
The following products are included in the FibeAir IP-20 Assured platform:
• FibeAir IP-20N Assured
• FibeAir IP-20A Assured
• FibeAir IP-20LH Assured
Note: CeraOS 10.9 cannot be used in FibeAir IP-20 Assured platforms. For FibeAir IP-20
Assured, use CeraOS 8.3.
8. 1.3 System (CERAGON) Overview
A split-mount or all-outdoor FibeAirIP-20 system consists of an IP-20N indoor unit (IDU)
and any of the following radio frequency units (RFUs):
• 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. Interfaces
with the IDU via RIC-D.
• 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. Interfaces with the IDU via RIC-D.
• 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. Interfaces with the IDU via RIC-D.
• RFU-S – Operates in the 6-42 GHz frequency range, supporting channel bandwidth of
14-112 MHz and modulations of BSPK to 4096 QAM. Interfaces with the IDU via RIC-D.
• RFU-C – Supported with FibeAir IP-20N and IP-20A systems. A state-of-the-art RFU
designed for a broad range of interfaces and capacities from 10 Mbps up to 500 Mbps.
RFU-C operates in a wide range of spectrum bands, from 6 to 42 GHz. The premium
version, RFU-Ce, provides a range of modulations from QPSK to 2048 QAM. Interfaces
with the IDU via RMC-B or RMC-A. RFU-C and RFU-Ce require RFU SW version: 2.17.
9. • 1500HP/RFU-HP – Supported with FibeAir IP-20N, IP-20A, and IP-20LH systems.
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 and
RFU-HP can chain up to five carriers per single antenna port and 10 carriers for dual
port, making them ideal for trunk or multi carrier applications. The 1500HP and RFU-HP
can be installed in either indoor or outdoor configurations. Interfaces with the IDU via
RMC-B or RMC-A. RFU-HP requires RFU SW version: 5.14. 1500HP requires RFU SW
version 8.13a2.
• RFU-A (including RFU-Ae/Aep) –Supported with FibeAir IP-20A systems. 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 6, 7, 8, and 11 GHz.1 Interfaces with the IDU via RMC-B or RMC-A. RFU-A
requires RFU SW version: 5.14.
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)
Both transceivers interface with the IDU via RMC-E.
10. 1.3.1 System Components
Traffic Control Card (TCC)
IP-20N offers the following types of TCC:
• TCC-B – Standard TCC option. Provides 2 x FE Ethernet management interfaces and 2 x GbE combo interfaces (electrical or optical) for Ethernet traffic.
• TCC-B-MC – Supports single Multi-Carrier ABC groups with capacity of up to 1 Gbps. Provides 2 x FE Ethernet management interfaces and 2 x GbE combo interfaces (electrical or
optical) for Ethernet traffic.
• TCC-B2 – Provides 2 x FE Ethernet management interfaces, 2 x GbE optical interfaces, 2 x GbE electrical interfaces, and 2 x dual mode electrical or cascading interfaces.
• TCC-B2-XG-MC – Supports up to two Multi-Carrier ABC groups with capacity of 2.5 Gbps or up to four Multi-Carrier ABC groups with capacity of 1 Gbps per group. Provides 2 x FE
Ethernet management interfaces, 2 x GbE optical interfaces, 2 x GbE electrical interfaces, and 2 x dual mode electrical or cascading interfaces.
All TCC models can be used in both 1RU and 2RU chassis and support TCC redundancy. In a chassis with TCC redundancy, both TCCs must be the same model.
FibeAir and Evolution IP-20LH systems require TCCs that support Multi-Carrier ABC configurations (TCC-B-MC or TCC-B2-XG-MC).
Radio Modem Cards (RMC) and Radio Interface Cards (RIC)
The Radio Modem Card (RMC) or Radio Interface Card (RIC) provides the interface between the IDU and the RFU.
In FibeAir IP-20N and IP-20A systems, the 1RU IDU can accommodate up to five RMCs and/or RICs and the 2RU IDU can accommodate up to ten RMCs or RIC eight RICs.
In FibeAir and Evolution IP-20LH systems, the 1RU IDU can accommodate up to four RMCs and the 2RU IDU can accommodate up to eight RMCs.
The following RMCs and RICs are available:
• RMC-A – Supported with FibeAir IP-20N and IP-20A systems2 and used with RFU-C, 1500HP/RFU-HP, and RFU-A. Based on the same modem technology used in IP-10 family IDUs.
Supports up to 256 QAM (with ACM).
• RMC-B – Supported with FibeAir IP-20N, IP-20A, and IP-20LH systems and used with RFU-C, 1500HP/RFU-HP, and RFU-A. Supports up to 2048 QAM, Header De-Duplication, XPIC,
Multi-Carrier ABC, and BBS Space Diversity.
11. • RMC-E – Supported with Evolution IP-20LH systems. Supports up to 2048 QAM, XPIC,
and Multi-Carrier ABC. Includes an STM-1/OC-3 RST interface for both radio and TDM
support.
• RIC-D – Supported with FibeAir IP-20N and IP-20A systems and used with RFU-D,
RFU-D-HP, RFU-E, and RFU-S. Supports up to 4096 QAM, Header De-Duplication, XPIC,
and Multi-Carrier ABC.
Line Cards (LIC)
IP-20N supports the following Ethernet and TDM traffic line cards (LICs):
• Ethernet Line Card – LIC-X-E4-Elec – 4x GE, with 1 GbE combo interface and 3 GbE
electrical (RJ-45) interfaces
• Ethernet Line Card – LIC-X-E4-Opt – 4x GE, with 1 GbE combo interface and 3 GbE
optical (SFP) interfaces
• Ethernet Line Card – LIC-X-E10 – 1 x 10G optical interface
• TDM Line Card – LIC-T16 (E1/DS1) – 16 x E1/DS1
• TDM Line Card – LIC-T155 (STM-1/OC-3) – 1 x ch-STM-1/OC-3 with RJ-45
synchronization interface
• TDM Line Card – LIC-STM1/OC3-RST (STM-1/OC-3) – 1 x STM-1/OC-3
12. 1.3.2 IDU Overview and Slot Population Guidelines
Two basic chassis options are provided:
• 1RU – Fits in a single ETSI rack slot, with one Main Traffic and Control Card (TCC), five
universal slots for a combination of up to four (for FibeAir and Evolution IP-20LH
systems) or five (for FibeAir IP-20N and IP-20A systems) Radio Modem Cards (RMCs)
and/or Radio Modem Cards (RICs) and/or five Line Cards for traffic (LICs), and a Power
Distribution Card (PDC).
• 2RU – Fits in two ETSI rack slots, with one or two Main Traffic and Control Cards (TCCs),
ten universal slots for a combination of up to eight (for FibeAir and Evolution IP-20LH
systems) or ten (for FibeAir IP-20N and IP-20A systems) Radio Modem Cards (RMCs), or
up to eight Radio Interface Cards (RICs), and/or ten Line Cards for traffic (LICs), and two
Power Distribution Cards
The figures below show the 1RU and 2RU chassis slot numbers. The mapping of the
numbered slots to the different cards is described in the tables that follow.
Figure 1: 1RU Chassis Slot Numbering
13. Figure 2: 2RU Chassis Slot Numbering
The following tables list the card types that can be inserted in each slot.
Table 2: Card Types Allowed Per Slot – 1RU .
Slot Number Allowed Card Type Notes
1 •TCC
Does not include LIC-
STM1/OC3-RST (1 x
STM1/OC-3)
2
RMC-A, RMC-B, RIC-D
• Ethernet LIC
• TDM LIC
3 TO 6
• RMC-A, RMC-B, RMC-E, RIC-D
When a single Multi-Carrier
ABC group is used, consisting
of RMCs, slot 3 can be
unoccupied or must be
populated with an RMC,
which must be part of the
Multi-Carrier ABC group.
• TDM LIC
