|
fv:SiteCont Container for all multi-site sites. This is shardeable so that we store all mappings in a single
shard for simplicity. |
├
|
|
fv:RtToRemoteSiteCont Relation that will cause the download of the
fv:SiteCont when required. this will be
triggered by behavioural code on PE when
handling changes on the LNodePDef Mo.
NOTE: the update-type is 'subtree-with-rels' because the
entire SiteCont hierarchy needs to be pulled down. |
├
|
|
fv:Site Site object added for multi site support |
|
|
|
├
|
|
fault:Delegate Exposes internal faults to the user. A fault delegate object can be defined on IFC (for example, for an endpoint group) and when the fault is raised
(for example, under an endpoint policy on a switch), a fault delegate object is created on IFC under the specified object. A fault delegate object follows the lifecycle of the original fault instance object, being created, modified, or deleted based on the changes of the original fault. |
|
|
|
├
|
|
fault:Delegate Exposes internal faults to the user. A fault delegate object can be defined on IFC (for example, for an endpoint group) and when the fault is raised
(for example, under an endpoint policy on a switch), a fault delegate object is created on IFC under the specified object. A fault delegate object follows the lifecycle of the original fault instance object, being created, modified, or deleted based on the changes of the original fault. |
|
|
|
├
|
|
fault:Delegate Exposes internal faults to the user. A fault delegate object can be defined on IFC (for example, for an endpoint group) and when the fault is raised
(for example, under an endpoint policy on a switch), a fault delegate object is created on IFC under the specified object. A fault delegate object follows the lifecycle of the original fault instance object, being created, modified, or deleted based on the changes of the original fault. |
|