Class fabric:ProtoPol (ABSTRACT)

Class ID:695
Encrypted: false - Exportable: true - Persistent: true - Configurable: true - Subject to Quota: Disabled - Abstraction Layer: Concrete Model - APIC NX Processing: Disabled
Write Access: []
Read Access: [admin]
Creatable/Deletable: derived (see Container Mos for details)
Possible Semantic Scopes: 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:Def, Sub Mos: fabric:IntfPol, fabric:L2ProtoPol, fabric:L3ProtoPol, fabric:ProtoDomPol, fabric:ProtoIfPol, fabric:ProtoInstPol, lbp:Pol,

Inheritance

naming:NamedObject An abstract base class for an object that contains a name.  ├ pol:Obj Represents a generic policy object.    ├ pol:Def Represents self-contained policy document.      ├ fabric:ProtoPol A base class for protocol policies.        ├ fabric:IntfPol An abstraction of the interface policy.          ├ fabric:HIfPol The host interface policy specifies the layer 1 parameters of host facing ports.        ├ fabric:L2ProtoPol A base class for layer 2 protocol policies.        ├ fabric:L3ProtoPol A base class for layer 3 protocol policies.          ├ bgp:APeerPfxPol The abstraction of a peer prefix policy.            ├ bgp:PeerPfxPol The peer prefix policy defines how many prefixes can be received from a neighbor and the action to take when the number of allowed prefixes is exceeded. This feature is commonly used for external BGP peers, but can also be applied to internal BGP peers.          ├ bgp:ARtTarget  Abstraction of BGP Route Target            ├ bgp:RtTarget  BGP Route Target            ├ bgp:RtTargetDef  BGP Route Target Definition          ├ bgp:ARtTargetInstrP  Abstracttion of BGP Route Target Instrumentation Profile            ├ bgp:RtTargetInstrP  BGP Route Target Instrumentation Profile            ├ bgp:RtTargetInstrPDef  BGP Route Target Instrumentation Profile Definition          ├ bgp:ARtTargetP  Abstraction of BGP Route Target Profile            ├ bgp:AutoRtTargetPDef  BGP Automatic Route Target Profile Definition            ├ bgp:RtTargetP  BGP Route Target Profile            ├ bgp:RtTargetPDef  BGP Route Target Profile Definition          ├ coop:Pol The COOP policy contains groups of Oracles nodes and COOP repositories.          ├ l3ext:AFabricExtRoutingP  Abstraction of Fabric External Routing Profile            ├ l3ext:FabricExtRoutingP  Fabric External Routing Profile            ├ l3ext:FabricExtRoutingPDef  Fabric External Routing Profile Definition          ├ l3ext:ARouteTagPol The route tag policy.            ├ l3ext:RouteTagDef Definition of Route Tag Policy            ├ l3ext:RouteTagPol A route tag is used to assign a number to identify the policy.        ├ fabric:ProtoDomPol A base class for context-level protocol policies.          ├ fabric:L2DomPol A base class for layer 2 context-level policies.            ├ fv:AEpRetPol Abstract of an endpoint retention policy.              ├ fv:EpRetDef An endpoint retention definition.              ├ fv:EpRetPol The endpoint retention policy provides the parameters for the lifecycle of the endpoints.            ├ igmp:ASnoopPol Restricts flooding of multicast traffic by sending multicast traffic only to the bridge domains that are subscribed to a particular multicast group.              ├ igmp:SnoopDef The process of listening to Internet Group Management Protocol (IGMP) network traffic. The feature allows a network switch to listen in on the IGMP conversation between hosts and routers. By listening to these conversations the switch maintains a map of which links need which IP multicast streams.              ├ igmp:SnoopPol The IGMP snooping policy streamlines multicast traffic handling for VLANs. By examining (snooping) IGMP membership report messages from interested hosts, multicast traffic is limited to the subset of VLAN interfaces on which the hosts reside.            ├ mld:ASnoopPol  MLD Snoop policy Per BD              ├ mld:SnoopDef The process of listening to Multicast Listener Discovery (MLD) network traffic. The feature allows a network switch to listen in on the IGMP conversation between hosts and routers. By listening to these conversations the switch maintains a map of which links need which IP multicast streams.              ├ mld:SnoopPol The MLD snooping policy streamlines multicast traffic handling for VLANs. By examining (snooping) MLD membership report messages from interested hosts, multicast traffic is limited to the subset of VLAN interfaces on which the hosts reside.          ├ fabric:L3DomPol A base class for layer 3 context-level policies.            ├ fabric:L3CtxPol A base class for layer 3 context-level policies.              ├ bgp:ACtxAfPol The BGP address family context policy.                ├ bgp:CtxAfDef The BGP address family context definition.                ├ bgp:CtxAfPol               ├ bgp:ACtxPol The context-level BGP policy.                ├ bgp:CtxDef An internal object for the BGP context-level policy definition.                ├ bgp:CtxPol The BGP timers policy uses timers to control periodic activities such as the frequency keepalive messages that are sent to its peer, the amount of time the system waits to declare a peer dead after keepalive messages stop being received, and the amount of time before restarting a dead peer. The BGP timer policy enables you to specify the intervals for the periodic activities and supplies two options for graceful restart control: the graceful rest...                ├ bgp:NodeCtxDef  Node-level bgp definition              ├ eigrp:ACtxAfPol The abstraction of the context-level EIGRP policy, which contains the configuration for an address family on a context on the node. The EIGRP policy is configured under the tenant protocol policies and can be applied to one or more contexts (private domains) under the tenant. The EIGRP context policy can be enabled on a context through a relation in the context per address family. If there is no relation to a given address family, or the EIGRP c...                ├ eigrp:CtxAfDef The context-level EIGRP address family definition.                ├ eigrp:CtxAfPol An EIGRP context policy can be applied on one or more contexts under the tenant. EIGRP context policies can be enabled on a context through a relation in the context per address family. If there is no relation to a given address family such as IPv6 or the EIGRP context policy mentioned in the relation doesn't exist, then the default context policy created under Tenant Common will be used for that address family.              ├ hsrp:AGroupPol  hsrp group abstraction policy                ├ hsrp:GroupPol  Hsrp Group Policy              ├ ipmc:ACtxPol  Abstraction of Context-level Routed Multicast policy                ├ igmp:CtxDef  Context-level IGMP definition                ├ igmp:CtxP  Context-level IGMP policy              ├ ospf:ACtxPol The OSPF policy information.                ├ ospf:CtxDef The context-level OSPF definition.                ├ ospf:CtxDefAf The context-level OSPF definition per address family.                ├ ospf:CtxPol The context-level OSPF timer policy provides the Hello timer and Dead timer intervals configuration.              ├ rtdmc:ACtxPol  Abstraction of Context-level Routed Multicast policy                ├ pim:CtxDef Context-level PIM definition.                ├ pim:CtxP Context-level PIM policy.                ├ pim:IPV6CtxDef  Context-level PIM definition                ├ pim:IPV6CtxP  Context-level PIM policy            ├ isis:DomPol The domain policy is used to configure IS-IS domain specific properties.        ├ fabric:ProtoIfPol A base class for interface-level protocol policies.          ├ fabric:L1IfPol             ├ stormctrl:IfPol The storm control interface policy. A traffic storm occurs when packets flood the LAN, creating excessive traffic and degrading network performance. You can use the traffic storm control feature to prevent disruptions on ports by a broadcast, multicast, or unknown unicast traffic storm on physical interfaces.          ├ fabric:L2IfPol A base class for layer 2 interface-level policies.            ├ cdp:AIfPol The CDP Interface Policy parameters. CDP is primarily used to obtain protocol addresses of neighboring devices and discover the platform of those devices. CDP can also be used to display information about the interfaces your router uses. CDP is media- and protocol-independent, and runs on all Cisco-manufactured equipment including routers, bridges, access servers, and switches.              ├ cdp:IfPol The CDP interface policy, which is primarily used to obtain protocol addresses of neighboring devices and discover the platform of those devices. CDP can also be used to display information about the interfaces your router uses. CDP is media- and protocol-independent, and runs on all Cisco-manufactured equipment including routers, bridges, access servers, and switches.              ├ cdp:IfPolDef The read only copy of CDP interface policy.            ├ copp:IfPol  Per interface per protocol CoPP policy            ├ copp:ProtoClassP             ├ dwdm:AOptChnlIfPol  Abstract class for all the profiles for DWDM C optic channel that can be applied              ├ dwdm:FabIfPol               ├ dwdm:IfPol DWDM policy that can be applied at interface level            ├ extdev:SDWanPolCont  SDWAN policy Container            ├ fc:IfPol  interface FC policy            ├ l2:IfPol             ├ l2:LoadBalancePol             ├ l2:PortAuthPol             ├ lacp:ALagPol The abstract LACP policy definition.              ├ lacp:LagPol The PortChannel policy enables you to bundle several physical ports together to form a single port channel. LACP enables a node to negotiate an automatic bundling of links by sending LACP packets to the peer node.              ├ lacp:LagPolDef Read-only copy of LACP policy.            ├ lacp:IfPol The PortChannel interface policy defines a common configuration that will apply to one or more LACP interfaces.            ├ lldp:AIfPol A summary of the interface policy. We recommend you include information about where and when the policy should be used. The abstraction can be up to 128 characters.              ├ lldp:IfPol The LLDP interface policy, which defines a common configuration that will apply to one or more LLDP interfaces. LLDP uses the logical link control (LLC) services to transmit and receive information to and from other LLDP agents.              ├ lldp:IfPolDef Read-only copy of the LLDP interface policy.            ├ macsec:AAIfPol  Abstraction of MACSEC Interface Policy              ├ macsec:AIfPol  Access MACSEC Policy                ├ macsec:IfPol  Infra MACSEC Policy              ├ macsec:FabIfPol  Fabric MACSEC Infra Policy            ├ macsec:AAKeyChainPol  MACSEC Abstract KeyChain Policy              ├ macsec:AKeyChainPol  MACSEC Access Abstract KeyChain Policy                ├ macsec:KeyChainPol  MACSEC KeyChain Policy            ├ macsec:AAKeyPol  MACSEC Abstract Key Policy              ├ macsec:AKeyPol  MACSEC Access Abstract Key Policy                ├ macsec:KeyPol  MACSEC Key Policy            ├ macsec:AAParamPol  Abstraction of MACSEC Interface Policy              ├ macsec:AParamPol  MACSEC Parameters Policy                ├ macsec:ParamPol  MACSEC Access Parameters Policy              ├ macsec:FabParamPol  MACSEC Fab Parameter Policy            ├ mcp:AIfPol               ├ mcp:IfPol             ├ netflow:AFabExporterPol Abstarct Fabric Netflow Exporter              ├ netflow:AExporterPol  Abstract Netflow Exporter                ├ netflow:ExporterPol  Exporter information for bootstrapping the netflow Collection agent                ├ netflow:ExporterPolDef  Define the Netflow Exporter Policy MO which contains internal information needed to program the leaf              ├ netflow:VmmExporterPol               ├ netflow:VmmExporterPolDef  Read only copy of VMM Netflow Exporter policy            ├ netflow:AMonitorPol               ├ netflow:MonitorPol               ├ netflow:MonitorPolDef  Define the Netflow Monitor Policy MO which contains internal information needed to program the leaf            ├ netflow:ARecordPol  Abstract Flow Record              ├ netflow:RecordPol  Flow Record              ├ netflow:RecordPolDef  Define the Netflow Record Policy MO which contains internal information needed to program the leaf            ├ poe:AIfPol  Abstraction of POE Interface Policy              ├ poe:IfPol  POE Interface Policy            ├ qos:ADppPol  Define a Data Plane Policing policy. User is supposed to use this in scenarios where the incoming traffic need to be policed to certain levels              ├ qos:DppPol  Define a Data Plane Policing policy. User is supposed to use this in scenarios where the incoming traffic need to be policed to certain levels              ├ qos:DppPolDef  Define the Data Plane Policing MO which contains internal information needed to program the leaf            ├ stp:AIfPol An abstraction of an spanning-tree protocol interface policy. This is applicable to leaf ports and n1000v distributed virtual switches. Extended chassis ports have BPDU guard filter enabled by default.              ├ stp:IfPol The Spanning-Tree Protocol (STP) interface policy defines a common configuration that will apply to one or more interfaces. STP prevents loops from being formed when the interfaces are interconnected via multiple paths. Spanning-Tree Protocol implements the 802.1D IEEE algorithm by exchanging BPDU messages with other switches to detect loops, and then removes the loop by shutting down selected bridge interfaces. This algorithm guarantees that th...              ├ stp:IfPolDef The read-only copy of the spanning-tree protocol interface policy.          ├ fabric:L2PortSecurityPol             ├ l2:PortSecurityPol  Port Security Policy            ├ l2:PortSecurityPolDef  Port Security Policy          ├ fabric:L3IfPol A base class for layer 3 interface-level policies.            ├ arp:AIfPol  This object holds arp information that is operated at a interface level              ├ arp:IfPol               ├ arp:IfPolDef             ├ bfd:AIfPol  Interface-level bfd abstraction policy              ├ bfd:IfPol  Interface-level bfd policy            ├ cloudsec:IfPol  Internal Mo for Cloudsec Policy            ├ eigrp:IfPol The EIGRP interface policy, which defines a common configuration that will apply to one or more EIGRP interfaces.            ├ hsrp:AIfPol  Interface-level hsrp abstraction policy              ├ hsrp:IfPol  Interface-level hsrp policy            ├ ipmc:AIfPol  Interface-level ipmc policy              ├ igmp:IfDef               ├ igmp:IfPol  Interface-level IGMP policy            ├ l3:IfPol  L3 Interface Policy            ├ nd:AIfPol The neighbor discovery interface policy defines a common configuration that will apply to one or more neighbor discovery interfaces.              ├ nd:IfPol The neighbor discovery interface policy defines a common configuration that will apply to one or more neighbor discovery interfaces.              ├ nd:IfPolDef The read only copy of the neighbor discovery interface policy.            ├ nd:APfxPol The neighbor discovery prefix policy.              ├ nd:PfxPol The neighbor discovery prefix policy.              ├ nd:PfxPolDef The neighbor discovery prefix policy definition.            ├ ospf:IfPol The OSPF interface-level policy information.            ├ rtdmc:AIfPol  Interface-level rtdmc-SM policy              ├ pim:IfDef PIM interface definition.              ├ pim:IfPol Interface-level PIM-SM (sparse mode) policy.            ├ rtdmc:AIfPolCont  Interface-level rtdmc              ├ rtdmc:IPV6McastIfDefCont  Interface Policy Container              ├ rtdmc:McastIfDefCont  Interface Policy Container            ├ rtdmc:ARtMapPol  Route Map Policy              ├ pim:RouteMapDef PIM route map definition              ├ pim:RouteMapPol PIM route map policy          ├ fabric:L4IfPol             ├ nws:AFwPol  Firewall Policy Definition              ├ nws:FwPol               ├ nws:FwPolDef  read only copy of lacp policy          ├ fabric:QinqIfPol         ├ fabric:ProtoInstPol A base class for instance-level protocol policies.          ├ dns:AProfile The DNS Profile.            ├ dns:Prof The DNS instance information.            ├ dns:Profile The DNS profile defines a set of DNS providers and can be deployed to a switch for tenant contexts. To deploy a DNS profile on a switch, the appropriate label has to be defined for the context deployed on switch.          ├ dnsepg:ADomain  DNS Abstract Domain            ├ dnsepg:Domain  DNS Domain          ├ dnsepg:ZoneDB  DNS Zone DB          ├ dnsepg:ZoneEntry  DNS Zone Entry          ├ fabric:L2InstPol A base class for layer 2 interface-level policies.            ├ cdp:InstPol Specifies the node-level CDP policy.            ├ edr:ErrDisRecoverPol The error disabled recovery policy specifies the policy for re-enabling a port that was disabled due to one or more pre-defined error conditions.            ├ ep:ControlP  Endpoint Control Policy            ├ ep:IpAgingP             ├ ep:LoopProtectP The endpoint loop protection policy specifies how loops detected by frequent mac moves are handled.            ├ fc:FabricPol             ├ fc:InstPol             ├ l2:AInstPol A fabric-wide L2 policy.              ├ l2:InstPol The Layer 2 instance policy is used for configuring fabric-wide layer 2 settings. Currently, this policy contains only fabric MTU and management MTU configuration.              ├ l2:InstPolDef A read-only copy of the fabric MTU policy.            ├ l2:NodeAuthPol             ├ lldp:InstPol The node level LLDP policy.            ├ mcp:InstPol             ├ poe:InstPol  Node level poe policy            ├ span:ADest The abstraction of an SPAN destination. The SPAN destination 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...              ├ span:AVDest The abstraction of a VSPAN destination. The VSPAN destination is where network traffic is sent for analysis by a network analyzer. A VSPAN destination can be local or remote (VERSPAN). When you create a traffic monitoring session, you must select a VSPAN source and a VSPAN destination. The type of session (Tenant, Access, or Fabric) determines the allowed types of VSPAN sources and destinations. The destination can be either a port or an endpoint...                ├ span:VDest The VSPAN destination is where network traffic is sent for analysis by a network analyzer. A VSPAN destination can be local or remote (VERSPAN). When you create a traffic monitoring session, you must select a VSPAN source and a VSPAN destination. The type of session (tenant, access, or fabric) determines the allowed types of VSPAN sources and destinations. The destination can be either a port or an endpoint group. If the destination is a port, it...                ├ span:VDestDef The VLAN-based SPAN (VSPAN) destination definition.              ├ span:Dest The SPAN destination 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, it shoul...            ├ span:ASrcGrp The abstraction of a SPAN source group. The SPAN source group can contain a group of SPAN sources, which is where network 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 group and a SPAN destination. The type of session (Tenan...              ├ span:SrcGrp The SPAN source group can contain a group of SPAN sources. A SPAN source is where network 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 group and a SPAN destination. The type of session (Tenant, Access, or Fabric) determines...              ├ span:SrcGrpDef The SPAN source group definitions. The 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 an...            ├ span:AVDestGrp The abstraction of a VSPAN destination group. The VSPAN destination group can contain a group of VSPAN destinations. A VSPAN destination is where network traffic is sent for analysis by a network analyzer. A VSPAN destination can be local or remote (VERSPAN). When you create a traffic monitoring session, you must select a VSPAN source and a VSPAN destination. The type of session (Tenant, Access, or Fabric) determines the allowed types of VSPAN so...              ├ span:VDestGrp The VSPAN destination group contains a group of VSPAN destinations. A VSPAN destination is where network traffic is sent for analysis by a network analyzer. A VSPAN destination can be local or remote (VERSPAN). When you create a traffic monitoring session, you must select a VSPAN source and a VSPAN destination. The type of session (tenant, access, or fabric) determines the allowed types of VSPAN sources and destinations. The destination can be ei...              ├ span:VDestGrpDef VSPAN destination group used for configuring VSPAN source group definitions.            ├ span:AVSrcGrp The abstraction of a VSPAN source group. The VSPAN source group can contain a group of VSPAN sources. A VSPAN source is where network traffic is sampled. A VSPAN source can be an endpoint group (EPG), one or more ports, or port traffic filtered by an EPG (Access VSPAN), a Layer 2 bridge domain, or a Layer 3 context (Fabric VSPAN). When you create a traffic monitoring session, you must select a VSPAN source group and a VSPAN destination. The type ...              ├ span:VSrcGrp The VSPAN source group can contain a group of VSPAN sources. A VSPAN source is where network traffic is sampled. A VSPAN source can be an endpoint group (EPG), one or more ports; or port traffic filtered by an EPG (access VSPAN), a Layer 2 bridge domain, or a Layer 3 context (fabric VSPAN). When you create a traffic monitoring session, you must select a VSPAN source group and a VSPAN destination. The type of session (tenant, access, or fabric) de...              ├ span:VSrcGrpDef The VSPAN source group definition.            ├ span:DestGrp The SPAN destination group contains a group of SPAN destinations. A SPAN destination 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 p...            ├ span:SpanProv The SPAN destination provider is used for configuring SPAN destination provider parameters.            ├ span:SrcTargetShadow The SPAN source to EPG information.            ├ span:SrcTargetShadowBD The SPAN source to bridge domain (BD) information.            ├ span:SrcTargetShadowCtx The SPAN source to Ctx information.            ├ span:SrcTargetShadowL3If  Holds span src to l3 itnerface related information            ├ span:TaskParam The SPAN source to EPG task information.            ├ span:VSpanProv The VSPAN destination provider is used for configuring VSPAN destination provider parameters.            ├ stp:InstPol The spanning Tree Protocol (STP) instance policy, which enables you to set the bridge protocol data unit (BPDU) guard policy or filter. BDPUs are packets that run the STP protocol. The specification for STP is IEEE 802.1D. The main purpose of STP is to ensure that you do not create loops when you have redundant paths in your network. Loops are deadly to a network.            ├ vpc:InstPol The node-level vPC domain policy, which is used to specify a vPC domain and is applied to both vPC peer devices, the vPC peer keepalive link, the vPC peer link, and all the PortChannels in the vPC domain connected to the downstream device. You can have only one vPC domain ID on each device.          ├ fabric:L3InstPol A base class for layer 3 instance-level policies.            ├ bfd:AInstPol  Global BFD policy              ├ bfd:Ipv4InstPol               ├ bfd:Ipv6InstPol             ├ bgp:InstPol The BGP Instance level policy is used to configure MP-BGP policies inside the fabric.            ├ dhcp:ARelayP The abstract DHCP Relay profile, which is used for configuring relay parameters per bridge domain (BD).              ├ dhcp:RelayP The DHCP relay profile, with one or more helper addresses in it, configures a DHCP relay agent for forwarding DHCP packets to a remote server.          ├ fabric:UtilInstPol A base class for policies.            ├ psu:InstPol The power redundancy policy is for all power supply units on the fabric nodes (leaves and spines) that are consuming the power supply policy through their respective selector profile policy.          ├ fabric:VxlanInstPol             ├ l4:AVxlanInstPol               ├ l4:VxlanInstPol               ├ l4:VxlanInstPolDef           ├ twamp:ResponderPol TWAMP Responder Policy.          ├ twamp:ServerPol  Node level TWAMP policy        ├ lbp:Pol The load balancing policy options for balancing traffic among the available uplink ports. Static hash load balancing is the traditional load balancing mechanism used in networks where each flow is allocated to an uplink based on a hash of its 5-tuple. This load balancing gives a distribution of flows across the available links that is roughly even. Usually, with a large number of flows, the even distribution of flows results in an even distributi...

