Troubleshooting VDOMs
This section addresses common problems and specific concerns that you may encounter when using VDOMs. All steps assume that you are accessing the management VDOM and have access to global and per-VDOM settings.
This section includes:
- The option to enable VDOMs is missing
- Administrators can't access their assigned VDOM
- Your FortiGate is running slowly
- Your license for additional VDOMs doesn't appear
- You can't delete a VDOM
- A non-management VDOM isn't working with SNMP
The option to enable VDOMs is missing
If the option to enable VDOMs doesn't appear in the GUI, connect to the CLI and use the following command:
config system global
set vdom-admin enable
end
Administrators can't access their assigned VDOM
Use the following steps to troubleshoot administrator access:
- Confirm that the administrator is assigned to the correct VDOM by going to Global > System > Administrators. Edit the administrator account and make sure Virtual Domain is set to the right VDOM.
- Confirm that the administrator is using the correct FortiGate interface to access the VDOM by going to Global > Network > Interfaces. Edit the interface and make sure Virtual Domain is set to the right VDOM and Administrative Access allows the proper protocols.
|
|
If the interface is referenced by the configuration, you can't change which VDOM it's assigned to. |
- If you have a remote administrator, make sure that the administrator is using an interface that is part of the same VDOM as the group the administrator is a part of.
Your FortiGate is running slowly
When using VDOMS, your FortiGate may run slowly because you either have configured too many VDOMs or one or more VDOMS are consuming too many system resources.
If you have configured many VDOMs on your system, the performance of your FortiGate may be affected. Each VDOM you create on your FortiGate requires system resources to function - CPU cycles, memory, and disk space. When there are too many VDOMs configured there are not enough resources for operation.
If you have sufficient hardware to support the number of VDOMs you're running, check the global resources on your FortiGate by going to Global > System > Global Resources. If any VDOM uses more resources than desired, you can set limits as appropriate.
Your license for additional VDOMs doesn't appear
When you apply a license for more VDOMs on your FortiGate, it may take up to 4 hours for the license to appear on the FortiGate. To speed this process up, you can run the CLI command execute update-now to tell the FortiGate to update all licenses.
You can't delete a VDOM
|
|
The root VDOM can't be deleted. |
If you aren't able to delete a VDOM, make sure that nothing in the current configuration doesn't reference that VDOM, including interfaces, routes, and policies. To check if there are any current references, go to Global > System > VDOM and look at the Ref. column. The number of references to each VDOM is listened.
When you select the number, a list of the references opens. You may be able to delete some references directly from this list. Others, such as interface assignment, must be changed using the main GUI page, such as Network > Interfaces.
A non-management VDOM isn't working with SNMP
Because SNMP is configured as a global setting, traps can only be sent to interfaces that belong to the management VDOM.