ip 10g basic course handbook v3.1

Visit our Customer Training Portal at Training.Ceragon.Com

or contact us at [email protected]

Trainee Name:

IP-10G Basic Course

1 Ceragon Training Agenda v2.2

Ceragon Training Agenda

Product: IP-10 G

Course: Basic Operation and Maintenance

Duration: 2 days (Theory + Practice)

DAY ONE

Greetings and Course Opening

IP-10 G-Series Nodal Solution Introduction

Introduction to ODU

Front Panel Overview

Physical Overview

System Architecture & Design:

Standalone VS. Shelf IP allocation in a shelf Management Modes (In Band, OOB, WSC) Switch Mode (Pipe, Managed, Metro) Protection Mode

Page 1

2 Ceragon Training Agenda v2.2

Ceragon Training Agenda

DAY TWO

Installation (Practical Exercise using the Element Management System):

Standalone guidelines Installing IDU in a shelf Protection mode (Main and Extensions) Setting IP address via CLI Setting up a radio link (frequency, Link ID, RSL, TSL, ATPC, MSE, MRMC, ASP) Setting MNG in a standalone IDU Setting MNG in a shelf Setting MNG using Wayside Channel

Troubleshooting Tools & Maintenance:

Using the Current Alarms Using the Event Log Using RMON Registers and Statistics Performing Loopbacks Saving Unit Information Files Configuration File Upload / Download Software File Download

Licensing (retrieving license and installing license on IDU)

Trap Configuration

Course Summary / Exam

Page 2

6/13/2010

1

Ceragon in a Nutshell

Ceragon FibeAir Family

Carrier Ethernet Switch TDM Cross Connect

ACM Ch-STM1/

OA&M Service Management Security

XPIC

Proprietary and Confidential2

Native2 RadioEthernet + TDM

OC3

Terminal Mux

E1/T1FastEthernet

GigabitEthernet

10-500Mbps, 7-56MHz

RFU (6-38GHz)

MultiRadio

SD/FD

Page 29

6/13/2010

2

RFUs

FibeAir RFU-HP FibeAir RFU-HS FibeAir RFU-P FibeAir RFU-C FibeAir RFU-D

Proprietary and Confidential

High power(e.g. Smaller antennas – reduced cost)

Standard power

3

ISPs

CERAGON MAST - Mobile Architecture for Service Transport

Fixed

Cable TV

Networks

Cellular Backhaul Rural Access


PDH

IP DSLAM

PSTN

xDSLSubscribers

SDH/SONET RING

IP/ETH Customer Network

Page 30

6/13/2010

3

CERAGON MAST - Mobile Architecture for Service Transport

Complete end-to-end network architecture, powering operators with a highly efficient, scalable and cost-optimized solution for scaling up their networksscaling up their networks

Regardless of transport technology or the service being carried MAST offers a complete set of tools to ensure high QoS & full OA&M functionality across entire networks

• Allows risk-free migration to IP/Ethernet• Simplifies fixed and mobile network designs • Giving operators a single point of contact for all the transport, networking and service


g p g p p gdelivery needs

• A true end-to-end, service-oriented package

MAST allows customers to design highly scalable, flexible and future-proof networks in a simple and cost efficient manner

FibeAir IP-10R1 – Main features

• Unique Adaptive Coding & Modulation (ACM)

• Enhanced radio efficiency and capacity for Ethernet traffic• Enhanced radio efficiency and capacity for Ethernet traffic• Integrated Carrier Ethernet switching functionality

• Enhanced QoS for differentiated services

• Supported configurations

• 1+0

• 1+1 HSB – Fully-redundant!

• Nodal solution with ring


• Extensive and secure management solution

6

Page 31

6/13/2010

4

IP-10R1 Integrated Carrier Ethernet switch

3 modes for Ethernet switching:

• Metro switch – Carrier Ethernet switching is enabled

• Managed Switch – 802.1 L2 switchManaged Switch 802.1 L2 switch

• Smart pipe – Carrier Ethernet switching is disabled

• Only a single Ethernet interface is enabled for user traffic

• The unit operates as a point-to-point Ethernet MW radio

IP-10

Radio

IP-10

Radio Ethernet

User

Ethernet

User


interface interface

Smart pipe modeMetro/Managed switch mode

User

Interfaces

User

Interface

Carrier EthernetSwitch

Extensive Carrier Ethernet feature-set

eliminates the need for external switches7

IP-10R1 radio capacity - ETSI7MHz

ACMPoint

Modulation# of E1s

Ethernet Capacity (Mbps)

1 QPSK 4 9.5 – 13.5

2 8 PSK 6 14 – 20

3 16 QAM 8 19 – 28

ACMPoint

Modulation# of E1s


1 QPSK 8 20 - 29

2 8 PSK 12 29 - 41

3 16 QAM 16 42 60

14MHz

ACMPoint

Modulation# of E1s


1 QPSK 16 38 - 54

ACMPoint

Modulation# of E1s


1 QPSK 16 76 - 109

ACMPoint

Modulation# of E1s


1 QPSK 16 56 - 80

3 16 QAM 8 19 – 28

4 32 QAM 10 24 – 34

5 64 QAM 12 28 – 40

6 128 QAM 13 32 – 46

7 256 QAM 16 38 – 54

8 256 QAM 16 42 – 60

3 16 QAM 16 42 - 60

4 32 QAM 16 49 – 70

5 64 QAM 16 57 – 82

6 128 QAM 16 69 - 98

7 256 QAM 16 81 - 115

8 256 QAM 16 87 - 12528MHz 40MHz 56MHz


2 8 PSK 16 53 - 76

3 16 QAM 16 77 - 110

4 32 QAM 16 103 - 148

5 64 QAM 16 127 - 182

6 128 QAM 16 156 - 223

7 256 QAM 16 167 - 239

8 256 QAM 16 183 - 262

2 8 PSK 16 114 - 163

3 16 QAM 16 151 - 217

4 32 QAM 16 202 - 288

5 64 QAM 16 251 - 358

6 128 QAM 16 301 - 430

7 256 QAM 16 350 - 501

8 256 QAM 16 372 - 531

2 8 PSK 16 82 - 117

3 16 QAM 16 122 - 174

4 32 QAM 16 153 - 219

5 64 QAM 16 188 - 269

6 128 QAM 16 214 - 305

7 256 QAM 16 239 - 342

8 256 QAM 16 262 - 374

8

Page 32

6/13/2010

5

Wireless Carrier Ethernet Ring Example configuration (1+0 ring)

N x GE/FE

N x GE/FE N x GE/FE

WirelessCarrier Ethernet

Ring


(up to 500Mbps)

Integrated EthernetSwitching

N x GE/FE

9

Native2 Microwave Radio Technology

• At the heart of the IP-10 solution is Ceragon's market-leading Native2

microwave technology.

• With this technology, the microwave carrier supports native IP/Ethernet traffic together with optional native PDHtraffic together with optional native PDH.

• Neither traffic type is mapped over the other, while both dynamically share the same overall bandwidth.

• This unique approach allows you to plan and build optimal all-IP or hybrid TDM-IP backhaul networks which make it ideal for any RAN (Radio Access Network)


• In addition, Native2 ensures:

• Very low link latency of <0.15 msecs @ 400 Mbps.

• Very low overhead mapping for both ETH & TDM traffic

• High precision native TDM synchronization distribution

10

Page 33

6/13/2010

6

Native Ethernet

Carrier Ethernet (MW links) SDH/SONET (Hybrid Fiber/MW)

Ethernet over SDH/SONET

NG-SDH/SONET complementary solution Carrier Ethernet at the access, NG-SDH/SONET at the aggregation

CoreSite

HubSite

Tail site FibeAir IP-10 NG-SDH

MSPP

RNC

FibeAir IP-10 NG-SDH

MSPP

Ethernet over SDH/SONET

FE/GEGE

GE


Site

Ethernet services are transported natively over Carrier Ethernet based MW radio links.

NG-SDH/SONET MSPP node acts as gateway between the Carrier Ethernet and NG-SDH/SONET based networks.

Ethernet services are mapped over SDH/SONET

SDH/SONET MW links are used where fiber connections not available

11

Native Ethernet

Carrier Ethernet (MW links)

IP/MPLS complementary solution Carrier Ethernet at the access, IP/MPLS at the aggregation

IP/MPLS (Hybrid Fiber/MW)

Ethernet PWs or IP routing

CoreSite

HubSite

Tail site FibeAir IP-10

RNC

FibeAir IP-10

FE/GEGE

GE

MPLSRouter

MPLSRouter

Ethernet PWs or IP routing


Site

Both Ethernet and E1/T1 services are mapped over MPLS using pseudo-wires or routed using IP

High-capacity “IP/MPLS-aware" Ethernet MW radio is used where fiber connections not available

IP/MPLS edge router acts as gateway between the Carrier Ethernet and IP/MPLS based networks.

Ethernet services are transported natively over Carrier Ethernet based MW radio links.

12

Page 34

6/13/2010

7

IP-10R1 integrated QoS support - overview

• 4 CoS/priority queues per switch port

• Advanced CoS/priority classification basedon L2/L3 header fields: • Source Port

• VLAN 802 1 W1 Hi h t i it

Priority Queues

• VLAN 802.1p

• VLAN ID

• IPv4 DSCP/TOS, IPv6 TC

• Highest priority to BPDUs

• Advanced ingress traffic rate-limitingper CoS/priority

• Flexible scheduling scheme per port• Strict priority (SP)

W1 - Highest priority

W2

W3

W4 – lowest priority

Scheduling departures

Classify Arrivals


• Weighted Round Robin (WRR)

• Hybrid – any combination of SP & WRR

• Shaping per port

W4 lowest priority

Support differentiated Ethernet services

with SLA assurance

13

IEEE 802.1ag CFM (Connectivity Fault Management)


Page 35

6/13/2010

8

FibeAir IP-10G IDU: A Nodal Solution


STM Rings

Cellular traffic (TDM)

FibeAir IP-10G IDU: A Nodal Solution


Page 36

6/13/2010

9

IP-10F IDU

Fans drawer

Craft 16 x E1s


Craft Terminal

(DB9)

External Alarms(DB9)

16 x E1s(optional)

5 x FE Electrical

(RJ45)

ProtectionInterface

(RJ45)

RFU interface(N-Type)

Power-48V DC

GND

Typical Native2 network with IP-10 G & F-Series

1+0 1+1 F

FF

1+11+1

F

1+0

1+0F

(22 E1,50M)

4 E1s 25M Eth

4 E1s 25M Eth

4 E1s

4 E1s 25M Eth

4 E1s 25M Eth(22 E1

F

IP-10 F-Series

IP-10 G-Series

IP-10 G-Series with XPIC

4 E1s 25M Eth

(22 E1,50M)

F

GX

GX

G

G

G

G

G

GX

GX

G

G

G

G

G

G

F F F F F

GX

1 1

F

1+0

1+0

F

F

F

1+0

1+0

1+0

1+0

1+0

2+0

2+02 0

F

Native2 1+0 Ring

(Up to 44 E1

or 100M Eth)

Native2 1+0 Ring

(Up to 75 E1

or 500Mbps Eth)

(22 E1,50M)

(44 E1,100M) (44 E1,

100M)4 E1s 25M Eth

4 E1s 25M Eth

25M Eth25M Eth

4 E1s 25M Eth

4 E1s 25M Eth

(22 E1,50M)

4 E1s 25M Eth

Terminal configuration


GX

GX1+0

1+1F

F

F

F

F

F

0

2+0

2+01+0 Native2 2+0 Ring

(Up to 150 E1

or 1Gbps Eth)

4 E1s 25M Eth

4 E1s 25M Eth4 E1s

25M Eth

(22 E1,50M)

(22 E1,50M)

4 E1s 25M Eth

Nodal configuration

Page 37

6/13/2010

10

IP-10G VS. IP-10FFeature F-Series G-Series

Supported radio configurations 1+0, 1+1 HSB, 1+1 SD

1+0, 1+1 HSB, 1+1 SD,

2+0 with XPIC

2+2 HSB with XPIC

XPIC option - Yes

Max radio capacity 100 Mbps 500Mbps 1Gbps using 2+0/XPIC

Multi-radio support - Yes

# of Ethernet interfaces 5 x FE RJ-45 5 x FE RJ-45+2 x GE combo (RJ-45/SFP)

Full Carrier Ethernet switching feature-set including ring protection Yes Yes

# of E1/T1 integrated IDU interfaces option 16 E1, None 16 E1, 16T1, None


# of E1/T1s per radio carrier 44 E1s 75 E1s / 84 T1s

T-Card slot (additional 16 E1/T1 interfaces or STM1/OC3 Mux) - Yes

Nodal/XC/SNCP support Yes Yes

Sync unit option Yes Yes

V.11/RS232 User Channel option - 2 x Async V.11/RS232 or1 x Sync V.11

Outdoor Enclosures – Solution Benefits

Full Outdoor solution:

• Dust and weather proof

• Compact size reduces the cost of leasing or purchasing rack space.

• Ideal for Greenfield areas, at solar-powered sites, and at repeater sites adjacent to highways.

• One-man installation and shorter cabling reduce installation costs.


• Environment-friendly: Greener deployments, saving on power and air-conditioning costs.

20

Page 38

6/13/2010

11

Typical IP10

Higher Spectral-EfficiencyWhat’s in it for The Operator?

Microwave Radio Microwave Radio

Required Capacity155‐200Mbps

TWO radio linksor

56MHz channel bandwidth

ONE radio link using

28MHz channel bandwidth

Required Capacity70‐100Mbps

28MHzChannel Bandwidth

14MHzChannel Bandwidth


The operator saves CAPEX and free‐up valuable frequency resources

21

Higher Spectral-Efficiency is not enough…

Radio Type Ant. Diameter Length Modulation Capacity

Typical System Gain 1.80 m 30 Km 16QAM 32 x E1s

Typical System Gain 1.80 m 21 Km 128QAM STM‐1/OC‐3

Typical System Gain 3.00 m 30 Km 128QAM STM‐1/OC‐3

High System Gain 1.80 m 30 km 128QAM STM‐1/OC‐3High System Gain


should always be coupled with

Spectral Efficiency

System Gain

Page 39

6/13/2010

12

Ceragon’s Management Overview


IP-10 FibeAir

“Tree Topology”


Page 40

6/13/2010

13

Thank You!Thank [email protected]

Page 41

Advanced Operation & Maintenance Course

1


FibeAir IP-10 G-Series

Front Panel Description

®


Front Panel Overview

2

Let’s go over the front panel connections of the IP-10 G-Series

We shall explain them one by one, left to right…

GUI Example)

Page 42


2


CLI – Serial Connection

3

DB9 Craft Line Interface (CLI)

Baud: 115200

Data bits: 8

Parity: None

Stop bits: 1

Flow Control: None


EOW – Easy Comm. Via Radio

4

Engineering Order Wire –

To communicate with your colleague on the

other side of the radio link, simply connect

here your headset

Page 43


3


External Alarms

5

DB9 Dry Contact External Alarms –

The IP-10 supports 5 input alarms and a single output alarm

The input alarms are configurable according to:

1) Intermediate, 2) Critical, 3) Major, 4) Minor and 5) Warning

The output alarm is configured according to predefined categories


LED Indications

6

LINK: GREEN – radio link is operational

ORANGE - minor BER alarm on radio

RED – Loss of signal, major BER alarm on radio

IDU: GREEN – IDU functions ok

ORANGE - fan failure

RED – Alarm on IDU (all severities)

RFU: GREEN – RFU functions ok

ORANGE – Loss of communication (IDU-RFU)

RED – ODU Failure

Page 44


4


LED Indications

7

PROT: Main unit – GREEN (when there no alarms)

STBY unit: YELLOW (when there no alarms)

ORANGE – Forced switch, Protection lock

RED – physical errors (no cable, cable failure)

OFF – Protection is disabled, or not supported on

device

RMT: GREEN – remote unit OK (no alarms)

ORANGE – minor alarm on remote unit

RED – major alarm on remote unit


User Channels (1)

8

Two software-selectable user channels (RJ-45):

A single synchronous channel OR two asynchronous channels

Each asynchronous channel will make use of its own RJ-45 external

interface

The synchronous channel mode will make use of both interfaces

(acting as a single interface)

Page 45


5


User Channels (2)

9

Modes of operation:

• V.11 Asynchronous (9600bps)

• RS-232 Asynchronous (9600bps)

• V.11 Synchronous Co-Directional (64Kbps)

• V.11 Synchronous Contra Directional (64Kbps)


