Monitoring Intersight managed Cisco UCS (help)
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)?149Views3likes0CommentsCisco UCS monitoring doubt
Hello, Now that a new suite of data sources is available for the UCS stuff, we're having some doubts on the monitoring related with the Cisco UCS Manager & their respective components (Fabric Interconnects, etc...) I'm sure the new suite removes the need of the SNMP legacy datasources (that's great btw!!!), however, we're now kinda lost on what should we add into LM (in terms of components). I'm pretty sure in the past we had to add the UCS Manager + the Fabric Interconnect devices (to fetch some hardware related info that wasn't fetched via UCS Manager), but currently, I see the same datasources applied to the UCS & both Fabrics. I'm assuming that we only require to monitor the actual UCS Manager from now on (everything else will be monitored under it). Specially the hardware portion of both Fabric Interconnects (at least from what I'm seeing). Is my assumption correct? Or, is there anything else we need to have in mind in terms of the Fabrics. Appreciate the clarification guys! Regards,133Views0likes3Comments