Skip to main content

Schedule Automatic backup config in Cisco Nexus




Nexus-Sw1(config)#feature scheduler   //Enable scheduler service in Nexus

Nexus-Sw1(config)#scheduler job name backup-daily      // Job Name

Nexus-Sw1(config)#scheduler aaa-authentication username abcd password abcd@123    // AAA - Authentication for Job created above (If AAA configured)

Nexus-Sw1(config)#scheduler job name backup-daily
copy running-config tftp://192.168.1.23/$(SWITCHNAME)-cfg.$(TIMESTAMP)         //IP of TFTP SERVER , file will saved with switch name and timestamp
exit

Nexus-Sw1(config)#scheduler schedule name backup-daily   // Setup Schedule to run for the JOB

Nexus-Sw1(config-schedule)# time ?
  daily    Specify a daily schedule
  monthly  Specify a monthly schedule
  start    Specify a future time schedule
  weekly   Specify a weekly schedule

  
Example : 
 Nexus-Sw1(config-schedule)# time start now repeat 00:00:05
Schedule starts from Mon Mar  4 10:44:41 2013
Nexus-Sw1(config-schedule)# job name backup-daily             // Job Name to be schedule in Scheduler 
Nexus-Sw1(config-schedule)# exit
Nexus-Sw1(config)# exit
Nexus-Sw1# show scheduler config
Nexus-Sw1# show scheduler logfile

Comments

Popular posts from this blog

Duplicate IP Address has been Detected Rule

A duplicate IP address has been detected on the network Rule Knowledgebase Summary This rule generates an alert when Windows® detects that he local machine’s IP address is in conflict with one or more identical IP addresses on the network. Until the IP address conflict is resolved, remote clients and applications may have difficulty accessing resources on any of the effected computers. Additionally, the local computer may not be able to access network resources. Related Events This rule generates an alert whenever the following events occur and are recorded in the System Event Log: The system detected an address conflict for IP address %2 with the system having network hardware address %3. The local interface has been disabled. Source: TCPIP; Event ID: 4198; The system detected an address conflict for IP address %2 with the system having network hardware address %3. The local interface has been disabled. Source: TCP...

VMware CPU and Memory Reservations: Fixing Insufficient resources to satisfy configured failover level for HA

Source Knowledge From :-  http://geekswing.com/geek/vmware-cpu-and-ram-reservations-fixing-insufficient-resources-to-satisfy-configured-failover-level-for-ha/ VMware CPU and Memory Reservations: Fixing Insufficient resources to satisfy configured failover level for HA This post comes from a few days of poring over manuals as well as some technical support. This is a good one. The error came from trying to power on a VM in our VMware cluster and we would get these errors: “Insufficient resources to satisfy configured failover level for HA” And this alert on our cluster “Insufficient resources to satisfy HA failover level on cluster vmCluster in vmTST” Our way of thinking was we had to power one off to power another one on. But that didn’t work. Here we is the actual solution. (p.s. Great VMware HA education for me on this one!) PROBLEM SOURCE: VMware HA is turned on and you are violating constraints VMware HA is turned on, and you have i...