Exporting and Importing a VSB
This chapter describes how to back up and recover a virtual service blade (VSB), and includes the following sections:
Information about Exporting and Importing a VSB
You can export or import a VSB on the Cisco Nexus Cloud Services Platforms by creating a copy of the VSB backup file. You can store the backup copy remotely to use as a recovery mechanism, or when you need to move a VSB between Cisco Nexus Cloud Services Platforms. Use the procedures in the following sections to export and import a VSB on the Cisco Nexus Cloud Services Platform.
Guidelines and Limitations
The following are guidelines and limitations to use when backing up and recovering a VSB:
- You can create multiple export files with this process. Do not change the file suffix for numbering purposes. If you change the prefix for one file, you must change it for all files.
- You must shut down the VSB before creating the file to export.
- The bootflash: export-import directory must be empty before you create an export file or copy the file from external storage.
Exporting a VSB
You can create a backup copy of a VSB, store it remotely, and then reimport it to either recover a VSM, or move a VSB between Cisco Nexus Cloud Services Platforms. This section includes the following topics:
Exporting a VSB Backup File
You can create a backup file for exporting a VSB.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
- Log in to the CLI of the Cisco Nexus Cloud Services Platform in EXEC mode.
- Know the name of the VSB for which you are creating a file to export.
- Execute the copy running-config startup-config command to copy the running configuration to the startup configuration before you begin this procedure.
- Verify that the bootflash: export-import directory is empty. If files are present in this directory, you must delete them before starting this procedure.
- Shut down the VSB that you want to back up before creating the file to export. This procedure includes a step for shutting down the VSB and then a step to restart the VSB after creating the file.
Note You can create multiple files. Do not change the file suffix for numbering purposes. If you change the prefix for one file, you must change it for all files.
SUMMARY STEPS
1. dir bootflash:export-import
2. (Optional) delete foldername
3. config t
4. virtual-service-blade name
5. shutdown [primary | secondary]
6. show virtual-service-blade summary
7. export [primary | secondary]
8. dir bootflash:export-import
9. no shutdown [primary | secondary]
10. show virtual-service-blade summary
DETAILED STEPS
|
|
|
Step 1 |
dir bootflash:export-import Example: switch# dir bootflash:export-import DOCS-CPPA# dir export-import Usage for bootflash://sup-local 496164864 bytes used 3495215104 bytes free 3991379968 bytes total switch# |
Displays the contents of the export-import directory for verification that the directory is empty. If there is anything in this directory, you must use the next step to delete it before proceeding. |
Step 2 |
delete bootflash:export-import foldername Example: switch-1(config-vsb-config)# delete bootflash:/export-import/1/*.* switch-1(config-vsb-config)# delete bootflash:/export-import/1 switch-1(config-vsb-config)# |
(Optional) Deletes the VSB compressed tar file and its folder created for export. |
Step 3 |
configure terminal Example: switch-1# configure terminal switch-1(config)# |
Enters global configuration mode. |
Step 4 |
virtual-service-blade name Example: switch-1(config)# virtual-service-blade vsm-1 switch-1(config-vsb-config)# |
Enters the configuration mode for the named virtual service blade. |
Step 5 |
shutdown [primary | secondary] Example: switch-1(config-vsb-config)# shutdown secondary switch-1(config-vsb-config)# |
Shuts down the VSB that you are exporting from. If you have a redundant pair of Cisco Nexus Cloud Services Platforms, you must specify whether to shut down the primary or secondary. |
Step 6 |
show virtual-service-blade summary |
(Optional) Displays the virtual service blade configuration for verification. |
|
Example: switch-1(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- VSM1 PRIMARY VSB POWERED ON Nexus1010-PRIMARY VSM1 SECONDARY VSB POWERED OFF Nexus1010-SECONDARY |
Step 7 |
export [primary | secondary] Example: switch-1(config-vsb-config)# export secondary Note: export started.. Note: please be patient.. Note: please be patient.. Note: please be patient.. Note: export completed...switch-1(config-vsb-config)# Example: switch-1(config-vsb-config)# export primary ERROR: Please clean export-import directory first, then proceed. switch-1(config-vsb-config)# Example: switch-1(config-vsb-config)# export secondary ERROR: Cannot export active virtual-service-blade, please shut and retry. |
Creates a directory named for the slot ID of the exported VSB that contains a compressed tar image of the VSB. If exporting from a redundant pair of Cisco Nexus Cloud Services Platforms, you must specify whether you are exporting from the primary or secondary. Note The export command does not move the configuration file off of the Cisco Nexus Cloud Services Platform. The export command creates a backup copy that you must then copy to the remote storage location. |
Step 8 |
dir bootflash:export-import Example: switch-1(config-vsb-config)# dir bootflash:export-import 4096 Sep 08 19:12:52 2011 1/ Usage for bootflash://sup-local 310870016 bytes used 3680509952 bytes free 3991379968 bytes total |
Displays the contents of the bootflash: export-import directory, including the directory name of the folder that contains the compressed tar image of the VSB, for verification. Note You need this folder name in Step 11. |
Step 9 |
no shutdown [primary | secondary] Example: switch-1(config-vsb-config)# no shutdown secondary switch-1(config-vsb-config)# |
Powers on the VSB that was powered off when creating the file for export. If you have a redundant pair of Cisco Nexus Cloud Services Platforms, you must specify primary or secondary. |
Step 10 |
show virtual-service-blade summary |
Displays the VSB configuration for verification. |
|
Example: switch-1(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- VSM1 PRIMARY VSB POWERED ON Nexus1010-PRIMARY VSM1 SECONDARY VSB POWERED ON Nexus1010-SECONDARY |
Step 11 |
dir bootflash:export-import / directory-name Example: switch-1(config-vsb-config)# dir bootflash:export-import/1 279955021 Sep 08 19:13:21 2011 Vdisk1.img.tar.00 Usage for bootflash://sup-local 310870016 bytes used 3680509952 bytes free 3991379968 bytes total |
Displays the contents of the Cisco Nexus Cloud Services Platform export folder, including the filename of the VSB compressed tar image. Note You identified this folder name in Step 8. Note You can create multiple files. Do not change the file suffix for numbering purposes. If you change the prefix for one file, then you must change it for all files. |
Copying the Exported VSB to an External Storage Location
You can copy the exported VSB to a remote storage location and then delete the folder created for this purpose from the Cisco Nexus Cloud Services Platform.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
- You have created a file to export using the instructions in the Exporting a VSB Backup File section and you know the name of this file and the name of the folder it resides in.
Note You can create multiple files. If so, use the first filename in this procedure. Do not change the file suffix for numbering purposes. If you change the prefix for one file, you must change it for all files.
- Log in to the CLI of the Cisco Nexus Cloud Services Platform in EXEC mode.
- Know the name of the path to a remote storage location.
- After copying the export backup file, delete the contents, including the files and folders, of the export-import directory. Do not delete the export-import folder.
SUMMARY STEPS
1. copy bootflash:export-import/ folder-name / filename ftp:
2. delete foldername
3. dir
DETAILED STEPS
|
|
|
Step 1 |
copy bootflash:export-import / folder-name / filename ftp: Example: switch# copy bootflash:export-import/1/Vdisk1.img.tar.00 ftp: Enter vrf (If no input, current vrf 'default' is considered): Enter hostname for the ftp server: 10.78.109.51 Enter username: administrator Password: ***** Transfer of file Completed Successfully ***** switch# |
Copies the VSB image from the Cisco Nexus Cloud Services Platform export-import folder to a remote storage location. |
Step 2 |
delete bootflash:export-import foldername Example: switch# delete bootflash:/export-import/1/Vdisk1.img.tar.00 switch# delete bootflash:/export-import/1 switch# |
Deletes the VSB compressed tar file and its folder created for export. |
Step 3 |
dir Example: switch# dir switch# |
Displays the contents of the export-import directory for verification. |
Importing a VSB
You can import a previously saved location backup copy of a VSB from a remote storage location to the Cisco Nexus Cloud Services Platform.
BEFORE YOU BEGIN
- Log in to the CLI of the active Cisco Nexus Cloud Services Platform in EXEC mode.
- You have previously created and saved a copy of the VSB configuration in a remote storage location using the instructions in Exporting a VSB.
Note You can create multiple. If so, use only the first filename with the import command. Do not change the file suffix for numbering purposes. If you change the prefix for one file, then you must change it for all files.
- Know the name of the VSB and the path to the remote storage location.
- Verify that the bootflash: export-import directory is empty. If files are present in this directory, you must delete them before importing a VSB configuration file.
SUMMARY STEPS
1. dir bootflash:export-import
2. (Optional) delete foldername
3. copy ftp: filename bootflash:export-import
4. config t
5. virtual-service-blade name
6. import [primary | secondary] filename
7. show virtual-service-blade summary
8. configure uplinks
9. no shutdown primary filename
10. show virtual-service-blade name name
11. copy running-config startup-config
DETAILED STEPS
|
|
|
Step 1 |
dir bootflash:export-import Example: switch# dir bootflash export-import DOCS-CPPA# dir export-import Usage for bootflash://sup-local 496164864 bytes used 3495215104 bytes free 3991379968 bytes total switch# |
Displays the contents of the export-import directory for verification that the directory is empty. If there is anything in this directory, you must use the next step to delete it before proceeding. |
Step 2 |
(Optional) delete bootflash:export-import foldername Example: switch-1(config-vsb-config)# delete Vdisk1.img.tar.00 switch-1(config-vsb-config)# |
(Optional) Deletes the VSB compressed tar file and its folder created for export. |
Step 3 |
copy ftp: filename bootflash:export-import Example: switch# copy ftp:Vdisk1.img.tar.00 bootflash:export-import Enter vrf (If no input, current vrf 'default' is considered): Enter hostname for the ftp server: 10.78.109.51 Enter username: administrator Password: ***** Transfer of file Completed Successfully ***** |
Copies the exported image file from a remote storage location into the Cisco Nexus Cloud Services Platform export-import folder in the bootflash: repository.
- The filename argument is the name of the export file. Multiple files may have been created. If so, copy these files into export-import directory and use only the first filename with the import command. Do not change the file suffix for numbering purposes. If you change the prefix for one file, then you must change it for all.
|
Step 4 |
configure terminal Example: switch-1# configure terminal switch-1(configure)# |
Enters the global configuration mode. |
Step 5 |
virtual-service-blade name Example: switch-1(config)# virtual-service-blade vsm-5 switch-1(config-vsb-config)# |
Enters the configuration mode for the named virtual service blade. |
Step 6 |
import primary filename Example: switch-1(config-vsb-config)# import primary Vdisk1.img.tar.00 Note: import started.. Note: please be patient.. Note: Import cli returns check VSB status for completion switch-1(config-vsb-config)# |
Powers off the primary VSB, imports the specified VSB configuration file, and then removes the configuration file from the export-import folder.
- The filename argument is the name of the export file that you copied from the remote server to the bootflash: repository.
|
Step 7 |
show virtual-service-blade summary |
(Optional) Displays a summary of all VSB configurations by type name, such as VSM or NAM. Verify that the primary VSB is powered off. |
Step 8 |
Configure the network uplinks by completing the following set of tasks. These tasks might vary based on the network topology and uplink types:
- Modifying the uplink type
- Migrating from static to flexible uplink
- Migrating from flexible to static uplink
- Configuring port channels
- Assigning uplinks to a VSB Interface
|
Configures your network uplinks with the procedures listed in the Configuring Network Uplink Types section. |
Step 9 |
no shutdown primary filename Example: switch-1(config)# virtual-service-blade VSM1 switch-1(config)# no shutdown primary switch-1(config)# |
Powers on the primary VSB and imports the primary VSB configuration.
- The filename argument is the name of the imported primary VSB
|
|
Example: switch-1(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- VSM1 PRIMARY VSB POWERED OFF Nexus1010-PRIMARY VSM1 SECONDARY VSB POWERED ON Nexus1010-SECONDARY |
Step 10 |
show virtual-service-blade name name |
Displays the virtual service blade information for verification. From the command output, make a note of the control and management VSB Ethernet interfaces. |
|
Example: switch-1(config-vsb-config)# show virtual-service-blade name VSM1 virtual-service-blade VSM1 Description: Slot id: 1 Host Name: Management IP: VSB Type Name : VSM-1.1 vCPU: 1 Ramsize: 2048 Disksize: 3 Heartbeat: 0 HA Admin role: Primary HA Oper role: NONE Status: VSB POWERED OFF Location: PRIMARY SW version: VsbEthernet1/1/1: control vlan: 1306 state: up VsbEthernet1/1/2: management vlan: 1304 state: up VsbEthernet1/1/3: packet vlan: 1307 state: up Interface: internal vlan: NA state: up HA Admin role: Secondary HA Oper role: NONE Status: VSB POWERED ON Location: SECONDARY SW version: VSB Info: switch-1(config-vsb-config)# |
Step 11 |
copy running-config startup-config Example: switch-1(config-vsb-config)# copy running-config startup-config |
Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration. |
Verifying the Export and Import of a VSB
To verify the backup and recovery, use the following commands:
|
|
dir bootflash:export-import / folder-name |
Displays the contents of the export-import directory folder. See Example 6-1 on page 6-10 . |
show virtual-service-blade summary |
Displays the redundancy state (active or standby) and the redundancy role (primary or secondary) for each VSB. See Example 6-2 on page 6-10 . |
show virtual-service-blade [name name ] |
Displays the configuration for a specific virtual service blade. See Example 6-3 on page 6-11 . |
Example 6-1 export-import Directory
switch-1(config-vsb-config)# dir bootflash:export-import/1
279955021 Sep 08 19:13:21 2011 Vdisk1.img.tar.00
Usage for bootflash://sup-local
310870016 bytes used
3680509952 bytes free
3991379968 bytes total
Example 6-2 Virtual Service Blade Summary
switch-1(config-vsb-config)# show virtual-service-blade summary
-------------------------------------------------------------------------------
Name Role State Nexus1010-Module
-------------------------------------------------------------------------------
VSM1 PRIMARY VSB POWERED OFF Nexus1010-PRIMARY
VSM1 SECONDARY VSB POWERED ON Nexus1010-SECONDARY
Example 6-3 Virtual Service Blade
switch# show virtual-service-blade name VSM1
virtual-service-blade VSM1
Description:
Slot id: 1
Host Name:
Management IP:
VSB Type Name : VSM-1.1
vCPU: 1
Ramsize: 2048
Disksize: 3
Heartbeat: 0
HA Admin role: Primary
HA Oper role: NONE
Status: VSB POWERED OFF
Location: PRIMARY
SW version:
VsbEthernet1/1/1: control vlan: 1306 state: down
VsbEthernet1/1/2: management vlan: 1304 state: down
VsbEthernet1/1/3: packet vlan: 1307 state: up
Interface: internal vlan: NA state: up
HA Admin role: Secondary
HA Oper role: NONE
Status: VSB POWERED ON
Location: SECONDARY
SW version:
VSB Info:
switch-1(config)#
Additional References
For additional information related to VSB backup and recovery features, see the following sections:
Related Documents
|
|
Software setup configuration |
Cisco Nexus Cloud Services Platform Software Installation and Upgrade Guide, Release 4.2(1)SP1(6.1) |
VSB Configuration |
Configuring Virtual Service Blades section |
Cisco Nexus Cloud Services Platform installation |
Cisco Nexus Cloud Services Platform Hardware Installation Guide |
Complete command syntax, command modes, command history, defaults, usage guidelines, and examples for all Cisco Nexus Cloud Services Platform commands. |
Cisco Nexus Cloud Services Platform Command Reference, Release 4.2(1)SP1(6.1) |
Feature History for Export and Import
This section provides the export and import feature release history.
|
|
|
VSB export and import |
4.2(1)SP1(3) |
This feature was introduced. |