Class vns:FltInst (CONCRETE)

Class ID:4807
Encrypted: false - Exportable: false - Persistent: true - Configurable: false - Subject to Quota: Disabled - Abstraction Layer: Logical Model - APIC NX Processing: Disabled
Write Access: [NON CONFIGURABLE]
Read Access: [admin, nw-svc-policy]
Creatable/Deletable: yes (see Container Mos for details)
Semantic Scope: EPG
Semantic Scope Evaluation Rule: Parent
Monitoring Policy Source: Parent
Monitoring Flags : [ IsObservable: false, HasStats: false, HasFaults: false, HasHealth: false, HasEventRules: false ]

RN FORMAT: fltInst-{[aFltDn]}

    [1] PREFIX=fltInst- PROPERTY = aFltDn




DN FORMAT: 

[1] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeProv-{name}/outtmnl/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[3] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeCon-{name}/outtmnl/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[5] uni/tn-{name}/GraphInst_C-{[ctrctDn]}-G-{[graphDn]}-S-{[scopeDn]}/TermNodeInst-{name}/outtmnl/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[7] uni/tn-{name}/AbsGraph-{name}/outtmnl/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[9] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeProv-{name}/intmnl/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[11] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeCon-{name}/intmnl/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[13] uni/tn-{name}/GraphInst_C-{[ctrctDn]}-G-{[graphDn]}-S-{[scopeDn]}/TermNodeInst-{name}/intmnl/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[15] uni/tn-{name}/AbsGraph-{name}/intmnl/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[17] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeProv-{name}/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[19] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeCon-{name}/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[21] uni/tn-{name}/GraphInst_C-{[ctrctDn]}-G-{[graphDn]}-S-{[scopeDn]}/TermNodeInst-{name}/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[23] uni/tn-{name}/AbsGraph-{name}/rstermToAny-{[tDn]}/fltInst-{[aFltDn]}

[25] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeProv-{name}/outtmnl/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

[27] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeCon-{name}/outtmnl/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

[29] uni/tn-{name}/GraphInst_C-{[ctrctDn]}-G-{[graphDn]}-S-{[scopeDn]}/TermNodeInst-{name}/outtmnl/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

[31] uni/tn-{name}/AbsGraph-{name}/outtmnl/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

[33] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeProv-{name}/intmnl/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

[35] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeCon-{name}/intmnl/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

[37] uni/tn-{name}/GraphInst_C-{[ctrctDn]}-G-{[graphDn]}-S-{[scopeDn]}/TermNodeInst-{name}/intmnl/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

[39] uni/tn-{name}/AbsGraph-{name}/intmnl/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

[41] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeProv-{name}/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

[43] uni/tn-{name}/AbsGraph-{name}/AbsTermNodeCon-{name}/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

[45] uni/tn-{name}/GraphInst_C-{[ctrctDn]}-G-{[graphDn]}-S-{[scopeDn]}/TermNodeInst-{name}/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

[47] uni/tn-{name}/AbsGraph-{name}/rstermToEPg-{[tDn]}/fltInst-{[aFltDn]}

                

Diagram

Super Mo: pol:Comp, Container Mos: vns:RsTermToAny (deletable:yes), vns:RsTermToEPg (deletable:yes),

Containers Hierarchies

top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeProv An abstract terminal node connected to contract provider.                    ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeProv An abstract terminal node connected to contract provider.          ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.                    ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.          ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:TermNodeInst A terminal node instance.                    ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:TermNodeInst A terminal node instance.          ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).                    ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).          ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeProv An abstract terminal node connected to contract provider.                    ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeProv An abstract terminal node connected to contract provider.          ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.                    ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.          ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:TermNodeInst A terminal node instance.                    ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:TermNodeInst A terminal node instance.          ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).                    ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).          ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeProv An abstract terminal node connected to contract provider.                    ├ vns:ATerm A terminal.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeProv An abstract terminal node connected to contract provider.          ├ vns:ATerm A terminal.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.                    ├ vns:ATerm A terminal.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.          ├ vns:ATerm A terminal.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:TermNodeInst A terminal node instance.                    ├ vns:ATerm A terminal.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:TermNodeInst A terminal node instance.          ├ vns:ATerm A terminal.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).                    ├ vns:ATerm A terminal.                      ├ vns:RsTermToAny                         ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).          ├ vns:ATerm A terminal.            ├ vns:RsTermToAny               ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeProv An abstract terminal node connected to contract provider.                    ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeProv An abstract terminal node connected to contract provider.          ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.                    ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.          ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:TermNodeInst A terminal node instance.                    ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:TermNodeInst A terminal node instance.          ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).                    ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).          ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeProv An abstract terminal node connected to contract provider.                    ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeProv An abstract terminal node connected to contract provider.          ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.                    ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.          ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:TermNodeInst A terminal node instance.                    ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:TermNodeInst A terminal node instance.          ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).                    ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).          ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeProv An abstract terminal node connected to contract provider.                    ├ vns:ATerm A terminal.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeProv An abstract terminal node connected to contract provider.          ├ vns:ATerm A terminal.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.                    ├ vns:ATerm A terminal.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNodeCon An abstract terminal node connected to a contract consumer.          ├ vns:ATerm A terminal.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:TermNodeInst A terminal node instance.                    ├ vns:ATerm A terminal.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:TermNodeInst A terminal node instance.          ├ vns:ATerm A terminal.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. top:Root  This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.  ├ fabric:Topology The root for IFC topology.    ├ fabric:Pod A pod.      ├ fabric:Node The root node for the APIC.        ├ ctx:Local The local Context.          ├ ctx:Application The context application.            ├ 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).                    ├ vns:ATerm A terminal.                      ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object                        ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group. 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:AbsTermNode An abstract terminal node. Abstract terminal nodes are typically attached to the endpoint groups, and are connected to the abstract graph (AbsGraph) through an abstract connection (AbsConnection).          ├ vns:ATerm A terminal.            ├ vns:RsTermToEPg A source relation to a set of endpoints. Note that this relation is an internal object              ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group.