Fabripath in Cisco Nexus Switches - CLI version
- Pavan Raja
- Apr 8, 2025
- 36 min read
Summary:
It seems like you're providing detailed instructions on configuring various parameters for IS-IS over FabricPath in Cisco Nexus switches. Here is a summary of your provided information: 1. **Configure reference bandwidth**: You can set the reference bandwidth using the command `switch(config-fabricpath-isis)# reference-bandwidth {ref-mbps
| ref-gbps
}`. The default value is 400000 Mbps, with a range from 1 to 400000 for `ref-mbps` and from 1 to 4000 for `ref-gbps`. 2. **Configure interval between LSA arrivals**: Use the command `switch(config-fabricpath-isis)# spf-interval msecs
` with optional parameters like `spf-max-wait`, `spf-initial-wait`, and `spf-second-wait`. 3. **Enable graceful restart**: Use the command `switch(config-fabricpath-isis)# graceful-restart
` with a default timer of 60 seconds, ranging from 30 to 65535.
4. **Enable dynamic hostname**: Use the command `switch(config-fabricpath-isis)# hostname dynamic`.
For configuring advanced FabricPath Layer 2 IS-IS parameters on Cisco Nexus switches:
1. Enter configuration mode with specific interface commands like `fabricpath isis`. 2. Set authentication type using `authentication-type` and optional key chains if needed. 3. Adjust interval settings such as `csnp-interval`, `hello-interval`, `lsp-interval`, and others within specified ranges. 4. Configure metric values, retransmission intervals, and throttle intervals similarly with range limitations. 5. Exit configuration modes to show the running configuration or copy it to the startup configuration.
For clearing and verifying Advanced FabricPath configurations:
1. Ensure you are on an F Series module with Enhanced Layer 2 license and FabricPath feature set. 2. Use commands like `clear fabricpath isis adjacency`, `clear fabricpath isis statistics`, and `clear fabricpath isis traffic` to clear counters. 3. Verify configurations using show commands such as `show fabricpath isis adjacency`, `show fabricpath isis database`, etc.
This summary captures the essence of configuring and managing IS-IS over FabricPath in Cisco Nexus switches, including setting up advanced parameters and verifying configurations.
Details:
The document "Cisco Nexus 7000 Series NX-OS FabricPath Configuration Guide" provides a comprehensive guide on configuring the Cisco Nexus 7000 Series switches to support FabricPath, which is designed to enable high performance and scalability in virtualized data center environments. Key aspects covered include:
1. **Overview**: The document introduces key concepts such as FabricPath, Conversational MAC Address Learning, Virtualization, and High Availability. It outlines the licensing requirements for implementing these features within a Cisco Nexus switch environment.
2. **Configuring FabricPath Switching**: This section covers essential aspects of setting up FabricPath switching, including encapsulation methods (FabricPath Encapsulation), header specifications (FabricPath Headers), forwarding tags (Forwarding Tags or FTags), default IS-IS behavior, and conversational MAC address learning settings. It also addresses core port learning, support for an emulated switch (FEX), conflict resolution mechanisms, and interoperability between different module types like the M Series and F Series.
3. **High Availability**: The guide details how to configure High Availability features such as Virtual Device Contexts within the FabricPath framework.
4. **Licensing Requirements**: Clearly states the licensing requirements for using FabricPath in a Cisco Nexus switch setup, emphasizing that users are responsible for their application of any products and should refer to the software license provided with the product or contact their Cisco representative if needed.
5. **Documentation Feedback**: Provides guidance on obtaining further documentation and submitting service requests related to the configuration guide itself.
The document is intended for network administrators, engineers, and IT professionals who are responsible for configuring and managing networking infrastructure in data centers utilizing Cisco Nexus switches with NX-OS software. It includes a preface outlining the audience and organization of the document, as well as conventions followed throughout the manual. The content is subject to change without notice, reflecting typical practices in technical documentation where updates are continuously made based on new developments or user feedback.
This document provides a comprehensive guide to configuring and managing the FabricPath feature set on Cisco Nexus 7000 Series switches, focusing on NX-OS software. It covers various aspects including enabling/disabling the FabricPath feature, configuring MAC learning mode, switch ID settings, timers, and forwarding mechanisms. The document also delves into advanced features such as virtual device contexts (vPC) and Layer 2 IS-IS configurations for enhanced network performance and fault tolerance. Additionally, it outlines prerequisites, licensing requirements, and limitations associated with FabricPath configuration. Finally, the guide includes information on specific configurations limits and a feature history section that highlights changes across different versions of the software.
The provided text is primarily focused on summarizing new and changed features within Cisco NX-OS Release 6.0 for the Nexus 7000 Series, specifically regarding the FabricPath feature. It details enhancements such as a new default MAC address learning method for mixed chassis configurations, load balancing support with F2 modules, introduction of core port learning for VPC+ on F2 cards, and support for emulating a switch using FEXs. The document also outlines the organization and conventions of the accompanying Cisco Nexus 7000 Series NX-OS FabricPath Configuration Guide, which includes chapters covering overview, configuring FabricPath switching, interfaces, forwarding, and advanced features. It emphasizes experienced user audience targeting and provides detailed descriptions with specific conventions for command usage in terminal sessions.
The preface of the "Cisco Nexus 7000 Series NX-OS FabricPath Configuration Guide" outlines several key points and provides guidance for users, including information on how to obtain additional documentation and submit feedback or service requests. Here's a summary:
1. **Document Purpose**: This document is designed to assist with the configuration of Cisco Nexus 7000 Series switches running NX-OS software, focusing specifically on FabricPath features. It aims to help users avoid potential issues like equipment damage or data loss by providing essential information and best practices for setting up and managing these devices.
2. **Related Documentation**: Users are directed to various other Cisco documents that may be relevant to their configuration efforts. These include release notes, configuration guides, command references, and more. The full list includes manuals like the "Cisco Nexus 7000 Series NX-OS Release Notes", "Cisco Nexus 7000 Series NX-OS Configuration Examples", "Cisco NX-OS Licensing Guide", among others, providing a comprehensive set of resources for different aspects of the system management.
3. **Feedback and Support**: Users are encouraged to provide feedback or report errors by emailing nexus7k-docfeedback@cisco.com. Additionally, Cisco provides a mechanism for users to submit service requests, though this is not detailed in the provided text.
4. **Updating Knowledge Base**: The preface also mentions that Cisco regularly updates their technical documentation and encourages customers to stay informed through resources like "What’s New in Cisco Product Documentation", which lists all new and revised documentation. Subscribers can access this information at a specified URL, though it is not detailed here how one subscribes or accesses this service.
5. **Document Feedback**: Users are directed to provide feedback on the document itself if they encounter errors or feel that important information is missing. This direct link for feedback (nexus7k-docfeedback@cisco.com) is provided, which indicates Cisco's commitment to continuous improvement of their documentation through user input.
In summary, this preface serves as a guide and resource list for users working with Cisco Nexus 7000 Series switches and NX-OS software, emphasizing the importance of staying informed through official channels and providing feedback where needed.
The document "Cisco Nexus 7000 Series NX-OS FabricPath Configuration Guide" outlines a product documentation system as an RSS feed for delivering content directly to users' desktops via reader applications, supporting RSS version 2.0. The guide provides an overview of the FabricPath and conversational MAC address learning features specific to Cisco's NX-OS software for its Nexus 7000 Series devices.
The chapter titled "Overview" explains that the FabricPath feature is available with certain modules starting from Cisco NX-OS Release 5.1, enhancing Layer 2 multipathing without requiring Spanning Tree Protocol (STP), and providing a single control plane for various types of traffic including unknown unicast, unicast, broadcast, and multicast. It also introduces virtualization and high availability features within the FabricPath network.
Conversational MAC address learning is another key feature enabled from the same release, allowing interfaces to learn only those MAC addresses that are actively communicating with them, rather than all MAC addresses in the domain. This selective learning method helps scale networks beyond individual switch MAC address tables limitations. Both features support operational simplicity and performance within Layer 2 domains.
The article discusses configuring FabricPath switching on Cisco Nexus 7000 Series devices, emphasizing its use for multipath networking at the Layer 2 level without requiring the Spanning Tree Protocol (STP). It highlights that FabricPath switching supports conversational MAC learning and can be configured in various VLANs. Additionally, it mentions high availability features within the FabricPath network, which retain configurations during an infrastructure subsystem upgrade (ISSU), as well as licensing requirements for using this feature. The article provides a detailed guide on how to configure and verify FabricPath switching, with examples of configuration settings and steps for setting up VDCs and core ports.
This section of the Cisco Nexus 7000 Series NX-OS FabricPath Configuration Guide covers various aspects of configuring and utilizing FabricPath switching. The main focus is on simplifying network management through conversational MAC address learning, which reduces the number of MAC addresses learned, thus making MAC tables smaller and more manageable.
1. **FabricPath Encapsulation**: Introduces how frames are encapsulated with a new FabricPath header when entering the FabricPath network. This includes details about the FabricPath headers (with outer MAC destination address ODA and source address OSA), FTags, and their roles in forwarding packets across multiple paths within the network.
2. **FabricPath Headers**: Explains that upon entry into the FabricPath network, a layer 2 frame is encapsulated with a new header called the FabricPath header. This header includes ODA (outer MAC destination address) and OSA (outer MAC source address), which are used for addressing within the network.
3. **Forwarding Tags (FTags)**: Discusses how FTags specify paths through which packets traverse the FabricPath network, particularly useful for multidestination packets. The FTag is a 10-bit field with values from 1 to 1024, assigned on edge ports and representing fixed routes learned from topology information.
Overall, this section aims to provide guidance on how Cisco supports conversational learning schema in FabricPath (both FP and CE VLANs) for smaller, more manageable MAC tables, through encapsulation of frames with a new header including ODA/OSA and FTags, simplifying the network management process.
In summary, Cisco Nexus 7000 Series NX-OS FabricPath allows for a dynamic link-state routing protocol called FabricPath Layer 2 IS-IS, which automatically discovers network topology and calculates loop-free paths without requiring Spanning Tree Protocol (STP). This setup operates on the principle of forming adjacencies through hello packets sent over core ports. The default behavior uses equal-cost multipathing for unicast traffic to forward up to 16 paths, while it constructs two loop-free trees for multicast traffic using FTag identifiers. These features are implemented with extensions specific to the FabricPath environment, such as a single IS-IS area without hierarchical routing and unique MAC addresses from Layer 3 IS-IS instances. The system utilizes SPF algorithm to compute shortest paths and ECMP for load balancing across multiple parallel links.
This passage discusses the configuration of MAC address learning in Cisco Nexus 7000 Series switches, specifically on F Series modules. The primary methods for MAC address learning are traditional and conversational, with conversational MAC learning being more efficient due to its selective nature, where interfaces only learn MAC addresses involved in bidirectional communication. Conversational MAC learning is configured per VLAN and applies to both FabricPath (FP) and Customer Edge (CE) VLANs, though CE VLANs default to traditional learning unless specified otherwise. The use of multiple forwarding engines (FEs) on the F Series modules further aids in reducing the size of MAC address tables by allowing each FE to independently learn MAC addresses without overloading the interface or other FEs with unnecessary information.
This text is about FabricPath switching, a method for hierarchical MAC addressing and learning in networking devices like Cisco Nexus 7000 Series NX-OS. It involves using VLANs to categorize devices into two types: CE (Customer Edge) and FP (Fabric Path). CE devices are those on the edge with interfaces that carry specific VLANs, while FP devices have interfaces carrying a mix of VLANs and use conversational learning to manage MAC addresses through Layer 2 IS-IS topology information. The system enables core port learning mode by default for F2 cards supporting VPC+ in NX-OS Release 6.1, where local MACs are copied to the core ports' forwarding engines. This method results in smaller MAC tables due to hierarchical addressing and conversational learning across interfaces at the edge of the network.
This document provides information about configuring FEXs (Fabric Extenders) with VPC+ (Virtual Port Channel Plus) for an emulated switch on Cisco Nexus 7000 Series devices running NX-OS Release 6.1 and later. The setup involves enabling the FabricPath feature set, configuring partial DF mode, setting up a specific switch ID, and associating FEXes to enable Layer 2 host interfaces (HIF) port channels. It also covers conflict resolution and optional tuning for the FabricPath network.
The process begins with entering configuration mode on both VPC peers, then enabling partial DF mode using the 'fabricpath multicast load-balance' command. Next, configure the emulated switch ID by setting up a domain with an assigned ID number. For each FEX, associate it to a port channel and set the interface to operate in FEX fabric mode before disabling and exiting shutdown on the interface.
After these steps, create a Layer 2 host interface (HIF) port channel for the FEX by creating a new Ethernet interface with the specified FEX number and satellite port number, grouping it into a channel group of ID/1001, and enabling it. Finally, configure the VPC ID on this HIF port channel to complete the setup. The document also notes that if there are conflicts in switch IDs, these can be resolved through optional tuning settings within the configuration process.
The article discusses Cisco's FabricPath switching, a network architecture that automates the assignment of unique switch IDs and FIDs (FabricPath Identifiers) to switches in a network. If there are conflicts between switch IDs or FIDs, the system automatically resolves these conflicts by assigning new values for the conflicting devices.
The process involves several steps:
1. The FabricPath system assigns a random value as a tentative switch ID and waits to check if this value is already used by another device in the network.
2. If the value is already being used, it triggers conflict resolution where the switch with the lower system ID keeps its specified value while the other gets a new switch ID.
3. In single-switch joins, the switch changes its switch ID value rather than any switches in the existing network changing their values. After confirming that no conflicts exist or after resolving them, the switch ID is marked as confirmed.
4. FabricPath interfaces come up but are not operational until they check for conflicts and resolve them; tuning timer values allows adjusting the conflict checking duration.
5. The system uses Layer 2 IS-IS protocol to distribute database information across switches, ensuring unique allocation of FIDs and proper network management.
6. When using static switch IDs manually configured on devices, automatic conflict resolution is not available, potentially causing issues that require manual intervention to resolve.
7. For mixed chassis configurations with both M Series (which can't enable FabricPath) and F Series modules, the F Series interfaces learn MAC addresses from M Series interfaces due to proxy learning provided by the FabricPath interface in such setups.
8. The article also notes licensing requirements for utilizing certain aspects of FabricPath switching as per other Cisco documentation referred to at the end.
Overall, this document provides a comprehensive guide on configuring and managing FabricPath switching within a Nexus 7000 Series device environment, highlighting key considerations regarding automatic conflict resolution, static ID configurations, and the unique interactions between different module types in the chassis.
The Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide and Multicast Routing Configuration Guide provide detailed information about interoperation between F1 Series and M Series modules, highlighting prerequisites, licensing requirements, configuration guidelines, and limitations for FabricPath switching. To configure FabricPath switching, users must have a working knowledge of classical Ethernet Layer 2 functionality, install the FabricPath feature set in default and nondefault VDCs before enabling it, ensure they are logged onto the device with an enhanced layer 2 license, and work within the correct virtual device context (VDC) on F Series modules. The configuration requires enabling FabricPath interfaces for encapsulated traffic only, configuring private VLANs under specific guidelines, and avoiding placing FabricPath ports in them. Additionally, STP does not run inside a FabricPath network, and multiple SPAN destination ports or virtual SPAN are unsupported.
The passage from the Cisco Nexus 7000 Series NX-OS FabricPath Configuration Guide outlines the steps and considerations for enabling the FabricPath feature set on a device, which is necessary before configuring various FabricPath features such as MAC learning mode, switch ID, timers, and graceful merge. The process involves entering global configuration mode, enabling the FabricPath feature set with the 'feature-set fabricpath' command, and exiting configuration mode. Optionally, users can configure these settings manually to customize behavior according to specific needs.
### Key Points:
1. **Prerequisites**: Before starting the configuration, ensure that you have installed an Enhanced Layer 2 license and an F Series module on the device.
2. **Enabling FabricPath Feature Set**: The process involves entering global configuration mode with 'config terminal', then enabling the FabricPath feature set using 'feature-set fabricpath'.
3. **Optional Configuration**: Users can optionally configure MAC learning mode, switch ID, timers, and graceful merge settings manually to fine-tune network behavior.
4. **Graceful Merge Feature**: This is enabled by default but may cause traffic drops if disabled; it involves managing the merging of links in a FabricPath network.
5. **Forcing Links Up**: Users can configure this feature to force link activation at startup, ensuring immediate networking readiness.
6. **Documentation Reference**: The passage provides detailed steps and examples for each command, including 'config terminal', 'feature-set fabricpath', 'exit', 'show feature-set', and 'copy running-config startup-config'.
This guide is essential for network administrators looking to implement or configure FabricPath switching on Cisco Nexus devices, ensuring optimal performance and configuration of the networking environment.
The provided text outlines the steps and commands necessary for configuring and disabling FabricPath functionality, along with setting up MAC learning modes in a Cisco Nexus 7000 Series switch running NX-OS. Here's a summarized version of the information presented:
1. **Disabling FabricPath Functionality:**
To disable FabricPath, use the following commands:
```
1. config terminal
2. no feature-set fabricpath
3. exit
4. (Optional) show feature-set
5. (Optional) copy running-config startup-config
```
Commands explained:
`config terminal` enters global configuration mode.
`no feature-set fabricpath` disables the FabricPath feature set in the Virtual Device Context (VDC).
`exit` returns to the command line interface.
`show feature-set` displays enabled features; optional for this task but useful for verification.
`copy running-config startup-config` copies the current configuration to the startup configuration, ensuring the setting persists through reboots.
2. **Configuring MAC Learning Mode:**
For CE VLANs (Customer Edge Virtual Local Area Network), traditional learning mode is default but can be switched to conversational MAC address learning:
```
1. config terminal
2. mac address-table learning-mode conversational vlan vlan-id
3. exit
4. (Optional) show mac address-table learning-mode {vlan vlan-id}
5. (Optional) copy running-config startup-config
```
Commands explained:
`mac address-table learning-mode conversational vlan vlan-id` configures the specified CE VLANs for conversational MAC learning, using the no form to revert to traditional learning mode if needed.
These steps are crucial for managing network configurations in a Cisco Nexus switch, ensuring optimal performance and efficiency based on specific networking requirements. This document provides detailed steps on how to manually configure a Cisco Nexus 7000 Series switch's FabricPath switch ID. The process involves entering global configuration mode, specifying a unique switch ID (value between 1-4094), exiting configuration mode, and optionally displaying or copying the running configuration for future reference. It also outlines optional steps to show switch IDs and copy configurations. Additionally, it mentions configuring timers such as allocate-delay, linkup-delay, and transition-delay which control how quickly new values are propagated in the network and help resolve conflicts between user configured switch IDs. These steps must be performed on each switch that participates in the FabricPath network to ensure proper operation. The document provides a guide to configure and manage FabricPath switching on Cisco Nexus 7000 Series switches. To begin, ensure the module is an F Series and that the FabricPath feature and Enhanced Layer 2 license are enabled. Follow these steps for configuring or disabling FabricPath timers: 1. Enter global configuration mode with `config terminal`. 2. Set FabricPath timer values using the command `fabricpath timers {allocate-delay seconds | linkup-delay seconds | transition-delay seconds}`. The default values range from 1 to 1200 seconds, but it's recommended to use at least a linkup-delay of 60 seconds. 3. Exit configuration mode with `exit`. 4. Optionally, display the FabricPath timers using `show fabricpath timers`. 5. Copy the running configuration to startup configuration with `copy running-config startup-config`. For disabling graceful merges in case you need to: 1. Enter global configuration mode with `config terminal`. 2. Use the command `
fabricpath graceful-merge disable` to toggle the feature off.
3. Exit configuration mode with `exit`.
4. Optionally, display the running configuration using `show running-config`.
5. Copy the running configuration to startup configuration with `copy running-config startup-config`.
Remember that these steps must be performed on each switch participating in the FabricPath network.
The document provides a guide on configuring FabricPath switching in Cisco Nexus 7000 Series switches, including enabling the feature, setting switch IDs, and verifying the configuration. It advises against using the `fabricpath force link-bringup` command as recommended practice but outlines its purpose if needed. Additionally, it includes commands for displaying and clearing statistics related to FabricPath switching, along with example configurations.
The article provides an overview of default parameters for FabricPath switching on Cisco Nexus 7000 Series devices. It includes details about MAC address learning modes, VLANs, timers such as allocate-delay, linkup-delay, and transition-delay, and the status of graceful merge. Additionally, it outlines the feature history for configuring FabricPath using the CLI, including release notes, introduced features, and interfaces involved. The article also discusses information about FabricPath interfaces, including their role in STP, vPC+, designated forwarder, high availability, virtual device contexts, licensing requirements, prerequisites, guidelines and limitations for configuration, example configurations, and how they interact with FP VLANs and CE VLANs.
This document is about how Cisco Nexus 7000 Series switches, called FabricPath interfaces, work with a network system called STP (Spanning Tree Protocol). These interfaces help manage traffic between computers and servers connected to the switch. The important thing in this setup is that all the switches involved are aware only of special VLANs for their own use and not about regular ones used by computers.
To make sure there are no loops causing problems, each FabricPath Layer 2 gateway switch must be made the root for its STP domain to prevent issues. This means configuring a lower priority than other devices in that domain. The system automatically assigns MAC addresses for bridge IDs and all connected CE devices see one unified network through these switches.
If needed, you can set up unique identifiers (domain ID) for each STP domain associated with the same FabricPath network to help manage information better. When a change is detected in this setup, it flushes remote MACs related to that domain and sends the update within its own domain. This process helps maintain order and efficiency across both domains and connected devices.
The article discusses how Cisco Nexus 7000 Series switches, when equipped with FabricPath capabilities, can integrate with classical Ethernet (CE) virtual port channels (vPCs). A novel extension called vPC+ is introduced to facilitate this integration. This configuration allows for active-active FHRP (First Hop Routing Protocol) capability at the boundary between a CE domain and a Cisco FabricPath cloud.
vPC+ extends the functionality of traditional vPCs by enabling them to interoperate with other vPC domains, even though they are configured in the same Virtual Device Context (VDC). This is achieved through the use of unique virtual switch IDs for each vPC+. The configuration of such a domain requires that all devices within the vPC+ have the same domain settings.
A crucial aspect of vPC+ is its ability to provide active-active Layer 2 paths, essential for dual-homed CE devices or cloud environments. Despite the limitation in FabricPath networks where MAC addresses map directly to switch IDs (1:1), vPC+ creates a virtual switch that functions as an intermediary between the CE and FabricPath networks. This setup ensures continuous connectivity by emulating a single virtual switch, distributing traffic appropriately based on its source MAC address.
To fully leverage vPC+, all interfaces in the peer link must be part of an F Series module with FabricPath enabled. These downstream links are specifically designed for interfacing with CE hosts and will operate as FabricPath edge interfaces. The assignment of a virtual switch ID (vSI) is crucial, as it determines the outer source address (OSA) used in the encapsulation header during transmission over the FabricPath network.
For routing functions within a vPC+ domain, the system requires an M Series module for proxy routing capabilities since F1 Series modules are primarily Layer 2 interfaces. Both First Hop Routing Protocols (FHRP), including HSRP (Hot Standby Routing Protocol), can operate in conjunction with vPC+, requiring dual attachment of Layer 3 devices to both peer devices for proper functionality.
In summary, the vPC+ feature enhances interoperability between classical Ethernet and Cisco FabricPath networks by enabling active-active FHRP at the network boundary and maintaining robust Layer 2 connectivity across these distinct networking paradigms. This integration is critical for supporting complex multi-homed environments where multiple CE devices or clouds need to communicate with a single FabricPath cloud, ensuring high availability and efficient traffic management through unique virtual switch identities and encapsulation headers.
This document discusses various configurations related to High Availability Redundancy Protocol (HSRP) in a vPC+ environment. It emphasizes the importance of configuring lower and upper thresholds to prevent group state flaps due to interface flaps, especially when multiple tracking objects are involved. When a primary vPC peer device fails over to the secondary, FHRP traffic should continue smoothly without interruption by ensuring a separate Layer 3 link for routing is used instead of relying on VLAN network interfaces.
The document also warns against configuring the burnt-in MAC address option (use-bia) or manually setting virtual MAC addresses in a vPC+ environment as these can negatively impact load balancing. It stresses the importance of using the same MAC address configuration across both vPC peer devices and highlights the use of a restore timer to delay the reestablishment of a vPC after failover until the network interfaces are fully operational again, thus preventing potential packet drops due to routing table convergence issues.
Furthermore, it provides information on configuring custom MAC addresses for HSRP in a vPC+ environment and discusses the consequences of enabling certain delays (HSRP delay or preemption delay) without proper configuration. It also advises on using specific CLI commands like 'delay restore' for configuring these features and directs readers to further resources such as the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x, for more detailed information.
The document also introduces a feature in NX-OS where two peers can be configured as partial designated forwarders when both vPC legs are up, using the 'fabricpath multicast load-balance' CLI command under vPC domain mode. It describes the three possible states of a vPC port regarding designated forwarding: all (where the local switch acts as the designated forwarder), partial (each peer is the designated forwarder for half of the resources), and none (no forwarding occurs if the local leg is down).
Lastly, it discusses how FabricPath topologies retain their configuration during an in-service software upgrade and emphasizes the importance of installing the FabricPath feature set before enabling it on a switch. It provides guidance on which port pairs or port sets must be in the same Virtual Device Context (VDC) depending on the module type.
The text provided outlines the licensing requirements and prerequisites for using FabricPath interfaces on Cisco NX-OS switches, specifically within the context of the Cisco Nexus 7000 Series. It states that to utilize these interfaces, an Enhanced Layer 2 license is mandatory. Before enabling FabricPath on a switch, one must have a basic understanding of classical Ethernet Layer 2 functioning and previously installed the feature set for FabricPath in both default and non-default Virtual Device Contexts (VDCs).
The document also outlines several guidelines and limitations associated with configuring and using FabricPath interfaces:
1. **Licensing Requirements**: Only devices licensed for Enhanced Layer 2 can use FabricPath interfaces, requiring a specific type of license that extends Layer 2 capabilities beyond those provided by standard Layer 2 switches.
2. **Prerequisites**: Users must be familiar with basic Ethernet Layer 2 operation before enabling FabricPath on the switch. They also need to install and configure the FabricPath feature set across all relevant VDCs.
3. **Feature Set Installation**: If a device is in an unstable state (e.g., after a service failure or power-up), it might cause the standby supervisor module to reload.
4. **Configuration Guidelines and Limitations**:
**Traffic Types**: Only FabricPath encapsulated traffic should be carried by these interfaces.
**STP Operation**: STP does not function within a FabricPath network, implying that Spanning Tree Protocol must be configured externally if needed.
**SPT Priority**: The priority for STP on Layer 2 gateway devices in the FabricPath network should be set to 8192.
**F Series Module Limitations**: This module type does not support certain advanced features like multiple SPAN destinations or VLAN-specific configurations that might affect its operation within a VDC.
5. **Private VLANs and FabricPath**: It is crucial that all VLANs in private VLAN configurations are either in CE (Customer Edge) or FP (FabricPath) mode, avoiding mixed configurations which could lead to inactive VLANs. Additionally, FabricPath ports must not be included in any private VLAN setup. 6. **MAC Addresses**: The system does not support hierarchical static MAC addresses; only static MAC addresses for CE can be configured. 7. **VPC Domain Behavior**: In a VPC (Virtual Port Channel) domain, pruning does not occur as it normally would in standalone networks, and all switches might receive multicast traffic but forward it to the receiver based on internal rules. 8. **Maximum Ports**: The number of vPC+ member ports per vPC+ domain is capped at 244, which could be a limitation for certain network configurations. This summary provides an overview of the key aspects and constraints related to FabricPath interfaces as specified in the provided document, focusing on the licensing, configuration, and operational requirements that must be considered when implementing these interfaces on Cisco Nexus switches. The document provides a guide for configuring FabricPath interfaces on Cisco Nexus 7000 Series switches with F Series modules, which are required to enable the Enhanced Layer 2 feature. Before beginning any configurations, ensure that you have an F Series module installed and that FabricPath is enabled across all devices. You must also hold an Enhanced Layer 2 license. To configure FabricPath interfaces: 1. Enter global configuration mode with "config terminal". 2. Specify the interfaces to be configured as FabricPath interfaces using "interface
". 3. Set the switchport mode to fabricpath with "
switchport mode fabricpath". 4. Optionally, convert all CE interfaces on the F Series module to FabricPath interfaces with "system default switchport fabricpath". 5. Exit interface configuration mode with "exit". 6. Optional commands include displaying interface information with "show interface" and copying the running configuration to startup with "copy running-config startup-config". For configuring STP priority with Rapid PVST+: 1. Enter global configuration mode with "config terminal". 2. Set the spanning-tree VLAN priority using "spanning-tree vlan
priority
" for all Layer 2 gateway devices in the same STP domain. 3. Exit configuration mode with "exit". 4. Optionally, display a summary of STP settings with "show spanning-tree summary". 5. Copy the running configuration to startup with "copy running-config startup-config". The document also includes examples and command syntax for each step. This document provides detailed instructions and examples for configuring FabricPath interfaces on Cisco Nexus 7000 Series switches running NX-OS. The primary focus is on setting up Rapid PVST+ VLANs with a lower STP priority of 8192, as well as configuring Multiple Spanning-Tree (MST) instances across all devices in the network. It also covers optional steps to verify and save configuration changes. ### Key Steps: 1. **Enter Configuration Mode:** Use `config terminal` command to enter global configuration mode. 2. **Configure STP Priority for VLANs:** Apply the `spanning-tree vlan
priority
` command to set a lower priority across all Rapid PVST+ VLANs on FabricPath Layer 2 gateway interfaces. The recommended value is 8192. 3. **Exit Interface Configuration Mode:** Use `exit` to return to the global configuration mode after configuring the interface settings. 4. **Optional - Verify STP Information:** Optionally, use `show spanning-tree summary` to display information on STP configurations. 5. **Save Configuration:** To ensure that the configuration persists across reboots, use `copy running-config startup-config`. ### Additional for MST Configuration: 1. **Configure MST Instances with Priority 8192:** Use `spanning-tree mst
priority
` to set the STP priority uniformly across all MST instances on FabricPath Layer 2 gateway devices.
2. **Exit Interface Configuration Mode:** As previously, use `exit` to navigate back to global configuration mode after setting up MST configurations.
3. **Optional - Verify STP Information:** Optionally check STP status with `show spanning-tree summary`.
4. **Save Configuration:** Complete the process by copying running configuration to startup configuration using `copy running-config startup-config`.
### Prerequisites:
Ensure you are working on an F Series module.
Have FabricPath feature enabled across all devices.
Install Enhanced Layer 2 license if not already installed.
### Reference:
For more detailed information and additional commands, refer to the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Command Reference.
This guide ensures that the configuration is uniform across the FabricPath network, optimizing STP settings for efficient operation in a multi-switch environment.
To summarize the provided text regarding configuring STP domains attached to a FabricPath network and configuring a vPC+ switch ID, here are the key points for each task:
### Configuring STP Domain ID Attached to FabricPath Layer 2 Gateway:
1. **Prerequisites**: Ensure you're working on an F Series module, have enabled the FabricPath feature on all devices, and installed the Enhanced Layer 2 license.
2. **Steps**:
Enter global configuration mode with `config terminal`.
Assign an STP domain ID using the command `spanning-tree domain domain-id`, where the range is from 1 to 1023.
Exit configuration mode with `exit`.
Optionally, check the STP summary with `show spanning-tree summary`.
Copy the running configuration to the startup configuration with `copy running-config startup-config`.
### Configuring a vPC+ Switch ID:
1. **Prerequisites**: Ensure you're working on an F Series module, have enabled the vPC and FabricPath features, and are in the correct VDC (or use `switchto vdc`).
2. **Steps**:
Enter global configuration mode with `configure terminal`.
Create a vPC+ domain using `vpc domain domain-id` and enter the vpc-domain configuration mode.
Assign a static vPC+ ID using `fabricpath switch-id switch-id`, where the range is from 0 to 4094.
This static ID is the virtual switch ID for FabricPath encapsulation. Ensure this ID is assigned to each of the two vPC+ peer devices before they can form an adjacency.
### Verifying FabricPath Interface Configuration:
**To display information**: Use commands such as `show feature-set`, `show interface brief`, `show interface switchport`, or `show interface type {slot/port | channel-number} ` to verify the configuration.
These steps and checks ensure that your FabricPath network configurations are correctly set up, allowing for proper operation and management of Layer 2 interfaces in a Cisco Nexus 7000 Series switch.
The document outlines various commands and configurations for managing and configuring FabricPath interfaces in Cisco Nexus 7000 Series switches. It includes descriptions of how to display status information (interfaces, spanning-tree summary, fabricpath is-is database, vpc brief, vpc consistency-parameters, vpc peer-keepalive, vpc role, and vpc statistics), as well as commands for clearing counters and showing interface counters. The document also provides a step-by-step guide on how to enable FabricPath, configure interfaces as FabricPath interfaces, set STP priorities, configure STP domain IDs, and manage vPC+ configurations. It emphasizes the importance of following specific steps when configuring these settings and refers to other configuration guides for further information.
To summarize this information about configuring a vPC+ setup on Cisco Nexus 7000 Series devices using NX-OS, follow these steps:
1. Enter the fabricpath switch-id switch-id command in the vPC domain configuration mode.
2. On each peer link interface, enter the switchport mode fabricpath command in interface configuration mode.
3. For each vPC+ peer link port channel, enter the no shutdown command.
4. Save the configuration using the save running-config startup-config command.
5. If you encounter situations where there is either no switchport mode FabricPath configuration on the peer-link interfaces or a mismatch between the configured FabricPath switch ID in the vPC domain and the switchport mode fabricpath configuration, follow these additional steps:
Enter the shutdown command on all the peer-link interfaces.
Then enter the no shutdown command on those interfaces.
6. Refer to Table 3-2 for feature history related to configuring FabricPath using the CLI.
7. For information about FabricPath forwarding, refer to Chapter 4 of the Cisco Nexus 7000 Series NX-OS FabricPath Configuration Guide, which covers prerequisites, guidelines, and limitations, as well as how to configure and verify a FabricPath configuration.
The text describes a network architecture called FabricPath, which is used to distribute and balance multicast traffic across multiple trees within a network. These trees are defined by Layer 2 IS-IS (Intermediate System-to-Intermediate System) and are based on a root switch chosen according to system ID. Multicast packets are distributed between the two main trees through a hash function, ensuring load balancing throughout the FabricPath network.
The architecture includes several components:
1. **FabricPath Layer 2 IS-IS**: This protocol defines the two forwarding trees in the network, with each tree having its own root determined by system ID configuration. The highest priority system ID is chosen for the first tree's root and a lower priority for the second tree's root.
2. **System ID Configuration**: Each device can configure its own system ID, which determines its position in the trees.
3. **Multicast Traffic Distribution**: Multicast traffic between the two trees is distributed based on a hash function applied to the ODA field within the FabricPath header of each packet.
4. **RPF Mechanism**: The reverse path forwarding (RPF) mechanism ensures that packets are received from the correct tree interface, dropping packets if they do not match the expected route.
5. **Link-State Information Flooding**: Layer 2 IS-IS is used to flood link-state information across the network, allowing all devices to share the same topology and forwarding information.
6. **VLAN Configuration**: The system automatically assigns FabricPath interfaces and VLANs to a single topology where all ports on the device are in the same virtual device context (VDC). Only active FP VLANs configured on each switch are advertised in Layer 2 IS-IS messages.
7. **Default VLAN Mode**: The default mode is Classical Ethernet (CE), but FabricPath interfaces and VLANs operate only on FP VLANs, with CE VLAN traffic not appearing on these interfaces. FP/CE VLANs interact with the network to carry specific types of traffic between switches and hosts.
The text also highlights that once configured, no further manual configuration is required for path assignment and load balancing as the system handles this automatically based on the topology defined by Layer 2 IS-IS.
The article discusses the implementation of FabricPath forwarding in a network environment. It highlights how encapsulated traffic is managed at the ingress switch by assigning ODA (Overlay Distribution Address) values. Once assigned, unicast packets are forwarded using Layer 2 IS-IS ECMP across up to 16 active paths. This setup allows for efficient load balancing of unicast traffic with up to 16 routes available per node. The article also introduces a loop-free broadcast functionality that handles multicast, unknown unicast, and multicast traffic through multiple system-created paths or trees, each identified by an FTag assigned at the ingress switch during encapsulation.
The network devices within the FabricPath network exchange topology information using IS-IS adjacencies to forward known unicast traffic flows based on available next hops. Each node in the network evaluates the FabricPath header for each traffic flow and chooses a forwarding path through ECMP. For broadcast, unknown unicast, and multicast traffic, the system creates two trees: one for broadcast traffic and another that load balances multicast across two trees per flow. The FTag assigned during encapsulation determines which loop-free tree such multidestination traffic follows.
The article also covers Layer 2 multicast multipathing where FabricPath uses a hash-based system to assign multicast flows to either of the two designated trees, ensuring balanced load distribution for multicast traffic across the network. This is facilitated by using both FabricPath Layer 2 IS-IS and Classical Ethernet IGMP snooping to learn and carry group membership information through the Network via Group Membership LSP (GM-LSP). The system ensures that multicast data packets are forwarded only to switches with interested receivers, maintaining a consistent view of forwarding trees across all nodes in the network.
The text discusses various aspects of FabricPath forwarding in Cisco Nexus 7000 Series switches, focusing on its scalability and high availability features. It explains how IGMP snooping helps to learn about multicast receivers and routers, creating an edge-port multicast state across the network. This setup uses GM LSPs for information propagation within the network.
The document also highlights that starting from Cisco Release 5.2(1), there are configurations available to enhance handling of multiple multicast groups. It mentions that PIM (Protocol Independent Multicast) is not necessary for Layer 2 multicast traffic when using FabricPath, and provides guidance on how Layer 3 multicast packets are handled with the ODA (Originating Designated Address).
Regarding high availability, the document states that FabricPath topologies maintain their configurations during ISSU (In-Service Software Upgrade). It also discusses the importance of having all interfaces for a single FabricPath network within the same Virtual Device Context (VDC), and provides specific port pairings or sets that must be in the same VDC due to the presence of multiple forwarding engines.
The text also covers load balancing using port channels, where traffic is distributed across all operational interfaces based on hashed addresses, selecting one link from a channel. This method ensures default load balancing with MAC, IP, or Layer 4 address selection capabilities depending on the configuration.
Finally, the document mentions licensing requirements for FabricPath forwarding and lists prerequisites such as understanding basic Ethernet Layer 2 operations and installing the necessary FabricPath feature set before enabling it on switches.
The text outlines steps and guidelines for configuring FabricPath on Cisco Nexus 7000 Series switches, specifically within the F Series modules. It emphasizes the importance of enabling the Enhanced Layer 2 license and ensuring that you are in the correct virtual device context (VDC). Key points include:
1. **Installation and Enablement**: The process involves installing and enabling the FabricPath feature set with the command `feature-set fabricpath`. It also notes potential system reloads if not done correctly, such as after a service failure or power-up in standby supervisor mode.
2. **Configuration Guidelines and Limitations**:
**FabricPath Interfaces**: These carry only FabricPath-encapsulated traffic.
**SPT (Shortest Path Tree)**: Does not run within a FabricPath network, avoiding routing loops.
**F Series Module Limitations**: Supports single SPAN destination ports and does not support multiple; VLANs in private VLANs must be of the same mode (CE or FP), with no FabricPath ports allowed in such VLANs.
**Static Addresses**: Hierarchical static MAC addresses and routes are unsupported, but user-configured static MACs are programmed on all forwarding engines for relevant VLANs.
3. **Default Settings**: The default settings for FabricPath topology is 0 (no specific topology), with the exception of FP VLANs automatically assigned to the FabricPath topology unless otherwise configured. The default VLAN mode is CE, and adjustments need to be made in the configuration interface by exiting VLAN mode after setting it.
4. **Multicast Traffic**: If multicast traffic sent to a group without receivers is present, it may not be constrained for OMF (router-optimized multicast flooding) entry based on VDC or per-VLAN but rather on a per-VDC basis. Use specific commands (`show fabricpath mroute vdc-omf` and `show fabricpath mroute omf resolved ftag`) to view these entries.
This summary provides a condensed overview of the main points for configuring FabricPath in a Cisco Nexus 7000 Series switch, particularly within the F Series modules.
This document provides a guide to configuring FabricPath forwarding on Cisco Nexus 7000 Series switches, specifically for F Series modules. The process involves setting the VLAN mode to either CE (Customer Edge) or FP (FabricPath), and then optionally configuring unicast or multicast load balancing for enhanced network performance.
The first step is to configure the global settings in terminal mode, creating and entering VLAN configurations with a specific ID. After that, you can set the VLAN mode to FabricPath using the 'mode fabricpath' command within the VLAN configuration mode. This setting allows the switch to use FabricPath features for better network efficiency.
For F1/MI VDCs, you may configure load balancing options like source, source-destination, XOR, destination, or symmetric. In contrast, F2 VDCs require specifying a port-channel and algorithm if needed, and enabling unicast load balancing with optional settings such as layer type (layer3, layer4, mixed) and rotation amount for VLAN inclusion.
Finally, the guide provides an option to copy running configurations to startup configuration for persistence across reboots. This process is crucial for ensuring that network settings are retained after a reboot or other operational interruptions.
This document outlines steps for configuring FabricPath forwarding on Cisco Nexus 7000 Series switches, specifically focusing on unicast load balancing. The process begins with entering global configuration mode using the 'config terminal' command. For F1/MI and F2 VDCs, specific commands are provided to configure port-channel load balance settings based on destination MAC or source IP-VLAN for specified modules.
For example:
To configure unicast load balancing in a F1/MI VDC, use 'fabricpath load-balance unicast layer3'.
In a F2 VDC, set up port-channel load balance with algorithms and specify modules if necessary.
Additional commands include adjusting rotation amounts for L3/L4 preferences and VLAN usage, which can be toggled between TRUE or FALSE depending on the configuration needs. The document also covers returning to default settings by using 'fabricpath load-balance unicast no' and optionally copying running configurations to startup configurations. Lastly, examples are provided demonstrating how to configure specific VDCs for both F1/MI and F2 VDCs regarding FabricPath unicast load balancing, including setting source IP-VLAN based selection in module 4 and destination MAC selection for other modules. The provided text discusses configuring FabricPath multicast load balancing on Cisco Nexus 7000 Series switches, specifically for F2 VDCs and modules. The steps include enabling the FabricPath feature set, configuring either source or source-destination load balancing for F1/MI VDCs, and port-channel load balancing for F2 VDCs. For F2 VDCs, specific configurations are detailed regarding destination MAC based selection and includes non-IP and IP protocols usage in hash calculations. The text also provides examples of commands to be executed and the purpose behind each step. The provided text outlines a set of commands and configurations for managing VLANs, load balancing, and ECMP (Equal Cost MultiPath) in a Cisco Nexus 7000 Series switch using the NX-OS operating system. These commands are configured within a specific Virtual Domain Context (VDC), which is necessary for advanced networking features such as FabricPath Forwarding. Key highlights of the configuration include: 1. **Port Channel Load-Balancing Configuration:** Commands to configure source IP, VLAN, and MAC based load balancing on port channels across different modules in a chassis are provided. For instance, configuring module 4 with "src ip-vlan" for its port channel hash ingress selection while retaining destination MAC based selection, and setting the rotate amount for load balancing at 3 bytes using a source IP VLAN based method. 2. **FabricPath Load-Balance Configuration:** Commands to configure FabricPath forwarding, specifically for multicast traffic. The configuration includes rotation of 2 bytes and VLAN excluded in hash calculation with a source based selection for module 4, and destination based selection for other modules in the F2 Fabricpath enabled VDC. 3. **ECMP Load-Balancing Configuration:** Commands to configure ECMP load balancing where L3/L4 preference is mixed, with rotate amounts set differently depending on the protocol (9 bytes for IP and 0x2 bytes for non-IP). The VLAN use varies between TRUE and FALSE across different configurations. 4. **Enhanced Multicast Scalability:** An optional feature introduced in Cisco Release 5/2(1) allows users to increase multicast scalability by aggregating routes and excluding FTag routes, which can be configured using the "fabricpath multicast aggregate-routes
" command. This is detailed with steps including entering global configuration mode, applying the route aggregation, displaying the applied configuration, and exiting configuration mode.
The text concludes with a note about increasing multicast scalability on F Series modules after ensuring appropriate licenses and feature set activation.
Overall, this document provides comprehensive guidance for network administrators to configure advanced networking features in a Cisco Nexus switch, optimizing performance through tailored load balancing strategies and VLAN management.
This documentation provides a comprehensive guide to configuring increased FabricPath multicast scalability on Cisco Nexus 7000 Series switches, specifically within the NX-OS environment. The process involves several steps and commands designed to ensure optimal performance of the network's forwarding capabilities for both unicast and multicast traffic.
Firstly, configuration begins with entering 'config terminal' mode followed by enabling the FabricPath feature set using the command 'feature-set fabricpath'. This sets up the necessary environment where FabricPath functionalities can be configured.
Next, commands such as 'fabricpath multicast aggregate-routes' are used to configure increased scalability for multicast routes. The configuration also includes detailed verification tools that allow users to display information about FabricPath forwarding (such as unicast and multicast routes), topology details, load balancing across interfaces, and the overall running configuration of the network settings related to FabricPath.
For instance, 'show fabricpath load-balance unicast' and 'show fabricpath load-balance multicast' commands provide real-time information about how these types of traffic are being handled by the system, including which interface is selected for specific flows based on criteria such as source IP address or destination IP address.
Additionally, the guide provides examples of what output looks like when using these command to verify configurations and troubleshoot issues related to FabricPath operations.
Overall, this documentation serves as a detailed manual for network administrators aiming to enhance multicast scalability in their NX-OS based networks through effective configuration and management of FabricPath features. It includes all necessary commands, outputs, and procedures needed to ensure that the setup is correctly implemented and maintained across different devices within the network infrastructure.
This document outlines steps and guidelines for configuring advanced features of Cisco Nexus 7000 Series NX-OS FabricPath using the CLI, including setting up VLANs in fabricpath mode, displaying configurations, saving them, and understanding licensing requirements. It also describes how to configure Layer 2 Intermediate System-to-Intermediate System (IS-IS) parameters for enhanced control over the network's operation. The document includes information about prerequisites, limitations, and detailed steps for applying these advanced features in a networking environment.
This document provides information about configuring and using Cisco Nexus 7000 Series switches for high availability, redundancy, and advanced FabricPath features. It highlights the importance of Virtual Device Contexts (VDCs), discusses prerequisites, licensing requirements, and outlines guidelines and limitations. Key points include:
1. **Virtual Device Contexts**: All interfaces on a single FabricPath network must be in the same VDC. This is crucial for proper operation and requires installing the FabricPath feature set before enabling it.
2. **VDC Configuration**: Ports 1-32 of F Series modules must be in the same VDC. Ensure you have an Enhanced Layer 2 license, are logged into the device, working on the F Series module, and installed the FabricPath feature set correctly.
3. **Prerequisites for FabricPath Advanced Features**: Users should have a basic understanding of classical Ethernet Layer 2 functioning, install the feature set in default and non-default VDCs, and ensure the standby supervisor is stable before activating FabricPath.
4. **Licensing Requirements**: Only devices with an Enhanced Layer 2 license can use advanced FabricPath features. For complete licensing information, refer to the Cisco Nexus 7000 Series Licensing Guide.
5. **Guidelines and Limitations**:
All F Series modules support only encapsulated traffic within a FabricPath network.
STP is not applicable in a FabricPath network.
Multi-SPAN destinations or virtual SPAN are not supported on the F Series module when using VDCs.
6. **Private VLAN Configuration**: Private VLAN configurations must have all VLANs either in CE (Customer Edge) or FP (FabricPath) mode, and FabricPath ports cannot be included. In summary, this guide provides a comprehensive set of instructions for setting up and configuring Cisco Nexus 7000 Series switches to support advanced networking features using the NX-OS operating system. The text discusses configuring advanced parameters for the FabricPath Layer 2 IS-IS protocol on Cisco Nexus 7000 Series F Series modules. It explains that while the protocol works automatically once enabled, optional global and per-interface configurations can be set up. These include setting authentication checks, logging adjacency changes, adjusting LSP generation intervals and MTU sizes, configuring graceful restart settings, managing hostname dynamics, and setting root priority values. To implement these configurations, one must enter global configuration mode, specify the FabricPath domain as default, and then configure optional parameters such as authentication type (cleartext or md5), key-chain for authentication, logging adjacency changes, LSP generation intervals, maximum path forwarding, reference bandwidth, SPF interval settings, graceful restart with manual T3 adjustment, hostname dynamics, and root priority values. After setting the desired configurations, it is recommended to check the running configuration and save them using 'show running-config' and 'copy running-config startup-config', respectively. This document outlines how to configure advanced FabricPath Layer 2 IS-IS parameters on a Cisco Nexus 7000 Series switch using NX-OS. The steps include setting various intervals and bandwidth configurations, as well as enabling or disabling features like graceful restart and dynamic hostname. Here's a summary of each step: 1. **Enable logging adjacency changes**: Configure the command `switch(config-fabricpath-isis)# log-adjacency-changes` to enable logging of IS-IS adjacency changes. The default is 'Off'. 2. **Configure LSP generation interval**: Use the command `switch(config-fabricpath-isis)# lsp-gen-interval msecs
`. Optional parameters include:
`max-wait` (default 8000 ms),
`lsp-initial-wait` (default 50 ms),
`lsp-second-wait` (default 50 ms).
3. **Set LSP MTU**: Use the command `switch(config-fabricpath-isis)# lsp-mtu mtu`. The range is from 128 to 4352, with a default of 1492. 4. **Configure maximum LSP lifetime**: Set the maximum LSP lifetime in seconds using `switch(config-fabricpath-isis)# max-lsp-lifetime secs`. The range is from 128 to 4352, and the default value is 1000 seconds. 5. **Set maximum paths per destination**: Use the command `switch(config-fabricpath-isis)# maximum-paths max-paths` with a range of 1 to 16, where the default is 4. 6. **Configure reference bandwidth**: Set the reference bandwidth using `switch(config-fabricpath-isis)# reference-bandwidth {ref-mbps
| ref-gbps
}`. The default value is 400000 Mbps, with a range from 1 to 400000 for `ref-mbps` and from 1 to 4000 for `ref-gbps`. 7. **Configure interval between LSA arrivals**: Use the command `switch(config-fabricpath-isis)# spf-interval msecs
`. Optional parameters include:
`spf-max-wait` (default 8000 ms),
`spf-initial-wait` (default 50 ms),
`spf-second-wait` (default 50 ms).
8. **Enable graceful restart**: Use the command `switch(config-fabricpath-isis)# graceful-restart
`. The default timer is set to 60 seconds, with a range from 30 to 65535. This feature is enabled by default.
9. **Enable dynamic hostname**: Use the command `switch(config-fabricpath-isis)# hostname dynamic` to enable dynamic hostname configuration for IS-IS. To disable it, enter the no form of this command.
This guide provides detailed instructions on how to adjust various parameters and features in a Cisco Nexus switch configured with FabricPath and Layer 2 IS-IS, ensuring optimal network performance and stability.
The summary provides a step-by-step guide on configuring advanced FabricPath Layer 2 IS-IS parameters using the `hostname` command in Cisco NX-OS switches. It outlines how to set up interface configurations for both global and per-interface settings, including optional features like authentication checks, key chains, and other protocol parameters such as CSNP (Complete Sequence Number PDU), hello interval, metric values, and more. The steps also cover exiting configuration modes, showing the running configuration, and copying it to the startup configuration. This guide is applicable for F Series modules with an Enhanced Layer 2 license enabled and FabricPath feature set activated.
The provided text outlines a series of steps and commands for configuring advanced FabricPath Layer 2 IS-IS parameters on Cisco Nexus 7000 Series switches. These include setting authentication type, interval settings between PDUs (like CSNP and LSP), padding configurations, metric values, retransmission intervals, and more. The process involves entering configuration mode with specific interface commands like `fabricpath isis`, followed by optional parameters such as `authentication-type`, `csnp-interval`, `hello-interval`, `hello-multiplier`, `hello-padding`, `lsp-interval`, `metric`, `retransmit-interval`, and `retransmit-throttle-interval`. These settings can be adjusted with ranges from 1 to 65535, except for the metric which has a specific range of 0 to 16777215. The default values vary across interfaces and some configurations must revert to defaults by entering `no` forms of the respective commands. After setting these parameters, users can optionally display or save the running configuration as detailed in Steps 13-16. This guide is part of the Cisco Nexus 7000 Series NX-OS FabricPath Configuration Guide and covers OL-22842-01, focusing on advanced features for configuring Layer 2 IS-IS networks.
This document provides a guide to clearing and verifying Advanced FabricPath configurations using Cisco Nexus 7000 Series NX-OS. To begin, ensure you are working on an F Series module and have the Enhanced Layer 2 license installed along with enabling the FabricPath feature set. The steps for clearing counters involve three optional commands: clear fabricpath isis adjacency to remove Layer 2 IS-IS adjacencies, clear fabricpath isis statistics to reset protocol statistics, and clear fabricpath isis traffic to erase traffic information. After performing these actions, verify the configurations using various show commands such as show fabricpath isis adjacency, show fabricpath isis database, and others listed in the document for further troubleshooting or monitoring of the network topology.
This document outlines various commands and features for managing and configuring FabricPath in Cisco Nexus switches. It includes show commands to display topology, traffic, IS-IS SSN (Sequence Number), and other related information. The article also provides a feature history table, configuration limits, and troubleshooting sections. Additionally, it discusses prerequisites, configurations, limitations, and the process of creating and managing vPCs (virtual Port Channels).
Comments