Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gracefully handle errors better if xml command fails #60

Open
ktbyers opened this issue Oct 12, 2018 · 0 comments
Open

Gracefully handle errors better if xml command fails #60

ktbyers opened this issue Oct 12, 2018 · 0 comments

Comments

@ktbyers
Copy link

ktbyers commented Oct 12, 2018

The below would just come back as a generic Netmiko error intead of raising the underlying error that happened from the xml command.

Would be better if the xml command that resulted in an ERROR raised the underlying error message.

RP/0/RP0/CPU0:ios-xr#
RP/0/RP0/CPU0:ios-xr#terminal length 0
Fri Oct 12 19:56:36.548 UTC
RP/0/RP0/CPU0:ios-xr#terminal width 511
Fri Oct 12 19:56:36.774 UTC
RP/0/RP0/CPU0:ios-xr#
RP/0/RP0/CPU0:ios-xr#xml
Fri Oct 12 19:56:37.485 UTC
ERROR: 0xa3679c00 'XML Service Library' detected the 'fatal' condition 'The router is low on memory. Please retry the request after memory consumption has gone down.'
RP/0/RP0/CPU0:ios-xr#<?
                     ^
% Invalid input detected at '^' marker.
RP/0/RP0/CPU0:ios-xr#<xml version="1.0" encoding="UTF-8"?
                     ^
% Invalid input detected at '^' marker.
RP/0/RP0/CPU0:ios-xr#<xml version="1.0" encoding="UTF-8"><Request MajorVersion="1" MinorVersion="0"><Get><Operational><SystemTime/><PlatformInventory/>        </Operational></Get></Request>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant