The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to backup and recover a VSB, and includes the following sections:
You can create a backup copy of a VSB and store it remotely to use as a recovery mechanism or when you need to move a VSB between Cisco Nexus Virtual Services Appliances.
Figure 6-1 shows the process for backing up and recovering a VSB.
The following are guidelines and limitations to use when backing up and recovering a VSB:
This section includes the following topics and procedures:
You can use the following process for backing up and restoring a VSB configuration.
Figure 6-1 Flow Chart: Backing Up and Restoring a VSB Configuration
You can use the following procedures to create a backup copy of a VSB, store it remotely, and then re-import it to either recover a VSM or move a VSB between Cisco Nexus Virtual Services Appliances.
You can use this procedure to create a file for exporting a VSB.
Before beginning this procedure, you must know or do the following:
NoteMultiple files may be created. Do not change the file suffix for numbering purposes. If you change the prefix for one file, then you must change it for all.
1. dir bootflash:export-import
2. (Optional) delete bootflash:export-import foldername
5. shutdown [primary | secondary]
6. show virtual-service-blade summary
7. export [primary | secondary]
8. dir bootflash:export-import
|
|
|
---|---|---|
switch# dir bootflash:export-import |
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. |
|
delete bootflash:export-import foldername switch-1(config-vsb-config)# delete bootflash:/export-import/1/*.* switch-1(config-vsb-config)# delete bootflash:/export-import/1 |
Deletes the VSB compressed tar file and its folder created for export. |
|
Enters configuration mode for the named virtual service blade. |
||
shutdown [primary | secondary] |
Shuts down the VSB you are exporting from. If a redundant pair of Cisco Nexus Virtual Services Appliances, you must specify whether to shut down the primary or secondary. |
|
Displays the virtual service blade configuration for verification. |
||
switch-1(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- VSM1 PRIMARY VSB POWERED ON Nexus1010-PRIMARY |
||
switch-1(config-vsb-config)# export secondary Note: export completed...switch-1(config-vsb-config)# switch-1(config-vsb-config)# export primary ERROR: Please clean export-import directory first, then proceed. 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 containing a compressed tar image of the VSB. If exporting from a redundant pair of Cisco Nexus Virtual Services Appliances, you must specify whether exporting from the primary or secondary. Note The export command does not move the configuration file off of the Cisco Nexus Virtual Services Appliance. The export command creates a backup copy that you must then copy to remote storage. There is a separate procedure for this. |
|
switch-1(config-vsb-config)# dir bootflash:export-import |
Displays the contents of the bootflash: export-import directory, including the directory name of the folder containing the compressed tar image of the VSB, for verification. Note You need this folder name in Step 11. |
|
no shutdown [primary | secondary] |
Powers on the VSB that was powered off when creating the file for export. If a redundant pair of Cisco Nexus Virtual Services Appliances, you must specify primary or secondary. |
|
Displays the virtual service blade configuration for verification. |
||
switch-1(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- VSM1 PRIMARY VSB POWERED ON Nexus1010-PRIMARY |
||
dir bootflash:export-import switch-1(config-vsb-config)# dir bootflash:export-import/1 279955021 Sep 08 19:13:21 2011 Vdisk1.img.tar.00 |
Displays the contents of the Cisco Nexus Virtual Services Appliance export folder, including the filename of the VSB compressed tar image. Note You identified this folder name in Step 8. Note Multiple files may be created. Do not change the file suffix for numbering purposes. If you change the prefix for one file, then you must change it for all. |
Use this procedure to copy a VSB configuration file to remote storage and then delete the folder created for this purpose from the Cisco Nexus Virtual Services Appliance.
Before beginning this procedure, you must know or do the following:
NoteMultiple files may be created. 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, then you must change it for all.
1. copy bootflash:export-import/ folder-name / filename ftp:
You can use the following procedure to import a previously-saved backup copy of a VSB from remote storage to the Cisco Nexus Virtual Services Appliance.
NoteMultiple files may be created. 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.
1. dir bootflash:export-import
2. (Optional) delete bootflash:export-import foldername
3. copy ftp: filename bootflash:export-import
6. import [primary | secondary] filename
7. show virtual-service-blade summary
You can use this procedure to recover a VSM using a backup configuration file.
Before beginning this procedure, you must know or do the following:
– HA Role (must be set to the same role as that of the VSM on which it is imported)
For detailed information about setting up the VSM software, see the Cisco Nexus 1000V Getting Started Guide, Release 4.2(1)SV1(5.1)
For detailed information about the vCenter server connection, see the
Step 1 From the Cisco Nexus Virtual Services Appliance, shut down the control and management interfaces of the VSM VSB.
switch-1(config)# interface vethernet1/1
The VSM management and control interfaces are no longer communicating with VEMs and vCenter.
Step 2 Verify that the control and management interfaces are down.
show virtual-service-blade name name
switch-1(config)# show virtual-service-blade name VSM1
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
virtual-service-blade name
no shutdown [primary | secondary]
switch-1(config)# virtual-service-blade VSM1
switch-1(config)# no shutdown primary
Step 4 Log in to Cisco Nexus Virtual Services Appliance serial port of the primary VSM.
Step 5 Erase the startup configuration.
The previous configuration is erased. You will replace it with the previously-saved backup of your running configuration in Step 11.
The Cisco Nexus Virtual Services Appliance boots up and the setup wizard starts.
Step 7 Use the setup wizard to configure the VSM. Accept defaults for all except the following:
The system summarizes the new setup configuration.
Step 8 Copy the running configuration to the startup configuration.
copy running-config startup-config
n1000v# copy running-config startup-config
[########################################] 100%
Step 9 Reopen the management interface of the VSM VSB.
switch-1(config)# interface vethernet1/2
The VSM management interface is again communicating with VEMs and vCenter.
Step 10 Verify that the management interface is up.
show virtual-service-blade name name
switch-1(config)# show virtual-service-blade name VSM1
VsbEthernet1/1/1: control vlan: 1306 state: down
VsbEthernet1/1/2: management vlan: 1304 state: up
VsbEthernet1/1/3: packet vlan: 1307 state: up
Interface: internal vlan: NA state: up
Step 11 Copy your saved running configuration backup to the VSM bootflash.
Step 12 Copy the running configuration to the startup configuration.
copy running-config startup-config
n1000v# copy running-config startup-config
[########################################] 100%
Step 13 Reopen the control interface of the VSM VSB.
switch-1(config)# interface vethernet1/1
The VSM control interface is again communicating with VEMs and vCenter.
Step 14 Verify that the control interface is up.
show virtual-service-blade name name
switch-1(config)# show virtual-service-blade name VSM1
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
Step 15 Check the modules by entering the show module command at the VSM CLI.
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
1 0 Virtual Supervisor Module Nexus1000V active *
2 0 Virtual Supervisor Module Nexus1000V ha-standby
3 248 Virtual Ethernet Module NA ok
4 248 Virtual Ethernet Module NA ok
--- ---------------- ------------------------------------------------
3 4.2(1)SV1(4a) VMware ESXi 4.0.0 Releasebuild-208167 (1.9)
4 4.2(1)SV1(4a) VMware ESX 4.1.0 Releasebuild-260247 (2.0)
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
2 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
3 02-00-0c-00-03-00 to 02-00-0c-00-03-80 NA
4 02-00-0c-00-04-00 to 02-00-0c-00-04-80 NA
Mod Server-IP Server-UUID Server-Name
--- --------------- ------------------------------------ --------------------
3 10.78.109.72 44454c4c-4300-1046-8043-b6c04f563153 10.78.109.72
4 10.78.109.71 44454c4c-3300-1056-8057-b3c04f583153 10.78.109.71
switch-1(config)# enable secondary
The VSM is again operating in HA mode with a primary and secondary module.
Step 17 You have completed this procedure.
To verify the backup and recovery, use the following commands:
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
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
VsbEthernet1/1/1: control vlan: 1306 state: down
VsbEthernet1/1/2: management vlan: 1304 state: down
VsbEthernet1/1/3: packet vlan: 1307 state: up
For additional information related to implementing system-level HA features, see the following sections:
|
|
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
|
|
---|---|
|
|
---|---|
This section provides the export and import feature release history.
|
|
|
---|---|---|