FibeAir ® IP-10 G-Series

EMS RSTP Configuration

Proprietary and Confidential

Agenda

• Student Perquisites

• General Overview

• Limitations

• Site / Node Types

• Switchover Criteria

• In Band Management

• Out of band Management

• Configuration Example

2 Proprietary and Confidential

 Student Perquisites
Viewers / end-user are required to have previous experience prior to
practicing this module:

1.End users should be familiar with Switch configuration

2.Be End users should be familiar with setting port membership

3.End users should be familiar with management mode configuration

4.End users should be familiar with configuring Automatic State Propagation

3 Proprietary and Confidential

 RSTP Disabled

RSTP Ceragon Fast

Disabled IEEE 802.1w Ring RSTP

When disabled, Ceragon’s L2 switch is most suitable for

topologies that do not require ETH service protections (Chain
Topology)

4 Proprietary and Confidential

 Standard 802.1w RSTP

RSTP Ceragon Fast

Disabled IEEE 802.1w Ring RSTP

RSTP is an improved and much faster version of 801.d STP.

The re-convergence of the STP may carry on for 50 seconds

while RSTP re-convergence time may last for less than a
second.

With this feature enabled, Ceragon’s IP-10 can merge with

existing standard RSTP networks.

5 Proprietary and Confidential

 Ceragon’s Fast Ring RSTP

RSTP Ceragon Fast

Disabled IEEE 802.1w Ring RSTP

Ceragon Networks ring solution enhances the RSTP algorithm

for ring topologies, accelerating the failure propagation relative
to the regular RSTP:

• Up to 4 nodes < 150mSec

• Up to 8 nodes < 200mSec

6 Proprietary and Confidential

 Ceragon’s Fast Ring RSTP Overview

• Ring-RSTP itself is different than “classic” RSTP, as it exploits the topology of

the ring, in order to accelerate convergence.

• Ethernet-Fast-Ring-RSTP will use the standard RSTP BPDUs:

01-80-C2-00-00-00

• The ring is revertible. When the ring is set up, it is converged according to
RSTP definitions. When a failure appears (e.g. LOF is raised), the ring is
converged. When the failure is removed (e.g. LOF is cleared) the ring reverts
back to its original state, still maintaining service disruption limitations.

• RSTP PDUs coming from “Edge” ports are discarded (and not processed or
broadcasted).

7 Proprietary and Confidential

 System Limitations

User should be aware of the following limitations:

1. Ring RSTP is a proprietary implementation of Ceragon Networks, and cannot

inter-work with other Ring RSTP implementations of other 3rd party vendors.

2. Ring RSTP gives improved performance for ring topologies. For any other
topology the algorithm will converge but performance may take several
seconds:
• For this reason, there should be only 2 edge ports in every node.
• Also, only one loop should be present

3. Ring RSTP can be activated in “Managed Switch” or “Metro Switch”

applications; it is not available in any the “Single Pipe” application.

4. Ring RSTP may run with protection 1+1, but in some cases (change of root
node) the convergence time may be above 1sec.

8 Proprietary and Confidential

 Site / Node Types

The ring can be constructed by two types of nodes/sites:

1.Node/Site Type A:

• The site is connected to the ring with one Radio interface (e.g. East) and one
Line interface (e.g. West).

• The site contains only one IP-10 IDU. The Radio interface towards one
direction (e.g. East), and one of the Gigabit (Copper or Optical) interfaces,
towards the second direction (e.g. West).

• Other line interfaces are in “edge” mode, meaning, they are user interfaces,
and are not part of the ring itself.

9 Proprietary and Confidential

 Site / Node Types

The ring can be constructed by two types of nodes/sites:

2. Node/Site Type B:

• The site is connected with Radios to both directions of the ring (e.g. East &
West).

• Site contains two IDUs. Each IDU support the Radio in one direction

• One IDU runs with the “Ring RSTP”, and the second
runs in “Single pipe” mode.

• Both IDUs are connected via Gigabit interface

(either optical or electrical).

• Other line interfaces are in “edge” mode.

10 Proprietary and Confidential

 Switchover / Convergence Criteria

The following failures will initiate convergence:

• Radio LOF
Note:
• Link ID mismatch. Ring port (non-edge port)
shutdown will initiate
• Radio Excessive BER (optional) convergence!

However, since this is a user action,

• ACM profile is below pre-determined threshold (optional).
it is not considered a failure, thus it
is not “propagated”.
• Line LOC
When user issues “port shutdown”
• Node cold reset (“Pipe” and/or “Switch”). fast convergence should not
be expected.
• Node power down (“Pipe” and/or “Switch”)

• xSTP port disable / enable

11 Proprietary and Confidential

 In-Band Management (1)
In this scenario, management is part of the data traffic, thus, management is
protected with the traffic when the ring is re-converged as a result of a ring
failure.

• “Managed Switch” IDUs will be configured to “In-Band”, while “Single Pipe” IDUs will be
configured to “Out-of-Band”.

• “Single Pipe” nodes will be connected with external Ethernet cable to the
“Managed Switch” for management.

• The reason for that requirement is the “automatic state propagation”

behavior of the “Single Pipe” that shuts down its GbE traffic port upon failure,
thus, management might be lost to it.

Note – When using a node (Outdoor Enclosure), there is no need to configure

Management mode for the 2nd slot

12 Proprietary and Confidential

 In-Band Management (2)

13 Proprietary and Confidential

 Out of band Management (1)
• In this scenario, all elements (“Single pipe” and “Managed Switch” IDUs)
should be configured to “Out-of-band”, with WSC “enabled”. Management will
be delivered over WSC.

• External xSTP switch should be used in order to gain resilient management,

and resolve the management loops.

• The following picture demonstrates 4 sites ring, with out-of-band management:

14 Proprietary and Confidential

 Out of band Management (2)

15 Proprietary and Confidential

 EMS
Configuration
16 Proprietary and Confidential
 Setup Configuration

Site #1 Site #2

1 6 7 1 6 7
Pipe (slot #2) Pipe (slot #2)

1 2 3 4 5 6 7 1 2 3 4 5 6 7
Managed (slot #1) Managed (slot #1)

Site #3

1 6 7
Managed (slot #2)

1 2 3 4 5 6 7
Managed (slot #1)

EMS

1. You may start with out of band configuration to avoid physical loops
2. Establish the Radio links according to the setup scheme

17 Proprietary and Confidential

 Setup Configuration

Site #1 Site #2

1 6 7 1 6 7
Pipe (slot #2) Pipe (slot #2)

1 2 3 4 5 6 7 1 2 3 4 5 6 7
Managed (slot #1) Managed (slot #1)

Site #3

1 6 7
Managed (slot #2)

1 2 3 4 5 6 7
Managed (slot #1)

EMS

3. Connect between slot 2 and slot 1 using ports number 1 and fibers
4. Enable RSTP in all Managed Switch IDUs (see next slide)

18 Proprietary and Confidential

 Setup Configuration – Enabling RSTP

19 Proprietary and Confidential

 Setup Configuration – Configuring In Band MNG

Site #1 Site #2

1 6 7 1 6 7
Pipe (slot #2) Pipe (slot #2)

1 2 3 4 5 6 7 1 2 3 4 5 6 7
Managed (slot #1) Managed (slot #1)

Site #3

1 6 7
Managed (slot #2)

1 2 3 4 5 6 7
Managed (slot #1)

EMS

5. Enable In Band Management + VID 200

6. Connect the EMS PC to one of the IDUs (MNG port #7), disconnect other connections
7. Verify all GbE ports 1 of Slots #1 are Trunk & members of VID 200 (next slide)

20 Proprietary and Confidential

 GbE Port #1 Configuration

Add Services of other VLANs as

well if the RING is required to pass
ETH data as well (see example
below, VID 1000…)

Please note – the VIDs need to be

created first in the Switch
Configuration page

21 Proprietary and Confidential

 RSTP Verification

Site #1 Site #2

1 6 7 1 6 7
Pipe (slot #2) Pipe (slot #2)

1 2 3 4 5 6 7 1 2 3 4 5 6 7
Managed (slot #1) Managed (slot #1)

Site #3

1 6 7
Managed (slot #2)

1 2 3 4 5 6 7
Managed (slot #1)

EMS

8. PING EMS to all Sites at the same time (multiple PING sessions)

22 Proprietary and Confidential

 RSTP Verification

Aggregated Path Cost

9. Examine which switch is the Root Bridge and which ports are the Root Ports
10. Verify that the ring is set up properly (one Root)

23 Proprietary and Confidential

 RSTP Verification

11. Identify the Edge Ports and Non-Edge ports in your setup and make sure they are
configured correctly

24 Proprietary and Confidential

 Enabling ASP
Make sure that all RING IDUs (Pipe & Managed) support Automatic State
Propagation (enabled).

Enabling ASP allows RSTP Ring to converge faster by propagating radio

alarms into the Line and thus, accelerating port state changes.

Configure the ASP Criteria as required.

25 Proprietary and Confidential

 Triggering a Switchover

• Disconnect a radio link and make sure PING to all Main units is maintained

• Restore connectivity.

• Disconnect a different radio link and make sure PING to all Main units is
maintained

• Repeat the same tests with traffic and trails (SNCP).

26 Proprietary and Confidential

Prioritizing RSTP ports & topologies

Proprietary and Confidential

 Prioritization Criteria

1. Bridge Priority (User configurable)

2. MAC Address (unique per IDU)

3. Port Priority (User configurable)

4. Path Cost (User configurable)

28 Proprietary and Confidential

 Setting the Bridge Priority

All bridges are given the same Bridge Priority

(32768) by default.

Values range by multiples of 4096.

A bridge with lower priority will become the Root

Bridge.

You may consider this option as a “Topology Fine

Tuning Potentiometer…”

29 Proprietary and Confidential

 Reading the Aggregated Path Cost

This value shows the time it takes for the bridge to

get to the Root-Bridge (in terms of interface
capacity).

• The bigger the capacity – the lower the cost

• The lower the cost the better

Root Bridges will show this value = 0

This value indicates the aggregated cost a bridge

has to go through to get to the Root bridge.

30 Proprietary and Confidential

 Setting the Port Priority

All ports are given the same priority – 128

Should you wish to manually select the Root Port,

you may set a lower value

Ports with lower priority are more likely to be chosen

as the Root Port

31 Proprietary and Confidential

 Setting the Path Cost

The bigger the port capacity is, the lower this value
becomes

For example:
1GbE is given lower path cost than FE port

The bridge assigns a Root Port with the lowest Path

Cost to the Root Bridge

32 Proprietary and Confidential

 Thank You !
training@ceragon.com

33