Filter
Top Products
5 – Software Installation
OpenFabrics Drivers and Services Configuration and Startup
5-20 IB0056101-00 G
S
a. Format 1: Defining 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;}
b. 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 attempts to connect to the specified IOC
(1, 2, or 3) 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:
Do not create EIOC names with similar character strings (e.g.,
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.
NOTE:
The IOCSTRING field is a literal, case-sensitive string. Its syntax
must be exactly in the format shown in the previous example,
including the placement of commas. to reduce the likelihood to
syntax error, use the command ib_qlgc_vnic_query -es.
Note that the chassis serial number must match the chassis Ox
(Hex) value. The slot serial number is specific to the line card as
well.