I wrote a script for a coworker who was at a customer site and needed to collect information from every blade in every UCS in the customer’s data center. The information to be collected was
Adapter Firmware Version
CIMC Firmware Version
Board Controller Firmware Version
Host Firmware Policy
When I started I was looping through the blades and for each blade making a series of cmdlet calls to retrieve the information related to each blade and the script ran very slow. In fact the information retrieval for the items above resulted in 5 Get-Ucs cmdlet calls per blade. If the UCS had 80 blades there would be 401 Get-Ucs cmdlet calls to retrieve all the information just for that one UCS. One call to get all the blades, plus 5 times the number of blades in the system of Get-Ucs cmdlet calls (4 Get-UcsFirmwareRunning calls and 1 Get-UcsServiceProfile). The script worked and it was good enough to get the job done perhaps if it was only going to be run once.
However it could be better, more efficient and take the number of Get-Ucs cmdlet calls from 1 + (5*#blades) per UCS domain to 3 per domain. That’s significantly better and the script will run much much faster. Think about the information that you need to retrieve and if there is a way to get more than just a single item per cmdlet call.
For the list above I know that I can get the blade dn and it’s AssignedToDn with a call to Get-UcsBlade, all the firmware information can be retrieved with a call to Get-UcsFirmwareRunning, finally the host firmware policy can be pulled from Get-UcsServiceProfile. Since I’m getting all the blades and looping through them, why can’t I also get ALL the firmware for all the blades and ALL the service profiles for all the blades and look through the retrieved objects. That is exactly what I did and resulted in the script below. I am filtering the results of two of my cmdlet calls, which is ok, but you could get all the firmware and all the service profiles, the script would still produce the same results, it just might run a slight bit slower.
Ucs-Blade-Info, get blade info from one ore more UCS Domains and output as CSV.DESCRIPTION
Ucs-Blade-Info, get blade info from one ore more UCS Domains and output as CSV.NOTES
John McDonough, Cisco Systems, Inc. (jomcdono).PARAMETER Ucs
Hi Team, I am using secured environment where python code is working fine but after converting the code to .exe file using pyinstaller it giving below error. Code for connecting to pod from ucsmsdk.ucshandle import UcsHandlehandle = U...
I am getting the below error while running the plugin: ./cisco_imc_nagiosError occurred while trying to import IMC Python SDK. Check if you are using the latest IMC Python SDK. Else check IMC Python SDK install guide for further information. we ...
I'm trying to use the Python uscmsdk library; however it's failing at the login with the error "Not supported on server". The code I'm using is equivalent to: "from ucsmsdk.ucshandle import UcsHandle# Create a connection handle handle = UcsHandle(<...
UCS always recommends to keep vNIC MTU same as that of assigned QoS policy priority class value.
Below warning appears when you assign QoS policy to any vNIC.
When the QoS policy is not assigned to vNIC, it takes the best-efforts cl...
I'm trying to install the IMC plugin 0.9.4. I'm running Nagios Core 4.4.5. There doesn't seem to have been any posts on this in a while I'm wondering if the plugin will still work? The install guide is dated 2017. I'm looking to monitor a UCS C2...