FabricPath Configuration Guide, Cisco DCNM for LAN, Release 6.x
FabricPath Switching
Downloads: This chapterpdf (PDF - 457.0KB) The complete bookPDF (PDF - 1.69MB) | Feedback

Configuring FabricPath Switching

Table Of Contents

Configuring FabricPath Switching

Information About FabricPath Switching

FabricPath Encapsulation

FabricPath Headers

Forwarding Tags (FTags)

Default IS-IS Behavior with FabricPath

Conversational MAC Address Learning

Switching Using FabricPath

Conflict Resolution and Optional FabricPath Tunings

Interoperation between the M Series and the F Series Modules

High Availability

Licensing Requirements for FabricPath Switching

Platform Support

Enabling or Disabling FabricPath Feature Set Using DCNM

Configuring FabricPath Tunings Using DCNM (Optional)

Configuring the Switch ID

Configuring the FabricPath Timers

Disabling and Enabling Graceful Merges

Forcing the Links to Come Up

Displaying Conflict Information

Displaying FTag Information

Field Descriptions for FabricPath Optional Configurations

Resources: Resources Details: Switch ID Settings Section

Resources: Resources Details: Conflict Information Section

Resources: FTAG Status: FTAG Status Section

Feature History for Configuring FabricPath Switching Using the DCNM


Configuring FabricPath Switching



Note You must have an F Series module installed in your Cisco Nexus 7000 Series chassis in order to run FabricPath and conversational learning.


This chapter describes how to configure FabricPath switching on the Cisco Nexus 7000 Series NX-OS devices.

This chapter includes the following sections:

Information About FabricPath Switching

Licensing Requirements for FabricPath Switching

Platform Support

Enabling or Disabling FabricPath Feature Set Using DCNM

Configuring FabricPath Tunings Using DCNM (Optional)

Field Descriptions for FabricPath Optional Configurations

Feature History for Configuring FabricPath Switching Using the DCNM

Information About FabricPath Switching

FabricPath switching allows multipath networking at the Layer 2 level. The FabricPath network still delivers packets on a best-effort basis (which is similar to the Classical Ethernet [CE] network), but the FabricPath network can use multiple paths for Layer 2 traffic. In a FabricPath network, you do not need to run the Spanning Tree Protocol (STP), with its blocking ports. Instead, you can use FabricPath across data centers, some of which have only Layer 2 connectivity, with no need for Layer 3 connectivity and IP configurations.

The FabricPath encapsulation facilitates MAC mobility and server virtualization, which means that you can physically move the Layer 2 node but retain the same MAC address and VLAN association for the virtual machine. FabricPath also allows LAN extensions across data centers at Layer 2, which is useful in disaster recovery operations, as well as clustering applications such as databases. Finally, FabricPath is very useful in high-performance, low-latency computing.

With FabricPath, you use the Layer 2 intermediate System-to-Intermediate System (IS-IS) protocol for a single control plane that functions for unicast, broadcast, and multicast packets. There is no need to run the Spanning Tree Protocol (STP); it is a purely Layer 2 domain. This FabricPath Layer 2 IS-IS is a separate process than Layer 3 IS-IS.

With the F Series module and the Cisco NX-OS Release 5.1, Cisco introduces the conversation-based MAC learning schema. Conversational learning can be applied to both FabricPath (FP) and CE VLANs. Using FabricPath and conversational MAC address learning, the device has to learn far fewer MAC addresses, which results in smaller, more manageable MAC tables.

This section includes the following topics:

FabricPath Encapsulation

Default IS-IS Behavior with FabricPath

Conversational MAC Address Learning

Switching Using FabricPath

Conflict Resolution and Optional FabricPath Tunings

Interoperation between the M Series and the F Series Modules

High Availability

FabricPath Encapsulation

This section includes the following topics:

FabricPath Headers

Forwarding Tags (FTags)

FabricPath Headers

