Fabric Leaf Interface Profile

Leaf Interface Profiles can either be auto-generated, one per leaf, by providing a naming convention or can be defined explicitly. In case of auto-generated profiles the following placeholders can be used when defining the naming convention:

• \\g<id>: gets replaced by the respective leaf node ID
• \\g<name>: gets replaced by the respective leaf hostname

Location in GUI: Fabric » Fabric Policies » Interfaces » Leaf Interfaces » Profiles

Diagram

Classes

apic

Name	Type	Constraint	Mandatory	Default Value
auto_generate_switch_pod_profiles	Boolean	true, false	No	false
auto_generate_fabric_leaf_switch_interface_profiles	Boolean	true, false	No	false

fabric_policies (apic)

Name	Type	Constraint	Mandatory	Default Value
leaf_interface_profile_name	String	min: 1, max: 64	No	LEAF\g<id>
leaf_interface_profiles	List	[leaf_interface_profiles]	No

nodes (apic.node_policies)

Name	Type	Constraint	Mandatory	Default Value
id	Integer	min: 1, max: 4000	Yes
name	String	Regex: ^[a-zA-Z0-9_.:-]{1,64}$	No

leaf_interface_profiles (apic.fabric_policies)

Name	Type	Constraint	Mandatory	Default Value
name	String	Regex: ^[a-zA-Z0-9_.:-]{1,64}$	Yes
expected_state	Class	[expected_state]	No

expected_state (apic.fabric_policies.leaf_interface_profiles)

Name	Type	Constraint	Mandatory	Default Value
minimum_health	Integer	min: 0, max: 100	No
maximum_critical_faults	Integer	min: 0	No
maximum_major_faults	Integer	min: 0	No
maximum_minor_faults	Integer	min: 0	No

Examples

Auto-generate profiles:

apic:
  auto_generate_switch_pod_profiles: true
  fabric_policies:
    leaf_interface_profile_name: "LEAF\\g<id>"

Explicitly configured profiles:

apic:
  fabric_policies:
    leaf_interface_profiles:
      - name: LEAF1001