Cisco Nexus 1010 Software Configuration Guide, Release 4.2(1) SP1(2)

Bias-Free Language

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.

Book Contents

Find Matches in This Book

Available Languages

Download Options

Book Title

Cisco Nexus 1010 Software Configuration Guide, Release 4.2(1) SP1(2)

Chapter Title

Configuring Virtual Services

PDF - Complete Book (2.72 MB) PDF - This Chapter (193.0 KB)
View with Adobe Reader on a variety of devices

Results

Updated:: February 1, 2011

Chapter: Configuring Virtual Services

Guidelines and Limitations
Creating a Virtual Service Blade
Deleting a Virtual Service Blade
Modifying a Virtual Service Blade
- Modifying a Virtual Service Blade on the Cisco Nexus 1010
- Modifying a VSM on the Cisco Nexus 1000V
Verifying the Virtual Service Blade Configuration
Additional References
- Related Documents
- Standards
- MIBs
- RFCs
Feature History for Virtual Service Blade

Configuring Virtual Service Blades

This chapter describes how to create and configure virtual service blades and includes the following sections:

•Guidelines and Limitations

•Creating a Virtual Service Blade

•Deleting a Virtual Service Blade

•Modifying a Virtual Service Blade

•Verifying the Virtual Service Blade Configuration

•Additional References

•Feature History for Virtual Service Blade

Guidelines and Limitations

Follow these guidelines and limitations 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.

Caution Do not change the management VLAN on a virtual service blade. Since the management VLAN is inherited from the Cisco Nexus 1010, if you change it, then the change is applied to both the Cisco Nexus 1010 and all of its hosted Cisco Nexus 1000V VSMs.

Creating 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(4).

BEFORE YOU BEGIN

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 know whether you are using a new ISO file from the bootflash repository folder or from an existing virtual service blade.

–If you are using a new ISO file in the bootflash repository, you know the filename.

Cisco Nexus 1000V: nexus-1000v.4.0.4.SV1.3.iso

Cisco NAM: nam-4-2-1.iso

–If you are using an ISO file from an existing virtual service blade, you must 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.

SUMMARY STEPS

1. config t

2. virtual-service-blade name

3. show vsb-type summary

4. virtual-service-blade-type [name name | new iso 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

DETAILED STEPS


	Command	Purpose
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] Example: switch(config-vsb-config)# virtual-service-blade-type new nexus-1000v.4.0.4.SV1.3.iso switch(config-vsb-config)# Example: switch(config-vsb-config)# virtual-service-blade-type name VSM-1.1 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 Cisco Nexus 1000V or Cisco NAM ISO 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 Example: switch(config-vsb-config)# show virtual-service-blade name vsm-2 virtual-service-blade vsm2 Description: Slot id: 2 Host Name: Management IP: VSB Type Name : VSM-1.0 Interface: control vlan: 0 Interface: management vlan: 231 Interface: packet vlan: 0 Interface: internal vlan: NA Ramsize: 2048 Disksize: 3 Heartbeat: 0 HA Admin role: Primary HA Oper role: NONE Status: VSB NOT PRESENT Location: PRIMARY SW version: HA Admin role: Secondary HA Oper role: NONE Status: VSB NOT PRESENT Location: SECONDARY SW version: VSB Info: switch(config-vsb-config)#	Displays the virtual service blade you have just created including the interface names that you configure in the next step.
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: ERROR: Interface name not found in the associated virtual-service-blade type Caution Do not assign a management VLAN. Unlike control and packet VLANs, the management VLAN is inherited from the Cisco Nexus 1010. Caution To prevent loss of connectivity, you must configure the same control and packet VLANs on the hosted VSMs.
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 This must be a different domain ID than the one you used for the Cisco Nexus 1010. •Management IP address •Management subnet mask length •Default gateway IPV4 address •Switchname •Administrator password
Step 10	show virtual-service-blade name Example: switch(config-vsb-config)# show virtual-service-blade name vsm-1 virtual-service-blade vsm-1 Description: Slot id: 1 SW version: 4.0(4)SV1(3) Host Name: vsm-1 Management IP: 10.78.108.40 VSB Type Name : VSM-1.1 Interface: control vlan: 1044 Interface: management vlan: 1032 Interface: packet vlan: 1045 Interface: internal vlan: NA Ramsize: 2048 Disksize: 3 Heartbeat: 1156 HA Admin role: Primary HA Oper role: STANDBY Status: VB POWERED ON Location: PRIMARY HA Admin role: Secondary HA Oper role: ACTIVE Status: VB POWERED ON Location: SECONDARY VB Info: Domain ID : 1054 switch(config-vsb-config)#	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.
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.

