Class pol:Comp (ABSTRACT)

Class ID:4597
Encrypted: false - Exportable: true - Persistent: true - Configurable: true - Subject to Quota: Disabled
Write Access: []
Read Access: [admin]
Creatable/Deletable: derived (see Container Mos for details)
Possible Semantic Scopes: Common, EPG, Infra, Fabric,
Semantic Scope Evaluation Rule: Subclasses
Monitoring Policy Source: Parent
Monitoring Flags : [ IsObservable: false, HasStats: false, HasFaults: false, HasHealth: false, HasEventRules: false ]

DN FORMAT: 

                

Diagram

Super Mo: pol:Obj, Sub Mos: callhome:Dest, callhome:DestReachState, callhome:DestState, callhome:InvTask, comm:Comp, comp:PrimaryEncapDef, compat:Filter, compat:Fw, compat:Hw, compat:Sw, config:Job, config:Snapshot, config:SubJob, cons:Node, cons:Root, cons:SubNode, coop:Rep, datetime:ANtpAuthKey, datetime:ANtpProv, dbg:ACRulePCommon, dbg:AtomicCntrP, dbg:DebugP, dhcp:AInfraProvP, dhcp:GwDef, dnsepg:IpAddrBlk, fabric:ANodePEp, fabric:AnycastMulticastSetupP, fabric:ChainCtxP, fabric:CtrlrIdentP, fabric:Decommission, fabric:DecommissionJob, fabric:NodeIdentP, fabric:ProtLink, fabric:ProtoComp, fabric:SetupP, file:ARemoteHost, firmware:Source, fmcast:NodePEp, fmcast:NumTree, fmcast:TreeEp, fv:AIfConn, fv:APodConnP, fv:AREpPDomDefDependencyResolver, fv:ASiteConnP, fv:CepNetCfgPol, fv:Comp, fv:Encap, fv:EncapDef, fv:EpPCtrctInfo, fv:ExtLocaleCont, fv:L3extOutLblDepl, fv:PoolDef, fv:PrimaryEncapDef, fv:PullREpPCont, fv:QinqFabEncapDef, fv:REpPCont, fv:SystemGIPoDef, fv:TepPoolDef, fv:VsanEncapDef, fvns:AAddrBlk, fvns:AEncapBlk, geo:Building, geo:Floor, geo:Rack, geo:Room, geo:Row, health:LevelP, health:Pol, health:PolCont, hvs:Encap, ident:AllocRule, ident:Block, igmp:AIfP, igmp:ASnoopAccessGroup, igmp:ASnoopStaticGroup, infra:AFunc, infra:ANode, infra:AttPolicyGroup, infra:Encap, infra:EncapDef, infrazone:Zone, ip:ANexthopEpP, ip:ANexthopP, ipmc:ASSMXlateP, l2:Cons, l3:Cons, l3ext:AExtEncapAllocator, l3ext:AMember, l3ext:AOutRefSrc, l3ext:AOutRefSrcCont, l3ext:DepPolState, l3ext:GlobalCtxName, l3ext:GlobalCtxNameDef, l3ext:InfraNodeP, l3ext:IntersiteLoopBackIfP, l3ext:IntersiteLoopBackIfPDef, l3ext:LoopBackIfP, l3ext:LoopBackIfPDef, l3ext:OutRef, mgmt:AZone, mon:ATarget, mon:ExportP, mon:Group, mon:ProtoP, mon:SecAuthP, mon:Src, mon:Subj, monitor:Destination, monitor:Session, monitor:Source, nws:ASrc, pim:RouteMapDefWrapper, planner:ATmpl, planner:FexTmpl, planner:LeafTmpl, planner:SpineTmpl, planner:TenantTmpl, qos:ABuffer, qos:ACong, qos:AQueue, qos:ASched, qos:Classification, qosp:PrioFlowCtrl, rtctrl:CtxP, rtctrl:Scope, rtctrl:SubjDef, rtctrl:SubjP, rtdmc:AFilterPol, rtdmc:APatPol, rtdmc:ARPPol, rtdmc:ARtMapEntry, rtdmc:AStaticRPEntry, snmp:AClientGrpP, snmp:ACommunityP, snmp:AUserP, span:ASource, span:Destination, span:Session, stats:AColl, stats:AExportJob, stats:AThrP, stats:Reportable, stp:AllocEncapBlkDefDependencyResolver, stp:DomFabCons, stp:DomFabEncap, stp:EncapSegIdPair, svccore:CoreState, syslog:Console, syslog:DestState, syslog:FacilityFilter, syslog:File, syslog:LogMsg, syslog:SystemMsgP, trig:Executable, tunnel:Cons, ui:SettingsCont, useg:DomainCont, useg:UsegEPgDefCont, vns:ALDevCtx, vns:ALIfCtx, vns:ATerm, vns:CtrlrMgmtPol, vns:FltInst, vns:OrchReq, vns:RedirectDest, vpc:KAPol, vz:AFiltEntry, vz:ASubj, vz:ATerm, vz:AllocateSharedService, vz:AnyDef, vz:AnyGroupDef, vz:AnyREpPCont, vz:GlobalPcTagRequest, vz:GlobalPcTagRequestCont, vz:PcTagCons, vz:ResPcTag,

Inheritance

