Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
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 XML API. To see the metrics exposed via the UCS Manager XML API, refer to your API documentation at http://<your UCS Manager IP address>/docs.
http://<your UCS Manager IP address>/docs
LogicMonitor’s Cisco UCS suite supports monitoring Cisco UCS environments through two management tools offered by Cisco – Cisco UCS Manager (UCSM) or Cisco Integrated Management Controller (CIMC). UCSM environments will need their accompanying Fabric Interconnects (FI) added into LM for full monitoring coverage. The 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. CIMC devices are unmanaged standalone servers with an XML API that is consistent with the one used by UCSM.
As of August 2021, LogicMonitor’s Cisco UCS package is confirmed to be compatible with all current versions of Cisco UCS Manager XML API. As Cisco releases newer versions of this API, LogicMonitor will test and extend coverage as necessary.
The following steps are required to set up Cisco UCS Monitoring in your LogicMonitor environment.
If your UCS device is managed using CIMC, you only need to add the CIMC server into monitoring. However, UCSM environments must add the following three resources into monitoring from within the LogicMonitor interface for complete monitoring:
For more information on adding resources into monitoring, see Adding Devices.
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.
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.
Import all Cisco UCS LogicModules from the LogicMonitor public repository. See the list of LogicModules in Package. If these LogicModules are already present, make sure you have the most recent versions.
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.
LogicMonitor’s package for Cisco UCS consists of the following LogicModules. For full coverage, ensure that all of these LogicModules are imported into your LogicMonitor platform. The table also provides a reference for which UCS device type each module is compatible with.
When setting static datapoint thresholds on the various metrics tracked by the DataSources in this package, 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.
The SNMP-based Cisco UCS LogicModules were deprecated in June 2020. This section provides details on how to migrate to the new API-based 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:
The following table lists the deprecated SNMP modules and maps their functionality to the new API module(s).
If you are currently monitoring Cisco UCS devices using any of these legacy DataSources, you will not experience data loss upon importing the new DataSources. This is because DataSource names have been changed to eliminate module overwriting.
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 above-listed 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.
In This Article