When a frame enters the FabricPath network, the system encapsulates the Layer 2 frame with a new FabricPath header. The switch IDs that the system assigns to each FabricPath device as it enters the FabricPath network is used as the outer MAC destination address (ODA) and outer MAC source address (OSA) in the FabricPath header. Figure 3-1 shows the FabricPath header encapsulating the classical Ethernet (CE) frame.

Figure 3-1 FabricPath Frame Encapsulation

The system applies the encapsulation on the ingressing edge port of the FabricPath network and decapsulates the frame on the egressing edge port of the FabricPath network; all the ports within the FabricPath network are FabricPath ports that use only the hierarchical MAC address (see Chapter 4 "FabricPath Interfaces" for more information on configuring FabricPath interfaces). This feature greatly reduces the size of the MAC tables in the core of the FabricPath network.

The system automatically assigns each device in the FabricPath network with a unique switch ID. Optionally, you can configure the switch ID for the FabricPath device.

The outer source address (OSA) is the FabricPath switch ID of the device where the frame ingresses the FabricPath network, and the outer destination address (ODA) is the FabricPath switch ID of the device where the frame egresses the FabricPath network. When the frame egresses the FabricPath network, the FabricPath device strips the FabricPath header, and the original CE frame continues on the CE network. The FabricPath network uses only the OSA and ODA, with the Layer 2 IS-IS protocol transmitting the topology information. Both the FabricPath ODA and OSA are in a standard MAC format (xxxx.xxxx.xxxx).

The FabricPath hierarchical MAC address carries the reserved EtherType 0x8903.

When the frame is originally encapsulated, the system sets the TTL to 32; on each hop through the FabricPath network, each switch decrements the TTL by 1. If the TTL reaches 0, that frame is discarded. This feature prevents the continuation of any loops that may form in the network.

Forwarding Tags (FTags)

The Forwarding Tag (FTag) in the FabricPath header specifies which one of multiple paths that the packet traverses throughout the FabricPath network. The system uses the FTag-specified paths for multidestination packets that enter the FabricPath network. The FTag is a fixed route that the software learns from the topology. The FTag is a 10-bit field with the values from 1 to 1024 (see Chapter 5 "FabricPath Forwarding" for more information on topologies and multiple paths).

This FTag is assigned on the edge port as the frame ingresses the FabricPath network and is honored by all subsequent FabricPath switches in that FabricPath network. Each FTag is unique within one FabricPath topology.

Default IS-IS Behavior with FabricPath

The interfaces in a FabricPath network run only the FabricPath Layer 2 IS-IS protocol; you do not need to run STP in the FabricPath network because FabricPath Layer 2 IS-IS discovers topology information dynamically.

FabricPath Layer 2 IS-IS is a dynamic link-state routing protocol that detects changes in the network topology and calculates loop-free paths to other nodes in the network. Each FabricPath device maintains a link-state database (LSDB) that describes the state of the network; each device updates the status of the links that are adjacent to the device. The FabricPath device sends advertisements and updates to the LSDB through all the existing adjacencies. FabricPath Layer 2 IS-IS protocol packets do not conflict with standard Layer 2 IS-IS packets because the FabricPath packets go to a different Layer 2 destination MAC address than that used by standard IS-IS for IPv4/IPv6 address families.

The system sends hello packets on the FabricPath core ports to form adjacencies. After the system forms IS-IS adjacencies, the FabricPath unicast traffic uses the equal-cost multipathing (ECMP) feature of Layer 2 IS-IS to forward traffic, which provides up to 16 paths for unicast traffic.

Within the FabricPath network, you use a single control plane protocol, Layer 2 IS-IS, for all unicast, multicast, and broadcast traffic. To use the basic FabricPath functionality, you do not need to configure Layer 2 IS-IS because you can use the default topology. The control plane Layer 2 IS-IS comes up and runs automatically when you enable FabricPath on the device.

The loop-free Layer 2 IS-IS protocol builds two trees for the topology. One tree carries unknown unicast, broadcast, and multicast traffic, and the second tree carries load-balanced multicast traffic. The system load balances multicast traffic across both trees (see Chapter 5 "FabricPath Forwarding" for more information on trees and topology).

