[cisco-voip] howto: automatically backup cme config

[Ryan West]

Mark,

Check out http://brainhub.wordpress.com/2007/11/01/automate-backup-cisco-configs-using-expect/ there are hundreds of links like this.  Any *nix box (with TCL/expect) installed will run the commands from the netpro discussion.  Then you would just use a Cron job to run the backups.

-ryan

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mark J
Sent: Friday, September 12, 2008 1:19 AM
To: Erick Bergquist
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] howto: automatically backup cme config

Hi Erick,

Thanks for the link, I think this will be really useful!

What does Tony mean by a script server? Is this the router or a server? If it is the router, how would you set a schedule for this job to run?

Thanks for all your help.

Mark


2008/9/12 Erick Bergquist <erickbee at gmail.com<mailto:erickbee at gmail.com>>
No problem, I had stumbled across that awhile ago at a old gig when I
dealt with AIM-CUE failures 1-2 times a month (150+ locations). Now,
not as much, but I do recall reading some posting somewhere where they
had CUE automated backup on a roadmap for a future version, this was
like 6-9 months ago.

On Thu, Sep 11, 2008 at 9:28 PM, Ryan West <rwest at zyedge.com<mailto:rwest at zyedge.com>> wrote:
> Erick,
>
> Thanks for the link.  Not sure why Cisco wouldn't want to post TCL/Expect scripts to add with a product that badly needs a built-in automatic backup function.  I figured this was the only alternative.  Thanks for the link.
>
> -ryan
>
> -----Original Message-----
> From: Erick Bergquist [mailto:erickbee at gmail.com<mailto:erickbee at gmail.com>]
> Sent: Wednesday, September 10, 2008 1:05 AM
> To: Joe Cisco
> Cc: Ryan West; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
> Subject: Re: [cisco-voip] howto: automatically backup cme config
>
> I haven't tried this, but...
>
> http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Expert%20Archive&topic=Voice%20and%20Video&topicID=.ee7f996&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40^1%40%40.1dde3c2a/45#selected_message
>
>
> On Tue, Sep 9, 2008 at 3:27 PM, Joe Cisco <smetsysocsic at gmail.com<mailto:smetsysocsic at gmail.com>> wrote:
>> No problem on the hijack. When we install a new system we usually have
>> the administrator use the CUE GUI, which obviously must be kicked off
>> manually. However, it would be nice to be able to auto script it
>> somehow.
>>
>> -Joe C.
>>
>> On Tue, Sep 9, 2008 at 3:10 PM, Ryan West <rwest at zyedge.com<mailto:rwest at zyedge.com>> wrote:
>>> Not to highjack your post here, but has anyone figured out a way to auto backup the CUE config?
>>>
>>> -ryan
>>>
>>> -----Original Message-----
>>> From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Joe Cisco
>>> Sent: Tuesday, September 09, 2008 4:05 PM
>>> To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
>>> Subject: [cisco-voip] howto: automatically backup cme config
>>>
>>> I assume a large percentage of you may have already known this, but I
>>> hadn't seen it and thought i'd post it. This a cheap/easy way to
>>> automatically back up a CME (or any IOS device for that matter) if you
>>> have an available FTP server. I think they started supporting this
>>> somewhere in the 12.3 range of code.
>>>
>>> ! *** the following config will automatically back up the config
>>> ! *** of the device to the folder of the ftp server listed in the
>>> ! *** PATH statement every 10080 minutes (7 days). It will
>>> ! *** also copy the config every time a "write mem" or "copy
>>> ! *** run start" is issued.
>>> !
>>> !
>>> ! *** set ftp server username
>>> ip ftp username admin
>>> ! *** set ftp server password
>>> ip ftp password ftp-server-password-goes-here
>>> !
>>> !
>>> !
>>> archive
>>>  path ftp://10.0.0.10/ucme-configs/router-hostname-here
>>>  log config
>>>  write-memory
>>>  time-period 10080
>>> !
>>> !
>>>
>>> Later,
>>>
>>> Joe C.
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080912/322604bd/attachment-0001.html>