Scribd
Upload
56 views4 pages

Configuring PRP On Stratix 5400 - 5410 Switches

Uploaded by

Orion Valground
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
56 views4 pages

Configuring PRP On Stratix 5400 - 5410 Switches

Uploaded by

Orion Valground
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Industries Capabilities Products News Events Sales & Partners Support

Support Center Get Support  Training & Webinars Online Forum My TechConnect  Customer Care  orion_valtie… 

03-Feb-2022 - Important product notice regarding Microsoft vulnerability patch (MS KB5004442)

ID: QA33861 | Access Levels: TechConnect

Configuring PRP on Stratix 5400 / 5410 switches


READ LATER:  Email this page  Print

To find an answer using a previous Answer ID, click here

Search Knowledgebase... SEARCH ADD TO FAVORITES

Document ID QA33861

Published Date 02/14/2020

Summary
Configuring PRP on Stratix 5400 / 5410 switches

Question
How can I configure Parallel Redundancy Protocol on Stratix 5400 and 5410 switches?

Environment
IOS 15.2(2)EA1

Answer
Stratix 5400 and 5410 switches can be configured as Redundancy Boxes for Parallel
Redundancy Protocol (PRP).
PRP Terminology

Parallel Redundancy Protocol allows systems to overcome any single network failure
without affecting the data transmission. It can be applied to most Industrial Ethernet
applications since it is independent of the protocols and provides seamless failover.
Under PRP, each network node has two Ethernet ports attached to two different local
area networks of arbitrary, but similar topology.
The topology consists of 2 independent networks/LANs which are NOT
interconnected.

The individual LANs can be any topology, but a ring topology is recommended for
deterministic recovery and network symmetry
Double Attached Node for PRP (DANP)

A DANP is an end device that implements PRP for generating and processing the dual
Ethernet frame.
Each DANP has an additional element implemented in their network card called LRE -
Link Redundancy Entity. How DANP operates is:
1. Transmit data on both LANs: the LRE sends each frame simultaneously on LAN A
and LAN B.
2. Transfer: Frames over LAN A and B transit with different delays (or could not
arrive at all).
3. Receive from both LANs: the node receives both frames, the LRE between link
layer and Ethernet controllers handles the frames and can filter duplicates.

Single Attached Node

A SAN is a single-port end device that does not contain any PRP processing. SANs can
be connected to either LAN A or LAN B but not both at the same time.

Redundancy Box aka Red Box

In an EtherNet/IP system, directly attached SANs can cause issues with the address
conflict detection (ACD) feature.
The Redundancy Box (Red-Box) is a PRP proxy for non-PRP devices. Installing SANs
behind a Red-Box (Stratix 5400, 5410) creates Virtual Double Attached Nodes (VDANs).

Validated Network Topologies


Several topologies have been tested to prove PRP protocol is working on Stratix
switches. Switches acting as RedBox were Stratix 5400 while access switches in LAN
A and LAN B were Stratix 5700. Logix controllers were connected via RedBoxes to
measure network outage time using Produce/Consume Tag mechanism.
Topology #1 - LANs built using default Spanning Tree Protocol (MSTP)

Links connecting RedBox switches to LAN A and LAN B need to be configured as


access (and NOT trunk). You can use Multiport Automation Device smartport to achieve
that. Additional setting that turns BPDU Filtering on must be applied to those links.

All remaining links between switches in LANs are configured as trunk using Switch For
Automation smartport.

During testing there was no communication outage observed in neither of cases:


Failure of switches in LAN A or LAN B
Failure of cable connecting RedBox to LAN A or LAN B
Topology #2 - LANs built using Resilient Ethernet Protocol (REP)

Links connecting RedBox switches to LAN A and LAN B need to be configured as


access (and NOT trunk). You can use Multiport Automation Device smartport to achieve
that. Additional setting that turns BPDU Filtering on must be applied to those links.

All remaining links between switches in LANs are configured as trunk using Switch For
Automation smartport. Additionally REP was configured to for a ring topology.

During testing there was no communication outage observed in neither of cases:

Failure of switches in LAN A or LAN B


Failure of cable connecting RedBox to LAN A or LAN B

Stratix 5400 Configuration for PRP

To achieve RedBox functionality for the above architectures following settings were
applied:
1. Multiport Automation Device smartport set on links Gi1/1 and Gi1/2 connecting to
LAN A and LAN B.
2. PRP Channel 1 enabled on those two ports with Command Line Interface:
configure terminal
no spanning-tree etherchannel guard misconfig
interface range Gi1/1-2
no keepalive
prp-channel-group 1
3. Enable BPDU Filter and bring up the PRP interface:
exit
interface prp-channel 1
spanning-tree bpdufilter enable
no shutdown
end

More detail on PRP configuration can be found in Cisco Industrial Ethernet 4000 Series
Switch Software Configuration Guide.

Please provide feedback on


this technote
Met my needs Room for
improvement

RATE CONTENT

Related Answers

Product Notice 2021-10-001 -


PowerFlex 755TL/TR/TM frames
5…15 and PowerFlex 6000T Stratix Switch Fiber Connection
Stratix 5400 DLR ports
frames A, B, and R may stop Facts
responding after 388 days of
continuous power-up

DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such
subjects. Accordingly, the information in this web site is not intended to constitute application, design, software or other professional engineering advice or services.
Before making any decision or taking any action, which might affect your equipment, you should consult a qualified professional advisor.

ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE DATA CONTAINED IN THIS WEB SITE AND MAY MAKE
CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS "AS IS." IN NO
EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT OR DAMAGE, EVEN
IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.

ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE INFORMATION (INCLUDING SOFTWARE) PROVIDED
HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT. Note that certain
jurisdictions do not countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.

About Us Careers Investors Integrity-Sustainability Locations Contact Us



Copyright © 2022 Rockwell Automation, Inc. All Rights Reserved. Top
Legal Notices | Privacy & Cookies Policy

You might also like