These commands copy the Event Log content to a remote host, attached USB device, or to a serially connected
PC or UNIX workstation.
Parameters and options
oobm
For switches that have a separate OOBM port, the
oobm
parameter specifies that the transfer is through the
OOBM interface. If this parameter is not specified, the transfer is through the data interface. The
oobm
parameter is not available on switches that do not have a separate OOBM port.
Copy the event log to a PC connected to the switch
Figure 36: Sending event log content to a file on an attached PC
Transferring switch configurations
Using the CLI commands described in the section beginning with
TFTP: Copying a configuration file to a
on page 358, you can copy switch configurations to and from a switch, or copy a software
image to configure or replace an ACL in the switch configuration.
NOTE:
For greater security, you can perform all TFTP operations using SFTP, as described in the section
You can also use the
include-credentials
command to save passwords, secret keys, and other
security credentials in the running config file. For more information, see the section on "Saving
Security Credentials in a Config File" in the access security guide for your switch.
TFTP: Copying a configuration file to a remote host (CLI)
Syntax:
copy {<startup-config | running-config>} tftp <
ip-addr
> <
remote-file
> [pc | unix]
copy config <
filename
> tftp <
ip-addr
> <
remote-file
> [pc | unix]
This command can copy a designated config file in the switch to a TFTP server. For more information, see
"Multiple Configuration Files" in the basic operation guide for your switch.
Example:
To upload the current startup configuration to a file named
sw8200
in the configs directory on drive
"d"
in a TFTP
server having an IP address of 10.28.227.105:
switch# copy startup-config tftp 10.28.227.105
d:\configs\sw8200
358
Aruba 2930F / 2930M Management and Configuration Guide
for ArubaOS-Switch 16.08
