Support Center

To better serve you during these uncertain times, we will be hosting a weekly support webinar. We’ll cover topics like LogicMonitor admin basics as well as ways to monitor a remote work environment. Tune in every Wednesday at 11:00am PST.

Sign up here

To better serve you during these uncertain times, we will be hosting a weekly support webinar. We’ll cover topics like LogicMonitor admin basics as well as ways to monitor a remote work environment. Tune in every Wednesday at 11:00am PST.

Sign up here

Cisco UCS Monitoring


Cisco UCS (Unified Computing System) is a data center product line composed of computing hardware, virtualization support, switching fabric, and management software. LogicMonitor gathers metrics for the system via the UCS Manager SOAP API. For more information on the metrics exposed via the API, see your API documentation, which is available at http://<your UCS Manager IP address>/docs.

UCS Manager is tied to a virtual IP address and the management database is replicated on the secondary Fabric Interconnect so failure of a single interconnect should not affect data collection.


As of early 2020, LogicMonitor’s Cisco UCS package is confirmed to be compatible with all current versions of Cisco UCS. As Cisco releases newer versions of UCS, LogicMonitor will test and extend coverage as necessary.

Setup Requirements

Add Resources Into Monitoring

For each Cisco UCS system you are monitoring, you must add the following three resources into monitoring from within the LogicMonitor interface:

  • UCS Manager
  • Fabric Interconnects (2)

For more information on adding resources into monitoring, see Adding Devices.

Obtain Credentials for UCS Manager

LogicMonitor must provide credentials when accessing the UCS Manager API. These credentials should belong to an API user account that is assigned the read-only role. For security purposes, it is strongly recommended that the user account does not have privileges above read-only as the majority of other available roles can make configuration changes using the API. For more information on creating UCS user accounts, see the Cisco UCS Manager GUI Configuration Guide.

Assign Properties to Resources

The following custom properties must be set on the Cisco UCS resources within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.



ucs_api.mgmt_host The IP address or FQDN of the UCS Manager.
ucs_api.user The UCS Manager username.
ucs_api.pass The UCS Manager password.
ucs_api.port (Optional) The port used to access the UCS Manager API. Defaults to 443 if not specified.

Import LogicModules

From the LogicMonitor repository, import all Cisco UCS LogicModules, which are listed in the LogicModules in Package section of this support article. If you were previously running the now-deprecated SNMP-based Cisco UCS LogicModules, see the Migration from Legacy Cisco UCS DataSources section of this support article for details on how to safely migrate to the new Cisco UCS DataSources.

Once the LogicModules are imported (assuming all previous setup requirements have been met), the PropertySource will automatically assign the appropriate values to the system.categories property for your Cisco UCS resources. This, in turn, will automatically associate the DataSources and data collection will begin.

Migration from Legacy Cisco UCS DataSources

In April of 2020, LogicMonitor released a new suite of Cisco UCS DataSources. The new DataSources query the UCS Manager API for data, whereas the prior suite relied on an SNMP collection method. Gathering metrics via the API offers many advantages, including:

  • Access to more data
  • Less network and interconnect resource usage, which allows DataSources to collect data at more frequent intervals
  • Easier setup and configuration

If you are currently monitoring Cisco UCS using the legacy DataSources, you will not experience any data loss upon importing the new DataSources. This is because DataSource names have been changed to eliminate module overwriting (the new DataSources feature underscores in their names whereas the legacy DataSources do not).

However, you will collect duplicate data and receive duplicate alerts for as long as both sets of DataSources are active. For this reason, we recommend that you disable the legacy Cisco UCS DataSources after importing the new set of DataSources and confirming that they are working as intended in your environment.

When a DataSource is disabled, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSources altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSources, see Disabling Monitoring for a DataSource or Instance.

LogicModules in Package

LogicMonitor’s package for Cisco UCS consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.


Display Name



addCategory_Cisco_UCS n/a PropertySource Adds either "CiscoUCSFabricInterconnect" or "CiscoUCSManager" as a value to the resource’s system.categories property, depending on the resource’s properties.
Cisco_UCS_FabricInterconnect Cisco UCS Fabric Interconnect DataSource Performance and port summary metrics for the Fabric Interconnect.
Cisco_UCS_ChassisUtilization UCS Chassis Slots DataSource Status metrics for chassis slots.
Cisco_UCS_BladeServers UCS Blade Servers DataSource Performance metrics for Blade Servers.
Cisco_UCS_RackServers UCS Rack Servers DataSource Performance metrics for Rack Servers.
Cisco_UCS_Ports UCS Ports DataSource Performance and status metrics for individual Fabric Interconnect ports.
Cisco_UCS_Disks UCS Disks DataSource Status metrics for server and storage array disks.
Cisco_UCS_Faults UCS Faults DataSource Creates an instance for each fault in the fault table and gathers fault related metrics.

When setting static datapoint thresholds on the various metrics tracked by this package’s DataSources, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.

In this Article: