Product specifications

4–InfiniPath Cluster Setup and Administration
OpenFabrics Drivers and Services Configuration and Startup
4-14 IB6054601-00 H
S
Look at the qlgc_vnic.cfg.sample file to see how VNIC configuration
files are written. This file can be found with the OFED documentation, or in
the qlgc_vnictools subdirectory of the QLogicIB_Basic download. You
can use this configuration file as the basis for creating a configuration file by
replacing the destination global identifier (DGID), IOCGUID, and
IOCSTRING values with those of the EVIC/VEx IOCs present on your fabric.
QLogic recommends using the DGID of the EVIC/VEx IOC, as it ensures the
quickest startup of the VNIC service. When DGID is specified, the IOCGUID
must also be specified. For more details, see the qlgc_vnic.cfg sample
file.
3. Edit the VirtualNIC configuration file,
/etc/infiniband/qlgc_vnic.cfg. For each IOC connection, add a
CREATE block to the file using the following format:
{CREATE; NAME="eioc2";
PRIMARY={IOCGUID=0x66A0130000105; INSTANCE=0; PORT=1; }
SECONDARY={IOCGUID=0x66A013000010C; INSTANCE=0; PORT=2;}
}
a. Format 1: Define an IOC using the IOCGUID. Use the following format
to allow the host to connect to a specific VIO hardware card,
regardless of which chassis and/or slot the VIO hardware card resides:
{CREATE;
NAME="eioc1";
IOCGUID=0x66A0137FFFFE7;}
The following is an example of VIO hardware failover:
{CREATE; NAME="eioc1";
PRIMARY={IOCGUID=0x66a01de000003; INSTANCE=1; PORT=1; }|
SECONDARY={IOCGUID=0x66a02de000003; INSTANCE=1; PORT=1;}
}
NOTE:
The qlgc_vnic.cfg file is case and format sensitive.
NOTE:
Do not create EIOC names with similar character strings (for
example, eioc3 and eioc30). There is a limitation with certain
Linux operating systems that cannot recognize the subtle
differences. The result is that the user will be unable to ping
across the network.