Those steps will not work when UCS Central is configured. Without the management pool IP address information available it will not show up as part of the UCS Domain. You can still add the nodes as individual SNMP hosts at the ESX layer(which is what we are doing), but it doesn't recognize it as part of the UCS Domain.
You have to enable and assign CIMC IP on blades.
Then add each blade as Node (ICMP polling only).
List should be populated with blades.
What you get as result?
Response Time, percent loss, status.
This is a simple ping to your blades.
I suggest to monitor servers using ESXi Host polling - via SNMP.
This will give you more overview on hardware.
For fast and decent alerting: UCS CallHome feature.
Can you explain more on this.
We do have a CMIC pool configured at UCS Central. However, it appears that configuring it at UCS Central causes UCS Master to report on the IP's differently. You can run the UCS HealCheck powershell script and see that the mgmt IP pool table is not filled out.
The UCS does not provide blade's IP addresses, so we are not able to map blades to nodes.
Only fabrics sys/switch-A and sys/switch-B have defined extIP.
All blades have extIP="0.0.0.0"
You must need to configure UCS to provide extIP for blades. Only then the status in Orion will be available .
Please run this tool - it will collect some data about UCS to xml file.
Cisco UCS Config Down loader Tool
Then please check the file how the UCS is configured.
Run it from CMD:
- UCSDownloadXML.exe /S:188.8.131.52 /U:User /P:password /O:output.xml
in a case you are using SSL:
- UCSDownloadXML.exe /SSL /S:184.108.40.206 /U:User /P:password /O:output.xml
S: - source IP address
U: - user
P: - password
O: - output file
I expect, in the file we will see that the blades don't have defined external ip addresses that are required by NPM as i have explained above .
If the USC will not provide external IP Address for blades NPM will failed to collect the data such as (ResponseTime / Percent Loss / Status ) for the servers.