As a matter of fact I do have experience with Net::Telnet::Cisco in particular and telnet'ing into routers and switches.
A while back I wrote a rather convoluted and re-entrant script to update our MAC address pools in QIP.
Just as an aside: QIP as an IP address management product sucks. It just sucks less than its competition.
The way my script worked was when run on a machine it first looked at the routing table on that machine and figured out what the default router was. The default route could actually be a switch.
Then we dumped the arp cache for that device and stored it and then dumped the devices routing table to find its neighbors. Then for each neighbor we recursed until we ran out of unique neighbors and had the whole list of ARP addresses for the enterprise.
Doing this not only allowed us to update our global MAC pools, but it help us discover routers and switches that were not supposed to be there. After all this is a school campus and college students will play!
Net::Telnet::Ciso worked very will for this. What I did discover though was I had to make my login algorithm somewhat intelligent because different devices posed different behavior upon login so my script had to be sensitive to that.
| Peter L. Berghold | Brewer of Belgian Ales |
| Peter@Berghold.Net | www.berghold.net |
| Unix Professional | |
In reply to Re: Telnet into Cisco switches
by blue_cowdawg
in thread Telnet into Cisco switches
by primus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |