Implementing Frrp; Frrp Configuration; Creating The Frrp Group - Dell S6100 Configuration Manual

Concept Explanation
•
•

Implementing FRRP

• FRRP is media and speed independent.
• FRRP is a Dell proprietary protocol that does not interoperate with any other vendor.
• You must disable the spanning tree protocol (STP) on both the Primary and Secondary interfaces before you can enable FRRP.
• All ring ports must be Layer 2 ports. This is required for both Master and Transit nodes.
• A VLAN configured as a control VLAN for a ring cannot be configured as a control or member VLAN for any other ring.
• The control VLAN is not used to carry any data traffic; it carries only RHFs.
• The control VLAN cannot have members that are not ring ports.
• If multiple rings share one or more member VLANs, they cannot share any links between them.
• Member VLANs across multiple rings are not supported in Master nodes.
• Each ring has only one Master node; all others are transit nodes.

FRRP Configuration

These are the tasks to configure FRRP.
•

Creating the FRRP Group

• Configuring the Control VLAN
• Configure Primary and Secondary ports
• Configuring and Adding the Member VLANs
• Configure Primary and Secondary ports
Other FRRP related commands are:
• Clearing the FRRP Counters
• Viewing the FRRP Configuration
• Viewing the FRRP Information
Creating the FRRP Group
Create the FRRP group on each switch in the ring.
To create the FRRP group, use the command.
• Create the FRRP group with this Ring ID.
CONFIGURATION mode
protocol frrp ring-id
Ring ID: the range is from 1 to 255.
340 Force10 Resilient Ring Protocol (FRRP)
Hello RHF (HRHF) — These frames are processed only on the Master node's Secondary port. The Transit
nodes pass the HRHF through without processing it. An HRHF is sent at every Hello interval.
Topology Change RHF (TCRHF) — These frames contains ring status, keepalive, and the control and
member VLAN hash. The TCRHF is processed at each node of the ring. TCRHFs are sent out the Master
Node's Primary and Secondary interface when the ring is declared in a Failed state with the same sequence
number, on any topology change to ensure that all Transit nodes receive it. There is no periodic transmission of
TCRHFs. The TCRHFs are sent on triggered events of ring failure or ring restoration only.