Cisco Nexus Hyperfabric Release Notes, 2026
Available Languages
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- US/Canada 800-553-2447
- Worldwide Support Phone Numbers
- All Tools
Feedback
Feedback
Required Nexus Hyperfabric switch software version for new features
Cisco Nexus Hyperfabric enables customers easily to design, deploy, and scale any number of data center fabrics located anywhere. Delivered as a fabric-as-a-service solution, it reinvents and simplifies every step of IT operations, ensuring repeatable and predictable outcomes.
Note
Software version 20250320 had its end of support on October 15, 2025. If any devices in a fabric are running this version, in the Cisco Nexus Hyperfabric GUI, you will see a banner with text similar to this example:
Fabric1 device software approaching targeted end of support
You have less than one month to upgrade your devices to a newer version go to software management.
Fabric1 is the name of your fabric. You must upgrade the software of the devices to a supported version.
Cisco Nexus Hyperfabric is a data center fabric-as-a-service solution that consists of two components:
● Cloud controller—A scalable, globally distributed multitenant cloud service that is used to design, plan, control, upgrade, and monitor fabrics using a browser or APIs.
● Cisco 6000 series switches—Installed with Cisco Nexus Hyperfabric–managed software, the 6000 series switches connect to the cloud for centralized real-time visibility and control.
This document describes the features, issues, and scale limits for Cisco Nexus Hyperfabric.
New features in March 2026
Table 1. New hardware and software features for Nexus Hyperfabric in March 2026
| Feature |
Description |
| IP SLA tracking for static routes |
Monitors the health of your network services by sending probes from switches to destinations. If a service becomes unresponsive, the system automatically updates your routing table to prevent traffic loss and restores the path once the service recovers. This allows you to monitor real-time connectivity and troubleshoot issues by identifying exactly which routes are affected by service failures. For more information, refer to Cisco Nexus Hyperfabric — IP SLA Tracking. |
| QoS and traffic classification |
Manages network resources by classifying traffic into specific queues using DSCP labels. This allows you to prioritize critical applications and guarantee bandwidth for demanding workloads, such as AI storage. This keeps your most important data moving smoothly and prevents congestion by effectively managing how bandwidth is shared across the fabric. For more information, refer to Cisco Nexus Hyperfabric — Quality of Service (QoS) and Traffic Classification. |
| Multi-Site preview |
Interconnects multiple fabrics, allowing them to function as a unified network. Multi-Site provides these benefits:
● Centralized management: You can manage all fabrics from a single point.
● Resiliency: If one fabric encounters issues, other fabrics can remain operational.
● Optimized resources: You can distribute applications and services among the fabrics for best performance.
Currently, you can use a preview of this feature to see what is upcoming. The preview is not for production use. For more information, see Cisco Nexus Hyperfabric — Multi-Site. |
New features in January 2026
Table 2. New hardware and software features for Nexus Hyperfabric in January 2026
| Feature |
Description |
| BGP peering from host interfaces |
Establishes BGP sessions between the fabric and devices within a data center's logical network subnet. This ensures routing stability and continuous connectivity even when workloads migrate to different physical hosts. For more information, see Cisco Nexus Hyperfabric — Configure BGP. |
| Splunk webhook endpoints |
Integrate Splunk with Cisco Nexus Hyperfabric to export actionable alerts. This feature allows you to send assertion details directly to your Splunk environment using an HTTP Event Collector (HEC). Each notification includes a timestamp, criticality level, and a breadcrumb link back to the associated fabric blueprint. For more information, see Cisco Nexus Hyperfabric — Notifications. |
| Import the same fabric blueprint into organization and cloning a fabric blueprint |
Imports a fabric blueprint into an organization that already has that fabric blueprint, but you must give the imported blueprint a new name. You can also clone a fabric blueprint to create a duplicate in the organization, but you also must give the clone a new name. For more information, see Cisco Nexus Hyperfabric — Configure Fabrics. |
| Removal of the "classic" fabric mode |
The "Classic" fabric mode has been removed. There is now only one fabric mode, which does not have a special label in the GUI. Nexus Hyperfabric automatically migrates all classic fabrics to the one (and only) fabric mode. |
Required Nexus Hyperfabric switch software version for new features
This table shows which Nexus Hyperfabric switch software version added support for the specified Cisco Nexus Hyperfabric features.
Table 3. Required Nexus Hyperfabric switch software version for new features
| Switch software version |
Supported Cisco Nexus Hyperfabric features |
| 20260217 |
● Multi-Site preview
● IP SLA tracking for static routes
● QoS and traffic classification
|
| 20260109 |
BGP peering from host interfaces |
To see additional information about the caveats, click the bug ID to access the Bug Search Tool (BST).
Table 4. Resolved issues for Nexus Hyperfabric in January 2026
| Bug ID |
Description |
| In HF6100 switches running the Hyperfabric OS and managed by Nexus Hyperfabric, under rare conditions ARP can fail to synchronize across VTEPs for ESI port channels, leading to traffic getting dropped. |
To see additional information about the caveats, click the bug ID to access the Bug Search Tool (BST).
Table 5. Open issues for Nexus Hyperfabric in January 2026
| Bug ID |
Description |
| N/A |
There are no open issues for this month. |
Table 6. Verified scalability limits for Nexus Hyperfabric
| Feature |
Scale limits |
| Topology per fabric |
● Switches: 64
● Servers: 64
|
| Port configuration |
● Port channels per fabric: 50
● Physical ports per port channel: 4
● Breakout-enabled ports per switch: 32
● Routed sub-interfaces per physical port: 100
|
| Layer 2 scale per fabric |
● VLANs: 256
● PVST+ instances: 256
● MAC, IPv4/MAC, and IPv6/MAC endpoints (EVPN type-2 routes): 15,000
|
| IP scale per fabric |
● VRF instances: 10
● SVIs: 256
● IPv4 routes: 50,000
● IPv6 routes: 5,000
● IPv4+IPv6 routes: 55,000
● ECMP paths: 4
● Static routes: 1,000
● External BGP sessions: 20 peers per switch
◦ These are external and do not reflect the underlay BGP sessions.
● BGP import and export policies: 10
● DHCP relay VLANs: 32
|
You can access the Cisco Nexus Hyperfabric documentation from the following website:
https://www.cisco.com/c/en/us/support/data-center-networking/nexus-hyperfabric/series.html
| Document |
Description |
| Cisco Nexus Hyperfabric Release Notes |
This document. |
| Describes how to deploy Nexus Hyperfabric. |
|
| Describes the various Nexus Hyperfabric features and use cases. |
|
| Lists the licenses and notices for open source software used in this product. |
To provide technical feedback on this document, or to report an error or omission, send your comments to ciscohyperfabric-docfeedback@cisco.com.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2026 Cisco Systems, Inc. All rights reserved.