H3C S9500 Series User manual

Operation Manual – RPR
H3C S9500 Series Routing Switches Table of Contents
i
Table of Contents
Chapter 1 RPR Configuration....................................................................................................... 1-1
1.1 Introduction to RPR ...........................................................................................................1-1
1.1.1 Overview .................................................................................................................1-1
1.1.2 Ring Structure of RPR.............................................................................................1-1
1.1.3 Data Operations on RPR ........................................................................................1-2
1.1.4 Topology Discovery.................................................................................................1-4
1.1.5 Fault Response Methods........................................................................................1-5
1.1.6 RPR Timers.............................................................................................................1-7
1.1.7 RPR Ports ...............................................................................................................1-8
1.1.8 Protocols and Standards.........................................................................................1-9
1.2 Configuring RPR................................................................................................................1-9
1.3 Configuring Protection Mode...........................................................................................1-10
1.4 Configuring Protection Reversion Mode..........................................................................1-10
1.5 Configuring Ringlet Selection Table ................................................................................1-11
1.5.1 Adding a static ringlet selection entry ...................................................................1-12
1.5.2 Configuring default ringlet selection......................................................................1-12
1.6 Configuring Rate Limiting ................................................................................................1-12
1.7 Configuring Station Weight..............................................................................................1-13
1.8 Configuring Timers ..........................................................................................................1-14
1.9 Configuring RPR POS Interface......................................................................................1-15
1.10 Configuring Port Type....................................................................................................1-16
1.11 Configuring Station Name..............................................................................................1-16
1.12 Configuring Protection Requests...................................................................................1-16
1.13 Configuring RPR VLAN Tunnel .....................................................................................1-17
1.14 Testing Connectivity Between Stations .........................................................................1-17
1.15 Displaying and Maintaining RPR...................................................................................1-18
1.16 RPR Configuration Examples........................................................................................1-19
1.16.1 RPR Protection Mode/Static Ringlet Selection Configuration Examples............ 1-19
1.16.2 RPR VLAN Tunnel Configuration Examples.......................................................1-21

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-1
Chapter 1 RPR Configuration
When configuring RPR, go to these sections for information you are interested in:
zIntroduction to RPR
zConfiguring RPR
zDisplaying and Maintaining RPR
zRPR Configuration Examples
1.1 Introduction to RPR
This section covers these topics:
zIntroduction to RPR
zRing Structure of RPR
zData Operations on RPR
zTopology Discovery
zFault Response Methods
zRPR Timers
zRPR Ports
zProtocols and Standards
1.1.1 Overview
Resilient packet ring (RPR) is a new MAC layer protocol designed for transferring mass
data services over MANs. It can operate on synchronous optical network/synchronous
digital hierarchy (SONET/SDH), dense wavelength division multiplexing (DWDM) and
Ethernet to provide flexible and efficient networking schemes for broadband IP MANs
carriers. The RPR technology delivers these benefits:
zPhysical layer diversity
zHigh bandwidth utilization
zMulticast and broadcast support
zAutomatic topology discovery
zQuick protection mechanism
zTraffic level guarantee based on bandwidth reservation and rate limiting
zBandwidth sharing fairness among stations on the ring
1.1.2 Ring Structure of RPR
RPR is made up of dual unidirectional counter-rotating ringlets identified as Ringlet 0
and Ringlet 1, as shown in Figure 1-1:

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-2
Station
West
EastWest
East
West
East East West
East
West
Ringlet 0
Ringlet 1
Span
Figure 1-1 Ring structure of RPR
Ringlet 0, also called outer ring, is for clockwise or west data traffic. Ringlet 1, also
called inner ring, is for counterclockwise or east data traffic.
On Ringlet 0, stations send data frames out of east interfaces and receive data frames
from west interfaces; on Ringlet 1, stations send data frames out of west interfaces and
receive data frames from east interfaces. A group of consecutive stations associated
with the same attribute form a domain.
Any two adjacent stations are connected by a pair of unidirectional logical channels
called links transmitting in opposite directions. These two links form a span. Aspan on
which data frames are not allowed to pass is called an edge. If a ring contains at least
one detected edge, it is called open ring. If it does not contain any detected edges, it is
called closed ring.
1.1.3 Data Operations on RPR
Stations on an RPR handle data frames by performing the following operations:
zInsertion, to place a frame on a ringlet.
zCopy, to deliver an inbound frame from the ring to the upper layer. The copying of
a frame does not imply its removal from the ring.
zTransit, to pass a frame to the next station.
zStripping, to remove a frame from a ringlet.
By performing these operations, stations implement unicast transmission, broadcast
transmission, and multicast transmission.

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-3
I. Unicast transmission
Transit
Strip
Strip
Transit
Copy from
ringlet 1
Copy from
ringlet 0
Insert to
ringlet 0
Insert to
ringlet 1
Transit
Strip
Figure 1-2 Unicast transmission on an RPR ring
Figure 1-2 shows how a unicast data frame is transmitted on an RPR ringlet:
1) Source station inserts the unicast frame into the data stream on Ringlet 0 or
Ringlet 1.
2) Transit stations transit the frame.
3) The frame is copied and stripped when it reaches the destination station or when
its time to live (TTL) expires.
Different from traditional ring technologies where unicast frames are removed from the
ring at the source station, RPR adopts destination stripping to remove unicast frames
from the ring at the destination station. This increases bandwidth utilization and spatial
bandwidth reuse efficiency.
II. Broadcast transmission
Copy from
ringlet 0
Copy from
ringlet 0
Copy from
ringlet 0
Copy from
ringlet 0
Strip
Strip
Insert to
ringlet 0
Figure 1-3 Broadcast/flooded transmission on an RPR ring
Figure 1-3 shows how a frame is flooded or broadcasted on an RPR ringlet:
1) Source station inserts the frame into the data stream on Ringlet 0 or Ringlet 1.

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-4
2) Transit and destination stations copy and transit the frame if the TTL of the frame
has not expired.
3) The frame is stripped when it returns to the source station or whenits TTL expires.
III. Multicast transmission
Figure 1-4 Multicast transmission on an RPR ring
Figure 1-4 shows how a multicast frame is transmitted on an RPR ringlet:
zSource station inserts the frame into the data stream on Ringlet 0 or Ringlet 1.
zTransit stations transit the frame.
zDestination station transits and copies the frame.
zThe frame is stripped when it returns to the source station or whenits TTL expires.
1.1.4 Topology Discovery
RPR performs automatic topology discovery to collect such information as the number
of stations, ring state, order of the stations on the ring to build a topology database. This
database does not change after the ring topology becomes stable.
I. Topology database
Each RPR station maintains a topology database that describes the topology of the
entire RPR ring. Based on this database, the station creates its ringlet selection table.
A topology database contains three categories of information:
zRinglet topology information, such as the number of stations, ring state, and
available bandwidth.
zLocal station topology information, such as the MAC address, protection mode,
protection state, station name, topology checksum of the local station and the
neighbor stations.
zTopology information of other stations, such as the MAC address, validity state,
reachability, protection mode, station ID, station name, and reserved bandwidth.

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-5
II. Topology discovery process
RPR uses three types of control frames for topology discovery: attribute discovery
(ATD), topology protection (TP), and topology checksum (TC).
zTP frames convey configuration and status information of stations. The stations on
an RPR ring broadcast TP frames to advertise their configuration and status
information and update their own topology databases after receiving TP frames
from other stations. Finally, all the stations reach an agreement on the topology of
the ring.
zTC frames convey topology checksum information. They are sent between
adjacent stations to check whether the topology databases on them are
synchronized, thus identifying stability of the RPR ring topology.
zATD frames convey attributes of the local station such as the MAC address and
station name. These attributes will be included in the topology database.
All these control frames are sent at regular intervals, which are user configurable. For
TP and TC frames, two types of intervals, fast sending interval and slow sending
interval, are used.
When a station on the ring starts initializing or detects a topology change, it sends TP
frames to propagate topology information throughout the network. When doing that, it
sends the first nine TP frames at fast intervals and subsequent TP frames at slow
intervals.
After the RPR ring topology converges, the station starts to send TC frames. When
doing that, it sends first five TC frames at fast intervals and then subsequent TC frames
at slow intervals.
Only one type of interval is available for sending ATD frames, regardless of topology
change.
1.1.5 Fault Response Methods
RPR delivers strong self-recovery capability. Its protection mechanism provides event
detection, quick self-recovery, and fast service recovery when faults occur to the
fiber-optic or stations. The network can thus detect faults quickly and react
appropriately to restore services in 50 ms.
RPR is available with two fault response methods: passthrough and protection.
I. Passthrough
The passthrough approach mainly applies to handle station faults. When a station
detects an internal fault, it can enter the passthrough mode where it behaves similar to
a repeater and does not handle any services on the ring. Frames arriving at this station
are forwarded directly as if it was transparent, and the station is invisible on the ring.
See Figure 1-5.

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-6
Station failure
Pass-through
Figure 1-5 Passthrough mode
II. Protection
If a station is unable to forward traffic as the result of power failure or fiber cut for
example, it should enter protection mode.
1) Protection mode
RPR provides two protection modes: wrapping and steering.
zWrapping
In wrapping mode, after a span or station fails, protected traffic is directed at the point of
failure to the opposing ringlet. The two ringlets thus form a closed single ring around the
point of the failure.
As shown in Figure 1-6, after the span between station Aand station B fails on Ringlet 0,
traffic that should originally travel from station B to A along Ringlet 0 is directed to
Ringlet 1 to reach station B.
Figure 1-6 Wrapping mode
As the wrapping mode allows quick switchover, data frame loss can be minimized. This,
however, wastes bandwidth.
zSteering mode
Unlike in wrapping mode, in steering mode, the two stations at the two sides of the point
of failure updates their topology databases first; and then sends TP frames at fast

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-7
intervals to the other stations on the ring. After a new topology database is stabilized,
the source station directs protected frames to the ringlet that retains connectivity to their
destinations.
As shown in Figure 1-7, traffic that should have traveled from station A to station B
along Ringlet 0 is steered to Ringlet 1 for transmission.
Steered path
Station A
Station B
Figure 1-7 Steering mode
The steering mode can avoid the bandwidth waste with wrapping mode, but as it
requires topology reconvergence, it can cause frame loss and service interruption.
2) Protection switching
RPR protection switching uses the following protection hierarchy listed in the order of
decreasing severity:
zForced switch (FS)
zSignal fail (SF), related to current physical status.
zSignal degrade (SD), related to current physical status.
zManual switch (MS)
zWait to restore (WTR)
zIdle
Protection switching occurs only when requested by a station on the ring. The hierarchy
of protection requests is the same as this protection switching hierarchy. Among
protection requests, FS and MS requests are sent manually, whereas SF, SD, and
WTR requests are sent automatically.
The MS request sent by a station will not be processed if a higher priority protection
request is present on the RPR ring.
If an FS request is present on the current ring, the SF or SD request automatically sent
as the result of a link failure will be processed only after the FS request is cleared.
1.1.6 RPR Timers
RPR is available with the following user-configurable timers:

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-8
zTP fast timer: defines the fast interval at which TP frames are sent. A TP fast timer
starts when a station starts initializing or detects a topology change. After sending
nine TP frames at fast intervals, the station begins to send TP frames at slow
intervals.
zTP slow timer: defines the slow interval at which TP frames are sent. This timer is
active when the ring topology is stable.
zTC fast timer: defines the fast interval at which TC frames aresent. A TC fast timer
starts on a station when the ring topology becomes converged. After sending five
TC frames at fast intervals, the station begins to send TC frames at slow intervals.
zTC slow timer: defines the slow interval at which TC frames are sent. TC frames
are sent in slow intervals when the ring topology is stable.
zATD timer: defines the interval at which ATD frames are sent.
zWTR timer: When a protection switching event occurs on a station due to link
failure, the station enters automatic protection state; after the link recovers, the
station enters the idle protection state. The WTR timer defines the delay that a
station transits to the idle protection state after entering the automatic protection
state.
zHold-off timer: defines the delay for the physical layer (PHY) to report a protection
request after detecting a link failure.
zKeepalive timer: A single choke fairness frame (SCFF) is transmitted point to point
every fairness algorithm period. When a station fails to receive a SCFF, a
keepalive timer starts. If no SCFF frame is received after the timer expires, the
station sends an SF protection request.
zTopology stability timer: When a station detects a topology change on the ring, it
starts the topology stability timer and begins to collect topology information to
update its topology database. After the timer expires, the station checks the
validity of received topology information. If the information is valid, the station
enters topology valid state; if not, the station re-starts the timer.
1.1.7 RPR Ports
An RPR station comprises one RPR logical interface and two physical ports. The two
physical ports are used to transmit data to or receive data from the ring and the logical
port is provided for you to make configuration.
Logical port is available for RPR stations: XGE (10GE).
Three types of physical ports are available for RPR stations: XGE, 2.5 Gbps POS, and
10 Gbps POS.
The RPR logical ports are available depend on the physical RPR ports on your station,
as shown in the following table:

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-9
Table 1-1 RPR physical and logical port dependencies
RPR physical port RPR logical port
XGE XGE
2.5 Gbps POS XGE
10 Gbps POS XGE
Note:
zMany commands available on an Ethernet port can be used on an RPR logical port.
These commands involve these configurations: broadcast suppression, port
description, link type, VLAN assignment, default VLAN ID assignment (for a hybrid
or trunk port), flow control, priority configuration, and the loopback command. For
how to configure them, refer to Ethernet Port Configuration.
zRPR logical ports support STP, QoS, and ACL.
1.1.8 Protocols and Standards
The RPR implementation follows the following document:
IEEE802.17: Resilient packet ring (RPR) access method and physical layer
specifications
1.2 Configuring RPR
Complete these tasks to configure RPR:
Task Remarks
Configuring Protection Mode Optional
Configuring Protection Reversion Mode Optional
Configuring Ringlet Selection Table Optional
Configuring Rate Limiting Optional
Configuring Station Weight Optional
Configuring Timers Optional
Configuring RPR POS Interface Optional
Configuring Port Type Optional
Configuring Station Name Optional
Configuring Protection Requests Optional

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-10
Task Remarks
Configuring RPR VLAN Tunnel Optional
Testing Connectivity Between Stations Optional
1.3 Configuring Protection Mode
Follow these steps to configure the protection mode on the RPR station:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view interface interface-type
interface-number —
Configure the
protection mode rpr protect-mode { steer | wrap }
Optional
Steering mode applies by
default.
Caution:
All the stations on an RPR ring must adopt the same protection mode for the ring to
operate normally.
1.4 Configuring Protection Reversion Mode
Two protection reversion modes are available:
zRevertive mode, where a station resumes the idle protection state once the WTR
timer expires.
zNon-revertive mode, where the station remains in automatic protection state upon
expiration of the WTR timer and does not resume the idle state until a higher
protection request is present on the ring.
Follow these steps to configure the protection reversion mode on the RPR station:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view interface interface-type
interface-number —

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-11
To do... Use the command... Remarks
Configure the protection
reversion mode
rpr reversion-mode
{revertive |
non-revertive }
Optional
Revertive mode applies
by default.
1.5 Configuring Ringlet Selection Table
Each RPR station maintains a ringlet selection table, based on which the decision as to
which ringlet should be selected to transmit frames is made. A ringlet selection table
entry contains such information as the MAC address of a station, the ringlet through
which frames are transmitted.
The RPR ringlet selection table comprises a static ringlet selection table, a dynamic
ringlet selection table, a default ringlet selection table, an overall ringlet selection table,
an IPv6 ringlet selection table, and a VRRP ringlet selection table.
zStatic ringlet selection table is administratively configured to specify the ringlet for
delivering a frame to a destination station.
zDynamic ringlet selection table is built dynamically based on the topology
database.
zDefault ringlet selection table specifies the default ringlet for delivering frames.
zOverall ringlet selection table is created from the above three tables. Static ringlet
selection table has the highest priority. If a static ringlet selection entry is available
for reaching a destination station, it is added into the overall ringlet selection table.
If no static entry is available, the system looks at the dynamic ringlet selection
table. If two shortest paths are available, default ringletselection applies to pick up
one from them. The selected entry is then added into the overall ringlet selection
table. When sending frames, the station consults this table to identify the path to
the destination MAC address.
Note:
Each station on the RPR can be configured with only one VRRP group and it can only
be configured on the VLAN virtual interface to which the PVID corresponds.

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-12
1.5.1 Adding a static ringlet selection entry
Follow these steps to add an entry into the static ringlet selection table:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view interface interface-type
interface-number —
Add a static ringlet
selection entry rpr static-rs mac-address { ringlet0 | ringlet1 }
Required
No static ringlet selection
entry is created by default.
Caution:
Static ringlet selection entries take effect only when the RPR ring is closed.
1.5.2 Configuring default ringlet selection
Follow these steps to configure default ringlet selection:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view interface interface-type
interface-number —
Configure default ringlet
selection rpr default-rs { ringlet0 | ringlet1 }
Optional
By default, the default
ringlet is Ringlet 0.
Caution:
The default ringlet you configured is not necessarily the one in use. This happens when
a span is faulty and unable to forward data.
1.6 Configuring Rate Limiting
RPR services fall into three classes: class A, class B and class C, with decreasing
priorities.

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-13
Class A is further divided into subclass A0 and subclass A1. RPR can reserve
bandwidth for the subclass A0 service. When congestion occurs, the unused reserved
bandwidth cannot be used by lower priority services. For the subclass A1 service, rate
limiting is used. When congestion occurs, subclass A1 allows lower priority services to
use its unused bandwidth and the bandwidth allocation in this case is regulated by
fairness algorithms.
Class B can also be divided into two subclasses: committed information rate (CIR) and
excess information rate (EIR). For class B traffic, the portion within the predefined rate
limit uses the class B CIR service and the portion exceeding the limit uses the class B
EIR service. Similar to the class C service, the class B EIR service is regulated by
fairness algorithms.
The class C service is regulated by fairness algorithms and takes the lowest priority.
Follow these steps to assign reserved bandwidths to service classes:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view interface interface-type
interface-number —
Assign reserved
bandwidth to a
service class
rpr rate-limiter { high |
low | medium |
reserved } { ringlet0 |
ringlet1 } value
Optional
By default, no bandwidth is
reserved for subclass A0; the
rate limit is 2‰ for subclass A1,
0 for class B CIR and class B
EIR, and 1000‰ for class C.
Caution:
zThe total bandwidth reserved for subclass A0 by the stations on a ringlet must be
less than the ringlet bandwidth.
zThe ringlet0 and ringlet1 keywords in the command refer to sending ringlets.
zFor detailed description about service classes, refer to QoS Configuration in the
QoS ACL Volume.
1.7 Configuring Station Weight
On an RPR ring, bandwidth resources are shared among stations. When traffic size is
small, RPR can handle bandwidth requests of all stations on the ring well. When traffic
size gets heavy, congestion may occur. To prevent some stations from taking
advantage of their spatially or chronologically favorable position on the ring to occupy

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-14
excessive bandwidth, RPR adopts a fairness algorithm to ensure bandwidth allocation
fairness.
The fairness algorithm of RPR mainly regulates class B-EIR and class C traffic on the
RPR ring. You can assign a weight to a station to adjust the ratio of its available service
bandwidth to the total non-reserved bandwidth on a ringlet. The fairness weight of a
station is configured as an exponent of 2.
Follow these steps to assign the bandwidth allocation fairness weight to the RPR
station on a ringlet:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view interface interface-type
interface-number —
Configure the weight of
the station rpr weight { ringlet0 | ringlet1 } value
Optional
The value argument is an
exponent of 2.
By default, the fairness
weight of a station is 1 on
both Ringlet 0 and Ringlet 1.
1.8 Configuring Timers
Follow these steps to configure timers:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view interface interface-type
interface-number —
Set the ATD timer rpr timer atd value Optional
1 second by default
Set the hold-off timer rpr timer holdoff value Optional
0 milliseconds by default
Set the keepalive timer rpr timer keepalive value Optional
3 milliseconds by default
Set the topology stability
timer rpr timer stability value Optional
40 milliseconds by default
Set the TC fast timer rpr timer tc-fast value Optional
10 milliseconds by default

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-15
To do... Use the command... Remarks
Set the TC slow timer rpr timer tc-slow value Optional
100 milliseconds by
default
Set the TP fast timer rpr timer tp-fast value Optional
10 milliseconds by default
Set the TP slow timer rpr timer tp-slow value Optional
100 milliseconds by
default
Set the WTR timer rpr timer wtr value Optional
10 seconds by default
1.9 Configuring RPR POS Interface
Follow these steps to configure an RPR POS interface:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR POS
interface view interface rprpos
interface-number Required
Configure SD1and
SF2thresholds threshold { sd | sf }
value
Optional
The default SD threshold is 5 and
the default SF threshold is 3. The
value of SF must be smaller than
SD, and their difference must not be
larger than 2.
Note:
1. SD = Signal degrade
2. SF = Signal failure
Note:
zFor description about the threshold command, refer to POS Interface Configuration
in the Access Volume.
zFor physical parameters configuration on RPR POS interfaces, refer to POS
Interface Configuration in the Access Volume.

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-16
1.10 Configuring Port Type
Follow these steps to set physical RPR port type on an RPR logical port:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view interface interface-type
interface-number —
Set RPR physical port
type rpr port-type { 10gpos | 10ge }
Optional
The RPR port type
detected at initialization
applies by default.
Caution:
zAfter you change the RPR port type, the interface card will reboot to have the
change take effect. The previous settings on the interface card will be lost as a
result.
zThe rpr port-type command can only take effect on 10 Gbps POS and 10GE
physical ports. It cannot take effect on 2.5 Gbps POS ports.
1.11 Configuring Station Name
Follow these steps to assign a name to the RPR station:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view interface interface-type
interface-number —
Configure a station
name rpr station-name
station-name
Required
No station name is
configured by default.
1.12 Configuring Protection Requests
A station can automatically send protection requests onto an RPR ringlet to trigger
protection. Besides that, you may send FS or MS protection requests manually to
trigger protection or send idle protection requests to clear the manually sent protection
requests present on a ringlet.

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-17
Follow these steps to send an FS or MS protection request onto the ringlet:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view interface interface-type
interface-number —
Send an RPR protection
request onto a ringlet
rpr admin-request { fs |
ms | idle } { ringlet0 |
ringlet1 }
Optional
The default is idle.
1.13 Configuring RPR VLAN Tunnel
RPR stations that adopt the RPR VLAN tunnel technology directly unicast frames to
destination stations rather than flood them on ringlets. This improves bandwidth
utilization efficiency.
RPR tunnels are configured specific to VLAN ID on RPR logical interfaces. You may
configure up to 4096 tunnels on an RPR logical interface. For each tunnel, you need to
specify its frame copying station. In addition, to distinguish traffic destined to the same
MAC address but using different tunnels, you need to configure static ringlet selection
entries for them.
Follow these steps to configure an RPR VLAN tunnel:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view interface interface-type
interface-number —
Configure an RPR VLAN
tunnel
rpr tunnel vlan { vlan-id-list | all }
dest-mac mac-address [ ringlet0 |
ringlet1 ] Required
Caution:
Before configuring a VLAN tunnel on an RPR interface, first configure the interface to
allow the VLAN to pass.
1.14 Testing Connectivity Between Stations
You may send Echo Request/Echo Response messages to test the connectivity
between two stations and locate failure points if any. The connectivity between the
current station and the destination station is considered as normal if the connection

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-18
between the two stations is normal on both the specific sending ringlet and the
receiving ringlet. In this case, the destination station should be able to receive theEcho
Request messages that the current station sends along the specific ringlet and the
current station should be able to receive the Echo Response message that the
destination station sends along the specificringlet. Otherwise, the connectivity between
the current station and the destination station is considered as having failed.
Follow these steps to test the connectivity to a specific station:
To do... Use the command... Remarks
Enter system view system-view —
Enter RPR logical
interface view
interface
interface-type
interface-number —
Test the
connectivity to a
specific station
rpr echo mac
mac-address [ -c value
| -r { ringlet0 | ringlet1 |
reverse } | -s { ringlet0
| ringlet1 } | -t value ] *
Required
If the number of test frames is not
specified (-c value), 5 test frame is
sent; if the receiving ringlet
(-r)/sending ringlet (-s) is not
specified, the default ringlet is
used. If the echo timeout (-t) is not
specified, the default timeout of 10
milliseconds applies.
Caution:
If neither the sending ringlet nor the receiving ringlet is specified, the default ringlet
currently in use will be used for transmitting Echo Request packets and Echo
Response.
1.15 Displaying and Maintaining RPR
To do... Use the command...
Display information about an RPR
physical port display interface { RPRXGE | RPRPOS } interface-number
Display RPR defect information display rpr defect [ interface-type
interface-number ]
Display RPR fairness settings display rpr fairness [ interface-type
interface-number ]
Display RPR protection information display rpr protection [ interface-type
interface-number ]

Operation Manual – RPR
H3C S9500 Series Routing Switches Chapter 1 RPR Configuration
1-19
To do... Use the command...
Display RPR ringlet selection table
information
display rpr rs-table { default |dynamic
|ipv6 |overall |static | dynamic|vrrp }
[ interface-type interface-number ]
Display statistics about traffic on the
RPR ring
display rpr statistics { dmac | smac }
[ mac-address ] [ interface-type
interface-number ]
Display the settings of all configurable
RPR timers display rpr timers [ interface-type interface-number ]
Display RPR topology information display rpr topology { all |local |ring |
stations } [ summary ] [ interface-type
interface-number ]
Display VRRP standby group
information of RPR display rpr vrrp-info [ interface-type interface-number ]
Clear the statistics about protection
events on the RPR station reset rpr protection statistics [ interface-type interface-number ]
Display RPR VLAN tunnels display rpr tunnel vlan { vlan-id1 [to vlan-id2 ]|all }[valid |invalid ]
[interface-type interface-number ]
Note:
The above table shows the display command with the interface-type interface-number
argument:
zThe argument can only be used to specify an RPR logical interface.
zWhen the interface-type interface-number argument is not specified in interface
view, only the information about the RPR ring to which this interface belongs is
displayed.
zWhen the interface-type interface-number argument is specified in other views, only
the information about the RPR ring to which this interface belongs is displayed or
cleared. Otherwise, the information about all RPR rings is displayed or cleared.
1.16 RPR Configuration Examples
1.16.1 RPR Protection Mode/Static Ringlet Selection Configuration
Examples
I. Network requirements
Stations A through E form an RPR ring and work in steer protection mode by default.
Do the following:
zChange the protection mode of the ring to wrapping.