Cisco ONS 15454 SDH - Understanding the RPR-IEEE Interface

26-33
Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide, R8.0
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring
Creating the RPR-IEEE Interface and Bridge Group
6. Enable the rpr-ieee interface.
7. Set the encapsulation on the Ethernet interface.
8. Create rpr-ieee subinterfaces and assign them to the bridge group.
Caution A duplicate MAC address on the RPR-IEEE can cause network problems.
Understanding the RPR-IEEE Interface
When the card mode is changed to IEEE 802.17, the physical rpr-ieee interface is automatically created.
It provides all the normal attributes of a Cisco IOS virtual interface, such as support for default routes.
An rpr-ieee interface is considered a trunk port, and like all trunk ports, subinterfaces must be configured
for the rpr-ieee interface to join a bridge group.
The POS interfaces are not visible or configurable in 802.17 card mode.
Understanding the RPR-IEEE Bridge Group
The default behavior of the ML-Series card is that no traffic is bridged over the RPR-IEEE even with the
interfaces enabled. This is in contrast to many Layer 2 switches, including the Cisco Catalyst 6500 series
and the Cisco Catalyst 7600 series, which forward VLAN 1 by default. The ML-Series card will not
forward any traffic by default, including untagged or VLAN 1 tagged packets.
For any RPR-IEEE traffic to be bridged on an ML-Series card, a bridge group needs to be created for
that traffic. Bridge groups maintain the bridging and forwarding between the interfaces on the ML-Series
card and are locally significant. Interfaces not participating in a bridge group cannot forward bridged
traffic. The bridge group enables data transport across the RPR-IEEE infrastructure.
Figure 26-7 illustrates a bridge group spanning the ML-Series card interfaces, including the rpr-ieee
virtual interface.
Figure 26-7 RPR-IEEE Bridge Group
Caution All Layer 2 network redundant links (loops) in the connecting network, except the RPR-IEEE topology,
must be removed for correct RPR-IEEE operation. Or if loops exist, you must configure STP/RSTP.
Caution RPR-IEEE requires GFP-F framing. High-level data link control (HDLC) framing is not supported.
ML-Series Card
151979
Ethernet
Port 0
Ethernet
Port 1
Bridge Group
East Span
West Span
RPR
Interface