-
Notifications
You must be signed in to change notification settings - Fork 105
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
traceroute failing #274
Comments
I'm experiencing the same issue with the same Docker image for Arista devices, not just with Traceroute, but also with other commands that takes a bit longer to finish. I resolved the issue by increasing the read_timeout by adding |
Thanks. This worked well. I needed to modify that and the timeout in the config.yaml to the same value. The ssh_netmiko.py file is embedded into the docker image so I had to modify the file and re-commit the docker @thatmattlove you should make this value configurable or always have it match the timeout value in the config file. The value just simply tells netmiko to wait that max value for the prompt to come back. the default is like 10 seconds which is not long enough for traces |
Hey guys |
If it is running on Docker you need to change the file in the docker image not in the app directory on the OS. If you are not running Docker then it is enough to just add the value in the app directory. Here are the instructions I documented to assist
|
Thank you very much. |
Previously trace ipv6 2600:: and 2a11:: its not working. (for juniper) |
Hi, /opt/hyperglass/hyperglass/defaults/directives/huawei.py:
The correction:
|
Deployment Type
Docker
Version
v2.0.4
Steps to Reproduce
I am seeing this with built in XR directive as well as custom directive as well as Juniper. traceroutes to quite a bit of internet destinations fail. debug is showing pattern not detected. This seems to happen if there is a timeout along the path.
Expected Behavior
traceroute to properly display
Observed Behavior
error on display
Configuration
No response
Devices
No response
Logs
The text was updated successfully, but these errors were encountered: