Description
This article describes the behavior of installation to the same FortiGate (multi VDOM) in separate ADOM (advanced enabled) will show a message 'waiting for other session' and 'blocked by session id(xxx)'.
Scope
FortiGate (multi VDOM), FortiManager (advanced ADOM enabled).
Solution
FortiGate setup (multi VDOM enabled):
- root (VDOM 1).
- diffADOM (VDOM 2).
FortiManager setup (advanced ADOM enabled): Go under System Settings -> Advanced -> ADOM Mode -> Advanced, add FortiGate diffADOM VDOM to ADOM 72, and remain root VDOM in root ADOM.
When installing both different ADOMs which is most probably concurrently, FortiManager's current behavior will detect it on a per-device basis instead of a per-VDOM basis. There for the later installation will need to wait for the first installation to finish first, which results in the message in Task Monitor as 'waiting for other session'.
If the installation is made from a different ADOM with a different FortiGate it will not observe the error message unless there are multiple tasks concurrently running which causes the session unable to detect it correctly, and there for 'Workspace' is recommended for multi-user managing FortiManager.
Related article:
Technical Tip: Tasks are blocked due to 'Waiting for other session id'
