Netmiko Logging and Optional Source Removal for Ping/Traceroute #336
Description
Version
v2.0.4
Feature Details
Sorry if these features already exist.
- Netmiko Logging
It would be great to have the ability to log all commands sent via Netmiko and their outputs, including any errors. Ideally, logs could be automatically appended to a file named like:
{router-hostname}-{yyyymmdd}.txt
This would help in troubleshooting and auditing commands executed through Hyperglass.
- Optional Removal of Source for Ping and Traceroute
Currently, when using Cisco IOS XE devices (with the cisco_ios platform setting), ping and traceroute commands automatically include the source {source4} option.
I tried to modify /opt/hyperglass/hyperglass/defaults/directives/cisco_ios.py and removed "source {source4}", but the commands still run with the source parameter.
It would be useful to have an option to remove the source4 parameter, so that standard commands like:
ping {target} repeat 5
can be executed without forcing a specific source address.
Thank you!
Feature Type
Change to Existing Functionality
Use Case
In our network, the router may have multiple public IP addresses. If Hyperglass includes the source {source4} parameter in ping or traceroute commands, users could discover the internal or source IP addresses of our routers. By providing an option to disable automatic source assignment, we can hide our source interface, protecting internal addressing while still allowing accurate external network tests.