|
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. |
|
|
|
|
|
|
|
├
|
|
vns:GraphInst The instance of a service graph. All instance objects are implicit. |
|
|
|
|
|
|
|
|
├
|
|
vns:NodeInst An instance of a function node. A service graph consists of multiple function nodes.. |
|
|
|
|
|
|
|
|
|
|
├
|
|
vns:AbsFuncCfg The configuration for a function. This configuration can be shared across multiple functions. |
|
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. |
|
|
├
|
|
vns:GraphInst The instance of a service graph. All instance objects are implicit. |
|
|
|
├
|
|
vns:NodeInst An instance of a function node. A service graph consists of multiple function nodes.. |
|
|
|
|
|
├
|
|
vns:AbsFuncCfg The configuration for a function. This configuration can be shared across multiple functions. |
|
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. |
|
|
|
|
|
|
├
|
|
infra:Infra A container for all tenant infra configurations. |
|
|
|
|
|
|
|
├
|
|
vns:MDev Import a device package into the Application Policy Infrastructure Controller (APIC). The device package contains meta device type definition and definitions of the metadata for a service device type. The metadata contains vendor-specific data including the vendor name, device model, and device version. |
|
|
|
|
|
|
|
|
|
|
├
|
|
vns:AbsFuncProf An abstract function profile includes the abstract device configuration, the abstract group configuration, and the abstract function configuration. These are analogous to the function configuration, group configuration, and device configuration within a device. |
|
|
|
|
|
|
|
|
|
|
|
├
|
|
vns:AbsFuncCfg The configuration for a function. This configuration can be shared across multiple functions. |
|
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. |
|
├
|
|
infra:Infra A container for all tenant infra configurations. |
|
|
├
|
|
vns:MDev Import a device package into the Application Policy Infrastructure Controller (APIC). The device package contains meta device type definition and definitions of the metadata for a service device type. The metadata contains vendor-specific data including the vendor name, device model, and device version. |
|
|
|
|
|
├
|
|
vns:AbsFuncProf An abstract function profile includes the abstract device configuration, the abstract group configuration, and the abstract function configuration. These are analogous to the function configuration, group configuration, and device configuration within a device. |
|
|
|
|
|
|
├
|
|
vns:AbsFuncCfg The configuration for a function. This configuration can be shared across multiple functions. |
|
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. |
|
|
|
|
|
|
|
|
|
├
|
|
vns:AbsFuncProf An abstract function profile includes the abstract device configuration, the abstract group configuration, and the abstract function configuration. These are analogous to the function configuration, group configuration, and device configuration within a device. |
|
|
|
|
|
|
|
|
|
|
├
|
|
vns:AbsFuncCfg The configuration for a function. This configuration can be shared across multiple functions. |
|
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. |
|
|
|
|
├
|
|
vns:AbsFuncProf An abstract function profile includes the abstract device configuration, the abstract group configuration, and the abstract function configuration. These are analogous to the function configuration, group configuration, and device configuration within a device. |
|
|
|
|
|
├
|
|
vns:AbsFuncCfg The configuration for a function. This configuration can be shared across multiple functions. |
|
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. |
|
|
|
|
|
|
|
├
|
|
vns:AbsGraph The abstract graph is made up of abstract nodes and used to define the traffic flow through a service function such as load balancing, SSL offload, and firewall. Abstract nodes are comprised of service nodes such as a service node balancer (SLB) or firewall (FW), abstract term nodes (the nodes that are connected to endpoint groups), and connections. |
|
|
|
|
|
|
|
|
├
|
|
vns:AbsNode An abstract node represents a service node such as a server load balancer (SLB) or firewall (FW). An abstract node is contained in an abstract graph. |
|
|
|
|
|
|
|
|
|
├
|
|
vns:AbsFuncCfg The configuration for a function. This configuration can be shared across multiple functions. |
|
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. |
|
|
├
|
|
vns:AbsGraph The abstract graph is made up of abstract nodes and used to define the traffic flow through a service function such as load balancing, SSL offload, and firewall. Abstract nodes are comprised of service nodes such as a service node balancer (SLB) or firewall (FW), abstract term nodes (the nodes that are connected to endpoint groups), and connections. |
|
|
|
├
|
|
vns:AbsNode An abstract node represents a service node such as a server load balancer (SLB) or firewall (FW). An abstract node is contained in an abstract graph. |
|
|
|
|
├
|
|
vns:AbsFuncCfg The configuration for a function. This configuration can be shared across multiple functions. |
|