New and Changed Information
The following table provides an overview of the significant changes up to this current release. The table does not provide an exhaustive list of all changes or of the new features up to this release.
Release Version | Feature | Description |
---|---|---|
NDFC release 12.2.2 |
Support for connecting fabrics using inter-fabric links with MACsec using a QKD server or a preshared key |
With this feature, you can connect two fabrics using inter-fabric links with Media Access Control Security (MACsec) using a quantum key distribution (QKD) server for secure exchange of encryption keys. Beginning with NDFC 12.2.2, NDFC added support for MACsec for inter-fabric links for the following fabric types:
Prior to NDFC 12.2.2, NDFC supported MACsec for intra-fabric links for the Data Center VXLAN EVPN fabric and the BGP fabric. For more information about configuring MACsec with or without QKD, see About Connecting Two Fabrics with MACsec Using QKD. |
About Connecting Two Fabrics with MACsec Using QKD
Media Access Control Security (MACsec) is the IEEE 802.1AE standard for authenticating and encrypting packets between two MACsec-capable devices.
With this feature, you can connect two fabrics using inter-fabric links with MACsec, either using a quantum key distribution (QKD) server for secure exchange of encryption keys, or by providing a preshared key. If you choose not to enable QKD, NDFC configures preshared keys supplied by the user instead of using quantum keys generated by the QKD server. You need to enable MACsec to enable the use of the QKD server for MACsec.
NDFC does not manage the QKD server.
Beginning with NDFC 12.2.2, NDFC added support for MACsec for inter-fabric links for the following fabric types:
-
Data Center VXLAN EVPN
-
Enhanced Classic LAN
-
External Connectivity Network
Prior to NDFC 12.2.2, NDFC supported MACsec for intra-fabric links for the Data Center VXLAN EVPN and the BGP fabrics.
The following sections provide information about connecting two fabrics with MACsec using QKD:
Benefits of Connecting Two Fabrics with MACsec Using QKD
-
Supports generation of quantum keys for encryption using a QKD server for protecting the privacy and authenticity of data.
-
Instead of using preshared keys between the endpoints, NDFC uses the keys from the QKD server that are difficult to break.
-
Helps to ensure data confidentiality by providing strong encryption at Layer 2 for VRF-Lite inter-fabric links. For more information, see the section "Create a VRF-Lite Inter-Fabric Link" in VRF Lite.
-
Provides a secure connectivity association between fabrics.
Supported Switches and Cisco NX-OS Releases for Connecting Two Fabrics with MACsec Using QKD
For more information about MACsec configuration, which includes supported platforms and releases, see the Configuring MACsec chapter in the Cisco Nexus 9000 Series NX-OS Security Configuration Guide.
Supported Configurations for Connecting Two Fabrics with MACsec Using QKD
You can connect two fabrics with MACsec using QKD for the following use cases:
Fabric Type | Fabric Type |
---|---|
Data Center VXLAN EVPN |
Data Center VXLAN EVPN |
Data Center VXLAN EVPN |
External Connectivity Network |
Data Center VXLAN EVPN |
Enhanced Classic LAN |
Enhanced Classic LAN |
Enhanced Classic LAN |
Enhanced Classic LAN |
External Connectivity Network |
Guidelines for Connecting Two Fabrics with MACsec Using QKD
-
You can change MACsec global parameters in the fabric settings at any time.
-
MACsec and CloudSec can coexist on a border gateway (BGW) device.
-
MACsec status of a link with MACsec enabled is displayed on the Links page.
-
Brownfield migration of devices with MACsec configured is supported using switch and interface freeform configurations.
Limitations for Connecting Two Fabrics with MACsec Using QKD
This feature does not support the following fabric types:
-
BGP
-
Campus VXLAN EVPN
-
VXLAN EVPN Multi-Site
This feature does not support inter-fabric links between two External Connectivity Network fabrics. You can use a freeform configuration to achieve this use case.
Workflow for Connecting Two Fabrics with MACsec Using QKD
-
Before enabling MACsec using QKD on the fabric and the associated switches, you need to do the following:
-
Create the RSA keys.
-
Associate the key pair to the trust point.
-
Get the signed certificate and upload it to NDFC. For more information, see Uploading a Certificate for Connecting Two Fabrics with MACsec Using QKD.
-
Manually add the signed certificate to the appropriate switches.
For more information, see the section "Configuring CAs and Digital Certificates" in the Cisco Nexus 9000 Series NX-OS Security Configuration Guide.
-
-
Create or edit one of the supported fabric types to enable MACsec and the QKD server.
For more information, see the following sections:
-
Create a VRF-Lite inter-fabric link or a Layer 2 inter-fabric link.
For more information, see the "Create a VRF-Lite Inter-Fabric Link" section or the "Create a Layer 2 DCI Link" section in VRF Lite.
Troubleshooting Connecting Two Fabrics with MACsec Using QKD
If you cannot configure MACsec with QKD on the physical interfaces of the link, an error displays when you click Save.
The error may occur for the following reasons:
-
You are not using the minimum required release version for Cisco NX-OS. For more information, see Supported Switches and Cisco NX-OS Releases for Connecting Two Fabrics with MACsec Using QKD.
-
The interface is not MACsec-capable.
Uploading a Certificate for Connecting Two Fabrics with MACsec Using QKD
-
Navigate to the Admin > Certificate Management > CA Certificates tab.
-
Click the Upload Certificate button.
The Upload Certificate - CA dialog box displays.
-
Drag and drop your CA certificate file to the dialog box or browse to the location of your certificate file.
The following are the accepted file types:
-
.pem
-
.cer
-
.key
-
.crt
-
-
Click Upload.
Editing Fabric Settings for Connecting Two Fabrics with MACsec Using QKD
Enable MACsec on the fabric and on each inter-fabric link to configure MACsec using a quantum key distribution server (QKD).
When you enable MACsec on an inter-fabric link, NDFC uses the local fabric settings for prepopulating the MACsec parameters. Switches in an External Connectivity Network fabric take MACsec settings from a Data Center VXLAN EVPN fabric or from an Enhanced Classic LAN fabric. An External Connectivity Network fabric, Data Center VXLAN EVPN fabric, or an Enhanced Classic LAN fabric can be either the source or the destination fabric.
Each MACsec-enabled inter-fabric link includes an override option to use the link’s local settings instead of from the fabric settings. The override option, Use Link MACsec Setting, allows switches in external fabrics to use a different QKD server from the one used in the Data Center VXLAN EVPN fabric or the Enhanced Classic LAN fabric. NDFC autopopulates MACsec parameters from the fabric settings if the Use Link MACsec Setting option is not enabled.
Editing Fabric Settings for an Enhanced Classic LAN Fabric for Enabling MACsec Using QKD
-
Choose Manage > Fabrics.
-
Choose an Enhanced Classic LAN fabric.
-
From the Actions drop-down list, choose Create Fabric to create a new fabric or Edit Fabric to edit an existing fabric.
If you are editing an Enhanced Classic LAN fabric, you can change MACsec parameters at any time. You need to perform a Recalculate and Deploy operation to generate new configurations based on the updated fabric settings.
-
Click the Security tab.
Field Description Enable DCI MACsec
Check the check box to enable MACsec on DCI links.
Enable QKD
Check the check box to enable the QKD server for generating quantum keys for encryption.
If you choose to not enable the Enable QKD option, NDFC uses preshared keys provided by the user instead of using the QKD server to generate the keys. If you disable the Enable QKD option, all the fields pertaining to QKD are grayed out.
DCI MACsec Cipher Suite
Choose one of the following DCI MACsec cipher suites for the DCI MACsec policy:
-
GCM-AES-128
-
GCM-AES-256
-
GCM-AES-XPN-128
-
GCM-AES-XPN-256
The default value is GCM-AES-XPN-256.
DCI MACsec Primary Key String
Specify a Cisco Type 7 encrypted octet string that is used for establishing the primary DCI MACsec session. For AES_256_CMAC, the key string length must be 130 and for AES_128_CMAC, the key string length must be 66. If these values are not specified correctly, an error is displayed when you save the fabric.
The default key lifetime is infinite.
DCI MACsec Primary Cryptographic Algorithm
Choose the cryptographic algorithm used for the primary key string. It can be AES_128_CMAC or AES_256_CMAC. The default value is AES_128_CMAC.
You can configure a fallback key on the device to initiate a backup session if the primary session fails.
DCI MACsec Fallback Key String
Specify a Cisco Type 7 encrypted octet string that is used for establishing a fallback MACsec session. For AES_256_CMAC, the key string length must be 130 and for AES_128_CMAC, the key string length must be 66. If these values are not specified correctly, an error is displayed when you save the fabric.
This parameter is mandatory if Enable QKD is not selected.
DCI MACsec Fallback Cryptographic Algorithm
Choose the cryptographic algorithm used for the fallback key string. It can be AES_128_CMAC or AES_256_CMAC. The default value is AES_128_CMAC.
QKD Profile Name
Specify the crypto profile name.
The maximum size of the crypto profile is 63.
KME Server IP
Specify the IPv4 address for the Key Management Entity (KME) server.
KME Server Port Number
Specify the port number for the KME server.
Trustpoint Label
Specify the authentication type trustpoint label.
The maximum size is 64.
Ignore Certificate
Enable this check box to skip verification of incoming certificates.
MACsec Status Report Timer
Specify the MACsec operational status periodic report timer in minutes.
-
-
Click Save to save the fabric settings.
-
From the Actions drop-down list, choose Recalculate and Deploy to apply the new MACsec settings to links that have MACsec enabled and where the Use Link MACsec Setting option is disabled.
Editing Fabric Settings for a Data Center VXLAN Fabric for Enabling MACsec Using QKD
-
Choose Manage > Fabrics.
-
Choose a Data Center VXLAN EVPN fabric.
-
From the Actions drop-down list, choose Edit Fabric to edit the fabric settings.
-
Click the Security tab.
The DCI MACsec parameters are the same as for the Enhanced Classic LAN fabric type, as the Data Center VXLAN EVPN fabric type has MACsec parameters for intra-fabric links. For more information, see Editing Fabric Settings for an Enhanced Classic LAN Fabric for Enabling MACsec Using QKD.
For more information about the remaining fields, see the section "Creating a VXLAN EVPN Fabric Using the Data Center VXLAN EVPN Template > MACsec" in Data Center VXLAN EVPN.
-
Click Save to configure the MACsec with QKD feature on each switch in the fabric.
-
From the Actions drop-down list, choose Recalculate and Deploy.
Editing Fabric Settings for an External Connectivity Network Fabric for Enabling MACsec Using QKD
With this release, no MACsec parameters are added to the External Connectivity Network fabric.
Switches in an External Connectivity Network fabric take MACsec settings from a Data Center VXLAN EVPN fabric or from an Enhanced Classic LAN fabric.
For more information, see the section "Creating an External Fabric" in External Connectivity Network.
Disabling MACsec Using QKD
The process described in this section is for disabling MACsec for an inter-fabric link for the supported fabric type. For the supported fabric types, see About Connecting Two Fabrics with MACsec Using QKD.
The following operations will disable MACsec and QKD from a link:
-
Disables MACsec on the inter-fabric link using QKD or a preshared key.
-
If this is the last link where MACsec is enabled, NDFC deletes the switch-level MACsec configuration from the switch.
-
Navigate to the Fabric Overview > Links tab.
-
Choose the link on which you want to disable MACsec with QKD.
-
From the Link Management - Edit Link page, navigate to the Security tab and unselect the following options:
-
Enable MACsec
-
Enable QKD
-
-
Click Save.
-
From the Fabric Overview > Switches tab, select Actions > Deploy to remove the MACsec configuration from the switch.
-
Copyright
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
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 included 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.
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.
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: http://www.cisco.com/go/trademarks. 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. (1110R)
© 2017-2024 Cisco Systems, Inc. All rights reserved.
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.
Need help?
- Open a Support Case
- (Requires a Cisco Service Contract)