Technical Tip: VDOM 'dmgmt-vdom' was added causing HA out-of-sync

[ychia]

Description	This article explains why VDOM 'dmgmt-vdom' was added automatically. Based on the logs: itime=1685830059 date="2023-06-04" time="06:06:41" devid="FG1KXXXXXXXXXXX" vd="root" type="event" subtype="ha" bid=37446314 devname="FGT01" dstepid=3 dsteuid=3 dvid=1222 epid=3 euid=3 eventtime=1685830002022110601 id=7240584970018750480 level="notice" logdesc="Virtual cluster VDOM added" logid="0108037891" logver=602061175 msg="Virtual cluster's vdom is added" to_vcluster=1 tz="+0800" vdname="dmgmt-vdom" Followed by HA slave synchronization failed: itime=1685830059 date="2023-06-04" time="06:06:42" devid="FG1KXXXXXXXXXXXX" vd="root" type="event" subtype="ha" bid=37446314 devname="FGT01" dstepid=3 dsteuid=3 dvid=1222 epid=3 euid=3 eventtime=1685830002068442263 id=7240584970018750481 level="error" logdesc="HA slave synchronization failed" logid="0108035011" logver=602061175 msg="HA slave sync failed in 3 turns" tz="+0800"
Scope	FortiGate.
Solution	FortiGate has a reserved VDOM 'dmgmt-vdom' for dedicated management. FortiGate (vdom) # edit dmgmt-vdom <-----'dmgmt-vdom' is reserved and cannot be edited directly. Ignore those events as it is per design and should not affect the FortiGate.