Cisco Nexus Hyperfabric Release Notes, 2025
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
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.
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 August 2025
Table 1. New hardware and software features for Nexus Hyperfabric in August 2025
| Feature |
Description |
| Introduction of Classic and Beta fabric mode |
Cisco Nexus Hyperfabric has two fabric modes: Classic and Beta. You must use the classic mode for non-AI clusters fabrics and beta mode for AI clusters fabrics.
● You can use the beta mode to create AI cluster fabrics.
● You can use the Fabric mode toggle to switch between the classic and beta mode. By default, the classic mode is enabled.
● You can view all fabrics from either mode from the Fabrics page. However, to view the detailed view of the classic fabric, you will be prompted to switch back to classic mode.
● For non-AI cluster fabrics, you should continue using the classic mode.
For more information, see Cisco Nexus Hyperfabric—Getting Started. |
| Root Certificates |
For classic fabric mode, you can configure switches to trust root certificates issued by their organization for establishing a secure Transport Layer Security (TLS) connection to Cisco Nexus Hyperfabric controller. For more information, see Cisco Nexus Hyperfabric—Getting Started. |
| Introduction of the label “Classic” to all existing fabrics |
In the Fabric page, a new label “Classic” is displayed next to the existing fabric name. For more information, see Cisco Nexus Hyperfabric—Getting Started. |
| New improved Switch view layout |
The Switch view now includes two new tabs:
● Port Status - which shows port and breakout details, and
● Face Plate -which displays switch model specific face plate information.
By default, the details view in this new layout is collapsed. For more information, see Cisco Nexus Hyperfabric—Configure Switches. |
| Enhancements to assertions |
The following enhancements for assertions are now available.
● Introduction of a new non-critical Warning (yellow) status for assertions that are lower in severity than Critical.
● In the Assertions page, you can now configure filters based on assertion Status, Latched state, and Type. By default, the assertions are filtered by Critical and Warning status and Latched state.
● In the Assertion page, switch assertions are now categorized into three types: Device, Port, and Network. You can also view the assertion counts for each severity level: Critical, Warning, Unknown, and OK.
By default, only the Critical assertion count is shown in the left navigation.
● You can view the port assertions in the Port Details page.
For more information, see Cisco Nexus Hyperfabric - Assertions. |
Open issues
To see additional information about the caveats, click the bug ID to access the Bug Search Tool (BST).
Table 2. Open issues for Nexus Hyperfabric in August 2025
| Bug ID |
Description |
| Nexus Hyperfabric UI does not display JSON diff in the Review Configuration page. |
New features in July 2025
Table 3. New hardware and software features for Nexus Hyperfabric in July 2025
| Feature |
Description |
| Cisco Nexus Hyperfabric Subscription |
Subscriptions are required to use Cisco Nexus Hyperfabric. Subscriptions provide entitlements that bind devices like Cisco 6000 series switches within an organization’s fabrics. Cisco Nexus Hyperfabric subscriptions come with embedded support contracts and allow entitled device owners to access Cisco Technical Support for software and hardware related issues. For more information, see Cisco Nexus Hyperfabric—Subscription |
New features in June 2025
Table 4. New hardware and software features for Nexus Hyperfabric in June 2025
| Feature |
Description |
| Claim a discovered device without using a claim code |
After you have claimed at least one device using a claim code, you can claim additional discovered devices without using claim codes. For more information, see Cisco Nexus Hyperfabric—Getting Started. |
| Software lifecycle management |
Cisco Nexus Hyperfabric simplifies the task of upgrading the software of the devices in your fabric by enabling you to upgrade the software with minimal effort. Cisco Nexus Hyperfabric can upgrade the software after you bind the devices to a fabric or while the devices are already bound to a fabric. For more information, see Cisco Nexus Hyperfabric—Software lifecycle management. |
| Mobile-friendly web page for deploying your fabric on site |
A network administrator can give a URL for a mobile-friendly web page of a fabric blueprint to the network cabling technicians. A technician can open the URL on a mobile device to view the blueprint and follow that to set up the physical fabric topology or to view the status of the fabric. This is an additional method instead of only being able to use the main Cisco Nexus Hyperfabric GUI to perform these tasks. For more information, see Cisco Nexus Hyperfabric—Deploying Your Fabric on Site. |
| Notifications |
The Notifications feature allows users to receive alerts about fabric-related events via email or Amazon S3 endpoints. Notifications are triggered by changes in latched assertions and follow timing methods of 30 seconds or five minutes, depending on state changes. For more information, see Cisco Nexus Hyperfabric - Notifications. |
| View BGP peer details |
You can now view BGP peer details and received route details. For more information, see Cisco Nexus Hyperfabric—Configure BGP. |
New features in May 2025
Table 5. New hardware and software features for Nexus Hyperfabric in May 2025
| Feature |
Description |
| Import a fabric blueprint |
If you have a JSON file of a fabric blueprint, you can import that blueprint into your Cisco Nexus Hyperfabric organization to create a new fabric blueprint. For more information, see Cisco Nexus Hyperfabric—Getting Started. |
| Switch cloud connectivity status |
You can verify the cloud connectivity status of the switches, including the source IP port, connection path, and transport layer security (TLS) certificate chain. For more information, see Cisco Nexus Hyperfabric—Getting Started. |
| View inventory details |
In Inventory, you can view all the devices that are claimed and bound to a fabric for an organization and also view all the claimed devices that are not bound to a fabric. For more information, see Cisco Nexus Hyperfabric—Configure Switches. |
| Request an estimate ID for a bill of materials |
When you request an estimate ID for a bill of materials (BOM), Cisco Nexus Hyperfabric communicates with the Cisco Commerce Workspace (CCW) to create the estimate and sends you an email with the estimate ID. You can then work with your partner or sales team contacts to discuss the estimate and order the parts. For more information, see Cisco Nexus Hyperfabric—Getting Started. |
| Nexus Hyperfabric On-site |
The Helping Hands feature of Cisco Nexus Hyperfabric is now called On-site. For more information, see Cisco Nexus Hyperfabric—On-site. |
New features in April 2025
Table 6. New hardware and software features for Nexus Hyperfabric in April 2025
| Feature |
Description |
| Helping Hands |
The Helping Hands feature of Cisco Nexus Hyperfabric greatly simplifies cabling operations of the switches in a fabric. A network administrator uses Cisco Nexus Hyperfabric to create a blueprint that automatically includes a cabling plan for the switches. You can then go to the on-site page and follow the tasks to set up the physical fabric topology or to view the status of the fabric. For more information, see Cisco Nexus Hyperfabric—Helping Hands. |
New features in March 2025
Table 7. New hardware and software features for Nexus Hyperfabric in March 2025
| Feature |
Description |
| Cisco 6000 Series Switches |
Introducing Cisco HF6100 switch models.
● HF6100-32D: Cisco 6000 Hyperfabric switch with 32x 40/100/200/400Gb QSFP-DD.
● HF6100-60L4D: Cisco 6000 Hyperfabric switch with 60x 10/25/50G SFP56 and 4x 100/400Gb QSFP-DD.
|
| Cisco Nexus Hyperfabric |
A scalable, globally distributed, multi-tenant cloud-based software-as-a-service (SaaS) network infrastructure management solution. The Cisco Nexus Hyperfabric service is hosted and operated by Cisco and is the single point of provisioning and visibility for your fabrics. The fabrics can be mesh or spine-leaf topologies and use EVPN VXLAN, Layer 2 VLANs, or IPv4/IPv6 routing. |
To see additional information about the caveats, click the bug ID to access the Bug Search Tool (BST).
Table 8. Resolved issues for Nexus Hyperfabric in June 2025
| Bug ID |
Description |
| When you click All Lanes button in the Fabric > Optics page to view optic lanes information, it does not display optic lanes information. |
|
| When you configure a VLAN tag greater than 3600, an error is raised. |
Table 9. Resolved issues for Nexus Hyperfabric in May 2025
| Bug ID |
Description |
| FRR BGP VRF configuration is not re-configured following a FRR crash. |
|
| If more than one Nexus Hyperfabric switches are unbonded, but configuration is committed in a single commit, the unbonded switches will not go through a reload and factory reset. |
|
| When Enable VLAN tagging is set to disable, sub interface is not displayed in Routed interfaces section in the corresponding VRF. |
To see additional information about the caveats, click the bug ID to access the Bug Search Tool (BST).
Table 10. Open issues for Nexus Hyperfabric in May 2025
| Bug ID |
Description |
| When you click All Lanes button in the Fabric > Optics page to view optic lanes information, it does not display optic lanes information. |
|
| When you configure a VLAN tag greater than 3600, an error is raised. |
Table 11. Verified scalability limits for Nexus Hyperfabric
| Feature |
Scale limits |
| Topology per fabric |
● Spine switches: 4
● Leaf switches: 32
|
| 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. |
|
| Open Source document for Cisco HF6100-32D and Cisco HF6100-60L4D |
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.
© 2025 Cisco Systems, Inc. All rights reserved.