IP 10G BASIC Course Handbook v3 1

IP-10G Basic Course
Visit our Customer Training Portal at Training.Ceragon.Com or contact us at training@ceragon.com
Trainee Name:
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
v2.2
Page 1
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
v2.2
Page 2
6/13/2010
Ceragon in a Nutshell
Ceragon FibeAir Family
OA&M
Service Management
Security
Carrier Ethernet Switch ACM

Gigabit Ethernet Fast Ethernet
TDM Cross Connect

XPIC Multi Radio SD/FD
Radio Ethernet + TDM

10-500Mbps, 7-56MHz
Native2
E1/T1
Ch-STM1/ OC3
Terminal Mux
RFU (6-38GHz)
2
Proprietary and Confidential
Page 29
6/13/2010
RFUs
FibeAir RFU-HP
FibeAir RFU-HS
FibeAir RFU-P
FibeAir RFU-C
FibeAir RFU-D
High power
(e.g. Smaller antennas reduced cost)
Standard power
CERAGON MAST - Mobile Architecture for Service Transport

ISPs Fixed Networks Cable TV
CellularBackhaul
RuralAccess
PDH xDSL Subscribers IPDSLAM IP/ETH Customer Network SDH/SONETRING PSTN

4
Page 30
6/13/2010
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 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 p g p g point of contact for all the transport, networking and service p g delivery 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
5
FibeAir IP-10R1 Main features
Unique Adaptive Coding & Modulation (ACM) 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
IP-10R1 Integrated Carrier Ethernet switch

3 modes for Ethernet switching:
Metro switch Carrier Ethernet switching is enabled Managed 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 IP-10
Ethernet User Interfaces

Carrier Ethernet Switch
Radio interface
Ethernet User Interface
Radio interface
Metro/Managed switch mode
Smart pipe mode

Extensive Carrier Ethernet feature-set eliminates the need for external switches
IP-10R1 radio capacity - ETSI

7MHz
ACM Point 1 2 3 4 5 6 7 8 Modulation QPSK 8 PSK 16 QAM 32 QAM 64 QAM 128 QAM 256 QAM 256 QAM # of E1s 4 6 8 10 12 13 16 16 Ethernet Capacity (Mbps) 9.5 13.5 14 20 19 28 24 34 28 40 32 46 38 54 42 60 ACM Point 1 2 3 4 5 6 7 8
14MHz
Modulation QPSK 8 PSK 16 QAM 32 QAM 64 QAM 128 QAM 256 QAM 256 QAM # of E1s 8 12 16 16 16 16 16 16 Ethernet Capacity (Mbps) 20 - 29 29 - 41 42 - 60 49 70 57 82 69 - 98 81 - 115 87 - 125
28MHz
ACM Point 1 2 3 4 5 6 7 8 Modulation QPSK 8 PSK 16 QAM 32 QAM 64 QAM 128 QAM 256 QAM 256 QAM # of E1s 16 16 16 16 16 16 16 16 Ethernet Capacity (Mbps) 38 - 54 53 - 76 77 - 110 103 - 148 127 - 182 156 - 223 167 - 239 183 - 262 ACM Point 1 2 3 4 5 6 7 8
40MHz
Modulation QPSK 8 PSK 16 QAM 32 QAM 64 QAM 128 QAM 256 QAM 256 QAM # of E1s 16 16 16 16 16 16 16 16 Ethernet Capacity (Mbps) 56 - 80 82 - 117 122 - 174 153 - 219 188 - 269 214 - 305 239 - 342 262 - 374 ACM Point 1 2 3 4 5 6 7 8 Modulation QPSK 8 PSK 16 QAM 32 QAM 64 QAM 128 QAM 256 QAM 256 QAM # of E1s 16 16 16 16 16 16 16 16
56MHz
Ethernet Capacity (Mbps) 76 - 109 114 - 163 151 - 217 202 - 288 251 - 358 301 - 430 350 - 501 372 - 531
8
Page 32
6/13/2010
Wireless Carrier Ethernet Ring

Example configuration (1+0 ring)
N x GE/FE
N x GE/FE
N x GE/FE
Wireless Carrier Ethernet Ring
(up to 500Mbps)
Integrated Ethernet Switching
9
N x GE/FE
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 PDH 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)

10
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
Page 33
6/13/2010
NG-SDH/SONET complementary solution

Carrier Ethernet at the access, NG-SDH/SONET at the aggregation
Carrier Ethernet (MW links) SDH/SONET (Hybrid Fiber/MW)
Native Ethernet Ethernet over SDH/SONET
Hub Site
FE/GE GE
GE
RNC FibeAir IP-10
Tail site
FibeAir IP-10
NG-SDH MSPP
NG-SDH MSPP
Core 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 NGSDH/SONET based networks.
Ethernet services are mapped over SDH/SONET
SDH/SONET MW links are used where fiber connections not available
11
IP/MPLS complementary solution

Carrier Ethernet at the access, IP/MPLS at the aggregation
Carrier Ethernet (MW links) IP/MPLS (Hybrid Fiber/MW)
Native Ethernet Ethernet PWs or IP routing
Hub Site
FE/GE GE
GE
RNC
Tail site
FibeAir IP-10
FibeAir IP-10
MPLS Router
MPLS Router
Core Site
Ethernet services are transported natively over Carrier Ethernet based MW radio links.
IP/MPLS edge router acts as gateway between the Carrier Ethernet and IP/MPLS based networks.
Both Ethernet and E1/T1 services are mapped over MPLS using pseudo-wires or routed using IP
High-capacity IP/MPLSaware" Ethernet MW radio is used where fiber connections not available
12
Page 34
6/13/2010
IP-10R1 integrated QoS support - overview

4 CoS/priority queues per switch port Advanced CoS/priority classification based
on L2/L3 header fields:
Source Port VLAN 802 1 802.1p VLAN ID IPv4 DSCP/TOS, IPv6 TC Highest priority to BPDUs
Priority Queues W1 - Hi h t priority Highest i it
Classify Arrivals
W2
Scheduling departures
Advanced ingress traffic rate-limiting

per CoS/priority Flexible scheduling scheme per port
W3
Strict priority (SP) 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
FibeAir IP-10G IDU: A Nodal Solution
Cellulartraffic (TDM)
STM Rings
15
FibeAir IP-10G IDU: A Nodal Solution
16
Page 36
6/13/2010
IP-10F IDU
Fans drawer
Craft Terminal (DB9)
External Alarms (DB9)
16 x E1s (optional) Protection Interface (RJ45) 5 x FE Electrical (RJ45)
RFU interface (N-Type)
GND Power -48V DC
17
Typical Native2 network with IP-10 G & F-Series

4 E1s 25M Eth
F
1+0
F F F
4 E1s 25M Eth 4 E1s 25M Eth
(22 E1, 50M) 1+1 1+0

F F F
1+0
F G G
1+1
F F
1 1 1+1 (44 E1, 100M)
(22 E1, 50M)

4 E1s 25M Eth 4 E1s 25M Eth
(22 E1, 50M)

4 E1s 25M Eth
(44 E1, 100M)
4 E1s 25M Eth

F G G
1+0
(22 E1 E1, 50M) 1+0

4 E1s 25M Eth
4 E1s 25M Eth
F G GX
IP-10 F-Series IP-10 G-Series IP-10 G-Series with XPIC
4 E1s 25M Eth
F F
Native2 1+0 Ring (Up to 75 E1 or 500Mbps Eth) 1+0

G F F G G
1+0
1+0
4 E1s 25M Eth
1+0
Native2 1+0 Ring (Up to 44 E1 or 100M Eth) 1+0

F
1+0
G GX
2+0
GX GX GX
Terminal configuration 2+0 0

F
Native2
GX
Nodal configuration 1+1 1+0

F F F F
4 E1s 25M Eth

GX
2+0 Ring (Up to 150 E1 or 1Gbps Eth)
2+0 2 0
(22 E1, 50M)

4 E1s 25M Eth
(22 E1, 50M)
4 E1s 25M Eth
2+0
4 E1s 25M Eth
18
Page 37
6/13/2010
IP-10G VS. IP-10F

Feature F-Series G-Series 1+0, 1+1 HSB, 1+1 SD, Supported radio configurations 1+0, 1+1 HSB, 1+1 SD 2+0 with XPIC 2+2 HSB with XPIC XPIC option Max radio capacity Multi-radio support # of Ethernet interfaces Full Carrier Ethernet switching feature-set including ring protection # of E1/T1 integrated IDU interfaces option # of E1/T1s per radio carrier T-Card slot (additional 16 E1/T1 interfaces or STM1/OC3 Mux) Nodal/XC/SNCP support Sync unit option V.11/RS232 User Channel option 100 Mbps 5 x FE RJ-45 Yes 500Mbps 1Gbps using 2+0/XPIC Yes 5 x FE RJ-45+ 2 x GE combo (RJ-45/SFP) Yes
Yes
16 E1, None 44 E1s Yes Yes -
16 E1, 16T1, None 75 E1s / 84 T1s Yes Yes Yes 2 x Async V.11/RS232 or 1 x Sync V.11
19
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
10
6/13/2010
Higher Spectral-Efficiency
Whats in it for The Operator?
Typical
Microwave Radio
RequiredCapacity 155200Mbps RequiredCapacity 70100Mbps TWOradio links or 56MHz channelbandwidth 28MHz ChannelBandwidth
IP10
MicrowaveRadio
ONE radiolink using 28MHzchannelbandwidth 14MHz ChannelBandwidth
TheoperatorsavesCAPEX andfreeupvaluablefrequencyresources
21
Higher Spectral-Efficiency is not enough

