You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 'cli' function is a wrapper for the XML API 'cli' function. The limitation of this is documented by Cisco:
"CLI Command Limitations
The CLI commands, which are supported through XML, are limited to CLI configuration commands and EXEC mode show commands (and responses) that are wrapped in tags.
This prevents us for example from clearing interface or protocol statistics, or issuing "mpls traffic-eng" requests.
It would be very useful to have a 'raw cli' function which exits the XML interface to issue non-show commands. I understand that some of those commands might result in further interactive CLI prompts which could be awkward to catch (and suspect this is why Cisco devs have imposed the limitation in the XML API !), so the new function could be provided with this caveat...
The text was updated successfully, but these errors were encountered:
The 'cli' function is a wrapper for the XML API 'cli' function. The limitation of this is documented by Cisco:
"CLI Command Limitations
The CLI commands, which are supported through XML, are limited to CLI configuration commands and EXEC mode show commands (and responses) that are wrapped in tags.
This prevents us for example from clearing interface or protocol statistics, or issuing "mpls traffic-eng" requests.
It would be very useful to have a 'raw cli' function which exits the XML interface to issue non-show commands. I understand that some of those commands might result in further interactive CLI prompts which could be awkward to catch (and suspect this is why Cisco devs have imposed the limitation in the XML API !), so the new function could be provided with this caveat...
The text was updated successfully, but these errors were encountered: