Nexus Hyperfabric Endpoint Target

Last updated
Save as PDF

A Nexus Hyperfabric Endpoint target connects Cisco Workflows to the Nexus Hyperfabric API. The target stores the controller endpoint referenced by Nexus Hyperfabric atomic workflows and Generic Hyperfabric API Request.

Before You Begin

Make sure you have:

Access to the Nexus Hyperfabric controller for your organization.
The controller host name. For the Cisco-hosted service, use hyperfabric.cisco.com.
A saved Nexus Hyperfabric Credentials account key.

Creating Nexus Hyperfabric Targets

In Workflows, go to Automation > Targets.
Select New Target.
Select Nexus Hyperfabric Endpoint.
Enter a display name and description.
Select a saved Nexus Hyperfabric Credentials account key.
In Connection, select HTTPS and enter the controller host name.
Enter a non-default controller port only when your deployment requires one.
Select Save.

Use the Hyperfabric atomic workflows for common fabric, device, VRF, VNI, and candidate-configuration operations. For an API operation without an atomic, use Generic Hyperfabric API Request with a relative API path such as /api/v1/fabrics?max=1.

Target Fields

Field	Required	Description
Protocol	Yes	HTTPS.
Host	Yes	Nexus Hyperfabric controller host. For Cisco-hosted Nexus Hyperfabric, use `hyperfabric.cisco.com`.
Port	No	Controller HTTPS port when a non-default port is required.