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

nxos using nx-api ping unable to handle no route to host message #718

Open
ktbyers opened this issue Apr 27, 2018 · 1 comment
Open

nxos using nx-api ping unable to handle no route to host message #718

ktbyers opened this issue Apr 27, 2018 · 1 comment
Assignees

Comments

@ktbyers
Copy link
Contributor

ktbyers commented Apr 27, 2018

This test:

nxos1# ping google.com
PING google.com (172.217.7.238): 56 data bytes
ping: sendto google.com 64 chars, No route to host
Request 0 timed out
ping: sendto google.com 64 chars, No route to host
Request 1 timed out
ping: sendto google.com 64 chars, No route to host
Request 2 timed out
ping: sendto google.com 64 chars, No route to host
Request 3 timed out
ping: sendto google.com 64 chars, No route to host
Request 4 timed out

--- google.com ping statistics ---
5 packets transmitted, 0 packets received, 100.00% packet loss

Resulted in an empty dictionary being returned.

@ktbyers
Copy link
Contributor Author

ktbyers commented Apr 27, 2018

There is also no unit test data for the ping method for NX-API for any of the failure cases (the normal test case only handles a ping success).

@ktbyers ktbyers self-assigned this May 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant