I’ve been trying to find some documentation on the Web Services API other than the Webservices API Guide for DCNM which gives you pretty much nothing other than a list of functions and what parameters they take...
I really need some more technical description on how to structure the data to pass to the webservices (methods with input parameters).
Lets take the InterfacesAppService for instance.
The function "getAllInterfacesInNetworkElement" takes two parameters:
"opContext - operational context" and
"neInstanceNameId - InstanceNameId corresponding to the network element"
Based on the WSDL the SOAP call should look pretty much like this:
There are no definitions on what kind of data this parameters should be (int, string etc.)
What is operational context ?
What is InstanceNameId ?
A lot of theese functions refeers to an "InstanceNameId" which is nowhere to be found!
In the API Guide (link below), they give an example from the InventoryAppService and calls "getAllChassisInNetwork" which takes one optional parameter. Here you can find "InstanceName, instanceClassId and even an neId in the InstanceName".
This one also works for me, and I've been trying almost every single value from my response, but with no luck.
To interact with DCNM-SAN Web Services, the you must obtain a token through LogonWS and attach this token to the header message of every SOAP requests. DCNM-SAN Web Services verifies user credentials using a unique token string that is administered by LogonWS. At any given time, HTTPS should be deployed to secure the communication channel. The following example displays the format of the header message:
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.