User Channels (3)

10

Allowed configurations:

• Two RS-232 Asynchronous UCs (default)

• Two V.11 Asynchronous UCs

• One RS-232 Asynchronous UC, and one V.11 Asynchronous UC

• One V.11 Synchronous Co-Directional

• One V.11 Synchronous Contra Directional UC

> All settings are copied to Mate when working in Protected mode

Page 46


6


Protection Port

11

Protection Port (only for standalone units) –

Protect your Main unit with a STBY unit

Protection ports on both units deliver the proprietary protocol to

support automatic or manual switchover

The FE protection port is static (only used for protection, not traffic). Its switching is performed

electrically. If the unit is a stand-alone, an external connection is made through the front panel. If the

unit is connected to a backplane, the connection is through the backplane, while the front panel port

is unused.


T-Cards (Add-on Mezzanines)

12

Field upgradeable modules (T-Cards):

• 16 x E1 T-Card (32 total per unit)

• DS1 T-Card

• STM1/OC3 MUX T-Card

Page 47


7


T-Cards (Add-on Mezzanines)

13

An optional STM-1 interface card can be inserted in a dedicated slot in the

system; the card can transmit and receive up to 63 E1s in a channelized

STM-1 signal.

The supported mapping is VC4 only:

VC-12->TU-12->TUG-2->TUG-3->VC-4->AU-4->AUG

The STM-1 T-card is only supported in unprotected main units or in

unprotected stand-alone IDUs


GbE Ports

14

Two GbE ports, each port with 2 physical interfaces:

Port #1: optical (SFP transceiver) or electrical

Port #2: optical (SFP transceiver) or electrical

� GbE ports support QoS as in IP-10 (scheduler, policers, shaper, classifiers)

Port #1Port #2

Page 48


8


FE Ports

15

5 FE ports:

Port 3: Data

Port 4: Data or WSC (2 Mbps Wayside Channel)

Port 5,6 &7: Data or local management

� All ports support QoS as in IP-10 (scheduler, policers, shaper, classifiers)


Radio and misc.

16

The Radio port is the switch’s 8th port (same as in IP-10)

In addition –

• Grounding

• -48vdc Power Connector

• Fan Drawer

Page 49


9


XC using a Shelf Configuration

17

XC operation is implemented using two-unit backplanes, which

provide the interconnectivity.

Up to three backplanes, consisting of six IDUs, can be stacked to

provide an expandable system


XC using a Shelf Configuration

18

All IDUs that operate within

the XC system have

identical hardware, and act

as stand-alone units.

The 2 lower units can be configured as Main units.

The role an IDU plays is determined during installation by its position in the

traffic interconnection topology

Page 50


10


Thank You !

[email protected]

Page 51

Advanced Operation & Maintenance Course1

FibeAir IP‐10 G‐Series®


Installation

General

If installation requires CFG file upload & download and / or SW file upload & down -

1. Make sure FTP Server is installed on your PC2. FTP is configured (RD/WR permissions)3. Latest SW version is available (FTP root directory)

FTP installation guide


is available at Training.Ceragon.Com:

see Modules / Installation

Page 52


Agenda

• Site Requirements• Packing & Transportation• Unpacking• Required Toolsq• IDU Dimensions• Installing standalone IDU in a 19” Rack• Installing Nodal Enclosures in a 19” Rack• Preparing the IDU for a Shelf installation• Installing the IDU in a Shelf • Installing a Blank Panel IDU in a Shelf• Installing a T-Card into an IDU• Grounding the IDU


• Lightning Protection• Power General Requirements• Installing the IDU-ODU IF cable

Site Requirements

• IDU must be located indoors

• The environment temperature must be between -5 C and +45 C.

•Easily accessible, but only by authorized personnel.

• Available power source of -48 VDC, and the site must comply with National Electric Code (NEC) standards.

• Available management connection (Ethernet or dial-up).• IDU-ODU connection (IF cable): no more than 300m


Page 53


Site Requirements

Heat Dissipation:

The IP-10 IDU overall heat dissipation is 25W max (~85 BTU/h). The ODU heat dissipation is 100W max.p

Antenna Location:

As with any type of construction, a local permit may be required before installing an antenna. It is the owner’s responsibility to obtain any and all permits.


Packing & Transportation

The equipment is packed at the factory, and sealed moisture-absorbing bags are inserted.

The equipment is prepared for public transportation. The cargo must be kept dry during transportation.

Keep items in their original boxes till they reach their final destination.

If intermediate storage is required, the packed equipment must be stored in dry and cool conditions and out of direct sunlight

Wh ki


When unpacking –Check the packing lists, and ensure that the correct part numbers and quantities of components arrived.

Page 54


Unpacking

A single FibeAir system (1+0) is shipped in 5 crates.

Upon delivery, make sure that the following items are included:

• Two indoor units and accessories• Two outdoor units• For 13-38 GHz systems, verify that there is a high RFU and low RFU.• One CD with a management user guide.


Unpack the contents and check for damaged or missing parts. If any part is damaged or missing, contact your local distributor.

Required Tools

The following tools are required to install the IDU:

• Philips screwdriver #2 (for mounting the IDU to the rack and grounding screw)

• Flathead small screwdriver (for PSU connector)

• Sharp cutting knife (for wire stripping)

• Crimping tool for ground cable lug crimping (optional: if alternative grounding cable is used)


Setting up Management will require -

• ETH cable (for setting management)• Serial Cable (for setting management)

Page 55


Specifications

Connector spec, cable spec & interface pin layout can be found in our complete PDF installation guide

installation guides available at Training.Ceragon.Com:

M d l / I t ll ti


see Modules / Installation

IDU Dimensions


42.60mm

Page 56


Installing standalone IDU in a 19” Rack

As shown in the illustration, four screws, supplied with the installation kit are used to secure the IDU to the rackinstallation kit, are used to secure the IDU to the rack.


Installing Nodal Enclosures in a 19” Rack


Page 57



Before you install the enclosures –

Plan carefully the required space within the rack !

Should you need to install 3 enclosures – prepare at least 10Us (6Us for enclosures + 2Us free space for maneuvering above and below

shelves)Main Enclosure


Start the installation process from bottom to top, e.g. – Mainenclosure should be installed first at the bottom of your rack space


Step #1:Install the IP-10 Main enclosure in the 19 inch rack using 4 screws.


Page 58




Step #2:Slide down the 2nd extension enclosure. Male connector should plug in smoothly into the Main enclosure.




Step #2:Slide down the 2nd extension enclosure. Male connector should plug in smoothly into the Main enclosure.

Step #3:


Step #3:Slide down the 2nd extension enclosure. Male connector should be plugged in smoothly into the Main enclosure.

Page 59



Step #4:Secure the 2nd extension into the Main enclosure. Use the built-in screw.

Mount the 2nd extension into the rack using the 4 screws



Step #4:Secure the 2nd extension into the Main enclosure. Use the built-in screw.

Mount the 2nd extension into the rack using the 4 screws

Step #5:Add the 3rd extension when needed


when needed

Page 60


Preparing the IDU for a Shelf installation

Remove the two 19" brackets mounted on the IP-10 IDU by unscrewing the 3 screws at each side.


Installing the IDU in a Shelf

Slide the IP-10 IDU into the enclosure and tighten it using 2 screws. Repeat this step in accordance with the configuration.

IDU insertion & extraction should NOT be under power


Page 61


Installing a Blank Panel IDU in a Shelf

Slide the IP-10 blank panel into the enclosure, and tighten it using 2 screws.


Installing a T-Card into an IDU

Remove the IP-10 T-Card blank panel from the IDU, by releasing the 2 side screws.


Page 62


Installing a T-Card into an IDU

Insert the IP-10 T-Card panel and tighten it using the 2 side screws.


Grounding the IDU


Single Point Stud

Grounding Wire

Page 63


Grounding the IDU

• The IDU is suitable for installation in a Common Bonding Network (CBN).

• Only copper wire should be used.

• The wire must be at least 14 AWG.

• Connector and connection surfaces must be plated. Bare conductors must be coated with antioxidant before crimp connections are made to the screws.

• FibeAir provides a ground for each IDU, via a one-hole mounted lug onto a single-point stud.

Th t d t b i t ll d i UL li t d i t t i l d t t


• The stud must be installed using a UL-listed ring tongue terminal, and two star washers for anti-rotation.

Lightning Protection

For antenna ports, lightning protection is used that does not permit transients of a greater magnitude than the following:magnitude than the following:

• Open Circuit: 1.2-50us 600V• Short Circuit: 8-20us 300A

The ampacity of the conductor connecting the IDU frame to the DC return conductor is equal to or greater than, the ampacity of the associated DC return conductor.


Page 64


Power General Requirements

1. A readily accessible Listed branch circuit over-current protective device, rated 15 A, must be incorporated in the building wiring.

2. This equipment is designed to permit connection between the earthed conductor of the DC supply circuit and the earthing conductor at the equipment.

3. The equipment shall be connected to a properly grounded supply system

4. The DC supply system is to be local, i.e. within the same premises as the equipment


5. A disconnect device is not allowed in the grounded circuit between the DC supply source and the frame/grounded circuit connection.

Power Requirements

When selecting a power source, the following must be considered:

• DC power can be from -40.5 VDC to -60 VDC.

• Recommended: Availability of a UPS (Uninterrupted Power Source), battery backup, and emergency power generator.

• Whether or not the power source provides constant power (i.e., power is secured on weekends or is shut off frequently and consistently).

• The power supply must have grounding points on the AC and DC sides.

Th l GND t b t d t th iti l i th IDU


• The user power supply GND must be connected to the positive pole in the IDU power supply.

• Any other connection may cause damage to the system!

Page 65


Power Requirements

Important –

Make sure to use a circuit breaker to protect the circuit from damage by short or overload.


Installing the IDU-ODU IF cable

Route the IF Coax Cable from the IDU to the ODU/RFU and terminate it with N-type male connectors.

Note: Make sure you fasten the cable along the ladder!

Make sure that the inner pin of the connector does not exceed the edge of the connector.

The cable should have a maximum attenuation of 30 dB at 350 MHz.


Page 66


Thank You [email protected]


[email protected]

Page 67

3/14/2010

1

RFU‐C & Mediation Devices


The Most Comprehensive Portfolio

Carrier Ethernet

FibeAir® Family

RFUs EMS & NMS

Multi-Service

Carrier EthernetRFUs6-38 GHz

EMS & NMS3200T

IP-10 640P

RFU-C

RFU-HP

PolyView (NMS)

CeraView (EMS)

IP-MAX2

IP-10 IP-MAX2


TDM1500R/1500P 3200T

RFU-P, RFU-SP

CeraView (EMS)

Page 68

3/14/2010

2

IDU – RFU Compatibility

RFU-C IP-10

RFU-HP

RFU-P, RFU-SP1500R


RFU-SP

IP-IP-MAX2

640P

1500P

3

IDU – IDU Compatibility Across Link

IP-10

1500R1500R

IP 10 IP-10IP-10

1500R

IP-10IP-MAX/IP-MAX2

1500P


Must Match IDU Type Across a Link

1500R chassis Cannot House 1500P IDC and IDMs

1500P chassis Cannot House 1500R IDC and IDMs

4

Page 69

3/14/2010

3

RFU-C direct mount configurations

1+0 direct


RFU-C direct mount configurations

1+1 direct


Page 70

3/14/2010

4

RFU-C remote mount configurations

1+0 remote


RFU-C remote mount configurations

1+1 remote


Page 71

3/14/2010

5

RFU-C antenna adaptors

• Adaptors for RFU-P direct antenna mount

• Adaptors for NSN Flexi Hopper direct antenna mount

• Adaptors for Ericsson R1A 23GHz direct antenna mount

• Remote adaptors and configurations


RFU-C to NSN antenna


Page 72

3/14/2010

6

RFU-C to Ericsson antenna (R1A 23GHz)


• Connect the headset to AGC monitor BNC/TNC connector on ODU

Connect Digital Volt Meter (DVM) to the AGC BNC connector

Antenna Alignment (1)

• Connect Digital Volt Meter (DVM) to the AGC BNC connector

• Align the antenna until voltage reading is achieved (1.2 to 1.7Vdc)

• Repeat antenna alignment at each end until the minimum dc voltage is

achieved


• 1.30vdc = -30dBm

• 1.45vdc = -45dBm

• 1.60vdc = -60dBm

• etc

12

Page 73

3/14/2010

7

• Compare achieved RX level to

Antenna Alignment (2)

• Compare achieved RX level to

calculated RX level

• Keep aligning until the achieved

level is up to 4 dB away from the

calculated received signal level

• If voltage reading is more than 4

dB away or higher than 1.7vdc,


dB away or higher than 1.7vdc,

re-align antenna to remote site

13



Thank You !g@ g

14

Page 74


FibeAir IP‐10 G‐Series®


Setting Management

Agenda

• Getting started• General notes• General commands• Command historyy• Reading current IP• Setting new IP• Connecting PC to IDU• Troubleshooting• Factory Defaults


Page 75


Getting started

Verify that physical installation is successfully completed:

• IDU is properly mounted in a shelf / rack• Power + GND• IF Cable between IDU and ODU

Connect a PC to the Terminal connector and launch a serial application

• Baud: 115200

• Data bits: 8

• Parity: None

St bit 1

You may use any Serial Application such as Hyper Terminal PuTTY TeraTerm


• Stop bits: 1

• Flow Control: None

Log on using (admin/admin) for user name and password.Now, you should be able to see the IP-10 CLI Prompt

Terminal, PuTTY, TeraTermetc…

General notes on CLI

IP-10:/>

Note that the > sign indicates your current directory in the CLI tree

Most of the CLI commands are based on GET/SET conceptSome commands may require a different syntax


Ceragon strongly recommends to use CLI only for setting management IP address when current IP is unknown

All functions & features can be configured faster and easier using the WEB based EMS

4

Page 76


IP-10:/ >?IP-10:/lsIP-10:/lspIP-10:/ > exit

General Commands

/ >

IP-10:/ > cdIP-10:/ > cd ..

Type ? (question mark) to list helpful commandsType ls to list your current directoryType lsp to available commands of current directory


Type lsp to available commands of current directory

Type exit to terminate the session

Type cd to change directory Type cd .. to return to root directory

5

Use the arrow keys to navigate through recent commands

Command History

commands

Use the TAB key to auto-complete a syntax


Page 77


To read current IP type the following:

IP-10:/>cd management/networking/ip-address/

Reading current IP

IP-10:/ management/networking/ip-address>

IP-10:/ management/networking/ip-address>get ip-address

Note that the prompt has changed. Now, type get ip-address:

Upon completion the current IP will be displayed followed by the new


IP-10:/ management/networking/ip-address>get ip-address192.168.1.1IP-10:/ management/networking/ip-address>

Upon completion, the current IP will be displayed, followed by the new prompt:

7

Now, let us set a new IP for the MNG:

We assume the required IP is 192.168.1.144

Setting new IP

Type set ip-address 192.168.1.144

IP-10:/ management/networking/ip-address>set ip-address 192.168.1.144

You may lose remote management connection to the unit if this value

Upon completion, you will be prompt:


You may lose remote management connection to the unit if this value is changed incorrectly.Are you sure? (yes/no):

Type yes and connect the IDU to your network / PC

8

Page 78


1. Connect your EMS/NMS to the IDU (port 7) with ETH CAT.5 cable

2. Verify that your PC’s IP is in the same subnet

3 Make sure Link is up

Connecting IDU to EMS

3. Make sure Link is up

4. PING the IDU

5. Launch a WEB browser with the URL set as the IDU’s IP


In case PC cannot PING IDU –

1. Check your ETH cable – it might not be inserted properly (broken PIN)2. Verify the management port is enabled in the EMS General/Management

configuration

Management Troubleshooting

3. Make sure you connect to a management-enabled port (7, 6 or 5)4. Verify right LED is ON (see below)5. Verify your PC is in the same subnet as the IDU6. In case your IDU is connected to a router: set the IDU’s Default GW = Router IP7. In case your PC is connected to several IDUs (through switch/hub) – make sure

every IDU has a unique IP

When ON (Green) = Port is set to ManagementWhen OFF = Port is set to Data


Page 79


Going back to factory defaults can be done with EMS or CLIIn case you need to set factory defaults with CLI type the following -

Back to factory defaults

IP-10:/> cd management/mng-services/cfg-service

IP-10:/management/mng-services/cfg-service>set-to-default

In the new directory type the following:




[email protected]

Page 80

4/16/2010

1

FibeAir IP-10 G-Series®


EMS Performance Monitoring

Agenda

EMS – General Information

Faults:Faults:• Current Alarms• Event Log

PM & Counters:• Remote Monitoring • TDM Trails• TDM interfaces


TDM interfaces• Radio (RSL, TSL, MRMC and MSE)• Radio TDM• Radio ETH

Page 81

4/16/2010

2

EMS - General

Easy, user friendly GUI

No need to install an application – WEB Based software

No need to upgrade your EMS application – embedded in the IDU SW

No need for strong working station – simple PC is sufficient

(For maintenance issues FTP Server is required)


Easy access – simply type the IP address of the IDU on your web page

Supports all IDU versions and configurations

EMS Main View

Access application via IP address


User friendly navigation menu

Page 82

4/16/2010

3

EMS Main View

Graphical “MENU”: Click to configure


EMS Main View

Protection Status Display &


Protection Status Display & Quick Access Icons

Page 83

4/16/2010

4

EMS Main View

In this example slot #1 and slot #2 are configured to support 1+1 ProtectionSlot #1 is selected and in Active mode.


Black Rectangular to indicate selected slot for configuration

EMS Main View

When the user selects Slot 2 the GUI updates automatically


Page 84

4/16/2010

5

Faults - CAS

The CAS window shows collapsed list of alarms

By expanding a line we can see additional information:

• Probable cause• Corrective Actions


Faults – Event Log

The Event Log shows max. 200 lines of eventsWhen Event #201 occurs, Event #1 is erased and #201 is logged as #200.


Page 85

4/16/2010

6

Available PM Statistics - Radio

TDM

TDM PM in Radio (allocated E1s)

(16 E1s)

ETH PM (Data + In-Band):1. Aggregated Errors2. Throughput3. Capacity4. Radio Link Utilization5. RMON standard is

implemented as well to


pprovide detailed data

Radio PM:1. RSL2. MSE3. MRMC (ACM)4. Aggregate

Available PM Statistics – Line Interfaces

• STM-1 interface facing customer equipment• TDM interfaces facing customer equipmentg q p• End-to-End Trails


Page 86

4/16/2010

7

Clearing previous data

To erase all IDU PM data, click the CLEAR button -


ETH PM – RMON

The system supports Ethernet statistics counters (RMON) display (depends on port availability). The counters are designed to support:

• RFC 2819 – RMON MIB.• RFC 2665 – Ethernet-like MIB.• RFC 2233 – MIB II.• RFC 1493 – Bridge MIB.


Page 87

4/16/2010

8

PM – TDM Trails – In Detail

Report Interval:

Display 15 minutes intervals or single Daily interval (24 hours)

The number of trails in the list is derived from radio link capacity (default license = 10Mbps)

Information can be displayed as a graph


PM – RMON – Special Registers

RMON register / Counter Description

Undersize frames received Frames shorter than 64 bytes

Oversize frames received Frames longer than 1632 bytesOversize frames received Frames longer than 1632 bytes

Jabber frames receivedTotal frames received with a length of more than 1632 bytes, but with an invalid FCS

Fragments frames receivedTotal frames received with a length of less than 64bytes, and an invalid FCS

Rx error frames received Total frames received with Phy‐error

FCS frames receivedTotal frames received with CRC error, not countered in"Fragments", "Jabber" or "Rx error" counters


Fragments , Jabber or Rx error counters

In Discard FramesCounts good frames that cannot be forwarded due tolack of buffer memory

In Filtered FramesCounts good frames that were filtered due to egressswitch VLAN policy rules

Pause frames received Number of flow‐control pause frames received

16

Page 88

4/16/2010

9

Troubleshooting with RMON: Filtering Example

Radio port is a member of VID 100

T AA Tagging

Radio port is a member of VID 100

T No membership

Site BSite A

Untagged FramesTagged with default VID 100

Access port with default VID = 300


Site B Ingress port (Radio) receives the frame and checks the Egress port VID membership

Egress port default VID is 300, therefore frame is filtered by the remote Radio port

Troubleshooting with RMON: Oversized frames

T AT T

Site BSite A

Tagged Frames with frame size > 1632 bytes


When ingress frames exceed the maximum frame size, RMON counter “Oversized frames received” is updated accordingly

Page 89

4/16/2010

10

Troubleshooting with RMON: Discarding Example

T AT T

Site BSite A

Ingress traffic does not comply to Policer rules


Discarding Examples:

Ingress rate > Rate LimiterIngress frames do not qualify to Policer rules

Troubleshooting with RMON: Monitoring specific traffic types

Site BSite A

Rate Limiter

Video streams are generally transmitted over UDP with multicast addresses

T T

Monitor

Rate Limiter


To monitor traffic, check out the Multicast Frames Received register

To limit MC traffic, assign a Policer with a UDP & MC CIR rules

Page 90

4/16/2010

11


Errored Second (ES):

A one-second period with one or more errored blocks or at least one defect



Severely Errored Second (SES):

A one-second period, which contains 30% errored blocks or at least one defectdefect.

SES is a subset of ES.


Page 91

4/16/2010

12


A period of unavailable time begins at the onset of 10 consecutive Severely Errored Second (SES) events. These 10 seconds are considered to be part of unavailable time.

A new period of available time begins at the onset of 10 consecutive non-SES events. These 10 seconds are considered to be part of available time.



Background Block Error (BBE):

An errored block not occurring as part of a SES.


Page 92

4/16/2010

13


Number of Switches (only relevant for Protected SNCP Trails):

The number of times the IP-10 switched from Primary Path to Secondary Path and vice versa (per 15min or 24hrs interval)and vice versa (per 15min or 24hrs interval)



Active Path Seconds (only relevant for Protected SNCP Trails):

The number of times seconds the Active Path was available


Page 93

4/16/2010

14


Integrity:

Indicates whether information is reliable for analysis (ticked) or not

For example – if clock was changed or system was restarted during this interval then information is not reliable


PM – E1 / DS-1 (Radio PM)

This PM data relates to the TDM Line Interfaces.


Page 94

4/16/2010

15

PM – E1 / DS-1 (Radio PM)

Here we can analyze TDM PM through the radio link


PM – STM-1 Interface

This PM data relates to the STM-1 Line Interface.


Page 95

4/16/2010

16

PM – Radio

Signal Level – RSL & TSL analysis

Allows setting RSL & TSL thresholdsEMS will notify when signal exceeds THSLD

>> Easier maintenance

Aggregated radio traffic analysis

MRMC – PM related to ACM:


• Associated Script• Available Bit rate• Available Radio VCs

MSE analysis

31

PM – Radio – Signal Level - Example


- 40dBm = Nominal RSL for an operational Link

Level 1: 25 secLevel 2: 15 sec

900 sec = 15min Interval

Page 96

4/16/2010

17

PM – Radio – Signal Level - Example

Using graphical display of the THSLD analysis allows us easier examination of the RSL & TSL state throughout certain period of time

-40

-50

RSL


-68

-99 T [sec]10 5 10

33

PM – Radio - Aggregate

Aggregated radio traffic analysis


Page 97

4/16/2010

18

PM – Radio - MRMC

The information displayed in this page is derived from the license and script assigned to the radio.

When ACM is enabled and active as link quality degrades or improves theWhen ACM is enabled and active, as link quality degrades or improves, the information is updated accordingly.


PM – Radio - MSE

The information displayed in this page is derived from the license and script assigned to the radio. When link quality degrades or improves, the MSE reading is updated accordingly. Differences of 3dB trigger ACM modulation changing.

Threshold can be configured as well for easier maintenance.


Page 98

4/16/2010

19

PM – Ethernet

ETH Traffic + Threshold settings:

Frame Error Rate –Frame error rate (%) measured on radio-EthernetFrame error rate (%) measured on radio Ethernet interface

Throughput – data bits measured on radio-Ethernet interface

Capacity - overall Ethernet bits rate, data & overhead, measured on radio-Ethernet interface


Utilization - (Actual Ethernet throughput, relative to the potential Ethernet throughput of the radio, excluding TDM channels).

Utilization (%) is displayed as one of five bins: 0-20%, 20-40%, 40-60%, 60-80%, 80-100%

37

Throughput / Capacity / Utilization

To better understand these terms, we shall examine the Ethernet tagged frame full structure:

A frame viewed on the actual physical wire would show Preamble and Start Frame Delimiter, in addition to the other data (required by the physical hardware).

Pre. SFD DA SA VLAN ETH Type / Length

Payload + Padding

CRC InterframeGap

, ( q y p y )

However, these bits are stripped away at OSI Layer 1 by the Ethernet adapter before being passed on to the OSI Layer 2 which is where data is detected.


7 octets 1 octet 6 octets 6 octets 4 octets 2 octets 46‐1500 octets

4 octets 12 octets

Data Rate: min. 64 octets – max. 1522 octets

Physical wire rate: min. 84 octets – max. 1542 octets

Page 99

4/16/2010

20


Pre. SFD DA SA VLAN ETH Type / Length

Payload + Padding

CRC InterframeGap

7 octets 1 octet 6 octets 6 octets 4 octets 2 octets 46‐1500 octets

4 octets 12 octets

Data Rate: min. 64 octets – max. 1522 octets

Physical wire rate: min. 84 octets – max. 1542 octets

In case we use a 64 bytes frame:


Throughput (Data rate) = ~ 77% of physical transmitted rate (64/84=0.77)Stripped bits = ~ 23% of physical transmitted rate (20/84=0.23)

Hence, when we transmit 100Mbps, the actual throughput would be 77 Mbps


Throughput = 77 Mbps

Radio Capacity = (license) = 400Mbps

Transmitted rate = Capacity = Received frame rate


100 Mbps = 100 Mbps

Utilization = Throughput = 77 = 20 %Radio Capacity 400

Page 100

4/16/2010

21

PM – Ethernet

Ethernet throughput & Capacity PMs are measured by accumulating

the number of Ethernet octets every secondthe number of Ethernet octets every second

Accurate analysis requires accumulating a full interval (15min/24hrs)


Thank You !training@ceragon com

42

[email protected]

Page 101

6/1/2010

1


EMS General Configuration

Agenda

In this module we shall explain

the following features as they

appear on the EMS navigation


Menu

Page 102

6/1/2010

2

Unit Parameters – Step # 1

Configure specific information that may assist you later


assist you later

Such info will help you locate your site easier and faster



VDC reading

Page 103

6/1/2010

3



Celsius (metric) or Fahrenheit (Imperial)


By default the time & date are derived from the operating system clock

User may set new values

These settings are also used for NTP


used for NTP connection (later explained)

Page 104

6/1/2010

4


IDU Serial number is important when you submit your requestsubmit your request for a License upgrade

When you complete configuring all settings, click Apply.


Versions


This page shows the complete package of IDU and ODU software components

Page 105

6/1/2010

5

Versions

Let’s explore this example:

• The IDU running SW is displayed in the aidu line and currently it is 3 0 92


• The IDU running SW is displayed in the aidu line and currently it is 3.0.92

• A new SW was downloaded sometime in the past (3.0.97)

• The IDU was not upgraded yet

Versions – RFU files

Th IDU h ld ll th SW fil f ll th


The IDU holds all the SW files for all the components (IDU + ODU)

You can see here the different files per ODU type

10

Page 106

6/1/2010

6

External Alarms – Collapsed Input Alarm Config.


Dry Contact Alarms (DB-9):

5 Inputs

1 Output

External Alarms – Expended Input Alarm Config.


Page 107

6/1/2010

7

External Alarms – Configuring the Output Alarm

‘Group’ of alarms will trigger the external alarm Output.

Communication – Alarms related to traffic: Radio / Ethernet line / TDM line

Q lit f S i W d t h ifi l f Q SQuality of Service – We do not have specific alarms of QoS

Processing – Alarms related to SW: Configuration / Resets / corrupted files

Equipment – Alarms related to: HW / FAN / RFU mute / Power Supply / Inventory.

Environmental – Alarms of ‘extreme temperature’.

All Groups.


Test mode – manual switch.

Management – Network Properties

Here you can set the Network Properties of the IDUthe IDU

This is the switch MAC address


If your link is up – you should be able to see the other end’s IP

Page 108

6/1/2010

8

Management – Local Properties (Out of band)

The IDU has 3 ports for local management: Port 7, Port 6 and Port 5.


You may enable none or up to 3 ports:

Number of ports =3 Port 7, Port 6, Port 5Number of ports =2 Port 7, Port 6Number of ports =1 Port 7Number of ports =0 NO LOCAL MANAGEMENT !!!

Management – In Band Properties

In Band Management requires unique VLAN ID

This helps separating MNG traffic from other services


In Band MNG packets are transferred via the radio link

When the link is down, management is down as well.

Page 109

6/1/2010

9

Management – Port Properties

These parameters allow you setting the

t it


management capacity and port properties

Trap Configuration (OSS / NMS / Northbound)

To manage the IDU with OSS /To manage the IDU with OSS / NMS, you will need to configure the IP address of the OSS Server

You may configure up to 4 Servers (Trap Destinations)


Page 110

6/1/2010

10

Licensing – Default License

“Demo” license can be enabled on-site, it expires after 60 days (operational time)

Licenses are generated per IDU S/N upon request (capacity / ACM / switch mode)


License upgrade requires system reset.

Licensing – Demo License Enabled

Demo License allows you full

evaluation of the IDU

functionality, features and

capacities


Page 111

6/1/2010

11

NTP Client Properties

• Enable / Disable

• Type NTP Server IP address

• Expect IDU to lock on NTP Server’s clock

• Expected Status:

1. If locked, it returns the IP address of the server it is locked on.

2. “Local” – if the NTP client is locked to the local element’s real-time clock


3. “NA” - if not synchronized with any clock (valid only when Admin is set toDisable).

The feature supports “Time Offset” and “Daylight Saving Time”.“Time Offset” and “Daylight Saving Time” can be configured via WEB (“UnitInformation” page) or via CLI: /management/mng-services/time-service>

NTP Properties


Page 112

6/1/2010

12

NTP Properties

When using NTP with external protection 1+1, both “Active” and “Standby”

nits sho ld be locked independentl on the “NTP ser er” and reportunits should be locked independently on the “NTP server”, and report

independently their “Sync” status.

Time & Date are not copied from the “Active” unit to the “Standby” unit

