-
I was wondering if anyone else has experienced this. ^^^^^^^^ Executing Netmiko Send Command: term length 0 on Devices with Expect String Matching ^^^^^^^^ Above you can see that it data returned in the Nornir Restult was actually the command I should have sent previously. If I use netmiko by itself I don't encounter this issue when using send_command_timing as it does not look for a prompt and the issue is bypassed. I don't know if there is a way to ignore the prompt somehow in nornir-netmiko when using use_timing. I would expect the same behavior but nornir always seems to be looking for the HOST# prompt.
VS a simple test with netmiko:
OUTPUT: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
@bgile What you are seeing is not Try setting |
Beta Was this translation helpful? Give feedback.
@bgile
use_timing=True
in nornir-netmiko executessend_command_timing
.What you are seeing is not
send_command_timing
executing the previous command, but theecho
of the previous command by the device. Likely what this means is your Python script is ahead of the state of the device (i.e. your device is slow to respond so you are reading things that you think should be already done).Try setting
global_cmd_verify=True
as a ConnectHandler argument to Netmiko (mapped into a Nornir-netmiko context), adtran Netmiko driver defaults this to False (we are in process of changing this as someone separately brought it up and we realized that global_cmd_verify should probably now be switched to True)…