26.12.2014 Views

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3–<strong>Fabric</strong> <strong>Manager</strong> Configuration<br />

Configuring the <strong>QLogic</strong> <strong>Fabric</strong> <strong>Manager</strong><br />

Table 3-7. Sm Multicast Routing Parameters (Continued)<br />

Parameter<br />

Default<br />

Value<br />

Description<br />

MinCostImprovement 50% When using LeastTotalCost or<br />

LeastWorstCaseCost, the MinCost-<br />

Improvement parameter controls when<br />

the multicast spanning tree root should<br />

be changed if there are changes in the<br />

number of switches in the fabric. The root<br />

will be changed only if in the new topology<br />

a switch's cost is MinCostImprovement<br />

(expressed as a percentage)<br />

better than that of the current root switch<br />

or when the current root switch goes<br />

offline.<br />

A higher value of MinCostImprovement<br />

would result in the multicast spanning<br />

tree root not being changed too<br />

frequently and therefore would cause<br />

less disruptions in multicast traffic. A<br />

smaller value would select the best<br />

switch and provide better multicast<br />

latency but can cause disruptions to multicast<br />

traffic upon fabric changes.<br />

<strong>Fabric</strong> Multicast MLID Sharing<br />

IPv6 (and possibly other applications) can create numerous Multicast groups.<br />

Each Multicast group needs an MLID.<br />

In the case of IPv6, there is one Solicited-Node multicast group per CA port. This<br />

results in an excessively large number of multicast groups. Also in large fabrics,<br />

this quickly exceeds MLIDTableCap. To address this situation, the MLIDShare<br />

fields allow groups of Multicast GIDs to share a limited number of MLIDs. This can<br />

conserve the Hardware MLID tables so other uses of Multicast can be optimized<br />

and efficient.<br />

the MLIDShare fields allow specification of 32 separate groups of MGIDs. Each<br />

group of MGIDs are combined into its own unique set of MLIDs. Each MGID is<br />

ANDed with MGIDMask then compared to MGIDValue. On a match the MGID will<br />

be given a MLID within a pool of MaxMLIDs.<br />

MGIDs are 128 bits specified as two colon separated, 64-bit values, IPv6<br />

Solicited-Node multicast, combined to 500 MLIDs<br />

#SM_0_mcastGrpMGidLimitValue_0#!<br />

IB0054608-01 B 3-25

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!