Configuration considerations for creating and running commands in batches

  • You can create only up to 4 batches of commands and each batch can have a maximum of 10 commands.
  • The following list of commands cannot be issued using the batch process at the privileged EXEC mode:
    • exit
    • ping
    • reload
    • telnet
    • quit
    • traceroute
    • ssh
  • The following list of commands cannot be issued using the batch process at the global configuration mode:
    • quit
    • relative-utilization
    • batch
  • The maximum duration limit that can be configured to start batch buffer execution is 49 days from the current system clock time.
  • If multiple commands that perform flash access are added in a batch, it is likely to give an error because the flash operation of the first command will hinder the subsequent command to access flash resulting in the failure of command execution.
  • Batches scheduled for execution can be edited. That is, you can add, replace, or remove the commands in the batch buffer. The latest changes will be carried out at the time of batch execution.
  • A change in the system date and time does not bear any impact on a batch buffer that is already scheduled for execution.
  • The show running-config command, if added recursively in the same or multiple batches, will impact optimal utilization of system resources.
  • Any command that requires user intervention (for example, providing user credentials) will fail during batch execution.
  • At a particular instance, a batch can be scheduled only once.
  • A batch buffer cannot be scheduled when the batch execution process for that batch is in progress.
  • When a telnet or SSH session executing a batch command is closed, the corresponding batch execution will be cancelled.