Hi, me again ;)

How easy would it be to implement a login method (similar again to Net::Telnet::Cisco) for the following type of scenario:

We are an ISP, auditing both configs on our PE routers and on the appropriate CE routers that are connected.

During the course of the script, if certain conditions are true, we connect (from the PE router) to the CE router. In this way, we reuse the session object that we created to connect to the PE. (this is because we can't necessarily reach the CE router from our management station).

Net::Appliance::Session handles both the connection and the login in the one method, connect. using the above example, with NTC we could do something like the following:

I'm not sure if a login method would be used very often with NAS, as the connect method generally handles all it needs to, but it would be handy.

Thanks
Raimund

Glad to know I can still send guys off to the drawing board to think ;)

Thanks for your help here - there's no rush at least - I've implemented a workaround in most cases.

Regards
Raimund

OK, I got my app working OK. I troubleshot this some more, First I took a deeper look at the phrasebook and determined there was no real issue there, so changing phrasebooks wouldn't have helped me as far as I could tell. To verify I set my connection phrasebook to PIXOS and it connected to the router OK and then ssh to PIX OK but still failed to enable.

I was using this method as per the example in a past post here:

I did some further troubleshooting and determined this line in Net-Appliance-Session-Engine.pm in the begin_privileged sub was causing my problem

So now instead of setting in_privileged_mode to false I am using this and it works OK for me

Now it occurs to me why my router to router connections worked OK while router to PIX failed. I am logining in straight to priv level 15 when going from router to router. So I would have had this same problem as I did with the PIX had I needed to do an enable after logging into the next router.

Thanks!

Hi Oliver, thanks for the reply!

Not a bad idea, here's my 2 cents if you're interested. In some of the networks I work on it can take 2 or 3 router hops before I can reach my ultimate destination. I work as a consultant and use your module in my auto-backup script I run after finishing work on customer sites. I don't control the policies at these networks and many are partitioned off and/or have access-class statements that make it necessary for me to hop my way through a few routers to finally be able to make a connection to the intended router.

The above would be useful for me if it was architected in a nested manner that allowed for more than 1 router hop.

Expanding on what you have show would this then be possible?