Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Cisco UCS Monitoring - Chassis to Blades link

Hi All,

I have recently setup NPM to monitor our Cisco UCS installation.

I was hoping to be able to see our complete computing hierarchy from the physical blades(1) to the ESX(2) infrastructure to the VM's(3) themselves. As we know NPM already links 2 to 3 but the UCS chassis links to the KVM/Management IP of the blade not the ESX host

To me this doesn’t provide much useful information but as I have only just implemented this feature I wanted to ask the group, is the relationship to the management IP useful or would it be better to have the relationship to the box itself.

In our UCS implementation we use the server's hostname as the UCS profile name so the information could be pulled out to build the relationship, alternatively one could use the blade description field.

What are the community's thoughts on this?

Find more posts tagged with

Accepted answers

All comments

aaron_daniels

Bummer, wrong forum.
Can this please be moved to the NPM forum?