The Create new interface window appears.

• When you create a port channel through Nexus Dashboard Fabric Controller, add interfaces of the same speed. A port channel that is created from interfaces of varying speeds won’t come up. For example, a port channel with two 10 Gigabit Ethernet ports is valid. However, a port channel with a 10-Gigabit Ethernet + 25-Gigabit Ethernet port combination isn’t valid.

• To add vPC hosts, you must designate vPC switches in the fabric topology and deploy vPC and peer-link configurations using the Save Deploy option. After the vPC pair configurations are deployed, it appears in the Select a vPC pair drop-down box.

  You can create a vPC using the int_vpc_trunk_host policy.

• When adding a subinterface, you must select a routed interface from the interface table before clicking the Add button.

• You can preprovision Ethernet interfaces in the Interface window. This preprovisioning feature is supported in Easy, eBGP, and External fabrics. .

• After preprovision the Ethernet interface you can preprovision subinterface on a physical interface.

Devices are listed based on the fabric and interface type.. In the case of vPC or Active to Active FEX, select the vPC switch pair.

You can override this value. The new value is used only if it’s available in the Resource Manager pool. Else, it results in an error.

The field only lists the Interface Python Policy with tag interface_edit_policy and filtered based on the interface type.

You must not create a _upg interface policy. For example, you shouldn’t create a policy using the vpc_trunk_host_upg, port_channel_aa_fex_upg, port_channel_trunk_host_upg, and trunk_host_upg options.

The fields vary according to the interface type you choose.

From Cisco NDFC Release 12.1.2e, you can set Native Vlan for the interface which has int_trunk_host or int_port_channel_trunk_host, or int_vpc_trunk_host policy template.

A trunk port can carry nontagged packets simultaneously with tagged packets. When you assign a default port VLAN ID to the trunk port, all untagged traffic travels on the default port VLAN ID for the trunk port, and all untagged traffic is assumed to belong to this VLAN. This VLAN is referred to as the native VLAN ID for a trunk port. That is, the native VLAN ID is the VLAN that carries untagged traffic on trunk ports.

Only saved configurations are pushed to the device. While adding the interface, you can only modify the policy attribute after the first save. If you try to use an ID that is already used, you encounter the Resource could not be allocated error.

The newly added interface appears in the screen.

Breakout and Un-Breakout: You can break out and unbreakout an interface by using the Breakout and Un-Breakout options.

You can break out and unbreak out an interface by using the breakout option in the Actions menu.

Select corresponding check boxes for editing multiple interfaces. You cannot edit multiple port channels and vPC. You cannot edit interfaces of different types at the same time.

The variables that are shown in the Edit interface window are based on the template and its policy. Select the appropriate policy. Save the policy and deploy the same. This window lists only Interface Python Policy with the tag interface_edit_policy and filtered based on the interface type.

In a vPC setup, the two switches are in the order the switch names are displayed in the edit window. For example, if Switch Name is displayed as LEAF1:LEAF2, then Leaf1 is peer switch one and Leaf2 is peer switch two.

During overlay network deployment on switches, the network can be associated with trunk interfaces. The trunk interface to network association is reflected in the Interfaces tab. You can update such interfaces.

For interface policies that are not created from the LAN > Interfaces > Interfaces screen, you can edit some configurations but not change the policy itself. The policy and fields that cannot be edited are grayed out.

The following are some examples of policies that cannot be edited:

• Loopback interface policies - The int_fabric_loopback policy is used to create a loopback interface. You can edit the loopback IP address and description but not the int_fabric_loopback policy instance.

• Fabric underlay network interface policies (int_fabric_num, for example) and fabric overlay network interface (NVE) policies.

• Policies associated with port channels and member ports of port channels, including the port channels and member ports associated with a vPC.

• SVIs created during network and VRF creation. The associated VLANs appear in the interfaces list.

You cannot delete logical interfaces created in the fabric underlay.

A confirmation window appears where you can save, preview, and deploy the changes. Click Save to preview of deploy the changes.

A confirmation window appears where you can save, preview, and deploy the changes. Click Save to preview or deploy the changes.

Select the interface whose configurations you want to view and click Actions > More > Show commands.

For Show commands, you must have corresponding show templates for interface or interface sub types like port channel or vPC, defined in the Templates.

After you deploy the interface configuration, the interface status information is updated. However, the overall switch-level state may be in the pending state, which is in blue. The overall switch-level state goes to the pending state whenever there is a change in intent from any module, such as interface, link, policy template update, top-down, or so on. In the pending state, a switch may have pending configurations or switch-level recomputation. The switch-level recomputation occurs when:

• You deploy for the switch

• During a deploy

• During hourly sync

An interface group name can have a maximum length of 64 characters

From Cisco NDFC Release 12.1.2e, a new Policy field is introduced in the Create new interface group window. You can add a shared policy to the interface group which can be shared by the interfaces existing in that group. Shared Policy is optional, for upgrades, all the existing interface group will not have a policy.

.

If you have already created an interface group, select it from the Select Interface Group drop-down list. Also, if an interface is already part of an interface group, you can move it to a different interface group by selecting the new group from the Select Interface Group drop-down list.

You can create interface groups from either the Interfaces Groups window or the Interfaces window under Fabric Overview.

In the Interfaces window, you can see the interface group name under the Interface Group column.

A dialog box pops up asking whether you want to clear all the associated interfaces. Click Yes to proceed. Note that if there are any networks attached to these interfaces, they are detached as well when you click Clear.

• Select an existing interface group from the Select Interface Group drop-down list and click Save.

  For example, you select three networks and the interface group test, and click the Save button, the following operations are performed in the background:

  1. Nexus Dashboard Fabric Controller retrieves interfaces that are part of the interface group test.

  2. Nexus Dashboard Fabric Controller determines that three networks are added to the interface group test. Therefore, it autoattaches these networks to all the interfaces that are part of the interface group test.

  3. For each interface, Nexus Dashboard Fabric Controller pushes the “switchport trunk allowed vlan add xxxx” command three times for each selected network.

     Note	Nexus Dashboard Fabric Controller ensures that there’s no duplicate configuration intent.

  If you click the Clear button, Nexus Dashboard Fabric Controller pushes “switchport trunk allowed vlan remove xxx’ config intent.

• Create a custom interface group by entering an interface group name in the Select Interface Group field and click Create new interface group. Click Save.

  If you choose this option, make sure to add interfaces to this Interface Group in the Interfaces window. As a result, Nexus Dashboard Fabric Controller performs the following operations:

  1. Removes all existing overlay networks that don’t belong to the interface group from these interfaces.

  2. Adds new overlay networks to these interfaces that are part of the interface group but not yet attached to these interfaces.

     For more information about associating interfaces to interface groups, see Creating an Interface Group.

Under the Overlay Network column, you can see the detached network in the red color for the corresponding interface. Click the network to view the expected config that is struck through.