Cisco 15327 - Manual (Page 283)

17-31
Ethernet Card Software Feature and Configuration Guide, R7.2
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring
LFP Configuration Requirements
To enable and configure the LFP slave link, perform the following procedure on an ML-Series card in
the Cisco proprietary RPR other than the ML-Series card configured for the master link. Begin in global
configuration mode:
LFP Configuration Requirements
LFP has these configuration requirement:
• A link-fault master and slave should not be configured on the same card.
• The ML-Series card must be running the Enhanced microcode image.
• All ML-Series cards in the Cisco proprietary RPR must be running Software Release 5.0 or later.
• ML-Series card configured for DRPRI should not be configured for LFP, and LFP on DRPRI is
unsupported.
• Only ML-Series card Gigabit Ethernet interfaces are eligible to become link-fault masters.
• Only one link-fault master is allowed per Cisco proprietary RPR.
• Gigabit Ethernet and Fast Ethernet interfaces are both eligible to become link-fault slaves.
• There is no configuration limit on link-fault slaves on a Cisco proprietary RPR.
Monitoring and Verifying LFP
A slave interface in link-down state raises a carrier loss (CARLOSS) alarm in CTC. CTC does not
distinguish between a local loss on the slave link and loss due to LFP. For more information on
CARLOSS, refer to refer to the “Alarm Troubleshooting” chapter of the Cisco ONS 15454
Troubleshooting Guide or the “Alarm Troubleshooting” chapter of the Cisco ONS 15454 SDH
Troubleshooting Guide.
The Cisco IOS status of link-down interface is shown as protocol down/link down. Neither the
show controller command nor the show interface command reveals the difference between a local loss
on the link and an LFP loss.
After LFP is configured, you can monitor the LFP status of each master or slave link using the show
link-fault command. Use this command to determine whether LFP caused the link down on a slave
interface.
Example 17-6 illustrates the output from this command on a slave interface.
Command Purpose
Step 1 Router# interface {gigabit ethernet |
fastethernet } number
Activates interface configuration mode to
configure the Gigabit Ethernet or Fast Ethernet
interface.
Step 2 Router(config-if)# link-fault rpr-slave Enables link-fault slave status on the interface.
The no form of this command disables link-fault
slave status.
Step 3 Router(config-if)# no shutdown Enables the interface by preventing it from
shutting down.
Step 4 Router(config)# end Returns to privileged EXEC mode.
Step 5 Router# copy running-config startup-config (Optional) Saves configuration changes to the
TCC2/TCC2P flash database.