Cisco UCS monitoring doubt
Hello, Nowthat a new suite of data sources is available for the UCS stuff, we're havingsome doubts on the monitoring related with the Cisco UCS Manager & their respective components (Fabric Interconnects, etc...) I'm sure the new suite removes the needof 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 assumingthat 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 clarificationguys! Regards,
Monitoring Intersight managed Cisco UCS (help)
We’ve been monitoring ourCisco UCSfabric interconnects and blade serversvia the traditional “Cisco UCS Monitoring” that targets UCSM (UCS Manager) directly. We’re in the process of movingtoCisco Intersight(which replacesUCS Central). TheIntersightmodules arelimited strictly to monitoringlicensing, advisory alerts, and HyperFlex Clusters. This is leaving me unclear as tohowwe could go about achieving parity visibility in to ournew 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)?