childAction

Type: mo:ModificationChildAction
Primitive Type: scalar:Bitmask32

Units: null
Encrypted: false
Access: implicit
Category: TopLevelChildAction

Delete or ignore. For internal use only.

descr

Type: naming:Descr
Primitive Type: string:Basic

Like: naming:Described:descr
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "128"
        Allowed Chars:
            Regex: [a-zA-Z0-9\\!#$%()*,-./:;@ _{|}~?&+]+

Specifies a description of the policy definition.

dn

Type: reference:BinRef

Units: null
Encrypted: false
Access: implicit
Category: TopLevelDn

A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module.

name

Type: naming:Name
Primitive Type: string:Basic

Overrides:naming:NamedObject:name

Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "64"
        Allowed Chars:
            Regex: [a-zA-Z0-9_.:-]+

null

nameAlias

Type: naming:NameAlias
Primitive Type: string:Basic

Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "63"
        Allowed Chars:
            Regex: [a-zA-Z0-9_.-]+

NO COMMENTS

ownerKey

Type: naming:Descr
Primitive Type: string:Basic

Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "128"
        Allowed Chars:
            Regex: [a-zA-Z0-9\\!#$%()*,-./:;@ _{|}~?&+]+

The key for enabling clients to own their data for entity correlation.

ownerTag

Type: naming:Descr
Primitive Type: string:Basic

Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "64"
        Allowed Chars:
            Regex: [a-zA-Z0-9\\!#$%()*,-./:;@ _{|}~?&+]+

A tag for enabling clients to add their own data. For example, to indicate who created this object.

rn

Type: reference:BinRN

Units: null
Encrypted: false
Access: implicit
Category: TopLevelRn

Identifies an object from its siblings within the context of its parent object. The distinguished name contains a sequence of relative names.

status

Type: mo:ModificationStatus
Primitive Type: scalar:Bitmask32

Units: null
Encrypted: false
Access: implicit
Category: TopLevelStatus

The upgrade status. This property is for internal use only.