For reasons I never took the time to fully investigate, I could never get Net::Telnet or Net::Telnet::Cisco to work for this either. Since I was short on time I ended up using Expect to automate a real telnet process, and in the end this worked better than the original plan anyway (among other things, when I ran into a switch that had telnet access disabled and only allowed access via ssh, it was a one-line change to make the command that the script called be configurable).
| We're not surrounded, we're in a target-rich environment! |
|---|
In reply to Re: Net::Telnet on routers and switches
by jasonk
in thread Net::Telnet on routers and switches
by pbwiz1970
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |