How do I retrieve Fabric Interconnect serial numbers via XML API?

RE: UCS PowerTool and Pending Activities

2013-01-14T15:39:49Z

Hi Joe, You say you're adding vNICs to the service profile template, but rebooting blades. Have you unbound and re-bound the service profiles to the template? Sage

RE: How to start, stop, reboot a Blade Server via XML API

2012-10-08T14:39:49Z

Hi Helmut, I know you are specifically looking for help on this with XML. I just wanted to offer that there are a couple of other tools you can use to manage UCS. Like you I initially started with the XML API, but then I discovered the UCS PowerTool which is a powershell interface. Another option is GoUCS which I believe is more of a java centric approach. With the Powertool starting a service profile is as simple as: Get-UcsServiceProfile -Name esxhost01 | Set-UcsServerPower -State "admin-up" -Force Sage

RE: Powertool connection to UCS via AD?

2012-09-17T20:27:16Z

Hi Gary, Find out what the name of your authentication domain for active directory is. Then try passing in the user credential prefixed with "ucs-[name]/gary", replacing [name] with whatever your authentication domains name is. i.e. if you've got your authentication domain name set to ActitveDirectory, then login as "ucs-ActiveDirectory/gary" with your AD password. Sage

RE: Modify Boot Policy to service profile template

2012-07-31T15:03:49Z

Hi Matteo, You can do something like this: [code]Get-UcsServiceProfile -name spName | Set-UcsServiceProfile -BootPolicyName san_boot -Force or when you're done... Get-UcsServiceProfile -name spName | Set-UcsServiceProfile -BootPolicyName local_boot -Force[/code] That's assuming you've set up a boot policy called san_boot & local_boot, you've got boot luns built, presented, zoned, etc. The -Force just prevents confirmation that you want to change the boot policy setting. Sage

RE: Booting a service profile?

2012-07-24T15:54:56Z

That worked perfectly, thank you Bhaskar. Sage

Booting a service profile?

2012-07-17T21:01:52Z

I hate asking because I'm sure it's something super trivial but I just can't seem to find it. How do I power on a service profile by name? I just download .9.9 and I can't seem to find a boot/power option that works. Any help would be appreciated, thanks. Sage

RE: Collect CPU speeds via UCS PowerTool...

2012-05-23T18:45:54Z

John, Thank you very much that was exactly what I needed. Sage

Collect CPU speeds via UCS PowerTool...

2012-05-14T19:43:07Z

Hi all, I'm trying to get the CPU speed from the blades I have installed as part of an inventory script. The Get-UcsBlade commandlet gets me most of what I need, but I can't seem to find where I'd get the speeds from. Anyone have any suggestions? Thanks, Sage

RE: Gathering F/w details

2012-02-09T17:27:55Z

[quote] we are in the process of porting goucs to linux. we have a RC that I can send you. Please email me directly at goucs@cisco.com and I can send you a copy. Should be releasing it fully on CDN in a couple weeks. Eric[/quote] That will be fantastic, can't wait to check it out.

RE: Gathering F/w details

2012-02-09T17:02:44Z

