Feature History
Feature |
Release |
Feature Information |
Platform |
---|---|---|---|
REP Segment ID Autodiscovery - Interoperability with Cisco IOS XE |
15.2(8)E4 |
This feature allows the REP Segment ID Autodiscovery feature on Cisco Classic IOS switches to interoperate with Cisco IOS XE based platforms. |
IE 4000, IE 4010, and IE 5000 |
REP Zero Touch Provisioning |
15.2(8)E4 |
The REP ZTP feature allows PnP to function on insertion of a new IE switch into an existing REP ring. |
IE 4000, IE 4010, and IE 5000 |
REP Negotiated and REP Segment ID Validation |
15.2(8)E2 |
When the switch interfaces are configured with REP Negotiated (see REP Negotiated), REP status is negotiated with the peers. If the peer supports REP, it is migrated to REP. If the peer does not support REP, it is migrated to STP. The peer is migrated to REP or STP using an Embedded Event Manager (EEM) macro. The REP node learns the Segment ID and maintains it on interfaces until the link goes down. The ring must be initially configured with a static REP Segment ID from the edge, but the rest of the REP ring can implement REP Segment ID autodiscovery to facilitate deployment and automation. |
IE 4000, IE 4010, and IE 5000 |
Resilient Ethernet Protocol (REP) |
15.2(5)E |
REP controls a group of ports connected in a segment, ensures that the segment does not create any bridging loops, and responds to link failures within the segment.Faster convergence time (<50ms) for unicast and multicast traffic on Fiber ports |
IE 4000, IE 4010, and IE 5000 |