Forrester: Demystifying Hybrid Solutions and Architectures
Hybrid infrastructure is a strategy, not a solution — and it's more than just cloud.
Why Customers Choose Us
Discover why the largest companies in the world choose Zenoss.
Customer Support Portal
Zenoss Learning Center
Zenoss Partner Portal
Become a Partner
Top 5 Focus Areas to Succeed With DevOps
Forrester shares the tools, technologies and best practices to meet the challenges of today's modern IT environments.
Learn. Discuss. Participate.
Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Hybrid IT Monitoring
Zenoss provides complete visibility into physical, virtual, cloud and converged environments.
Request A Demo
This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.
This ZenPack provides support for monitoring the Cisco UCS Central Infrastructure via the Cisco UCS Central XML API.
This ZenPack adds the following features to Zenoss.
The following components will be automatically discovered. The properties and relationships will be periodically remodeled to provide automatically up-to-date monitoring when the system configuration changes.
Zenoss periodically polls the UCS Central for faults and creates Zenoss events when they occur. The UCS Central fault life-cycle closely matches that of a Zenoss event. This means that corresponding Zenoss events will automatically clear when their UCS Central fault counterparts clear.
Note: UCS Central fault events may reoccur in Zenoss if they're closed in Zenoss, but not cleared on the UCS Central. For this reason it is recommended that the UCS Central fault events are acknowledged in Zenoss instead of closed until they are actually resolved on the UCS Central system.
Note: Zenoss attempts to set the timestamp on fault events to the timestamp the UCS Central reported their occurrence instead of the time that Zenoss collected them. For this reason it is recommended that both your UCS Centrals and Zenoss servers keep accurate time.
The following fields will be populated for each event.
The following additional fields and potentially more will also be populated for each event. These are the fields native to an Cisco UCS Central fault. If a fault occurs that has other fields, those fields will be added with the same cisco.ucsc prefix.
Zenoss supports Event Subscription feature of Cisco UCS Central. It provides a possibility to add/remove/update Zenoss components basing on the incoming events from Cisco UCS Central.
The following components are affected by this feature:
For UCS Domain component we accept updates only for the following attributes:
Please check Cisco UCS Central XML API for more details.
Use the following steps to start monitoring a Cisco UCS Central using the Zenoss web interface.
Alternatively you can use zenbatchload to add Cisco UCS Central Endpoints from the command line. To do this, you must create a file with contents similar to the following. Replace all values in angle brackets with your values minus the brackets. Multiple Cisco UCS Centrals can be added under the same /Devices/CiscoUCS/UCS-Central section.
my-ucsc setManageIp='192.168.0.1', zCiscoUCSCentralUsername='admin', zCiscoUCSCentralPassword='changeme'
You can then load the devices(s) with the following command.
Installing this ZenPack will add the following items to your Zenoss system.
View the discussion thread.
This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.