Hi Johan,
Interesting problem indeed. I haven't run into it as of yet since I haven't tested compliance tests with stacked switchen yet. Will do this pretty soon though.
Have you tried adding some more line breaks between the interface and command in...
Hi Dal,
You are correct, it is a bug that appeared in 2.0. Like you I ran into this problem and the bug is specified here (CSCux39158) in Ciscos Bug Search-tool. The solution is to use the correct order in the XML-scheme but they fail to specify what...
Hi Shaik,Have your problem been solved? It seems like the correct URI for making the Delete-call in version 1.4 is: https://<mntnode>/admin/API/mnt/Session/Delete/MACAddress/<madaddress>It has changed a bit from version 1.2 and hopefully that's your ...
Hello,It seems like the account you used while making the API-call is lacking the correct priviliges. Please check the account's priviliges and make sure you are using an account that is allowed to make API-calls.
Hi,I have also run into this problem on two different Prime 2.1-systems when trying to get all Client-data available. I haven't figured out a way to fix it more than making small calls (.maxResults=100) then trying to pin-point and skip the ID giving...