I started playing with the Cisco UCSM Toolkit recently (currently in Beta) and with its 70 Cmdlets I have been able to automate quite a few actions in UCS that can often take up a fair amount of administrative effort. For me its extremely useful to be able to automate those initial configuration tasks that would be repeated on every UCS instillation. Working for a solutions provider I often have to install multiple UCS deployments and find allot of repetition.
Using UCSM’s XML API for all commination between the toolkit and UCSM instance. By creating the appropriate XML document for the API call it can then send it to the Web Service on all the UCSM instances.
So why is this UCSM ToolKit of interest?
Well not everyone can afford tools like UIM and EMC Bladelogic to automate the provisioning of the UCS components within a single UCS environment and also (more importantly) with multiple UCSM instances. By adopting the XML API, UCSM opens up the API to almost any scripting language in the future. Utilising the VMware PowerCli and the UCSM Toolkit, it is now possible to automate a huge chunk of a VMware on UCS deployment which has not been easy to achieve previously.
You don’t need a real UCS system.
Download the UCSM Toolkit here (you will need to register with Cisco) and follow the instructions in the user guide.
Using the UCS emulator you can perform pretty much every cmdlet that is in the Toolkit. The emulator runs as a VM and presents a small UCS B-Series environment that critically contains the XML API.
You can download the emulator here.
Here’s a really basic script that will connect to the UCSM server and create a new service profile then configure it with a description
# the bellow module contains the cmdlets
# connect to UCSM
connect-ucsm -Name 192.168.70.128
# Add a masic service profile and configure it.
add-serviceprofile -spname davetest | set-serviceprofile -Desc vmackem
# disconnect all UCSM Sessions