Presentation of New Features

Y Yoga A
August 2012

Key Features of IP-10E aka IP-10R3

Added 2 x GBE Optical/Electrical combo port

Bigger FPGA
Separate port for protection
Customizable Queue Size
Enhanced Traffic Manager
Enhanced Header Compression (in SW 6.9)

Software Version
SW 6.9 has been successfully tested, pending
approval.
Cannot use IP-10R3 software with IP-10R1, so
it is very important software upgrade task
must be carefully monitored
If used, can cause memory corruption & need
to send for repair

Front Panel Overview

Lets go over the front panel connections of the IP-10 E-Series

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

CLI Serial Connection

DB9 Craft Line Interface (CLI)

Baud: 115200
Data bits: 8
Parity: None
Stop bits: 1
Flow Control: None
5

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

6

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

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

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

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 #1
10

Port #2

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)

11

Radio and misc.

The Radio port is the switchs 8th port (same as in IP-10)

In addition
Grounding
-48vdc Power Connector
Fan Drawer

12

IP-10R1 Vs G-Series Vs E-Series

IP-10 R1

G-Series

E-Series

13

Unit Parameters

Licensing Copy, Paste, Ready to

start
Licenses are generated per IDU S/N (capacity / ACM / switch mode)
License upgrade requires system reset.

15

Versions - IDU

16

Versions - ODU

17

Licensing: General
In order to upgrade license, license-key must be entered to the system (requires coldreset)
When system is up, its license key is checked, allowing access to new capacities and/or
features
If license key is illegal (syntax errorillegal S/N) specific alarm will be raised
When "License Violation" alarm is raised, Radio port capacity is automatically limited
to ~3Mbps, allowing only management channels to remote end
To clear the violation alarm, user must configure the system to comply with the loaded
license, and then, issue cold-reset (radio resumes full operational status if the
violation is no longer relevant)

18

Radio - EMS Configuration

Radio Settings Local Radio

20

Radio Settings Local Radio - 2

21

ATPC Local Radio - 3

22

Radio Settings Local Radio 4 Disabling IF

As explained in previous slide, enabling or disabling the IF interface

requires a reset

23

Radio Settings Local Radio 5 Disabling IF

MRMC

Enhanced Header Compression

(SW 6.9)

1+1 Protection Configuration

Configuring external 1+1 from scratch

(1)
1. Set all IDUs to factory defaults
2. When IDUs complete the booting sequence, verify:

All IDUs have the same HW version (same P/N)

All IDUs have the same SW version
All IDUs have the same license
Every IDU has unique IP address (within the same subnet)
Active and STBY have the same SW mode (Pipe / Managed / Metro)
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.
28

Configuring external 1+1 from scratch

(1)
3. Install the first 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 second IDU is enabled)
6. Install second IDU in each site (no need to configure it)

29

ODU

ODU

ODU

ODU

Configuring external 1+1 from scratch

(1)
7. Enable protection in second 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:

30

ODU

ODU

ODU

ODU

Configuring external 1+1 from scratch

(1)
11. Verify Active IDU shows Mates IP address
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. Verify there are no Configuration Mismatch alarms
16. Unlock protection on Active IDUs
17. Initiate Manual Switchover / Forced Switchover: verify traffic is OK.

31

1+1 Protection Configuration

1. Configure unique IPs to slot 1 and slot 2 (when not in installed in shelf)
2. You may use a floating IP
3. Make sure all IPs are in the same subnet

32

EMS GUI

Select 1+1 HSB and then click Apply

The IDU will block management for 60 seconds to allow setting up
the correct mode (Active or STBY)
This action is not traffic effective.

33

EMS GUI
Protection
mode
status

When 2nd IDU is

properly
configured and
connected, IP
and MAC are
displayed here

34

EMS GUI
Click here to check
communication
with STBY unit

35

EMS GUI

To force a switchover
regardless to 2nd IDU
qualifying status
change to ON and click
Apply

36

Admin State Lock

EMS GUI

To request a switchover
click here.
If 2nd IDU (Mate) does not qualify to Active state,
request is ignored.

37

EMS GUI

Click here to copy the configuration from

Active to Mate
Please note
The following parameters are not copied :
MNG mode (In-Band / OOB)
In-Band VLAN
Switch mode
license

38

Trunk Vs. Access Vs. Hybrid

I6.8

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

40

VLAN TAG Attributes

1.

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

attributes

2.

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

3.

Together, port membership + L2 traffic engineering convert connectionless to

connection-oriented network

4.

In such networks, services are better deployed and maintained

5.

VLAN TAG attributes include:

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

6.

Additional attributes may be used to engineer traffic:

MAC DA
Port number

41

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

42

Access Port

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

L2 ETH SW

DA

43

SA

Type

Payload

FCS

Access Port Tagging ingress frames

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

Tagging

Port #8

Port #1
DA

SA

VLAN TAG

Tagged frame
DA

SA

Type

Payload

Access Port:Untagged frame

44

FCS

Type

Payload

FCS

Access Port
Utagging frames towards customer interfacing ports

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