FabricPath Layer 2 IS-IS is based on the standard IS-IS protocol with the following extensions for the FabricPath environment:

FabricPath has a single IS-IS area with no hierarchical Layer 1/Layer 2 routing as prescribed within the IS-IS standard. All devices within the FabricPath network are in a single Layer 1 area.

Multiple instances of IS-IS can be run, one per set of VLANs/topology.

The system uses a MAC address that is different from the MAC address used for Layer 3 IS-IS instances.

The system adds a new sub-TLV that carries switch ID information, which is not in standard IS-IS. This feature allows Layer 2 information to be exchanged through the existing IS-IS protocol implementation.

Within each FabricPath Layer 2 IS-IS instance, each device computes its shortest path to every other device in the network using the shortest-path first (SPF) algorithm. This path is used for forwarding unicast FabricPath frames. FabricPath Layer 2 IS-IS uses the standard IS-IS functionality to populate up to 16 routes for a given destination device. The system uses multiple equal-cost available parallel links that provide equal-cost multipathing (ECMP).

FabricPath IS-IS introduces certain modifications to the standard IS-IS in order to support constructing broadcast and multicast trees (identified by the FTags). Specifically, using FabricPath, the system constructs two loop-free trees for forwarding multidestination traffic.

Once the adjacency is established among the devices in the FabricPath network, the system sends update information to all neighbors.

By default, you can run Layer 2 IS-IS with FabricPath with no configuration, However, you can fine-tune some of the Layer 2 IS-IS parameters (see Chapter 6 "Configuring Advanced FabricPath Features" for information on configuring optional IS-IS parameters).

Additionally, FabricPath IS-IS helps to ensure that each switch ID in steady-state is unique within the FabricPath network. If FabricPath networks merge, it is possible for switch IDs to collide. If the IDs are all dynamically assigned, FabricPath IS-IS ensures that this conflict is resolved without affecting any FabricPath traffic in either network,

Conversational MAC Address Learning


Note You must be working on the F Series module in your Cisco Nexus 7000 Series chassis to use conversational MAC learning.


In traditional MAC address learning, each host learns the MAC address of every other device on the network. When you configure a VLAN for conversational learning, the associated interfaces learn only those MAC addresses that are actively speaking to them. Not all interfaces have to learn all the MAC addresses on an F Series module, which greatly reduces the size of the MAC address tables.

Beginning with Cisco NX-OS Release 5.1 and using the F Series module, you can optimize the MAC learning process. Conversational MAC learning is configured per VLAN. All FabricPath VLANs always use conversational learning; you can configure CE VLANs for conversational learning on this module also. (See Chapter 5 "FabricPath Forwarding" for more information on CE and FabricPath VLANs.)

The F Series modules have 16 forwarding engines (FEs), and the MAC learning takes place on only one of these FEs. Each FE performs MAC address learning independently of the other 15 FEs on the module. An interface only maintains a MAC address table for the MACs that ingress or egress through that FE; the interface does not have to maintain the MAC address tables on the other 15 FEs on the module.

Conversational MAC address learning, in conjunction with the 16 forward engines (FEs) on each F Series module result in MAC address tables that are much smaller for FabricPath, which uses this module and conversational MAC learning.

The MAC address learning modes available on the F Series modules are the traditional learning and conversational learning. The learning mode is configurable and is set by VLAN mode.

The following VLAN modes have the following MAC learning modes:

FabricPath (FP) VLANs—Only conversational MAC learning

CE VLANs—Traditional learning by default; you can configure CE VLANs on the F Series module for conversational learning.

With conversational MAC learning, the interface learns only the source MAC address of an ingressing frame if that interface already has the destination MAC address present in the MAC address table. If the source MAC address interface does not already know the destination MAC address, it does not learn that MAC address. Each interface learns only those MAC addresses that are actively speaking with the interface. In this way, conversational MAC learning consists of a three-way handshake.The interface learns the MAC address only if that interface is having a bidirectional conversation with the corresponding interface. Unknown MAC address are forwarded, or flooded, throughout the network.

This combination of conversational MAC address learning and multiple FEs on each F Series module produces greatly reduced MAC address tables on each F Series module.

For CE VLANs, you can configure conversational learning per VLAN on the F Series module using the command-line interface (CLI). CE VLANs use traditional MAC address learning by default.Traditional MAC learning is not supported on FabricPath VLANs with Cisco Release NX-OS 5.1 or higher.


Note You must use the CLI to configure CE VLANs for conversational MAC address learning. You cannot change the default using the DCNM.


Figure 3-2 shows the allowed FabricPath and CE ports on the M and F Series modules and the allowed FP and CE VLANs.

Figure 3-2 FP and CE VLAN Examples

Switching Using FabricPath

The FabricPath hierarchical MAC address scheme and conversational learning result in much smaller, conversational learning MAC tables within the FabricPath network. Within the FabricPath network, the system uses Layer 2 IS-IS to transmit topology information. The interfaces on the edge of the network, which use conversational MAC address learning, do not have to learn all the MAC addresses in the network (see Figure 3-3).

Figure 3-3 FabricPath Ports Use Only the FabricPath Header to Switch Frames

MAC mobility is expedited using the FabricPath hierarchical MAC addresses. That is, when you want to move a host and keep its same MAC address and VLANs, only the interfaces at the edge of the FabricPath network track this change. Within the FabricPath network, the FabricPath interfaces update their tables with only the outer MAC addresses (ODA and OSA) that have changed from the FabricPath encapsulation.

See Chapter 4 "FabricPath Interfaces" for information on FabricPath interfaces.

The interface on the edge of the FabricPath network encapsulates the original frame inside the FabricPath header. Once the frame reaches the last, or directly connected, FabricPath switch, the egress interface strips the FabricPath header and forwards the frame as a normal CE frame.

The ports on an F Series module at the edge of a FabricPath network can use conversational learning to learn only those MAC addresses that the specified edge port is having a bidirectional conversation with. Every edge interface does not have to learn the MAC address of every other edge interface; it just learns the MAC addresses of the speakers.

As the frame traverses the FabricPath network, all the devices work only with the FabricPath header. So, the FabricPath interfaces work only with the ODAs and OSAs; they do not need to learn the MAC address for any of the CE hosts or other devices attached to the network. The hierarchical MAC addressing provided by the FabricPath headers results in much smaller MAC tables in the FabricPath network, which are proportional to the number of devices in that network. The interfaces in the FabricPath network only need to know how to forward frames to another FabricPath switch so they can forward traffic without requiring large MAC address lookup tables in the core of the network.

The switches in the FabricPath network decrement the TTL in the FabricPath header by 1 at each hop. When the TTL reaches 0, the packet is dropped. This process prevents the continuation of any loops that may form in the network.

Conflict Resolution and Optional FabricPath Tunings


Note Use the CLI to tune the FabricPath network.
Beginning with Cisco Release 5.2(1) for the Cisco Nexus 7000 Series devices, you can also use DCNM to tune the FabricPath network.


After you enable FabricPath in all devices, the system automatically assigns a random switch ID to each FabricPath device. The switch ID is a 12-bit value that is dynamically assigned to every switch in the FabricPath network, with each switch being a unique value in that FabricPath network. Optionally, you can configure a specific switch ID. If any of the switch IDs in the FabricPath network are not unique, the system provides automatic conflict resolution.

The FabricPath system chooses a random value for the switch ID and sets this value as tentative during a period when the system waits to hear if this value is already in use. If this value is being used by another device in the network, the system begins a conflict resolution process. The switch with the lower system ID keeps the specified value and the other switch gets a new value for its switch ID.

In the case of a single switch joining an existing FabricPath network, the single switch changes the switch ID value rather than any switches in the existing switches in the network changing values. If the specified value is not in use by another device or after the conflict is resolved, the switch ID is marked as confirmed.

