Configuring Drivers and Services

OpenFabrics Drivers and Services Configuration and Startup

S

5.You can look for the newly created devices in the /proc/partitions file. The file will look similar to this example (the partition names may vary):

# cat /proc/partitions major minor #blocks name

864 142325760 sde

865 142319834 sde1

8

80

71162880

sdf

8

81

71159917

sdf1

8

96

20480

sdg

8

97

20479

sdg1

6.Create a mount point (as root) where you will mount the SRP device. For example:

#mkdir /mnt/targetname

#mount /dev/sde1 /mnt/targetname

NOTE:

Use sde1 rather than sde. See the mount(8) man page for more information on creating mount points.

Configuring and Administering the VNIC Interface

The VirtualNIC (VNIC) Upper Layer Protocol (ULP) works in conjunction with firmware running on Virtual Input/Output (VIO) hardware such as the SilverStorm Ethernet Virtual I/O Controller (EVIC™) or the InfiniBand/Ethernet Bridge Module for IBM® BladeCenter®, providing virtual Ethernet connectivity.

The VNIC driver along with the QLogic EVIC’s two 10 Gigabit ethernet ports, enables Infiniband clusters to connect to Ethernet networks. This driver also works with the earlier version of the I/O Controller, the VEx.

The QLogic VNIC driver creates virtual Ethernet interfaces and tunnels the Ethernet data to/from the EVIC over InfiniBand using an InfiniBand reliable connection.

The virtual Ethernet interface supports any Ethernet protocol. It operates normally like any other interface--ping, ssh, scp, netperf etc.

The VNIC interface must be configured before it can be used. To do so, perform the following steps:

1.Discover the EVIC/VEx Input/Output Controllers (IOCs) present on the fabric using ib_qlgc_vnic_query. For writing the configuration file, you will need information about the EVIC/VEx IOCs present on the fabric, such as

6-6

Preliminary

IB0056101-00 G.02

Page 78
Image 78
Q-Logic OFED, IB0056101-00 G.02 manual Configuring and Administering the Vnic Interface