Monitoring Intersight managed Cisco UCS (help)
Summary: djAesthetic is transitioning from Cisco UCS Manager to Cisco Intersight for monitoring Cisco UCS fabric interconnects and blade servers. They are facing challenges as Intersight modules are limited to monitoring licensing, advisory alerts, and HyperFlex Clusters, and there's no UCS Manager API available. Daniel Blanco shares a similar experience with Intersight having deprecated API v2 for v3, criticizing the current LogicMonitor (LM) modules as ineffective. Patrick Rouse provides a link to an updated Intersight integration using the latest API, suggesting a possible solution to improve monitoring capabilities.
We’ve been monitoring our Cisco UCS fabric interconnects and blade servers via the traditional “Cisco UCS Monitoring” that targets UCSM (UCS Manager) directly. We’re in the process of moving to Cisco Intersight (which replaces UCS Central). The Intersight modules are limited strictly to monitoring licensing, advisory alerts, and HyperFlex Clusters. This is leaving me unclear as to how we could go about achieving parity visibility in to our new Fabric Interconnects and blades since there is no UCS Manager API to target when using Intersight.
Has anyone else successfully managed this yet (and if so what’s the trick)?
Daniel Blanco
·4 months agoBumping as we just tried the OOTB LM Intersight modules as well and as of today Cisco Intersight depreciated their API v2 and uses v3. The OOTB LM intersight DS/PS/AT can't use the v3 secret key.
But also these are pretty useless to us as we want to use this to see everything Intersight see's including all the devices managed thru it. We need a better DS is LM can provide one.
Patrick Rouse
·4 months agoThis Intersight integration uses the latest API:
https://www.logicmonitor.com/support/cisco-ucs-x-series-monitoring