Graceful migration provides that there is no traffic disruption if a conflict arises in the resources, such as two switches that temporarily have the same switch ID.


Note The FabricPath interfaces will come up, but they are not operational until the switch checks for FabricPath conflicts and resolves those conflicts.


The FabricPath resources timers have default values, but you can also change the timer values. You can tune the device to wait longer or shorter periods to check the conflicts.

Some of the important processes of the FabricPath network are as follows:

Achieves a conflict-free allocation of switch IDs and FTags

Provides graceful resource migration during network merges or partition healing

Supports static switch IDs

Provides fast convergence during link bringup or network merge

FabricPath uses the Layer 2 IS-IS protocol to transport the database to all switches in the network. The information is distributed among the FabricPath network devices using an IS-IS TLV. Each switch sends its version of the database that contains information about all the switches.

The system allocates the FabricPath values, guarantees their uniqueness within the FabricPath network, and deletes the value from the database once that resource is no longer needed.


Note When you manually configure static switch IDs for the device, the automatic conflict resolution process does not work and the network does not come up. You will see syslog messages about the conflict and must manually change one or more switch IDs of the devices in the network.


Interoperation between the M Series and the F Series Modules

Beginning with Cisco Release 5.2(1) for the Nexus 7000 Series devices, the MAC learning for the F Series FabricPath-enabled modules when an M Series module is present in the chassis has changed. Now, in this configuration, the FabricPath switches will copy all locally learned MAC address entries onto the core port. This is the default learning mode in a chassis containing both F Series and M Series modules.

When you have an M Series module and an F Series module in the same Cisco Nexus 7000 Series chassis, the FabricPath interface on the F Series modules also learns the MAC addresses that traverse that port from the M Series module. In this way, the FabricPath interface provides proxy learning for the MAC addresses on the M Series module in the mixed chassis.

Because M Series modules cannot enable FabricPath, those FabricPath-enabled interfaces that coexist in the same Cisco Nexus 7000 Series chassis do have to learn the MAC addresses of the packets that are traversing the FabricPath-enabled F Series interfaces from the M Series interfaces. In this way, the FabricPath interface provides proxy learning for the MAC addresses on the M Series module in the mixed chassis.

See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x, and Cisco Nexus 7000 Series NX-OS Multicast Routing Configuration Guide, Release 6.x, for more information on interoperation between the F1 Series and M Series modules.

High Availability

The FabricPath topologies retain their configuration through ISSU.

See the Cisco Nexus 7000 Series NX-OS High Availability and Redundancy Guide, Release 6.x, for more information on high availability.

Licensing Requirements for FabricPath Switching

The following table shows the licensing requirements for this feature:

Product
License Requirement

Cisco NX-OS

FabricPath requires an Enhanced Layer 2 license. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco Nexus 7000 Series Licensing Guide.

Cisco DCNM

FabricPath requires no license. Any feature not included in a license package is bundled with the Cisco DCNM and is provided at no charge to you. For an explanation of the Cisco DCNM licensing scheme, see the Cisco DCNM Installation and Licensing Guide.


Platform Support

The following platform supports this feature. For platform-specific information, including guidelines and limitations, system defaults, and configuration limits, see the corresponding documentation.

Platform
Documentation

Cisco Nexus 7000 Series Switches

Cisco Nexus 7000 Series Switches Documentation


Enabling or Disabling FabricPath Feature Set Using DCNM


Note You must install the FabricPath feature set before you enable FabricPath on the device. See the Configuring Feature Set for FabricPath guide for information on installing the FabricPath feature set.


BEFORE YOU BEGIN

Ensure that you have enabled FabricPath.

Ensure that you are working on an F Series module.

DETAILED STEPS

To enable or disable the FabricPath feature on the device, follow these steps:


Step 1 From the Feature Selector pane, choose Switching > Fabricpath > Resources to open the Resources pane.