naming:NamedObject An abstract base class for an object that contains a name.  ├ pol:Obj Represents a generic policy object.    ├ pol:Comp Represents a policy component. This object is part of the policy definition.      ├ callhome:Dest The Call Home destination profile contains the delivery information for receiving email-based alert notifications of critical system policies. A range of message formats are available for compatibility with pager services or XML-based automated parsing applications. You can use this feature to page a network support engineer, email a Network Operations Center, or use Cisco Smart Call Home services to generate a case with the Technical Assistance...      ├ callhome:DestReachState  CallHome Dest state Per Apic Node      ├ callhome:DestState       ├ callhome:InvTask       ├ comm:Comp default port value is 0. All services that have assigned port override port value. 0 indicates that this service does not use a separate port        ├ comm:Shell SuperClass for shell-based access (Ssh and Telnet) and not directly used for user configuration.          ├ comm:Shellinabox           ├ comm:Ssh Object that encompasses properties related to Secure Shell access to the APIC, namely admin-state (default=enabled) and port(default=22).          ├ comm:SshInst           ├ comm:Telnet Telnet          ├ comm:TelnetInst  Service configuration for various services        ├ comm:Web SuperClass for web based access (HTTP and HTTPS) and not directly used for user configuration.          ├ comm:Http HTTP          ├ comm:Https HTTPS      ├ comp:PrimaryEncapDef       ├ compat:Filter Feature filter - software is not compatible when any of the filters evaluates to True        ├ compat:CompFilter Complex filter - logical grouping of Leaf terms        ├ compat:LfFilter Leaf term      ├ compat:Fw Firmware version        ├ compat:CtlrFw Controller Firmware        ├ compat:FexFw Fex Firmware        ├ compat:LcFw Line card Firmware        ├ compat:SwitchFw Switch Firmware        ├ compat:VSwitchFw VSwitch Firmware      ├ compat:Hw Hardware model        ├ compat:CtlrHw Controller hardware        ├ compat:FexHw Fex hardware        ├ compat:LcHw Line card hardware        ├ compat:SwitchHw Switch hardware      ├ compat:Sw         ├ compat:FvSw       ├ config:Job The configuration job.      ├ config:Snapshot       ├ config:SubJob The sub job.      ├ cons:Node       ├ cons:Root       ├ cons:SubNode       ├ coop:Rep The COOP repository. The user can only change the associated policy.      ├ datetime:ANtpAuthKey This object is a digital signature. The usual data packet plus the key is used to build a non-reversible number that is appended to the packet. The receiver (having the same key) does the same computation and compares the result. If the results match, authentication succeeds.        ├ datetime:NtpAuth The NTP client authentication configures the device to authenticate the time sources to which the local clock is synchronized. When you enable NTP authentication, the device synchronizes to a time source only if the source carries one of the authentication keys specified by the ntp trusted-key command. The device drops any packets that fail the authentication check and prevents them from updating the local clock. NTP authentication is disabled by...        ├ datetime:NtpAuthKey The date/time NTP authentication key is used to define a client authentication key if your NTP server requires authentication.      ├ datetime:ANtpProv These user-configured NTP provider names are listed as host names/IP addresses and can be between 1 and 64 alphanumeric characters. These names cannot be changed after the objects have been saved.        ├ datetime:NtpProv The date/time NTP provider is an NTP server.        ├ datetime:NtpProvider Represents the date/time NTP provider information for the switch.      ├ dbg:ACRulePCommon The atomic counter rule policy common.        ├ dbg:ACRuleIp The IP match rule policy for atomic counter probe.      ├ dbg:AtomicCntrP User-configured flows/match rules for atomic counter probes.      ├ dbg:DebugP The debug policy.      ├ dhcp:AInfraProvP Abstract class for infrastructure provider profiles.        ├ dhcp:InfraProvP The infrastructure provider policy.        ├ dhcp:InfraProvPDef The infrastructure provider definition.      ├ dhcp:GwDef       ├ dnsepg:IpAddrBlk       ├ fabric:ANodePEp A base class for node policy endpoint.        ├ bgp:RRNodePEp The MP-BGP Route Reflector End Point Policy is used to specify Route Reflector Nodes/Spines for the MP-BGP running inside the fabric.        ├ coop:NodePEp The COOP group member information.        ├ fabric:NodePEp The node policy endpoint. This is specified by a unique node ID.        ├ fabric:VpcConsumer         ├ pres:RegdNode         ├ pres:Resolver This is generated and used only by internal processes.        ├ pres:ResolverDef This is generated and used only by internal processes.      ├ fabric:AnycastMulticastSetupP       ├ fabric:ChainCtxP A node proxy IP holder per protection type.      ├ fabric:CtrlrIdentP       ├ fabric:Decommission An object for decommissioning a node.      ├ fabric:DecommissionJob An internal object for tracking decommission jobs.      ├ fabric:NodeIdentP The node identity profile assigns IDs to the fabric nodes.      ├ fabric:ProtLink The information about a protected link between two fabric nodes.      ├ fabric:ProtoComp A base class for protocol policies.        ├ dns:ADomain Sets the DNS domain parameters.          ├ dns:Dom The DNS domain uses a hierarchical scheme for establishing host names for network nodes and allows local control of the segments of the network through a client-server scheme. The DNS system can locate a network device by translating the hostname of the device into its associated IP address.          ├ dns:Domain The DNS domain uses a hierarchical scheme for establishing host names for network nodes and allows local control of the segments of the network through a client-server scheme. The DNS system can locate a network device by translating the hostname of the device into its associated IP address.        ├ fabric:L2ProtoComp A base class for layer 2 protocol policies.          ├ edr:EventP The per event recovery policy specifies from which error event a port is allowed to recover. The supported error events are bpdu guard, mcp loop, and ep move.          ├ stp:MstDomPol The MST domain policy enables you to assign two or more VLANs to a spanning tree instance. MST is not the default spanning tree mode; Rapid per VLAN Spanning Tree (Rapid PVST+) is the default mode. MST instances with the same name, revision number, and VLAN-to-instance mapping combine to form an MST region. The MST region appears as a single bridge to spanning tree configurations outside the region. MST fails over to IEEE 802.1D Spanning Tree Pro...          ├ stp:MstRegionPol The MST region policy enables switches to participate in MST instances when you consistently configure the switches with the same MST configuration information. A collection of interconnected switches that have the same MST configuration is an MST region. An MST region is a linked group of MST bridges with the same MST configuration.        ├ fabric:L3ProtoComp A base class for layer 3 protocol policies.          ├ bfd:AIfP             ├ bfd:AIfDef               ├ bfd:IfDef             ├ bfd:IfP           ├ bgp:AAsP The profile of an autonomous system (AS) is a set of routers under a single technical administration, using an interior gateway protocol (IGP) and common metrics to determine how to route packets within the AS, and using an inter-AS routing protocol to determine how to route packets to other autonomous systems.            ├ bgp:AsDef An internal object for the BGP autonomous system profile definition.            ├ bgp:AsP The BGP autonomous system profile information.          ├ bgp:AExtP The profile of an external BGP neighbor.            ├ bgp:ExtDef An internal object for the BGP external profile definition.            ├ bgp:ExtP When created, this profile indicates that IBGP will be configured for the endpoint groups in this external network.          ├ bgp:ALocalAsnP An abstraction of a local autonomous system (AS) information profile.            ├ bgp:LocalAsnDef The local autonomous system number (ASN) definition.            ├ bgp:LocalAsnP The local autonomous system information pertaining to a peer.          ├ bgp:APeerP The profile for connecting with a BGP peer.            ├ bgp:APeerDef  Peer connectivity definition              ├ bgp:InfraPeerDef  Infra Peer connectivity definition              ├ bgp:PeerDef An internal object for the BGP peer connectivity definition.            ├ bgp:InfraPeerP  Peer connectivity profile            ├ bgp:PeerP The BGP peer connectivity profile contains the peer IP address and defines the peer connectivity control settings. These values are for BGP routers, which can only exchange routing information when they establish a peer connection between them.          ├ bgp:ARRP  Abstract Route Reflector Profile            ├ bgp:ExtIntersiteRRP  External Intersite Route Reflector Profile            ├ bgp:ExtRRP  External Route Reflector Profile            ├ bgp:RRP The BGP route reflector profile information.          ├ eigrp:AExtP The abstraction of an EIGRP external profile.            ├ eigrp:ExtDef An EIGRP external profile definition.            ├ eigrp:ExtP The EIGRP external profile information.          ├ eigrp:AIfP The abstraction of an interface profile.            ├ eigrp:IfDef The EIGRP interface definition.            ├ eigrp:IfP The EIGRP interface profile, which enables EIGRP on the interface. Optionally, the EIGRP interface profile can have a relation to an EIGRP interface policy for more granular control over interface proprieties.          ├ hsrp:AGroupP  Hsrp Group Profile            ├ hsrp:AGroupDef               ├ hsrp:GroupDef             ├ hsrp:GroupP  Hsrp Group Profile          ├ hsrp:AIfP             ├ hsrp:AIfDef               ├ hsrp:IfDef             ├ hsrp:IfP           ├ hsrp:ASecVip  Abstract Secondary Address Policy            ├ hsrp:SecVip  Secondary Address Policy            ├ hsrp:SecVipDef           ├ isis:LvlComp Per-level IS-IS vrf information.          ├ l3ext:AIp The abstraction of a secondary IP address.            ├ l3ext:Ip A secondary IP address policy.            ├ l3ext:IpDef The definition of a secondary IP address policy.          ├ mgmt:AIp  Secondary interface connection parameters            ├ mgmt:Ip  Secondary interface connection parameters            ├ mgmt:IpDef  Secondary interface connection parameters definition          ├ ospf:AExtP An abstraction of the OSPF external profile.            ├ ospf:ExtDef The external definition profile.            ├ ospf:ExtP The OSPF external profile information.          ├ ospf:AIfP An abstraction of the OSPF interface profile information.            ├ ospf:IfDef The OSPF interface definition model.            ├ ospf:IfP The OSPF interface profile enables OSPF on the interface. Optionally, the OSPF interface profile can have a relation to an OSPF interface policy for more granular control over interface proprieties.          ├ pim:AIfP             ├ pim:IfP PIM interface policy.          ├ rtctrl:AAttrP The abstraction for a Set Action Rule Profile.            ├ rtctrl:AttrDef An attribute definition.            ├ rtctrl:AttrP The action rule profile, which specifies actions for events that meet a configured action rule.          ├ rtctrl:AMatchRule The abstraction for all match rules.            ├ rtctrl:AMatchCommFactor  Abstraction of Match Community Factor              ├ rtctrl:MatchCommFactor  Match Community Factor              ├ rtctrl:MatchCommFactorDef  Match Community Factor Definition            ├ rtctrl:AMatchCommRegexTerm  Abstraction Match Rule Based on Community Regular Expression              ├ rtctrl:MatchCommRegexTerm  Match Rule Based Route Regular Expression Community              ├ rtctrl:MatchCommRegexTermDef  Match Rule Based Route Regular Expression Community Definition            ├ rtctrl:AMatchCommTerm  Abstraction of Match Community Term              ├ rtctrl:MatchCommTerm  Match Community Term              ├ rtctrl:MatchCommTermDef  Match Community Term Definition            ├ rtctrl:AMatchIpRule The abstraction for all IP address based on match rules.              ├ ip:ARouteP An abstraction of route definitions.                ├ ip:RouteDef The route definitions, which are are used for pushing subnets and static routes to PE. They also push subnets under EpPD to VMMMGR (for configuring external networks in vCD).                ├ ip:RouteP Configure the IP address and next hop IP address for the routed outside network.              ├ rtctrl:MatchRtDest The match action rule based on the route destination.              ├ rtctrl:MatchRtDestDef The match route destination definition.              ├ rtctrl:MatchRtNh Match Rule based Route Next Hope              ├ rtctrl:MatchRtNhDef The match route next hop definition.              ├ rtctrl:MatchRtSrc The match rule based on a route source.              ├ rtctrl:MatchRtSrcDef The match route source definition.            ├ rtctrl:AMatchRtType The abstraction of a match rule based on the route type.              ├ rtctrl:MatchRtType The match rule based on a route type.              ├ rtctrl:MatchRtTypeDef The match route type definition.          ├ rtctrl:ASetASPathASN  Abstraction of AS Path ASN            ├ rtctrl:SetASPathASN  AS Path ASN            ├ rtctrl:SetASPathASNDef           ├ rtctrl:ASetRule The abstraction for all set action rules.            ├ rtctrl:ASetASPath  Abstraction of Set Action Rule based on AS Path              ├ rtctrl:SetASPath  Set rule based on AS Path              ├ rtctrl:SetASPathDef             ├ rtctrl:ASetComm The abstraction of a set action rule based on communities.              ├ rtctrl:SetAddComm               ├ rtctrl:SetAddCommDef               ├ rtctrl:SetComm The set action rule based on communities.              ├ rtctrl:SetCommDef The set community definition.            ├ rtctrl:ASetDamp  Set rule for dampening policy              ├ rtctrl:SetDamp  Set rule based on dampening              ├ rtctrl:SetDampDef             ├ rtctrl:ASetNh Sets the action rule based on a next hop address.              ├ rtctrl:SetNh Sets action rule based on the next hop address.              ├ rtctrl:SetNhDef The set next hop definition.            ├ rtctrl:ASetOspfFwdAddr The abstraction of set action rule based on the OSPF forwarding address.              ├ rtctrl:SetOspfFwdAddr The set rule based on the OSPF forwarding address.              ├ rtctrl:SetOspfFwdAddrDef The set OSPF forward address definition.            ├ rtctrl:ASetOspfNssa The abstraction of a set action rule based on OSPF-NSSA.              ├ rtctrl:SetOspfNssa The set rule based on the OSPF-NSSA.              ├ rtctrl:SetOspfNssaDef The set OSPF-NSSA definition.            ├ rtctrl:ASetPref Sets the action rule based on preference.              ├ rtctrl:SetPref The set action rule based on preference.              ├ rtctrl:SetPrefDef The set preference definition.            ├ rtctrl:ASetRtMetric Sets action rule based on a metric value.              ├ rtctrl:SetRtMetric The set action rule based on metric.              ├ rtctrl:SetRtMetricDef The set route metric definition.            ├ rtctrl:ASetRtMetricType Sets the action rule based on the metric type.              ├ rtctrl:SetRtMetricType The set action rule based on a metric type.              ├ rtctrl:SetRtMetricTypeDef The definition for a set action rule based on a metric type.            ├ rtctrl:ASetTag The abstraction of a set action rule based on the route tag.              ├ rtctrl:SetTag The set action rule based on route tag.              ├ rtctrl:SetTagDef The set tag definition.            ├ rtctrl:ASetWeight  Set rule for route weight              ├ rtctrl:SetWeight  Set rule based on dampening              ├ rtctrl:SetWeightDef           ├ rtctrl:ASubnet The abstraction of the external subnet.            ├ extnw:AInstPSubnet An abstraction of the instance profile subnet.              ├ l2ext:AInstPSubnet An abstraction of an external network instance.              ├ l3ext:AInstPSubnet An abstract logical node profile. This defines the characteristics to be applied to resources that match with the profile name.                ├ l3ext:Exception The exception from the external subnet.                ├ l3ext:Subnet The network visibility of the domain.                ├ l3ext:SubnetDef An internal object that represents subnets defined under an L3 outside.            ├ fv:BDSubnet             ├ fv:ImplSubnet An implied subnet.            ├ fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain.            ├ mgmt:AInstPSubnet The abstract instance profile subnet.              ├ mgmt:Subnet The external subnet to be imported. The bridge domain context defines a unique IP address space, which can consist of multiple subnets. Those subnets are defined in one or more bridge domains that reference the corresponding context.              ├ mgmt:SubnetDef The subnet definition.            ├ nd:RaSubnet Neighbor Discovery (ND) uses ICMPv6 messages known as Router advertisement (RA) messages, which have a value of 134 in the Type field of the ICMP packet header, are periodically sent out each configured interface of an IPv6 device. For stateless autoconfiguration to work properly, the advertised prefix length in RA messages must always be 64 bits.            ├ nd:RaSubnetDef An external subnet.            ├ orchs:TnSvcsSubnet  Represents default gateway of a BD          ├ rtdmc:AExtP             ├ pim:ExtDef OSPF external profile definition.            ├ pim:ExtP OSPF external profile.      ├ fabric:SetupP       ├ file:ARemoteHost Remote host with reachability information        ├ callhome:SmtpServer The hostname or IP for export destination. Call Home sends email messages to either the IP address or hostname, and the associated port number.        ├ file:ARemotePath Remote location for data import or export.          ├ file:RemotePath The remote destination path parameters for the data export.          ├ stats:DestP The export policy. The export policy enables you to output statistics collection policy reports in an XML or JSON format. The reports are exported at a specified frequency and to a chosen export destination. Specifying the export destination can require selecting the protocol used when communicating with a remote server and entering a hostname/IP address, a remote path, the username and password the system should use to log in to the remote s...        ├ snmp:TrapDest A destination to which traps and informs are sent.        ├ syslog:RemoteDest The syslog remote destination host enables you to specify syslog servers to which messages from the APIC and fabric nodes should be forwarded.      ├ firmware:Source The firmware source specifications including CCO, and any server (SCP, HTTP, FTP) in which Curl can extract files.        ├ firmware:CcoSource Cisco.com is the source of images.        ├ firmware:InternalSource The internal source of firmware images, which contains images that are pre-packaged into the controller.        ├ firmware:OSource An outside source of images, such as an HTTP or SCP server.        ├ vns:SvcPkgSource The services device package installer support for the CLI.      ├ fmcast:NodePEp The root of the multicast tree. Note that only the spine can be the root.      ├ fmcast:NumTree The number of multicast trees rooted on the node. For example, the number of multicast tree objects contained by the multicast tree root object .      ├ fmcast:TreeEp The multicast tree. This is an internal object that contains the tree number and is used for propagating tree information between the APIC and the nodes.      ├ fv:AIfConn         ├ fv:FcIfConn  Represents the FC If connectivity parametres        ├ fv:IfConn Connectivity parameters for an interface.      ├ fv:APodConnP  Abstract POD Connectivity Profile        ├ fv:PodConnP  POD Connectivity Profile        ├ fv:PodConnPDef  POD Connectivity Profile Definition      ├ fv:AREpPDomDefDependencyResolver       ├ fv:ASiteConnP  Abstract class for Multisite Connectivity Information        ├ fv:SiteConnP  Container for Local Multisite Connectivity Information for MultiSite deployments        ├ fv:SiteConnPDef  Container for Local Multisite Connectivity Information for MultiSite deployments      ├ fv:CepNetCfgPol  Represents Client End Point network configuration policy, Used this information for Microsoft SCVMM/Azure application to create SCVMM static IP pool      ├ fv:Comp An abstraction of the fabric virtualization policy definition.        ├ fv:ATg Base class for the Attachable Target Group          ├ fv:CCg A special endpoint group representing a set of connectivity rules to a compute container or hypervisor.          ├ fv:EPg A set of endpoints.            ├ extnw:EPg An abstraction of a policy controlling connectivity to an external network such as another fabric or WAN.              ├ l2ext:InstP The external network instance profile represents a group of external subnets that have the same security behavior. These subnets inherit contract profiles applied to the parent instance profile. Each subnet can also associate to route control profiles, which defines the routing behavior for that subnet.              ├ l3ext:InstP The external network instance profile represents a group of external subnets that have the same security behavior. These subnets inherit contract profiles applied to the parent instance profile. Each subnet can also associate to route control profiles, which defines the routing behavior for that subnet.              ├ l3ext:InstPDef The L4-L7 services route peering.            ├ fv:CEPg A set of hypothetical client endpoints attaching to the network.              ├ fv:AEPg A set of requirements for the application-level EPG instance. The policy regulates connectivity and visibility among the end points within the scope of the policy.              ├ fv:TnlEPg  qinq End Point Group              ├ vns:AEPpInfo                 ├ vns:EPpInfo Internal object to store encap info (vlan ID) for an endpoint.                ├ vns:REPpInfo                 ├ vns:SDEPpInfo                 ├ vns:SHEPpInfo             ├ infra:EPg Abstraction of an infrastructure endpoint group.              ├ infra:ACEPg An abstraction of the infrastructure client endpoint group. The client endpoint group represents a set of hypothetical client endpoints attaching to the network.                ├ dhcp:CRelPg A group of DHCP relay function providers: A set of DHCP Server to which client DHCP requests are relayed.                ├ infra:CEPg A base class for the client endpoint group.              ├ infra:APEPg An abstraction of the infrastructure provider endpoint group. The provider endpoint group represents a set of hypothetical provider endpoints attaching to the network; for example, a set of DHCP servers, fabric relays, or client requests.                ├ dhcp:PRelPg A group of DHCP Relay Function Providers: A set of DHCP Servers to which client DHCP Requests are relayed.                ├ infra:PEPg Ignore, removed            ├ mgmt:InB The in-band management endpoint group consists of switches (leaves/spines) and APICs. Each node in the group is assigned an IP address that is dynamically allocated from the address pool associated with the corresponding in-band management zone. The allocated IP address is then configured as the in-band management access IP address on the corresponding node. Any host that is part of another endpoint group can communicate with the nodes in the...          ├ mgmt:InstP The external management entity instance profile communicates with nodes that are part of out-of-band management endpoint group. To enable this communication, a contract is required between the instance profile and the out-of-band management endpoint group.          ├ mgmt:InstPDef The instance profile definition.          ├ mgmt:OoB An out-of-band management endpoint group, which consists of switches (leaves/spines) and APICs that are part of the associated out-of-band management zone. Each node in the group is assigned an IP address that is dynamically allocated from the address pool associated with the corresponding out-of-band management zone. The allocated IP address is then configured on the out-of-band management port of the corresponding node. Hosts that are par...        ├ vz:Any vzAny associates all endpoint groups (EPGs) in a context (fvCtx) to one or more contracts (vzBrCP), rather than creating a separate contract relation for each EPG. EPGs can only communicate with other EPGs according to contract rules. A relationship between an EPG and a contract specifies whether the EPG provides the communications defined by the contract rules, consumes them, or both. By dynamically applying contract rules to all EPGs in a conte...      ├ fv:Encap The encapsulation associated with the functions.      ├ fv:EncapDef An internal encapsulation definition. This is an internal object used for deployment of encapsulation.      ├ fv:EpPCtrctInfo       ├ fv:ExtLocaleCont A container for the extended fabric node information shared across all nodes.      ├ fv:L3extOutLblDepl  Container for Logical Outside Profile Deployment      ├ fv:PoolDef  POD Specific Ip Pool Definition      ├ fv:PrimaryEncapDef       ├ fv:PullREpPCont       ├ fv:QinqFabEncapDef       ├ fv:REpPCont Container for a remote endpoint profile.      ├ fv:SystemGIPoDef  System GIPo - one value across the whole fabric. Its used when sending multicast traffic across PODs. @@@ It is same as Infra BDs GIPo. It should work according to switch team @@@ Its sharded by the tenant infra's dn.      ├ fv:TepPoolDef  PODs TEP Pool Definition      ├ fv:VsanEncapDef       ├ fvns:AAddrBlk The abstraction of the IP address block.        ├ fvns:McastAddrBlk The multicast address block policy defines the multicast IP address ranges. These addresses can be used for various purposes, such as VxLAN encapsulation.        ├ fvns:McastAddrBlkDef The multicast address block definition.        ├ fvns:UcastAddrBlk Defines the first and last unicast IP addresses in the namespace block.      ├ fvns:AEncapBlk The abstraction of the encapsulation block.        ├ fvns:EncapBlk The VLAN encapsulation block.        ├ fvns:EncapBlkDef The encapsulation block definition.        ├ fvns:VsanEncapBlk         ├ topoctrl:EncapBlk The encap blocks.        ├ vns:EncapBlkDef       ├ geo:Building The building identifier where the node is located.      ├ geo:Floor The floor number of the building where the node is located.      ├ geo:Rack The rack identifier where the node is located.      ├ geo:Room The room name or number where the node is located.      ├ geo:Row The row name where the node is located.      ├ health:LevelP Represents the health score level policy.      ├ health:Pol Defines how much influence a child's health score has on its parent's health score.      ├ health:PolCont The health score policies container.      ├ hvs:Encap Contains the encap and multicast address of the ExtPol. If this child encap exists, the ExtPol uses this encap or the encap properties of the ExtPol.      ├ ident:AllocRule The identity allocation rule.      ├ ident:Block The base class for the ID block subclasses must have the From and To properties defined.        ├ ident:Block16 The identity block 16.        ├ ident:Block32 The identity block 32.        ├ ident:Block64 The identity block 64.        ├ ident:BlockIp The identity block Ip.      ├ igmp:AIfP         ├ igmp:IfP       ├ igmp:ASnoopAccessGroup  IGMP Snoop Access Group, defines a filter for the IGMP joins that can be accepted on a given port/encap or fvAEPg. This enable to perform a selective admission control on certain interfaces        ├ igmp:SnoopAccessGroup  Representation of an IGMP snooping filter        ├ igmp:SnoopAccessGroupDef  In case the filter will take place at the fvAEPg level For future releases Internal Representation of an IGMP snooping filter      ├ igmp:ASnoopStaticGroup  IGMP Snoop Static Group, it's used to allow a tenant admin to statically join a multicast stream on some port,encap or fvAEPG        ├ igmp:SnoopStaticGroup  Representation of an IGMP snooping static (*,G) or (S,G) membership        ├ igmp:SnoopStaticGroupDef  In case the static group membership is at the fvAEPg level For future releases Internal representation of the group memebership      ├ infra:AFunc The abstraction of a function or functions provided by the port selector.        ├ infra:Boot The hypervisor boot function provides the policies used for booting hypervisors. For example, the VLAN and endpoint group policies used during hypervisor bootup.        ├ infra:Generic The hypervisor generic function provides policies used for any generic hypervisor functionality. This can be used when any other pre-defined functions are not sufficient. The VLAN and endpoint group policies associated with this function are deployed on the leaf ports.        ├ infra:Image The port characteristics required for accessing storage. Note that this is only used for L2 storage.        ├ infra:Mgmt The Vcenter management connectivity. The Vcenter management encap is a regular VLAN.        ├ infra:PreProv         ├ infra:ProvAcc The provider access function is defined when the hypervisor is using an encapsulation protocol, such as VxLAN/NVGRE, and provides the policies to impacting VxLAN/NvGRE packets from NVGRE. You do not need to provide the encapsulation VLAN and endpoint for the provider access function. The system uses the Infra VLAN (provided during APIC bootup) as the encapsulation and associates it to the default endpoint group under the default tenant.        ├ infra:Storage The hypervisor storage function provides the policies used for hypervisors and virtual machines to access the storage network. For example, the VLAN and endpoint group policies.      ├ infra:ANode A node is a base class representing the node where the endpoint group will be deployed.        ├ fv:ANode  Abstract Node Definition @@@ Class for passing some internal node specific information between PM & PE          ├ fv:NodeDef  Node Definition @@@ Class for passing some internal node specific information between PM & PE        ├ infra:Node The node where the endpoint group will be deployed.        ├ infra:NodeDef A node definition.        ├ mgmt:ANodeDef           ├ mgmt:NodeDef The node definition.          ├ mgmt:StNodeDef         ├ mgmt:EffNodeDef       ├ infra:AttPolicyGroup The attachable policy group acts as an override of the policies given at the AccBaseGrp for the ports associated with the Attachable Entity Profile.      ├ infra:Encap The encaps associated with the functions.      ├ infra:EncapDef The encapsulation information. This object is generated and used only by internal processes.      ├ infrazone:Zone  Infrastructure Zone: Represents a policy deployment zone in the fabric. A zone consists of member nodes      ├ ip:ANexthopEpP  Abstratcion of Route definitions        ├ ip:NexthopEpP         ├ ip:NexthopEpPDef       ├ ip:ANexthopP An abstraction of route definitions.        ├ ip:NexthopDef The Nexthops for the static route.        ├ ip:NexthopP The Nexthop policy for the static route.      ├ ipmc:ASSMXlateP  Abstraction of SSM Translate        ├ igmp:SSMXlateDef  Context-level SSM Translate Definition        ├ igmp:SSMXlateP  Context-level SSM Translate Policy      ├ l2:Cons Used for reference counting the consumers corresponding to the RsPathDomAtt relation. Requirement from switch team: If an circuit is associated to port-x, then the BD should also get associated with the same port. This managed object is used for reference counting the circuit endpoints that need the BD-to-port association.      ├ l3:Cons  Represents a consumer of a resource.      ├ l3ext:AExtEncapAllocator An internal object for managing encap allocation for an external SVI.        ├ l3ext:CtxExtEncapAllocator  COntext External Encap Id Allocator        ├ l3ext:ExtEncapAllocator The external encap ID allocator.        ├ l3ext:ExtEncapDef The external encap definition.      ├ l3ext:AMember The member. The member is used for providing per node IP address configuration.        ├ l3ext:Member The member. The member is used for providing per node IP address configuration.        ├ l3ext:MemberDef The member definition. The member is used for providing per node IP address configuration. This is used internally.      ├ l3ext:AOutRefSrc  Policy Source L3 Out(Ref)        ├ l3ext:BgpPeerSrc  BGP Peer Policy Source L3 Out(Ref)        ├ l3ext:BgpPolSrc  BGP Role Policy Source L3 Out(Ref)        ├ l3ext:DampeningPolSrc  Dampening Policy Source L3 Out(Ref)        ├ l3ext:DefRtLeakCriteriaSrc  DefRtLeakCriteria Policy Source L3 Out(Ref)        ├ l3ext:DefRtLeakScopeSrc  DefRtLeakScope Policy Source L3 Out(Ref)        ├ l3ext:EigrpPolSrc  Ospf Role Policy Source L3 Out(Ref)        ├ l3ext:InterleakPolSrc  Interleak Policy Source L3 Out(Ref)        ├ l3ext:OspfAreaIdSrcRefs  Ospf Area ID Policy Source L3 Out(Ref) OutDns        ├ l3ext:OspfRoleSrc  Ospf Role Policy Source L3 Out(Ref)        ├ l3ext:RouterIdSrc  Router ID Policy Source L3 Out(Ref)      ├ l3ext:AOutRefSrcCont  Abstraction of Container for L3 Out Policy Sources ( L3 OutsRef )        ├ l3ext:BgpPeerSrcCont  Container for BGP Peer Sources ( L3 OutsRef )        ├ l3ext:BgpPolSrcCont  Container for BGP Policy Sources ( L3 OutsRef )        ├ l3ext:DampeningPolSrcCont  Dampening Policy Sources ( L3 OutsRef )        ├ l3ext:DefRtLeakCriteriaSrcCont  Container for DefRtLeakCriteria Sources ( L3 OutsRef )        ├ l3ext:DefRtLeakScopeSrcCont  Container for DefRtLeakScope Sources ( L3 OutsRef )        ├ l3ext:EigrpPolSrcCont  Per Adress Family Container for EIGRP Policy Sources ( L3 OutsRef )        ├ l3ext:InterleakPolSrcCont  Interleak Policy Sources ( L3 OutsRef )        ├ l3ext:OspfAreaIdSrc  Ospf Area ID Policy Source L3 Out(Ref)        ├ l3ext:OspfAreaIdSrcCont  Container for Ospf Area ID Sources ( L3 OutsRef )        ├ l3ext:OspfRoleSrcCont  Per Adress Family Container for Ospf Role Sources ( L3 OutsRef )        ├ l3ext:RouterIdSrcCont  Container for Router ID Sources ( L3 OutsRef )      ├ l3ext:DepPolState  L3 Outside Policy Reference      ├ l3ext:GlobalCtxName  Global VRF Name      ├ l3ext:GlobalCtxNameDef  Global VRF Name Definition      ├ l3ext:InfraNodeP  Infra Logical Node Profile      ├ l3ext:IntersiteLoopBackIfP  Intersite Loop Back Interface Profile      ├ l3ext:IntersiteLoopBackIfPDef  Intersite Loop Back Interface Profile Definition      ├ l3ext:LoopBackIfP The loopback interface profile.      ├ l3ext:LoopBackIfPDef       ├ l3ext:OutRef The Layer 3 outside policy reference.      ├ mgmt:AZone The managed node zone.        ├ mgmt:InBZone The in-band management zone.        ├ mgmt:OoBZone The out-of-band zone.      ├ mon:ATarget The base monitoring target policy model.        ├ mon:Target The base monitoring target policy model.          ├ mon:EPGTarget Creating a monitoring target will allow you to associate certain monitoring policies to the target object for this tenant. These associated policies can be related to stats collection, stats export, Callhome/SNMP/Syslog, event severities, fault severities, and fault lifecycle policies. The target object will be found in the Monitoring Object drop-down menu in the sub-folders of this monitoring policy, if available.          ├ mon:FabricTarget The monitoring target policy model for the fabric semantic scope.          ├ mon:InfraTarget Creating a monitoring target will allow you to associate certain monitoring policies to the target object for the fabric infrastructure. These associated policies can be related to stats collection, stats export, Callhome/SNMP/Syslog, event severities, fault severities, and fault lifecycle policies. The target object will be found in the Monitoring Object drop-down menu in the sub-folders of this monitoring policy, if available.      ├ mon:ExportP The export data policy for a given user.        ├ stats:ExportP The export policy, which enables you to output statistics collection policy reports in an XML or JSON format. The reports are exported at a specified frequency with an option for gzip file compression.      ├ mon:Group The monitoring group.        ├ callhome:Group Call Home provides an email-based notification for critical system policies. A range of message formats are available for compatibility with pager services or XML-based automated parsing applications. You can use this feature to page a network support engineer, email a Network Operations Center, or use Cisco Smart Call Home services to generate a case with the Technical Assistance Center.        ├ snmp:Group The SNMP destination group contains information needed to send traps or informs to a set of destinations.. SNMP is an application-layer protocol that provides a message format for communication between SNMP managers and agents. SNMP provides a standardized framework and a common language used for the monitoring and management of devices in a network.        ├ syslog:Group The syslog destination group contains all information required to send syslog messages to a group of destinations.      ├ mon:ProtoP The objects in the hierarchy under mon:Pol (Policy, Target Subjects, ...) that define scopes for monitoring activities, including statistics reporting and notification dispatching. To enable notification dispatching, a user attaches a mon:Src object under the object with the desired scope. The source provides an association to a group, which contains all the information needed to dispatch notifications to a set of destinations using a specifie...        ├ callhome:Prof Contains all site information and the address of the SMTP server used to send emails.        ├ syslog:Prof Represents the configuration parameters used for this protocol.      ├ mon:SecAuthP The Security/Authorization profile.      ├ mon:Src Acts as a tap: place it under another mon managed object to start funnelling events to the destinations in the group using the specified profiles and credentials. Note that the creation of Fault/Event/Audit record managed objects happens independently of the presence of an Src.        ├ callhome:Src The call home source profile determines the information to deliver and the urgency level for sending email-based alert notifications to a call home destination. A range of message formats are available for compatibility with pager services or XML-based automated parsing applications. You can use this feature to page a network support engineer, email a Network Operations Center, or use Cisco Smart Call Home services to generate a case with the Te...        ├ snmp:Src The SNMP source profile determines the fault information, severity level, and destination for sending messages to the SNMP destination. SNMP is an application-layer protocol that provides a message format for communication between SNMP managers and agents. SNMP provides a standardized framework and a common language used for the monitoring and management of devices in a network .        ├ syslog:Src The syslog source configures a syslog source that specifies the minimum severity of items to be sent as syslog messages to the syslog servers in the destination group.      ├ mon:Subj An abstract object that identifies a scope within a target. Reaction to conditions (fault/events) are examples of scopes that can be captured with a Subj MO.        ├ condition:CondP Represents a base class for policies on conditions within a given scope.          ├ condition:SevAsnP             ├ event:SevAsnP Represents a policy that specifies the initial and target severity for a specific event.            ├ fault:SevAsnP The initial and target severities for a specific fault can be specified in a custom or default monitoring policy directly under an observable target object.          ├ fault:LcP The fault lifecycle policy specifies the timer intervals of faults in their lifecycle. This policy can be specified in a common, default, or custom monitoring policy. Custom and default monitoring policies can be applied globally, per monitoring object or to a group of monitoring objects.      ├ monitor:Destination The span destination information.        ├ monitor:ERDest The ERSPAN destination information.        ├ monitor:LocalDest The local span destination information.      ├ monitor:Session The monitor session definition. There can only be a few sessions active at a given time (with a maximum of 4).      ├ monitor:Source The sources to be monitored.      ├ nws:ASrc  Firewall logging policies        ├ nws:ASyslogSrc  Abstract Syslog Source for Firewall. Contains configuration parameters for syslog functionality of the firewall device and a relation to the syslog group, which contains the list of destination servers          ├ nws:SyslogSrc  Policy providing a concrete implementation of a syslog source for a firewall.          ├ nws:SyslogSrcDef  Read-only instance of syslog source for a firewall. Intended for internal use.      ├ pim:RouteMapDefWrapper  PIM Route Map DEF wrapper      ├ planner:ATmpl  A named template        ├ planner:ADomainTmpl  Base class for domain templates          ├ planner:AzureDomainTmpl  Azure Domain Template          ├ planner:VmwareDomainTmpl  Vmware Domain Template        ├ planner:AEpgDomain  Base class for epg domain          ├ planner:AzureDomain  Azure Domain          ├ planner:PhysDomain  Phys Domain          ├ planner:VmwareDomain  Vmware Domain        ├ planner:AObject  An enuemrable object template          ├ planner:AEpg  Abstract Epg base class            ├ planner:EpgTmpl  Epg template            ├ planner:L2OutTmpl  L2Out template            ├ planner:L3OutTmpl  L3Out template        ├ planner:BdTmpl  BD template        ├ planner:ContractTmpl  Contract template        ├ planner:GraphTmpl  Grapth template        ├ planner:L4L7ClusterTmpl  L4L7 Cluster template        ├ planner:VrfTmpl  VRF template      ├ planner:FexTmpl  Fex Tmpl      ├ planner:LeafTmpl  Leaf Template      ├ planner:SpineTmpl  Spine Template      ├ planner:TenantTmpl  Tenant template      ├ qos:ABuffer The buffer policy holder describes the minimum guaranteed packet buffer reservations. These are applied per class currently in the system.        ├ qos:Buffer The buffering information of a class, such as the minimum buffer required for a class. This is applied at system level        ├ qosp:Buffer The buffering information of a class, such as the minimum buffer required for a class, which is applied at system level.      ├ qos:ACong An abstraction of a congestion management policy holder. This object describes congestion algorithms and ECN information. These are applied at a per class today in the system.        ├ qos:Cong The congestion algorithm and ECN information of a class. This is applied at system level        ├ qosp:Cong A container for the congestion policy. This container holds information that describes the congestion parameters of the class such as ECN, WRED, and Tail-drop. These congestion parameters are applied at per class-level in the system.      ├ qos:AQueue An abstraction of a queue management policy holder. This object describes the queue threshold parameters, such as management method, limits, etc. These are applied at a per class today in the system.        ├ qos:Queue The queuing information, such as the limit and queuing method. This is applied at system level.        ├ qosp:Queue A container for the queue management policy. This container holds information that describes the queue threshold parameters, such as the management method, which are applied at a per-class basis in the system.      ├ qos:ASched An abstraction of a schedule policy holder. This object describes the minimum guaranteed packet buffer reservations. These are applied at a per class today in the system.        ├ qos:Sched The information about the scheduling parameter of the class. This object has the scheduling method and bandwidth parameter and is applied at system level.        ├ qosp:Sched A container for the schedule policy. This container holds information that describes the bandwidth and scheduling algorithm (Strict priority or WRR), which are applied at a per-class basis in the system.      ├ qos:Classification An abstract class for dot1p and DSCP classification rules.        ├ qos:ADot1PClass An abstraction of a dot1P class.          ├ qos:Dot1PClass The class level for dot1P to prioritize the map.          ├ qos:Dot1PClassDef The definition class to be attached to the endpoint profile. Note that this is an internal object.        ├ qos:ADscpClass An abstraction of a DSCP class.          ├ qos:DscpClass The class level for DSCP to prioritize the map.          ├ qos:DscpClassDef The definition class to be attached to the endpoint profile. Note that this is an internal object.      ├ qosp:PrioFlowCtrl       ├ rtctrl:CtxP The context policy, which is a unique layer 3 forwarding and application policy domain. The context defines a layer 3 address domain.      ├ rtctrl:Scope The route context Scope. The scope defines the node on which the policy is deployed.      ├ rtctrl:SubjDef The subject definition.      ├ rtctrl:SubjP The subject profile.      ├ rtdmc:AFilterPol  Abstraction of Filter Policy        ├ ipmc:ARepPol  Report Policy          ├ igmp:RepDef           ├ igmp:RepPol         ├ ipmc:AStRepPol  Static Report Policy          ├ igmp:StRepDef           ├ igmp:StRepPol         ├ ipmc:AStateLPol  State Limit          ├ igmp:StateLDef           ├ igmp:StateLPol         ├ rtdmc:ABSRFilter           ├ pim:BSRFilterDef The PIM Bootstrap Router (BSR) filter definition.          ├ pim:BSRFilterPol The PIM Bootstrap Router (BSR) filter policy.        ├ rtdmc:AJPFilterPol  Interface Join-PruneFilter Policy          ├ pim:JPInbFilterDef Interface-level inbound join/prune filter definition.          ├ pim:JPInbFilterPol Interface-level inbound join/prune filter policy.          ├ pim:JPOutbFilterDef Interface-level outbound join/prune filter definition.          ├ pim:JPOutbFilterPol Interface-level outbound join/prune filter policy.        ├ rtdmc:AMAFilter           ├ pim:MAFilterDef PIM MA filter definition.          ├ pim:MAFilterPol Mapping agent (MA) filter policy.        ├ rtdmc:ANbrFilterPol  Interface Neighbor Filter Policy          ├ pim:NbrFilterDef Interface-level neighbor filter definition.          ├ pim:NbrFilterPol Interface-level neighbor filter policy.        ├ rtdmc:ARPGrpRangePol           ├ pim:RPGrpRangeDef Specifies if RP multicast group range definition.          ├ pim:RPGrpRangePol Specifies if RP multicast group range policy.        ├ rtdmc:ARegTrPol           ├ pim:RegTrDef PIM register traffic policy definition          ├ pim:RegTrPol PIM register traffic policy        ├ rtdmc:AResPol           ├ pim:ResDef PIM resource policy definition          ├ pim:ResPol PIM resource policy        ├ rtdmc:ASGRangeExpPol  Abstraction of (S,G) expiry policy          ├ pim:SGRangeExpDef The (S,G) expiry definition.          ├ pim:SGRangeExpPol The (S,G) range expiry policy.        ├ rtdmc:ASSMRangePol  Abstraction of SSM group range policy          ├ pim:SSMRangeDef Source-specific group range definition          ├ pim:SSMRangePol Source-specific group range policy        ├ rtdmc:ASharedRangePol  Abstraction of shared tree policy          ├ pim:SharedRangeDef Shared tree definition          ├ pim:SharedRangePol Shared tree group range policy      ├ rtdmc:APatPol  Abstraction of Multicast Pattern policy        ├ rtdmc:AASMPatPol  Abstraction of Any Source Multicast Pattern policy          ├ pim:ASMPatDef The any-source multicast pattern definition.          ├ pim:ASMPatPol The any-source multicast pattern policy.        ├ rtdmc:ABidirPatPol  Abstraction of Bidirectional Multicast Pattern policy          ├ pim:BidirPatDef  Bidirectional Multicast Pattern definition          ├ pim:BidirPatPol  Not configurable until feature is ready - Bidirectional Multicast Pattern policy        ├ rtdmc:ASSMPatPol  Abstraction of Source Specific Multicast Pattern policy          ├ pim:SSMPatDef Source-specific multicast pattern definition          ├ pim:SSMPatPol Source-specific multicast pattern policy      ├ rtdmc:ARPPol  Abstraction of Multicast RP policy        ├ rtdmc:AAutoRPPol  Abstraction of Multicast AutoRP policy          ├ pim:AutoRPDef The Auto-RP PIM definition.          ├ pim:AutoRPPol The Auto-RP policy.        ├ rtdmc:ABSRPPol  Abstraction of Multicast Bootstrap RP policy          ├ pim:BSRPDef The Bootstrap Router (BSR) policy definition.          ├ pim:BSRPPol The Bootstrap Router (BSR) policy.        ├ rtdmc:AStaticRPPol  WILL BE EXPOSED/IMPEMENTED in a future release          ├ pim:StaticRPDef Static RP PIM definition          ├ pim:StaticRPPol Static RP PIM policy      ├ rtdmc:ARtMapEntry  Route Map Entry        ├ pim:RouteMapEntry PIM route map entry        ├ pim:RouteMapEntryDef PIM route map entry definition      ├ rtdmc:AStaticRPEntry         ├ pim:StaticRPEntryDef PIM MA filter definition        ├ pim:StaticRPEntryPol Static RP entry policy      ├ snmp:AClientGrpP An abstract representation of a client group profile.        ├ snmp:ClientGrp A client group is a group of client IP addresses that allows SNMP access to routers or switches.        ├ snmp:ClientGrpP A client group is a group of client IP addresses that allows SNMP access to routers or switches.      ├ snmp:ACommunityP An abstract representation of a community profile.        ├ snmp:CommSecP A security profile using a community string match for authentication.        ├ snmp:CommunityP The SNMP community profile enables access to the router or switch statistics for monitoring. SNMP is an application-layer protocol that provides a message format for communication between SNMP managers and agents. SNMP provides a standardized framework and a common language used for the monitoring and management of devices in a network.      ├ snmp:AUserP An abstract representation of a user profile.        ├ snmp:UserP The SNMP user profile is used to associate users with SNMP policies for monitoring devices in a network. SNMP is an application-layer protocol that provides a message format for communication between SNMP managers and agents. SNMP provides a standardized framework and a common language used for the monitoring and management of devices in a network.        ├ snmp:UserSecP An authentication profile using user names.      ├ span:ASource The abstraction of a SPAN source. A SPAN source is where traffic is sampled. A SPAN source can be an endpoint group (EPG), one or more ports, or port traffic filtered by an EPG (Access SPAN), a Layer 2 bridge domain, or a Layer 3 context (Fabric SPAN). When you create a traffic monitoring session, you must select a SPAN source and a SPAN destination. The type of session (Tenant, Access or fabric) determines the allowed types of SPAN sources and d...        ├ span:FabSource The fabric source port (also called a monitored port), which is a switched port that you monitor for network traffic analysis. In a single local SPAN session, you can monitor source port traffic such as received (Rx), transmitted (Tx), or bidirectional (both). The switch supports any number of source ports (up to the maximum number of available ports on the switch).        ├ span:Source The SPAN or ERSPAN source, which is where traffic is sampled. A source can be an endpoint group (EPG), one or more ports, or port traffic filtered by an EPG (Access SPAN), a Layer 2 bridge domain, or a Layer 3 context (Fabric SPAN). When you create a traffic monitoring session, you must select a source and a destination. The type of session (Tenant, Access, or Fabric) determines the allowed types of sources and destinations. The destination can b...      ├ span:Destination The SPAN destination, which is where network traffic is sent for analysis by a network analyzer. A SPAN destination can be local or remote (ERSPAN). When you create a traffic monitoring session, you must select a SPAN source and a SPAN destination. The type of session (Tenant, Access, or Fabric) determines the allowed types of SPAN sources and destinations. The destination can be either a port or an endpoint group. If the destination is a port, i...        ├ span:ERDestination The ERSPAN destination, which is where network traffic is sent for analysis by a network analyzer. When you create a traffic monitoring session, you must select an ERSPAN source and ERSPAN destination. The type of session (Tenant, Access, or Fabric) determines the allowed types of ERSPAN sources and destinations. The destination can be either a remote port or endpoint group. If the destination is a port, it should not be one that has been config...        ├ span:LDestination The local SPAN destination, which is where network traffic is sent for analysis by a network analyzer. When you create a traffic monitoring session, you must select an local SPAN source and destination. The type of session (Tenant, Access, or Fabric) determines the allowed types of local SPAN sources and destinations. The destination can be either a port or endpoint group. If the destination is a port, it should not be one that has been configur...      ├ span:Session A local SPAN session is an association of a destination port with source ports. You can monitor incoming or outgoing traffic on a series or range of ports.      ├ stats:AColl A superclass that configures collection rules according to the granularity of the statistics.        ├ stats:Coll The collection configuration policy, which configures the collection policy according to the granularity of the statistics.. This is also a container for threshold policies for the statistic granularity.        ├ stats:HierColl The statistics collection policy, which enables you to determine how often the system collects data and to specify how far back in time data should be collected.      ├ stats:AExportJob A superclass for the export job status of statistical data.        ├ stats:ExportJob The model for the holding status of an export job for statistical data.        ├ stats:ShardExportSubJob       ├ stats:AThrP The superclass for the statistical threshold policy. Subclasses represent export policies for specific data types.        ├ stats:ThrDoubleP The concrete statistical threshold policy for a double data type.        ├ stats:ThrFloatP The concrete statistical threshold policy for a float data type.        ├ stats:ThrSByteP The concrete statistical threshold policy for a signed byte data type.        ├ stats:ThrSint16P The concrete statistical threshold policy for a 16-bit signed Int data type.        ├ stats:ThrSint32P The concrete statistical threshold policy for a 32-bit signed Int data type.        ├ stats:ThrSint64P The concrete statistical threshold policy for a 64-bit signed integer data type.        ├ stats:ThrTriggerP The concrete statistical threshold policy for a trigger counter type.        ├ stats:ThrUByteP The concrete statistical threshold policy for an unsigned byte data type.        ├ stats:ThrUint16P The concrete statistical threshold policy for a 16-bit unsigned Int data type.        ├ stats:ThrUint32P The concrete statistical threshold policy for a 32-bit unsigned Int data type.        ├ stats:ThrUint64P The concrete statistical threshold policy for a 64-bit unsigned integer data type.      ├ stats:Reportable A statistics policy container, which contains statistic collections and export policies for different types of statistics.      ├ stp:AllocEncapBlkDefDependencyResolver       ├ stp:DomFabCons       ├ stp:DomFabEncap       ├ stp:EncapSegIdPair The table created at the node for efficient lookups of the spanning tree flooding segment ID. This table is created from the spanning-tree protocol encap block definition for allocated IDs and the base segment ID used for the range pushed by IFC.      ├ svccore:CoreState       ├ syslog:Console A console terminal.      ├ syslog:DestState       ├ syslog:FacilityFilter       ├ syslog:File A local file.      ├ syslog:LogMsg       ├ syslog:SystemMsgP       ├ trig:Executable The container for executable policies.        ├ callhome:InvP The call home inventory policy is used to send Call Home messages with system inventory information.        ├ config:ABackupP The abstract backup policy.          ├ config:ExportP A configuration export policy is used to backup the system configuration.          ├ config:ImportIdP           ├ config:ImportP A configuration import policy specifies how to import a fabric configuration file.          ├ config:RollbackP           ├ config:SnapshotMgrP         ├ config:DumpP         ├ dbgexp:ExportP The data export policy creates an archive containing configuration information, logs and diagnostic data that will help TAC with troubleshooting and resolving a technical issue. This is an abstract class for technical support and core policies.          ├ dbgexp:CoreP The core policy provides a core file report containing data about the system and the component at the time of the failure.          ├ dbgexp:TechSupODev  Techsupport export for ODev          ├ dbgexp:TechSupOnDBase  TechSupport export on demand            ├ dbgexp:TechSupOnD The on-demand tech support policy creates an archive containing configuration information, logs and diagnostic data that will help TAC with troubleshooting and resolving a technical issue.            ├ dbgexp:TechSupVmm  Techsupport export for Vmm hypervisor          ├ dbgexp:TechSupP A tech support policy creates an archive containing configuration information, logs and diagnostic data that will help TAC with troubleshooting and resolving a technical issue.        ├ maint:AMaintP The maintenance policy specifies when and how maintenance takes place.          ├ maint:CatMaintP The catalog maintenance policy specifies when catalog maintenance takes place.          ├ maint:CtrlrMaintP The controller maintenance policy specification describes when and how maintenance takes place.          ├ maint:MaintP The maintenance policy determines the pre-defined action to take when there is a disruptive change made to the service profile associated with the node or set of nodes.          ├ maint:MaintPOnD The On Demand Maintenance policy specification for the node, which describes when and how maintenance takes place.        ├ recovery:ReconcileConfigP         ├ troubleshoot:Session  ****************** MOs *********************      ├ tunnel:Cons  tunnel:Cons: Used for reference counting the consumers responsible for creation of this tunnel      ├ ui:SettingsCont       ├ useg:DomainCont  Container For all EPg and UsegEPg in a given Domain      ├ useg:UsegEPgDefCont       ├ vns:ALDevCtx The logical device context.        ├ vns:LDevCtx A device cluster context points to the device cluster used to pick a specific device based on contract, subject, and function label or names. To specify a wild card, set the name to Any.        ├ vns:LDevHint Contains hints for the device cluster that must be picked for a specific node of a graph that belongs to a specific subject of a specific contract. In the absence of this hint in an abstract graph, a match for a device cluster context will be done based on the name of the contract, subject, and node. If that fails, a match will be made by wildcarding: the contract followed by the contract, and the subject followed by the contract, subject, and no...      ├ vns:ALIfCtx The logical interface context.        ├ vns:LIfCtx The logical interface context points to the logical interface used to pick a specific logical interface based on the connector name. To specify a wild card, set the name to Any.        ├ vns:LIfHint Contains hints for the logical interface that must be picked for a specific connector of a graph that belongs to the selected device cluster. The device cluster is selected based on device cluster hint.        ├ vns:LIfHintInst       ├ vns:ATerm A terminal.        ├ vns:InTerm An input terminal node. For abstract graphs (AbsGraph), InTerm refers to the terminal node at the input end.        ├ vns:OutTerm An output terminal node. For abstract graphs (AbsGraph), OutTerm refers to the terminal node at the output end.      ├ vns:CtrlrMgmtPol The management policy for the controller appliance IP address.      ├ vns:FltInst The representation of a whitelist filter that needs to be applied on a particular endpoint group.      ├ vns:OrchReq  normalized parameters from orchestrator        ├ vns:EPGExtRequest         ├ vns:FWReq         ├ vns:LBReq           ├ vns:LBIPReq           ├ vns:LBRNatReq           ├ vns:LBVSvcGrpSvrReq           ├ vns:LBVSvrReq         ├ vns:NATReq           ├ vns:NATDynPATReq           ├ vns:NATPATReq       ├ vns:RedirectDest       ├ vpc:KAPol The keepalive policy.      ├ vz:AFiltEntry An abstraction of a filter entry. A filter entry is a combination of network traffic classification properties.        ├ actrl:Entry The filter entry in the system, which is a unique set of classification filters identified by l4 parameters.        ├ vz:Entry A filter entry is a combination of network traffic classification properties.        ├ vz:RFltE A remote filter entry. A filter entry is a combination of network traffic classification properties. Note that this relation is an internal object.      ├ vz:ASubj The abstraction of a subject. A subject represents a sub application running behind an endpoint group. For example, an exchange server or a firewall.        ├ 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:TSubj The subjects for a service contract represents a sub-application running behind an endpoint group, such as an exchange server. A subject is parented by the contract.      ├ vz:ATerm The abstraction of a terminal.        ├ vz:ASTerm An abstraction of a subject terminal.          ├ vz:InTerm An input terminal node. For abstract graphs, this is the terminal node at the input end.          ├ vz:OutTerm An output terminal node. For abstract graphs, this is the terminal node at the output end.      ├ vz:AllocateSharedService Allocate shared service.      ├ vz:AnyDef       ├ vz:AnyGroupDef       ├ vz:AnyREpPCont       ├ vz:GlobalPcTagRequest       ├ vz:GlobalPcTagRequestCont  Container of all the requests for allocating global PcTag      ├ vz:PcTagCons       ├ vz:ResPcTag