Showing results for 
Search instead for 
Did you mean: 
Cisco Employee
Cisco Employee

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

  • Server
  • Service Profile
  • Adapter Firmware Version
  • CIMC Firmware Version
  • BIOS 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

The UCS hostame or IP address .PARAMETER UcsUser

A UCS user name .PARAMETER UcsPass

The user's password .EXAMPLE

Ucs-Blade-Info.ps1 -Ucs "" -UcsUser admin -UcsPass admin123Ucs-Blade-Info.ps1 -Ucs "," -UcsUser admin -UcsPass admin123 #>

param(   [Parameter(Mandatory=$true,HelpMessage="Enter a comma separated UCS hostname or IP address list")]     [string] $Ucs,   [Parameter(Mandatory=$true,HelpMessage="Enter UCS user")]     [string] $UcsUser,       [Parameter(Mandatory=$true,HelpMessage="Enter UCS user's Password")]     [string] $UcsPass


# Connect to UCS System

  Import-Module CiscoUCSPS -ErrorAction SilentlyContinue   Set-UcsPowerToolConfiguration -SupportMultipleDefaultUcs:$true > $null;   

  $password    = convertto-securestring -Force -AsPlainText $UcsPass;

  $credentials = new-object -typename System.Management.Automation.PSCredential -argumentlist $UcsUser,$password;

  $ucsms = $Ucs.Split(","); 

  Connect-Ucs  $ucsms -Credential $credentials > $null;  

  "UCS,Server,Service profile,Adapter firmware,CIMC firmware,BIOS,Board controller firmware,Host firmware policy";   $Firmware         = Get-UcsFirmwareRunning -Filter "dn -ilike sys/chassis-*/blade-*"; 

  $ServiceProfiles = Get-UcsServiceProfile -AssocState associated; 

  $Blades             = Get-UcsBlade;   $Blades | %{     $Blade  = $_;     $AdapterFirmVer     = $Firmware | ?{$_.dn -like $($Blade.dn + "/*") -and $_.Ucs -eq $Blade.Ucs -and $_.Type -eq "adaptor" -and $_.Deployment -eq "system"} | Select-Object -ExpandProperty Version;   

    $CimcFirmVer        = $Firmware | ?{$_.dn -like $($Blade.dn + "/*") -and $_.Ucs -eq $Blade.Ucs -and $_.Type -eq "blade-controller" -and $_.Deployment -eq "system"} | Select-Object -ExpandProperty Version;   

    $BiosVer            = $Firmware | ?{$_.dn -like $($Blade.dn + "/*") -and $_.Ucs -eq $Blade.Ucs -and $_.Type -eq "blade-bios"} | Select-Object -ExpandProperty Version;   

    $BoardControllerVer = $Firmware | ?{$_.dn -like $($Blade.dn + "/*") -and $_.Ucs -eq $Blade.Ucs -and $_.Type -eq "board-controller"} | Select-Object -ExpandProperty Version;   

    $HostFirmWarePolicy = $ServiceProfiles | ?{$_.dn -eq $Blade.AssignedToDn -and $_.Ucs -eq $Blade.Ucs} | Select-Object -ExpandProperty OperHostFwPolicyName;     $Blade.Ucs + "," + $Blade.dn + "," + $Blade.AssignedToDn + "," + $AdapterFirmVer + "," + $CimcFirmVer + "," + $BiosVer + "," + $BoardControllerVer + "," + $HostFirmWarePolicy;   }   Disconnect-Ucs; 

  Set-UcsPowerToolConfiguration -SupportMultipleDefaultUcs:$false > $null

Hope this helps.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers