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.

4–Virtual <strong>Fabric</strong>s<br />

Configuration<br />

Securing the Default Partition<br />

When using a secured default partition with v<strong>Fabric</strong>s and redundant <strong>QLogic</strong><br />

<strong>Fabric</strong> <strong>Manager</strong>s, it is recommended to explicitly specify the nodes/ports running<br />

the <strong>QLogic</strong> <strong>Fabric</strong> <strong>Manager</strong>s as Members of the default partition’s v<strong>Fabric</strong>. This is<br />

preferred over using the AllSMs parameter because, upon failure of the SM,<br />

other parts of the <strong>QLogic</strong> <strong>Fabric</strong> <strong>Manager</strong> on the given node may not be able to<br />

perform their functions.<br />

Similarly, if using <strong>QLogic</strong> Fast<strong>Fabric</strong> Toolset in conjunction with a secure default<br />

partition, it will be necessary to specify the nodes/ports running <strong>QLogic</strong> Fast<strong>Fabric</strong><br />

Toolset as Members of the default partitions. Failure to do so limits the operations<br />

that <strong>QLogic</strong> Fast<strong>Fabric</strong> Toolset can perform and the nodes that <strong>QLogic</strong> Fast<strong>Fabric</strong><br />

Toolset can manage.<br />

Multiple v<strong>Fabric</strong>s with Same PKey<br />

When multiple v<strong>Fabric</strong>s are specified with the same PKey, they share a single<br />

PKey. When this occurs, the security for the v<strong>Fabric</strong>s is the logical “OR” of the<br />

security for the two. If security is off in both, there are no limited members (only full<br />

members). If security is on for either (or both), security is imposed for both.<br />

When two v<strong>Fabric</strong>s share the same PKey, the list of members is the combined list<br />

from both v<strong>Fabric</strong>s. Members is the sum of members in both, and<br />

LimitedMembers is the sum of limited members in both.<br />

Multiple v<strong>Fabric</strong>s with Same BaseSL<br />

Parameters<br />

When multiple v<strong>Fabric</strong>s are specified with the same BaseSL, they share a single<br />

SL. When this occurs, the QoS for the v<strong>Fabric</strong>s is the logical “OR” of the QoS for<br />

the two.<br />

Table 4-3. Virtual<strong>Fabric</strong> Parameters<br />

Parameter<br />

Description<br />

Name<br />

Enable<br />

Name for Virtual<strong>Fabric</strong>.<br />

Every Virtual<strong>Fabric</strong> must have a unique name. The<br />

name must be unique among all Virtual<strong>Fabric</strong> names<br />

within an FM instance. When defined at Common level<br />

must be unique within all instances.<br />

The name is limited to 64 characters and is case sensitive.<br />

Enable (1) or Disable (0) a v<strong>Fabric</strong>.<br />

When Disabled (0), the Virtual<strong>Fabric</strong> is ignored. This<br />

allows the user to easily disable a Virtual<strong>Fabric</strong> without<br />

deleting its definition.<br />

IB0054608-01 B 4-21

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

Saved successfully!

Ooh no, something went wrong!