Fish the UCS API with Wireshark

RE: aaaRefresh and aaaLogout works on UCSPE but not a real UCS?

2010-10-04T17:11:57Z

Tested this again with Firefox and Poster: If I send aaaLogin I get an outCookie. If I send aaaRefresh with inCookie set to outCookie value, I get the response errorCode="552" invocationResult="unidentified-fail" errorDescr="Authorization required" If I send aaaRefresh with cookie set to outCookie value, I get the response errorCode="552" invocationResult="unidentified-fail" errorDescr="Authorization required" When I do this on UCSPE: If I send aaaLogin I get an outCookie. If I send aaaRefresh with inCookie set to outCookie value, I get the response

RE: aaaRefresh and aaaLogout works on UCSPE but not a real UCS?

2010-10-04T16:05:23Z

...and here's me running the exact same code but this time @ UCSPE... this is the end of a debug log (I'm using Ruby, but I get the same results with Firefox Poster). [b]First, aaaRefresh works:[/b] I, [2010-10-04T12:03:24.681215 #50103] INFO -- CiscoUCS:UCSM: dispatch called with I, [2010-10-04T12:03:24.694525 #50103] INFO -- CiscoUCS:UCSM: dispatch received [b]and so does aaaLogout:[/b] I, [2010-10-04T12:03:24.696213 #50103] INFO -- CiscoUCS:UCSM: logout @url=http://192.168.1.66/nuova, @cookie=1283408575/443b4d43-9492-489c-a5fe-c94c8db805d2 I, [2010-10-04T12:03:24.702486 #50103] INFO -- CiscoUCS:UCSM: dispatch starting I, [2010-10-04T12:03:24.702667 #50103] INFO -- CiscoUCS:UCSM: dispatch called with I, [2010-10-04T12:03:24.705481 #50103] INFO -- CiscoUCS:UCSM: dispatch received

aaaRefresh and aaaLogout works on UCSPE but not a real UCS?

2010-10-04T15:35:24Z

I had the two aaaRefresh/aaaLogout methods working fine on the UCS Platform Emulator, but then when I point at a "real" UCS I get errors back from the API. Here's the response for the aaaLogin (works fine) and then the two "broken" methods: [b]Login works fine, we get the cookie back:[/b] [b]I can get MOs back:[/b] Sent: Received: [b]But aaaRefresh doesn't work with the same cookie:[/b] Sent: Received: [b]Neither does aaaLogout"[/b] Sent: Received: Any ideas?

Easy access to the Cisco UCS API via the Ruby UCSAPI Module

2010-10-01T21:27:15Z

I'm working on a Ruby gem called UCSAPI. This is a blog post on ViewYonder about it and how to get it (really easy). Early days, just some basic stuff in there for now... worth a lookie tho' [url=http://viewyonder.com/2010/10/01/easy-access-to-the-cisco-ucs-api-via-the-ruby-ucsapi-module/]Easy access to the Cisco UCS API via the Ruby UCSAPI Module[/url] Here's what you can do so far... I'm working on going deeper on each object (e.g. into computeBlade) and wider to cover more objects (e.g. lsServer) and more methods (e.g. config changes and listening). Last login: Thu Sep 30 21:52:06 on ttys001 13:20:08 ~ $ irb >> require 'UCSAPI' => true >> include UCSAPI => Object >> ucspe = UCSM.new( :url => 'http://192.168.1.66/nuova', :inName => 'config', :inPassword => 'config') ...output removed.. >> ucspe.fabric ..dumps two fabric objects out, which look ugly on a blog... >> ucspe.fabric.each { |fabric| puts fabric.oobIfIp } 192.168.1.66 0.0.0.0 >> ucspe.chassis.each { |chassis| puts chassis.dn + " is managed by Fabric " + chassis.managingInst } sys/chassis-1 is managed by Fabric A sys/chassis-2 is managed by Fabric A sys/chassis-3 is managed by Fabric A >> ucspe.fan( :fabric => 'A' ).each { |fan| puts fan.serial + " is " + fan.operState } Chassis-2A is operable Chassis-1A is operable >> ucspe.psu( :chassis => 1).each { |psu| puts psu.dn + " voltage is " + psu.voltage } sys/chassis-1/psu-4 voltage is ok sys/chassis-1/psu-3 voltage is ok sys/chassis-1/psu-2 voltage is ok sys/chassis-1/psu-1 voltage is ok

Fish the UCS API with Wireshark

2010-09-19T13:51:33Z

You can monitor and control Cisco UCS via the XML API¿ if you just knew how. As well as learning the API, you also need to troubleshoot it. For those two reasons, you need to know how to use Wireshark to expose the raw API interactions. http://viewyonder.com/2010/09/19/fish-the-ucs-api-pool-with-wireshark/