Intersight API inconsistent results for memory units various API calls

[jseaman01111]

I have been using the get_memory_unit_list python API call and historically the OperState field has returned "operable" or "inoperable". Now for X210cM7 servers, it returns "OK".

I have also observed that get_compute_physical_summary has changed the unit for AvailableMemory from MiB to GiB for m7. Prior to m7, AvailableMemory would return 524,288, but now returns 512.

Are these kinds of arbitrary changes in the use of data fields within the Intersight configuration data to be expected?

thanks

[bigevilbeard]

No. These types of changes are generally not expected in well designed APIs, as they break backward compatibility and can cause integration issues. I would document this and open a TAC case or bring this up with your Cisco account manager.

Good luck!

[Torbjørn]

I have unfortunately seen similar things in the Intersight API before. Cisco/The relevant BU has some way to go when it comes to API best practices. As @bigevilbeard says this is not how it should be.