Fabric Manager Users Guide, Version 6.1, Revision A - QLogic
Fabric Manager Users Guide, Version 6.1, Revision A - QLogic
Fabric Manager Users Guide, Version 6.1, Revision A - QLogic
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
1–Overview of the <strong>QLogic</strong> <strong>Fabric</strong> <strong>Manager</strong> Suite<br />
Multiple <strong>Fabric</strong> <strong>Manager</strong>s in a <strong>Fabric</strong><br />
With the sticky failover feature, the <strong>Fabric</strong> <strong>Manager</strong>s can be configured so that<br />
once a <strong>Fabric</strong> <strong>Manager</strong> takes over the master role, it retains that role even if the<br />
original master returns to the fabric and arbitration rules dictate that it should<br />
reclaim the role. Using the sticky failover feature minimizes disruption to the<br />
fabric.<br />
PM – Master, Standby, Failover, Sticky Failover<br />
The PM is built into the SM, therefore the master PM will always be the exact<br />
same <strong>Fabric</strong> <strong>Manager</strong> as the master SM.<br />
BM – Master, Standby, Failover, Sticky Failover<br />
The BM is built into the SM, therefore the master BM will always be the exact<br />
same <strong>Fabric</strong> <strong>Manager</strong> as the master SM.<br />
The sticky failover feature may be applied to the BM as well.<br />
Sticky Failover and Elevated Priority<br />
Elevated priority is supported for the SM/PM and BM. It is the priority the manager<br />
will run at, once it becomes master. This feature defaults to off (0).<br />
By configuring an elevated priority, the user can configure a fabric to only failover<br />
managers when the master fails, rather than re-negotiating whenever a new<br />
manager comes online. This can be achieved by configuring the elevated priority<br />
to be higher than any manager's normal priority.<br />
When elevated priority is configured, a renegotiation at normal priorities can be<br />
forced using the restore priority operation. This will reduce the master's priority<br />
back to normal and renegotiate for master. When the present master is not the<br />
preferred master, this will allow a failover back to the normally preferred master to<br />
occur. For a host FM this is accomplished using the fm_cmd utility. For an<br />
embedded FM, this is accomplished using the smRestorePriority chassis CLI<br />
command.<br />
The intention of this feature is to allow failover to occur only once when a manager<br />
is experiencing intermittent failures, rather than repeatedly passing control back<br />
and forth, disrupting fabric operations. Therefore, it is a best practice to configure<br />
the SM, PM, and BM managers with the same elevated priority. However, this is<br />
not required.<br />
A typical configuration would be an elevated priority of 15 for all FMs, a normal<br />
priority of 8 for the preferred master and a normal priority of 1 for the preferred<br />
standby.<br />
IB0054608-01 B 1-7
Change language