Step 2 From the Contents pane, in the Summary pane, click the device on which you want to enable or disable FabricPath.

Step 3 From the menu bar, choose Actions > Enable Fabricpath Feature Set.

This action enables FabricPath on the device.

Step 4 From the menu bar, choose Actions > Disable Fabricpath Feature Set.

This action disables FabricPath on the device.

Step 5 (Optional) From the menu bar, choose File > Deploy to apply your changes to the device.


Configuring FabricPath Tunings Using DCNM (Optional)


Note You must have an F Series module in the chassis and enabled FabricPath on all the devices before you can see the FabricPath commands on the devices.


This section includes the following:

Configuring the Switch ID

Configuring the FabricPath Timers

Disabling and Enabling Graceful Merges

Forcing the Links to Come Up

Displaying Conflict Information

Displaying FTag Information


Note You must make these configurations on each switch that you want to participate in the Fabricpath network.


Configuring the Switch ID

By default, FabricPath assigns each FabricPath device with a unique switch ID after you enable FabricPath on all the devices.

BEFORE YOU BEGIN

Ensure that you have enabled FabricPath.

Ensure that you are working on an F Series module.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Switching > Fabricpath > Resources to open the Resources pane.

Step 2 From the Contents pane, in the Summary pane, click the device in which you want to configure the FabricPath switch ID.

The system highlights the device in the Summary pane, and tabs appear in the Details pane.

Step 3 In the Details pane, click the Resources Details tab.

Step 4 Click the Switch-ID Settings section.

Step 5 In the Switch-ID field, enter the value that you want to assign for the device's FabricPath switch ID.

Step 6 (Optional) From the menu bar, choose File > Deploy to apply your changes to the device.


Configuring the FabricPath Timers

You can change the following FabricPath timers:

allocate-delay—Configures the delay for a new resource to be propagated throughout the network before that value becomes available and permanent.

linkup-delay—Configures the link bringup delay to detect conflicts.

transition-delay—Configures the delay for propagating a transitioned value in the network; during this period both old and new resource values exist in the network.

BEFORE YOU BEGIN

Ensure that you have enabled FabricPath.

Ensure that you are working on an F Series module.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Switching > Fabricpath > Resources to open the Resources pane.

Step 2 From the Contents pane, in the Summary pane, click the device in which you want to configure the FabricPath switch ID.

The system highlights the device in the Summary pane, and tabs appear in the Details pane.

Step 3 In the Details pane, click the Resources Details tab.

Step 4 Click the Switch-ID Settings section.

Step 5 In the Allocate Timer field, enter the value that you want in seconds.

Step 6 In the Linkup Timer field, enter the value that you want in seconds.

Step 7 In the Transition Timer field, enter the value that you want in seconds.

Step 8 (Optional) From the menu bar, choose File > Deploy to apply your changes to the device.


Disabling and Enabling Graceful Merges


Note You may experience traffic drops if you disable this feature.


You can disable or enable the graceful merge feature of FabricPath.

BEFORE YOU BEGIN

Ensure that you have enabled FabricPath.

Ensure that you are working on an F Series module.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Switching > Fabricpath > Resources to open the Resources pane.

Step 2 From the Contents pane, in the Summary pane, click the device in which you want to configure the FabricPath switch ID.

The system highlights the device in the Summary pane, and tabs appear in the Details pane.

Step 3 In the Details pane, click the Resources Details tab.

Step 4 Click the Switch-ID Settings section.

Step 5 In the pull-down menu of the Graceful-Merge field, choose Enabled or Disabled.

Step 6 (Optional) From the menu bar, choose File > Deploy to apply your changes to the device.


Forcing the Links to Come Up

As a onetime event, you can force the FabricPath network links to connect. This configuration will not be saved when you enter the copy running-config startup-config command.

BEFORE YOU BEGIN

Ensure that you have enabled FabricPath.

Ensure that you are working on an F Series module.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Switching > Fabricpath > Resources to open the Resources pane.