Hi Vamsi, I had the need for something similar so I ended up using the XML API from a PHP script running on linux. This is what I use: [code] "http://ucs01/")); array_push($ucsDomains, array("url" => "http://ucs02/")); array_push($ucsDomains, array("url" => "http://ucs03/")); foreach($ucsDomains as $ucsDomain){ generateData($ucsDomain, $myLogin, $myPassword); } function generateData($details, $myLogin, $myPassword) { $chassisTypes = array( "N20-C6508" => "5108"); $Blades = array( "N20-B6620-1" => "B200 M1", "N20-B6625-1" => "B200 M2", "N20-B6625-2" => "B250 M2", "N20-B6730-1" => "B230 M1", "B230-BASE-M2" => "B230 M2", "N20-B6620-1" => "B200 M1", "N20-B6740-2" => "B440 M1"); $fabricInterconnects = array( "N10-S6100" => "6120XP", "N10-S6200" => "6140XP"); $url = $details['url']."nuova"; $aaaLogin = ""; $results = httpPost($url, $aaaLogin); $outCookie = $results->attributes()->outCookie; // Get Cluster name $xmlQuery = ""; $results = httpPost($url, $xmlQuery); $clusterName = $results->outConfigs->topSystem['name']; $xmlQuery =<< EOD; $results = httpPost($url, $xmlQuery); $firmwareBootUnit = $results->outConfigs->firmwareBootUnit; $fwResults = ""; foreach($firmwareBootUnit as $datum) { if ($datum['dn'] == "sys/mgmt/fw-boot-def/bootunit-system") { // Found UCSM $fwResults .= "$clusterName,UCSM,".$datum['version'].",".$datum['prevVersion'].",_".$datum['dn']."
\n"; } if (preg_match("/^sys\/(switch-[AB])\/mgmt\/fw-boot-def\/bootunit-kernel/", $datum['dn'])) { // Found a Fabric Interconnect $fwResults .= "$clusterName,Fabric Interconnect,".$datum['version'].",".$datum['prevVersion'].",_".$datum['dn']."
\n"; } if (preg_match("/^sys\/(chassis-[0-9]\/slot-[0-9])\/mgmt\/fw-boot-def\/bootunit-combined/", $datum['dn'])) { // Found an IOM $fwResults .= "$clusterName,Fabric Extender,".$datum['version'].",".$datum['prevVersion'].",".$datum['dn']."
\n"; } if (preg_match("/^sys\/(chassis-[0-9]\/blade-[0-9])\/mgmt\/fw-boot-def\/bootunit-combined/", $datum['dn'])) { // Found a CIMC $fwResults .= "$clusterName,CIMC,".$datum['version'].",".$datum['prevVersion'].",".$datum['dn']."
\n"; } if (strpos($datum['dn'], "bios")) { // Found a blade's BIOS $fwResults .= "$clusterName,Blade BIOS,".$datum['version'].",".$datum['prevVersion'].",".$datum['dn']."
\n"; } if (preg_match("/^sys\/(chassis-[0-9]\/blade-[0-9]\/adaptor-[0-9])\/mgmt\/fw-boot-def\/bootunit-combined/", $datum['dn'])) { // Found an Interface Card $fwResults .= "$clusterName,Interface Card,".$datum['version'].",".$datum['prevVersion'].",".$datum['dn']."
\n"; } } echo "Cluster,Type,Current Version,Prev/Backup Version,Node
"; $fwResults = str_replace ("/fw-boot-def/bootunit-system", "", $fwResults); $fwResults = str_replace ("/mgmt/fw-boot-def/bootunit-kernel", "", $fwResults); $fwResults = str_replace ("/mgmt/fw-boot-def/bootunit-combined", "", $fwResults); $fwResults = str_replace ("/bios/fw-boot-def/bootunit-combined", "", $fwResults); echo $fwResults; echo ""; echo "

\n"; // Logout $aaaLogout = ""; $results = httpPost($url, $aaaLogout); $outStatus = $results->attributes()->outStatus; } function httpPost($url, $package){ $request = new HTTP_REQUEST2($url, HTTP_REQUEST2::METHOD_POST); $request->setHeader("Content-type: text/xml"); $request->setBody($package); $response = $request->send(); $xml = new SimpleXMLElement($response->getBody()); return $xml; } ?> [/code] The output would end up looking something like this: [code] Cluster,Type,Current Version,Prev/Backup Version,Node ucs01,UCSM,2.0(1q),1.4(1j),_sys/mgmt ucs01,Fabric Interconnect,5.0(3)N2(2.1q),4.2(1)N1(1.4j),_sys/switch-B ucs01,Fabric Interconnect,5.0(3)N2(2.1q),4.2(1)N1(1.4j),_sys/switch-A ucs01,Fabric Extender,2.0(1q),1.4(1j),sys/chassis-4/slot-1 ucs01,Fabric Extender,2.0(1q),1.4(1j),sys/chassis-1/slot-1 ucs01,CIMC,2.0(1q),1.4(1j),sys/chassis-1/blade-1 ucs01,CIMC,2.0(1q),1.4(1j),sys/chassis-1/blade-3 ucs01,Fabric Extender,2.0(1q),1.4(1j),sys/chassis-1/slot-2 ucs01,CIMC,2.0(1q),1.4(1j),sys/chassis-4/blade-1 ucs01,Fabric Extender,2.0(1q),1.4(1j),sys/chassis-2/slot-1 ucs01,Fabric Extender,2.0(1q),1.4(1j),sys/chassis-3/slot-1 ucs01,Fabric Extender,2.0(1q),1.4(1j),sys/chassis-3/slot-2 ucs01,Fabric Extender,2.0(1q),1.4(1j),sys/chassis-4/slot-2 ucs01,Interface Card,2.0(1q),1.4(1j),sys/chassis-1/blade-3/adaptor-2 ucs01,Interface Card,2.0(1q),1.4(1j),sys/chassis-1/blade-3/adaptor-1 ucs01,Fabric Extender,2.0(1q),1.4(1j),sys/chassis-2/slot-2 ucs01,CIMC,2.0(1q),1.4(1j),sys/chassis-3/blade-3 ucs01,CIMC,2.0(1q),1.4(1j),sys/chassis-2/blade-1 ucs01,Interface Card,2.0(1q),1.4(1j),sys/chassis-1/blade-1/adaptor-2 ucs01,Interface Card,2.0(1q),1.4(1j),sys/chassis-1/blade-1/adaptor-1 ucs01,Interface Card,2.0(1q),1.4(1j),sys/chassis-4/blade-1/adaptor-2 ucs01,Interface Card,2.0(1q),1.4(1j),sys/chassis-4/blade-1/adaptor-1 ucs01,Interface Card,2.0(1q),1.4(1j),sys/chassis-2/blade-1/adaptor-2 ucs01,Interface Card,2.0(1q),1.4(1j),sys/chassis-2/blade-1/adaptor-1 ucs01,Interface Card,2.0(1q),1.4(1j),sys/chassis-3/blade-3/adaptor-2 ucs01,Interface Card,2.0(1q),1.4(1j),sys/chassis-3/blade-3/adaptor-1 ucs01,Blade BIOS,B440.2.0.1c.0.100520111754,B440M1.1.4.1b.0.120820101442,sys/chassis-1/blade-1 ucs01,Blade BIOS,B440.2.0.1c.0.100520111754,B440M1.1.4.1b.0.120820101442,sys/chassis-4/blade-1 ucs01,Blade BIOS,B440.2.0.1c.0.100520111754,B440M1.1.4.1b.0.120820101442,sys/chassis-1/blade-3 ucs01,Blade BIOS,B440.2.0.1c.0.100520111754,B440M1.1.4.1b.0.120820101442,sys/chassis-2/blade-1 ucs01,Blade BIOS,B440.2.0.1c.0.100520111754,B440M1.1.4.1b.0.120820101442,sys/chassis-3/blade-3 ucs01,Blade BIOS,B440.2.0.1c.0.100520111754,B440M1.1.4.1b.0.120820101442,sys/chassis-3/blade-1 ucs01,CIMC,2.0(1q),,sys/chassis-3/blade-1 ucs01,Interface Card,2.0(1q),1.3(0.841),sys/chassis-3/blade-1/adaptor-2 ucs01,Interface Card,2.0(1q),1.4(1j),sys/chassis-3/blade-1/adaptor-1 [/code] Hope that helps. Sage

RE: Memory details via XML API...

2011-10-03T19:30:58Z

Personally I would use a command line script. As you said it's not something I would look at on a regular basis. It's generally something that would only need to be done once in a while to either confirm or audit that all DIMMs are paired correctly. If I'm doing an audit I'd want something scriptable so I can easily hit all our blades.

RE: Memory details via XML API...

2011-09-28T22:54:29Z

That did it, thanks Paul. Do you know if there's a way to also get the manufactured week off the DIMM's too? Ultimately that's what I was looking for, I just thought it would be in that query. Somehow we've got some DIMM's that aren't paired correctly and I'd like to run something against all of our blades so we can be proactive and line 'em up before we have a problem. PS Enjoyed your presentation at the UCS user group meeting in RTP.

Memory details via XML API...

2011-09-28T15:36:03Z

Is there a way via the XML API to get the same information as if I had: * SSH'd to a FI * Scope server chassis1/blade1 * Show memory detail Thanks, Sage

RE: How to install OS to Virtual Machine in Emulator

2011-07-27T15:06:12Z

Hi Derek, A quick search turned up install guides for Redhat (and thus CentOS) as well as SuSE linux. As long as it's a recent build chances are good your OS is going to run on it, worst case you might have to add some device drivers. If you let us know what you're trying to run, perhaps someone can verify it works on a given UCS configuration. Sage

RE: How do I retrieve Fabric Interconnect serial numbers via XML API?

2011-07-05T22:06:44Z

Nevermind, I think I've got it figured out now. I was trying to capture packets immediately prior to displaying them in the UCSM. Instead I started wireshark before logging into the UCS and it was at that point I saw all of the classIds used to cache system details. For the benefit of those to come, the query used was:

RE: How do I retrieve Fabric Interconnect serial numbers via XML API?

2011-07-05T19:42:34Z

Hi John, That query worked perfecty, thank you! Do you have a suggestion on how I could have discovered that command via wireshark? Sage

How do I retrieve Fabric Interconnect serial numbers via XML API?

2011-07-05T18:50:02Z

Hi, I'm trying to retrieve the serial numbers from the Fabric Interconnects using the XML API. Initially I was testing against the UCS emulator but that does not supply serial numbers to the FI's. Using wireshark though I was able to narrow down a likely XML command to: The results however are not what I was looking for. I tried testing the XML against a real environment and the serial field still comes back blank. Anyone have suggestions on how I can retrieve that information?