RadioType
TypicalSystemGain TypicalSystemGain TypicalSystemGain HighSystemGain HighSystemGain
Ant.Diameter
1.80m 1.80m 3.00m 1.80m
Length
30Km 21Km 30Km 30km
Modulation
16QAM 128QAM 128QAM 128QAM
Capacity
32xE1s STM1/OC3 STM1/OC3 STM1/OC3
SpectralEfficiency shouldalwaysbecoupledwith SystemGain

22
Page 39
11
6/13/2010
Ceragons Management Overview
IP-10
23
FibeAir
Tree Topology
24
Page 40
12
6/13/2010
Thank You! training@ceragon.com
Page 41
13
FibeAir IP-10 G-Series

Front Panel Description
Front Panel Overview
GUI Example)
Lets go over the front panel connections of the IP-10 G-Series We shall explain them one by one, left to right
2
Advanced Operation & Maintenance Course

Page 42
CLI Serial Connection
DB9 Craft Line Interface (CLI) Baud: 115200 Data bits: 8 Parity: None Stop bits: 1 Flow Control: None
3
EOW Easy Comm. Via Radio
Engineering Order Wire To communicate with your colleague on the other side of the radio link, simply connect here your headset

Page 43
External Alarms
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

5
LED Indications
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
LED Indications
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)
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)
8

Page 45
User Channels (2)
Modes of operation: V.11 Asynchronous (9600bps) RS-232 Asynchronous (9600bps) V.11 Synchronous Co-Directional (64Kbps) V.11 Synchronous Contra Directional (64Kbps)
9
User Channels (3)
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
10

Page 46
Protection Port
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.
11
T-Cards (Add-on Mezzanines)
Field upgradeable modules (T-Cards):

16 x E1 T-Card (32 total per unit) DS1 T-Card STM1/OC3 MUX T-Card
12

Page 47
T-Cards (Add-on Mezzanines)
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
13
GbE Ports
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 #2
14
Port #1

Page 48
FE Ports
5 FE ports: Port 3: Port 4: Port 5,6 &7: Data Data or WSC (2 Mbps Wayside Channel) Data or local management
All ports support QoS as in IP-10 (scheduler, policers, shaper, classifiers)
15
Radio and misc.
The Radio port is the switchs 8th port (same as in IP-10)
In addition Grounding -48vdc Power Connector Fan Drawer
16

Page 49
XC using a Shelf Configuration
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
17
XC using a Shelf Configuration

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
18

Page 50
Thank You !
training@ceragon.com
10

Page 51
FibeAirIP10GSeries
Installation
General
If installation requires CFG file upload & download and / or SW file upload & down -
1. 2. 3.
Make sure FTP Server is installed on your PC FTP is configured (RD/WR permissions) Latest SW version is available (FTP root directory)
FTPinstallationguide isavailableat Training.Ceragon.Com: seeModules/ Installation
1
Page 52
Agenda
Site Requirements Packing & Transportation Unpacking Required Tools q 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
2
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 owners 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 When unpacking Wh ki Check the packing lists, and ensure that the correct part numbers and quantities of components arrived.
3
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)
8
4
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: see M d l / Installation Modules I t ll ti
IDU Dimensions
42.60mm
10
5
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 rack kit rack.
11
Installing Nodal Enclosures in a 19 Rack
12
6
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 Main Enclosure
space for maneuvering above and below shelves)
Start the installation process from bottom to top, e.g. Main enclosure should be installed first at the bottom of your rack space
13

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

Step #1: Install the IP-10 Main enclosure in the 19 inch rack using 4 screws. Step #2: Slide down the 2nd extension enclosure. Male connector should plug in smoothly into the Main enclosure.
15

Step #1: Install the IP-10 Main enclosure in the 19 inch rack using 4 screws. Step #2: Slide down the 2nd extension enclosure. Male connector should plug in smoothly into the Main enclosure. Step #3: Slide down the 2nd extension enclosure. Male connector should be plugged in smoothly into the Main enclosure.
16
8
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
17

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
18
9
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.
19
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
20
10
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.
21
Installing a T-Card into an IDU

Remove the IP-10 T-Card blank panel from the IDU, by releasing the 2 side screws.
22
11
Page 62
Installing a T-Card into an IDU

Insert the IP-10 T-Card panel and tighten it using the 2 side screws.
23
Grounding the IDU
Single Point Stud Grounding Wire
24
12
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. t be installed i i l d two star t Th stud must b i t ll d using a UL li t d ring t The t d UL-listed i tongue t terminal, and t washers for anti-rotation.
25
Lightning Protection
For antenna ports, lightning protection is used that does not permit transients of a greater 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.
26
13
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.
27
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 user power supply GND must be connected to the positive pole i th IDU The l tb t d t th iti l in the power supply. Any other connection may cause damage to the system!
28
14
Page 65
Power Requirements
Important Make sure to use a circuit breaker to protect the circuit from damage by short or overload.
29
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.
30
15
Page 66
ThankYou!
16
Page 67
3/14/2010
RFUC&MediationDevices
The Most Comprehensive Portfolio FibeAir Family

RFUs 6-38 GHz
RFU-C
Carrier Ethernet
IP-10 IP-MAX2 3200T
EMS & NMS

PolyView (NMS)
Multi-Service
RFU-HP IP-10 IP-MAX2 640P CeraView (EMS) RFU-P, RFU-SP 1500R/1500P
TDM
3200T
2
Page 68
3/14/2010
IDU RFU Compatibility
RFU-C
IP-10
RFU-P, RFU-SP
1500R
RFU-HP
IP-IP-MAX2
RFU-SP 640P
1500P
3
IDU IDU Compatibility Across Link

1500R 1500R
IP-10 IP 10
IP-10
1500P
1500R
IP-MAX/IP-MAX2
IP-10
1500P chassis Cannot House 1500R IDC and IDMs 1500R chassis Cannot House 1500P IDC and IDMs Must Match IDU Type Across a Link
4
Page 69
3/14/2010
RFU-C direct mount configurations
1+0 direct
5
RFU-C direct mount configurations

1+1 direct
6
Page 70
3/14/2010
RFU-C remote mount configurations
1+0 remote
7
RFU-C remote mount configurations

1+1 remote
8
Page 71
3/14/2010
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
9
RFU-C to NSN antenna
10
Page 72
3/14/2010
RFU-C to Ericsson antenna
(R1A 23GHz)
11
Antenna Alignment (1)
Connect the headset to AGC monitor BNC/TNC connector on ODU 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
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, re-align antenna to remote site
13
training@ceragon.com g@ g ThankYou! Thank You !
14
Page 74
FibeAirIP10GSeries
Setting Management
Agenda
Getting started General notes General commands Command history y Reading current IP Setting new IP Connecting PC to IDU Troubleshooting Factory Defaults
2

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 Stop bits: Flow Control: None
YoumayuseanySerial ApplicationsuchasHyper Terminal PuTTY TeraTerm Terminal,PuTTY,TeraTerm etc
Log on using (admin/admin) for user name and password. Now, you should be able to see the IP-10 CLI Prompt
3
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 concept Some 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
General Commands
IP-10:/ >? IP-10:/ls IP-10:/lsp IP-10:/ > exit / IP-10:/ > cd IP-10:/ > cd ..
Type ? (question mark) to list helpful commands Type ls to list your 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
Command History
Use the arrow keys to navigate through recent commands
Use the TAB key to auto-complete a syntax
6

Page 77
Reading current IP
To read current IP type the following:
IP-10:/>cd management/networking/ip-address/ IP-10:/ management/networking/ip-address>

Note that the prompt has changed. Now, type get ip-address:
IP-10:/ management/networking/ip-address>get ip-address

Upon completion, the current IP will be displayed followed by the new completion displayed, prompt:
IP-10:/ management/networking/ip-address>get ip-address 192.168.1.1 IP-10:/ management/networking/ip-address>

7
Setting new IP
Now, let us set a new IP for the MNG: We assume the required IP is 192.168.1.144 Type set ip-address 192.168.1.144
IP-10:/ management/networking/ip-address>set ip-address 192.168.1.144
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
Connecting IDU to EMS

1. Connect your EMS/NMS to the IDU (port 7) with ETH CAT.5 cable 2. Verify that your PCs IP is in the same subnet 3. 3 Make sure Link is up 4. PING the IDU 5. Launch a WEB browser with the URL set as the IDUs IP
9
Management Troubleshooting
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 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 IDU 6. In case your IDU is connected to a router: set the IDUs Default GW = Router IP 7. 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 Management When OFF = Port is set to Data
10

Page 79
Back to factory defaults

Going back to factory defaults can be done with EMS or CLI In case you need to set factory defaults with CLI type the following -
IP-10:/> cd management/mng-services/cfg-service
In the new directory type the following:
IP-10:/management/mng-services/cfg-service>set-to-default
11
ThankYou!

Page 80
4/16/2010

EMS Performance Monitoring
Agenda
EMS General Information Faults: Current Alarms
Event Log
PM & Counters: Remote Monitoring

TDM Trails TDM interfaces Radio (RSL, TSL, MRMC and MSE) Radio TDM Radio ETH
Page 81
4/16/2010
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
EMS Main View

Graphical MENU: Click to configure
EMS Main View
Protection Status Display & Quick Access Icons
Page 83
4/16/2010
EMS Main View

In this example slot #1 and slot #2 are configured to support 1+1 Protection Slot #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
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 events When Event #201 occurs, Event #1 is erased and #201 is logged as #200.
Page 85
4/16/2010
Available PM Statistics - Radio

TDM PM in Radio (allocated E1s)
TDM (16E1s)
ETH PM (Data + In-Band): 1. Aggregated Errors 2. Throughput 3. Capacity 4. Radio Link Utilization 5. RMON standard is implemented as well to p provide detailed data
Radio PM: 1. RSL 2. MSE 3. MRMC (ACM) 4. Aggregate
11
Available PM Statistics Line Interfaces
STM-1 interface facing customer equipment g q p TDM interfaces facing customer equipment End-to-End Trails
12
Page 86
4/16/2010
Clearing previous data

To erase all IDU PM data, click the CLEAR button -
13
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
PM TDM Trails In Detail

Report Interval: The number of trails in the list is derived from radio link capacity (default license = 10Mbps)
Display 15 minutes intervals or single Daily interval (24 hours) Information can be displayed as a graph
PM RMON Special Registers

RMONregister /Counter Undersizeframesreceived Oversizeframesreceived Oversize frames received Jabberframesreceived Fragmentsframesreceived Rxerrorframesreceived FCSframesreceived InDiscardFrames InFilteredFrames Pauseframesreceived
16
Description Framesshorterthan64bytes Frameslongerthan1632bytes Frames longer than 1632 bytes Totalframesreceivedwithalengthofmorethan1632bytes, butwithaninvalidFCS Totalframesreceivedwithalengthoflessthan64 bytes,andaninvalidFCS TotalframesreceivedwithPhyerror TotalframesreceivedwithCRCerror,notcounteredin "Fragments", "Jabber" or "Rx error"counters Fragments , Jabber or Rxerror counters Countsgoodframesthatcannotbeforwardeddueto lackofbuffermemory Countsgoodframesthatwerefilteredduetoegress switchVLANpolicyrules Numberofflowcontrolpauseframesreceived
Page 88
4/16/2010
Troubleshooting with RMON: Filtering Example

Site A A
Tagging Radio port is a member of VID 100 Radio port is a member of VID 100
Site B A
No membership
Untagged Frames Tagged 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
17
Troubleshooting with RMON: Oversized frames

Site A T T T Site B A
Tagged Frames with frame size > 1632 bytes
When ingress frames exceed the maximum frame size, RMON counter Oversized frames received is updated accordingly
18
Page 89
4/16/2010
Troubleshooting with RMON: Discarding Example

Site A T T T Site B A
Ingress traffic does not comply to Policer rules
Discarding Examples: Ingress rate > Rate Limiter Ingress frames do not qualify to Policer rules
19
Troubleshooting with RMON: Monitoring specific traffic types

Site A
Rate Limiter
Site B T T
Monitor
Video streams are generally transmitted over UDP with multicast addresses To monitor traffic, check out the Multicast Frames Received register To limit MC traffic, assign a Policer with a UDP & MC CIR rules
20
Page 90
10
4/16/2010

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 defect. defect SES is a subset of ES.
Page 91
11
4/16/2010

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
12
4/16/2010

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)

Active Path Seconds (only relevant for Protected SNCP Trails): The number of times seconds the Active Path was available
Page 93
13
4/16/2010

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.
28
Page 94
14
4/16/2010
PM E1 / DS-1 (Radio PM)

Here we can analyze TDM PM through the radio link
29
PM STM-1 Interface
This PM data relates to the STM-1 Line Interface.
30
Page 95
15
4/16/2010
PM Radio
Signal Level RSL & TSL analysis Allows setting RSL & TSL thresholds EMS 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 sec Level 2: 15 sec 900 sec = 15min Interval
Page 96
16
4/16/2010
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
RSL -40
-50 -68 -99 10 5 10 T [sec]
33
PM Radio - Aggregate
Aggregated radio traffic analysis
34
Page 97
17
4/16/2010
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 the active improves, information is updated accordingly.
35
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.
36
Page 98
18
4/16/2010
PM Ethernet
ETH Traffic + Threshold settings: Frame Error Rate Frame error rate (%) measured on radio-Ethernet radio Ethernet interface Throughput data bits measured on radioEthernet 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 p y , ( q y physical hardware). ) 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.
Pre.
SFD
DA
SA
VLAN
ETH Type /Length
Payload+ Padding
CRC
Interframe Gap
7octets
1octet
6octets
6octets 4octets
2octets
461500 4octets octets
12octets
DataRate:min.64 octets max.1522octets Physicalwirerate:min.84octets max.1542octets

38
Page 99
19
4/16/2010

Pre. SFD DA SA VLAN
ETH Type /Length
Payload+ Padding
CRC
Interframe Gap
7octets
1octet
6octets
6octets 4octets
2octets
461500 4octets octets
12octets
DataRate:min.64 octets max.1522octets Physicalwirerate:min.84octets max.1542octets
In case we use a 64 bytes frame: Throughput (Data rate) = ~ 77% of physical transmitted rate Stripped bits = ~ 23% of physical transmitted rate (64/84=0.77) (20/84=0.23)
Hence, when we transmit 100Mbps, the actual throughput would be 77 Mbps

39

Throughput = 77 Mbps
Radio Capacity = (license) = 400Mbps
Transmitted rate = 100 Mbps
Capacity = Received frame rate = 100 Mbps
Utilization = Throughput = 77 = 20 % Radio Capacity 400

40
Page 100
20
4/16/2010
PM Ethernet
Ethernet throughput & Capacity PMs are measured by accumulating the number of Ethernet octets every second Accurate analysis requires accumulating a full interval (15min/24hrs)
41
ThankYou! training@ceragon.com training@ceragon com
42
Page 101
21
6/1/2010

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
Unit Parameters Step # 1
Configure specific information that may assist you later Such info will help you locate your site easier and faster
VDC reading
Page 103
6/1/2010
Celsius (metric) or Fahrenheit (Imperial)

5
By default the time & date are derived from the operating system clock User may set new values These settings are also used for NTP connection (later explained)
Page 104
6/1/2010

IDU Serial number is important when you submit 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
8
Page 105
6/1/2010
Versions
Lets explore this example: The IDU running SW is displayed in the aidu line and currently it is 3 0 92 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 holds all th SW files for all the h ld ll the fil f ll th The components (IDU + ODU) You can see here the different files per ODU type
10
Page 106
6/1/2010
External Alarms Collapsed Input Alarm Config.
Dry Contact Alarms (DB-9): 5 Inputs 1 Output

11
External Alarms Expended Input Alarm Config.
12
Page 107
6/1/2010
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 Quality f S i Q lit of Service W do not h We d t have specific alarms of Q S ifi l f 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.
13
Management Network Properties

Here you can set the Network Properties of the IDU
This is the switch MAC address
If your link is up you should be able to see the other ends IP
14
Page 108
6/1/2010
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 Number of ports =2 Number of ports =1 Number of ports =0
15
Port 7, Port 6, Port 5 Port 7, Port 6 Port 7 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.
16
Page 109
6/1/2010
Management Port Properties
These parameters allow you setting the management capacity t it and port properties
17
Trap Configuration (OSS / NMS / Northbound)
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)
18
Page 110
6/1/2010
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.
19
Licensing Demo License Enabled
Demo License allows you full evaluation of the IDU functionality, features and capacities
20
Page 111
10
6/1/2010
NTP Client Properties

Enable / Disable Type NTP Server IP address Expect IDU to lock on NTP Servers 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 elements real-time clock 3. NA - if not synchronized with any clock (valid only when Admin is set to Disable).
The feature supports Time Offset and Daylight Saving Time. Time Offset and Daylight Saving Time can be configured via WEB (Unit Information page) or via CLI: /management/mng-services/time-service>
21
NTP Properties
22
Page 112
11
6/1/2010
NTP Properties
When using NTP with external protection 1+1, both Active and Standby units sho ld be locked independentl on the NTP ser er and report nits should independently server, 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 configuration, standby main units) are automatically synchronized to the active main units clock.
23
IP Table
Here you can manually set your neighbors network properties
24
Page 113
12
6/1/2010
SNMP
V1 V3
No security Authentication Authentication privacy SHA MD5 No Authentication
25
All ODU
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.
All ODU Disabled
All ODU Enabled
26
Page 114
13
6/1/2010
27
Page 115
14
6/13/2010

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
Configure specific information that may assist you later Such info will help you locate your site easier and faster
VDC reading
Page 117
6/13/2010
Celsius (metric) or Fahrenheit (Imperial)

5
By default the time & date are derived from the operating system clock User may set new values These settings are also used for NTP connection (later explained)
Page 118
6/13/2010

IDU Serial number is important when you submit 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
8
Page 119
6/13/2010
Versions
Lets explore this example: The IDU running SW is displayed in the aidu line and currently it is 3 0 92 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 holds all th SW files for all the h ld ll the fil f ll th The components (IDU + ODU) You can see here the different files per ODU type
10
Page 120
6/13/2010
External Alarms Collapsed Input Alarm Config.
Dry Contact Alarms (DB-9): 5 Inputs 1 Output

11
External Alarms Expended Input Alarm Config.
12
Page 121
6/13/2010
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 Quality f S i Q lit of Service W do not h We d t have specific alarms of Q S ifi l f 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.
13
Management Network Properties

Here you can set the Network Properties of the IDU
This is the switch MAC address
If your link is up you should be able to see the other ends IP
14
Page 122
6/13/2010
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 Number of ports =2 Number of ports =1 Number of ports =0
15
Port 7, Port 6, Port 5 Port 7, Port 6 Port 7 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.
16
Page 123
6/13/2010
Management Port Properties
These parameters allow you setting the management capacity t it and port properties
17
Trap Configuration (OSS / NMS / Northbound)
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)
18
Page 124
6/13/2010
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.
19
Licensing Demo License Enabled
Demo License allows you full evaluation of the IDU functionality, features and capacities
20
Page 125
10
6/13/2010
NTP Client Properties

Enable / Disable Type NTP Server IP address Expect IDU to lock on NTP Servers 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 elements real-time clock 3. NA - if not synchronized with any clock (valid only when Admin is set to Disable).
The feature supports Time Offset and Daylight Saving Time. Time Offset and Daylight Saving Time can be configured via WEB (Unit Information page) or via CLI: /management/mng-services/time-service>
21
NTP Properties
22
Page 126
11
6/13/2010
NTP Properties
When using NTP with external protection 1+1, both Active and Standby units sho ld be locked independentl on the NTP ser er and report nits should independently server, 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 configuration, standby main units) are automatically synchronized to the active main units clock.
23
IP Table
Here you can manually set your neighbors network properties
24
Page 127
12
6/13/2010
SNMP
V1 V3
No security Authentication Authentication privacy SHA MD5 No Authentication
25
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 required enabled Ext power feed.
All ODU Disabled
All ODU Enabled
26
Page 128
13
6/13/2010
27
Page 129
14
3/7/2010

EMS Switch Configuration
Agenda
1. Switch mode review 2. Guidelines 3. Single Pipe Configuration 4. Managed Mode Configuration 5. Managed Mode Common Applications
Page 130
3/7/2010
Switch Modes
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
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 Specific VLAN should be assigned to access the port A range of VLANs should be assigned to access the Port
Allowed Ingress Frames Only Untagged frames (or Tagged with VID=0 "Priority Tagged ) Only Tagged frames
Allowed Egress Frames Untagged frames
Access
Trunk
Tagged frames
Page 131
3/7/2010
Switch Modes
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.
Allowed Ingress Frames Allowed Egress Frames Untagged or C-tag (ether-type= 0x8100) frames. Configurable S-tag. (ether-type) 0x88a8 0x8100 0x9100 0x9200
Type CustomerNetwork
VLANs
Specific S-VLAN should be Untagged frames, or assigned to "Customerframes with C-tag Network" port (ether-type=0x8100). Configurable S-tag. (ether-type) 0x88a8 0x8100 0x9100 0x9200
ProviderNetwork
A range of S-VLANs, or "all" S-VLANs should be assigned to "ProviderNetwork" port
Guidelines
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
Single Pipe Configuration

7
Single Pipe Configuration
Untagged VID 4 VID 100 45 VID 51
IP-10 Switch
Port 1: GbE (Optical or Electrical) Port 3: FE (RJ45)
Port 8 (Radio)
Page 133
3/7/2010
Configuration Single Pipe
This is the default setting
Configuration Single Pipe
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
10
Page 134
3/7/2010
Managed Mode Configuration

11
Configuration Managed Mode

Lets use this diagram as an example Port #2 as Trunk (VID 200)
IDU-B IDU-A
Port #3 as Trunk (VID 300)
Radios as Trunk by default
Port #2 as Trunk (VID 200, VID 300)
12
Page 135
3/7/2010

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)
13

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
14
Page 136
3/7/2010
2 3
4
15
Configuration Managed Mode Common Applications

Tagging / untangling
IP-10
Access Port Radio = Trunk Port Transmits and receives Untagged frames
Transmits and receives Untagged frames
PC
192.168.1.200
PC
192.168.1.100
16
Page 137
3/7/2010
Configuration Managed Mode Common Applications
Radio = Trunk Port
IP-10
Trunk Port
Multiple L2 streams, each identified with unique VID
Traffic Generator
Trunk Port
17
Thank You ! training@ceragon.com
18
Page 138
4/17/2010
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
VLAN TAG Attributes

1. In L2 ETH switching, L2 traffic can be engineered using the VLAN TAG attributes L2 traffic is controlled by defining port membership: Access or Trunk Together, port membership + L2 traffic engineering convert connectionless to connection-oriented network In such networks, services are better deployed and maintained VLAN TAG attributes include: VLAN ID (12 bits) Priority Bits (3 bits) Additional attributes may be used to engineer traffic: MAC DA Port number
2. 3.
4. 5. 5.
3
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 g information 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
Access Port
Let us examine the Tagging / Untagging process of a L2 switch
L2 ETH SW
DA
SA
Type
Payload
FCS
Access Port Tagging ingress frames

Let us examine the Tagging / Untagging process of Port #1
Tagging
Port #1
DA SA VLAN TAG
Port #8
Type Payload FCS
Tagged frame
DA SA Type Payload FCS
Access Port:Untagged frame

6
Page 141
4/17/2010
Access Port
Utagging frames towards customer interfacing ports
When Tagged frame from Network is forwarded to Access port, the VLAN Tag is removed
Untagging
Port #1
DA SA VLAN TAG
Port #8
Type Payload FCS
Tagged frame
DA SA Type Payload FCS
Access Port: Untagged frame

7
Access Port Tagging multiple ports

The switch can individually tag multiple Access ports with same VID or unique VID
Tagging
Port #8 Port #1 Port #2

DA DA SA Type Payload FCS SA Type Payload FCS DA SA SA VLAN TAG = 10 VLAN TAG = 33 Type Type Payload Payload FCS FCS
DA
Access Ports: Untagged frames

8
Page 142
4/17/2010
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
Port #8 Port #1 Port #2

DA DA SA Type Payload FCS SA Type Payload FCS DA SA SA VLAN TAG = 10 VLAN TAG = 33 Type Type Payload Payload FCS FCS
DA
Access ports: Untagged frames

9
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)
Trunk Port
Port #8 Port #2
DA DA DA SA VLAN TAG = 10 Type Type Payload Payload FCS FCS
SA SA
VLAN TAG = 10 VLAN TAG = 33
Type Type
Payload Payload
FCS FCS
SA VLAN TAG DA Untagged frames = 33

10
Page 143
4/17/2010
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)
Type Payload FCS DA SA VLAN TAG = 33 Type Payload FCS
DA
SA
Port #5: Access
Port #8: Trunk Port #2: Trunk

DA DA SA SA VLAN TAG = 10 VLAN TAG = 33 Type Type Payload Payload FCS FCS
DA
SA
VLAN TAG = 10
Type Type
Payload Payload
FCS FCS
SA VLAN DA Untagged frames TAG = 33 11
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)
12
Page 144
4/17/2010
EMS Trunk Configuration
2 3
4
13
14
Page 145
4/21/2010

EMS Metro Switch Configuration
Agenda
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
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 CustomerNetwork VLANs Allowed Ingress Frames Allowed Egress Frames Untagged or C-tag (ether-type= 0x8100) frames. Configurable S-tag. (ether-type) 0x88a8 0x8100 0x9100 0x9200
Specific S-VLAN should be Untagged frames, or assigned to "Customerframes with C-tag Network" port (ether-type=0x8100). Configurable S-tag. (ether-type) 0x88a8 0x8100 0x9100 0x9200
ProviderNetwork
A range of S-VLANs, or "all" S-VLANs should be assigned to "ProviderNetwork" port
Configuration guidelines
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
Network #1
Radio Ports (PN)

Network #2
S-VLAN 9 Network 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
S-VLAN 8 Network 2
Page 147
4/21/2010
Simplified Flow
IP-10
S-VLAN 1000
S-VLAN 222
S-VLAN 1000 S-VLAN 222
PN
Radio Port
CN
CN
ISP / BTS #1 C-VLAN 100 C-VLAN 101 C-VLAN 102

5
ISP / BTS #2 C-VLANs unknown
CN-PN-PN-CN
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
CN CN CN
6
CN
Page 148
4/21/2010
CN-PN-PN-PN
Radio Ports (PN)
S-VLAN 9 BTS 2
S-VLAN 8 BTS 1
CN CN
PN
7
Customer Network
Provider Network
Switch Mode Configuration
2
1. Set mode to Metro (requires reset) 2. Add the S-VLAN ID (set & apply)
Page 149
4/21/2010
CN Port Configuration
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
9
CN Port Configuration
2 1 4 5
10
Page 150
4/21/2010
PN Port Configuration
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
11
PN Port Configuration
2 1 1
4 6 5
12
Page 151
4/21/2010
PN Port Configuration Setting the S-Tag
0x88A8 0x8100 0x9100 0x9200
13
QoS with Metro Switch

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.
14
Page 152
4/21/2010
15
Page 153
4/30/2010
FibeAirIP10Series Commissioning the Radio Link
Radio Link Common Attributes

# Link ID
IP10
IP10
RSL MSE
Received Signal [dBm] 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
2
Page 154
4/30/2010
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
# 102 # 101 Link ID Mismatch
Link ID Mismatch
Page 155
4/30/2010
LINK ID Antenna Alignment Process

Both IDUs of the same link must use the same Link ID Otherwise, Link ID Mismatch alarm will appear in Current Alarms Window
# 101 # 101
# 102 # 101 Link ID Mismatch
Link ID Mismatch
ATPC
Page 156
4/30/2010
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 range power, 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

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 Radio
ATPC module
Radio Transceiver Radio Receiver
Radio Receiver Signal Quality Check
Ref. RSL
Feedback
Site A
RSL required change Site B
ATPC OFF = High Power Transmission
ATPC: Max. TSL: Monitored TSL: Monitored RSL:
Disabled 10 dBm 10 dBm -53 dBm
ATPC: Max. TSL: Monitored TSL: Monitored RSL:
Disabled 10 dBm 8 dBm -56 dBm
ATPC module
Radio
Ref. RSL
Feedback
Site A
10
Page 158
4/30/2010
ATPC ON = Reduced Power, cost & long-term maintenance

ATPC: Ref. RSL: Max. TSL: Monitored TSL: Monitored RSL: Enabled -65 dBm 65 10 dBm 2 dBm (before 10) -60 dBm (before 53) ATPC: Ref. Ref RSL: Max. TSL: Monitored TSL: Monitored RSL: Enabled - 65 dBm 10 dBm 2 dBm (before 8) -63 dBm (before 56)
ATPC module
Radio
Ref. RSL
Feedback
Site A
11
MRMC Adaptive TX Power
Page 159
4/30/2010
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.
13
MRMC Adaptive Power = OFF
256QAM @ Monitored TSL = 18 dBm (Max.)

Signal Degradation = Lower bit/symbol
16QAM @ MAX. TSL = 18 dBm
14
Page 160
4/30/2010
MRMC Adaptive Power = ON
256QAM @ Monitored TSL = 18 dBm(Max.)

Signal Degradation = Lower bit/symbol
16QAM @ Monitored TSL = 24 dBm
15
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 ( q (Power VS. Spectrum): Class 2 Class 4 Class 5B Class 6A FCC RFU C should h i 2.01 (or higher) for ti lit f RFU-C h ld have version 2 01 ( hi h ) f proper f functionality of Adaptive TX Power feature.
The Effective Isotropic Radiated Power (EIRP) is the apparent power transmitted towards the receiver assuming that the signal power is radiated equally in all directions 16
Page 161
4/30/2010
Configuration
Radio Settings Local Radio

Spectrum Mask FQ spacing (gap) between channels Monitored transmission power Monitored recei ed signal received Monitored Mean Square Error Required value = zero
Radio frequencies can be set locally or on remote unit as well (assuming links is up)
Enable / Disable Min. target RSL (local) Enable = no transmission Value depends on MRMC settings Must be identical on both IDUs
18
Page 162
4/30/2010
Radio Settings Local Radio
Enable on both IDUs to get maximum throughput (500Mbps @ 56MHz)
19
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
20
Page 163
10
4/30/2010
Remote Un-Mute
Simplified scheme
Site i Sit B is NOT transmitting t itti but receiver is still ON
Site A is transmitting
Site B
Site A
21
Radio Thresholds
These settings determine the sensitivity / tolerance for triggering: 1+1 HSB switchover Ethernet Shutdown PM generated alarms
22
Page 164
11
4/30/2010
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 these parameters dictate profiles 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.
23
MRMC Configuration
We shall review this page using the following slides:

24
Page 165
12
4/30/2010
MRMC reading current script

MAX. Capacity (w/out compression) ACM Script CH. BW Modulation Spectrum Mask ACM is on
Spectrum Class Type
25
MRMC Reading current capacity
26
Page 166
13
4/30/2010
27
Page 167
14
3/7/2010

Configuring Interfaces
Agenda
Ethernet Interfaces TDM Interfaces AIS Detection AIS Signaling (STM-1) STM-1 Interface Auxiliary Channels Wayside Channel (Various Configurations)
Page 168
3/7/2010
Ethernet Ports Configuration

Configuring ETH ports is discussed in previous modules:
Switch Configuration Trunk VS. Access Metro Switch Configuration QoS Configuration Interface Rate
Single Pipe
ETH 1 (SFP) ETH 2 (RJ 45) ETH 3 (RJ 45) ETH 4 (RJ 45) ETH 5 (RJ 45) ETH 6 (RJ 45) ETH 7 (RJ 45) ETH 8 Radio (N Type) GbE GbE FE 10 / 100 FE 10 / 100 FE 10 / 100 FE 10 / 100 FE 10 / 100 According to Licensed fq. Disabled / Traffic Disabled / Traffic Disabled / Protection Disabled / Wayside Disabled / MNG Disabled / MNG Disabled / MNG Disabled / Traffic
Functionality
Managed SW / Metro
Disabled / Traffic Disabled / Traffic Disabled / Traffic / Protection Disabled / Traffic / Wayside Disabled / Traffic / MNG Disabled / Traffic / MNG Disabled / Traffic / MNG Disabled / Traffic
Ethernet Ports Configuration
Page 169
3/7/2010
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
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
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
10
Page 172
3/7/2010
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
11
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.
12
Page 173
3/7/2010
Auxiliary Interfaces
Up to 19200 baud, Asynchronous RS-232. Up to 19200 baud, Asynchronous V.11.
EOW may be used as a simple solution for on-site communication between two technicians / installers / etc.
13
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.
14
Page 174
3/7/2010
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.
15
OOB MNG in a 1+1 standalone IDUs (Y-Splitter)
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.
16
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".
Page 175
3/7/2010
OOB MNG in a 1+1 standalone IDUs (P. Panel)
17
18
Page 176
3/7/2010

XC / SNCP / Nodal Solution
Introduction
Page 177
3/7/2010
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
SNCP (ITU- G.805)
With Wireless SNCP, a backup VC trail can be optionally defined for each individual VC trail
Main Path
Protective Path
Page 178
3/7/2010
FibeAir IP-10 Integrated Nodal Solution

IP-10 IDU can be used as a Standalone unit (1U) or in as a Nodal Solution
Connecting 2 IDUs requires a nodal enclosure: Best economical future upgrade Best flexibility for network designer Easier to Install / Maintain / expand
The solution is modular and forms a single unified nodal device: Common Ethernet Switch Common E1s Cross Connect Single IP address Single element to manage
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
Nodal enclosure Rear
Page 179
3/7/2010
FibeAir IP-10 Nodal Enclosures

Extension nodal enclosure
Main nodal enclosure
FibeAir IP-10 Scalable Nodal Enclosures

Pay as you grow !
Page 180
3/7/2010
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
Integrated Ethernet Switching Integrated TDM cross-connect

M E
Main unit Expansion unit
M M
Native2 1+1 HSB
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+0 Native2 1+0
Integrated Ethernet Switching Integrated TDM cross-connect

M E
E E E E
Native2 2+0/XPIC
Main unit Expansion unit
M M
Native2 1+1 HSB
Page 181
3/7/2010
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
12
Page 182
3/7/2010

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)
13

Identify Trail interfaces prior to configuration Note that Trail configuration is Bi-Directional !
Trail starts here: For SNCP we shall need to define 3 interfaces
Trail traverses through here: We shall need to define 2 interfaces
IP-10
IP-10
Bypass site
Protected Trail
(Automatic)
IP-10
Radio Link
14
Trail starts here: For SNCP we shall need to define 3 interfaces
Page 183
3/7/2010

Pay attention to the order of configuration:
2
The Trail Start/End points should be configured first (interface #1)
1 IP-10 3
Bypass site
IP-10
Interfaces #2 and #3 can be configured in a random order
Protected Trail (Automatic)
2 IP-10 1
15
Standalone non-protected Trail Configuration
Page 184
3/7/2010
Step #1: Access Trail Page
Click on the Add button
17
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.
In this example we selected the SDH connector. Your next step would be selecting the VC number.
18
Page 185
3/7/2010
Step #3: Configure 2nd Interface

Click on the 2nd interface connector
In this example we selected the 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
19
Step #4: Configure Trail Attributes

Make sure Trail ID is unique and identical on all sites/trails
20
Page 186
10
3/7/2010
Step #5: Trail Verification

If your settings are correct, trail alarms should disappear, trail path is ready to be tested
21
SNCP Trail Configuration in a Node
Page 187
11
3/7/2010
Selecting Main IDU for Trail Configuration

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
23
SNCP Trail in Nodal Architecture

PDH interface
Bypass Node
IP-10 IP-10
IP-10
SDH interface
24
Page 188
12
3/7/2010
1st Node
PDH interface IP-10 IP-10 Bypass site Radio CH #1 Radio CH #26 IP-10
SDH interface #1
25
Bypass Node
Radio CH #48
PDH interface IP-10 Bypass Node IP-10
Radio CH #1
IP-10
SDH interface
26
Page 189
13
3/7/2010
3rd Node
Radio CH #48
PDH interface IP-10
Bypass site
IP-10
Radio CH #26
IP-10
SDH interface
27
28
Page 190
14
4/30/2010
FibeAir IP-10 Series

Automatic State Propagation
Agenda
Introduction Interfacing IP-10 with external devices VS. Configuration VS Functionality Dead Lock Example ASP in Managed / Metro Mode
Page 191
4/30/2010
Introduction
Automatic State Propagation ("GigE Tx mute override") enables propagation of radio failures 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
Needtofind alternativepath
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 raised 2. Enable Remote Fault to mute local transmitter in case of remote LOF / Link ID mismatch & LOC 3. Enable Local Excessive BER recommended but not necessary
Page 192
4/30/2010
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 & LOC 3. Disable Local Excessive BER - to avoid a dead lock scenario
Example: Avoiding Dead Lock in Single Pipe

Site B Site A
TX
RX
RX
TX
1. GbE FO breaks down or disconnects at the ingress port of Site A
Page 193
4/30/2010

Site B Site A
TX
RX
LOC
RX
TX
1. GbE FO breaks down or disconnects at the ingress port of Site A 2. LOC alarm is raised

Site B Site A
TX
RX
LOC
RX
TX
1. GbE FO breaks down or disconnects at the ingress port of Site A 2. LOC alarm is raised 3. LOC alarm triggers Site A to shut down its transmitter (TX Mute)
Page 194
4/30/2010

Site B Site A
TX
RX
LOC
LOC
RX
TX
1. GbE FO breaks down or disconnects at the ingress port of Site A 2. LOC alarm is raised 3. LOC alarm triggers Site A to shut down its transmitter (TX Mute) 4. Site B detects silence on ingress port and declares LOC

Site B Site A
TX
X X
RX
LOC
LOC
RX
TX
1. GbE FO breaks down or disconnects at the ingress port of Site A 2. LOC alarm is raised 3. LOC alarm triggers Site A to shut down its transmitter (TX Mute) 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
10
Page 195
4/30/2010
Automatic State Propagation in Single Pipe
11
Single Pipe - Propagation Criteria

Using Optical GbE (SFP)
Local and remote IDUs must have identical settings: 1. 2. 3. ASP Enabled ACM profile threshold Excessive BER enabled
LocalCriteria: Local Criteria: LOC(GbE) RadioLOF LINKIDMismatch ExcessiveBER ACMprofileisbelowthreshold
Actions: Muteport1(GbESFP)
Actions: Muteport1(GbESFP)
12
Page 196
4/30/2010

Using Electrical GbE (RJ45)
LocalCriteria: L l C it i RadioLOF LINKIDMismatch ExcessiveBER ACMprofileisbelowthreshold
Actions: ShutdownElec. port
Actions: ShutdownElec. port
13

Using Electrical GbE (RJ45)
LocalGbE Criteria: LOC
Port i l i ll l P t is logically closed b t not d but t shut down LOC will not trigger port shut down (it will not be possible to enable the port when LOC is cleared) Remote LOC will not trigger port shut down (it will not be possible to enable the port when LOC is cleared)
14
Page 197
4/30/2010
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.
16
Page 198
4/30/2010
Managed / Metro - Propagation Criteria

Local and remote IDUs must have identical settings: 1. 2. 3. LocalCriteria: RadioLOF LINKIDMismatch ExcessiveBER ACMprofileisbelowthreshold ASP Enabled ACM profile threshold Excessive BER enabled
8 Actions: ShutdownRadio
17
Managed / Metro - Propagation Criteria

Localcriteria: GbE LOC
8 Actions: Noactiontaken ShutdownRadio
18
Page 199
4/30/2010
19
Page 200
10
6/14/2010
FibeAir IP10
1+1 Protection
Agenda
IntroductiontoExternalProtection IntroductiontoShelfProtection Introduction to Shelf Protection Guidelines ExternalProtectionProcess:1+1fromscratch ExternalProtectionProcess:Upgrading1+0to1+1 Troubleshooting
Page 201
6/14/2010
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 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
In this example 1+1 Protection is only deployed at one site

f1 - high
IDU
f1 - low
Shelf Protection
When enabling a Shelf Protection, the following rules should be applied:
Shelf backplane replaces the external Protection Cable Th There i only one IP address f each of th pair units is l dd for h f the i it 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)
6
In this example Protection is configured in every pair of IDUs (slots)
5 4 3 2 1
IDU
IDU
IDU
Page 202
6/14/2010
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 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
Configuring external 1+1 from scratch
Configuring external 1+1 from scratch (1)

1. Set all IDUs to factory defaults 2. When IDUs 2 Wh IDU complete th b ti sequence, verify: l t the booting if
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.
8
Page 204
6/14/2010

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. Install d 6 I t ll 2nd IDU i each site (no need to configure it) in h it
ODU ODU
ODU
9
ODU

7. Enable protection in 2nd IDU in each site 8. Connect ETH Cross Cable between both protection ports
ODU ODU
ODU
ODU
9. Disconnect the MNG cables. 10. Connect the PC to IDUs via ETH Y-Cable:
ODU ODU
PC
ODU ODU
10
Page 205
6/14/2010

11. Verify Active IDU shows Mates 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.
11
Upgrading (1+0) to (1+1)
Page 206
6/14/2010

1. Assuming 1st link operates well, configure the 2nd IDUs to match Active IDUs:
2nd 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 Actives 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
Standby Link (not connected)

ODU ODU
13

2. Enable Protection on Active IDUs (management will be lost for 60 sec) 3. Lock Protection 3 L k P t ti on b th A ti IDU (to avoid unnecessary switchover both Active IDUs
when 2nd IDU is enabled)
4. Install 2nd IDU in each site (verify TX is muted before physical installation)
ODU
ODU
ODU
ODU
14
Page 207
6/14/2010

5. Enable protection in 2nd IDU in each site 6. Connect ETH Cross Cable between both protection ports
ODU ODU
ODU
ODU
7. Disconnect the MNG cables. 8. Connect the PC to IDUs via ETH Y-Cable 9. Cancel TX mute on both Mate IDUs
15

10. Verify Active IDU shows Mates 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 15. Repeat steps 10 to13 16. Unlock protection on Active IDUs 17. Initiate Manual Switchover / Forced Switchover: verify traffic is OK.
16
Page 208
6/14/2010
Troubleshooting Protection
Common issues followed by CLI commands
Troubleshooting
Alarm/Error ProbableCause/Workaround 1. Protection cableisnotconnected 2. ETHstraightcableisconnectedinsteadof cross cable crosscable 3. Oneofthe2IDUsisnotconfiguredin Protection
Protection LED is on (RED) LEDison(RED)
CheckCFGofbothIDUs:HW,SW,switchmode, CurrentAlarmsshow Configuration managementmode,InBandVID Mismatchalarm InitiateCopytoMateinActiveIDUs IcannotPINGtheSTBYunit. MainIDU doesnotrespondto PING Thisisnormalbehavior, Matecannotbe accesseddirectly,onlyviaActiveIDU UseCLIcommandstoverifythisIDUisinSTBY mode,ifso,useCLItorecoverIDU
CheckthecurrentalarmsofSTBYIDU CurrentAlarmsshows MateComm. ReportbacktoCeragonSupport Failurealarm ReplaceSTBYunit ReplaceActiveunit

18
Page 209
6/14/2010
Troubleshooting Useful CLI Commands

General commands:
lsp ls cls prints executable commands in current directory prints available child directories child-directories clears screen
To execute Protection commands, you will need to change directory:

IP-10:/> cd platform/mate-idu Then, Then to read current status of IDU type the following (in blue): IDU, IP-10:/platform/mate-idu> get protection-mode The system return these values: 1. Active 2. Standby
19

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>
20
Page 210
10
6/14/2010

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
21
22
Page 211
11
3/7/2010

Loopback Maintenance
Agenda
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
RFU RF Loopback
RFU RF LB
RFU RF Loopback
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
IF Loopback
IDU IF LB
IF Loopback
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
IF Loopback Analysis using Event Log

Lets assume radio link is down LINK LED is RED 16:29:01 16:29:05 16:30:01 16:30:05 We enable IF LB, therefore Link alarms clear Loopback replaces remote unit therefore alarm disappears Loopback automatically stops, link recovers to original state Radio link is down (original state)
PDH Line LB towards Line (NE)
LB towards the line
Page 215
3/7/2010
PDH Line LB towards Line (Near End)

Use this feature to evaluate connection to customers patch-panel Alarm is displayed in CAS:
and in Event Log:
PDH Line LB towards Radio (FE)
LB towards the radio
Tester
10
Page 216
3/7/2010
PDH Line LB towards Radio Event Log Analysis

Lets assume PDH port #1 is enable but not connected Therefore, Major alarm is on (RED)
16:59:44 16:59:46 17:06:37 17:06:38
We enable Line LB towards the radio Loopback replaces end-device therefore alarm disappears Loopback is OFF PDH port alarm is ON again..
11
SDH Line LB towards System

Towards System signal (trail) is looped back to IP-10
12
Page 217
3/7/2010
SDH Line LB towards Line

Towards Line signal (trail) is looped back to customer interface
13
IDU-RFU Interface Monitoring
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
14
Page 218
3/7/2010
15
Page 219
3/7/2010

EMS Backup Maintenance
Agenda
In this module we shall describe the various actions we can perform to properly maintain and troubleshoot the IP-10G system using: 1. 2. 3.
2
Configuration File Unit Information File FTP Server

Page 220
3/7/2010
Configuration File
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

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
Local FTP Server

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

You may assign a remote server to host the configuration and unit files
EMS PC
Remote FTP Server
Page 222
3/7/2010
FTP Root Directory

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).
Examples for SW packages
Examples for CFG & Unit Files

7
Configure your FTP Server Properties
2
8
Page 223
3/7/2010
Upload / Download using standalone IP-10G

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

Click Create Archive to allow the IP-10G zipping all parameters into one file
10
Page 224
3/7/2010
Wait till task is successfully completed
11

Next step: Click Upload Archive to allow the IP-10G transferring the zipped file to your server
12
Page 225
3/7/2010

Wait till task is successfully completed
13
Check your FTP Root Directory
This is your copy of the configuration file You may place it now in the dedicated folder (Configuration Files)
14
Page 226
3/7/2010

Follow the same steps to upload the Unit Information file:
1
15
2
Check your FTP Root Directory
This is a copy of your Unit Information file
16
Page 227
3/7/2010
Downloading the CFG File (Server IP-10G)

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 !
1
17
2
Upload / Download in a shelf

18
Page 228
3/7/2010
Shelf Backup: Creating the Nodal Shelf Backup

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
19
Shelf Backup: Creating the Nodal Shelf Backup
First you need to create the CFG files. To do so, select the unit(s) and click the relevant Backup button
20
Page 229
10
3/7/2010
Shelf Backup: Upload from IP-10G to Server

Next, click Upload Archive(s) and the file(s) will be uploaded to your FTP root directory
21
Shelf Backup: Download from Server to IP-10G
To download a file to a certain slot, select the unit number and click this button
22
Page 230
11
3/7/2010
Unified Unit Information File
A unified file is created for all stacked units Upload & Download action are identical to a standalone unit
23
Checking Backup History & Status
Click here to see the backup history

24
Page 231
12
3/7/2010
Checking Backup History & Status
25
Setting the unit back to Factory Defaults
You can restore your system to factory defaults You may also set the IP address to factory default address (192.168.1.1)
26
Page 232
13
3/7/2010
27
Page 233
14
4/21/2010

EMS Software Upgrade
Agenda
FTP Properties Standalone SW Download Standalone SW Upgrade Nodal IDU SW Download Nodal IDU SW Upgrade Rollback VS. Downgrade
Page 234
4/21/2010
Local FTP Server

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

If you do not have an FTP Server installed locally on your PC, you may configure an IP address of a remote server.
EMS PC
Remote FTP Server

Page 235
4/21/2010
FTP Root Directory

Make sure you are familiar with your FTP Root Directory: this is where the files are stored (software versions, CFG & Unit).
Examples for SW packages
Configuring FTP Server Properties
Page 236
4/21/2010
Configuring FTP Server Properties
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
Page 237
4/21/2010
Standalone SW Download
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
Standalone SW Download
Download was successfully completed, you may proceed to upgrade the IDU
10
Page 238
4/21/2010
Download completed Upgrade delayed

In case Upgrade is scheduled for later moments, the Version table will display the following status:
11
Standalone Upgrade
Click on the Upgrade button. When upgrades completes successfully, the IDU will restart automatically.
You may view at any time the upgrade process by clicking on the Log Icon
12
Page 239
4/21/2010
SW Upgrade in a shelf (Node)
13
Shelf Configuration
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
Slot 4 Slot 3 Slot 2 Slot 1
14
Page 240
4/21/2010
Shelf SW Download
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 process by clicking on the Log Icon
15
Shelf SW Upgrade
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
16
Page 241
4/21/2010
Shelf SW Upgrade
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
17
Rollback VS. Downgrade
18
Page 242
4/21/2010
Rollback
1
Upgrade #1
2
Upgrade #2
2.8.25
2.8.31 2.8.32
Rollback
2.8.35
3
Downgrade
Rollback does not revert previous Downgrade operation ! It rolls back IDU version 1 step back (prior to last Upgrade)
19
20
Page 243
10
3/7/2010

EMS Security Configuration
Agenda
SSH HTTPS SFTP Users & Groups Password
Page 244
3/7/2010
Security Configuration
Update 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-10s "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, hmacripemd160, 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
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 IDUs 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
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
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 IDUs 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
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
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
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
17
Page 252
6/13/2010
FibeAir Outdoor Enclosure

Same 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 IP-10/IP-10G Series 1500R Roof top, wall, or pole
Support for the same FibeAir product line used for indoor deployment
Installation anywhere
Passive heat exchange - no need for air conditioning systems External battery backup solution with enclosure (Optional) Heating unit for frigid environments
CERAGONNETWORKSLTD.
Proprietary and Confidential information of Ceragon Networks Ltd
Page 253
6/13/2010
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 Site l Sit lease or acquisition savings i iti i 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
Lower overall costs
IP-55 certification for water and dust proofing
Elegant, Easier to Install & Maintain Solution

CERAGONNETWORKSLTD.
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+0 HSB, 2+0, 4+0 TDM XC / grooming Packet switch solution All interfaces N*E1/T1 N*Ethernet interfaces (FE, GbE) STM-1
CERAGONNETWORKSLTD.
Page 254
6/13/2010
Outdoor Enclosure Practical experience

External alarm inputs for external fans and door opening Sunshade for solar radiation protection Door stopper Installation h k I t ll ti hooks Documentation pocket Door Lock Pole mount option or wall mount option Light weight Battery Backup option
CERAGONNETWORKSLTD.
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 ( p (dust & water) ) 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) 489-4 CB IEC 60950-1 (Safety)
CERAGONNETWORKSLTD.
Page 255
6/13/2010
IPprotectionclasses that mean ? IP 55 What does

First Characteristics Numeral IP XY - Foreign Bodies Protection, Solids Index Protection against Human/Tool Contact No special protection Back of hand, Fist Finger Tools and wires etc with a thickness >2.5mm Tools and wires etc with a thickness >1mm Large foreign bodies, diam. >50mm Medium-sized foreign bodies, diam. >12 Small foreign bodies, diam. >2.5mm Protection against solid objects (foreign bodies)
0 1 2 3
Granular foreign bodies, diam. >1mm g ,
Complete protection, Dust protected; dust deposits are permitted, but their (limited ingress permitted) volume must not affect the function of the unit. Complete protection Dust-proof
7
CERAGONNETWORKSLTD.
IPprotectionclasses that mean ? IP 55 What does

Second Characteristics Numeral IP XY - Water Protection, Liquids Index 0 1 2 3 4 5 6 High pressure jets from all directions, (limited ingress permitted) 7 8 Permanent Immersion, under pressure Temporary immersion, 15 cm to 1m Protection against water No N special protection i l t ti Water dripping/falling vertically Water sprayed at an angle (up to 15 degrees from the vertical) Spray water (any direction up to 60 degrees from the vertical) Spray water from all directions, (limited ingress permitted) Low pressure water jets from all directions, (limited ingress permitted) Condensation/Light rain Light rain with wind Heavy rainstorm Splashing Hose down, residential Hose d H down, commercial. eg. Ship decks Immersion in tank For use on Titanic recovery vehicle
8
CERAGONNETWORKSLTD.
Protection from condition
Page 256
6/13/2010
Outdoor Enclosure Design - external

D W
General Dimensions H: 18.5 in / 47 cm W: 24 in / 61 cm D: 17 in / 43 cm Weight 55 Pounds / 25Kg
CERAGONNETWORKSLTD.
Accessories list
Marketing Model
OE-Enclosure OE-Pole-Installation OE-Heater OE H t OE-Ext-Fans OE-Fan-Drawer-Kit OE-Ext-Power-CBL-15M ODE-NTYPE-JUMPER-CBL-3M OE-Ext-Alarms-CBL-0.45M IP10-OE-CBL-ETH-RJ45-15m CBL-OE-E1-RJ45-RJ45-15m CBL-OE-T1-RJ45-RJ45-15m IP10-OE-CBL-ETH-RJ45-XED-15m CBL-OE-E1-RJ45-RJ45- XED-15m CBL-OE-T1-RJ45-RJ45- XED-15m OE-Sealing-Compound-1.5M FA Outdoor Enclosure FA Outdoor Enclosure Pole installation FA Outdoor Enclosure heater O td E l h t FA Outdoor Enclosure external fans Outdoor Enclosure Fan Drawer Kit Outdoor environment power cable (-48V). Ferrule-Ferrule 15m Outdoor Enclosure IF Jumper Cable 3m Outdoor Enclosure External alarms cable, D-9M - D-9F, 0.45M IP-10 ETH Outdoor RJ45 cable 15m, straight IP-10 E1 Outdoor RJ45 cable 15m, straight IP-10 T1 Outdoor RJ45 cable 15m, straight IP-10 ETH Outdoor RJ45 cable 15m, Cross IP-10 E1 Outdoor RJ45 cable 15m, Cross IP-10 T1 Outdoor RJ45 cable 15m, Cross Outdoor Enclosure sealing compound
Marketing Description
(*) all IP-10 standard accessories can be used. Enclosure space should be taken into consideration
CERAGONNETWORKSLTD.
Page 257
6/13/2010
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 users 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: info@ceragon.com 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: infous@ceragon.com
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: infoeuro@ceragon.com 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
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:
FibeAir IP-10 License Management System
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
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:
CeraView User Guide
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.
CeraView User Guide
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.
CeraView User Guide
Page 268
Search for Devices In the main device list web page, you can click Search registered in the system. to locate a particular device that is
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 .
CeraView User Guide
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 The following web page appears: .
In this web page, only the devices you selected will appear.
Page 271
10
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 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 Value 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Description IP10-CAP-010 IP10-CAP-025 IP10-CAP-050 IP10-CAP-100 IP10-CAP-150 IP10-CAP-200 IP10-CAP-300 IP10-CAP-400 IP10-UPG-025-050 IP10-UPG-025-100 IP10-UPG-025-150 IP10-UPG-025-200 IP10-UPG-025-300 IP10-UPG-025-400 IP10-UPG-050-100 IP10-UPG-050-150 IP10-UPG-050-200 IP10-UPG-050-300 IP10-UPG-050-400 IP10-UPG-100-150 IP10-UPG-100-200 IP10-UPG-100-300 IP10-UPG-100-400 IP10-UPG-150-200 IP10-UPG-150-300 IP10-UPG-150-400 IP10-UPG-200-300 IP10-UPG-200-400 IP10-UPG-300-400 Name in License Management Site Feature disabled Radio Cap. Upgrade 10->25 Mbps Radio Cap. Upgrade 10->50 Mbps Radio Cap. Upgrade 10->100 Mbps Radio Cap. Upgrade 10->150 Mbps Radio Cap Upgrade 10->200 Mbps Radio Cap Upgrade 10->300 Mbps Radio Cap Upgrade 10->400 Mbps Radio Cap. Upgrade 25->50 Mbps Radio Cap. Upgrade 25->100 Mbps Radio Cap. Upgrade 25->150 Mbps Radio Cap. Upgrade 25->200 Mbps Radio Cap Upgrade 25->300 Mbps Radio Cap Upgrade 25->400 Mbps Radio Cap. Upgrade 50->100 Mbps Radio Cap. Upgrade 50->150 Mbps Radio Cap. Upgrade 50->200 Mbps Radio Cap Upgrade 50->300 Mbps Radio Cap Upgrade 50->400 Mbps Radio Cap. Upgrade 100->150 Mbps Radio Cap. Upgrade 100->200 Mbps Radio Cap Upgrade 100->300 Mbps Radio Cap Upgrade 100->400 Mbps Radio Cap. Upgrade 150->200 Mbps Radio Cap Upgrade 150->300 Mbps Radio Cap Upgrade 150->400 Mbps Radio Cap Upgrade 200->300 Mbps Radio Cap Upgrade 200->400 Mbps Radio Cap Upgrade 300->400 Mbps
CeraView User Guide
Page 272
11
ACM
License Type 1 1 Value 0 1 IP10-ACM Description Name in License Managament Site Feature disabled ACM
Networking (Metro Switch Enabled)

License Type 2 2 Value 0 1 IP10-Metro Description Name in License Management Site Feature disabled 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
12
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.
CeraView User Guide
Page 274
13
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
14
Click Continue to go back to the device list page. The device list page will appear with the updated information.
CeraView User Guide
Page 276
15
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 following web page 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
16
Click the number in the Qty Generated column for a list of licenses used to generate keys.
CeraView User Guide
Page 278
17
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
18
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.
CeraView User Guide
Page 280
19
Page 281
20
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.
CeraView User Guide
Page 282
21
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
22
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 define a new user, click New
.
to locate a particular user. The following page appears:
CeraView User Guide
Page 284
23
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
24
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.
CeraView User Guide
Page 286
25
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
26

IP 10G BASIC Course Handbook v3 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IP 10G BASIC Course Handbook v3 1

Uploaded by

Copyright:

Available Formats

IP-10G Basic Course

Visit our Customer Training Portal at Training.Ceragon.Com or contact us at training@ceragon.com

Ceragon Training Agenda

Ceragon Training Agenda

Ceragon Training Agenda

Ceragon Training Agenda

Ceragon FibeAir Family

Carrier Ethernet Switch ACM

TDM Cross Connect

Radio Ethernet + TDM

Proprietary and Confidential

CERAGON MAST - Mobile Architecture for Service Transport

PDH xDSL Subscribers IPDSLAM IP/ETH Customer Network SDH/SONETRING PSTN

CERAGON MAST - Mobile Architecture for Service Transport

FibeAir IP-10R1 Main features

IP-10R1 Integrated Carrier Ethernet switch

Ethernet User Interfaces

Ethernet User Interface

Metro/Managed switch mode

Smart pipe mode

Proprietary and Confidential

IP-10R1 radio capacity - ETSI

Wireless Carrier Ethernet Ring

Wireless Carrier Ethernet Ring

Integrated Ethernet Switching

Native2 Microwave Radio Technology

NG-SDH/SONET complementary solution

Native Ethernet Ethernet over SDH/SONET

RNC FibeAir IP-10

Ethernet services are mapped over SDH/SONET

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

IP/MPLS complementary solution

Native Ethernet Ethernet PWs or IP routing

IP-10R1 integrated QoS support - overview

Priority Queues W1 - Hi h t priority Highest i it

Advanced ingress traffic rate-limiting

Support differentiated Ethernet services with SLA assurance

IEEE 802.1ag CFM (Connectivity Fault Management)

Proprietary and Confidential

FibeAir IP-10G IDU: A Nodal Solution

Proprietary and Confidential

FibeAir IP-10G IDU: A Nodal Solution

Proprietary and Confidential

Craft Terminal (DB9)

External Alarms (DB9)

16 x E1s (optional) Protection Interface (RJ45) 5 x FE Electrical (RJ45)

RFU interface (N-Type)

GND Power -48V DC

Proprietary and Confidential

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

4 E1s 25M Eth 4 E1s 25M Eth

(22 E1, 50M) 1+1 1+0

1 1 1+1 (44 E1, 100M)

(22 E1, 50M)

(22 E1, 50M)

(44 E1, 100M)

4 E1s 25M Eth

(22 E1 E1, 50M) 1+0

4 E1s 25M Eth

IP-10 F-Series IP-10 G-Series IP-10 G-Series with XPIC

4 E1s 25M Eth

Native2 1+0 Ring (Up to 75 E1 or 500Mbps Eth) 1+0

4 E1s 25M Eth