If you are running a version of CloudBolt from 9.4.1 and prior you will be limited to 4 network cards to an environment.
We recommend installing the latest version of CloudBolt to gain the additional NICS out of the box, however, if you are not in a position to upgrade at the moment then the following steps will help increase the amount of NICS in your environment.
Please be aware that this method is a Global Setting so will add an additional network card to all your builds in scope. We STRONGLY suggest upgrading to the latest version
You can SSH to your CloudBolt appliance
You have a knowledge of shell_plus
We recommend upgrading to the latest version of CloudBolt as this is a workaround.
This is a global default and will apply an additional network card to anything within scope
Adding additional NICS through Shell_Plus
SSH to your CloudBolt appliance
Go into shell_plus by typing the following command
from Shell_Plus run the following command to add NIC5 (Repeat as necessary changing sc_nic_N and NICN)
n,_= CustomField.objects.get_or_create(name = 'sc_nic_4', label='NIC5', type='NET')
In your CloudBolt web console, go to Admin, Parameters and search for sc_nic. You will see you now have the additional NIC available as a parameter.
Click on NIC5 to edit the settings then click on the plus next to Global Defaults
Select the network for NIC5, leave the Global Target and then choose an OS family and then click on Set Global Default.
NOTE: This is a global setting, this means it will add a network card to EVERY build for that OS Family you select. This is why we recommend upgrading to the latest version of CloudBolt
Now when you deploy a server that meets your OS type it will deploy an additional NIC. This does not take into consideration if there are 4 network cards already selected, this will apply if even 1 NIC is applied. This is the biggest reason we STRONGLY recommend upgrading to the latest version of CloudBolt.
I have test deployed a VM with the 4 NICS assigned and you will see in vCenter the 5th NIC is assigned automatically.
I also test deployed a VM with only the first NIC assigned, and it deployed with a second NIC. This is the behavior expected from this workaround.
CloudBolt Quick Start Guide : https://docs.cloudbolt.io/articles/#!cloudbolt-latest-docs/quick-start-guide