QLogic OFED+ Host Software User Guide, Rev. B

C–VirtualNIC Interface Configuration and Administration
VirtualNIC Interface Configuration and Administration
Format 2: Defining an IOC using the IOCSTRING
Defining the IOC using the IOCSTRING allows VIO hardware to be hot-swapped
in and out of a specific slot. The host will attempt to connect to the specified IOC
(1 or 2) on the VIO hardware that currently resides in the specified slot of the
specified Chassis. Use the following format to allow the host to connect to a VIO
hardware that resides in a specific slot of a specific chassis:
{CREATE;
NAME="eioc1";
IOCSTRING="Chassis 0x00066A0005000001, Slot 1, IOC 1";
RX_CSUM=TRUE;
HEARTBEAT=100; }
NOTE:
The IOCSTRING field is a literal, case-sensitive string, whose syntax must
be exactly in the format shown in the example above, including the
placement of commas. To reduce the likelihood of syntax error, the user
should execute ib_qlgc_vnic_query -es. Note that the chassis serial
number must match the chassis 0x (Hex) value. The slot serial number is
specific to the line card as well.
Each CREATE block must specify a unique NAME. The NAME represents the Ethernet
interface name that will be registered with the Linux Operating System.
Format 3: Starting VNIC using DGID
NOTE:
It is not always necessary to use DGID. It is recommended to use DGID if
the user has a large cluster.
Following is an example of a DGID and IOCGUID VNIC configuration. This
configuration allows for the quickest start up of VNIC service:
{CREATE; NAME="eioc1";
DGID=0xfe8000000000000000066a0258000001;IOCGUID=0x66a01300000
01;
}
This example uses DGID, IOCGUID and IOCSTRING:
{CREATE; NAME="eioc1";
DGID=0xfe8000000000000000066a0258000001;
IOCGUID=0x66a0130000001;
IOCSTRING="Chassis 0x00066A00010003F2, Slot 1, IOC 1";
}
C-6 D000046-005 B