RANCID's fantastic!

[Andrew Fort]

* Andrew Pollock <rancid-andrew at andrew.net.au> [2004-01-22 11:10:40 +1000]:

> [snip]
> 
> Thanks for the very detailed pointer. That helps get me started.
> 
> The way I have our Cyclades setup is you can SSH to it thusly:
> 
> ssh andrew:switch1 at mycyclades
> or
> ssh -l andrew:switch1 mycyclades
> 
> and you'll land straight onto the console port in question. Obviously you
> need to send a ~. to get off again. So you don't spend any time on the
> console server itself.

So this works now? (or perhaps with asp's patch he posted)?

add username mycyclades {andrew:switch1}
add userpasswd mycyclades {blah}

just that you have the overloaded 'mycyclades' issue to resolve?

> Is it best to hack in a new method along the lines of "cas" and a have a cas
> user and password in cloginrc? Then the foreach loop of the login procedure
> would just do nothing if the method was cas, and I'd be conditionally
> sourcing another script prior to the foreach that handles connecting to the
> port if the method was cas. Then the rest of the login procedure should be
> able to cope from there. I guess I'd just have to handle disconnecting from
> the port then somewhere as well.

changing rancid minimally would suggest (if i'm right above) that you have multiple host aliases (for the switches' names) all pointing to the same IP address of mycyclades, and you treat them differently in .cloginrc (different username password pairs per 'switch'); and then just ssh to the 'switch' (really the cyclades with the extended username).

> regards
> Andrew

-afort (away for a week to have surgery.. wish me luck :)