IP10G Nodal Configuration-Rev1 1

IP10G Nodal Solution

Configuration file

FibeAir® IP-10G

August 2010

PROPRIETARY

Table of Contents

TABLE OF CONTENTS...........................................................................................................................2

1. DOCUMENT CONTROL................................................................................................................3

2. EQUIPMENT................................................................................................................................3

3. IP-10G NODAL CONFIGURATION.................................................................................................4

3.1 Shelf Characteristics...........................................................................................................43.2 Management in a Shelf Configuration................................................................................53.3 Centralized System Features...............................................................................................5

4. GENERAL SHELF CONFIGURATION..............................................................................................7

4.1 Pre configuration check......................................................................................................74.2 Configuring the Shelf from scratch.....................................................................................7

5. 1+1 CONFIGURATION IN A SHELF................................................................................................8

5.1 Protection – General Notes.................................................................................................85.2 Conditions for Protection....................................................................................................95.3 Configuring “Protection Enable” from “scratch” in shelf configuration..............................10

IP10G Nodal Solution Nodal Configuration Rev1 .02

PROPRIETARY

1. Document Control

Ceragon Networks Ltd.

Project: IP10G

Document Name: IP10G Nodal configuration

Publication History

Revision Date Author Notes

Rev 1.0 11/08/2010 Erez Aviv

2. Equipment

Ceragon Equipment FibeAir® IP-10G

IDU SoftwareI6.6GA

IDU Package6.6.0.0.2.53

NMS PolyView Server

NMS SoftwareN6.6GA

NMS Package6.6.0.0.2


PROPRIETARY

3. IP-10G Nodal Configuration

IP-10G can be used in two distinct modes of operation:

Stand-alone configuration: In this mode the system performs basically as in previous versions, allowing point-to-point TDM and Ethernet transport.

Nodal configuration: In this mode several IDUs are stacked in a dedicated modular shelf, and act as a single network element (NE) having multiple radio links.

3.1 Shelf Characteristics

There are two kinds of shelves available: main and extension. A main shelf is required in each node, and can hold two IDUs. Extension shelves can be stacked on top of main shelves; each extension shelf can contain two more IDUs, and up to two extension shelves can be stacked, allowing nodes of up to 6 radio links:

IDUs in such a shelf get each a “slot ID” indicating their position: slot 1 is the lowest IDU and 6 is the highest

In each such node, IDUs may assume two different roles:


PROPRIETARY

