Downloads |
 Feedback
|
Table Of Contents
IEEE 802.17 Resilient Packet Ring Feature Guide
Comparison of RPR with SRP and DPT Technologies
Configuring the Attribute Discovery Timer
Configuring Source Address Tracking
Configuring the SONET/SDH Overhead
Configuring the Reporting of SONET Alarms
Configuring BER Threshold Values
Configuring Traffic Rates for Transmission
Configuring Fairness Rate Adjustments
Configuring Multichoke Fairness
How to Configure RPR Protection
Configuring the Hold-off Timer
Configuring Protection Preferences
Configuring Forced or Manual Switching
Configuring the Wait-to-Restore Timer
Protection Troubleshooting Tips
How to Use Modular QoS CLI to Configure RPR Service Classes
Configuration Example Using MQC to Configure RPR Service Classes
How to Verify RPR Configuration and Operation
rpr-ieee fairness active-weights-detect
rpr-ieee protection sonet holdoff-timer
rpr-ieee protection pref jumbo
rpr-ieee protection request forced-switch
rpr-ieee protection request manual-switch
rpr-ieee protection sonet threshold
rpr-ieee tx-traffic rate-limit
IEEE 802.17 Resilient Packet Ring Feature Guide
This feature guide describes how to configure the Cisco implementation of the IEEE 802.17 Resilient Packet Ring (RPR) protocol on supported Cisco routers and includes information about the benefits of the feature, supported platforms, related publications, and so on. RPR is similar but not identical to the Spatial Reuse Protocol (SRP), the underlying technology used in the Cisco Dynamic Packet Transfer (DPT) family of products. Throughout this document, this feature is referred to as RPR.
This document covers the use of the RPR feature. It does not include hardware installation and initial configuration information. Refer to the appropriate router installation and configuration note for information on how to configure the hardware and prepare it for use with RPR.
Feature History for RPR
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
How to Configure RPR Fairness
•
•
•
•
Information About RPR
Resilient Packet Ring (RPR), as described in IEEE 802.17, is a metropolitan area network (MAN) technology supporting data transfer among stations interconnected in a dual-ring configuration. This protocol is very similar to Spatial Reuse Protocol (SRP), which was designed by Cisco and implemented in Dynamic Packet Transport (DPT) products. New DPT interfaces have been designed to include the 802.17 RPR protocol and are available for multiple Cisco router platforms. This guide describes the RPR interface and how to use RPR on compliant Cisco equipment.
RPR is a high-speed MAC-layer protocol that is optimized for packet transmission in resilient ring topologies. RPR employs a ring structure using unidirectional, counter-rotating ringlets. Each ringlet is made up of links with data flow in the same direction. The ringlets are identified as ringlet 0 and ringlet 1, as shown in Figure 1. The use of dual fiber-optic rings provides a high level of packet survivability. If a station fails or fiber is cut, data is transmitted over the alternate ring.
Figure 1 Dual-Ring Structure
East RX
Ringlet 0 data (downstream)
West TX
Ringlet 0 control (upstream)
West RX
Ringlet 1 data (downstream)
East TX
Ringlet 1 control (upstream)
As shown in Figure 1, the east interface of Station 1 (S1) transmits to and receives from the west interface of Station 2 (S2). Ringlet 0 always transverses from east to west and ringlet 1 from west to east. The west span is the span on which RPR transmits on ringlet 1 and the east span is the span on which RPR transmits on ringlet 0.
RPR stations dynamically share the ring bandwidth and permit many simultaneous conversations. Spatial bandwidth reuse is possible due to the packet destination-stripping property of RPR. RPR provides efficient use of available bandwidth by allowing the destination station to remove unicast packets after they are read, thereby providing bandwidth reuse for the other stations on the RPR ring.
Figure 2 illustrates the end-to-end MAC architecture of RPR.
Figure 2 End-to-End View of MAC Architecture
While DPT and SRP uses SONET/SDH as the physical medium, IEEE 802.17 RPR has been defined to use both SONET/SDH and the layer used for Gigabit and 10 Gigabit Ethernet.
Comparison of RPR with SRP and DPT Technologies
IEEE 802.17 RPR is very similar to the Cisco-developed SRP technology, which is used in the Cisco DPT product line. Besides their different frame formats, other differences and similarities between IEEE 802.17 RPR and SRP can be summarized as follows:
•
–
–
•
–
–
–
–
–
RPR Features
RPR offers the following main features:
•
•
–
–
–
•
–
–
–
–
–
•
–
–
–
•
•
–
–
–
–
How to Configure RPR
General configuration tasks for the RPR feature are presented in the following sections.
•
•
•
•
•
•
•
For information on configuring RPR fairness, protection, and service classes, see the following additional sections:
•
•
•
Configuring the Attribute Discovery Timer
Because station attributes are communicated separately from topology and protection packets, there is a separate timer to control the frequency at which these packets are sent. Attribute propagation is therefore determined by the attribute discovery (ATD) timer. The default rate is 1 packet for each ringlet per second.
To configure the ATD timer, perform the following steps.
Restrictions
Both ringlets are configured with the same value.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring the Clock Source
To configure the clock source for the interface, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Source Address Tracking
To count packets from a specified source on the ringlet, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Troubleshooting Tips
Use the show rpr-ieee source-counters command to view the source address counters.
Router# show rpr-ieee source-countersSource Address Information for Interface RPR-IEEE1/10001.0001.0001, index 0, pkt. count 0, byte count 00003.0003.0003, index 1, pkt. count 0, byte count 0Configuring the SONET/SDH Overhead
To configure the SONET/SDH overhead values for the frame header, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring the SONET Framing
To configure the framing for the packet header and trailer to ensure synchronization and error control, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Loopback Mode
To configure the framer into loopback mode, perform the following steps. This task is for diagnostics only and affects ring operation.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring the Reporting of SONET Alarms
To enable the reporting of information regarding various SONET alarms, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
slof | slos} [east | west]DETAILED STEPS
Configuring BER Threshold Values
To configure BER threshold values for various alarms on an RPR interface, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Traffic Rates for Transmission
The different priorities of traffic can be configured with rate limiters and prescribed specific bandwidths. This configuration may differ on the east and west spans, or can be configured equally on both. Also, transmitted idle packets can be configured to partake in rate synchronization.
The highest-priority traffic, known as service class A0, can reserve a portion of total ringlet bandwidth using the reserved keyword. This reservation is propagated throughout the ringlet, and all stations recognize the bandwidth allocation cumulatively. Reserved A0 bandwidth can be used only by the station that reserves it. The default allocation is 0 megabits per second.
Service class A1 is configured as high-priority traffic in excess of the A0 bandwidth reservation, and can be rate-limited using the high tx-traffic rate limiter. The default allocation is 10 megabits per second.
The medium transmit traffic rate limiter allows a certain amount of traffic to be added to the ringlet that is not subject to fairness eligibility, but must compete for the unreserved bandwidth with other traffic of the same service class. This traffic is committed information rate (B-CIR) traffic. Some interfaces may not support this class of traffic, so this command may not be available on all RPR interfaces. The default allocation is 10 megabits per second.
The low transmit traffic rate limiter restricts the amount of bandwidth that service classes B-EIR and C may use on the ringlet. This traffic class is fairness eligible and thus this value impacts the effectiveness of the fairness algorithm. The default allocation is full bandwidth.
The idle packet transmitter approximately synchronizes rates between stations by padding traffic with idle packets transmitted at a certain rate. Idle packets are transmitted only to the neighbor, and therefore do not take up transit queue space. If the transit queue vacancy of the local station falls below the configurable idle threshold, fewer idle packets are transmitted by the local station to give more transmit time to drain the queue. This rate synchronization is used in the extreme congestion case to prevent packet drops in the transit queue.
Traffic can be specified to be in strict or relaxed mode. Relaxed mode does not flush (drop) traffic in case of a protection event, such as a fiber failure. As a result, there is less traffic loss but a slight possibility of re-ordering packets during a node recovery. Relaxed mode is the default traffic mode. Strict mode flushes traffic after a topology change, such as a protection event, until the topology stabilizes.
To configure transmit traffic rates, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Troubleshooting Tips
Use the show rpr-ieee rate-limit command to view the configured values for the rate manipulators on the various classes of traffic. There are rate limiters for classes A0 (or reserved), A1, B-CIR, and B-EIR and C. Some interfaces don't support class B on transmit, so only the other three are displayed.
Following is sample output from the show rpr-ieee rate-limit command:
Router# show rpr-ieee rate-limitRate Limit Information for Interface RPR-IEEE1/1West Span:Reserved Bandwidth (Class A0): 0 MbpsRate Limiter High (Class A1): 10 MbpsRate Limiter Medium (Class B-CIR): 10 MbpsRate Limiter Low (Class B-EIR, C): 2488 MbpsEast Span:Reserved Bandwidth (Class A0): 0 MbpsRate Limiter High (Class A1): 10 MbpsRate Limiter Medium (Class B-CIR): 10 MbpsRate Limiter Low (Class B-EIR, C): 2488 MbpsFollowing is sample output from the show rpr-ieee rate-limit command when no low rate limit is configured. In this instance, full is shown. This is equivalent to having a rate limit of 2488 Mbps configured on an OC48 link.
Router# show rpr-ieee rate-limitWest Span:Reserved Bandwidth (Class A0): 0 MbpsRate Limiter High (Class A1): 10 MbpsRate Limiter Medium (Class B-CIR): 10 MbpsRate Limiter Low (Class B-EIR, C): fullUse the details keyword to display the idle packet transmission configuration, as shown in the following example:
router# show rpr-ieee rate-limit detailsRate Limit Information for Interface RPR-IEEE1/1West Span:Reserved Bandwidth (Class A0): 0 MbpsRate Limiter High (Class A1): 10 MbpsRate Limiter Medium (Class B-CIR): 10 MbpsRate Limiter Low (Class B-EIR, C): 2488 MbpsEast Span:Reserved Bandwidth (Class A0): 0 MbpsRate Limiter High (Class A1): 10 MbpsRate Limiter Medium (Class B-CIR): 10 MbpsRate Limiter Low (Class B-EIR, C): 2488 MbpsService Type: RelaxedIdle Shaper is EnabledTransmit at 500 packets per million when PTQ vacancy above 18432 bytesTransmit at 250 packets per million when PTQ vacancy below 18432 bytesHow to Configure RPR Fairness
A larger enhancement of RPR over DPT is its configurable fairness system, used to control congestion on each ringlet. This feature moderates bandwidth utilization of the ringlet to minimize and potentially eliminate starvation of any station. Each station has two instances of the fairness machine, to control traffic that is being transmitted and transited out of each span of the interface. Each fairness machine is devoted to a particular ringlet, and controls the traffic that is destined to that ringlet.
Fairness is configured in the west and east directions independently. Each ringlet in an unwrapped ring is independent, and thus the fairness configuration can differ for each direction.
To configure RPR fairness, perform the following tasks:
•
•
Configuring Active Weights
IEEE 802.17 fairness is a weighted process for negotiating fair rates. By default, all weights are set to the lowest possible value (1), and this results in equal-weight fairness. If any station is configured with a higher weight, then weighted fairness is activated. In aggressive fairness mode, this happens automatically and a station uses its own weight to determine the fair transmission rate. In conservative fairness mode, the station uses its own weight and weights detected from upstream stations to determine its fair transmission rate. If you do not want conservative fairness mode to use detected weights in the fair-rate calculation, you can disable the active-weight detection (which is enabled by default). Active-weight detection affects only conservative fairness mode when weights are not set to their lowest value.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Fairness Rate Adjustments
The fairness rate adjustment method can be changed to one of two modes. Only one mode is selectable at a time on an interface. Switching between modes can be disruptive to traffic because it requires that the fairness machine completely restart with new initial values. Aggressive and conservative stations can be configured on the same ringlet, but more consistent operation results from using one or the other on every station. Aggressive rate adjustment is the default setting.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Multichoke Fairness
Multichoke fairness enables enhanced fairness beyond a single congestion point. This feature may not be supported on all platforms and is optional in the 802.17 standard. It is disabled by default.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Fairness Weights
The local station weight impacts how congested the station appears with respect to other stations in the ringlet. It also affects how much more bandwidth a station may use over other stations in the ring. A higher weight tends to result in giving the local station more than its fair share of ringlet bandwidth compared with its neighbors. Lower weights tend to result in less bandwidth demand from the local station. The default value is 0 configured as an exponent of 2, which yields an effective weight of 1.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Troubleshooting Tips
To view the fairness information, use the show rpr-ieee fairness command. The fairness system uses a large quantity of input to determine its behavior. This input and some results of the fairness algorithm can be displayed. Information for both directions is always shown. The following example shows what would be seen on an OC-48 interface employing aggressive rate adjustment, with no multichoke fairness.
Router# show rpr-ieee fairnessIEEE 802.17 Fairness on RPR-IEEE1/1:Bandwidth: 2488320 kilobits per secondStation using aggressive rate adjustment.Westbound Tx (Ringlet 1)Weighted Fairness:Local Weight: 0 (1)Single-Choke Fairness Status:Local Congestion:Congested? NoHead? NoDownstream Congestion:Congested? NoTail? NoReceived Source Address: 0001.0001.0001Reserved Rate:0 KbpsUnreserved Rate:2488320 KbpsEastbound Tx (Ringlet 0)Weighted Fairness:Local Weight: 0 (1)Single-Choke Fairness Status:Local Congestion:Congested? NoHead? NoDownstream Congestion:Congested? NoTail? NoReceived Source Address: 0003.0003.0003Reserved Rate:0 KbpsUnreserved Rate:2488320 KbpsThis information can also be viewed in a more detailed form by using the details keyword. The additional information includes the coefficients used, more expressions of the configured and detected rates, and transit queue information.
How to Configure RPR Protection
RPR includes steering and wrapping protection. A number of tasks can be used to configure the protection capabilities:
•
•
•
•
•
•
Configuring the Hold-off Timer
A protection response to Layer 1 failure events (such as a signal failure or signal degradation) can be delayed by configuring the hold-off timer. A higher value for this timer causes a protection response to be delayed, avoiding link errors that persist long enough to be detected by protection but short enough to avoid costs of protecting the span. This delay can result in higher traffic loss, however. The default value for this timer is 0 milliseconds.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Protection Preferences
The interface can be configured to support jumbo frames and wrapping. These commands are not mutually exclusive.
The jumbo setting specifies that the station support an MTU of up to 9100 bytes. To be enabled, all stations on the ring must be set to support jumbo frames. The wrap setting specifies that by default the station use wrapping instead of steering.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Forced or Manual Switching
You can request certain protection states to take effect manually on either span of the interface, to avoid link usage or in anticipation of failures.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring SONET Protection
For SONET-based devices, RPR can set the threshold at which a protection event occurs for a signal failure or signal degradation (sf-ber or sd-ber).
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Protection Timers
Protection messages are sent based on the intervals of two timers. These timers apply under different circumstances:
•
•
The protection timers are configured the same on both spans of an interface.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring the Wait-to-Restore Timer
When a failure is de-asserted on a span, a wait-to-restore timer defines how long before the span becomes unprotected. This timer can be used to protect against false negatives in the detection of the failure status, and thus avoid protection-flapping by using larger values. Smaller values result in faster recovery times, however. This timer can be configured between 0 and 1440 seconds, or configured to not recover automatically at all. The default for the timer is 10 seconds.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Protection Troubleshooting Tips
To verify the protection configurations, use the show rpr-ieee protection command. Following is sample output from this command:
Router# show rpr-ieee protectionProtection Information for Interface RPR-IEEE1/1MAC AddressesWest Span (Ringlet 0 RX) neighbor 0001.0001.0001East Span (Ringlet 1 RX) neighbor 0003.0003.0003Station MAC address 0002.0002.0002TP frame sending timers:fast timer: 10 msecslow timer: 1x100 msec (100 msec)Protection holdoff timers:L1 Holdoff Keepalive DetectionWest Span 0x10 msec ( 0 msec) West Span 3 msecEast Span 0x10 msec ( 0 msec) East Span 3 msecConfigured protection mode: STEERINGProtection StatusRing is IDLEProtection WTR period is 10 sec. (timer is inactive)Self Detected Requests Remote RequestsWest Span IDLE West Span IDLEEast Span IDLE East Span IDLEDistant RequestsEast Span IDLE West Span IDLEWest Span Failures: noneEast Span Failures: noneShutting Down a Span
To cause a forced switch on the span of the interface, perform the following steps. The rpr-ieee shutdown command performs the same task as the rpr-ieee protection request forced-switch command.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Keepalive Events
A station can determine whether a link is alive if it is receiving fairness messages from it. This feature is independent of the fairness algorithm itself, but is nonetheless a function performed by the fairness machine. The number of milliseconds that pass without receiving a fairness message from the neighboring stations is measured. When this time exceeds a configured timeout, then a keepalive event is triggered, which generates a protection event. The timer may have a different value on either span. The keepalive timer should be configured greater than or equal to the hold-off timer. The default keepalive timer is 3 milliseconds.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
How to Use Modular QoS CLI to Configure RPR Service Classes
Layer 3 prioritized traffic is directed to the three service classes supported by RPR by using the Modular QoS CLI (MQC). MQC is a CLI structure that allows you to create traffic policies and attach these policies to interfaces. A traffic policy contains a traffic class and one or more QoS features. A traffic class classifies traffic, while the QoS features in the traffic policy determine how to treat the classified traffic.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
Configuration Example Using MQC to Configure RPR Service Classes
Following is an example of the entire configuration process for the three RPR service classes:
class-map match-any RPR_Amatch ip precedence 6 7class-map match-any RPR_Bmatch ip precedence 4 5class-map match-any RPR_Cmatch ip precedence 0 1 2 3policy-map RPR_CLASSclass RPR_Ashape 2488320set rpr-ieee service-class aclass RPR_Bshape 2488320set rpr-ieee service-class bclass RPR_Cshape 2488320set rpr-ieee service-class cinterface rpr-ieee1/1service-policy output RPR_CLASSTroubleshooting Tips
To verify the service class configurations, use the following commands:
Following is sample output from the show policy-map command:
Router# show policy-map RPR_CLASSPolicy Map RPR_CLASSClass RPR_Ashape 2488320set rpr-ieee service-class aClass RPR_Bshape 2483320set rpr-ieee service-class bClass RPR_Cshape 2488320set rpr-ieee service-class cFollowing is sample output from the show policy-map interfaces command:
Router# show policy-map interfaces rpr-ieee1/1Service-policy output: RPR_CLASS (1047)Class-map: RPR_A (match-any) (1083/4)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 6 7 (1084)shape (VCCI 2->side E): 2488320 kbpsshape (VCCI 3->side W): 2488320 kbpsQoS Setrpr-ieee service-class aPackets marked 0Class-map: RPR_B (match-any) (1105/5)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 4 5 (1106)shape (VCCI 2->side E): 2481023 kbpsshape (VCCI 3->side W): 2481023 kbpsQoS Setrpr-ieee service-class bPackets marked 0Class-map: RPR_C (match-any) (1122/6)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 0 1 2 3 (1123)shape (VCCI 2->side E): 2488320 kbpsshape (VCCI 3->side W): 2488320 kbpsQoS Setrpr-ieee service-class cPackets marked 0Class-map: class-default (match-any) (1059/0)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: any (1060)0 packets, 0 bytes5 minute rate 0 bpsHow to Verify RPR Configuration and Operation
To verify RPR configuration and operation, perform the following tasks:
•
Viewing Traffic Counters
Traffic counters are collected from various sources in the interface, and are displayed using the show rpr-ieee counters command. This command shows received, transited, and transmitted quantities of each of the various service classes, and on each span. Receive errors are also indicated for each span. Following is sample output from the show rpr-ieee counters command:
Router# show rpr-ieee countersData Traffic Counters for Interface RPR-IEEE1/1WEST Span:Transit Packets BytesTotal Low Priority 0 0Total Med EIR Priority 0 0Total Med CIR+EIR Priority 0 0Total High Priority 0 0Total Multicast 0 0Total Unicast 0 0Host Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Host Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Traffic Rate (5 Minutes) packets/sec bits/secTransit Low Priority 0 0Transit Med EIR Priority 0 0Transit Med CIR+EIR Priority 0 0Transit High Priority 0 0Transit Multicast 0 0Transit Unicast 0 0Host Receive 0 0Total Receive 0 0Host Transmit 0 0Total Transmit 0 0Received Errors:0 input errors, 0 CRC, 0 ignored,0 framer runts, 0 framer giants, 0 framer aborts,0 mac runts, 0 mac giants, 0 mac ttl strips,0 non-we dropEAST Span:Transit Packets BytesTotal Low Priority 0 0Total Med EIR Priority 0 0Total Med CIR+EIR Priority 0 0Total High Priority 0 0Total Multicast 0 0Total Unicast 0 0Host Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Host Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Traffic Rate (5 Minutes) packets/sec bits/secTransit Low Priority 0 0Transit Med EIR Priority 0 0Transit Med CIR+EIR Priority 0 0Transit High Priority 0 0Transit Multicast 0 0Transit Unicast 0 0Host Receive 0 0Total Receive 0 0Host Transmit 0 0Total Transmit 0 0Received Errors:0 input errors, 0 CRC, 0 ignored,0 framer runts, 0 framer giants, 0 framer aborts,0 mac runts, 0 mac giants, 0 mac ttl strips,0 non-we dropViewing Failures
The show rpr-ieee failures command displays all input used to determine the failure state of each span of the interface. This information can be used to debug the cause of a protection event. Following is sample output from this command:
Router# show rpr-ieee failuresSelf Detected Failures Information for Interface RPR-IEEE1/1Span WEST:Reported Debounced Current Stable Debouncestate state state for(sec) delay(sec)HW missing IDLE IDLE IDLE 22641 0Layer 1 IDLE IDLE IDLE 22629 0MAC Keepalive IDLE IDLE IDLE 22640 10Link quality IDLE IDLE IDLE 22641 0Mate interface IDLE IDLE IDLE 22641 10Span mismatch IDLE IDLE IDLE 22641 0Result Self Detect = IDLESpan EAST:Reported Debounced Current Stable Debouncestate state state for(sec) delay(sec)HW missing IDLE IDLE IDLE 22641 0Layer 1 IDLE IDLE IDLE 22630 0MAC Keepalive IDLE IDLE IDLE 22640 10Link quality IDLE IDLE IDLE 22641 0Mate interface IDLE IDLE IDLE 22642 10Span mismatch IDLE IDLE IDLE 22642 0Result Self Detect = IDLEViewing the RPR Topology
The show rpr-ieee topology command provides information on the local station, its neighbors, and the general state of the ring. Packets sent to communicate topology information are constructed using data from various sources, such as the configured preferences, cumulative reserved bandwidth, protection states, and station name. This information is displayed for the local station and every active station from which a topology message has been received.
Following is sample output from the show rpr-ieee topology command:
Router# show rpr-ieee topologyRing Topology: CLOSED (STABLE)Configured protection mode: WRAPPINGJumbo preference: SET (ring supports JUMBOS)Number of nodes onringlet0: 3 ringlet1: 3Checksum: 0x001800D6Index (Ri 0) MAC IP Address Edge W/E Request W/E1 0001.0001.0001 1.1.1.1 NO/NO IDLE/IDLE2 0003.0003.0003 1.1.1.3 NO/NO IDLE/IDLE3 0002.0002.0002 1.1.1.2 NO/NO IDLE/IDLEIndex (Ri 1) MAC IP Address Edge W/E Request W/E1 0003.0003.0003 1.1.1.3 NO/NO IDLE/IDLE2 0001.0001.0001 1.1.1.1 NO/NO IDLE/IDLE3 0002.0002.0002 1.1.1.2 NO/NO IDLE/IDLEFollowing is sample output from the show rpr-ieee topology details command:
Router# show rpr-ieee topology details802.17 Topology DisplayRX ringlet0->West span RX ringlet1->East spanNumber of nodes onringlet0: 3 ringlet1: 3=======================================================================Local Station Topology Info=======================================================================Topology entry:Station MAC address: 0002.0002.0002West Span (Outer ringlet RX) neighbor 0001.0001.0001East Span (Inner ringlet RX) neighbor 0003.0003.0003Ring Topology: CLOSED (STABLE)Containment Active: NOA0 class reserved rate:ringlet0: 0 (mbps) ringlet1: 0 (mbps)Ringlet reserved rate:ringlet0: 0 (mbps) ringlet1: 0 (mbps)Ringlet unreserved rate:ringlet0: 2488 (mbps) ringlet1: 2488 (mbps)Advertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOConfigured protection mode: WRAPPINGJumbo preference: SET (ring supports JUMBOS)Is revertive: YESMeasured LRTT: 0Sequence Number: 4ATD INFO:ATD timer: 0 secStation Name: RouterA0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 0 ringlet1: 0Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology Map for Outer ringlet==============================================================================================================================================Topology entry at Index 1 on ringlet 0:Station MAC address: 0001.0001.0001Valid on ringlet0: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: WRAPPINGJumbo preference: SET (ring supports JUMBOS)Measured LRTT: 0Sequence Number: 54ATD INFO:Station Name: RouterA0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 0 ringlet1: 0Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology entry at Index 2 on ringlet 0:Station MAC address: 0003.0003.0003Valid on ringlet0: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: WRAPPINGJumbo preference: SET (ring supports JUMBOS)Measured LRTT: 0Sequence Number: 40ATD INFO:Station Name: RouterA0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 0 ringlet1: 0Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology entry at Index 3 on ringlet 0:Station MAC address: 0002.0002.0002Valid on ringlet0: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: WRAPPINGJumbo preference: SET (ring supports JUMBOS)Measured LRTT: 0Sequence Number: 4ATD INFO:Station Name: RouterA0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 0 ringlet1: 0Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology Map for Inner ringlet==============================================================================================================================================Topology entry at Index 1 on ringlet 1:Station MAC address: 0003.0003.0003Valid on ringlet1: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: WRAPPINGJumbo preference: SET (ring supports JUMBOS)Measured LRTT: 0Sequence Number: 40ATD INFO:Station Name: RouterA0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 0 ringlet1: 0Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology entry at Index 2 on ringlet 1:Station MAC address: 0001.0001.0001Valid on ringlet1: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: WRAPPINGJumbo preference: SET (ring supports JUMBOS)Measured LRTT: 0Sequence Number: 54ATD INFO:Station Name: RouterA0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 0 ringlet1: 0Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology entry at Index 3 on ringlet 1:Station MAC address: 0002.0002.0002Valid on ringlet1: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: WRAPPINGJumbo preference: SET (ring supports JUMBOS)Measured LRTT: 0Sequence Number: 4ATD INFO:Station Name: RouterA0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 0 ringlet1: 0Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)Viewing Transit Buffer Delays
Use the show rpr-ieee transit command to display transit buffer delays for each span.
Router# show rpr-ieee transitTransit Buffer Delay Counters for Interface RPR-IEEE1/1WEST Span:Transit Delay (5 Minutes) NanosecondsLow TB Min Delay: 720Low TB Avg Delay: 761Low TB Max Delay: 800High TB Min Delay: 440High TB Avg Delay: 504High TB Max Delay: 580EAST Span:Transit Delay (5 Minutes) NanosecondsLow TB Min Delay: 0Low TB Avg Delay: 0Low TB Max Delay: 0High TB Min Delay: 480High TB Avg Delay: 528High TB Max Delay: 580Configuration Example for RPR
The following example shows a typical configuration of an RPR interface:
class-map match-any RPR_HIGHmatch ip precedence 6 7class-map match-any RPR_LOWmatch ip precedence 0 1 2match ip precedence 3 4 5!!policy-map RPR_CLASSclass RPR_HIGHshape 2488320set rpr-ieee service-class aclass RPR_LOWshape 2488320set rpr-ieee service-class cinterface RPR-IEEE1/1mac-address 0002.0002.0002ip address 1.1.1.2 255.255.255.0no ip directed-broadcastrpr-ieee count 0001.0001.0001rpr-ieee count 0003.0003.0003rpr-ieee fairness mode aggressiverpr-ieee protection pref wraprpr-ieee protection pref jumborpr-ieee protection wtr-timer 60rpr-ieee tx-traffic rate-limit reserved 10 eastrpr-ieee tx-traffic rate-limit reserved 10 westrpr-ieee tx-traffic rate-limit high 100 eastrpr-ieee tx-traffic rate-limit high 100 westno cdp enableservice-policy output RPR_CLASSendAdditional References
The following sections provide references related to RPR.
Related Documents
Standards
MIBs
•
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
Technical Assistance
Command Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0S command reference publications.
•
•
•
•
•
•
•
•
•
•
•
interface rpr-ieee
To configure an RPR interface, use the interface rpr-ieee command in global configuration mode.
interface rpr-ieee slot/port
Syntax Description
Defaults
No interface types are configured
Command Modes
global configuration
Command History
Usage Guidelines
This command is used to enter interface configuration mode on an RPR interface.
Examples
The following example specifies to configure the first interface in slot 1:
router(config)# interface rpr-ieee1/0Related Commands
ping rpr-ieee oam-echo
To perform an 802.17 echo, use the ping rpr-ieee oam-echo command in privileged EXEC mode.
ping rpr-ieee oam-echo source rpr-ieee [slot/port] dest-address {r0 | r1} {r0 | r1 | rev} [count] [timeout]
Syntax Description
Defaults
count: 1
timeout: 2 secondsCommand Modes
Privileged EXEC
Command History
Usage Guidelines
This command applies to RPR interfaces only.
This command performs an 802.17 Echo, which is basically a Layer 2 ping. It is independent of any Layer 3 configuration and is designed to test ring connectivity in the absence of any upper layers. The command uses specific 802.17 control packets designed for the purpose. The command allows you to test each ringlet to each station independently and thereby verify all Layer 2 connections.
If you enter the ping command without any other syntax (ping<cr>), the CLI displays an interactive system dialog that prompts you for the additional syntax appropriate to the protocol you specify (See the "Examples" section).
To exit the interactive ping dialog before responding to all prompts, type the escape sequence. The default escape sequence is Ctrl-^,X (simultaneously press and release the Ctrl, Shift, and 6 keys and then press the X key). The escape sequence varies depending on your line configuration. For example, another commonly used escape sequence is Ctrl-c.
Table 1 describes the test characters sent by the ping facility.
Examples
The following example requests 10 OAM echoes to address 0002.0002.0002:
router(config-if)# ping rpr-ieee oam-echo source rpr-ieee 1/1 2.2.2 r0 r1 10 2Type escape sequence to abort.Sending 10 RPR-IEEE OAM Echoes to 0002.0002.0002, timeout is 2 seconds:!!!!!!!!!!Success rate is 100 percent (10/10), round-trip min/avg/max = 1/1/4 msAfter you enter the ping command in privileged EXEC mode, the system prompts you for a protocol keyword. The default protocol is IP.
If you enter a host name or address on the same line as the ping command, the default action is taken as appropriate for the protocol type of that name or address.
The following example is sample dialog from the ping command using rpr-ieee as the protocol and other default values.
Router# pingProtocol [ip]: rpr-ieeeRPR-IEEE Interface: rpr-ieee1/1Destination MAC address: 2.2.2Request ringlet ID <0-1> [0]:Response ringlet ID (r0, r1 or rev) <0-2> [0]:Repeat Count [5]:Timeout [2]:Type escape sequence to abort.Sending 5 RPR-IEEE OAM Echoes to 0002.0002.0002, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 msrpr-ieee atd-timer
To configure the attribute discovery timer (ATD), use the rpr-ieee atd-timer command in interface configuration mode. To restore the default timer value, use the no form of this command.
rpr-ieee atd-timer seconds
no rpr-ieee atd-timer
Syntax Description
seconds
Specifies the time, in seconds, within which one station attributes packet is sent for each ringlet. The default is one packet for each ringlet per second.
Defaults
1 second
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Use this command to configure the attribute discovery timer. Because station attributes are communicated separately from topology and protection packets, there is a separate timer to control the frequency at which these packets are sent. Attribute propagation is therefore determined by the ATD timer. Both ringlets are configured with the same value.
Examples
The following example sets the ATD timer to be 2 seconds:
router(config-if)# rpr-ieee atd-timer 2Related Commands
Displays the RPR protection, topology, counters, and transit information for an RPR interface.
Configures the wait-to-restore timer.
rpr-ieee clock-source
To configure the clock source, use the rpr-ieee clock-source interface configuration command. To restore the default clock source, use the no form of this command.
rpr-ieee clock-source {line | internal} [east | west]
no rpr-ieee clock-source [east | west]
Syntax Description
Defaults
Internal
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
When you configure a connection between two Cisco 10700 Series Routers, you can configure the RPR interfaces for the clock source as follows:
•
•
You can configure the RPR interface on one side of the connection as internal and the RPR interface on the other side as line. This configuration is available for installations in which line timing is desirable, such as Add/Drop Multiplexer (ADM) and Wavelength Division Multiplexing (WDM).
Examples
The following example shows how to configure the clock source:
Router# configure terminalRouter(config)# interface rpr-ieee2/0Router(config-if)# rpr-ieee clock-source line eastRouter(config-if)#Related Commands
rpr-ieee count
To count packets from a specified source address, use the rpr-ieee count command in interface configuration mode. To disable source address packet counting, use the no form of this command.
rpr-ieee count src-address
no rpr-ieee count src-address
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Examples
The following example shows how to enable packet counting on the source address 1.1.1:
Router(config-if)# rpr-ieee count 1.1.1Related Commands
rpr-ieee fairness active-weights-detect
To enable the calculation of ringlet weights from stations that have recently contributed traffic over a configurable interval from the specified direction, use the rpr-ieee fairness active-weights-detect command in interface configuration mode. To disable the use of these weights, use the no form of this command.
rpr-ieee fairness active-weights-detect [east | west]
no rpr-ieee fairness active-weights-detect [east | west]
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
IEEE 802.17 fairness is a weighted process for negotiating fair rates. Disabling equal-weight fairness is done by configuring the lowest weight for the local station, and disabling active-weights-detect. Disabling equal-weight fairness removes any effect of weights from both the rate adjustment process, and also from the rates advertised to neighbors. When active-weights is enabled, however, it allows for the calculation of ringlet weights from stations that have recently contributed traffic.
Examples
The following example shows how to enable the calculation of ringlet weights on the east span:
Router(config-if)# rpr-ieee fairness active-weight-detect eastRelated Commands
rpr-ieee fairness mode
To specify the fairness rate adjustment method, use the rpr-ieee fairness mode command in interface configuration mode.
rpr-ieee fairness mode {aggressive | conservative}
Syntax Description
Defaults
Aggressive
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
The fairness rate adjustment method can be changed to one of two modes. Only one mode is selectable at a time for either direction. Switching between modes can be disruptive to traffic because it requires that the fairness machine completely restart with new initial values. Aggressive and conservative stations can be configured on the same ringlet, but more consistent operation results from using one or the other on every station.
Examples
The following example shows how to enable aggressive ramping for the fairness algorithm:
Router(config-if)# rpr-ieee fairness mode aggressive
Related Commands
rpr-ieee fairness multi-choke
To enable multichoke fairness on an interface, use the rpr-ieee fairness multi-choke command in interface configuration mode. To disable multichoke fairness, use the no form of this command.
rpr-ieee fairness multi-choke
no rpr-ieee fairness multi-choke
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Multichoke fairness enables enhanced fairness beyond a single congestion point. This feature may not be supported on all platforms and is optional in the 802.17 standard. It is disabled by default.
Examples
The following example shows how to enable multichoke fairness:
Router(config-if)# rpr-ieee fairness multi-choke
Related Commands
rpr-ieee fairness weight
To specify the weight for a station on an RPR ringlet, use the rpr-ieee fairness weight command in interface configuration mode. To restore the default fairness weight, use the no form of this command.
rpr-ieee fairness weight weight [east | west]
no rpr-ieee fairness weight weight [east | west]
Syntax Description
Defaults
0
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
The weight of the local station impacts how congested the station appears with respect to other stations in the ringlet. It also affects how much more bandwidth a station may use over other stations in the ring. A higher weight tends to result in giving the local station more than its fair share of ringlet bandwidth compared with its neighbors. A lower weight tends to result in less bandwidth demand from the local station. The default is 0 configured as an exponent of 2, which yields an effective weight of 1.
Examples
The following example shows how to set the weight of the east span to be 26 or 64:
Router(config-if)# rpr-ieee fairness weight 6 eastRelated Commands
rpr-ieee flag
To specify SONET/SDH overhead values for the frame header, use the rpr-ieee flag command in interface configuration mode. To restore the default overhead values, use the no form of this command.
rpr-ieee flag {c2 | j0} value [east | west]
no rpr-ieee flag {c2 | j0} value [east | west]
Syntax Description
Defaults
c2 value: 0x16
j0 value: 0x01Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Specify the value of the flag in decimal format.
Note that the j0 0x01 flag is specified indirectly by the choice of SONET or SDH framing in the rpr-ieee framing command.
Examples
The following example shows the use of the rpr-ieee flag command to specify the SONET/SDH overhead values on both the east and west spans of an RPR interface:
Router(config-if)# rpr-ieee flag j0 1Related Commands
Specifies framing for the packet header and trailer to ensure synchronization and error control.
rpr-ieee framing
To specify framing for the packet header and trailer to ensure synchronization and error control, use the rpr-ieee framing command in interface configuration mode. To restore the default framing, use the no form of this command.
rpr-ieee framing {sdh | sonet} [east | west]
no rpr-ieee framing {sdh | sonet} [east | west]
Syntax Description
Defaults
sonet
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Examples
The following example sets the framing to SDH on both the east and west spans:
Router(config-if)# rpr-ieee framing sdhRelated Commands
rpr-ieee keepalive-timer
To configure the amount of time to wait before a keepalive event is triggered on an RPR interface, use the rpr-ieee keepalive-timer command in interface configuration mode. To restore the default timer value, use the no form of this command.
rpr-ieee keepalive-timer time [east | west]
no rpr-ieee keepalive-timer time [east | west]
Syntax Description
Defaults
3 milliseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
A station can determine whether a link is alive if it is receiving fairness messages from it. This feature is independent of the fairness algorithm itself, but is nonetheless a function performed by the fairness machine. The number of milliseconds that pass without receiving a fairness message from the neighboring stations is measured. When this time exceeds the keepalive timeout value, then a keepalive event is triggered, which may generate a protection event. The timer may have a different value on either span.
Examples
The following example shows how to set the keepalive timer to 5 milliseconds:
Router(config-if)# rpr-ieee keepalive-timer 5 westRelated Commands
Displays the RPR protection, topology, counters, and transit information for an RPR interface.
rpr-ieee loopback
To configure the framer into loopback mode, use the rpr-ieee loopback command in interface configuration mode. To disable loopback mode, use the no form of this command.
rpr-ieee loopback {internal | line} {east | west}
no rpr-ieee loopback {internal | line} {east | west}
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
This command is for diagnostics only and affects ring operation.
Examples
The following example configures the framer into loopback mode:
Router(config-if)# rpr-ieee loopback internal westRelated Commands
Displays the status of RPR interfaces on the router.
Displays the status of the RPR Layer 1 controller information on the router.
rpr-ieee report
To enable reporting of selected alarms, use the rpr-ieee report interface configuration command. Use the no form of this command to restore the default value.
rpr-ieee report {b1-tca | b2-tca | b3-tca | lais | lrdi | pais | plop | prdi | sd-ber | sf-ber |
slof | slos} [east | west]no rpr-ieee report [b1-tca | b2-tca | b3-tca | lais | lrdi | pais | plop | prdi | sd-ber | sf-ber |
slof | slos] [east | west]Syntax Description
Defaults
Reporting enabled for section loss-of-signal (SLOS), section loss-of-frame (SLOF), and path loss-of-pointer (PLOP) errors.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
To determine which alarms are reported on the RPR interface, use the show controllers rpr-ieee command.
Examples
The following example shows how to use the rpr-ieee report command to enable reports for the SD-BER and LAIS alarms on an RPR interface:
Router(config-if)# rpr-ieee report sd-berRouter(config-if)# rpr-ieee report laisRelated Commands
rpr-ieee protection sonet holdoff-timer
To specify a delay before a protection response is sent, use the rpr-ieee protection sonet holdoff-timer command in interface configuration mode. To disable the hold-off timer, use the no form of this command.
rpr-ieee protection sonet holdoff-timer time [east | west]
no rpr-ieee protection sonet holdoff-timer time [east | west]
Syntax Description
Defaults
0 milliseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
A protection response to Layer 1 failure events (such as a signal failure or signal degradation) can be delayed by configuring the hold-off timer. A higher value for this timer causes a protection response to be delayed, avoiding link errors that persist long enough to be detected by protection but short enough to avoid costs of protecting the span. This higher value can result in higher traffic loss, however. The default for this timer is 0 milliseconds.
Examples
The following example shows how to configure the hold-off timer:
Router(config-if)# rpr-ieee protection sonet holdoff-timer 5 westRelated Commands
Displays the RPR protection, topology, counters, and transit information for an RPR interface.
rpr-ieee protection pref jumbo
To enable handling of jumbo frames, use the rpr-ieee protection pref jumbo command in installation configuration mode. To disable this option, use the no form of this command.
rpr-ieee protection pref jumbo
no rpr-ieee protection pref jumbo
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
This command enables handling of frames in excess of the standard 1500 bytes, up to a maximum size of 9100 bytes. If you configure the MTU to be jumbo (9100 bytes) it does not take effect unless all stations on the ring are configured to support jumbo frames. A warning message is displayed if the MTU is inconsistent between stations. A message is also displayed when the MTU value is changed.
Examples
The following example enables handling of jumbo frames:
Router(config-if)# rpr-ieee protection pref jumboRelated Commands
Displays the RPR protection, topology, counters, and transit information for an RPR interface.
rpr-ieee protection pref wrap
To enable the preference of wrapping protection instead of steering, use the rpr-ieee protection pref wrap command in installation configuration mode. To remove wrapping preference, use the no form of this command.
rpr-ieee protection pref wrap
no rpr-ieee protection pref wrap
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Stations can be made to prefer wrapping protection instead of steering, as long as conditions permit. Such a station use wrapping for protection only if every other station in the ring is also wrap preferred. This option is disabled by default to prefer steering. No warning message is displayed if the ring protection mode between stations is inconsistent.
Examples
The following example enables the preference of wrapping protection:
Router(config-if)# rpr-ieee protection pref wrapRelated Commands
Displays the RPR protection, topology, counters, and transit information for an RPR interface.
rpr-ieee protection request forced-switch
To initiate a forced switch, use the rpr-ieee protection request forced-switch command in interface configuration mode. To disable a forced switch, use the no form of this command.
rpr-ieee protection request forced-switch
no rpr-ieee protection request forced-switch
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
A forced switch precedes all other failure events on a ring, for the span on which it is configured. The operation protects the span indicated by the command. In the case of steering, forwarding uses only the topology list for the opposite span. In the case of wrapping, the other span becomes wrapped.
A forced switch is saved in the router configuration.
Examples
The following example shows the initiation of a forced switch on the east span:
Router(config-if)# rpr-ieee protection request forced-switch eastRelated Commands
rpr-ieee protection request manual-switch
To initiate a manual switch, use the rpr-ieee protection request manual-switch command in interface configuration mode. To disable the manual switch, use the no form of this command.
rpr-ieee protection request manual-switch
no rpr-ieee protection request manual-switch
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
A manual switch behaves similarly to a forced switch, in that it coerces a reaction from the protection system. The difference is that this configuration can be usurped by higher-level requests detected on the configured or opposite span.
A manual switch is not saved in the router configuration.
Examples
The following example shows the initiation of a manual switch on the west span:
Router(config-if)# rpr-ieee protection request manual-switch westRelated Commands
Initiates a forced switch on a span of the interface.
Displays the RPR protection, topology, counters, and transit information for an RPR interface.
rpr-ieee protection sonet threshold
To enable SONET protection, use the rpr-ieee protection sonet threshold command in interface configuration mode. To disable SONET protection, use the no form of this command.
rpr-ieee protection sonet threshold {sd-ber threshold | sf-ber threshold} [east | west]
no rpr-ieee protection sonet threshold {sd-ber threshold | sf-ber threshold} [east | west
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
For SONET-based devices, RPR can set the threshold at which a protection event occurs for a signal failure or signal degradation (sf-ber or sd-ber). This feature can be configured differently on either span.
Examples
The following example shows how to set the signal degradation threshold to 10-6:
Router(config-if)# rpr-ieee protection sonet threshold sd-ber 6rpr-ieee protection timer
To control the frequency of the transmission of protection requests, use the rpr-ieee protection timer command in interface configuration mode. To restore the default timer value, use the no form of this command.
rpr-ieee protection timer {fast time | slow time}
no rpr-ieee protection timer {fast time | slow time}
Syntax Description
Defaults
fast—10 milliseconds; slow—1x100 milliseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Protection messages are sent based on the intervals of two timers. These timers apply under different circumstances:
•
•
Examples
The following example shows how to set the fast protection timer to 10 milliseconds:
Router(config-if)# rpr-ieee protection timer fast 10Related Commands
rpr-ieee protection wtr-timer
To configure the wait-to-restore timer, use the rpr-ieee protection wtr-timer command in interface configuration mode. To restore the default of the timer, use the no form of this command.
rpr-ieee protection wtr-timer {time | never}
no rpr-ieee protection wtr-timer {time | never}
Syntax Description
time
Specifies a value of the wait-to-restore timer in seconds. Values range from 0 to 1440. The default is 10.
never
Specifies that protection is never restored (nonrevertive mode).
Defaults
10 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
When a failure is de-asserted on a span, a wait-to-restore timer defines how long before the span becomes unprotected. This timer can be used to protect against false negatives in the detection of the failure status, and thus avoid protection-flapping by using larger values. Smaller values result in faster recovery times, however.
Examples
The following example shows how to set the wait-to-restore timer to 20 seconds:
Router(config-if)# rpr-ieee protection wtr-timer 20Related Commands
rpr-ieee shutdown
To shut down an RPR interface by entering a forced switch on the span, use the rpr-ieee shutdown command in interface configuration mode. To remove the forced switch on the span, use the no form of this command.
rpr-ieee shutdown {east | west}
no rpr-ieee shutdown {east | west}
Syntax Description
east
Specifies that the configuration is for the east span.
west
Specifies that the configuration is for the west span.
Defaults
Interface not shutdown
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
This rpr-ieee shutdown command is an abbreviated form of the rpr-ieee protection request forced-switch interface configuration command that enters a forced-switch request on the span. The long form, rpr-ieee protection request forced-switch, appears in the show configuration output.
Examples
The following example shows how to disable the RPR interface on the east span:
Router(config-if)# rpr-ieee shutdown eastRelated Commands
Causes a forced switch on the span of an RPR interface.
Shows the status of RPR interfaces on the router.
rpr-ieee threshold
To set the BER threshold values of the specified alarms for an RPR interface, use the rpr-ieee threshold interface configuration command. Use the no form of this command to restore the default value.
rpr-ieee threshold {b1-tca | b2-tca | b3-tca | sd-ber | sf-ber} rate [east | west]
no rpr-ieee threshold {b1-tca | b2-tca | b3-tca | sd-ber | sf-ber} rate [east | west]
Syntax Description
Defaults
The default is 6 (10e-6) for all thresholds except for sf-ber, where the default is 3 (10e-3).
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Examples
The following example shows how to set the rpr-ieee threshold values on the east side of an RPR interface:
Router(config-if)# rpr-ieee threshold sd-ber 8 estRouter(config-if)# rpr-ieee threshold b1_tca 4 eastRelated Commands
Shows current alarm thresholds, along with other information.
Controls reporting of selected alarms.
rpr-ieee tx-traffic idle
To configure transmission of idle packets at various rates to accommodate neighbors that are not capable of higher transmission rates, use the rpr-ieee tx-traffic idle command. Use the no form of this command to disable transmission of idle packets.
rpr-ieee tx-traffic idle {enable | threshold threshold} [east | west]
no rpr-ieee tx-traffic idle {enable | threshold threshold} [east | west]
Syntax Description
Defaults
Enabled with a threshold of 1 MTU.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
The idle packet transmitter approximately synchronizes rates between stations by padding traffic with idle packets transmitted at a certain rate. Idle packets are transmitted only to the neighbor, and therefore do not take up transit queue space. If the transit queue vacancy of the local station falls below the configurable idle threshold, fewer idle packets are transmitted by the local station to give more transmission time to drain the queue. This rate synchronization is used for extreme congestion to prevent packet drops in the transit queue.
Examples
The following example shows how to set the idle threshold to 10000 MTU on the east span:
Router(config-if)# rpr-ieee tx-traffic idle threshold 10000 east
Related Commands
Displays the configured values for the rate manipulators on various classes of traffic.
rpr-ieee tx-traffic rate-limit
To configure the amount of high- and low-priority traffic being transmitted from the router onto the RPR ring, use the rpr-ieee tx-traffic command in interface configuration mode. Use the no form of this command to remove the TX traffic rate from the configuration.
rpr-ieee tx-traffic rate-limit {high | medium | low | reserved} rate [east | west]
no rpr-ieee tx-traffic rate-limit {high | medium | low | reserved} rate [east | west]
Syntax Description
Defaults
0 Mbps for reserved; 10 Mbps for high; full bandwidth for low; 10 Mbps for medium
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
The different priorities of traffic can be configured with rate limiters and prescribed specific bandwidths. This configuration may differ on the east and west spans, or can be configured equally on both.
The highest-priority traffic, known as service class A0, can reserve a portion of total ringlet bandwidth using the reserved keyword. This reservation is propagated throughout the ringlet, and all stations recognize the bandwidth allocation cumulatively. The default allocation is 0 megabits per second.
Service class A1 is configured as high-priority traffic in excess of the A0 bandwidth reservation, and can be rate-limited using the high tx-traffic rate limiter. The default allocation is 10 megabits per second.
The medium transmission traffic rate limiter allows a certain amount of traffic to be added to the ringlet that is not subject to fairness eligibility, but must compete for the unreserved bandwidth with other traffic of the same service class. This traffic is committed information rate (B-CIR) traffic. Some interfaces may not support this class of traffic, so this command may not be available on all RPR interfaces. The default allocation is 10 megabits per second.
The low tx-traffic rate limiter restricts the amount of bandwidth that service classes B-EIR and C may use on the ringlet. This traffic class is fairness eligible and thus this value impacts the effectiveness of the fairness algorithm. The default allocation is full bandwidth.
Examples
The following example shows how to set the high-priority rate limit to 20 Mbps on the west span:
Router(config-if)# rpr-ieee tx-traffic rate-limit high 20 west
Related Commands
Displays the configured values for the rate manipulators on various classes of traffic.
rpr-ieee tx-traffic strict
To specify that traffic be flushed after a topology change, such as a protection event, until the topology stabilizes, use the rpr-ieee tx-traffic strict command. Use the no form of this command to specify not to drop traffic in case of a protection event.
rpr-ieee tx-traffic strict
no rpr-ieee tx-traffic strict
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to RPR interfaces only.
The default TX traffic mode is relaxed, which means that traffic is redirected based on the protection setting as quickly as possible. In some cases, relaxed traffic arrives out of order or is duplicated, but results in less traffic loss during node recovery than strict traffic mode.
Strict traffic is flushed from the ring until the ring topology recovers and is stable. In this way, a possible duplication or re-ordering of strict traffic is prevented. Strict traffic mode results in greater traffic loss than relaxed mode during the topology change.
The traffic mode is configured as relaxed or strict for the router.
Examples
The following example shows how to set the traffic mode to strict:
Router(config-if)# rpr-ieee tx-traffic strict
Related Commands
show controllers rpr-ieee
To display RPR controller information, use the show controllers rpr-ieee command in privileged EXEC mode.
show controllers rpr-ieee [slot/port] [details] [transceiver]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(29)S
This command was introduced.
12.0(30)S
Support for the optional transceiver keyword was added.
Usage Guidelines
This command applies to RPR interfaces only.
Starting in IOS Release 12.0(30)S, use the transceiver keyword to display additional information about the status of the small form-factor pluggable (SFP) module used in an RPR port.
Examples
The following example shows sample output from this command:
Router# show controllers rpr-ieee 1/1Interface RPR-IEEE1/1Hardware is OC48 RPR-IEEERPR-IEEE1/1 - West Span (Ringlet0 RX, Ringlet1 TX)SFP Module West is VALIDOPTICSTX power -4 (+/- 3) dBmRX power -5 (+/- 3) dBmNo Active AlarmsNo Active WarningsSECTIONLOF = 0 LOS = 0 BIP(B1) = 0LINEAIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0PATHAIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0Active Defects: NoneActive Alarms: NoneAlarm reporting enabled for: SLOS SLOF PLOPFraming : SONETRx SONET/SDH bytes: (K1/K2) = 0/0 S1S0 = 0 C2 = 0x16Tx SONET/SDH bytes: (K1/K2) = 0/0 S1S0 = 0 C2 = 0x16 J0 = 0x1Clock source : InternalFramer loopback : NonePath trace buffer : StableRemote hostname : EAST-DRemote interface: RPR-IEEE1/1Remote IP addr : 1.1.1.1Remote side id : EASTBER thresholds: SF = 10e-3 SD = 10e-6IPS BER thresholds(B3): SF = 10e-3 SD = 10e-6TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6RPR-IEEE1/1 - East Span (Ringlet1 RX, Ringlet0 TX)SFP Module East is VALIDOPTICSTX power -4 (+/- 3) dBmRX power -5 (+/- 3) dBmNo Active AlarmsNo Active WarningsSECTIONLOF = 0 LOS = 0 BIP(B1) = 0LINEAIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0PATHAIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0Active Defects: NoneActive Alarms: NoneAlarm reporting enabled for: SLOS SLOF PLOPFraming : SONETRx SONET/SDH bytes: (K1/K2) = 0/0 S1S0 = 0 C2 = 0x16Tx SONET/SDH bytes: (K1/K2) = 0/0 S1S0 = 0 C2 = 0x16 J0 = 0x1Clock source : InternalFramer loopback : NonePath trace buffer : StableRemote hostname : WEST-DRemote interface: RPR-IEEE1/1Remote IP addr : 1.1.1.3Remote side id : WESTBER thresholds: SF = 10e-3 SD = 10e-6IPS BER thresholds(B3): SF = 10e-3 SD = 10e-6TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6The following example shows sample output from this command using the transceiver keyword:
Router# show controllers rpr-ieee 1/1 transceiverShow Transceiver: West SpanStatic informationID: SFP transceiverExtended ID: 4Connector: LCSONET compliance: OC48SRGigabit Ethernet compliance: unspecifiedFibre Channel link length: unspecifiedFibre Channel transmitter technology: unspecifiedFibre Channel transmission media: unspecifiedFibre Channel speed: unspecifiedEncoding: reservedBit Rate: 2500 MbpsSingle mode fiber supported length: 2 kmUpper bit rate limit: unspecifiedLower bit rate limit: unspecifiedDate code (yyyy/mm/dd): 2004/04/21Vendor PN: SCP6828-C5-BNEVendor revision number: DVendor serial number: ECL0817001LTransceiver status informationDiagnostics calibration is externalTemperature 39 (+/-3 Celsius)Voltage in transceiver 3232600 uV (+/- 10 mV)TX bias 8940 uA (+/- 100uA)TX power 316000 nW / -5 dBm (+/- 3dBm)RX power 300200 nW / -5 dBm (+/- 3dBm)No Active AlarmsNo Active WarningsAlarm Thresholds:high lowTemperature 96 C -44 CVoltage 4000000 uV 0 uVTX bias 70000 uA 0 uATX power 1000000 nW / 0 dBm 50100 nW / -13 dBmRX power 1008300 nW / 0 dBm unspecifiedWarning Thresholds:high lowTemperature 91 C - 9 CVoltage 3600000 uV 3000000 uVTX bias 60000 uA 0 uATX power 630900 nW / -2 dBm 79400 nW / -11 dBmRX power 1008300 nW / 0 dBm unspecifiedShow Transceiver: East SpanStatic informationID: SFP transceiverExtended ID: 4Connector: LCSONET compliance: OC48SRGigabit Ethernet compliance: unspecifiedFibre Channel link length: unspecifiedFibre Channel transmitter technology: unspecifiedFibre Channel transmission media: unspecifiedFibre Channel speed: unspecifiedEncoding: reservedBit Rate: 2500 MbpsSingle mode fiber supported length: 2 kmUpper bit rate limit: unspecifiedLower bit rate limit: unspecifiedDate code (yyyy/mm/dd): 2004/04/21Vendor PN: SCP6828-C5-BNEVendor revision number: DVendor serial number: ECL0817001MTransceiver status informationDiagnostics calibration is externalTemperature 38 (+/-3 Celsius)Voltage in transceiver 3230800 uV (+/- 10 mV)TX bias 8724 uA (+/- 100uA)TX power 285600 nW / -5 dBm (+/- 3dBm)RX power 309900 nW / -5 dBm (+/- 3dBm)No Active AlarmsNo Active WarningsAlarm Thresholds:high lowTemperature 96 C -44 CVoltage 4000000 uV 0 uVTX bias 70000 uA 0 uATX power 1000000 nW / 0 dBm 50100 nW / -13 dBmRX power 1008300 nW / 0 dBm unspecifiedWarning Thresholds:high lowTemperature 91 C - 9 CVoltage 3600000 uV 3000000 uVTX bias 60000 uA 0 uATX power 630900 nW / -2 dBm 79400 nW / -11 dBmRX power 1008300 nW / 0 dBm unspecifiedRelated Commands
Shows the status of RPR interfaces on the router.
Displays the RPR protection, topology, counters, and transit information for an RPR interface.
show interfaces rpr-ieee
To show information about an RPR interface, use the show interfaces rpr-ieee command in privileged EXEC mode.
show interfaces rpr-ieee slot-port [accounting | controller | dampening | description | fair-queue | mac-accounting | mpls-exp | precedence | random-detect | rate-limit | shape]
Syntax Descriptions
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
None of the options are specific to RPR interfaces.
Examples
The following example shows how to examine a specific RPR interface using the show interfaces rpr-ieee command:
router# show interfaces rpr-ieee 1/1RPR-IEEE1/1 is up, line protocol is upHardware is RPR-IEEE OC48, address is 0002.0002.0002 (bia 0008.e374.6580)Internet address is 1.1.1.2/24MTU 9100 bytes, BW 2488320 Kbit, DLY 100 usec, rely 255/255, load 1/255Encapsulation RPR-IEEE,West Span: loopback not setEast Span: loopback not setMAC passthrough not setLast input 00:00:00, output 00:00:00, output hang neverLast clearing of "show interface" counters 00:00:14Queueing strategy: PXF Class-based FairOutput queue Side West: 0/32768; Side East: 0/32768, 0 dropsInput queue 0/75, 0 dropsWest Span: 5 minutes output rate 0 bits/sec, 0 packets/sec5 minutes input rate 0 bits/sec, 0 packets/secEast Span: 5 minutes output rate 0 bits/sec, 0 packets/sec5 minutes input rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outRelated Commands
show rpr-ieee
To display RPR protection, topology, counters, and transit information, use the show rpr-ieee command in privileged EXEC mode.
show rpr-ieee [rpr-ieeeslot/port]
Syntax Description
rpr-ieeeslot/port
(Optional) Specifies the chassis slot number and port number of a specific RPR interface. If these are not specified, the command displays information for all RPR interfaces.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Examples
The following example shows sample output from this command:
Router# show rpr-ieee rpr-ieee1/1Protection Information for Interface RPR-IEEE1/1MAC AddressesWest Span (Ringlet 0 RX) neighbor 0001.0001.0001East Span (Ringlet 1 RX) neighbor 0003.0003.0003Station MAC address 0002.0002.0002TP frame sending timers:fast timer: 10 msecslow timer: 1x100 msec (100 msec)Protection holdoff timers:L1 Holdoff Keepalive DetectionWest Span 0x10 msec ( 0 msec) West Span 3 msecEast Span 0x10 msec ( 0 msec) East Span 3 msecConfigured protection mode: WRAPPINGProtection StatusRing is IDLEProtection WTR period is 10 sec. (timer is inactive)Self Detected Requests Remote RequestsWest Span IDLE West Span IDLEEast Span IDLE East Span IDLEDistant RequestsEast Span IDLE West Span IDLEWest Span Failures: noneEast Span Failures: noneSource Address Information for Interface RPR-IEEE1/10001.0001.0001, index 0, pkt. count 0, byte count 00003.0003.0003, index 1, pkt. count 0, byte count 0Ring Topology: CLOSED (STABLE)Configured protection mode: WRAPPINGJumbo preference: SET (ring supports JUMBOS)Number of nodes onringlet0: 3 ringlet1: 3Checksum: 0x001800DCIndex (Ri 0) MAC IP Address Edge W/E Request W/E1 0001.0001.0001 1.1.1.1 NO/NO IDLE/IDLE2 0003.0003.0003 1.1.1.3 NO/NO IDLE/IDLE3 0002.0002.0002 1.1.1.2 NO/NO IDLE/IDLEIndex (Ri 1) MAC IP Address Edge W/E Request W/E1 0003.0003.0003 1.1.1.3 NO/NO IDLE/IDLE2 0001.0001.0001 1.1.1.1 NO/NO IDLE/IDLE3 0002.0002.0002 1.1.1.2 NO/NO IDLE/IDLERate Limit Information for Interface RPR-IEEE1/1West Span:Reserved Bandwidth (Class A0): 0 MbpsRate Limiter High (Class A1): 10 MbpsRate Limiter Low (Class B-EIR, C): 2488 MbpsEast Span:Reserved Bandwidth (Class A0): 0 MbpsRate Limiter High (Class A1): 10 MbpsRate Limiter Low (Class B-EIR, C): 2488 MbpsData Traffic Counters for Interface RPR-IEEE1/1WEST Span:Transit Packets BytesTotal Low Priority 0 0Total Med EIR Priority 0 0Total Med CIR+EIR Priority 0 0Total High Priority 0 0Total Multicast 0 0Total Unicast 0 0Host Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Host Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Traffic Rate (5 Minutes) packets/sec bits/secTransit Low Priority 0 0Transit Med EIR Priority 0 0Transit Med CIR+EIR Priority 0 0Transit High Priority 0 0Transit Multicast 0 0Transit Unicast 0 0Host Receive 0 0Total Receive 0 0Host Transmit 0 0Total Transmit 0 0Received Errors:0 input errors, 0 CRC, 0 ignored,0 framer runts, 0 framer giants, 0 framer aborts,0 mac runts, 0 mac giants, 0 mac ttl strips,0 non-we dropEAST Span:Transit Packets BytesTotal Low Priority 0 0Total Med EIR Priority 0 0Total Med CIR+EIR Priority 0 0Total High Priority 0 0Total Multicast 0 0Total Unicast 0 0Host Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Host Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Traffic Rate (5 Minutes) packets/sec bits/secTransit Low Priority 0 0Transit Med EIR Priority 0 0Transit Med CIR+EIR Priority 0 0Transit High Priority 0 0Transit Multicast 0 0Transit Unicast 0 0Host Receive 0 0Total Receive 0 0Host Transmit 0 0Total Transmit 0 0Received Errors:0 input errors, 0 CRC, 0 ignored,0 framer runts, 0 framer giants, 0 framer aborts,0 mac runts, 0 mac giants, 0 mac ttl strips,0 non-we dropTransit Buffer Delay Counters for Interface RPR-IEEE1/1WEST Span:Transit Delay (5 Minutes) NanosecondsLow TB Min Delay: 0Low TB Avg Delay: 0Low TB Max Delay: 0High TB Min Delay: 480High TB Avg Delay: 537High TB Max Delay: 640EAST Span:Transit Delay (5 Minutes) NanosecondsLow TB Min Delay: 0Low TB Avg Delay: 0Low TB Max Delay: 0High TB Min Delay: 440High TB Avg Delay: 502High TB Max Delay: 640Table 2 describes the significant fields shown in the display.
Related Commands
show rpr-ieee counters
To display counters for each of the various service classes on each RPR span, use the show rpr-ieee counters command in privileged EXEC mode.
show rpr-ieee counters [rpr-ieeeslot/port]
Syntax Description
rpr-ieeeslot/port
(Optional) Specifies the chassis slot number and port number of a specific RPR interface. If these are not specified, the command displays information for all RPR interfaces.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Traffic counters are collected from various sources in the interface, and are displayed using the counters command. This command shows received, transited, and transmitted quantities of each of the various service classes, and on each span. Receive errors are also indicated for each span.
Examples
The following example shows sample output from this command:
Router# show rpr-ieee countersData Traffic Counters for Interface RPR-IEEE1/1WEST Span:Transit Packets BytesTotal Low Priority 0 0Total Med EIR Priority 0 0Total Med CIR+EIR Priority 0 0Total High Priority 0 0Total Multicast 0 0Total Unicast 0 0Host Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Host Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Traffic Rate (5 Minutes) packets/sec bits/secTransit Low Priority 0 0Transit Med EIR Priority 0 0Transit Med CIR+EIR Priority 0 0Transit High Priority 0 0Transit Multicast 0 0Transit Unicast 0 0Host Receive 0 0Total Receive 0 0Host Transmit 0 0Total Transmit 0 0Received Errors:0 input errors, 0 CRC, 0 ignored,0 framer runts, 0 framer giants, 0 framer aborts,0 mac runts, 0 mac giants, 0 mac ttl strips,0 non-we dropEAST Span:Transit Packets BytesTotal Low Priority 0 0Total Med EIR Priority 0 0Total Med CIR+EIR Priority 0 0Total High Priority 0 0Total Multicast 0 0Total Unicast 0 0Host Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Receive Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Host Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Total Transmit Packets BytesUnicast Low Priority 0 0Unicast Med EIR Priority 0 0Unicast Med CIR Priority 0 0Unicast High Priority 0 0Multicast Low Priority 0 0Multicast Med EIR Priority 0 0Multicast Med CIR Priority 0 0Multicast High Priority 0 0Traffic Rate (5 Minutes) packets/sec bits/secTransit Low Priority 0 0Transit Med EIR Priority 0 0Transit Med CIR+EIR Priority 0 0Transit High Priority 0 0Transit Multicast 0 0Transit Unicast 0 0Host Receive 0 0Total Receive 0 0Host Transmit 0 0Total Transmit 0 0Received Errors:0 input errors, 0 CRC, 0 ignored,0 framer runts, 0 framer giants, 0 framer aborts,0 mac runts, 0 mac giants, 0 mac ttl strips,0 non-we dropRelated Commands
show rpr-ieee failures
To display the input used to determine the failure state of each span of an RPR interface, use the show rpr-ieee failures command in privileged EXEC mode.
show rpr-ieee failures [rpr-ieeeslot/port]
Syntax Description
rpr-ieeeslot/port
(Optional) Specifies the chassis slot number and port number of a specific RPR interface. If these are not specified, the command displays information for all RPR interfaces.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command applies to RPR interfaces only.
This command is used to debug the cause of a protection event.
Examples
The following example shows sample output from this command:
Router# show rpr-ieee failuresSelf Detected Failures Information for Interface RPR-IEEE1/1Span WEST:Reported Debounced Current Stable Debouncestate state state for(sec) delay(sec)HW missing IDLE IDLE IDLE 22641 0Layer 1 IDLE IDLE IDLE 22629 0MAC Keepalive IDLE IDLE IDLE 22640 10Link quality IDLE IDLE IDLE 22641 0Mate interface IDLE IDLE IDLE 22641 10Span mismatch IDLE IDLE IDLE 22641 0Result Self Detect = IDLESpan EAST:Reported Debounced Current Stable Debouncestate state state for(sec) delay(sec)HW missing IDLE IDLE IDLE 22641 0Layer 1 IDLE IDLE IDLE 22630 0MAC Keepalive IDLE IDLE IDLE 22640 10Link quality IDLE IDLE IDLE 22641 0Mate interface IDLE IDLE IDLE 22642 10Span mismatch IDLE IDLE IDLE 22642 0Result Self Detect = IDLERelated Commands
show rpr-ieee fairness
To display the fairness settings and some results of the fairness algorithm, use the show rpr-ieee fairness command in privileged EXEC mode.
show rpr-ieee fairness [history [intervals]] [rpr-ieeeslot/port] [details]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(29)S
This command was introduced.
12.0(30)S
The history keyword was added.
Usage Guidelines
This command applies to RPR interfaces only.
The fairness system uses a large quantity of input to determine its behavior. This input and some results of the fairness algorithm, can be displayed using this command. Information for both directions is always shown.
The history keyword reports the fairness state in the last 96 fifteen-minute intervals (a total of 24 hours). This report provides a good indication of ring load and bandwidth utilization on a station-by-station basis. Note that due to the way the algorithm works, you never see 100-percent congestion. Any congestion over 80 percent can be considered as constant congestion.
Examples
The following example shows sample output from this command:
Router# show rpr-ieee fairnessIEEE 802.17 Fairness on RPR-IEEE1/1:Bandwidth: 2488320 kilobits per secondStation using aggressive rate adjustment.Westbound Tx (Ringlet 1)Weighted Fairness:Local Weight: 0 (1)Single-Choke Fairness Status:Local Congestion:Congested? NoHead? NoDownstream Congestion:Congested? NoTail? NoReceived Source Address: 0001.0001.0001Reserved Rate:0 KbpsUnreserved Rate:2488320 KbpsEastbound Tx (Ringlet 0)Weighted Fairness:Local Weight: 0 (1)Single-Choke Fairness Status:Local Congestion:Congested? NoHead? NoDownstream Congestion:Congested? NoTail? NoReceived Source Address: 0003.0003.0003Reserved Rate:0 KbpsUnreserved Rate:2488320 KbpsThe following example shows sample output from this command when the details keyword is used:
Router# show rpr-ieee fairness detailsIEEE 802.17 Fairness on RPR-IEEE1/1:Bandwidth: 2488320 kilobits per secondStation using aggressive rate adjustment.Westbound Tx (Ringlet 1)Weighted Fairness:Local Weight: 0 (1)Single-Choke Fairness Status:Local Congestion:Congested? YesHead? NoLocal Fair Rate:Approximate Bandwidth: 1190000 Kbps29750 normalized bytes per aging interval59500 bytes per ageCoef aging intervalDownstream Congestion:Congested? NoTail? NoReceived Source Address: 0001.0001.0001Received Fair Rate:Approximate Bandwidth: FULL RATE65535 normalized bytes per aging intervalReserved Rate:0 Kbps0 bytes per aging intervalUnreserved Rate:2488320 Kbps31104 bytes per aging intervalAllowed Rate:Approximate Bandwidth: 2488320 Kbps31104 bytes per aging intervalAllowed Rate Congested:Approximate Bandwidth: 2487040 Kbps31088 bytes per aging intervalTTL to Congestion: 255Total Hops Tx: 2Advertised Fair Rate:Approximate Bandwidth: 1179600 Kbps29490 normalized bytes per aging interval14745 bytes per aging intervalEastbound Tx (Ringlet 0)Weighted Fairness:Local Weight: 0 (1)Single-Choke Fairness Status:Local Congestion:Congested? YesHead? YesLocal Fair Rate:Approximate Bandwidth: 1188640 Kbps29716 normalized bytes per aging interval59432 bytes per ageCoef aging intervalDownstream Congestion:Congested? NoTail? NoReceived Source Address: 0003.0003.0003Received Fair Rate:Approximate Bandwidth: FULL RATE65535 normalized bytes per aging intervalReserved Rate:0 Kbps0 bytes per aging intervalUnreserved Rate:2488320 Kbps31104 bytes per aging intervalAllowed Rate:Approximate Bandwidth: 2488320 Kbps31104 bytes per aging intervalAllowed Rate Congested:Approximate Bandwidth: 2487040 Kbps31088 bytes per aging intervalTTL to Congestion: 255Total Hops Tx: 2Advertised Fair Rate:Approximate Bandwidth: FULL RATE65535 normalized bytes per aging interval32767 bytes per aging intervalThe following example shows sample output from this command with the history keyword and 3 intervals displayed:
Router# show rpr-ieee fairness history 3IEEE 802.17 Fairness History on RPR-IEEE1/1 for last 24 hours:Congestion information gathered every 900 second(s)Westbound Tx (Ringlet 1)Local Congestion:No. Time : Aging Intervals Seconds PercentCongested / Total Congested / Total CongestedInstantaneous : 46 / 80 4 (ms) / 8 (ms) 57%15 04:48:08 : 826447 / 9000000 82 / 900 9%14 04:33:08 : 7499346 / 9000000 749 / 900 83%13 04:18:08 : 2845843 / 9000000 284 / 900 31%Downstream Congestion:No. Time : Aging Intervals Seconds PercentCongested / Total Congested / Total CongestedInstantaneous : 38 / 80 3 (ms) / 8 (ms) 47%15 16:58:07 : 812434 / 9000000 81 / 900 9%14 16:43:07 : 7510728 / 9000000 751 / 900 83%13 16:28:07 : 2865744 / 9000000 286 / 900 31%Eastbound Tx (Ringlet 0)Local Congestion:No. Time : Aging Intervals Seconds PercentCongested / Total Congested / Total CongestedInstantaneous : 0 / 80 0 (ms) / 8 (ms) 0%15 04:48:08 : 0 / 9000000 0 / 900 0%14 04:33:08 : 0 / 9000000 0 / 900 0%13 04:18:08 : 0 / 9000000 0 / 900 0%Downstream Congestion:No. Time : Aging Intervals Seconds PercentCongested / Total Congested / Total CongestedInstantaneous : 0 / 80 0 (ms) / 8 (ms) 0%15 04:48:08 : 0 / 9000000 0 / 900 0%14 04:33:08 : 0 / 9000000 0 / 900 0%13 04:18:08 : 0 / 9000000 0 / 900 0%Table 3 describes the significant fields shown in the display.
Related Commands
show rpr-ieee protection
To display the RPR protection configurations, use the show rpr-ieee protection command in privileged EXEC mode.
show rpr-ieee protection [rpr-ieeeslot/port]
Syntax Description
rpr-ieeeslot/port
(Optional) Specifies the chassis slot number and port number of a specific RPR interface. If these are not specified, the command displays information for all RPR interfaces.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Examples
The following example shows sample output from this command:
Router# show rpr-ieee protectionProtection Information for Interface RPR-IEEE1/1MAC AddressesWest Span (Ringlet 0 RX) neighbor 0001.0001.0001East Span (Ringlet 1 RX) neighbor 0003.0003.0003Station MAC address 0002.0002.0002TP frame sending timers:fast timer: 10 msecslow timer: 1x100 msec (100 msec)Protection holdoff timers:L1 Holdoff Keepalive DetectionWest Span 0x10 msec ( 0 msec) West Span 3 msecEast Span 0x10 msec ( 0 msec) East Span 3 msecConfigured protection mode: STEERINGProtection StatusRing is IDLEProtection WTR period is 10 sec. (timer is inactive)Self Detected Requests Remote RequestsWest Span IDLE West Span IDLEEast Span IDLE East Span IDLEDistant RequestsEast Span IDLE West Span IDLEWest Span Failures: noneEast Span Failures: noneRelated Commands
show rpr-ieee rate-limit
To display the configured values for the rate manipulators on various classes of traffic, use the show rpr-ieee rate-limit command in privileged EXEC mode.
show rpr-ieee rate-limit [rpr-ieeeslot/port] [details]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Use this command to view the configured values for the rate manipulators on the various classes of traffic. There are rate limiters for classes A0 (or reserved), A1, B-CIR, and B-EIR and C. Some interfaces do not support class B on transmit, so only the other three are displayed.
Examples
The following example shows sample output from this command:
Router# show rpr-ieee rate-limitRate Limit Information for Interface RPR-IEEE1/1West Span:Reserved Bandwidth (Class A0): 0 MbpsRate Limiter High (Class A1): 10 MbpsRate Limiter Medium (Class B-CIR): 10 MbpsRate Limiter Low (Class B-EIR, C): fullEast Span:Reserved Bandwidth (Class A0): 0 MbpsRate Limiter High (Class A1): 10 MbpsRate Limiter Medium (Class B-CIR): 10 MbpsRate Limiter Low (Class B-EIR, C): fullThe following example shows sample output from this command when the details keyword is used:
router# show rpr-ieee rate-limit detailsRate Limit Information for Interface RPR-IEEE1/1West Span:Reserved Bandwidth (Class A0): 0 MbpsRate Limiter High (Class A1): 10 MbpsRate Limiter Medium (Class B-CIR): 10 MbpsRate Limiter Low (Class B-EIR, C): 2488 MbpsEast Span:Reserved Bandwidth (Class A0): 0 MbpsRate Limiter High (Class A1): 10 MbpsRate Limiter Medium (Class B-CIR): 10 MbpsRate Limiter Low (Class B-EIR, C): 2488 MbpsService Type: RelaxedIdle Shaper is EnabledTransmit at 500 packets per million when PTQ vacancy above 18432 bytesTransmit at 250 packets per million when PTQ vacancy below 18432 bytesRelated Commands
Specifies a rate limit on a traffic queue. The allowable rate depends on the speed of the interface.
Displays RPR protection, topology, counters, and transit information.
show rpr-ieee source-counters
To display the number of packets from a specified source on the ringlet, use the show rpr-ieee source-counters command in privileged EXEC mode.
show rpr-ieee source-counters [rpr-ieeeslot/port]
Syntax Description
rpr-ieeeslot/port
(Optional) Specifies the chassis slot number and port number of a specific RPR interface. If these are not specified, the command displays information for all RPR interfaces.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command applies to RPR interfaces only.
To view the count of packets from a specific source address, you must first configure the source address using the rpr-ieee count command in interface configuration mode.
Examples
The following example shows sample output from this command:
Router# show rpr-ieee source-countersSource Address Information for Interface RPR-IEEE1/10001.0001.0001, index 0, pkt. count 0, byte count 00003.0003.0003, index 1, pkt. count 0, byte count 0Related Commands
Counts the number of packets from a specific source address on an RPR ringlet.
Displays RPR protection, topology, counters, and transit information.
show rpr-ieee topology
To identify the stations on the ringlet, use the show rpr-ieee topology command in privileged EXEC mode.
show rpr-ieee topology [rpr-ieeeslot/port] [details]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command applies to RPR interfaces only.
This command provides information on the local station, its neighbors, and the general state of the ring. Packets sent to communicate topology information are constructed using data from various sources, such as configured preferences, cumulative reserved bandwidth, protection states, and station name. This information is displayed for the local station and every active station from which a topology message has been received.
Examples
The following example shows sample output from this command:
Router# show rpr-ieee topologyRing Topology: CLOSED (STABLE)Configured protection mode: STEERINGJumbo preference: NOT SET (ring doesn't support JUMBOS)Number of nodes onringlet0: 3 ringlet1: 3Checksum: 0x00180090 (VALID)West Neighbor Checksum: 0x00180090 (VALID)East Neighbor Checksum: 0x00180090 (VALID)Index (Ri 0) MAC IP Address Edge W/E Request W/E1 0001.0001.0001 1.1.1.1 NO/NO IDLE/IDLE2 0003.0003.0003 1.1.1.3 NO/NO IDLE/IDLE3 0002.0002.0002 1.1.1.2 NO/NO IDLE/IDLEIndex (Ri 1) MAC IP Address Edge W/E Request W/E1 0003.0003.0003 1.1.1.3 NO/NO IDLE/IDLE2 0001.0001.0001 1.1.1.1 NO/NO IDLE/IDLE3 0002.0002.0002 1.1.1.2 NO/NO IDLE/IDLEFollowing is sample output from this command when the details keyword is used:
Router# show rpr-ieee topology details802.17 Topology DisplayRX ringlet0->West span RX ringlet1->East spanNumber of nodes onringlet0: 3 ringlet1: 3=======================================================================Local Station Topology Info=======================================================================Topology entry:Station MAC address: 0002.0002.0002West Span (Outer ringlet RX) neighbor 0001.0001.0001East Span (Inner ringlet RX) neighbor 0003.0003.0003Ring Topology: CLOSED (STABLE)Containment Active: NOA0 class reserved rate:ringlet0: 0 (mbps) ringlet1: 0 (mbps)Ringlet reserved rate:ringlet0: 0 (mbps) ringlet1: 0 (mbps)Ringlet unreserved rate:ringlet0: 2488 (mbps) ringlet1: 2488 (mbps)Advertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOConfigured protection mode: STEERINGJumbo preference: NOT SET (ring doesn't support JUMBOS)Is revertive: YESMeasured LRTT: 0Sequence Number: 54ATD INFO:ATD timer: 1 secStation Name: UUT-D1A0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 1 ringlet1: 1Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology Map for Outer ringlet==============================================================================================================================================Topology entry at Index 1 on ringlet 0:Station MAC address: 0001.0001.0001Valid on ringlet0: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: STEERINGJumbo preference: NOT SET (ring doesn't supports JUMBOS)Measured LRTT: 0Sequence Number: 12ATD INFO:Station Name: EAST-DA0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 1 ringlet1: 1Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology entry at Index 2 on ringlet 0:Station MAC address: 0003.0003.0003Valid on ringlet0: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: STEERINGJumbo preference: NOT SET (ring doesn't supports JUMBOS)Measured LRTT: 0Sequence Number: 43ATD INFO:Station Name: WEST-DA0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 1 ringlet1: 1Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology entry at Index 3 on ringlet 0:Station MAC address: 0002.0002.0002Valid on ringlet0: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: STEERINGJumbo preference: NOT SET (ring doesn't supports JUMBOS)Measured LRTT: 0Sequence Number: 54ATD INFO:Station Name: UUT-D1A0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 1 ringlet1: 1Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology Map for Inner ringlet==============================================================================================================================================Topology entry at Index 1 on ringlet 1:Station MAC address: 0003.0003.0003Valid on ringlet1: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: STEERINGJumbo preference: NOT SET (ring doesn't supports JUMBOS)Measured LRTT: 0Sequence Number: 43ATD INFO:Station Name: WEST-DA0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 1 ringlet1: 1Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology entry at Index 2 on ringlet 1:Station MAC address: 0001.0001.0001Valid on ringlet1: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: STEERINGJumbo preference: NOT SET (ring doesn't supports JUMBOS)Measured LRTT: 0Sequence Number: 12ATD INFO:Station Name: EAST-DA0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 1 ringlet1: 1Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)=======================================================================Topology entry at Index 3 on ringlet 1:Station MAC address: 0002.0002.0002Valid on ringlet1: YESEntry reachable: YESAdvertised Protection requests:ringlet0: IDLE ringlet1: IDLEActive Edges:ringlet0: NO ringlet1: NOPreferred protection mode: STEERINGJumbo preference: NOT SET (ring doesn't supports JUMBOS)Measured LRTT: 0Sequence Number: 54ATD INFO:Station Name: UUT-D1A0 reserved Bandwidth:ringlet0: 0 mbps ringlet1: 0 mbpsWeight:ringlet0: 1 ringlet1: 1Secondary Mac Addresses:MAC 1: 0000.0000.0000 (UNUSED)MAC 2: 0000.0000.0000 (UNUSED)Related Commands
show rpr-ieee transit
To display the transit buffer delays for each span, use the show rpr-ieee transit command in privileged EXEC mode.
show rpr-ieee transit [rpr-ieeeslot/port]
Syntax Description
rpr-ieeeslot/port
(Optional) Specifies the chassis slot number and port number of a specific RPR interface. If these are not specified, the command displays information for all RPR interfaces.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command applies to RPR interfaces only.
Examples
The following example shows sample output from this command:
Router# show rpr-ieee transitTransit Buffer Delay Counters for Interface RPR-IEEE1/1WEST Span:Transit Delay (5 Minutes) NanosecondsLow TB Min Delay: 720Low TB Avg Delay: 761Low TB Max Delay: 800High TB Min Delay: 440High TB Avg Delay: 504High TB Max Delay: 580EAST Span:Transit Delay (5 Minutes) NanosecondsLow TB Min Delay: 0Low TB Avg Delay: 0Low TB Max Delay: 0High TB Min Delay: 480High TB Avg Delay: 528High TB Max Delay: 580Related Commands
Glossary
The following terms and acronyms are used regarding RPR:
A0—Service class for the highest-priority traffic.
A1—Service class for high-priority traffic, that which is in excess of the A0 bandwidth reservation.
Add/Drop Internet Multiplexer (ADM)—Device used to add or drop virtual channels from SONET/SDH lines into physical tributaries.
ATD—Attribute discovery timer
Aggressive—Default ramp rate for the fairness algorithm. Aggressive mode ramps up as quickly as possible when bandwidth is available and ramps down as quickly as possible when congestion occurs. This fast ramping can result in unstable traffic behavior in very bursty traffic scenarios.
B-CIR—Service class B for committed information rate.
B-EIR—Service class B for excess information rate. Service class associated with low-priority traffic.
BER—Bit Error Rate from SONET Standard (GR-253). The number of coding violations detected in a unit of time, typically 1 second.
C—Service class for lowest-priority traffic.
CIR—Committed information rate.
Closed ring—Idle ring.
Conservative—Optional ramp rate for the fairness algorithm. Conservative mode ramps up in stages (over a few hundred ms) when bandwidth is available and ramps down in stages (over a few hundred mn) when congestion occurs. This slow ramping can result in slightly lower bandwidth utilization, but is more applicable in very bursty traffic scenarios.
DPT—Dynamic Packet Transport. Creates dual, counter-rotating fiber rings. Both fibers concurrently transport both data and control traffic, and use Intelligent Protection Switching (IPS) that provides proactive performance monitoring, event detection, and rapid self-healing, and restores IP service after fiber facility or node failures. Also called SRP.
East—Span on which RPR transmits on ringlet 0.
Edge—Protection edge in an open ring
EIR—Excess information rate.
Exceed action—Action to take on packets above the rate allowed by the rate limit.
Excess burst size—Bytes allowed in a burst before all packets exceed the rate limit.
Fairness—Automatic traffic control algorithm that allocates bandwidth for low-priority traffic fairly among stations when traffic congestion occurs.
Forced switch—Takes precedence over all other failure events on a ring, for the span on which it is configured. The operation protects the span indicated by the command. In the case of steering, forwarding uses only the topology list from the opposite span. In the case of wrapping, the other span becomes wrapped. A forced switch is saved in the configuration.
Jumbo—Frames in excess of the standard 1500 bytes, up to a maximum size of 9100 bytes.
MAN—Metropolitan area network.
Manual switch—Coerces a reaction from the protection system. The difference between a manual and a forced switch is that this configuration can be usurped by higher-level requests detected on the configured or opposite span. A manual switch is not saved in the configuration.
Normal burst size—Bytes allowed in a burst before some packets will exceed the rate limit. Larger bursts are more likely to exceed the rate limit.
Open ring—Protected ring.
Rate limit—Traffic descriptor defined by the average rate, normal burst size, and excess burst size.
Rate policy—Rate limit, conform actions, and exceed actions that apply to traffic matching certain criteria.
Ringlet—One of two unidirectional, counter-rotating rings that connect the stations in an RPR topology. Ringlet0 transverses from east to west; ringlet 1 transverses from west to east.
RPR—Resilient Packet Ring, as defined in IEEE 802.17.
Signal degradation—Enters automatic protection switch wraps on a span when it is invoked by a media signal degrade, such as an excessive bit error rate.
Signal failure—Enters automatic protection switch wraps on a span when it is invoked by a media signal failure or SRP keepalive failure. The signal failure protection switch wrap remains in effect until the event is repaired.
SRP—Spatial Reuse Protocol.
Steering—Ring protection mode where stations that detect a failed span notify all other stations in the ring. Each individual station is then responsible for "steering" traffic away from the failed span to reach the destination.
Synchronous Digital Hierarchy (SDH)—European standard that defines a set of rate and format standards that are transmitted using optical signals over fiber. SDH is similar to SONET, with a basic SDH rate of 155.52 Mbps, designated at STM-1.
Synchronous Optical Network (SONET)—High-speed synchronous network specification developed by Bellcore and designed to run on optical fiber. STS-1 is the basic building block of SONET. Approved as an international standard in 1988.
Wait-to-restore (WTR)—Invokes a waiting period after the working channel meets the restoration criteria after a signal failure or signal degradation disappears. The wait-to-restore period prevents protection switch oscillations.
West—Span on which RPR transmits on ringlet 1.
Wrapping—Ring protection mode where the two stations on either end of a failed span react by "wrapping" traffic back onto the opposite ringlet to reach the destination.
Note
Copyright © 2004 Cisco Systems, Inc. All rights reserved.
