|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
vz:OOBBrCP An out-of-band binary contract profile can only be provided by an out-of-band endpoint group and can only be consumed by the external prefix set. A regular endpoint group cannot provide or consume an out-of-band contract profile. |
|
|
|
|
|
|
|
|
├
|
|
vz:Subj A subject is a sub-application running behind an endpoint group (for example, an Exchange server). A subject is parented by the contract, which can encapsulate multiple subjects. An endpoint group associated to a contract is providing one or more subjects or is communicating with the subject as a peer entity. An endpoint group always associates with a subject and defines rules under the association for consuming/providing/peer-to-peer communicati... |
|
|
|
|
|
|
|
|
|
├
|
|
vz:InTerm An input terminal node. For abstract graphs, this is the terminal node at the input end. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
vz:OOBBrCP An out-of-band binary contract profile can only be provided by an out-of-band endpoint group and can only be consumed by the external prefix set. A regular endpoint group cannot provide or consume an out-of-band contract profile. |
|
|
|
├
|
|
vz:Subj A subject is a sub-application running behind an endpoint group (for example, an Exchange server). A subject is parented by the contract, which can encapsulate multiple subjects. An endpoint group associated to a contract is providing one or more subjects or is communicating with the subject as a peer entity. An endpoint group always associates with a subject and defines rules under the association for consuming/providing/peer-to-peer communicati... |
|
|
|
|
├
|
|
vz:InTerm An input terminal node. For abstract graphs, this is the terminal node at the input end. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
vz:BrCP A contract is a logical container for the subjects which relate to the filters that govern the rules for communication between endpoint groups (EPGs). Without a contract, the default forwarding policy is to not allow any communication between EPGs but all communication within an EPG is allowed. |
|
|
|
|
|
|
|
|
├
|
|
vz:Subj A subject is a sub-application running behind an endpoint group (for example, an Exchange server). A subject is parented by the contract, which can encapsulate multiple subjects. An endpoint group associated to a contract is providing one or more subjects or is communicating with the subject as a peer entity. An endpoint group always associates with a subject and defines rules under the association for consuming/providing/peer-to-peer communicati... |
|
|
|
|
|
|
|
|
|
├
|
|
vz:InTerm An input terminal node. For abstract graphs, this is the terminal node at the input end. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
vz:BrCP A contract is a logical container for the subjects which relate to the filters that govern the rules for communication between endpoint groups (EPGs). Without a contract, the default forwarding policy is to not allow any communication between EPGs but all communication within an EPG is allowed. |
|
|
|
├
|
|
vz:Subj A subject is a sub-application running behind an endpoint group (for example, an Exchange server). A subject is parented by the contract, which can encapsulate multiple subjects. An endpoint group associated to a contract is providing one or more subjects or is communicating with the subject as a peer entity. An endpoint group always associates with a subject and defines rules under the association for consuming/providing/peer-to-peer communicati... |
|
|
|
|
├
|
|
vz:InTerm An input terminal node. For abstract graphs, this is the terminal node at the input end. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
vz:ABrCP An abstraction of a binary contract profile. |
|
|
|
|
|
|
|
|
├
|
|
vz:Subj A subject is a sub-application running behind an endpoint group (for example, an Exchange server). A subject is parented by the contract, which can encapsulate multiple subjects. An endpoint group associated to a contract is providing one or more subjects or is communicating with the subject as a peer entity. An endpoint group always associates with a subject and defines rules under the association for consuming/providing/peer-to-peer communicati... |
|
|
|
|
|
|
|
|
|
├
|
|
vz:InTerm An input terminal node. For abstract graphs, this is the terminal node at the input end. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
vz:ABrCP An abstraction of a binary contract profile. |
|
|
|
├
|
|
vz:Subj A subject is a sub-application running behind an endpoint group (for example, an Exchange server). A subject is parented by the contract, which can encapsulate multiple subjects. An endpoint group associated to a contract is providing one or more subjects or is communicating with the subject as a peer entity. An endpoint group always associates with a subject and defines rules under the association for consuming/providing/peer-to-peer communicati... |
|
|
|
|
├
|
|
vz:InTerm An input terminal node. For abstract graphs, this is the terminal node at the input end. |
|