beautypg.com

Selection of the master node for a ring – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual

Page 523

background image

Multi-Service IronWare Switching Configuration Guide

493

53-1003036-02

MRP Phase 2

14

FIGURE 118

Interface IDs and types

In

Figure 118

, nodes S1 and S2 have interfaces that belong to rings 1 and 2. Interface e 1/1 on S1

and e 2/2 on S2 are regular interfaces for ring 1, but they are tunnel interfaces for ring 2.

Selection of the master node for a ring

Configuring MRP rings with shared interfaces limits the nodes that can be designated as the
master node for any particular ring.

Any node on the ring that does not have any shared interfaces can be designated as the ring’s
master.

You can only designate a node that has shared interfaces as master for a ring where all
interfaces for the ring are marked as regular interfaces.

On a node with shared interfaces, where you configure the role as master, the secondary ring
interface should not be a shared interface. If you designate a shared interface as secondary it
will be blocking under normal operation and allow RHP’s but no data for lower priority rings.
This can create unexpected traffic flows on the rings.

In

Figure 118

any of the nodes on ring 1, even S1 or S2, can be a master node as all of the ring

interfaces, even the shared interfaces between S1 and S2, are marked as regular interfaces for
ring 1.

However for ring 2, neither S1 nor S2 can be a master node since the shared interfaces between
S1 and S2 are marked as tunnel interfaces for ring 2.