User Manual

Driver FeaturesRev 2.2-1.0.1
Mellanox Technologies
64
vNic Specific Configuration Files - ifcfg-ethX
EoIB configuration can use the ifcfg-ethX files used by the network service to derive the needed
configuration. In such case, a separate file is required per vNic. Additionally, you need to update
the ifcfg-ethX file and add some new attributes to it.
On Red Hat Linux, the new file will be of the form:
DEVICE=eth2
HWADDR=00:30:48:7d:de:e4
BOOTPROTO=dhcp
ONBOOT=yes
BXADDR=BX001
BXEPORT=A10
VNICIBPORT=mlx4_0:1
VNICVLAN=3 (Optional field)
GW_PKEY=0xfff1
The fields used in the file for vNic configuration have the following meaning:
ib_port The device name and port number in the form [device name]:[port number].
The device name can be retrieved by running ibv_devinfo and using the out-
put of hca_id field. The port number can have a value of 1 or 2.
vid [Optional field] If VLAN ID exists, the vNic will be assigned the specified
VLAN ID. This value must be between 0 and 4095.
• If the vid is set to 'all', the ALL-VLAN mode will be enabled and the
vNic will support multiple vNic tags.
• If no vid is specified or value -1 is set, the vNic will be assigned to the
default vHub associated with the GW.
vnic_id A unique number per vNic between 0 and 16K.
bx The BridgeX box system GUID or system name string.
eport The string describing the eport name.
pkey [Optional field] If discovery_pkey module parameter is set, this value will
control which partitions would be used to discover the gateways.
For more information about discovery_pkeys please refer to
Section 4.3.3.5, “Discovery Partitions Configuration”, on page 69
Table 4 - Red Hat Linux mlx4_vnic.conf file format
Field Description
DEVICE An optional field. The name of the interface that is displayed when running
ifconfig. If it is not present, the trailer of the configuration file name (e.g.
ifcfg-eth47 => "eth47") is used instead.
HWADDR The mac address to assign the vNic.
Table 3 - mlx4_vnic.conf file format
Field Description