Switch 2 can only be seen from the console of switch 1 so I will need to login to switch 1 first then telnet to switch 2 to get it's config.
This can be done in other config manager software how about cirrus?
What type of device is switch 2? Also, just curious, is this setup a requirement from the device or is this a preference for security purposes?
Both are Cisco switches, and it's an isolated remote network that we just don't route to or from our main network.
this would be cool, since we have a similar situation on one of ours. post back if you get it to work.
You can just go for Kiwi CatTools
Nice Price - Nice Tool
Looked at it, but after running Cirrus there is no way I'd use Kiwi.
I love being able to make changes to all my switches in one shot. This alone is worth not being able to directly get to those odd switches.
Also FYI: I think I figured out a way to grab the other switch configs using the scripts. Tell Cirrus to run my script on the first switch and that script then does a telnet session to the non routed network switch, grabs the config via tftp and sends it to the first switch as a unique file name. Then disconnect from the non routed switch and copy the config file via tftp to my Cirrus machine which is also running tftp.
The rest from there is a manual copy process but at least I can get it to be somewhat automated.
Thanks for the great post. I think many customers will find this useful.
Another FYI, you can import text files into Cirrus by highlighting the desired device within Cirrus, selecting the desired text file from Windows Explorer, dragging the text file to the Cirrus Node list, and selecting OK.
I will also add the ability to telnet to a switch via another switch without needing to manually transfer the config into Cirrus as a feature request for a future release.