From the Contents pane, in the Summary pane, click the device, for which the links need to be brought forcefully.

Step 2 From the menu bar, choose Actions > Force Link-Bringup or right-click on the device and click Force Link-Bringup to bring up the FabricPath links.


Displaying Conflict Information

If a switch ID conflict exists in the device, you can display information about the conflict.

BEFORE YOU BEGIN

Ensure that you have enabled FabricPath.

Ensure that you are working on an F Series module.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Switching > Fabricpath > Resources to open the Resources pane.

Step 2 From the Contents pane, in the Summary pane, click the device in which you want to display the conflict.

The system highlights the device in the Summary pane, and tabs appear in the Details pane.

Step 3 In the Details pane, click the Resource Details tab.

Step 4 Click the Conflict Information section.

The screen displays the conflict information.


Displaying FTag Information

You can display the FTAG information such as Tree ID, graph type, and status per Fabricpath topology for the selected device.

BEFORE YOU BEGIN

Ensure that you have enabled FabricPath.

Ensure that you are working on an F Series module.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Switching > Fabricpath > Resources to open the Resources pane.

Step 2 From the Contents pane, in the Summary pane, click the device in which you want to display FTag information.

The system highlights the device in the Summary pane, and tabs appear in the Details pane.

Step 3 In the Details pane, click the FTAG Status tab.

Step 4 In the Topology-ID/Graph Type field, click on the FabricPath topology in which you want to view the FTag information.

The screen displays the FTags for each topology and their status, which is either Tentative or Confirmed.


Field Descriptions for FabricPath Optional Configurations

These field descriptions are used for configuring the FabricPath optional features that fine-tune FabricPath. This section includes the following topics:

Resources: Resources Details: Switch ID Settings Section

Resources: Resources Details: Conflict Information Section

Resources: FTAG Status: FTAG Status Section

Resources: Resources Details: Switch ID Settings Section

Table 3-1 Resources: Resources Details: Switch ID Settings Section 

Field
Description
Basic Settings

Device Name

Display only. Name of the device.

Switch ID

Switch-ID for the device in the FabricPath topology.

Note The system automatically assigns the switch-ID when you enable FabricPath. You can manually override that assignment and assign you own switch ID, which must be unique for that device in that FabricPath topology.

Graceful-merge

Enables or disables FabricPath graceful merge feature.

Type

Display only. Static or dynamic switch-ID.

Status

Display only. Confirmed or Tentative switch-ID.

Secondary Switch-ID

Display only. Secondary switch-ID allocated during transition.

Note Secondary switch-id is displayed only during transition.

Delay Timer Settings

Allocate Timer (secs)

Value for propagating new FabricPath information throughout FabricPath topology.

Linkup Timer (secs)

Value for link bring-up for detecting conflicts in the switch ID.

Transition Timer (secs)

Value for propagating transition value.


Resources: Resources Details: Conflict Information Section

Table 3-2 Resources: Resources Details: Conflict Information Section 

Field
Description

Host Name/System-ID

Display only. Host name or MAC address of the device that has the same FabricPath switch ID as another device.

Interface Name

Display only. Name of FabricPath interface.

Operational Status

Display only. Operational status of FabricPath interface.

Note Status is Down if there are conflicts in the switch ID.

Status Description

Display only. Reason for operational status will be displayed as suspended protocol.


Resources: FTAG Status: FTAG Status Section

Table 3-3 Resources: FTAG Status: FTAG Status Section 

Field
Description

Topology ID/Graph Type

Display only. Displays the FabricPath topology ID.

TREE ID

Display only.

Status

Display only. The status can be Confirmed or Tentative.


Feature History for Configuring FabricPath Switching Using the DCNM

Table 3-4 lists the release history for this feature.

Table 3-4 Feature History for FabricPath Switching 

Feature Name
Releases
Feature Information

FabricPath

5.1(1)

These features were introduced.

New default MAC address learning mode in chassis containing both F Series and M Series modules

5.2(1)

This feature was introduced.