Fabric Manager Users Guide, Version 6.1, Revision A - QLogic

More documents

Recommendations

Info

4–Virtual Fabrics Configuration If Security is 0 (Off), LimitedMembers are treated the same as Members. This allows the user to easily turn off Security for a vFabric without changing the rest of the definition. Member and LimitedMember can each be specified more than once per VirtualFabric if required. If a device is in both the Members and LimitedMembers DeviceGroups subsection, it is treated as a Member. This allows All to be specified as a LimitedMember; then selected Members can be specified, ensuring the VirtualFabric includes all devices while allowing a limited set of Members. Devices in a DeviceGroup but not found in the fabric are ignored. By default the QLogic Fabric Manager picks an available PKey for the vFabric. When Security is off, the SM may share the same PKey among multiple vFabrics. If required a user-selected PKey can be specified. PKey must be specified for applications that do not use SA PathRecord queries, including MPIs that use non-IBTA compliant mechanisms for job startup. NOTE: When secure vFabrics are used, every host port must be a member of at least one vFabric for proper operation of host tools such as p1stats and iba_mon it. If a host port is not a member of any vFabric these tools will be unable to access the local port. Application Membership Applications are specified by the application name in the VirtualFabric section. Policies The QoS Policy, MaxMTU, and MaxRate can be specified for a vFabric. This is one way to restrict the capabilities of the vFabric and influence the performance available to applications and devices within the vFabric. Quality of Service (QoS) When setting up QoS within vFabrics, the user should identify the maximum bandwidth for each vFabric when the link is saturated. High-priority, low-volume groups can be configured with the HighPriority setting. The user can also configure the SL used to enforce this bandwidth. If not configured, the SL is assigned. The amount of configured bandwidth cannot exceed 100 percent. If the configured bandwidth does exceed 100 percent, a parser error is given. If there is a mixture of QoS and non-QoS vFabrics configured, all non-QoS vFabrics are assigned the same SL. Any unconfigured bandwidth is assigned to that SL. 4-18 IB0054608-01 B
4–Virtual Fabrics Configuration The Default Partition The InfiniBand Standard requires every fabric to have a default partition. At a minimum this vFabric is used by all end nodes to interact with the SM/SA. To meet this requirement there must be an enabled vFabric with the following items: • A PKey of 0x7ffff (or 0xffff) • The SA application (for example, an Application with SA) • The only enabled vFabric that includes the SA application • Have AllSMs (for example, a DeviceGroup with AllSMs) as a Member • Have All (for example, a DeviceGroup with All) as a Member or LimitedMember • Additional Application as needed • Additional DeviceGroups as Members or LimitedMembers as needed • All other vFabric policies (QoS, Security, MTU...) may be set as needed NOTE: It is a requirement that all chassis-managed spines (for example, SWE0) be a member of the default partition so that the chassis can access and manage its own leaf switch chips. IPoIB and vFabrics vFabrics are configured within the hardware in the order in which they appear in the configuration file. When IPoIB runs, it uses the first PKey on the given port for the default (ib0...) network device. Therefore, it is best to place the Networking/IPoIB vFabric first. IPoIB starts with the PKey for the IPoIB interface and uses that to define the MGID of the VLAN’s broadcast multicast group. Many aspects of the IPoIB VLAN are defined by the multicast group itself. Among them are the MTU for the VLAN. A given port or node can participate in more than one IPoIB subnet. Each such subnet must have its own unique PKey. For vFabrics other than the first, the PKey should be manually specified in the VirtualFabric section and the PKey must be supplied to IPoIB. On some Linux systems with the QLogic InfiniBand or OFED stack, additional IPoIB virtual interfaces can be created by a command such as: echo 0x1234 > /sys/class/net/ib0/create_child IB0054608-01 B 4-19
Page 1 and 2:
User Guide Fabric Manager 7.0.1 IB0
Page 3 and 4:
Table of Contents Preface Intended
Page 5 and 6:
Fabric Manager 7.0.1 User Guide Fab
Page 7 and 8:
Fabric Manager 7.0.1 User Guide 4 V
Page 9 and 10:
Fabric Manager 7.0.1 User Guide D E
Page 11 and 12:
Preface Intended Audience This manu
Page 13 and 14:
For details about available service
Page 15 and 16:
1 Overview of the QLogic Fabric Man
Page 17 and 18:
1-Overview of the QLogic Fabric Man
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
2 Advanced Fabric Manager Capabilit
Page 31 and 32:
2-Advanced Fabric Manager Capabilit
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
3 Fabric Manager Configuration This
Page 73 and 74:
3-Fabric Manager Configuration Conf
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112: 3-Fabric Manager Configuration Conf
Page 145 and 146: 4 Virtual Fabrics Overview Virtual
Page 147 and 148: 4-Virtual Fabrics Configuration Eac
Page 149 and 150: 4-Virtual Fabrics Configuration Tab
Page 151 and 152: 4-Virtual Fabrics Configuration The
Page 153 and 154: 4-Virtual Fabrics Configuration 0
Page 155 and 156: 4-Virtual Fabrics Configuration All
Page 157 and 158: 4-Virtual Fabrics Configuration . T
Page 161: 4-Virtual Fabrics Configuration The
Page 165 and 166: 4-Virtual Fabrics Configuration Sec
Page 167 and 168: 4-Virtual Fabrics Configuration Tab
Page 171 and 172: 4-Virtual Fabrics Configuration
Page 173 and 174: 4-Virtual Fabrics Configuration Al
Page 175 and 176: 5 Embedded Fabric Manager Commands
Page 177 and 178: 5-Embedded Fabric Manager Commands
Page 213 and 214:
5-Embedded Fabric Manager Commands
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
6 Installation and Set Up Installin
Page 255 and 256:
6-Installation and Set Up Installin
Page 257 and 258:
6-Installation and Set Up Installin
Page 259 and 260:
A Fabric Manager Command Line Inter
Page 261 and 262:
A-Fabric Manager Command Line Inter
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
B QLogic Fabric Manager Log Message
Page 277 and 278:
B-QLogic Fabric Manager Log Message
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
C Mapping Old Parameters Versions o
Page 309 and 310:
C-Mapping Old Parameters Old SM Par
Page 311 and 312:
C-Mapping Old Parameters Old SM Par
Page 313 and 314:
C-Mapping Old Parameters Old PM Par
Page 315 and 316:
C-Mapping Old Parameters Old BM Par
Page 317 and 318:
D QOS Options in a Mesh/Torus vFabr
Page 319 and 320:
E ./INSTALL Syntax Syntax ./INSTALL
Page 322:
Corporate Headquarters QLogic Corpo
show all

Fabric Manager Users Guide, Version 6.1, Revision A - QLogic

Create successful ePaper yourself

Delete template?

Save as template?