[f-nsp] RANCID with MLX 3.9.00a

Nick Buraglio buraglio at illinois.edu
Wed Feb 25 18:20:40 EST 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

After not looking at this problem for a bit I finally got back to it  
and found that the problem was with how skip-page-display was  
handled.  On the MLX code that I am running that command isn't there  
for the priv level I was using for the rancid process.  As opposed to  
messing around and giving more access to the rancid user, I found that  
MLX boxes now support "terminal length 0", so I just changed the  
flogin code to support that.  Since this instance of RANCID won't need  
to support older foundries and the user access level isn't shouldn't  
change, this was the right choice.
There may be an easier way but I'm still relatively new to foundry- 
land (or brocade-land?) and this works.

For anyone else that has my one-off problem, here is the diff for  
flogin:

- --- flogin.orig 2009-02-25 17:07:12.000000000 -0600
+++ flogin      2009-02-25 15:58:49.000000000 -0600
@@ -506,7 +506,8 @@
      global in_proc
      set in_proc 1

- -    send "skip-page-display\r"
+#    send "skip-page-display\r"
+    send "terminal length 0\r"
      expect -re "$prompt" {}

      set commands [split $command \;]
@@ -677,7 +678,8 @@
         }
      } elseif { $do_script } {
         # fucking foundry
- -       send "skip-page-display\r"
+       #send "skip-page-display\r"
+       send "terminal length 0\r"
         expect -re $prompt      {}
         source $sfile
         catch {close};


It's not exactly rocket science, basically just 2 very simple  
changes.  I know this is a little off topic for the list but since the  
thread started here I figured I'd follow up with the fix here (as well  
as the rancid list).


nb


- ---
Nick Buraglio
Network Engineer, CITES, University of Illinois
GPG key 0x2E5B44F4
Phone: 217.244.6428
buraglio at illinois.edu



On Jan 6, 2009, at 4:48 PM, Nick Buraglio wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Has anyone had success running RANCID 2.3.2a7 against a foundry MLX  
> running 3.9.00a over ssh?  We're seeing some strange behavior that  
> we don't expect and I'm just looking for confirmation that someone  
> else has actually done this with these parameters.
> As an interesting data point, it works fine using telnet and the  
> RANCID install works fine for other vendor boxes, which is why I'm  
> seeking anyone else that has done it under the aforementioned  
> circumstances.
> Again, I'm not necessarily looking for any kind of RANCID support  
> (since this isn't a RANCID support list) just a "yes, I've done it"  
> from someone out there.
>
>
> Thanks!
> nb
>
>
> - ---
> Nick Buraglio
> Network Engineer, CITES, University of Illinois
> GPG key 0x2E5B44F4
> Phone: 217.244.6428
> buraglio at illinois.edu
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Darwin)
>
> iEYEARECAAYFAklj37wACgkQFOm2Sy5bRPTVZwCePoXIsFwgYGjcqtNA4C2hb9tD
> MRMAnR2jlVS1D7Q7/oGceVwgudG6/4LK
> =kBjV
> -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkml0kgACgkQFOm2Sy5bRPR6OgCeNBduJOXAmcUFdzu9SH3f4Ccv
IccAn365lA/A3DDh0prAUKAj+kooI3t9
=BsTJ
-----END PGP SIGNATURE-----



More information about the foundry-nsp mailing list