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 create and configure virtual service blades and includes the following sections:
•Information About Virtual Service Blades
•Configuring Virtual Service Blades
•Verifying the Virtual Service Blade Configuration
•Feature History for Virtual Service Blade
The modules (VSM, NAM, VSG, DCNM) hosted, created, and managed by the Cisco Nexus 1010 product family are called virtual service blades (VSBs). VSBs are created using ISO or OVA files found in the Cisco Nexus 1010 bootflash repository. The ISO or OVA defines the following for a VSB:
•Required number of interfaces
•Required hard disk emulation
•Disk and RAM defaults
•Type of virtual service blade
–Cisco Nexus 1000V VSM Virtual Service Blade
–Cisco Network Analysis Module Virtual Service Blade
–Cisco Virtual Security Gateway Module Virtual Service Blade
–Cisco Data Center Network Manager Module Virtual Service Blade
•For the weighting matrix, see Virtual Service Blades
The Cisco Nexus 1010 can host up to six VSMs and the Cisco Nexus 1010-X can host up to ten VSMs, each controlling a group of virtual Ethernet modules (VEMs). From a network management perspective, a VSM and its VEMs make up a virtual switch; and the Cisco Nexus 1010 and the multiple virtual switches it hosts are viewed as a cluster of switches.
You can create redundant virtual supervisor modules (VSMs) on the Cisco Nexus 1010 product family with the Cisco Nexus 1000V ISO or OVA image located in bootflash. The image is copied to a new VSB when you create it. Once you have created the first VSM, you can point to that software image to create additional VSMs. You can upgrade your VSMs to a new release of Cisco Nexus 1000V software as needed.
This section includes the following topics:
To create a VSM virtual service blade, see the "Creating a Virtual Service Blade" procedure.
The Cisco Nexus 1010 and its hosted Cisco Nexus 1000V VSMs share the same management VLAN in static topology. Unlike the control and packet VLANs which are set when a VSB is created, the management VLAN is inherited. In a static topology, the management VLAN on a VSB cannot be changed. Since the management VLAN is inherited from the Cisco Nexus 1010, if you change management VLAN for Cisco Nexus 1010, then the change is applied to both the Cisco Nexus 1010 and all of its hosted Cisco Nexus 1000V VSMs in next reload.
However, this constraint does not exist in flexible topology and the management VLAN of a VSB can be different from the Cisco Nexus 1010 host.
High availability is configured for the redundant VSB pairs that you create on the Cisco Nexus 1010.
Not all VSBs are active on the active Cisco Nexus 1010. As long as there is connectivity between the active and standby Cisco Nexus 1010, access through a serial connection is maintained to any VSB. When one Cisco Nexus 1010 fails, the remaining Cisco Nexus 1010 becomes active and all VSBs in the standby state on that Cisco Nexus 1010 become active on their own.
A VSB can be removed completely from both redundant Cisco Nexus 1010s, or from only one. If one of a redundant pair of VSBs becomes unusable, it can be removed from only the Cisco Nexus 1010 where it resides. This mitigates the recovery by preserving the remaining VSB in the pair. This may become necessary if a new instance of the VSM must be provisioned.
For more information about VSM high availability, see the Cisco Nexus 1000V High Availability and Redundancy Configuration Guide, Release 4.2(1)SV1(5.1).
You can create one network analysis module (NAM) on the Cisco Nexus 1010 or Cisco Nexus 1010-X with the NAM ISO image in the Cisco Nexus 1010 bootflash. The image is copied to a new NAM VSB when you create it.
To create a VSB for NAM, see the "Creating a Virtual Service Blade" procedure.
For more information about NAM, see the Cisco Network Analysis Module Software Documentation Guide, 4.2.
You can create up to three virtual security gateway (VSG) modules on the Cisco Nexus 1010 or Cisco Nexus 1010-X with the VSG ISO image. You can copy the VSG ISO image from the following link and then copy it to the new VSG VSB when you create it.
•www.cisco.com/go/1010download
To create a VSB for VSG, see the "Creating a Virtual Service Blade" procedure.
For more information about VSG, see the Cisco Virtual Security Gateway for Nexus 1000V Series Switch Configuration Guide.
Cisco Nexus 1010 product family does not support OVA deployment and migration on VSG VSB.
Cisco Data Center Network Manager is advanced management software that provides comprehensive life cycle management of data center LAN & SAN. DCNM enables holistic management of the data center infrastructure & optimizes overall uptime & reliability.
You can create one data center network manager module (DCNM) on the Cisco Nexus 1010 or Cisco Nexus 1010-X with the DCNM ISO image in the Cisco Nexus 1010 bootflash. The image is copied to a new DCNM VSB when you create it.
For more information about installing DCNM on Cisco Nexus 1010, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.
The following are guidelines and limitations to use when configuring virtual service blades:
•The Cisco Nexus 1010 and its hosted Cisco Nexus 1000V VSMs must share the same management VLAN.
•Unlike the control and packet VLANs which are set when a virtual service blade is created, a virtual service blade inherits its management VLAN from the Cisco Nexus 1010.
This section includes the following procedures:
•Creating a Virtual Service Blade
•Deleting a Virtual Service Blade
•Modifying a Virtual Service Blade
Use this procedure to create a virtual service blade (VSB), such as a VSM, by installing and configuring the software.
Note For information about upgrading Cisco Nexus 1000V software on an existing VSB, see the Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(5.1).
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in EXEC mode.
•You know the name of the virtual service blade that you want to create.
•You can create a new VSB using an ISO file from any of the following sources:
–From a previously-created VSB.
–Ships with the Cisco Nexus 1010 in bootflash repository:
Cisco Nexus 1000V: nexus-1010.4.2.1.SP1.4.iso
Cisco NAM: nam-app-x86_64.5-1-2.iso
Cisco VSG: nexus-1000v.VSG1.3.1.iso
Cisco DCNM: dcnm-installer-k9.5.2.2a.iso
–Downloaded from www.cisco.com/go/1010download and copied to the bootflash repository.
•If you are using an ISO file from bootflash repository or downloaded, you know the filename.
•If you are using an ISO file from an existing virtual service blade, you know the name of the virtual service blade type. This procedure includes information about identifying this name.
•You know the following properties for the virtual service blade:
–Domain ID
–Management IP address
–Management subnet mask length
–Default gateway IPV4 address
–Switchname
–Administrator password
–Control and packet VLAN IDs
•This procedure shows you how to identify and assign control and packet VLANs for the virtual service blade. Do not assign a management VLAN because the management VLAN is inherited from the Cisco Nexus 1010.
1. config t
2. virtual-service-blade name
3. show vsb-type summary
4. virtual-service-blade-type [name name | new iso file name | new ova file name]
5. description description
6. show virtual-service-blade name name
7. interface name vlan vlanid
8. enable [primary | secondary]
9. show virtual-service-blade name name
10. copy running-config startup-config
|
|
|
---|---|---|
Step 1 |
config t
Example: switch# config t switch(config)# |
Places you in the CLI Global Configuration mode. |
Step 2 |
virtual-service-blade name
Example: switch(config)# virtual-service-blade vsm-1 switch(config-vsb-config)# |
Creates the named virtual service blade and places you into configuration mode for that service. name: an alphanumeric string of up to 80 characters |
Step 3 |
show virtual-service-blade-type summary
|
Displays a summary of all virtual service blade configurations by type name, such as VSM or NAM. You use this type name in the next step. |
Example: switch(config-vsb-config)# show virtual-service-blade-type summary ------------------------------------------------------------------------------- Virtual-Service-Blade-Type Virtual-Service-Blade ------------------------------------------------------------------------------- VSM_SV1_3 vsm-1 vsm-2 NAM-MV nam-1 switch(config-vsb-config)# |
||
Step 4 |
virtual-service-blade-type [name name | new iso file name | new ova file name]
Example: switch(config-vsb-config)# virtual-service-blade-type new nexus-1000v.4.2.1.SV1.5.1.iso switch(config-vsb-config)#
Example: switch(config-vsb-config)# virtual-service-blade-type new nexus-1000v.4.2.1.SV1.5.1.1010.ova switch(config-vsb-config)# |
Specifies the type and name of the software image file to add to this virtual service blade. •name: the name of the existing virtual service blade type. Enter the name of an existing type found in the Step 5 command output. •new: the name of the new ISO or OVA software image file in bootflash repository folder. |
Step 5 |
description description
Example: switch(config-vsb-config)# description vsm hamilton storage switch(config-vsb-config)# |
(Optional) Adds a description to the virtual service blade. description: an alphanumeric string of up to 80 characters |
Step 6 |
show virtual-service-blade name name
|
Displays the virtual service blade you have just created including the interface names that you configure in the next step. |
Example: switch(config-vsb-config)# show virtual-service-blade name vsm-1 virtual-service-blade vsm-1 Description: Slot id: 1 Host Name: switch Management IP: 172.23.181.37 VSB Type Name : VSM-1.1 vCPU: 1 Ramsize: 2048 Disksize: 3 Heartbeat: 35275 ----------------------------------------------------------------------------------------- ----- Interface Type VLAN State Uplink-Interface Primary Secondary Oper Admin ----------------------------------------------------------------------------------------- ------- VsbEthernet1/1 control 423 up up Po1 Po1 VsbEthernet1/2 management 231 up up Po1 Po1 VsbEthernet1/3 packet 423 up up Po1 Po1 internal NA NA up up HA Role: Primary HA Status: ACTIVE Status: VSB POWERED ON Location: PRIMARY SW version: 4.2(1)SV1(4a) HA Role: Secondary HA Status: STANDBY Status: VSB POWERED ON Location: SECONDARY SW version: 4.2(1)SV1(4a) VSB Info: Domain ID : 441 |
||
Step 7 |
interface name vlan vlanid
Example: switch(config-vsb-config)# interface control vlan 1044 switch(config-vsb-config)#
Example: switch(config-vsb-config)# interface packet vlan 1045 switch(config-vsb-config)#
|
Applies the interface and VLAN ID to this virtual service blade. Use the interface names from Step 6 command output. Note If you attempt to apply an interface that is not present, the following error is displayed: |
Step 8 |
Repeat Step 7 to apply additional interfaces. |
|
Step 9 |
enable [primary | secondary] Example: switch(config-vsb-config)# enable Enter domain id[1-4095]: 1054 Enter Management IP address: 10.78.108.40 Enter Management subnet mask length 28 IPv4 address of the default gateway: 10.78.108.117 Enter Switchname: VSM-1 Enter the password for 'admin': Sfish123 switch(config-vsb-config)# |
Initiates the configuration of the virtual service blade and then enables it. If you are enabling a non-redundant virtual service blade, you can specify its HA role as follows: •primary: designates the virtual service blade in a primary role. •secondary: designates the virtual service blade in a secondary role. The Cisco Nexus 1010 prompts you for the following: •Domain ID •Management IP address •Management subnet mask length •Default gateway IPV4 address •Switchname •Administrator password |
Step 10 |
show virtual-service-blade name |
Displays the new virtual service blade for verification. While the switch is configuring the virtual service blade, the switch output for this command progresses from in progress to powered on. |
Example: switch(config-vsb-config)# show virtual-service-blade name vsm-1
virtual-service-blade vsm-1 Description: Slot id: 1 Host Name: switch Management IP: 172.23.181.37 VSB Type Name : VSM-1.1 vCPU: 1 Ramsize: 2048 Disksize: 3 Heartbeat: 35275 ----------------------------------------------------------------------------------------- Interface Type VLAN State Uplink-Interface Primary Secondary Oper Admin ----------------------------------------------------------------------------------------- VsbEthernet1/1 control 423 up up Po1 Po1 VsbEthernet1/2 management 231 up up Po1 Po1 VsbEthernet1/3 packet 423 up up Po1 Po1 internal NA NA up up HA Role: Primary HA Status: ACTIVE Status: VSB POWERED ON Location: PRIMARY SW version: 4.2(1)SV1(4a) HA Role: Secondary HA Status: STANDBY Status: VSB POWERED ON Location: SECONDARY SW version: 4.2(1)SV1(4a) VSB Info: Domain ID : 441 switch(config-vsb-config)# switch# switch(config-vsb-config)#
|
||
Step 11 |
copy running-config startup-config
Example: switch(config-vsb-config)# copy running-config startup-config |
Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration. |
Use this procedure to delete a virtual service blade, such as a VSM or NAM.
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in EXEC mode.
•You know the name of the virtual service blade you are deleting.
•You must shut down the virtual service blade before it can be deleted. This procedure includes instructions for shutting down the virtual service blade.
•A virtual service blade can be removed completely from both redundant Cisco Nexus 1010s, or from only one. If one of a redundant pair of virtual service blade blades becomes unusable, it can be removed from only the Cisco Nexus 1010 where it resides. This mitigates the recovery by preserving the remaining virtual service blade in the pair. This may become necessary if a new instance of the service must be provisioned.
1. config t
2. virtual-service-blade name
3. shutdown
4. show virtual-service-blade summary
5. One of the following:
–no virtual-service-blade name
–no enable
6. show virtual-service-blade summary
7. copy running-config startup-config
Use this section to modify the control VLAN, packet VLAN, or the RAM size of a virtual service blade and then make the corresponding changes to the VSM.
This section includes the following topics:
•Modifying a Virtual Service Blade on the Cisco Nexus 1010
•Modifying a VSM on the Cisco Nexus 1000V
Use this procedure to modify the control VLAN, packet VLAN, or the RAM size of a virtual service blade.
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in EXEC mode.
•You know the name of the virtual service blade you are modifying.
•You must shut down the virtual service blade before modifying the RAM size. This procedure includes instructions for shutting down the virtual service blade.
•You must shut down the virtual service blade before modifying the control VLAN. This procedure includes instructions for shutting down the virtual service blade.
•You change the configuration first in the virtual service blade configuration and, then, in the Cisco Nexus 1000V VSM configuration. This procedure changes the virtual service blade configuration. To change the Cisco Nexus 1000V configuration, see the "Modifying a VSM on the Cisco Nexus 1000V" procedure.
1. config t
2. virtual-service-blade name
3. Do one of the following:
–If you are modifying the ram size or the control VLAN, then continue with the next step.
–Otherwise, go to Step 6.
4. shutdown
5. show virtual-service-blade summary
6. One of the following:
–ramsize size
–interface control vlan vlanid
–interface control vlan vlanid
7. no shutdown
8. show virtual-service-blade name name
9. copy running-config startup-config
|
|
|
---|---|---|
Step 1 |
config t
Example: switch# config t switch(config)# |
Places you in the CLI Global Configuration mode. |
Step 2 |
virtual-service-blade name
Example: switch(config)# virtual-service-blade vsm-5 switch(config-vsb-config)# |
Places you into configuration mode for the named virtual service blade. |
Step 3 |
Do one of the following: •If you are modifying the RAM size or the control VLAN, then continue with the next step. •Otherwise, go to Step 6. |
|
Step 4 |
shutdown
Example: switch(config-vsb-config)# shutdown switch(config-vsb-config)# |
Shuts down the virtual service blade. |
Step 5 |
show virtual-service-blade summary
|
Displays a summary of services for verification of the shutdown. |
Example: ----------------------------------------------------------------------------------------- Name HA-Role HA-Status Status Location ----------------------------------------------------------------------------------------- vsm-1 PRIMARY ACTIVE VSB POWERED ON PRIMARY vsm-1 SECONDARY STANDBY VSB POWERED ON SECONDARY
switch(config-vsb-config)#
|
||
Step 6 |
One of the following: •ramsize size •interface control vlan vlanid •interface packet vlan vlanid
Example: switch(config-vsb-config)# ramsize 1024 switch(config-vsb-config)#
Example: switch(config-vsb-config)# interface control vlan 1116 switch(config-vsb-config)#
Example: switch(config-vsb-config)# interface packet vlan 1117 switch(config-vsb-config)#
|
Modifies the virtual service blade. You can modify any of the following virtual service blade parameters: •memory allocated for RAM (1024-4096 MB). •control VLAN ID •packet VLAN ID |
Step 7 |
no shutdown
Example: switch(config-vsb-config)# no shutdown switch(config-vsb-config)# |
Returns the virtual service blade status to powered on. |
Step 8 |
show virtual-service-blade name name
|
Displays the virtual service blade information for verification of the changes. |
Example: switch(config-vsb-config)# show virtual-service-blade name vsm-1 virtual-service-blade vsm-1 Description: Slot id: 1 Host Name: switch Management IP: 172.23.181.37 VSB Type Name : VSM-1.1 vCPU: 1 Ramsize: 2048 Disksize: 3 Heartbeat: 35275 ----------------------------------------------------------------------------------------- Interface Type VLAN State Uplink-Interface Primary Secondary Oper Admin ----------------------------------------------------------------------------------------- VsbEthernet1/1 control 423 up up Po1 Po1 VsbEthernet1/2 management 231 up up Po1 Po1 VsbEthernet1/3 packet 423 up up Po1 Po1 internal NA NA up up HA Role: Primary HA Status: ACTIVE Status: VSB POWERED ON Location: PRIMARY SW version: 4.2(1)SV1(4a) HA Role: Secondary HA Status: STANDBY Status: VSB POWERED ON Location: SECONDARY SW version: 4.2(1)SV1(4a) VSB Info: Domain ID : 441 switch(config-vsb-config)#
|
||
Step 9 |
copy running-config startup-config
Example: switch(config)# copy running-config startup-config |
Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration. |
Step 10 |
You have completed this procedure. You must now update the VSM configuration using the "Modifying a VSM on the Cisco Nexus 1000V" procedure. |
Use this procedure to modify the control VLAN ID, packet VLAN ID, or RAM size in the VSM configuration on the Cisco Nexus 1000V.
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in EXEC mode.
•You know the name of the VSM you are modifying.
•You change the configuration first in the Cisco Nexus 1010 virtual service blade configuration and, then, in the Cisco Nexus 1000V VSM configuration. This procedure changes the Cisco Nexus 1000V VSM configuration. To change the Cisco Nexus 1010 virtual service blade configuration, see the "Modifying a Virtual Service Blade on the Cisco Nexus 1010" procedure.
1. login virtual-service-blade vb6
2. login
3. password
4. show svs domain
5. config t
6. svs-domain
7. control vlan vlanid
8. packet vlan vlanid
9. show svs domain
10. copy running-config startup-config
11. Ctrl \
12. close
To verify the virtual service blade configuration, use the following commands:
|
|
---|---|
show virtual-service-blade [name name] |
Displays the configuration for a specific virtual service blade. See Example 4-3 |
show virtual-service-blade summary |
Displays a summary of all virtual service blade configurations. Note This command is only recognized by the primary Cisco Nexus 1010. See Example 4-4 |
show virtual-service-blade-type summary |
Displays a summary of all virtual service blade configurations by type, such as VSM or NAM. See Example 4-1 |
show network-uplink type |
Displays the uplink configuration for verification. See Example 4-2 |
Example 4-1 Virtual Service Blade Type
n1010# show virtual-service-blade-type summary
-------------------------------------------------------------------------------
Virtual-Service-Blade-Type Virtual-Service-Blade
-------------------------------------------------------------------------------
VSM_SV1_3 vsm-1
vsm-2
NAM-MV nam-1
n1010#
Example 4-2 Network Uplink Type
n1010# show network uplink type
Administrative topology id: 2
Operational topology id: 1
n1010#
Example 4-3 Virtual Service Blade
virtual-service-blade vsm-1
Description:
Slot id: 1
Host Name: switch
Management IP: 172.23.181.37
VSB Type Name : VSM-1.1
vCPU: 1
Ramsize: 2048
Disksize: 3
Heartbeat: 35275
----------------------------------------------------------------------------------------------
Interface Type VLAN State Uplink-Interface
Primary Secondary Oper Admin
------------------------------------------------------------------------------------------------
VsbEthernet1/1 control 423 up up Po1 Po1
VsbEthernet1/2 management 231 up up Po1 Po1
VsbEthernet1/3 packet 423 up up Po1 Po1
internal NA NA up up
HA Role: Primary
HA Status: ACTIVE
Status: VSB POWERED ON
Location: PRIMARY
SW version: 4.2(1)SV1(4a)
HA Role: Secondary
HA Status: STANDBY
Status: VSB POWERED ON
Location: SECONDARY
SW version: 4.2(1)SV1(4a)
VSB Info:
Domain ID : 441
Example 4-4 Virtual Service Blade Summary
n1010# show virtual-service-blade summary
---------------------------------------------------------------------------------------------------
Name HA-Role HA-Status Status Location
---------------------------------------------------------------------------------------------------
vsm-1 PRIMARY ACTIVE VSB POWERED ON PRIMARY
vsm-1 SECONDARY STANDBY VSB POWERED ON SECONDARY
For additional information related to implementing system-level HA features, see the following sections:
•MIBs
•RFCs
|
|
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
|
|
---|---|
•CISCO-PROCESS-MIB |
To locate and download MIBs, go to the following URL: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml |
|
|
---|---|
No RFCs are supported by this feature |
— |
This section provides the virtual service blade blade release history.