About Cisco SAE GUI

The SAE GUI is installed on NSO. The GUI makes it fast and easy for you to design your services, create service catalogs, and deploy services.

GUI Features

The following sections list the new features that are supported on the Cisco Secure Agile Exchange GUI in the 2.x release.


The GUI supports the Google Chrome browser only.

New Features in Release 2.0.1

  • GUI Support for Physical Services: You can now create physical services using the Physical Services option under the Service Design section of the UI.

    • Support for Creating Physical Service Instances: You can now create a service instance for physical services by selecting the Physical Service Instance option under the Service Catalog section of the GUI. You can create service instances with specific configurations for each physical service. These configurations can be shared between physical service instances for the same physical service. You can also copy and edit an existing physical service instance and save it as a new one.

    • Support for Physical Services in Service Chain Instances: Support has been added to select a physical service at the time of creating a service chain instance under the Service Chain Instance option in the Service Catalog section of the GUI. This means that if a service chain has any physical Network Functions (PNFs) associated with it, they appear under the Service Chain Instance screen from where you can select them for each physical service.

    • Support to Add Physical Services to Service ChainsYou can now add physical services to a service chain by selecting the Add Physical Service option while creating a service chain. To do this, select the Service Chains option in the Service Designs section of the GUI.

  • Redeploying VNFs:The GUI now provides two ways to redeploy VNFs—recovering the VNF on the same CSP device or recovering the VNF on a different CSP device.

  • Viewing ESC Status and List of Services on CSP Devices: You can now view the status of ESC and the list of services on a CSP device on the Site Inventory page. To view the Site Inventory page, go to the Site section and select your site. Additionally, the CSP devices and switches are shown in separate tables below the ESC status. The CSP device table also displays the services on each CSP device ony our site.

  • Deploying and Undeploying Services on CSP Devices: The GUI now provides the option to deploy or undeploy services on a CSP device through the Site Inventory option under the Site section. The Deploy and Undeploy options are available in the Actions column of Site Inventory.

  • Export Device Details: You can export your devices and service chains as XML payloads through the GUI.

    • To export your devices, select Global > Devices. Next, click Export. This exports all the devices listed on the page as XML payloads.

    • To export your service chains, select Service Design > Service Chains. Next, click Export. All the service chains listed on the page as exported and downloaded to your system as XML payloads.

Enhancements in Release 2.0.1

The Devices page accessible from the Global section of the GUI now displays the site where the device is being used. The page also show the admin status of each device. Additionally, you can ping a device from the Devices page and check if the device status has changed at any point.

New Features in Release 2.0.0

Global Configuration

The Global area on the GUI lets you easily configure the following resources for global use within SAE.

  • IP Address Pools

  • ID Pool

  • Authentication

  • SAE Settings

  • Devices

Service Catalog

The Service Catalog area on the GUI lets you create the following:

  • Server Profiles: Server profiles define the server types and the type of physical interfaces that the server has.

  • Catalog: A service catalog is made up of server profiles.

  • Organization: This is your SAE site or provider.

  • Service Instances: Service instances are definitions of services in terms of how the services will be deployed.

  • Service Chain Instances: Refer to a common model for connecting the services together.

Service Design

The Service Design area of the GUI lets you design the following:

  • Services: These are blueprints for a service in terms of its deployment and operational behavior.

  • Service Chains: Service chains are a host of services that are brought together to connect providers and consumers.


The Site area of the GUI displays your existing sites and tenants and lets you create new sites, add resource zones and tenants to a site, view site inventory, and discover inventory. You can deploy service chains by clicking the tenants under your sites.

Important Information

  • If you delete a Service Instance, the service configuration associated with the instance is also deleted if the configuration is not being used by other service instances.

  • There are separate screens for adding provider-level and tenant-level endpoints. Provider endpoints can be viewed added by clicking a site. Tenant endpoints can be viewed and added by clicking any of the existing tenants. However, only provider endpoints can be added from the site view, and only tenant endpoints can be added from the tenant view.

  • Any service chains that you delete are moved to a list of deleted chains. This functionality addresses any instances of unintended deletions.

Known Behavior

Release 2.0.1

  • If a service profile is already connected to any of the SAPDs in a service chain, and you edit the flavor of the service profile, the service chain still shows the previous flavor.

  • You cannot perform the Save or Validate actions on a Site that you edit using the GUI under the following circumstances:

    • The site was not created through the GUI but site configuration was loaded into the GUI using load-merge

    • The site was created using NSO GUI, but the network type (NW_TYPE) was not set to SRIOV or VIRTIO


    This behavior does not apply if you create the site through the GUI or use the discovery feature in the GUI to discover your site.

Release 2.0.0

  • In the service chain work-flow, if the name that you give the service-profile is identical to an existing service-profile, the system replaces the previous entry with the new one.

  • In the service chain work-flow, if the name that you give an affinity is identical to an existing affinity name, the system replaces the previous entry with the new one.

  • In server profile for physical FTD devices, if you have the network type set to data, the GUI does not recognize it.

  • Creating a second virtual link connectivity between a service profile and a virtual link descriptor (VLD) overwrites the first connection. The system recognizes only one connection.


The behavior listed above does not apply to releases 2.0.1 and later.