Cisco IOS-XR introduces a new prompt format that is "breaking" Net::Telnet::Cisco. Basically, the Route Processor and CPU instance is added with a colon ":" before the router hostname. I was wondering why my Telnet sessions were "failing" but the logs showed they connected and got the prompt.
I looked for an update to Net::Telnet::Cisco, but the latest version I could find was 1.10, which is what I have installed. To get around this, I used the -prompt option when calling Net::Telnet::Cisco->new() from my script.
Under the "sub new" procedure in Cisco.pm, I found the existing prompt regex (you can't miss it). I copied that code and added the new piece and passed that in when I make the Net::Telnet::Cisco->new() call via the "-prompt" option. (See Net::Telnet for more info.)
All we're doing is adding a check for the Route Processor and CPU instance and colon before the hostname - optionally, so we don't break what's currently working. This is done with the addition of:
(?:[\w.\/]+\:)?
near the beginning of the existing regex.
use Net::Telnet::Cisco; ... my $session = Net::Telnet::Cisco->new( ... -prompt => '/(?m:^(?:[\w.\/]+\:)?[\w.-]+\s?(?:\(config[^\)]*\))?\s +?[\$#>]\s?(?:\(enable\))?\s*$)/' ... )
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Net::Telnet::Cisco and IOS-XR
by Anonymous Monk on Jun 10, 2009 at 22:39 UTC | |
by Anonymous Monk on Jun 29, 2010 at 18:32 UTC | |
by Anonymous Monk on Nov 23, 2011 at 06:52 UTC | |
by Kumar Mantri (Novice) on Nov 24, 2011 at 13:08 UTC | |
by Anonymous Monk on Jun 30, 2010 at 08:07 UTC | |
Re: Net::Telnet::Cisco and IOS-XR
by Anonymous Monk on Jun 30, 2010 at 08:06 UTC | |
by Anonymous Monk on Jun 30, 2010 at 08:18 UTC | |
by Anonymous Monk on Jul 27, 2010 at 17:44 UTC | |
by Kumar Mantri (Novice) on Nov 23, 2011 at 07:16 UTC | |
by Anonymous Monk on Jun 13, 2014 at 23:12 UTC |