By default, VNICs are created and allocated by the management controller of the gateway using Gateway Manual Mode. The createvnic command creates the VNICs, and the resulting VNIC resources are controlled by the gateway.
Alternatively, individual hosts can create and allocate VNICs on the gateway. There are two ways to enable this functionality.
sethostvniclimit – Running the sethostvniclimit command on the management controller of the gateway restricts the number of VNICs that can be created by specified host ports, for specified external ports 0A-ETH-1 to 0A-ETH-4 and 1A-ETH-1 to 1A-ETH-4. Using the sethostvniclimit command to allow host created VNICs is optimal, because the VNIC resources are controlled by the gateway.
allowhostconfig – Running the allowhostconfig command on the management controller of the gateway allows all hosts connected to the gateway through the IB fabric to create up to 1000 VNICs on any external port (0A-ETH-1 to 0A-ETH-4 and 1A-ETH-1 to 1A-ETH-4). In this situation, VNIC resources are not controlled by the gateway. Use of the allowhostconfig command requires consideration of the impact on the gateway's performance.
Only one of these methods can be used at a time. You can display which method is available for use with the showgwconfig command. If in the output of the showgwconfig command the Running Value for the Allow host VNIC config parameter is yes, then unrestricted host created VNICs functionality is enabled (allowhostconfig). If you want to restrict host created VNICs, use the disallowhostconfig command to change the Running Value to no (as seen with the showgwconfig command), and then use the sethostvniclimit command.
Gateway Reference, sethostvniclimit command
Gateway Reference, allowhostconfig command
Gateway Reference, showgwconfig command
Gateway Reference, disallowhostconfig command
Create VNICs
Enable VNICs
Disable VNICs
Delete VNICs