Sorry, I know this module only from its doc and source, because we don't have that much Ciscos.
The message "bad named parameter" isn't there, but in Net::Telnet. Obviously, Net::Telnet::Cisco->new gives all its input parameters to Net::Telnet->new without cleaning out its own extensions. Perhaps the error checking in Net::Telnet->new was put in later...
Anyway, if you leave it out, and put instead
$cs->send_wakeup('connect');
$cs->login(...);
at least this doesn't give the error message.
Update: tried it at work (no Cisco at home :-)), our cisco doesn't need send_wakeup, but works also with it. I tested using the following code use Net::Telnet::Cisco;
my ($host, $user, $pass) = qw(10.10.1.1 user pass);
my $cs = Net::Telnet::Cisco->new(
Host => $host,
Dump_Log => 'cisco.log',
Prompt => '/(?m:^\W?[\w\/\d.:-]+[>#])/',
);
$cs->send_wakeup('connect');
$cs->login( $user, $pass );
my @cmd_output = $cs->cmd( 'show ver | inc Configuration' );
print @cmd_output;
$cs->close;
|