Tagging

Port #8

Port #1
DA

SA

VLAN TAG

Tagged frame
DA

SA

Type

Payload

Access Port:Untagged frame

45

FCS

Type

Payload

FCS

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

Payload
FCS
DA SA Type
SA Type
Payload
FCS

Access Ports: Untagged frames

46

DA

SA
SA

VLAN TAG = 10
VLAN TAG = 33

Type
Type

Payload
Payload

FCS
FCS

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

Payload
FCS
DA SA Type
Payload
FCS
DA SA Type

Access ports: Untagged frames

47

DA

SA
SA

VLAN TAG = 10
VLAN TAG = 33

Type
Type

Payload
Payload

FCS
FCS

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

SA
VLAN
TAG = 33
DA Untagged
frames
48

Type
Type

Payload
Payload

FCS
FCS

SA
SA

VLAN TAG = 10
VLAN TAG = 33

Type
Type

Payload
Payload

FCS
FCS

Trunk & Access Extracting frames out of a

Trunk

SA

DA

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

Port #5: Access

Port #8: Trunk

DA

Port #2:
Trunk

DA

SA

VLAN TAG = 10

SA
VLAN TAG = 33
DA Untagged
frames
49

Type
Type

Payload
Payload

DA

FCS
FCS

SA
SA

VLAN TAG = 10
VLAN TAG = 33

Type
Type

Payload
Payload

FCS
FCS

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)

50

Access + Trunk Port = Hybrid Port

Hybrid Port is a combination of access port which is aware of a single

VLAN only and trunk port that allows multiple VLAN

Ingress untagged traffic is tagged with default VLAN

Ingress tagged traffic passes through based on VLAN membership
configuration

Egress tagged traffic with default VLAN is untagged

Egress tagged traffic passes through based on VLAN membership
configuration

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

different ports

51

Extracting Frames Out of an Hybrid Port

DA

A certain VLAN can be extracted out of a Hybrid assigned with specific VLAN
membership (Default VID)

SA

VLAN TAG = 43

Type

Payload

FCS

Port #2:
Hybrid

Port #8: Trunk

DA

SA
SA

DA
DA

SA

Type

Payload

SA

VLAN TAG = 10

SA
VLAN TAG = 33
DA Untagged
frames
52

VLAN TAG = 33

Type
Type

Payload

FCS

Payload

FCS

FCS
DA

DA

VLAN TAG = 10

Type
Type

Payload
Payload

FCS
FCS

SA

VLAN TAG = 43

Type

Payload

FCS

EMS Trunk/Hybrid Configuration

2
1

4
53

Enhanced Traffic Manager

Enhanced Traffic Manager

The Enhanced Traffic Manager (ETM) improves
the QoS capabilities by

Enhanced classification methods

Improved scheduler
Uses 8 queues (instead of 4)
Supports shaping capabilities per queue
Weighted Random Early Detect (WRED) support
PTP Optimized Transport
Enhanced performance monitoring and statistics

The ETM applies only to Radio port egress traffic

The ETM is licensed feature
55

The Processes
The Enhanced Traffic Manager (ETM) uses
the following processes
Classification

56

Policing /
Shaping

Scheduling

EMS Enhanced Traffic Manager

Classification Process
Responsible to check the validity of the frame coming in
Classify the traffic based on

Source MAC Address up to 16 addresses

Destination UDP Port
Source UDP Port
Known Protocol Data Unit Destination MAC Addresses 66 known protocol
MAC address
VLAN ID
VLAN Priority bits
IP DSCP/TOS bits
MPLS Experimental bits

Classification
58

Policing /
Shaping

Scheduling

Classification - Menu

Classification Process Output

The output of the classification process
Traffic Class of Service (CoS)
Traffic marked color, either Green or Yellow

CoS are mapped into queues

The mapping is configurable

60

Weighted Random Early Detect

Weighted Random Early Detect (WRED) algorithm is part of
the shaping process
The goal of WRED algorithm is to prevent TCP global
synchronization problem
TCP global synchronization is
when there is a congestion at the bottleneck, the radio port
frames from all flows are dropped, do the nature of TCP
Resulting in low throughput of the system

61

Weighted Random Early Detect

The upper graph demonstrates
two flows of TCP traffic without
a WRED algorithm

The lower graph demonstrates

two flows of TCP traffic with
WRED algorithm

62

Memory Queues
The enhanced traffic manager
supports up to 8 memory queues
The size of the memory allocated
for the queues is up to 4Mb
The size of each queue is
configurable
The default configuration is 0.5Mb
per queue

63

Egress Shaper
Egress shaper is used to shape the traffic profile sent to the
radio
There is an egress shaper for each priority queue
Each queue can be configured with
Committed Information Rate (CIR)
Commited Buffer Size (CBS)

There is the possibility to enable/disable all queues at once

64

Egress Shaper & Scheduler Menu

Ethernet Header Compression

Header Compression

Layer 1 Header Suppression

MAC Header Compression

MAC Header Compression (Contd)

Enhanced Compression

Enhanced Compression (Contd)

Thank You