Deleting a Virtual Service Blade

Use this procedure to delete a virtual service blade, such as a VSM or NAM.

BEFORE YOU BEGIN

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.

SUMMARY STEPS

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

DETAILED STEPS


	Command	Purpose
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	shutdown Example: switch(config-vsb-config)# shutdown switch(config-vsb-config)#	Shuts down the virtual service blade.
Step 4	show virtual-service-blade summary	Displays a summary of services for verification of the shutdown.
	Example: switch(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- vsm-1 PRIMARY VSB POWERED ON Nexus1010-PRIMARY vsm-1 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-2 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY vsm-2 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-3 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY vsm-3 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-4 PRIMARY VSB POWERED ON Nexus1010-PRIMARY vsm-4 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-5 PRIMARY VSB POWERED OFF Nexus1010-PRIMARY vsm-5 SECONDARY VSB POWERED OFF Nexus1010-SECONDARY switch(config-vsb-config)#
Step 5	One of the following: •no virtual-service-blade name •no enable [primary \| secondary] Example: switch(config-vsb-config)# no virtual-service-blade vsm-5 switch(config-vsb-config)# Example: switch(config-vsb-config)# no enable switch(config-vsb-config)#	Deletes the specified virtual service blade. •no virtual-service-blade: Removes the virtual service blade in its entirety from the Cisco Nexus 1010. •no enable: Removes the specified virtual service blade from the system but retains the infrastructure configuration (interface VLANs, RAM size, disk size overrides) in Cisco Nexus 1010. Use this command to delete only one virtual service blade in a pair (primary or secondary).
Step 6	show virtual-service-blade summary	Displays a summary of services for verification of the removal.
	Example: (no virtual-service-blade) switch(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- vsm-1 PRIMARY VSB POWERED ON Nexus1010-PRIMARY vsm-1 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-2 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY vsm-2 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-3 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY vsm-3 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-4 PRIMARY VSB POWERED ON Nexus1010-PRIMARY vsm-4 SECONDARY VSB POWERED ON Nexus1010-SECONDARY switch(config-vsb-config)# Example: (no enable) switch(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- vsm-1 PRIMARY VSB POWERED ON Nexus1010-PRIMARY vsm-1 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-2 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY vsm-2 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-3 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY vsm-3 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-4 PRIMARY VSB POWERED ON Nexus1010-PRIMARY vsm-4 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-5 PRIMARY VSB POWERED OFF Nexus1010-PRIMARY vsm-5 SECONDARY VSB POWERED OFF Nexus1010-SECONDARY switch(config-vsb-config)#
Step 7	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.

Modifying a Virtual Service Blade

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

Modifying a Virtual Service Blade on the Cisco Nexus 1010

Use this procedure to modify the control VLAN, packet VLAN, or the RAM size of a virtual service blade.

BEFORE YOU BEGIN

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.

Caution The VSM must be in the shut state before modifying the control VLAN to preserve high availability when the service comes back. The control VLAN passes control messages to the standby VSM.

•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.

Caution Do not modify the management VLAN. If you change the management VLAN, the change is applied to both the Cisco Nexus 1010 and all of the Cisco Nexus 1000V VSMs. The Cisco Nexus 1010 and its hosted Cisco Nexus 1000V VSMs share the same management VLAN. Unlike the control and packet VLANs which are set when a virtual service blade is created, the management VLAN is inherited.

SUMMARY STEPS

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

7. no shutdown

8. show virtual-service-blade name name

9. copy running-config startup-config

DETAILED STEPS


	Command	Purpose
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: switch(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- vsm-1 PRIMARY VSB POWERED ON Nexus1010-PRIMARY vsm-1 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-2 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY vsm-2 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-3 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY vsm-3 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-4 PRIMARY VSB POWERED ON Nexus1010-PRIMARY vsm-4 SECONDARY VSB POWERED ON Nexus1010-SECONDARY vsm-5 PRIMARY VSB POWERED OFF Nexus1010-PRIMARY vsm-5 SECONDARY VSB POWERED OFF Nexus1010-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-5 virtual-service-blade vsm-5 Description: Slot id: 1 SW version: 4.2(1)SV1(4) Host Name: vsm-5 Management IP: 10.78.108.40 VSB Type Name : VSM-1.1 Interface: control vlan: 1116 Interface: management vlan: 1032 Interface: packet vlan: 1117 Interface: internal vlan: NA Ramsize: 1024 Disksize: 3 Heartbeat: 1156 HA Admin role: Primary HA Oper role: STANDBY Status: VB POWERED ON Location: PRIMARY HA Admin role: Secondary HA Oper role: ACTIVE Status: VB POWERED ON Location: SECONDARY VB Info: Domain ID : 1054 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.

Modifying a VSM on the Cisco Nexus 1000V

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 YOU BEGIN

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.

SUMMARY STEPS

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. $

12. close

DETAILED STEPS


	Command	Purpose
Step 1	login virtual-service-blade vb6	Logs you into the Cisco Nexus 1000V CLI for the VSM you are modifying.
Step 2	login	Authenticates your user ID.
Step 3	password	Authenticates your password.
	Example: N1010-1# login virtual-service-blade 1 Telnet escape character is '^\'. Trying 192.168.0.18... Connected to 192.168.0.18. Escape character is '^\'. User Access Verification n1010-vsm1 login: password:
Step 4	show svs domain n1000v# show svs domain SVS domain config: Domain id: 100 Control vlan: 1114 Packet vlan: 1115 L2/L3 Control mode: L2 L3 control interface: NA Status: Config push to VC successful. n1000v#	Displays the domain configuration for the VSM.
Step 5	config t Example: n1000v# config t n1000v(config)#	Places you in the CLI Global Configuration mode.
Step 6	svs-domain Example: n1000v(config)# svs domain n1000v(config-svs-domain)#	Places you into SVS Domain Configuration mode.
Step 7	control vlan vlanid Example: n1000v(config-svs-domain)# control vlan 1116 n1000v(config-svs-domain)#	Modifies the VLAN ID of the VSM domain control VLAN.
Step 8	packet vlan vlanid Example: n1000v(config-svs-domain)# packet vlan 1117 n1000v(config-svs-domain)#	Modifies the VLAN ID of the VSM domain packet VLAN.
Step 9	show svs domain Example: n1000v(config-svs-domain)# show svs domain SVS domain config: Domain id: 100 Control vlan: 1116 Packet vlan: 1117 L2/L3 Aipc mode: L2 L2/L3 Aipc interface: mgmt0 Status: Config push to VC successful. n1000v(config-svs-domain)#	Displays the domain configuration for verification of the changes.
Step 10	copy running-config startup-config Example: n1000v(config-svs-domain)# copy running-config startup-config n1000v(config-svs-domain)#	Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.
Step 11	$ Example: n1000v(config-svs-domain)# $ Telnet>	Exits from the SVS Domain Configuration mode and returns you to a Telnet prompt.
Step 12	close Example: Telnet> close switch#	Closes the Telnet session and returns you to EXEC mode on the Cisco Nexus 1010.
Step 13	You have completed this procedure.

Verifying the Virtual Service Blade Configuration

To verify the virtual service blade configuration, use the following commands:


Command	Purpose
show virtual-service-blade [name name]	Displays the configuration for a specific virtual service blade. See Example 5-1
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 5-2
show virtual-service-blade-type summary	Displays a summary of all virtual service blade configurations by type, such as VSM or NAM. See Example 5-3
show network-uplink type	Displays the uplink configuration for verification. See Example 5-3

Example 5-1 Virtual Service Blade

This example shows how to display the configuration for a specific virtual service blade:

switch# show virtual-service-blade name vsm-5

virtual-service-blade vsm-5

Description:

Slot id: 1

SW version: 4.0(4)SV1(3)

Host Name: vsm-5

Management IP: 10.78.108.40

VSB Type Name : VSM-1.1

Interface: control vlan: 1116

Interface: management vlan: 1032

Interface: packet vlan: 1117

Interface: internal vlan: NA

Ramsize: 1024

Disksize: 3

Heartbeat: 1156

HA Admin role: Primary

HA Oper role: STANDBY

Status: VB POWERED ON

Location: PRIMARY

HA Admin role: Secondary

HA Oper role: ACTIVE

Status: VB POWERED ON

Location: SECONDARY

VB Info:

Domain ID : 1054

switch#

Example 5-2 Virtual Service Blade Summary

This example shows how to display a summary of all virtual service blade configurations:

switch# show virtual-service-blade summary

-------------------------------------------------------------------------------

Name Role State Nexus1010-Module

-------------------------------------------------------------------------------

vsm-1 PRIMARY VSB POWERED ON Nexus1010-PRIMARY

vsm-1 SECONDARY VSB POWERED ON Nexus1010-SECONDARY

vsm-2 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY

vsm-2 SECONDARY VSB POWERED ON Nexus1010-SECONDARY

vsm-3 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY

vsm-3 SECONDARY VSB POWERED ON Nexus1010-SECONDARY

vsm-4 PRIMARY VSB POWERED ON Nexus1010-PRIMARY

vsm-4 SECONDARY VSB POWERED ON Nexus1010-SECONDARY

vsm-5 PRIMARY VSB POWERED OFF Nexus1010-PRIMARY

vsm-5 SECONDARY VSB POWERED OFF Nexus1010-SECONDARY

switch#

Example 5-3 Virtual Service Blade Type

This example shows how to display a summary of all virtual service blade configurations by type, such as VSM or NAM:

switch# show virtual-service-blade-type summary

-------------------------------------------------------------------------------

Virtual-Service-Blade-Type    Virtual-Service-Blade

-------------------------------------------------------------------------------

VSM_SV1_3                     vsm-1

                              vsm-2

NAM-MV                        nam-1

Example 5-4 Network Uplink Type

This example shows how to display the uplink configuration:

switch# show network uplink type

Administrative topology id: 2

Operational topology id: 1

switch#

Additional References

For additional information related to implementing system-level HA features, see the following sections:

•Related Documents

•Standards

•MIBs

•RFCs

Related Topic	Document Title
Cisco Nexus 1010 software setup configuration	Setting Up the Management Software
Cisco Nexus 1010 virtual service blade configuration	Configuring Virtual Service Blades
Cisco Nexus 1010 commands	Cisco Nexus 1010 Command Reference, Release 4.2(1)SP1(2)
Cisco Nexus 1000V commands	Cisco Nexus 1000V Command Reference, Release 4.2(1)SV1(4)
Configuring the Cisco Nexus 1000V domain	Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(4)
Installing and upgrading the Cisco Nexus 1010 software	Cisco Nexus 1010 Software Installation and Upgrade Guide, Release 4.2(1)SP1(2)

Standards


Standards	Title
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.	—

MIBs


MIBs	MIBs Link
•CISCO-PROCESS-MIB	To locate and download MIBs, go to the following URL: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

RFCs


RFCs	Title
No RFCs are supported by this feature	—

Feature History for Virtual Service Blade

This section provides the virtual service blade blade release history.


Feature Name	Releases	Feature Information
Escape sequence	4.2(1)SP1(2)	Escape sequence changed from $ to ^\.
Virtual Service Blade	4.0(4)SP1(1)	This feature was introduced.

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)