Link Search Menu Expand Document

What’s New

This page provides brief descriptions about new features in the recent Orchestrator release with links to additional information.

Orchestrator 9.3.1

The following features are introduced in Orchestrator 9.3.1.

Regional Loopback Orchestration

Loopback Orchestration now lets you associate a configured region with a loopback interface. You can also change the loopback pool subnet IP for a loopback interface. Using the new reclaim feature, you can return deleted loopback IP addresses to their original pools so they can be used again. See Loopback Orchestration. This topic has also been enhanced.

All Advanced Security Settings Selected for New Installations

By default, all settings on the Advanced Security Settings dialog box are now automatically enabled for new Orchestrator installations. Orchestrator upgrades retain previous advanced security settings except for Perform Additional Identity Verification on Web Sockets, which is always enabled and is no longer displayed as a setting on the Advanced Security Settings dialog box. See Advanced Security Settings. This is a new topic.

Business Intent Overlays

You can now set a Session Affinity Timeout for local breakout flows, and there is now a Fixed Order option for ranking links when using Waterfall for Link Selection. See Business Intent Overlays. This topic has also been enhanced.

RBAC Interop API Support

Starting with Orchestrator 9.3.0, RBAC affected both Orchestrator UI users and Orchestrator REST API users. In Orchestrator 9.3.0, endpoint definitions changed for Aruba EdgeConnect Orchestrator REST APIs. This required users to update endpoint definitions in their Orchestrator REST API scripts. To reduce the magnitude of change required, Orchestrator 9.3.1 provides the ability to enable support for Interop (before Orchestrator 9.3.0 release) API endpoints so you can continue using your existing Orchestrator REST API scripts for a specific list of frequently used commands (see Pre 9.3 API Endpoints).

You should be aware of the following:

  • To enable Interop API support, navigate to Orchestrator > Software & Setup > Setup > Advanced Properties, and then set the enableLegacyApisSupport property to True.

    NOTE: It is recommended that you restart Orchestrator during a maintenance window.

  • RBAC settings affect users accessing the Orchestrator UI as well as the Orchestrator REST APIs, regardless of whether authentication is via login/password (role associated with the user) or via an API key (role associated with the API key).

  • For RBAC users, the RBAC filter will be applied to any legacy Orchestrator REST API calls (for releases before 9.3.0).

    NOTE: For non-RBAC users, the RBAC filter is disabled or will not be applied.

  • An API endpoint (rbac/legacyApi) has been introduced to add an Interop API pattern that is not already in the Interop list (see Pre 9.3 API Endpoints). You must test and verify that the pattern in the database does not create issues.

  • REST request performance will be impacted due to increased latency in request filtering and routing of Interop REST APIs. It is recommended that all scripts be modified to adapt to the Orchestrator 9.3 REST API endpoints.

For information about enabling Interop API support, see Orchestrator Advanced Properties. For information about using Interop APIs, see Pre 9.3 API Endpoints.

Dark Theme

Orchestrator provides a new dark theme. You can toggle between light and dark themes by clicking the sun or moon icon (img or img) in the upper-right corner of the Orchestrator application. See Light or Dark Theme.

Back to top

© Copyright 2023 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to Aruba EULA.

Open Source Code:

Hewlett Packard Enterprise Company
Attn: General Counsel
WW Corporate Headquarters
1701 E Mossy Oaks Rd Spring, TX 77389
United States of America