Odd truncation in UCS API?

RE: Odd truncation in UCS API?

2012-12-05T18:59:38Z

Here you go. First you need to login and get yoru cookie via the API with the curl commands below (which assumes HTTP communication): $ cat aaa.sh #!/bin/bash curl -H "Content-Type: text/xml" -N -s -d "" http://1.2.3.4/nuova $ ./aaa.sh Then take the cookie and use it with the following script as illustrated below: $ cat topsys.sh #!/bin/bash COOKIE=$1 curl -H "Content-Type: text/xml" -N -s -d '' http://1.2.3.4/nuova $ ./topsys.sh "1354316387/74eed11a-35d2-48a1-b569-f75c25ed1482" > topsys.out As you can see the file I was returned was 1.9 MB: $ ls -alh topsys.out -rw-r--r-- 1 ericwill staff 1.9M Dec 5 12:56 topsys.out

RE: Odd truncation in UCS API?

2012-12-05T18:32:13Z

I suspected the same and dug all the way back to using LWP directly. I'd be really surprised with that being distrbuted with a truncation error, but you never know. Do you have a sample of that curl to "grab all" that you talk about? That'll help me figure out of this bug is the module or not.

RE: Odd truncation in UCS API?

2012-12-05T04:48:45Z

Looks to be a bug with the Perl module you are using. I have had responses of much larger XML responses than that doing direct calls w/ tools like curl. Perform a configResolveClass w/ inHierarchical set to true on class "topSystem" on a UCS domain, and you will get the entire XML database returned. It can be a few MB of data, and I have never had issues getting truncation before.

Odd truncation in UCS API?

2012-11-28T00:05:40Z

I am using the perl module Cisco::UCS to communicate with a UCS blade center version 2.0(2q). I was running into trouble, and when I finally got down to debugging it I found that all the API responses I were receiving from the UCS were being truncated at 65536 characters/bytes. It is a usual HTTPS transaction. The query returns as a valid HTTP response (200) and all other interactions are the same. There just seems to be a hard size limit on the XML response. I've verified there are no network firewalls or such between me and the UCS. When I run the same script on the current UCS emulator (version 2.0(3c)), I do not have this issue. Has anyone seen this or do they have suggestions?