![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||
Solution Type Technical Instruction Sure Solution 1504026.1 : How to backup the management switch config for engineered systems.
Procedure for backup of Cisco switch in engineered systems such as Sparc SuperCluster or exadata. In this Document
Applies to:SPARC SuperCluster T4-4 - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform. GoalThis document is intended to help administrators back up the configuration of the Cisco switch included in an Oracle engineered system. FixPrerequisites You will need the IP address of the switch and a working TFTP server. It is expected that the reader is aware of TFTP and able to configure their own TFTP server. For example, using Solaris 11 an administrator would need to install the tftp server software: pkg install tftp and start the service: svcadm enable network/tftp/udp6 and be aware that any file which is received will need to already exist and be writable in the tftproot directory: mkdir /tftpboot
(note. The value of <system image> is determined in step II of this process below) and when the process is complete they may wish to disable the TFTP server: svcadm disable network/tftp/udp6 For more information on installing software and configuring a tftp server consult the appropriate documentation for your target OS.
I. connect to the switch as the privileged user II. identify the required files III. copy the files to the TFTP server
At the time of writing the Cisco switches shipped with Oracle engineered systems support telnet as the primary method of connectivity. To connect to the switch and enter privileged mode: # telnet <switch_ip> Once you have an interactive prompt which ends in a '#'' character it is safe to assume you have reached privileged mode. Step II. identify the required files There are 3 files which are of great importance: 1. The startup-config file which configures the switch at startup. The first two of these files can be referenced using the shorthand names: "running-config" and "startup-config" The system image file name will vary and needs to be determined by running: switch-hostname#show version<return> For example:
or: switch-hostname#show version | include boot Step III. copy the files to the tftp server copy <system image> tftp://<tftp server IP>/<system image> The tftproot of your tftp server should now contain backup copies of the three files. For reference here is a transcript of such a session: # telnet 10.10.10.10 User Access Verification Password: switch-hostname#copy bootflash:cat4500-ipbase-mz.122-53.SG5.bin tftp://10.10.10.11/bootflash:cat4500-ipbase-mz.122-53.SG5.bin switch-hostname#copy running-config tftp://10.10.10.11/running-config switch-hostname#copy startup-config tftp://10.10.10.11/startup-config switch-hostname#exit
Attachments This solution has no attachment |
||||||||||||||
|