Release Notes for Cisco ACI APIC Connector Pack

Cisco UCS Director

Cisco UCS Director delivers unified, highly secure management for supported compute, network, storage, and virtualization platforms and for the industry's leading converged infrastructure solutions, which are based on the Cisco Unified Computing System (Cisco UCS) and Cisco Nexus platforms. Cisco UCS Director extends the unification of computing and network layers through Cisco UCS to provide data center administrators with comprehensive visibility and management capabilities for compute, network, storage, and virtualization. For more information, see Cisco UCS Director on

Revision History




August 22, 2018

Created for Release

Connector Pack

Connector packs help you perform connector level upgrade in Cisco UCS Director without impacting other connectors. After claiming Cisco UCS Director in Cisco Intersight, as a system administrator, you can view information on new versions of connector packs that are available for upgrade. The top header pane of the user interface displays a Download icon indicating that new connector pack versions are available. You can select and upgrade the connector packs in Cisco UCS Director.

Cisco Application Centric Infrastructure APIC Connector Pack

Cisco Application Centric Infrastructure (ACI) Cisco Application Policy Infrastructure Controller (APIC) connector pack provides the support for new versions of Cisco ACI APIC. Using the connector pack, you can upgrade to the latest version of Cisco ACI APIC. During the upgrade process, Cisco UCS Director gets restarted automatically.

Upgrading Connector Packs

  • You have system administrator privileges.

  • Cisco UCS Director has been claimed in Cisco Intersight. For information on claiming a device, see the integrated guided walkthrough titled Learn How to Claim a Device available within the Online Help menu in the Cisco Intersight user interface.

  • Cisco UCS Director is successfully connected to Cisco Intersight.

  • Take a snapshot of Cisco UCS Director before you initiate the upgrade.


Step 1

On the header, click Available Connector Packs for Upgrade.

The Available Connector Packs for Upgrade screen appears that displays a list of available connector packs for upgrade along with the version information. Clicking Yes in the pop-up message that appeared immediately after you logged in to the user interface will display this screen.


The Available Connector Packs for Upgrade icon is visible on the header only when new versions of the current running connector packs are available for upgrade.

Step 2

Check the check box of a connector pack from the list.

You can check the check boxes of multiple connector packs.

Step 3

Click Upgrade.

Step 4

In the Confirm Upgrade dialog box, click Yes.

After you confirm that the connector version must be upgraded, the validation process is initiated. If the validation process completes successfully, the upgrade process is initiated and the Connector Pack Upgrade Status screen displays the upgrade status. After the upgrade process is successful, the Logout option is enabled. Proceed to step 5.

Following are some of the possible outcomes of the validation and upgrade process:

  • If the validation process fails due to issues in the connector pack, the Connector Pack Validation screen is displayed with error details and corrective measures.

    Review the information and click Close.

  • If the connector pack upgrade process fails, click Logout.


    If any of the connector pack upgrade fails, the connector pack is rolled back to the earlier version.

  • The validation process fails if other users have logged in to the system or if workflows are in progress. An upgrade failure error message with appropriate corrective action is displayed.

    Review the corrective action, and click Force Upgrade to proceed with the connector pack upgrade.

    The Connector Pack Upgrade Status screen is displayed with current status for the connector pack upgrade request. The other users are automatically logged out of the system with a system broadcast message about the upgrade and are redirected to the login page.


    When a connector pack upgrade is in progress, and if another user with system administrator privileges logs in to the system, the Connector Pack Upgrade Status screen is displayed with the status of the upgrade process. When a connector pack upgrade is in progress, and if an end user logs in to the system, the system startup page is displayed.

Step 5

Click Logout.

You can login to Cisco UCS Director after the upgrade process is complete.

What to do next

You can view the upgrade reports by choosing Administration > System > Connector Pack Upgrades. From this screen, you can double-click on a report, and view additional details on the upgrade process. For more information, see Viewing Connector Pack Upgrade Information.

Viewing Connector Pack Upgrade Information


Step 1

Choose Administration > System.

Step 2

On the System page, click Connector Pack Upgrades.

Information such as upgrade request ID, user that initiated the upgrade, upgrade start time and end time, and the upgrade status are displayed.
Step 3

Select a connector pack and choose View Details to view details such as connector pack name, upgraded version, and prior version.

Step 4

Click State History to view the various states of the connector pack upgrade process. For example, upgrade request received, upgrade process initiated or upgrade process completed.

Step 5

Click Stages to view the entire lifecycle of the connector pack upgrade request.

New and Changed Features in Release

This section provides an overview of the significant new and changed features in this release.

  • Support for Policy-Based Redirect (PBR) which enables provisioning service appliances, such as firewalls or load balancers, as unmanaged nodes without requiring a Layer 4 to Layer 7 package.

  • Extended the PBR support in the existing functionality by adding provision to feed PBR specific attributes in tenant bridge domain, Layer 4 to Layer 7 device cluster, Layer 4 to Layer 7 service graph template, logical device context, and logical interface context.

The use case on how to deploy PBR in intra-VRF design is documented in the Cisco ACI Policy-Based Redirect Use Case on Cisco UCS Director guide.

Open Bugs

There are no open bugs in this release, at the moment.

Resolved Bugs

All resolved bugs for this release are available in the Cisco Bug Search Tool.

Bug ID



Fabric Membership Report Incorrectly Depicted

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the . RSS feeds are a free service.