ACI Fabric Access Policies Part 4: Leaf Interface Profile, Leaf Switch Policy Group, and Leaf Switch Profile,

Leaf Interface Profile

 

This section explains how to create an object Interface Profile whose basic purpose is to attach the set of physical interfaces into this object. Phase 6 in Figure 1-40 illustrates the APIC Management Information Model (MIM) from the Interface Profile perspective. We are adding an object L101__102_IPR under the class AccPortP (Leaf Interface Profile). The name of the object includes Leaf switch identifiers (Leaf-101 and Leaf-102) in which I am going to use this Interface Profile. This object has a Child object Eth1_1-5 (class InfraHPorts) that defines the internet block and which has a relationship with the object Port_Std_ESXi-Host_IPG. By doing this we state that ethernet interfaces 1/1-5 are LLDP enabled 10Gbps ports which can use VLAN Identifiers from 300-399. Note that in this phase we haven’t yet specified in which switches we are using this Interface Profile.

 The RN rules used with related objects:

 Objects created under the class InfraAccportP (Leaf Interface Profile):Prefix1-{name}, where the Prefix1 is “accportprof”. This gives us RN “accportprof-L101_L102_IPR”.

 Objects created under the class InfraHPortS (Access Port Selector): Prefix1-{name}-Prefix2-{type}, where the Prefix1 is “hports” and the Prefix2 is “typ”. This gives us RN “hports-Eth1_1-5_typ-range”.

Objects created under the class InfraPortBlk (Access Port Block): Prefix1-{name}, where the Prefix1 is “portblk” and where the name is Property (autogenerated). This gives us the RN “portblk-Block2”.

Figure 1-39: APIC MIM Reference: Interface Profile.

Creating Interface Profile by using REST API

 

Figure 1-40 shows the REST call POST URL and JSON payload. The object L101-L102-IPR belongs to the class InfraAccPortP. It also Child object Eth1_5-5 (class infraHportS) which has Child object block2 and relationship with the object accportgrp-Port_Std_ESXi_Host_IPG.

The REST API call URL is:

“[url prefix]/uni/infra/funcprof/accportgrp-Port_Std_ESXi_Host_IPG.json”. 

Figure 1-40: REST API: Creating Interface Profile.

Creating Interface Profile by using APIC GUI

 

Navigate to the Fabric page and select Access Policies. Navigate to the sub-folder “Interface > Leaf Interface > Profiles” in the Policies folder-tree. Click the tools icon in Leaf Interfaces – Profiles window to create a new Interface Profile.

Figure 1-41: Interface Profile Configuration: Phase-1.

 

Name the Policy as  L101_L102_IPR and click the Plus sign in the Interface Selectors bar.

Figure 1-42: Interface Profile Configuration: Phase-2.

 

Name the Interface Selector as Eth_1-5 and selects the interface from 1/1 to 1/5. Select the object Port_Std_ESXi_Host (10Gbps and LLDP) from the Interface Policy Group drop-down menu. By clicking the Expand icon you can check the object properties. When ready, click Ok.

Figure 1-43: Interface Profile Configuration: Phase-3.

 

Click the Submit button on the Create Leaf Interface Profile window.

Figure 1-44: Interface Profile Configuration: Phase-3.

Figure 1-45 shows that we have created a Leaf Interface Profile L101_L102_IPR and include interfaces 1/1-5.

Figure 1-45: Interface Profile Configuration: Verification.

 

Leaf Switch Policy Group

 

This section explains how to create an object  Leaf Switch Policy Group that defines switch policies about STP, BFD, PoE, FC, and so on. Phase 9 in Figure 1-46 illustrates the APIC Management Information Model (MIM) from the Leaf Switch Policy Group perspective. We are adding an object Default_SPG under the class InfraAccessNodePGRP (Access Switch Policy Group). All values in this object have left in their default settings, so that is why I have named it as Deaful_SPG. The RN rule is Prefix1-{name}, where the Prefix1 is accnodepgrp. This gives us RN accnodepgrp-Default_SPG.

Figure 1-46: APIC MIM Reference: Access Switch Policy Group.

Creating Interface Policy Group by using REST API

 

Figure 1-47 shows the REST call POST URL and JSON payload. The object Default_SPG belongs to the class InfraAccNodePGrp. The REST API call URL is:

