Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 559)

Multi-Service IronWare Switching Configuration Guide 529
53-1003036-02
FBD flush optimization
15
FBD flush optimization
The FDB stores the node ID and BPR sent in the R-APS messages. When an ERN receives a new
R-APS message, it compares the received node ID and BPR to the node ID and BPR in its memory.
If the pair vary from the previously stored pair, the ERN deletes the previous pair and stores the
new pair. The device then triggers a FDB flush unless the DNF (No Not Flush) is set in the message.
FDB optimization is achieved with the following features:
• Non-revertive mode alleviates the need to flush the FDB after a link failure with link protection
(SF) condition
• Dual-end blocking decreases attempted messages and traffic to the RPL blocking port
• Interconnected ring support to decrease the latency for messaging
• Do Not Flush (DNF) messages
Configuring ERP
To configure and initialize ERP using only APS you must set up one RPL owner and one or more
Non-RPL nodes. The minimum configuration tasks are listed in this section.
Before configuring ERP, however, you must have already configured a VLAN and ports.
NOTE
ERP only supports topology-groups if the ERP interfaces are in the same VLAN
You must perform the following minimum configuration tasks for the RPL owner:
• Configure an ERP instance
• Set the left and right interfaces
• Set the role as owner
• Set the RPL
• Enable the configuration
You must perform the following minimum configuration tasks for each non-RPL node:
• Configure an ERP instance
• Set the left and right interfaces
• Enable the configuration
Sample configuration
The following example is of an ERP configuration consisting of four devices: an RPL owner, an RPL
node, and two non-RPL nodes.
NOTE
Before configuring any ERP settings, configure the VLAN and ports.