Setting up a Cisco UCS Cluster or ACI Fabric Discovery
About Cisco UCS Cluster / ACI Fabric jobs
Device42 will poll your Cisco UCS (Unified Computing System) Manager to discover cluster device information or ACI (Application Centric Infrastructure) Fabric to discover your SDN (software defined networks).
UCS jobs will discover chassis, blades, and service profile information, while ACI jobs will discover network policy details that are controlling both your and/or physical network.
Should you be looking to discover a load balancer (which shares this discovery job page), see the F5/Load balancer discovery docs.
You may create a job via the main menu at Discovery > UCS/ACI/Load Balancers to add/manage UCS Manager(s).
Add your Cisco UCS (aka Unified Computing System) Manager or ACI (Application Centric Infrastructure) Fabric discovery job by entering one or more IPs or FQDNs, and credentials with permissions on the device (i.e., a valid username/password).
You can click on run now to run immediately or schedule it to run at certain times:
Scheduling UCS Cluster or ACI Fabric Discovery Jobs
Scheduling your autodiscovery job to run on a recurring basis; you can choose to run it on certain weekdays and/or at specific times each day.
UCS Cluster / ACI Fabric Discovery Option Definitions
Hostname to use: Discovered Name or Serial #; Choose the hostname format to use for newly discovered devices – option only exists for UCS & ACI devices.
Give precedence to hostname: Select to force overwrite the existing hostname in Device42 for devices that already exist using the hostname option in hostname to use – ACS/UCI only.
VRF Group for discovered devices: Place discovered devices into the following VRF group – UCS/ACI devices only.
Object Category for discovered devices: Place discovered objects into the chosen category in Device42 – UCS/ACI devices only.
Overwrite existing object categories: Select to force overwrite of category on devices that already exist in Device42 – UCS/ACI devices only.
Device and Chassis Names
If an existing device is not found for the chassis or the blade(based on the serial #), Device42 will add a new device. The Name is derived from the DN and the serial # of the device, whether it is a chassis or a blade.
Navigate to DataCenter > UCS Service Profiles to see the discovered service profiles. Service profiles show the Name, the DN, the UCSManager, and the Device association. You can search from the service profile list page and the search box on the dashboard.
Run Now or Schedule
Select Run Now from the list page to run the job right away.
Select Add another Autodiscovery Schedule from the when editing the job to create a run schedule for the job.
A note on autodiscovery scheduling behavior: newly created jobs will not run on the first day they are created, to prevent an unintended large amount of jobs from running initially. If you would like to run a job after its initial creation, simply select the “Run Now” button next to the job after creation.