User Manual

ALL VLAN must be supported by both the BridgeX® and by the host side.

When enabling ALL VLAN, all gateways (LAG or legacy) that have eports belonging

to a gateway group (GWG) must be configured to the same behavior.

For example it is impossible to have gateway A2 configured to all-vlan mode and A3

to regular mode, because both belong to GWG

A gateway that is configured to work in ALL VLAN mode cannot accept login

requests from

•vNics that do not support this mode

•host admin vNics that were not configured to work in ALL VLAN mode, by setting

the vlan-id value to a 'all' as as described in Section 3.2.5.3.3.8, “Creating

vNICs that Support ALL VLAN Mode”, on page 145

Rev 2.3-1.0.1

Mellanox Technologies

145

3.2.5.3.3.8 Creating vNICs that Support ALL VLAN Mode

VLANs are created on a vNIC that supports ALL VLAN mode using "vconfig".

• net-admin vNics

The net-admin vNic supports ALL VLAN mode once it is created on a gateway configured with All-

VLAN mode.

• host-admin vNics

• To create an ALL VLAN vnic, set the VLAN's ID to 'all'.

A gateway that is configured to work in ALL VLAN mode, can only accept login requests from hosts that

are also working in a VLAN mode. e.g. the VLAN ID must be set to 'all'.

This is an example of how to create an ALL VLAN vNic using the mlx4_vnic.conf file:

name=eth44 mac=00:25:8B:27:14:78 ib_port=mlx4_0:1 vid=all vnic_id=5

bx=00:00:00:00:00:00:04:B2 eport=A10

• To create an All-VLAN vNic using a specific configuration file, add the following line to the con-

figuration file:

VNICVLAN=all

For further information on how to create host-admin vNics, please see Section 3.2.5.3.2.1, “EoIB

Host Administered vNic”, on page 137 EoIB Host Administered vNic.

3.2.5.3.3.9 Checking the Configuration

To verify the gateway / vNic is configured with the All-VLAN mode, use the mlx4_vnic_info

script.

• Gateway Support

To verify the gateway is configured to All-VLAN mode. Run:

mlx4_vnic_info -g <GW-NAME>