On Sat, Nov 22, 2008 at 9:55 PM, Tim Durack <[EMAIL PROTECTED]> wrote:
> On Sat, Nov 22, 2008 at 9:46 PM, ghostonthewire > <[EMAIL PROTECTED]> wrote: > > Tim Durack wrote: > >> > >> Amazing: > >> > >> usziplab001:~/config/Core# !scp > >> scp acl.txt [EMAIL PROTECTED]:running-config > >> Password: > >> acl.txt 100% 1694 1.7KB/s 00:01 > >> > >> I can dump a bunch dumb expect scripts now. > >> > > > > Expect scripts can handle exceptions caused by erroneus input, and > perform > > rollback action or just warn you that something went wrong, but copying > just > > performs unpredictable merge. Or it discards entire acl.txt on syntax > error? > > Not if the acl scripts are of the form: > > no ip access list extended acl_name > ip access list extended acl_name > ... > end Exactly how is scp going to save you? You have to handle the exceptions whether expect writes the commands to stdout or whether they get parsed after being copied to the running config via scp. - Laurent _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