Main IDU: centralizes management access to the system, and provides the switching fabric for TDM trails. Unit number 1 (the lowest unit in a shelf) is always a main unit. Unit number 2 is a main unit if configured as protected 1+1 (in which case it protects IDU#1); otherwise it is an extension unit.

Extension IDU: provides radio and line interfaces for TDM trails. It is accessed through the main unit.

3.2 Management in a Shelf Configuration

In a shelf configuration all management is carried out through the main unit, which communicates with the extension units by an internal shelf communications network. Therefore, it is required that management traffic arrives to the main unit for management to be available.

Local craft terminal (CLI) is available in each IDU individually. However, with the exception of the main unit functionality is limited to local configurations. From the main unit’s CLI access to all other units is provided.

For remote channels (WEB, telnet, NMS) this requires IP traffic to be directed to the main unit.

This is not carried out by the internal network, and therefore Ethernet cables must connect traffic from the extension units to the main unit. Use of each channel is described in the respective section below.

The IP address of the shelf is the address of the main unit in it. For 1+1 units, the shelf will have two IP addresses (the addresses of each of the main units) and it should be managed via the active unit.

3.3 Centralized System Features

Some system features make use of the shelf configuration and can be configured and monitored from the main unit. Others are available individually in each IDU in the system.

The main reason for this is that some features are strictly point-to-point (such as radio link configurations and performance) and therefore there is no value in centralizing them, while others encompass the shelf as a single unit.

Following is a list of features which are centralized and are handled by the main unit:

IP communications: All communication channels are opened through the main unit’s IP address

Management channels: WEB, CLI, SNMP offer mechanisms to reach every unit in the shelf (see below)


PROPRIETARY

Users management: login, adding/deleting users.

TDM trails cross-connect: TDM trails definitions, PM, statuses are all handled centrally from the main unit

Nodal time synchronization: system time is automatically synchronized in all IDUs in a shelf

Nodal software version management: SW version can be upgraded/downgraded in all IDUs from the main unit

Nodal configuration backup: configuration files can be created, downloaded and uploaded via the main IDU

Nodal reset: extension units can be reset individually or collectively from main unit, or locally

All other features are handled in each IDU individually.


PROPRIETARY

4. General Shelf Configuration

4.1 Pre configuration check

Before inserting the IDU’s into the shelf, User needs to check the following:

Replacing the brackets (“Ears”) into the shelf brackets All IDU’s has the same SW version.

Note: Do not insert/extract IDU’s to and from the chassis under power!

4.2 Configuring the Shelf from scratch.

Insert IDU’s into the shelf, while it is powered off. Power on the IDU’s from bottom to top. Configure the IP address, subnet mask and default gateway of the IDU in slot

#1.

Note: in non-protection mode, there is no need to configure more than 1 IP address in the system (slot #1). All the other IDU’s management ports will be shut down, and there is no need to change their IP addresses (for example – 192.168.1.1 – can be used for all the 2-6 IDU’s, or it can be configured to 10.1.1.2-10.1.1.6).


PROPRIETARY

5. 1+1 configuration in a shelf

5.1 Protection – General Notes

Equipment protection is possible in two configurations:

"External Protection" is achieved by using two separate boxes in stand-alone configuration. In this case, the IDUs must be connected by a dedicated Ethernet protection cable. Each box has its unique IP address.

1+1 protection in a shelf: in this case, units are connected by the backplane, and there is no need for extra cable. There is one IP address for each of the main units.

When a switchover occurs, and previous "Active" becomes "Standby", it should be understood that access to the new "Active" will be done using its IP address, which is obviously different than previous "Active" unit's IP address.

A "Protection Panel" or protection split cable is designed to implement E1/DS1 splitters. Split cables must be used for Ethernet signals. Customer equipment’s cables should be connected to the panel and cables. "Active" & "Standby" units' traffic, management and wayside ports should also be connected to the panel. It is also possible to use Ethernet splitters to FE and SFP (Optical GbE) ports.

Electrical GbE (10/100/1000) interface can be split (via panel, or via split cables) according to the following limitations:

o Should be set to “Autoneg OFF” with “100 Full”.

o When Standby unit is powered OFF and back ON, Ethernet traffic running through this port may be affected in the Active unit.


PROPRIETARY

5.2 Conditions for Protection

The following conditions must be met at both units for 1+1 protection configuration to be valid and work properly:

Both IDUs must have identical hardware (same P/N)

Same Ethernet application (smart pipe, managed switch, metro switch)

Management type should be the same (i.e. both out of band or both in-band) – otherwise “mate communication error” alarm will be raised

In case both are in-band management – in-band VLAN should be the same.

In case both are in-band management – in-band VLAN must NOT be used for traffic.

Different IP addresses (within the same subnet) should be configured for both units.

Both IDU's should have protection enabled.

Both IDU’s should have the same license type.

Notice that if it is desired to change the management type or in-band VLAN in an established 1+1 configuration, doing so in the active unit will cause communications to be lost. Therefore they should be first changed in the stand-by unit.

The conditions above are the minimum requirement for proper communications to be established between the active and the stand-by units. Even if they are fulfilled, after configuring 1+1 protection there still may be a configuration mismatch between the units. This will not cause communications to be lost, but in order to assure proper operation in case of a protection switch, user should make sure that configuration is identical at all times (see copy-to-mate mechanism below)


PROPRIETARY


PROPRIETARY

5.3 Configuring “Protection Enable” from “scratch” in shelf configuration

1. Disconnect all cables from units (radio, traffic, wayside, protection…), except for management cable.

2. Turn ON 1st unit.

3. 1st unit, connect management cable to the management interface, or via terminal configure the IDU:

a. Install License (if necessary).

b. Upgrade SW (if necessary).

c. Configure radio related parameters: radio parameters, radio script, etc.

d. Set security configurations: add users, SNMPv3, HTTPS, etc.

e. Set the required “Switch Application” (Single pipe, Managed Switch or Metro switch).

f. Configure “management type” (“out-of-band or “in-band”). If “in-band” is required, set its desirable “management VLAN ID” (CQ20084).

4. 1st unit: issue "Protection Admin Enable". At this point, management might be lost for approximately 50sec. Management will be available again when 50 sec time period is terminated.

5. 1st unit: Issue “Lockout”.

6. Do not insert 2nd unit to its slot., and turn it ON while it is outside the node (stand alone)

7. 2nd unit: connect management cable to the management interface. The 2nd unit should be prepared by following procedure (CQ19517):

a. Install its license (if necessary).

b. Upgrade SW (if necessary).

c. Set security configurations: add users, SNMPv3, HTTPS, etc.

d. Set the required “Switch Application” (Single pipe, Managed Switch or Metro switch).

e. Configure “management type” (“out-of-band or “in-band”) to fit the “Active” unit’s “management type”. If “in-band” is required, set its desirable “management VLAN” (CQ20084).

8. 2nd unit: Issue "Protection Admin Enable".

9. Turn OFF 2nd unit.

10. Insert 2nd unit to its slot. Install rack screws to ensure IDU is properly secured,


PROPRIETARY

and turn it ON. At this point, both units should start communicating, exchanging their local MAC & IP addresses.

11. Check on both units that "Mate Communication Failure" alarm is not raised. If it is raised, then "protection" installation is failed.

12. The management cable can be disconnected from the 2nd unit. Use ‘Y’ splitter cable or the “protection panel” to connect both units’ management interfaces.

13. If "Configuration Mismatch" alarm is raised, it means both units are not synchronized in terms of configuration. In this case a "copy-to-mate" operation must be issued on the "Active" unit. This operation will copy all "Active" unit's configuration to the mate unit, and then, issue "cold-reset" to the mate unit. When the mate unit is up and running, its configuration should be totally identical to the "Active" unit’s, and "Configuration Mismatch" alarm should be cleared on both units.

14. Connect all traffic, radio, wayside cables to both units (via protection panel, or via splitters). Configure Ethernet and E1/DS1 interfaces to “Enable”. An additional “copy-to-mate” operation should be executed, in order to re-synchronize both units’ configurations.

15. Disable “Protection Lockout” and verify no alarms are raised. Determine which unit should be the "Active" one, and issue "Manual Switch" if this IDU is "Standby".

Note: The IDU, which is connected to the ODU fed by the lower attenuation channel of the RF coupler, is the IDU that should be selected as "Active".

Note2: The same procedure should be issued in the remote end, while installing the radio.

Note3: The same procedure should be implemented on both extensions.

Note4: 2 different IP addresses need to be configured in the IDU #1 and in IDU #2. The other IDU’s IP addresses have no meaning.


Documents

IP10G Nodal Configuration-Rev1 1