When using NTP in a shelf configuration all units in the shelf (including


When using NTP in a shelf configuration, all units in the shelf (including

standby main units) are automatically synchronized to the active main unit’s

clock.

IP Table


Here you can manually set your neighbor’s network properties

Page 113

6/1/2010

13

SNMP

• V1• V3

• No security• Authentication• Authentication privacy

• SHA


• MD5• No Authentication

All ODU

All ODU Disabled All ODU Enabled

This feature is used to feed the integrated fans of the Outdoor Enclosure

When enabled, the Ext. Alarms connector is modified to provide the required power feed.


Page 114

6/1/2010

14


27

[email protected]

Page 115

6/13/2010

1


EMS General Configuration

Agenda

In this module we shall explain

the following features as they

appear on the EMS navigation


Menu

Page 116

6/13/2010

2


Configure specific information that may assist you later


assist you later

Such info will help you locate your site easier and faster



VDC reading

Page 117

6/13/2010

3



Celsius (metric) or Fahrenheit (Imperial)


By default the time & date are derived from the operating system clock

User may set new values

These settings are also used for NTP


used for NTP connection (later explained)

Page 118

6/13/2010

4


IDU Serial number is important when you submit your requestsubmit your request for a License upgrade

When you complete configuring all settings, click Apply.


Versions


This page shows the complete package of IDU and ODU software components

Page 119

6/13/2010

5

Versions

Let’s explore this example:

• The IDU running SW is displayed in the aidu line and currently it is 3 0 92


• The IDU running SW is displayed in the aidu line and currently it is 3.0.92

• A new SW was downloaded sometime in the past (3.0.97)

• The IDU was not upgraded yet

Versions – RFU files

Th IDU h ld ll th SW fil f ll th


The IDU holds all the SW files for all the components (IDU + ODU)

You can see here the different files per ODU type

10

Page 120

6/13/2010

6

External Alarms – Collapsed Input Alarm Config.


Dry Contact Alarms (DB-9):

5 Inputs

1 Output

External Alarms – Expended Input Alarm Config.


Page 121

6/13/2010

7

External Alarms – Configuring the Output Alarm

‘Group’ of alarms will trigger the external alarm Output.

Communication – Alarms related to traffic: Radio / Ethernet line / TDM line

Q lit f S i W d t h ifi l f Q SQuality of Service – We do not have specific alarms of QoS

Processing – Alarms related to SW: Configuration / Resets / corrupted files

Equipment – Alarms related to: HW / FAN / RFU mute / Power Supply / Inventory.

Environmental – Alarms of ‘extreme temperature’.

All Groups.


Test mode – manual switch.

Management – Network Properties

Here you can set the Network Properties of the IDUthe IDU

This is the switch MAC address


If your link is up – you should be able to see the other end’s IP

Page 122

6/13/2010

8

Management – Local Properties (Out of band)

The IDU has 3 ports for local management: Port 7, Port 6 and Port 5.


You may enable none or up to 3 ports:

Number of ports =3 Port 7, Port 6, Port 5Number of ports =2 Port 7, Port 6Number of ports =1 Port 7Number of ports =0 NO LOCAL MANAGEMENT !!!

Management – In Band Properties

In Band Management requires unique VLAN ID

This helps separating MNG traffic from other services


In Band MNG packets are transferred via the radio link

When the link is down, management is down as well.

Page 123

6/13/2010

9

Management – Port Properties

These parameters allow you setting the

t it


management capacity and port properties

Trap Configuration (OSS / NMS / Northbound)

To manage the IDU with OSS /To manage the IDU with OSS / NMS, you will need to configure the IP address of the OSS Server

You may configure up to 4 Servers (Trap Destinations)


Page 124

6/13/2010

10

Licensing – Default License

“Demo” license can be enabled on-site, it expires after 60 days (operational time)

Licenses are generated per IDU S/N upon request (capacity / ACM / switch mode)


License upgrade requires system reset.

Licensing – Demo License Enabled

Demo License allows you full

evaluation of the IDU

functionality, features and

capacities


Page 125

6/13/2010

11

NTP Client Properties

• Enable / Disable

• Type NTP Server IP address

• Expect IDU to lock on NTP Server’s clock

• Expected Status:

1. If locked, it returns the IP address of the server it is locked on.

2. “Local” – if the NTP client is locked to the local element’s real-time clock


3. “NA” - if not synchronized with any clock (valid only when Admin is set toDisable).

The feature supports “Time Offset” and “Daylight Saving Time”.“Time Offset” and “Daylight Saving Time” can be configured via WEB (“UnitInformation” page) or via CLI: /management/mng-services/time-service>

NTP Properties


Page 126

6/13/2010

12

NTP Properties

When using NTP with external protection 1+1, both “Active” and “Standby”

nits sho ld be locked independentl on the “NTP ser er” and reportunits should be locked independently on the “NTP server”, and report

independently their “Sync” status.

Time & Date are not copied from the “Active” unit to the “Standby” unit

When using NTP in a shelf configuration all units in the shelf (including


When using NTP in a shelf configuration, all units in the shelf (including

standby main units) are automatically synchronized to the active main unit’s

clock.

IP Table


Here you can manually set your neighbor’s network properties

Page 127

6/13/2010

13

SNMP

• V1• V3

• No security• Authentication• Authentication privacy

• SHA


• MD5• No Authentication

All ODU

This feature is used to feed the integrated fans of a 3rd party Outdoor Enclosure (standalone outdoor rack)

When enabled the Ext Alarms connector is modified to provide the requiredWhen enabled, the Ext. Alarms connector is modified to provide the required power feed.


All ODU Disabled All ODU Enabled

Page 128

6/13/2010

14


27

[email protected]

Page 129

3/7/2010

1


EMS Switch Configuration

®


Agenda

2

1. Switch mode review

2. Guidelines

3. Single Pipe Configuration

4. Managed Mode Configuration

5. Managed Mode Common Applications

Page 130

3/7/2010

2


Switch Modes

3

1. Single (Smart) Pipe (default mode, does not require license) –

This application allows only single GbE interface as traffic interface (Optical

GbE-SFP or Electrical GbE - 10/100/1000).

Any traffic coming from any GbE interface will be sent directly to the radio and

vice versa.

This application allows QoS configuration.

Other FE (10/100) interfaces can be configured to be "functional" interfaces

(WSC, Protection, Management), otherwise they are shut down.

Note: (CQ20473): Single pipe discards “PAUSE” PDU (01-80-C2-00-00-01)

and “Slow protocols” PDU (01-80-C2-00-00-02).


Switch Modes

4

2. Managed Mode (license depended) –

This application is “802.1Q” VLAN aware bridge, allowing L2 switching based

on VLANs. This application also allows QoS configuration.

All Ethernet ports are allowed for traffic. Each traffic port can be configured to

be "access" port or "trunk" port:

Type VLANs Allowed Ingress FramesAllowed Egress

Frames

AccessSpecific VLAN should be

assigned to access the port

Only Untagged frames

(or Tagged with VID=0 –

"Priority Tagged“ )

Untagged frames

TrunkA range of VLANs should be

assigned to access the PortOnly Tagged frames

Tagged frames

Page 131

3/7/2010

3


Switch Modes

5

3. Metro Mode (license depended) –

This application is “802.1Q” VLAN aware bridge, allowing Q-in-Q (A.K.A.

VLAN Stacking). This mode allows the configuration of a PE port and CE port.

Type VLANsAllowed Ingress

Frames

Allowed Egress

Frames

Customer-

Network

Specific S-VLAN should be

assigned to "Customer-

Network" port

Untagged frames, or

frames with C-tag

(ether-type=0x8100).

Untagged or C-tag

(ether-type= 0x8100)

frames.

Provider-

Network

A range of S-VLANs, or

"all" S-VLANs should be

assigned to "Provider-

Network" port

Configurable S-tag.

(ether-type)

0x88a8

0x8100

0x9100

0x9200

Configurable S-tag.

(ether-type)

0x88a8

0x8100

0x9100

0x9200


Guidelines

6

• Changing switch modes requires a reset

• Resets do not change the IP-10G settings (radio,

configuration, etc.)

• VLANs need to be created in the switch DB before assigned

to a port

Page 132

3/7/2010

4


Single Pipe

Configuration

7


Single Pipe Configuration

8

IP-10 Switch

Port 1: GbE (Optical or Electrical)

Port 3: FE (RJ45)Port 8 (Radio)

VID 51

Untagged

VID 4 VID 45

VID 100

Page 133

3/7/2010

5


Configuration – Single Pipe

9

This is the default setting


Configuration – Single Pipe

10

Only one ingress port

can be used:

Port 1 (Opt. or Elec.)

Port 3 (RJ45)

When one is enabled

the other is disabled

No need to configure

VID membership

Page 134

3/7/2010

6


Managed Mode

Configuration

11


Configuration – Managed Mode

12

Port #2 as Trunk (VID 200)

Radios as Trunk by

default Port #2 as Trunk

(VID 200, VID 300)Port #3 as Trunk

(VID 300)

IDU-B

IDU-A

Let’s use this diagram as an example -

Page 135

3/7/2010

7



13

Make sure both IDUs are aware of

the required VIDs

You need to create the VIDs before

you assign them to a certain port

(Set # & Apply)



14

Next steps:

1. Go to Interfaces page

2. Enable the required port (Ingress ports)

3. Configure the port type as Trunk or Access

4. Assign allowed VLAN IDs (port membership)

5. Radio port is automatically configured as Trunk, all VLANs are

allowed by default

Page 136

3/7/2010

8



15

12

3

4



– Common Applications

16

PC

IP-10

Access Port Radio = Trunk Port

PC

192.168.1.100

192.168.1.200

Transmits and

receives

Untagged

frames

Transmits and

receives

Untagged

frames

Tagging / untangling

Page 137

3/7/2010

9



– Common Applications

17

IP-10

Trunk Port

Radio = Trunk Port

Traffic

Generator

Trunk Port

Multiple L2

streams, each

identified with

unique VID

18

Thank You !

[email protected]

Page 138

4/17/2010

1

FibeAir IP-10®


Trunk VS. Access

Agenda

1. VLAN TAG Attributes

2. Access Port

3. Trunk Port

4. Extracting frames out of a trunk

5. General Guidelines


6. EMS Trunk Configuration

Page 139

4/17/2010

2

VLAN TAG Attributes

1. In L2 ETH switching, L2 traffic can be engineered using the VLAN TAG attributes

2. L2 traffic is controlled by defining port membership: Access or Trunk

3. Together, port membership + L2 traffic engineering convert connectionless to connection-oriented network

4. In such networks, services are better deployed and maintained

5. VLAN TAG attributes include:• VLAN ID (12 bits)


• VLAN ID (12 bits)• Priority Bits (3 bits)

5. Additional attributes may be used to engineer traffic:• MAC DA• Port number

Access Port

• Access Port is a port which is aware of a single VLAN only

• Ingress traffic is expected to be Untagged, e.g. – no VLAN g gg ginformation exists within the received Ethernet frame

• All frames that are received through this port are tagged with default VLAN (VID + P bits)

• All frames that exit through this port towards customer devices are untagged (VLAN is removed)


• Users can configure the L2 switch to assign different tagging scenarios to different ports

Page 140

4/17/2010

3

Access Port

• Let us examine the Tagging / Untagging process of a L2 switch

L2 ETH SW


DA SA Type Payload FCS

L2 ETH SW

Access Port – Tagging ingress frames

• Let us examine the Tagging / Untagging process of Port #1

Tagging

Port #8




VLAN TAG

Port #1Port #8

Access Port:Untagged frame

Tagged frame

Page 141

4/17/2010

4

Access Port –Utagging frames towards customer interfacing ports

• When Tagged frame from Network is forwarded to Access port, the VLAN Tag is removed

Untagging




VLAN TAG

Port #1Port #8

Access Port: Untagged frame

Tagged frame

Access Port – Tagging multiple ports

• The switch can individually tag multiple Access ports with same VID or unique VID

Tagging

Port #8





VLAN TAG = 10

Port #1Port #8

Port #2

Access Ports: Untagged frames

DA SA Type Payload FCSVLAN TAG = 33

Page 142

4/17/2010

5

Trunk Port – multiple VIDs awareness

• To be able to transmit & receive multiple VLANs, the common port has to be configured as a Trunk Port

Trunk Port





VLAN TAG = 10

Port #1Port #8

Port #2

Access ports: Untagged frames


Trunk Port – multiple VIDs awareness

• Any port can be configured as Trunk• In this example, port #2 is facing customer device to forward all the

network VLANs (TX&RX)

Port #8

Trunk Port



Port #2

Untagged frames




Page 143

4/17/2010

6

Trunk & Access – Extracting frames out of a Trunk

• A certain VLAN can be extracted out of a Trunk via Access port assigned with specific VLAN membership (Default VID)


Port #8: Trunk

Port #5: Access

DA SA Type Payload FCSVLAN TAG = 33DA SA Type Payload FCS


DA SA Type Payload FCSVLAN TAG = 10Port #2:Trunk

Untagged frames




General guidelines

• Access port can only receive untagged frames from customer device

• Access port can only transmit untagged frames towards customer device

• Access port supports single VLAN

• Access port can be connected to an Access port only

• Trunk port can only receive / transmit tagged frames

• Trunk port supports multiple VLANs


• Trunk port can be connected to a Trunk port only

• When configuring Access or Trunk port, membership needs to be defined next (which VLANs are supported…)

Page 144

4/17/2010

7

EMS Trunk Configuration

12

3


4


14

[email protected]

Page 145

4/21/2010

1



EMS Metro Switch Configuration

®


Agenda

2

Metro mode review

Configuration Guidelines

Simplified Flow

Common Applications: CN – PN – PN – CN

Common Applications: CN – PN – PN – PN

Switch Mode Configuration

CN Port Configuration

PN Port Configuration

Page 146

4/21/2010

2


Metro Mode (license depended)

3

This application is “802.1Q” VLAN aware bridge, allowing Q-in-Q

(A.K.A. VLAN Stacking).

This mode allows the configuration of a PE port and CE port.

Type VLANsAllowed Ingress

Frames

Allowed Egress

Frames

Customer-

Network

Specific S-VLAN should be

assigned to "Customer-

Network" port

Untagged frames, or

frames with C-tag

(ether-type=0x8100).

Untagged or C-tag

(ether-type= 0x8100)

frames.

Provider-

Network

A range of S-VLANs, or

"all" S-VLANs should be

assigned to "Provider-

Network" port

Configurable S-tag.

(ether-type)

0x88a8

0x8100

0x9100

0x9200

Configurable S-tag.

(ether-type)

0x88a8

0x8100

0x9100

0x9200


Configuration guidelines

4

• Customer Network frames are encapsulated with a 2nd VLAN (S-VLAN)

and forwarded to a PN port

• PN ports transport multiple encapsulated networks, each associated with

a unique S-VLAN

• CN ports remove the S-VLAN towards a Customer interface

Radio

Ports

(PN)

S-VLAN 9

Network 1

S-VLAN 8

Network 2

C-VLAN 100

C-VLAN 101

C-VLAN 102

C-VLAN 103

C-VLAN 100

C-VLAN 101

C-VLAN 102

C-VLAN 103

Network #1

Network #2

Page 147

4/21/2010

3


Simplified Flow

5

CN CN

ISP / BTS #1

C-VLAN 100

C-VLAN 101

C-VLAN 102

ISP / BTS #2

C-VLANs unknown

S-VLAN 1000

S-VLAN 222

Radio Port

IP-10

PNS-VLAN 1000

S-VLAN 222


CN-PN-PN-CN

6

BTS #1:

C-VLAN 100

C-VLAN 101

C-VLAN 102

C-VLAN 103

BTS #2:

C-VLAN 100

C-VLAN 101

C-VLAN 102

C-VLAN 103

CN

CN

CN

CN

Radio

Ports

(PN)

S-VLAN 9

BTS 2

S-VLAN 8

BTS 1

C-VLAN 100

C-VLAN 101

C-VLAN 102

C-VLAN 103

C-VLAN 100

C-VLAN 101

C-VLAN 102

C-VLAN 103

Page 148

4/21/2010

4


CN-PN-PN-PN

7

BTS #1:

C-VLAN 100

C-VLAN 101

C-VLAN 102

C-VLAN 103

BTS #2:

C-VLAN 100

C-VLAN 101

C-VLAN 102

C-VLAN 103

Radio

Ports

(PN)

S-VLAN 9

BTS 2

S-VLAN 8

BTS 1

C-VLAN 100

C-VLAN 101

C-VLAN 102

C-VLAN 103

C-VLAN 100

C-VLAN 101

C-VLAN 102

C-VLAN 103

CN

CNPN

Provider NetworkCustomer Network


Switch Mode Configuration

8

1. Set mode to Metro (requires reset)

2. Add the S-VLAN ID (set & apply)

1

2

Page 149

4/21/2010

5



9

1. Go to Interfaces / Ethernet Ports page

2. Enable the port

3. Set the type to Customer Network

4. Type the port ID (EVC name, free string)

5. Type the S-VLAN ID

6. Enable Port Learning

7. Apply & Refresh

8. See screen capture next slide



10

2

3

4

5

6

1

Page 150

4/21/2010

6



11

1. Go to Interfaces / Ethernet Ports page

2. Enable the port

3. Set the type to Provider Network

4. Enable Port Learning

5. Edit (if needed) the allowed S-VLANs

6. Apply & Refresh

7. Set the required S-Tag (Ether-Type)

8. See screen capture next slide



12

2

3

4

5

1

6

1

Page 151

4/21/2010

7


PN Port Configuration – Setting the S-Tag

13

7

• 0x88A8

• 0x8100

• 0x9100

• 0x9200


QoS with Metro Switch

14

CN ports only audits the P-Bit of C-VLANs:

Ingress frames through CN ports can be classified by applying a

VLAN P-Bit Classifier.

Page 152

4/21/2010

8

15

Thank You !

[email protected]

Page 153

4/30/2010

1

FibeAir IP‐10 Series®


Commissioning the Radio Link

Radio Link Common Attributes

IP‐10IP‐10

# Link ID

RSL – Received Signal [dBm]

MSE– Mean Square Error [dB]: • Modulation status• Signal to Noise Ratio (SNR)


Max. TSL – Max. allowed Transmission Signal [dBm]

Monitored TSL – Actual Transmission level [dBm]

# - Link ID: must be the same on both ends

Page 154

4/30/2010

2

LINK ID

LINK ID – Antenna Alignment Process

To avoid pointing the antenna to a wrong direction (when both links share the same frequency), LINK ID can be used to alert when such action is take.

# 101# 101

# 101

# 101

# 102“Link ID Mismatch”


“Link ID Mismatch”

# 101

Page 155

4/30/2010

3

LINK ID – Antenna Alignment Process

Both IDUs of the same link must use the same Link IDOtherwise, “Link ID Mismatch” alarm will appear in Current Alarms Window

# 101# 101

# 101

# 101

# 102“Link ID Mismatch”


“Link ID Mismatch”

# 101

ATPC

Page 156

4/30/2010

4

ATPC – Adaptive Transmission Power Control

The quality of radio communication between low Power devices varies significantly with time and environment.

This phenomenon indicates that static transmission power transmission rangeThis phenomenon indicates that static transmission power, transmission range, and link quality, might not be effective in the physical world.

• Static transmission set to max. may reduce lifetime of Transmitter• Side-lobes may affect nearby Receivers (image)

Main Lobe


Side Lobe


To address this issue, online transmission power control that adapts to external changes is necessary.

In ATPC, each node builds a model for each of its neighbors, describing the correlation between transmission power and link quality.

With this model, we employ a feedback-based transmission power control algorithm to dynamically maintain individual link quality over time.


Page 157

4/30/2010

5


1. Enable ATPC on both sites

2. Set reference RSL (min. possible RSL to maintain the radio link)

3. ATPC on both ends establish a Feedback Channel through the radio link (1byte)

4. Transmitters will reduce power to the min. possible level

5. Power reduction stops when RSL in remote receiver reaches Ref. level

TSL Adjustments Monitored RSL


ATPC module

Radio Transceiver

Radio Receiver

Radio Receiver

Signal Quality Check

‐

Site A Site B

Radio

Feedback

Ref. RSL

RSL required change

ATPC OFF = High Power Transmission

ATPC: Disabled ATPC: Disabled

Max. TSL: 10 dBm

Monitored TSL: 10 dBmMonitored RSL: -53 dBm

Max. TSL: 10 dBm

Monitored TSL: 8 dBmMonitored RSL: -56 dBm


ATPC module

Radio Transceiver

Radio Receiver

Radio Receiver


‐

Site A Site B

Radio

Feedback

Ref. RSL

RSL required change

Page 158

4/30/2010

6

ATPC ON = Reduced Power, cost & long-term maintenance

ATPC: EnabledRef. RSL: -65 dBm

ATPC: EnabledRef RSL: - 65 dBmRef. RSL: 65 dBm

Max. TSL: 10 dBm

Monitored TSL: 2 dBm (before 10)

Monitored RSL: -60 dBm (before 53)

Ref. RSL: 65 dBm

Max. TSL: 10 dBm

Monitored TSL: 2 dBm (before 8)

Monitored RSL: -63 dBm (before 56)


ATPC module

Radio Transceiver

Radio Receiver

Radio Receiver


‐

Site A Site B

Radio

Feedback

Ref. RSL

RSL required change

MRMC Adaptive TX Power

Page 159

4/30/2010

7

MRMC Adaptive TX Power

Designed to work with ACM in certain scenarios to allow higher Tx power available at lower order modulation schemes for a given modulation scheme.

When Adaptive TX is disabled:Maximum TX power is limited by the highest modulation configured in the MRMC ACM script.

In other words, when link suffers signal degradation, modulation may change from 256QAM to QPSK. However, Max. power will be limited to the value corresponding as Max. TX in 256QAM.


When Adaptive TX is Enable:When link suffers signal degradation, modulation may change from 256QAM to QPSK. However, Max. power will increase to compensate for the signal degradation.

MRMC Adaptive Power = OFF

256QAM @ Monitored TSL = 18 dBm (Max.)

16QAM @ MAX. TSL = 18 dBm

Signal Degradation = Lower bit/symbol


Page 160

4/30/2010

8

MRMC Adaptive Power = ON

256QAM @ Monitored TSL = 18 dBm(Max.)

16QAM @ Monitored TSL = 24 dBm

Signal Degradation = Lower bit/symbol


MRMC Adaptive Power

It is essential that Operators ensure they do not breach any regulator-imposed EIRP limitations by enabling Adaptive TX.

To better control the EIRP, users can select the required class (Power VS. q (Spectrum):

• Class 2• Class 4• Class 5B• Class 6A• FCC

RFU C h ld h i 2 01 ( hi h ) f f ti lit f


RFU-C should have version 2.01 (or higher) for proper functionality of “Adaptive TX Power” feature.

The Effective Isotropic Radiated Power (EIRP) is the apparent power transmitted towards thereceiver assuming that the signal power is radiated equally in all directions

Page 161

4/30/2010

9

Configuration

Radio Settings – Local Radio

Spectrum Mask

FQ spacing (gap) between channelsMonitored transmission power

Monitored recei ed signalMonitored received signal

Required value = zeroMonitored Mean Square Error

Radio frequencies can be set locally or on remote unit as well (assuming links is up)

Enable / Disable


Enable = no transmission

Min. target RSL (local)

Enable / Disable

Value depends on MRMC settings

Must be identical on both IDUs

Page 162

4/30/2010

10

Radio Settings – Local Radio


Enable on both IDUs to get maximum throughput (500Mbps @ 56MHz)

Radio Settings – Remote Radio

When the radio link is up, you can configure certain parameters on the remote unit:

• Make sure Remote IP is available• Remote RSL can be read


• Remote TSL can be set (depends on remote MRMC script)• Remote TX MUTE can be disabled (see next slide)• Remote target RSL for ATPC can be set

Page 163

4/30/2010

11

Remote Un-Mute

Sit B i NOT t itti

Simplified scheme

Site A is transmitting

Site B is NOT transmitting

but receiver is still ON


Site A

Site B

Radio Thresholds


These settings determine the sensitivity / tolerance for triggering:

• 1+1 HSB switchover• Ethernet Shutdown• PM generated alarms

Page 164

4/30/2010

12

MRMC – Multi Rate Multi Coding

Users may set the radio to a fixed capacity or automatic adaptive capacity using ACM.

ACM radio script is constructed of a set of profiles.

Each profile is defined by modulation order (QAM) and coding rate, while theseEach profile is defined by modulation order (QAM) and coding rate, while these parameters dictate profile’s capacity (bps).

When ACM script is activated, system “chooses” automatically which profile to use according to the channel fading conditions.

ACM TX profile can be different than ACM RX profile.

ACM TX profile is determined by remote RX MSE performance.


RX end is the one that initiates ACM profile upgrade or downgrade.

When MSE is improved above predefined threshold, RX generates a request to the remote TX to ‘upgrade’ its profile.

If MSE degrades below a predefined threshold, RX generates a request to the remote TX to “downgrade’ its profile.

MRMC Configuration


We shall review this page using the following slides:

Page 165

4/30/2010

13

MRMC – reading current script

MAX. Capacity (w/out compression)

ACM Script CH. BWModulation

Spectrum Mask

ACM is on

ACM Script CH. BW

Spectrum


Spectrum Class Type

MRMC – Reading current capacity


Page 166

4/30/2010

14


27

[email protected]

Page 167

3/7/2010

1



Configuring Interfaces

®


Agenda

2

• Ethernet Interfaces

• TDM Interfaces

• AIS Detection

• AIS Signaling (STM-1)

• STM-1 Interface

• Auxiliary Channels

• Wayside Channel (Various Configurations)

Page 168

3/7/2010

2


Ethernet Ports Configuration

Interface Rate Functionality

Single Pipe Managed SW / Metro

ETH 1 (SFP) GbE Disabled / Traffic Disabled / Traffic

ETH 2 (RJ 45) GbE Disabled / Traffic Disabled / Traffic

ETH 3 (RJ 45) FE 10 / 100 Disabled / Protection Disabled / Traffic / Protection

ETH 4 (RJ 45) FE 10 / 100 Disabled / Wayside Disabled / Traffic / Wayside

ETH 5 (RJ 45) FE 10 / 100 Disabled / MNG Disabled / Traffic / MNG



ETH 8 Radio

(N Type)

According to

Licensed fq.

Disabled / Traffic Disabled / Traffic

Configuring ETH ports is discussed in previous modules:

• Switch Configuration

• Trunk VS. Access

• Metro Switch Configuration

• QoS Configuration


Ethernet Ports Configuration

Page 169

3/7/2010

3


TDM Ports Configuration

IP-10G has 16 TDM ports + 16 additional ports when a 2nd T-Card

is installed.

Supported PHYs:

• E1

• DS1

Dynamic allocation:

Radio bandwidth (which may vary in ACM) is automatically allocated in the

following order:

1. High-priority TDM trails

2. Low-priority TDM trails

3. Ethernet traffic (Data + Management, QoS should be considered)

TDM trails in both sides of a link should have identical priorities.


TDM Ports Configuration – Standalone IDU

E1/DS1 port #n will be mapped to

radio VC#n (n=1-16).

When Trails are configured, default

mapping (above) is overwritten by Trail

Mapping.

However, if no trails are configured (all

are deleted) system will revert to the

default setting.

When Trail is configured and set to

Operational - TDM port is activated.

When Trail is configured but set to

Reserved - TDM port is disabled.

Page 170

3/7/2010

4


TDM Ports Configuration – Node Site

Up to 180 trails can be configured in a

Shelf / node

The number of Trails mapped to a

radio depends on radio capacity

(MRMC).

The maximum number of radio Trails

is 75 (E1) or 84 (DS1).


AIS Line Detection

This feature allows detection of AIS

signals in TDM traffic incoming from line

interfaces (E1/DS1, STM-1):

In case of detection, the following takes place:

• Signal failure is generated at the corresponding trail – this will cause the

far end not to receive a signal (including trail ID indications) and the trail

status to show “signal failure” and “trail ID mismatch”.

• An indication is given to user at the proper interface. Notice that this is

not a system alarm, since the problem originates elsewhere in the

Network

Page 171

3/7/2010

5


AIS Signaling in STM interface (VC 12)

In case of signal failure at the trail outgoing from the STM-1

interface, AIS will be transmitted at the payload of the VC-12.


STM interface Configuration

The following configurations are available:

Admin: Enable / Disable

When interface is disabled:

• There is no signal transmission

• Received signal is ignored

• Trails previously configured to STM-1 interface will get

“Signal Failure”

• No alarms will be shown

Clock source: Internal Clock / Loop / TDM Trail

Mute TX: mutes the outgoing STM-1 signal, but received

signal will be used for traffic

Excessive BER threshold: specific for STM-1 interface

Signal degrade threshold: specific for STM-1 interface

Page 172

3/7/2010

6


AIS Signaling in STM interface (V5)

The system can be configured to signal AIS at the VC

level (AIS-V) in the V5 byte of the overhead.

This is meant to provide indications to SDH

multiplexing equipment which may not have the ability

to detect AIS at the payload level.

For example: signaling in outgoing V5 byte upon AIS

detection at payload-level (E1)

“111111111”“111111111”

AIS @ E1 TS AIS @ STM V5


STM interface Configuration

J0 trace identifier is fully supported in both

15-byte and 1-byte modes:

• An alarm will be raised when the expected string

differs from the received string (but traffic will not be

affected).

• Transmit, Expected and Received strings are

provided.

• If a string is defined and user changes the length

from 15 bytes to 1 byte, the first byte will be analyzed

and other bytes ignored.

The string transmitted as J2 trace identifier is the Trail

ID defined for the TDM trail mapped to the

corresponding VC-12 interface.

Page 173

3/7/2010

7


Auxiliary Interfaces

EOW may be used as a simple solution for on-site

communication between two technicians / installers / etc.

• Up to 19200 baud, Asynchronous RS-232.

• Up to 19200 baud, Asynchronous V.11.


WSC Interface

• WSC interface is limited to 1628 bytes.

• 2.048Mbps (Wide) or 64Kbps (Narrow)

• Consumes BW from the total link BW

Out of band Management using WSC:

In this case, remote system is managed using Wayside channel.

On both local & remote units, Wayside channel will be connected to management port

(using cross Ethernet cable).

WSC can be configured to "narrow“ capacity (~64kbps) or "wide" capacity (~2Mbps).

It is recommended to use “wide” WSC in order to get better management performance,

since “narrow” WSC might be too slow.

Page 174

3/7/2010

8


OOB MNG in a 1+0 standalone link

At least 2 management ports are needed in a local unit:

One port for local management, and 2nd port that will be connected to Wayside port.

On remote unit, Wayside port will be connected to management port.


OOB MNG in a 1+1 standalone IDUs (Y-Splitter)

Active & Standby MNG

ports have 2 options to be

connected to the Host:

Using Ethernet splitter

cable connected to external

switch.

Using Protection "Patch

Panel".WSC port will be connected in each unit to other

available management port.

In remote site, each unit's Wayside port should be

connected to management port.

Page 175

3/7/2010

9


OOB MNG in a 1+1 standalone IDUs (P. Panel)

18


Page 176

3/7/2010

1



XC / SNCP / Nodal Solution

®

Introduction

Page 177

3/7/2010

2


SNCP (ITU- G.805)

• Ring topologies provide path protection for Ethernet or TDM signals

• In some scenarios additional protection is required

• The IP-10G Path-Protection is based on SNCP

(Sub-network Connection Protection)

• Individual E1/T1 trails will be protected by defining two separate trails, with the same

end-points, which are routed through two different paths in the network

• The end-points may be line interfaces or radio VCs, so partial path protection can

be provided for a trail in a network where full path redundancy topology is not

available

• The end-points are also referred to as branching-points

3


SNCP (ITU- G.805)

• With Wireless SNCP, a backup VC trail

can be optionally defined for each

individual VC trail

4

Main Path

Protective Path

Page 178

3/7/2010

3


FibeAir IP-10 – Integrated Nodal Solution

� The solution is modular and forms a singleunified nodal device:

• Common Ethernet Switch

• Common E1s Cross Connect

• Single IP address

• Single element to manage

� Connecting 2 IDUs requires a nodal enclosure:

• Best economical future upgrade

• Best flexibility for network designer

• Easier to Install / Maintain / expand

� IP-10 IDU can be used as a Standalone unit (1U) or in as a Nodal Solution


FibeAir IP-10 – Integrated Nodal Solution

• Up to 6 units can be stacked to form single nodal device

• Additional units can be added in the field as required

• Multiple nodes can be cascades to support large aggregation sites

• Stacking is done using 2RU “Nodal enclosures”

• Each enclosure has 2 slots for hot-swappable 1RU units

• Additional “Nodal enclosures” and units can be added in the field as required without

affecting traffic

Front

Rear

Nodal enclosure

Page 179

3/7/2010

4


FibeAir IP-10 – Nodal Enclosures

7

“Main” nodal enclosure

“Extension” nodal enclosure


FibeAir IP-10 – Scalable Nodal Enclosures

8

Pay as you grow !

Page 180

3/7/2010

5


Integrated nodal solution – “Main” units

Units located in the bottom “Nodal enclosure” are acting as the main units

• The main unit performs the cross-connect, switching and management functions for

all the units in the node

• Mandatory “active” main unit can be located in any of the 2 slots

• Optional “standby” main unit can be installed in other slot

• Switchover time <50msecs for all traffic affecting functions

M

E

Main unit

Expansion unit

Native2

1+1 HSB

Integrated Ethernet Switching

Integrated TDM cross-connect

M

M


Integrated nodal solution – “Expansion” units

• Units located in non-bottom “Nodal enclosures” are acting as “expansion” units

• All interfaces of the expansion units (radio, TDM and Ethernet) are connected to the

main units

• Expansion unit is fully managed through the main units

• Radios in each pair of main/expansion units can be configured as either:

• Dual independent 1+0 links

• Single 1+1 HSB link

• Single 2+0/XPIC link

Native2

1+1 HSB

M

M

E

E

Native2

2+0/XPIC

E

E

Native2

1+0

Native2

1+0

M

E

Main unit

Expansion unit

Integrated Ethernet Switching

Integrated TDM cross-connect

Page 181

3/7/2010

6

Trail Configuration Guidelines


XC Trails Guidelines (1)

1. XC Trails can be configured only via Main unit

2. All Trails are transported through main unit(s)

3. When Protection is enabled, configure trails to go via the Active unit

(XC Trails are automatically created on the STBY unit)

4. T-Cards (TDM / SDH) are not hot-swappable, do not extract / insert card

when IDU is powered up

5. Radio VCs must be identical on both sides of the radio link

Page 182

3/7/2010

7



5. Creating a TDM trail automatically activates the corresponding TDM port,

therefore an alarm will display next to the relevant T-Card accommodating

the activated port(s)

7. XC Trails can be configured between:

• Radio to Line

• Line to Radio

• Radio to Radio

8. Maximum number of Trails per Node = 180

9. Maximum number of Trails per Radio = 75 (E1) or 84 (T1) or 168 (SNCP)



Identify Trail interfaces prior to configuration

Note that Trail configuration is Bi-Directional !

IP-10

IP-10

IP-10

Trail starts here:

For SNCP we shall

need to define 3

interfaces

Trail traverses through here:

We shall need to define 2

interfaces

Trail starts here:

For SNCP we shall

need to define 3

interfaces

Bypass

site Protected Trail(Automatic)

Radio Link

Page 183

3/7/2010

8



Pay attention to the order of configuration:

The Trail Start/End points should

be configured first (interface #1)

Interfaces #2 and #3 can be

configured in a random order

IP-10

IP-10

IP-10

1

2 3

3

2

1

Bypass

site

Protected Trail

(Automatic)

Standalone non-protected Trail Configuration

Page 184

3/7/2010

9


Step #1: Access Trail Page

Click on the Add button


Step #2: Configure 1st Interface

Click on the 1st interface connector

In this example we selected the

PDH connector.

Your next step is selecting the PDH

port number.


SDH connector.

Your next step would be selecting

the VC number.

Page 185

3/7/2010

10


Step #3: Configure 2nd Interface

Click on the 2nd interface connector


Radio as the next interface

connector.

Your next step would be selecting

the radio channel number.

Alternatively you could choose other combinations as well:

• PDH to PDH

• PDH to Radio (above)

• PDH to SDH

• SDH to Radio

• SDH to Radio

• Radio to SDH

• Radio to PDH


Step #4: Configure Trail Attributes

Make sure Trail ID is unique and identical on all sites/trails

Page 186

3/7/2010

11


Step #5: Trail Verification

If your settings are correct, trail alarms should disappear, trail path is ready to be tested

SNCP Trail Configuration in a Node

Page 187

3/7/2010

12


Selecting Main IDU for Trail Configuration

23

• In the following example we assume every node has 2 IDUs installed in a

Main Enclosure

• Make sure your Main unit is selected on every Node-EMS

• Enable Protection when you configure the Trails (excluding Bypass Nodes)

• Trail ID should unique and identical on all nodes


SNCP Trail in Nodal Architecture

IP-10

IP-10

IP-10Bypass

Node

PDH interface

SDH interface

Page 188

3/7/2010

13


IP-10

IP-10

IP-10

Bypass

site

PDH interface

SDH interface #1

Radio CH #1 Radio CH #26

1st Node


IP-10

IP-10

IP-10Bypass

Node

PDH interface

SDH interface

Radio CH #1

Radio CH #48

Bypass Node

Page 189

3/7/2010

14


IP-10

IP-10

IP-10Bypass

site

PDH interface

SDH interface

Radio CH #26

Radio CH #48

3rd Node

28

Thank You !

[email protected]

Page 190

4/30/2010

1

FibeAir IP-10 Series®


Automatic State Propagation

Agenda

• Introduction• Interfacing IP-10 with external devices• Configuration VS FunctionalityConfiguration VS. Functionality• Dead Lock Example• ASP in Managed / Metro Mode


Page 191

4/30/2010

2

Introduction

“Automatic State Propagation” ("GigE Tx mute override") enables propagation of radiofailures back to the line, to improve the recovery performance of resiliency protocols(such as xSTP).

The feature allows the user to configure which criteria will force GbE port (or ports in case of “remote fault”) to be muted / shut down, in order to allow the network find alternative paths.

The feature is not operational in "External Protection".

Radio LOF


Need to find alternative path

Interfacing IP-10 with external devices

When external devices do not support Fault Propagation –

Configure the following:

1. Enable Local LOC - to mute local GbE when LOC is raised2. Enable Remote Fault – to mute local transmitter in case of remote LOF / Link ID

mismatch & LOC3. Enable Local Excessive BER – recommended but not necessary


Page 192

4/30/2010

3

Interfacing IP-10 with external devices

When external devices support Fault Propagation (another IP-10) –

Configure the following:

1. Disable Local LOC 2. Enable Remote Fault – to mute local transmitter in case of remote LOF / Link ID

mismatch & LOC3. Disable Local Excessive BER - to avoid a dead lock scenario


Example: Avoiding Dead Lock in Single Pipe

Site B Site A

TX RXTX

RX TX

RX

1. GbE FO breaks down or disconnects at the ingress port of Site A


Page 193

4/30/2010

4


Site B Site A

TX RX LOCTX

RX TX

RX



2. LOC alarm is raised


Site B Site A

TX RX LOCTX

RX TX

RX


X


3. LOC alarm triggers Site A to shut down its transmitter (TX Mute)


Page 194

4/30/2010

5


Site B Site A

TX RX LOCTX

RX TX

RX

LOC


X




4. Site B detects silence on ingress port and declares LOC


Site B Site A

TX RX LOCXTX

RX TX

RX

LOC


X

X




4. Site B detects silence on ingress port and declares LOC

5. Site B shuts down its transmitter – both sites are in a state of a dead lock

Page 195

4/30/2010

6

Automatic State Propagation in Single Pipe

11

Single Pipe - Propagation Criteria

Using Optical GbE (SFP)

Local Criteria:

Local and remote IDUs must have identical settings:

1. ASP Enabled2. ACM profile threshold3. Excessive BER enabled

Local Criteria:• LOC (GbE)• Radio LOF• LINK ID Mismatch• Excessive BER• ACM profile is below threshold

1 8 8 1


1 8 8 1

Actions:Mute port 1 (GbE ‐SFP)

Actions:Mute port 1 (GbE ‐SFP)

Page 196

4/30/2010

7


Using Electrical GbE (RJ45)Local and remote IDUs must have identical settings:


L l C it iLocal Criteria:• Radio LOF• LINK ID Mismatch• Excessive BER• ACM profile is below threshold

8 8


8 8

Actions:Shut down Elec. port

Actions:Shut down Elec. port


Using Electrical GbE (RJ45)Local and remote IDUs must have identical settings:


8 8

P t i l i ll l d b t t

Local GbE Criteria:• LOC


Remote LOC will not trigger port shut down (it will not be possible to enable the port when LOC is cleared)

Port is logically closed but not shut down

LOC will not trigger port shut down (it will not be possible to enable the port when LOC is cleared)

Page 197

4/30/2010

8

Automatic State Propagation in Managed / Metro Mode

15

ASP in Managed / Metro Mode

• Alarms are never propagated to a GbE port

• GbE will never shut down

• Alarms will be propagated to the Radio port

• In 1+1 external protection, ASP is disabled.


Page 198

4/30/2010

9

Managed / Metro - Propagation Criteria Local and remote IDUs must have identical settings:


Local Criteria:• Radio LOF• LINK ID Mismatch• Excessive BER• ACM profile is below threshold

8 8


8 8

Actions:Shut down RadioActions:Shut down Radio

Managed / Metro - Propagation CriteriaLocal and remote IDUs must have identical settings:


8 8


Local criteria:• GbE LOC

8 8

Actions:Shut down RadioNo action taken

Page 199

4/30/2010

10


19

[email protected]

Page 200

6/14/2010

1

FibeAir IP‐10®


1+1 Protection

Agenda

Introduction to External Protection

Introduction to Shelf ProtectionIntroduction to Shelf Protection

Guidelines

External Protection Process: 1+1 from scratch

External Protection Process: Upgrading 1+0 to 1+1


Troubleshooting

Page 201

6/14/2010

2

External Protection

• Achieved by using two standalone IDUs • The IDUs must be connected by an Ethernet Cross cable (via the protection ports)• Each IDU has its unique IP address• Each IDU has its unique IP address.• Protection Panel may be in use (shown in orange, supports TDM only)• 1st IDU is Active (TX & RX), 2nd IDU is STBY (awaits a switchover command)


f1 - high

f1 - high

IDU

f1 - low

In this example 1+1 Protection is only deployed at one site

Shelf Protection

When enabling a Shelf Protection, the following rules should be applied:

• Shelf backplane replaces the external Protection CableTh i l IP dd f h f th i it• There is only one IP address for each of the pair units

• Protection can enabled in each pair (1+2, 3+4, 5+6)• Each IDU must have a unique IP address• 1st IDU is Active (TX & RX), 2nd IDU is STBY (system awaits a switchover command)

IDUIn this example Protection 5

6


1

is configured in every pair of IDUs (slots)

2

3

4IDU

IDU

Page 202

6/14/2010

3

Guidelines

• A Standby IDU is referred to as the Mate

• When a switchover occurs, the Active IDU becomes Standby and the “Standby” IDU becomes “Active”Standby IDU becomes Active

• Accessing a Mate IDU can only be done via the Active IDU

• Accessing the new "Active" will be done using its IP address

• Y-Split cables must be used for Ethernet signals (fiber optics)


Setup Example (Standalone IDUs)


Page 203

6/14/2010

4

Configuring external 1+1 from scratch

Configuring external 1+1 from scratch (1)

1. Set all IDUs to factory defaults

2 Wh IDU l t th b ti if2. When IDUs complete the booting sequence, verify:

• All IDUs have the same HW version• All IDUs have the same SW version• Every IDU has unique IP address• Active and STBY have the same SW mode• All IDUs have the same Management mode (In band or OOB)• In case of In-Band, all IDUs have the same In-Band VID


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“.

Page 204

6/14/2010

5


3. Install the 1st link (make sure radio is up)

ODU ODU

4. Enable Protection on both IDUs (management will be lost for 60 sec)

5. Lock Protection on both IDUs (to avoid unnecessary switchover when 2nd IDU

is enabled)

6 I t ll 2 d IDU i h it

ODU ODU


6. Install 2nd IDU in each site (no need to configure it)

ODU ODU

ODU ODU


7. Enable protection in 2nd IDU in each site

8. Connect ETH Cross Cable between both protection ports

9. Disconnect the MNG cables.

ODU ODU

ODU ODU


9. Disconnect the MNG cables. 10. Connect the PC to IDUs via ETH Y-Cable:

ODU ODU

ODU ODU

PC

Page 205

6/14/2010

6


11. Verify Active IDU shows Mate’s IP address

12. Verify there are no “Configuration Mismatch” alarms

13. Verify there are no “Mate Communication failures”

14. Complete system setup by configuring Active IDU

15. In Active IDU: click “Copy to Mate” and verify Mate is restarting

16. Repeat steps 10 to13



17. Unlock protection on Active IDUs

18. Initiate Manual Switchover / Forced Switchover: verify traffic is OK.

Upgrading (1+0) to (1+1)

Page 206

6/14/2010

7


1. Assuming 1st link operates well, configure the 2nd IDUs to match Active IDUs:

• 2nd IDUs has the same HW version as Active IDU• 2 IDUs has the same HW version as Active IDU• 2nd IDU has the same SW version as Active IDU• 2nd IDU has unique IP address (different than Active’s IP)• 2nd IDU has the same switch mode as Active IDU• 2nd IDU has the same Management mode (In band or OOB)• In case of In-Band, 2nd IDU has the same In-Band VID as Active IDU• 2nd IDU is configured with the same radio parameters as Active IDU• Mute transmission on 2nd IDUs

Active Link:


ODU ODU

Active Link:

Standby Link (not connected)

ODU ODU


2. Enable Protection on Active IDUs (management will be lost for 60 sec)

3 L k P t ti b th A ti IDU3. Lock Protection on both Active IDUs (to avoid unnecessary switchover when 2nd IDU is enabled)

4. Install 2nd IDU in each site (verify TX is muted before physical installation)

ODU ODU


ODU ODU

ODU ODU

Page 207

6/14/2010

8


5. Enable protection in 2nd IDU in each site

6. Connect ETH Cross Cable between both protection ports


ODU ODU

ODU ODU



8. Connect the PC to IDUs via ETH Y-Cable

9. Cancel TX mute on both Mate IDUs


10. Verify Active IDU shows Mate’s IP address

11. Verify there are no “Configuration Mismatch” alarms

12. Verify there are no “Mate Communication failures”

13. Complete system setup by configuring Active IDU

14. In Active IDU: click “Copy to Mate” and verify Mate is restarting




16. Unlock protection on Active IDUs

17. Initiate Manual Switchover / Forced Switchover: verify traffic is OK.

Page 208

6/14/2010

9

Troubleshooting ProtectionCommon issues followed by CLI commands

Troubleshooting

Alarm / Error Probable Cause / Workaround

Protection LED is on (RED)

1. Protection cable is not connected2. ETH straight cable is connected instead of

cross‐cableProtection LED is on (RED) cross cable3. One of the 2 IDUs is not configured in

Protection

Current Alarms show “Configuration Mismatch” alarm

Check CFG of both IDUs: HW, SW, switch mode, management mode, In Band VIDInitiate “Copy to Mate” in Active IDUs

“I cannot PING the STBY unit….”This is normal behavior, Mate cannot be accessed directly, only via Active IDU


“Main IDU does not respond to PING”

Use CLI commands to verify this IDU is in STBY mode, if so, use CLI to recover IDU

Current Alarms shows “Mate Comm. Failure” alarm

Check the current alarms of STBY IDUReport back to Ceragon SupportReplace STBY unitReplace Active unit

Page 209

6/14/2010

10

Troubleshooting – Useful CLI Commands

General commands:

lsp prints executable commands in current directoryls prints available child directoriesls prints available child-directoriescls clears screen

To execute Protection commands, you will need to change directory:

IP-10:/> cd platform/mate-idu

Then to read current status of IDU type the following (in blue):


Then, to read current status of IDU, type the following (in blue):

IP-10:/platform/mate-idu> get protection-mode

The system return these values:1. Active2. Standby


To change Protection Admin mode, type the following:

IP-10:/platform/mate-idu> set protection-admin <enable/disable>

To lock the current protection mode, type the following:

IP-10:/platform/mate-idu> set protection-lockout <on/off>


Page 210

6/14/2010

11


To force a switchover, type the following:

IP-10:/platform/mate-idu> set protection-force-switch <on/off>

To request a manual switchover, type the following:

IP-10:/platform/mate-idu> manual-switch-cmd


To initiate a Copy-to-Mate process, type the following:

IP-10:/platform/mate-idu> copy-to-mate-cmd


22

[email protected]

Page 211

3/7/2010

1



Loopback Maintenance

®


Agenda

2

In this module we shall describe

the various actions we can

perform to properly maintain and

troubleshoot the IP-10G system

Page 212

3/7/2010

2


RFU RF Loopback

3

RFU RF LB


RFU RF Loopback

4

Use it to verify communication from Line to ODU is OK (including ODU)

• Traffic affecting – TX is stopped

• Configurable Timer to automatically restore traffic ( 0 = no time limits)

• RFU LED is RED when Loopback is ON

• LINK LED is GREEN when Loopback is ON

• Alarm is displayed in Current Alarms:

•

and Event log:

Page 213

3/7/2010

3


IF Loopback

5

IDU IF LB


IF Loopback

6

Use it to verify communication from Line to IF cable is OK

• Traffic affecting – TX is stopped

• Configurable Timer to automatically restore traffic (0 = no time limits)

• LINK LED is GREEN when Loopback is ON

• Alarm is displayed in Current Alarms:

•

and Event log (next slide):

Page 214

3/7/2010

4


IF Loopback – Analysis using Event Log

7

Let’s assume radio link is down – LINK LED is RED

16:29:01 We enable IF LB, therefore Link alarms clear

16:29:05 Loopback replaces remote unit – therefore alarm disappears

16:30:01 Loopback automatically stops, link recovers to original state

16:30:05 Radio link is down (original state)


PDH Line LB towards Line (NE)

8

LB towards the line

Page 215

3/7/2010

5


PDH Line LB towards Line (Near End)

9

Use this feature to evaluate connection to customer’s patch-panel

Alarm is displayed in CAS:

and in Event Log:


PDH Line LB towards Radio (FE)

10

LB towards the radio

Tester

Page 216

3/7/2010

6


PDH Line LB towards Radio – Event Log Analysis

11

Let’s assume PDH port #1 is enable but not connected

Therefore, Major alarm is on (RED)

16:59:44 We enable Line LB towards the radio

16:59:46 Loopback replaces end-device – therefore alarm disappears

17:06:37 Loopback is OFF

17:06:38 PDH port alarm is ON again…..


SDH Line LB towards System

12

Towards System – signal (trail) is looped back to

IP-10

Page 217

3/7/2010

7


SDH Line LB towards Line

13

Towards Line – signal (trail) is looped back to

customer interface


IDU-RFU Interface Monitoring

14

Before you leave the site, make sure that these registers are elapsed (zero)\

When one of these registers is different than 0 – you need to report to

your support representative

In such case, perform the Loopbacks we have just covered to narrow down the

probable causes for the errors

Page 218

3/7/2010

8

15

Thank You !

[email protected]

Page 219

3/7/2010

1


EMS Backup Maintenance

®


Agenda

2

In this module we shall describe the various

actions we can perform to properly maintain

and troubleshoot the IP-10G system using:

1. Configuration File

2. Unit Information File

3. FTP Server

Page 220

3/7/2010

2


Configuration File

3

The Configuration file stores the following parameters:

• License

• External Alarms

• SNMP Trap Destination

• NTP Server Properties

• Radio properties: Frequency, RSL, TSL, ATPC, etc.

• Switch Mode and database: Port types, VLAN membership, etc.

• Interface Configuration: PDH, TDM, Ethernet Switch

•Trail Configurations

• Service OAM

• Security: user accounts, login properties, etc.


Unit Information File

4

The Unit Information file stores the following parameters:

• Date & Time

•Daylight Saving Time properties

• System name and other ID parameters

• Measuring properties (voltage, temperature)

• Accumulated Performance Monitoring logs

• Serial numbers

Page 221

3/7/2010

3


Local FTP Server

5

Uploading or Downloading the CFG & Unit files requires an FTP Server

As long as your IP-10G communicates with the server, its location is

irrelevant

EMS PC with local FTP Server installed


Remote FTP Server

6

You may assign a remote server to host the configuration and unit files

EMS PC Remote FTP Server

Page 222

3/7/2010

4


FTP Root Directory

7

Examples for

SW packages

Examples for

CFG & Unit

Files

Every Server has its own properties. Make sure you are familiar with

your FTP Root Directory: this is where the files are stored (software

versions, CFG & Unit).


Configure your FTP Server Properties

8

2

1

Page 223

3/7/2010

5


Upload /

Download using

standalone IP-10G

9


Uploading the CFG File (IP-10G to Server)

10

Click “Create Archive” to

allow the IP-10G zipping

all parameters into one file

Page 224

3/7/2010

6



11

Wait till task is

successfully completed



12

Next step:

Click “Upload Archive” to allow

the IP-10G transferring the

zipped file to your server

Page 225

3/7/2010

7



13

Wait till task is successfully

completed


Check your FTP Root Directory

14

This is your copy of

the configuration file

You may place it now

in the dedicated folder

(Configuration Files)

Page 226

3/7/2010

8



15

1 2

Follow the same steps to upload the Unit Information file:


Check your FTP Root Directory

16

This is a copy of your Unit Information file

Page 227

3/7/2010

9


Downloading the CFG File (Server IP-10G)

17

1 2

Follow the same steps to download the CFG file

When download completes successfully, you will need to restart the

system for changes to take place

Please note – if the file does not exist in the root directory action will fail !


Upload /

Download in

a shelf

18

Page 228

3/7/2010

10


Shelf Backup: Creating the Nodal Shelf Backup

19

Uploading CFG files from a shelf is similar to a standalone

process

1. First you need to create the CFG files of all slots

2. After creating the CFG files, you need to upload them to your

FTP directory


Shelf Backup: Creating the Nodal Shelf Backup

20

First you need to create the

CFG files.

To do so, select the unit(s)

and click the relevant

“Backup” button

Page 229

3/7/2010

11


Shelf Backup: Upload from IP-10G to Server

21

Next, click “Upload

Archive(s)” and the

file(s) will be uploaded

to your FTP root

directory


Shelf Backup: Download from Server to IP-10G

22

To download a file to a

certain slot, select the

unit number and click

this button

Page 230

3/7/2010

12


Unified Unit Information File

23

A unified file is created for

all stacked units

Upload & Download

action are identical to a

standalone unit


Checking Backup History & Status

24

Click here to see the

backup history

Page 231

3/7/2010

13


Checking Backup History & Status

25


Setting the unit back to Factory Defaults

26

You can restore your system to

factory defaults

You may also set the IP address to

factory default address (192.168.1.1)

Page 232

3/7/2010

14

27

Thank You !

[email protected]

Page 233

4/21/2010

1


EMS Software Upgrade

®


Agenda

2

FTP Properties

Standalone SW Download

Standalone SW Upgrade

Nodal IDU SW Download

Nodal IDU SW Upgrade

Rollback VS. Downgrade

Page 234

4/21/2010

2


Local FTP Server

3

SW files are located on an FTP Server (local or remote)

Configure the FTP properties to point to your local server root directory

(Make sure RD/WR permissions are enabled)

EMS PC with local FTP Server installed


Remote FTP Server

4

EMS PC Remote FTP Server

If you do not have an FTP Server installed locally on your PC, you may

configure an IP address of a remote server.

Page 235

4/21/2010

3


FTP Root Directory

5

Examples for

SW packages

Make sure you are familiar with your FTP Root Directory: this is where

the files are stored (software versions, CFG & Unit).


Configuring FTP Server Properties

6

2

1

Page 236

4/21/2010

4


Configuring FTP Server Properties

7

Type the location of the software package:

• FTP IP address

• SW folder (when relevant, in this example “66253”)

Type the username & Password(You may log in using CMD window to verify settings are correct)


SW Upgrade on a

standalone IP-10G

8

Page 237

4/21/2010

5



9

Click on the “Download” button and wait till “Succeeded” message is

displayed (next slide)

You may view at any time the download

process by clicking on the Log Icon



10

Download was successfully completed, you may proceed to upgrade

the IDU

Page 238

4/21/2010

6


Download completed – Upgrade delayed

11

In case Upgrade is scheduled for later moments, the Version table will

display the following status:


Standalone Upgrade

12

Click on the “Upgrade” button. When upgrades completes successfully,

the IDU will restart automatically.

You may view at any time the upgrade


Page 239

4/21/2010

7


SW Upgrade in a

shelf (Node)

13


Shelf Configuration

14

Slot 4

Slot 3

Slot 2

Slot 1

1. Make sure your main unit (Slot 1) is upgraded with the latest version

2. If not, it is recommended to upgrade the main unit as a standalone IDU

3. Verify you are familiar with the slot number(s)

Slot 6

Slot 5

Page 240

4/21/2010

8


Shelf SW Download

15

Configure the FTP properties if needed

Click on the “Download” button and

wait till “Succeeded” message is

displayed

You may view at any time the download



Shelf SW Upgrade

16

Select the target slot and then click the

“Upgrade” button

Or – click “Upgrade All”

Please note –

1. The number of slots depend on

actual configuration

2. The slot numbers are not according

to physical allocation in the shelf

3. Failures may occur due to wrong

FTP configurations, unstable

network connection or missing files

4. IDU(s) will reset automatically upon

successful upgrade

Page 241

4/21/2010

9


Shelf SW Upgrade

17

Select the target slot and then click the

“Upgrade” button

Or – click “Upgrade All”

Please note –

1. The number of slots depend on

actual configuration

2. The slot numbers are not according

to physical allocation in the shelf

3. Failures may occur due to wrong

FTP configurations, unstable

network connection or missing files

4. IDU(s) will reset automatically upon

successful upgrade


Rollback

VS. Downgrade

18

Page 242

4/21/2010

10


Rollback

19

2.8.25 2.8.31 2.8.35

Upgrade #1 Upgrade #2

2.8.32

Downgrade

1 2

34Rollback

Rollback does not revert previous “Downgrade” operation !

It rolls back IDU version 1 step back (prior to last Upgrade)

20

Thank You !

[email protected]

Page 243

3/7/2010

1



EMS Security Configuration

®


Agenda

2

• SSH

• HTTPS

• SFTP

• Users & Groups

• Password

Page 244

3/7/2010

2


Security ConfigurationUpdate first FTP connection


SSH – Secured Shell

• SHHv1 and SSHv2 are supported.

• SSH protocol can be used as a secured alternative to "Telnet".

• SSH protocol is always be operational. Admin user can choose whether to

disable

• "Telnet" protocol, which will be "enabled" by default. Server authentication

will be based on IP-10’s "public key".

• Key exchange algorithm is RSA.

• Supported Encryptions: aes128-cbc, 3des-cbc, blowfish-cbc, cast128-cbc,

arcfour128, arcfour256, arcfour, aes192-cbc, aes256-cbc, aes128-ctr,

aes192-ctr, aes256-ctr.

• MAC (Message Authentication Code): SHA-1-96 (MAC length = 96 bits, key

length = 160 bit). Supported MAC: hmac-md5, hmac-sha1, hmac-

ripemd160, hmac-sha1-96, hmacmd5-96'

• The server will authenticate the user based on “user name” and

“password”. Number of failed authentication attempts is not limited.

• Server timeout for authentication: 10 min. This value cannot be configured.

Page 245

3/7/2010

3


HTTPS

In order to manage the system using HTTPS protocol, user should

follow the following steps:

• 1. Create the IDU certificate based on IDU's public key.

• 2. Download the IDU certificate.

• 3. Using CA certificate (Optional steps)

i. Download the IDU CA's certificate.

ii. Enable WEB CA certificate.

• 4. Set WEB Protocol parameter to HTTPS


HTTPS – Public Key Upload

The public key should be uploaded by the user for generating the IDU’s

digital certificate:

• The upload will be done by using FTP/SFTP (s

• The public key file will be in PEM format.

• Click “Upload Public Key”

• The status of the “upload” operation can be monitored. The returned status

values are: “ready” (default), “in-progress”, “success”, “failed”. In any case

of failure, an appropriate error message will appear.

Page 246

3/7/2010

4


HTTPS – Certificate Download (1)

Download IDU server certificate and/or IDU CA certificate (optional) :

• Download is done by using FTP/SFTP.

• PEM and DER certificate formats are supported.

• For downloading the IDU server certificate and/or IDU's CA certificate to the system, the

following steps must be fulfilled for each file type:

� Determine certificate file name (“Admin” privilege).

� Determine the certificate file type (“Admin” privilege): “Target Certificate” (for WEB

server digital certificate) or “Target CA certificate” (for WEB CA digital certificate).

� Determine certificate file format (“Admin” privilege): Format could be PEM (for PEM

formatted file), or DER (for DER formatted file).

� Determine whether to include the

CA certificate into the WEB configuration

definitions. This is an optional configuration

and is recommended for adapting the

WEB interface to all the WEB browsers

applications (“Admin” privilege).


HTTPS – Certificate Download (2)

� After setting the above configurations, a “Download Certificate” command

should be issued.

� The status of the download operation can be monitored. The returned status

values are: “ready”, “in-progress”, “success”, “failed”.

� It is recommended to “refresh” the WEB page when certificate download

operation is terminated.

� To apply the new certificate, the WEB server should be restarted (“Admin”

privilege). WEB server will be automatically restarted when it is configured to

HTTPS.

Page 247

3/7/2010

5


HTTPS - Activation

WEB interface protocol can be configured to be HTTP (default) or HTTPS

(cannot be both at the same time).

While switching to HTTPS mode, the following must be fulfilled:

• WEB server certificate file exist.

• Certificate public key is compatible to IDU’s private key.

• If one of the above tests fails, the operation will return an appropriate error

indication.

• Open WEB Browser and type the URL ”https:\\<IP of target IDU>”.

Note:

This parameter is NOT copied when “copy to mate” operation is initiated,

for security reasons (unsecured unit should not be able to override security

parameters of secured unit).


SFTP (Secure FTP)

SFTP can be used for the following operations:

• Configuration upload/download,

• Upload the unit info.

• Upload public key.

• Download certificate files.

• SW download

Page 248

3/7/2010

6


USERS,

GROUPS

&

PASSWORD


Adding Users

To add / edit users & groups click on the

item as shown in the captured imaged (left)

Click Add User to add new users…

Page 249

3/7/2010

7


Adding Users


Adding Users

New users will be required to change their

password when they log in for the first time

Page 250

3/7/2010

8


Changing Password

A valid password should be a mix of upper and lower case letters, digits, and other

characters.

You can use an 8 character long password with characters from at least 3 of these 4

classes. An upper case letter that begins the password and a digit that ends it do not

count towards the number of character classes used.


Changing Password

Good example:

L00pBack – using capital letters, small letters and digits (zeros instead of “O”)

Bad example:

Loopback – missing digits or other characters

Loopbacks – using more than 8 characters

Page 251

3/7/2010

9

17

Thank You !

[email protected]

Page 252

6/13/2010

1

FibeAir Outdoor EnclosureSame Advanced Features in a Compact,

Zero Footprint Casing

FibeAir Outdoor Enclosure Key Features • Full wireless solution at zero footprint

• Outdoor Enclosure for IDUs

• 5RU/19’’ rack space outdoor enclosure

• 4RU for Traffic IDUs, 1RU for Panels and cables• Support for the same FibeAir product line used for indoor deployment

• IP-10/IP-10G Series

• 1500R • Installation anywhere

• Roof top, wall, or pole• Passive heat exchange - no need for air conditioning systems

• External battery backup solution with enclosure (Optional)

• Heating unit for frigid environments

© CERAGON NETWORKS LTD. Proprietary and Confidential information of Ceragon Networks Ltd

• Heating unit for frigid environments

Page 253

6/13/2010

2

Outdoor Enclosure – Reduced OPEX & CAPEX

• Compact size and modular• Zero footprint - saves ground space at central offices / communication rooms

• All outdoor nodal or ring configurations

• Pole-mount, wall or roof-top installation

• Sit l i iti i• Site lease or acquisition savings

• Lower overall costs • Installation - Instant wireless site set-up. One man installation

• Rent - Versatile installation options saves site lease costs

• Power - Saves power, space and air conditioning

• Easier maintenance

• IP-55 certification for water and dust proofing


Elegant, Easier to Install & Maintain Solution

Outdoor Enclosure – Units configurations

• All configurations, interfaces, and customer needs

• IP-10 & 1500R with full networking functionality

• General configurations –

• 1+0 & 1+1 HSB 2+0 4+01+0 & 1+1 HSB, 2+0, 4+0…

• TDM XC / grooming

• Packet switch solution

• All interfaces

• N*E1/T1

• N*Ethernet interfaces (FE, GbE)

• STM-1


Page 254

6/13/2010

3

Outdoor Enclosure – Practical experience

• External alarm inputs for external fans and door opening

• Sunshade for solar radiation protection

• Door stopper

I t ll ti h k• Installation hooks

• Documentation pocket

• Door Lock

• Pole mount option or wall mount option

• Light weight

• Battery Backup option


Environmental Recommendation support

• Environmental Standards Compliance • GR-487-CORE

• ETSI EN 300 019-1-4, Class 4.1 (Non-weather protected locations)

• IEC 529 IP- 55 protected cabinet (dust & water)p ( )

• Operating Air Temperature -40 to +55degC

• Safety and Electromagnetic Standards (EMC) Compliance • UL60950-1 (Safety)

• FCC 47 CFR, part 15, class B (EMC)

• GR-1089-CORE (Safety & EMC part of NEBS)

• CSA CS22.2 60950-1 (Safety)

• ETSI EN 301 489-1

• ETSI EN 301 489 4 (EMC)


• ETSI EN 301 489-4 (EMC)

• CB IEC 60950-1 (Safety)

Page 255

6/13/2010

4

IP protection classesIP 55 – What does that mean ?

First Characteristics Numeral IP XY - Foreign Bodies Protection, Solids

IndexProtection against Human/Tool Contact

Protection against solid objects (foreign bodies)

0 No special protection

1 Back of hand, Fist Large foreign bodies, diam. >50mm

2 Finger Medium-sized foreign bodies, diam. >12

3Tools and wires etc with a thickness >2.5mm

Small foreign bodies, diam. >2.5mm

4Tools and wires etc with a thickness >1mm

Granular foreign bodies, diam. >1mm

© CERAGON NETWORKS LTD. Proprietary and Confidential information of Ceragon Networks Ltd7

thickness >1mmg ,

5Complete protection, (limited ingress permitted)

Dust protected; dust deposits are permitted, but their volume must not affect the function of the unit.

6 Complete protection Dust-proof

IP protection classesIP 55 – What does that mean ?

Second Characteristics Numeral IP XY - Water Protection, Liquids

IndexProtection against water

Protection from condition

0 N i l t ti

0 No special protection

1 Water dripping/falling vertically Condensation/Light rain

2 Water sprayed at an angle (up to 15º degrees from the vertical) Light rain with wind

3 Spray water (any direction up to 60º degrees from the vertical) Heavy rainstorm

4 Spray water from all directions, (limited ingress permitted) Splashing

5 Low pressure water jets from all directions, (limited ingress permitted)

Hose down, residential

6 H d

© CERAGON NETWORKS LTD. Proprietary and Confidential information of Ceragon Networks Ltd8

6High pressure jets from all directions, (limited ingress permitted)

Hose down, commercial.eg. Ship decks

7 Temporary immersion, 15 cm to 1m Immersion in tank

8Permanent Immersion, under pressure

For use on Titanic recovery vehicle

Page 256

6/13/2010

5

Outdoor Enclosure Design - external

WD

HH

• General Dimensions

• H: 18.5 in / 47 cm


• W: 24 in / 61 cm

• D: 17 in / 43 cm

• Weight

• 55 Pounds / 25Kg

Accessories list

Marketing Model Marketing Description

OE-Enclosure FA Outdoor Enclosure

OE-Pole-Installation FA Outdoor Enclosure Pole installation

OE H t FA O td E l h tOE-Heater FA Outdoor Enclosure heater

OE-Ext-Fans FA Outdoor Enclosure external fans

OE-Fan-Drawer-Kit Outdoor Enclosure Fan Drawer Kit

OE-Ext-Power-CBL-15M Outdoor environment power cable (-48V). Ferrule-Ferrule 15m

ODE-NTYPE-JUMPER-CBL-3M Outdoor Enclosure IF Jumper Cable 3m

OE-Ext-Alarms-CBL-0.45M Outdoor Enclosure External alarms cable, D-9M - D-9F, 0.45M

IP10-OE-CBL-ETH-RJ45-15m IP-10 ETH Outdoor RJ45 cable 15m, straight

CBL-OE-E1-RJ45-RJ45-15m IP-10 E1 Outdoor RJ45 cable 15m, straight


CBL-OE-T1-RJ45-RJ45-15m IP-10 T1 Outdoor RJ45 cable 15m, straight

IP10-OE-CBL-ETH-RJ45-XED-15m IP-10 ETH Outdoor RJ45 cable 15m, Cross

CBL-OE-E1-RJ45-RJ45- XED-15m IP-10 E1 Outdoor RJ45 cable 15m, Cross

CBL-OE-T1-RJ45-RJ45- XED-15m IP-10 T1 Outdoor RJ45 cable 15m, Cross

OE-Sealing-Compound-1.5M Outdoor Enclosure sealing compound

(*) all IP-10 standard accessories can be used. Enclosure space should be taken into consideration

Page 257

6/13/2010

6

Thank You

Page 258

FibeAir® IP-10

License Management

Guide

Part ID: BM-0139-0 Doc ID: DOC-00019183 Rev a.00

November 2008

Page 259

Notice This document contains information that is proprietary to Ceragon Networks Ltd.

No part of this publication may be reproduced, modified, or distributed without prior written authorization of Ceragon Networks Ltd.

This document is provided as is, without warranty of any kind.

Registered TradeMarks Ceragon Networks® is a registered trademark of Ceragon Networks Ltd.

FibeAir® is a registered trademark of Ceragon Networks Ltd.

CeraView® is a registered trademark of Ceragon Networks Ltd.

Other names mentioned in this publication are owned by their respective holders.

TradeMarks CeraMapTM, PolyViewTM, EncryptAirTM, ConfigAirTM, CeraMonTM, EtherAirTM, and MicroWave FiberTM, are trademarks of Ceragon Networks Ltd.

Other names mentioned in this publication are owned by their respective holders.

Statement of Conditions The information contained in this document is subject to change without notice.

Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or consequential damage in connection with the furnishing, performance, or use of this document or equipment supplied with it.

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.

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

Corporate Headquarters: Ceragon Networks Ltd. 24 Raoul Wallenberg St. Tel Aviv 69719, Israel Tel: 972-3-645-5733 Fax: 972-3-645-5499 Email: [email protected] www.ceragon.com

European Headquarters: Ceragon Networks (UK) Ltd. 4 Oak Tree Park, Burnt Meadow Road North Moons Moat, Redditch, Worcestershire B98 9NZ, UK Tel: 44-(0)-1527-591900 Fax: 44-(0)-1527-591903 Email: [email protected]

North American Headquarters: Ceragon Networks Inc. 10 Forest Avenue, Paramus, NJ 07652, USA Tel: 1-201-845-6955 Toll Free: 1-877-FIBEAIR Fax: 1-201-845-5665 Email: [email protected]

APAC Headquarters Ceragon Networks (HK) Ltd. Singapore RO Level 34 Centennial Tower 3 Temasek Avenue Singapore 039190 Tel - + 65 6549 7886 Fax: +65 6549 7011

Page 260

Contents

General .......................................................................................................... 1

Getting Started.............................................................................................. 1

How to use the System................................................................................. 5

Managing the License .................................................................................. 6

Working with Devices .......................................................................................... 6

Working with Licenses....................................................................................... 16

Settings ............................................................................................................... 23

Generating Reports ............................................................................................ 25

Page 261

FibeAir® IP-10 License Management System 1

General This guide explains how to work with the FibeAir® IP-10 web based License Management System.

The system enables authorised users to obtain license-related information and perform license-related operations.

Getting Started To start the management application:

1. In your web browser, go to the address http://80.74.99.83/LMManage/login.aspx

2. To log in to the system, enter your user name and password, and then click Login.

Note the following user name rules:

Page 262


For Demo OEM, the first five digits must be 00001. The next four digits after the first five should be numbered starting with 0001 for end users. For example, the number 000010001 would mean that Demo OEM end user 0001 is entering the system.

For users other than Demo OEM, the user name must start with 00000. For example, the number 000000001 would mean that non-Demo OEM user 0001 is entering the system.

For OEM Users

3a. If you enter as an OEM user, the following web page appears:

One of two modes can be selected:

Administrator (Demo OEM option) - The administrator can assign licenses and devices to customers, who can be either another OEM customer or Demo OEM. In this mode of operation, the OEM admin can assign licenses/devices to end users (including themself) and can generate license keys for the devices.

End User (Customer option) - The OEM end user, or the OEM itself can generate keys for self use. In this mode, the user can only generate licenses based on the available device database. The user can only view his/her own devices (that were assigned to that user) and licenses.

Page 263

CeraView® User Guide 3

End users that belong to that channel cannot see devices or licenses that belong to the OEM or other customers.

After you select the operating mode, the following web page appears:

Page 264


For Non-OEM Users

3b. If you enter as a non-OEM user the following web page appears:

Note that a channel or OEM user can also enter as one of their customers. In this case, the system identifies the user as a channel/OEM user and will display a drop-down list to enable entry under the user's name. This will be done to allow operations for devices that the user sent to his/her customers.

Page 265


How to Use the System The menus that you can select from are grouped according to their functions. Simply click the item you want within a menu group (such as the Devices or Settings group).

When you select an item within a group, the relevant web page will open with the details concerning that item.

At the top of the web page for the item, a line appears with buttons that you can click to perform a particular operation.

From within an item web page, you do not have to return to the main web page. Instead, use the tabs at the top (Devices, Licenses, etc.) to obtain a list of items for the particluar group.

Note that in any web page, you can click Print to send the contents of the page to the printer.

Page 266


Managing the License The following sections describe the system menus and options that you can select to obtain information concerning your licenses and to perform license-related operations.

Working with Devices

The Devices group includes items that can be selected to perform device-related operations, such as to obtain information about the devices included in your license, or import a device list from another source.

Device List

To obtain a list of devices:

In the Devices group, select All Devices, or click the Devices tab at the top of the web page (if it appears).

The following web page appears:

Page 267


Note that for OEM users, the Generate Keys button is replaced with Assign to Customer

.

The list includes all the devices you purchased from Ceragon.

Click Device ID for a more deatiled description of the device.

In this page, you can assign the current ID to an end user, using the drop-down list in the Assign to Customer field.

Page 268


Search for Devices

In the main device list web page, you can click Search to locate a particular device that is registered in the system.

Select the criteria (filters) you want for the search, and then click Search.

To clear the criteria you selected, click Clear.

Page 269


Import Devices

In the toolbar, click Import to import a list of devices from an external source.

You will be prompted to locate the file with the device list. Once you locate and select the file, click Import.

The device list file must be a text file with the following columns:

Device ID Customer Country Region / Network Link Side

In the Device ID column, use only upper case letters.

Adding and Deleting Devices

To add a new device, in the toolbar, click New .

Page 270


Enter a valid device ID in the field and click Save.

The device will be added to your device list.

To delete a device, select the device in the list, and click Delete .

Exporting a Device List

To export a device list to a file, click Export .

The list will be saved in an Excel file with the extension csv (Comma Separated Values).

Generating Keys

To generate license keys for one or more devices, select the devices in the main list by marking the

checkboxes beside them, and click Generate Keys .


In this web page, only the devices you selected will appear.

Page 271


The All Relevant Licenses area shows only the licenses that are common to all devices you selected (meaning their lowest common denominator).

The current license types include the following:

1 = ACM

2 = Networking

3 = Capacity Upgrade

The following tables list the current license possibilities:

Capacity Upgrade License

Type Value Description Name in License Management Site

3 0 IP10-CAP-010 Feature disabled 3 1 IP10-CAP-025 Radio Cap. Upgrade 10->25 Mbps 3 2 IP10-CAP-050 Radio Cap. Upgrade 10->50 Mbps 3 3 IP10-CAP-100 Radio Cap. Upgrade 10->100 Mbps 3 4 IP10-CAP-150 Radio Cap. Upgrade 10->150 Mbps 3 5 IP10-CAP-200 Radio Cap Upgrade 10->200 Mbps 3 6 IP10-CAP-300 Radio Cap Upgrade 10->300 Mbps 3 7 IP10-CAP-400 Radio Cap Upgrade 10->400 Mbps 3 8 IP10-UPG-025-050 Radio Cap. Upgrade 25->50 Mbps 3 9 IP10-UPG-025-100 Radio Cap. Upgrade 25->100 Mbps 3 10 IP10-UPG-025-150 Radio Cap. Upgrade 25->150 Mbps 3 11 IP10-UPG-025-200 Radio Cap. Upgrade 25->200 Mbps 3 12 IP10-UPG-025-300 Radio Cap Upgrade 25->300 Mbps 3 13 IP10-UPG-025-400 Radio Cap Upgrade 25->400 Mbps 3 14 IP10-UPG-050-100 Radio Cap. Upgrade 50->100 Mbps 3 15 IP10-UPG-050-150 Radio Cap. Upgrade 50->150 Mbps 3 16 IP10-UPG-050-200 Radio Cap. Upgrade 50->200 Mbps 3 17 IP10-UPG-050-300 Radio Cap Upgrade 50->300 Mbps 3 18 IP10-UPG-050-400 Radio Cap Upgrade 50->400 Mbps 3 19 IP10-UPG-100-150 Radio Cap. Upgrade 100->150 Mbps 3 20 IP10-UPG-100-200 Radio Cap. Upgrade 100->200 Mbps 3 21 IP10-UPG-100-300 Radio Cap Upgrade 100->300 Mbps 3 22 IP10-UPG-100-400 Radio Cap Upgrade 100->400 Mbps 3 23 IP10-UPG-150-200 Radio Cap. Upgrade 150->200 Mbps 3 24 IP10-UPG-150-300 Radio Cap Upgrade 150->300 Mbps 3 25 IP10-UPG-150-400 Radio Cap Upgrade 150->400 Mbps 3 26 IP10-UPG-200-300 Radio Cap Upgrade 200->300 Mbps 3 27 IP10-UPG-200-400 Radio Cap Upgrade 200->400 Mbps 3 28 IP10-UPG-300-400 Radio Cap Upgrade 300->400 Mbps

Page 272


ACM

License Type Value Description Name in License

Managament Site 1 0 Feature disabled 1 1 IP10-ACM ACM

Networking (Metro Switch Enabled)

License Type Value Description Name in License

Management Site 2 0 Feature disabled 2 1 IP10-Metro Metro Switch

To add a license for which you want to generate a key, select the license in the All Relevant Licenses area and click Add to add it to the Selected Licenses area.

Important! You can only select one license from each category (ACM, Networking, Capacity Upgrade). If you select a capacity upgrade license and want to add a different capacity upgrade license, you must first remove the first capacity upgrade license and then add the other one.

Once you select the licenses you want, click Generate Keys.

After you confirm your selection, the following example web page appears.

Page 273


Assigning Devices to a Customer

For OEM users, you can assign devices to other users by selecting Assign Devices to a Customer in the main web page Devices group. Or, you can click Assign to Customer at the top of the page.

In the Select Customer field, use the drop-down list to choose the customer you want to assign the devices to.

Click Show Available Devices for a list of devices you can choose from.

In the available list of devices, click Filter & Sort to customize the device list, as shown in the following example page.

Page 274


You can specify the ID of the device you want to include in the list, and select the list sort order (ascending or descending).

After you click Go to generate the list, in the Available Devices list, select the devices you want to assign to the user, and click Add to add them to the Assigned Devices list.

When you complete the operation, click Save.

In the confirmation page, click Confirm.

The following example page appears:

Page 275


Click Continue to go back to the device list page.

The device list page will appear with the updated information.

Page 276


Working with Licenses

In the Licenses group, select All Licenses, or click the Licenses tab at the top of the web page (if it appears).


The web page displays all the licenses you currently own.

To search for a particular license, click Search, specify the criteria you want, and click Search again.

Click the number in the Qty Assigned column for a list of licenses assigned to customers.

Page 277


Click the number in the Qty Generated column for a list of licenses used to generate keys.

Page 278


To generate license keys, select Generate Keys in the Licenses group in the main web page, or click Generate Keys in the web page that appears when you click the Licenses tab.

To add a license for which you want to generate a key, select the license in the All Available Licenses area and click Add to add it to the Selected Licenses area.

Click Show Relevant Devices for a list of devices associated with the licenses you chose.

Page 279


To add a device for which you want to generate a key, select the device in the All Available Devices area and click Add to add it to the Selected Devices area.

Once you select the devices you want, click Generate Keys.

The keys will be generated, as shown in the following example page, and the database will be updated.

Page 280


Page 281


Assigning Licenses to a Customer

For OEM users, you can assign licences to other users by selecting Assign Licenses to a Customer. Or, you

can click the Assign to Customer button at the top of the page.

In the Select Customer field, use the drop-down list to choose the customer you want to assign the licenses to.

Click Show Available Licenses for a list of licenses you can choose from.

Page 282


In the Filter by Type field, click the drop-down list and choose the license type (Capacity, ACM, Networking).

For License Code, click the drop-down list and choose the license specifications.

For Quantity to Assign, enter the amount of licenses you want to assign to that customer. The maximum quantity is limited to the available quantity for the license you choose.

After you complete the filter options, click Add to add the licenses to the Assigned Licenses list. You can repeat this procedure more than once to add other license types.

For Quantity to Return, enter the amount of unused licenses you would like to return (if relevant).

Click Save to save the license assigment information in the database.

In the page that appears, click Confirm to confirm the assignment.

A page will appear informing you that the operation was successful, and the main license list will be updated with the information.

Page 283


Settings

In the main web page, the Settings group includes items you can select for system information and configuration.

Managing Users

Select the Manage Users item to define users and modify their properties. You can also access this item by clicking the Settings tab at the top of the page (if it appears).

Use the Search button at the top to locate a particular user.

To define a new user, click New . The following page appears:

Page 284


In this page, enter the information in the fields, and then click Save.

To delete one or more users, in the user list, mark the checkboxes beside the users you want to delete, and

click Delete . Confirm your choice(s) in the page that appears and the users will be deleted.

Modifying your Profile

In the main Settings page, select the My Profile item to modify your personal information.

The same page appears as that for a new user. Modify the information as desired and click Save.

Page 285


Generating Reports

In the main web page, you can select a report to generate: an Orders report, or a Devices and Activations report.

To generate a report, select Orders Report or Devices & Activations Report in the main web page, or click the Reports tab at the top of the page (if it appears).

For an Orders Report:

For Order No., you can select All or Between. If you select Between, specify the range of order numbers you want to include in the report.

For Order Date, you can select All or Between. If you select Between, you will need to specify the range of dates you want to include in the report.

In the Include field, you can select All for all types of orders, Closed orders only, or Open orders only.

When you are done selecting the report criteria, click Create Report.

Page 286


For a Devices & Activations Report:

For Devices, you can select All or Between. If you select Between, specify the range of device IDs you want to include in the report.

For Activation Date, you can select All or Between. If you select Between, specify the range of activation dates you want to include in the report.

When you are done selecting the report criteria, click Create Report.

Page 287

ip 10g basic course handbook v3.1

Documents

ceragon training agenda

ceragon training agenda

confidential page

g course

service p g delivery

shelf ip allocation

shelf setting mng

ip address