FeedbackAbout Cisco SAE
The Cisco® Secure Agile Exchange (SAE) solution enables enterprises to interconnect users to applications quickly and securely by virtualizing the network edge (DMZ) and extending it to colocation centers, the crossroads of Internet traffic. For more information on the SAE solution, see Cisco Secure Agile Exchange (SAE) Solution Guide.
Find all the information you need about this SAE release—new features, known behavior, and related information, in this document.
 Note |
Explore Content Hub, the all new portal that offers an enhanced product documentation experience. Content Hub offers the following features to personalize your content experience.
|
What's New
-
Mixed SAE Versions Per Site: Supports mixed SAE release versions per site. This will allow users to take a step-by-step approach for upgrading sites with existing deployments from SAE 2.0.1 to 2.3.0 although SAE is versatile to deploy or modify services on sites with older SAE infrastructure releases.
-
VxLAN Traffic HandOff on External End Point: Supports VxLAN traffic hand off on external endpoint so that user can now specify VNID. In previous SAE release without this feature, user had to define VLAN ID on external endpoint and if required VxLAN handoff, SAE allocates VNID for it. So, user does not have the option to define VNID in Spine-Leaf infrastructure configuration.
Note
This feature is applicable only in case of Nexus 9000 Spine-Leaf infrastructure configuration.
-
Issues Fixed Since SAE 2.2: The following issues are fixed since SAE 2.2 release:
Bug IDs Description Clean-up action for service chain is stuck.
Custom template utils will allow single iteration or variable.
RO will check for enough CPUs when Affinity rules are used.
Known Issues
The following are known bugs associated with SAE. The table below provides a workaround to resolve them temporarily.
| Bug ID | Description and Workaround |
|---|---|
|
Description: SAE-ACI: Custom-template error when applying it on second Fabric as End-Point Gateway as NIC_1_IP_ADDRESS value is not provided by SAE. This issue could happen when second Fabric-as-End-Point Gateway is deployed with the custom template as same as the deployment of the first Fabric-as-End-Point Gateway. |
|
|
Description: VNFs recover would be failed from a down CSP to a live CSP in CSP non-Gluster mode. This issue could happen when recovering multiple VNFs by using "sae-actions recover-vnf-on-vim ..." request without waiting for the first vnf-recovery to be completed before issuing the second request for the second VNF recovery. |
|
|
Description: Ran out of IP addresses on fabric end of HA Half-Chain within Spine-Leaf or ACI environment. This issue could happen when assigning the CSPs from different clusters in Spine-Leaf or ACI environment to the resource zone(s) under a tenant. |
|
|
Description: Nexus 9000 NED migration in SAE 2.3 would fail in NSO GEO-HA with “Internal Error.” message. This issue could happen when migrating Nexus 9000 NED after upgrading the SAE pre-2.3 version to 2.3 in NSO GEO-HA environment. It wouldn’t happen in a standalone NSO. |
|
|
Description: When deploying a service, sometimes the service deployment would be failed as some of the VNF(s) in the service cannot be deployed by the assigned CSP with “Cannot set interface MAC/vlanid to 02:05:2a:43:4e:66/22 for ifname Eth4-2 vf 3: Resource temporarily unavailable” error message. This issue is caused by the current X710 driver running on the CSP. |
|
| CSCvw07383 |
Description: The first NIC port went down on X710 card after fresh-install or upgrade of the CSP. This issue could happen with CSP 2.8.0 or 2.9.0 within SAE 2.3. |
| CSCvw72380 |
Description: Failed to properly create cluster with gluster storage due to slow DNS look up. This issue may happen when storage network feature is enabled. ` |
| CSCvy42015 |
Description: NSO-Info does not display HA Info when a browser refresh is done on SAE GUI page. |
| CSCvw12259 |
Description: CSP's gets stuck in repository, when one node is down in cluster (GlusterFS). There is no workaround for it however it is observed that in other CSP GUI the Services tab would still function as expected. |