“[url prefix]/uni/infra/funcprof/accnodepgrp-Default_SPG.json”. 

Figure 1-47: REST API: Creating Interface Policy Group.

 

Creating Interface Policy Group by using APIC GUI

 

Navigate to the Fabric page and select Access Policies. Navigate to the sub-folder “Switches > Leaf Switches> Policy Groups” in the Policies folder-tree. Click the tools icon in Leaf Interfaces – Policy Group window to create a new Switch Policy Group. 

Figure 1-48: Switch Policy Group Configuration: Phase-1.

 

The name of the Switch Policy Group is Default_SPG and all settings are left to their default values. Click the Submit button.

Figure 1-49: Switch Policy Group Configuration: Phase-2.

 

Figure 1-50 shows that the Defaut_SPG is now under the Policy Group sub-folder.

Figure 1-50: Switch Policy Group Configuration: Verification.

Leaf Switch Profile

This section explains how to create an object Leaf Switch Profile that (a) selects one or more switches, (b) attach a Switch Policy Group (STP, BFD, etc.) to selected switches, and (c) attach the Leaf Interface Policy into these switches. Phase 10 in Figure 1-51 illustrates the APIC Management Information Model (MIM) from the Leaf Switch Profile perspective. We are adding an object L-101-L102 under the class infraNodeP (Leaf Profile). The name of the object includes Leaf switch identifiers (Leaf-101 and Leaf-102) in which I am going to attach this Leaf Profile.

 

This object has a Child object Leaf_101-Leaf_102 (class InfraLeafS) which in turn has a Child object fdb713407ce5c1fd (class InfraNodeBlk) that eventually defines switches that are attached to Switch Profile L-101-L102. The object Leaf_101-Leaf_102 has a relationship with Default_SPG (class infra AccNodePGrp) that specifies the STP, BFD, etc to use with the switches participating in Switch Profile L-101-L102.  

 

The object L-101-L102 (class infraNodeP) has a relationship with the Leaf Interface Profile object L101_L102_IPR. This is the glue where we attach physical interfaces and their settings (speed, LLDP, VLAN range) to.

 

The RN rules used with related objects:

 

Objects created under the class InfraNodeP (Leaf Profile):

Prefix1-{name}, where the Prefix1 = “nprof”. This gives us RN “nprof-L-101_L102_”.

 

Objects created under the class InfraLeafS (leafS):

Prefix1-{name}, where Prefix1 = “leaves”. This gives us RN “leaves-Leaf_101-Leaf_102”.

 

Objects created under the class InfraNodeBlk (Node Block):

Prefix1-{name}, where the Prefix1 is “nodeblk”. This gives us the RN “nodeblk- fdb713407ce5c1fd”.

 

 

At this point, the Fabric Access Policy is done. As a summary, what we achieved with it: Interfaces from 1/1  to 1/5 in Leaf switches L101 and L102 are 10Gbps, LLDP enabled interfaces where we can attach VLAN Id from 300 to 399.

Figure 1-51: APIC MIM Reference: Switch Profile.

Creating Interface Policy Group by using REST API

 

The objects and their Paren-Child model and relationship are shown in figure 1-52. 

Figure 1-52: REST API: Creating Switch Profile.

Creating Interface Policy Group by using APIC GUI

 

Navigate to the Fabric page and select Access Policies. Navigate to the sub-folder “Switches > Leaf Switches> Profiles” in the Policies folder-tree. Click the tools icon in Leaf Interfaces – Profiles window to create a new Switch Profile. 

Figure 1-53: Switch Profile Configuration: Phase-1.

 

Give the name to the object and associate Leaf switches L101 and L102 by selecting the object Leaf_101-Leaf_102. Click Next.

Figure 1-54: Switch Profile Configuration: Phase-2.

 

In the Create Leaf Profile: Association click Plus sign in the Interface Selector Profiles bar and select the object L101_L102_IPR. 

Figure 1-55: Switch Profile Configuration: Phase-3.

 

We can see the Switch Profile we just created under Profiles Sub-Folder.

Figure 1-56: Switch Profile Configuration: Verification.

 

Figure 1-57 summarizes the GUI based configuration tasks.

Figure 1-57: Fabric Access Policy Summary.