Se n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
Cisco Nexus 1010 Management Software
Release Notes, Release 4.0(4) SP1(1)
Updated: July 17, 2013
OL-22484-01
This document describes the features, limitations, and caveats for the Cisco Nexus 1010 management
software. Use this document in combination with documents listed in the “Available Documents” section
on page 10.
Contents
This document includes the following information about the Cisco Nexus 1010 management software.
•
Software Features, page 1
•
Software Compatibility, page 2
•
Limitations and Restrictions, page 3
•
Caveats, page 10
•
Available Documents, page 10
•
Obtaining Documentation and Submitting a Service Request, page 11
Software Features
This section describes the following new software features:
•
Management Software, page 2
•
Virtual Supervisor Module, page 2
•
Network Analysis Module, page 2
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Software Compatibility
Se n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
Management Software
The Cisco Nexus 1010 management software controls the virtual services and blades running on the
Cisco Nexus 1010 Virtual Services Appliance. These include up to four Cisco Nexus 1000V VSMs and
a Cisco Network Analysis Module (NAM).
Cisco Nexus 1010 software is pre installed as an ISO image that includes the following components:
•
Cisco Nexus 1010 kickstart image
This is the Cisco Nexus 1010 Management Software.
•
Hypervisor (KVM Linux) with a Cisco Nexus 1010 agent
Virtual Supervisor Module
The Cisco Nexus 1010 Management Software can manage up to four virtual supervisor modules
(VSMs), each controlling a group of virtual Ethernet modules (VEMs). If you are using Layer 3 Control,
the VEMs can also be in different Layer 3 domains. From a network management perspective. a VSM
and the VEMs it controls 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 VSMs on the Cisco Nexus 1010 with the Cisco Nexus 1000V software image.
The current version is bundled as an ISO image and included in the Cisco Nexus 1010 repository folder
in the bootflash directory.
For more information about creating virtual services, see the Cisco Nexus 1010 Software Configuration
Guide, Release 4.0(4)SP1(1).
Network Analysis Module
You can create a network analysis module (NAM) on the Cisco Nexus 1010 with the NAM ISO image
included in the Cisco Nexus 1010 repository folder in the bootflash directory.
To create a NAM virtual service see the Cisco Nexus 1010 Software Configuration Guide, Release
4.0(4)SP1(1).
For more information about Cisco NAM, see the Cisco Network Analysis Module Software
Documentation Guide, 4.2.
Software Compatibility
The Cisco Nexus 1010 management software is compatible with the following minimum software
versions:
•
Cisco Nexus 1000V Release 4.0(4)SV1(3)
•
Cisco Network Analysis Module Release 4.2.1
•
VMware vSphere 4 Enterprise+
The Cisco Nexus 1010 management software works with all Ethernet switches and all VMware
compatible servers.
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4) SP1(1)
2
OL-22484-01
Limitations and Restrictions
S e n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
Limitations and Restrictions
•
Configuration Limits, page 3
•
Domain ID and HA Role Cannot Be Changed, page 3
•
Boot Variables Cannot Be Manually Configured, page 3
•
Changing the Control or Mgmt VLAN Requires a Reload, page 3
•
HA Failure If Description is Added When Creating VSB, page 4
•
Connecting Uplinks for High Availability, page 10
Configuration Limits
Use the following configuration limits for the Cisco Nexus 1010 management software:
Component
Supported Limit
VSM
4 Cisco Nexus 1000V VSM (2 GB RAM each) 1
NAM
1 Cisco Network Analysis Module (2 GB RAM) 1
Hosts
(ESX or ESXi)
256
(4 VSMs with up to 64 hosts each)
Data Center per Cisco Nexus 1010 HA pair
1
RAM
Per VSB
Per Appliance
12 GB
400+ GB
1. Limited by available RAM on the Cisco Nexus 1010.
Domain ID and HA Role Cannot Be Changed
The configured domain ID and HA role (standalone, primary, or secondary) can never be changed. To
change the domain ID or the HA role, you must reinstall the software.
Boot Variables Cannot Be Manually Configured
The boot variables cannot be configured manually. To change the boot variables, you must enter the
install nexus1010 command. This command installs the software from the bootflash:/repository
directory and updates the boot variables with the name of the software image.
Changing the Control or Mgmt VLAN Requires a Reload
If you change the control or management VLAN, you must reload the software before the change takes
effect.
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4) SP1(1)
OL-22484-01
3
Limitations and Restrictions
Se n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
HA Failure If Description is Added When Creating VSB
If you add a description when creating a pair of HA virtual service blades, then the standby VSB cannot
synchronize with the active. The following error appears on the standby console, and its state remains
VSB NOT PRESENT:
%CPPA_MGR-5-REMOTE_VB_IMG_FAILURE: Could not verify image in standby for virtual service
blade 2 creation: image check operation timed out
To correct an HA failure that results from adding a description, remove and reinstall the HA pair using
the following procedures.
•
Deleting a Virtual Service Blade, page 4
•
Creating a Virtual Service Blade, page 6
Deleting a Virtual Service Blade
Use this procedure to delete a virtual service blade entirely from the Cisco Nexus 1010 after a
configuration failure when adding a description.
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.
1.
config t
2.
virtual-service-blade name
3.
shutdown
4.
show virtual-service-blade summary
5.
no virtual-service-blade name
6.
show virtual-service-blade summary
7.
copy running-config startup-config
SUMMARY STEPS
DETAILED STEPS
Step 1
Command
Purpose
config t
Enters global configuration mode.
Example:
switch# config t
switch(config)#
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4) SP1(1)
4
OL-22484-01
Limitations and Restrictions
S e n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
Step 2
Command
Purpose
virtual-service-blade name
Enters configuration mode for the named virtual service blade.
Example:
switch(config)#
virtual-service-blade vsm-5
switch(config-vsb-config)#
Step 3
shutdown
Shuts down the virtual service blade.
Example:
switch(config-vsb-config)#
shutdown
switch(config-vsb-config)#
Step 4
show virtual-service-blade
Displays a summary of services for verification of the shutdown.
summary
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
no virtual-service-blade name
Removes the virtual service blade entirely from the Cisco Nexus
1010.
Example:
switch(config-vsb-config)# no
virtual-service-blade vsm-5
switch(config-vsb-config)#
Step 6
show virtual-service-blade
Displays a summary of services for verification of the removal.
summary
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
switch(config-vsb-config)#
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4) SP1(1)
OL-22484-01
5
Limitations and Restrictions
Se n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
Step 7
Command
Purpose
copy running-config
startup-config
Saves the running configuration persistently through reboots and
restarts by copying it to the startup configuration.
Example:
switch(config)# copy
running-config startup-config
Creating a Virtual Service Blade
Use this procedure to create a virtual service blade after a configuration failure when adding a
description.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
Caution
HA Failure
Adding a description when creating the VSB causes a failure in forming a redundant pair. Do not use the
description or no description commands.
•
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, you know the filename.
– 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.
1.
config t
2.
virtual-service-blade name
SUMMARY STEPS
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4) SP1(1)
6
OL-22484-01
Limitations and Restrictions
S e n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
3.
show vsb-type summary
4.
virtual-service-blade-type [name name | new iso file name]
5.
show virtual-service-blade name name
6.
interface name vlan vlanid
7.
enable [primary | secondary]
8.
show virtual-service-blade name name
9.
copy running-config startup-config
DETAILED STEPS
Step 8
Command
Purpose
config t
Enters global configuration mode.
Example:
switch# config t
switch(config)#
Step 9
virtual-service-blade name
Creates the named virtual service blade and enters
configuration mode for that service.
Example:
switch(config)# virtual-service-blade
vsm-1
switch(config-vsb-config)#
Step 10
show virtual-service-blade-type summary
Example:
switch(config-vsb-config)#
name: an alphanumeric string of up to 80 characters
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.
show virtual-service-blade-type summary
------------------------------------------------------------------------------Virtual-Service-Blade-Type
Virtual-Service-Blade
-------------------------------------------------------------------------------
Step 11
VSM_SV1_3
vsm-1
vsm-2
NAM-MV
switch(config-vsb-config)#
nam-1
virtual-service-blade-type [name name |
new iso file name]
Example:
switch(config-vsb-config)#
virtual-service-blade-type new
nexus-1010.4.0.4.SV1.3.51.iso
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 10 command output.
•
new: the name of the new ISO software image file
in bootflash repository folder.
Example:
switch(config-vsb-config)#
virtual-service-blade-type name vsm-3
switch(config-vsb-config)#
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4) SP1(1)
OL-22484-01
7
Limitations and Restrictions
Se n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
Command
Step 12
show virtual-service-blade name name
Example:
switch(config-vsb-config)# 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
VB Type Name : VSM_SV1_3
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 13
interface name vlan vlanid
Example:
switch(config-vsb-config)# interface
control vlan 1044
switch(config-vsb-config)#
Purpose
Displays the virtual service blade you have just created
including the interface names that you configure in the
next step.
Applies the interface and VLAN ID to this virtual
service blade. Use the interface names from Step 12
command output.
Note
ERROR: Interface name not found in the
Example:
switch(config-vsb-config)# interface
packet vlan 1045
switch(config-vsb-config)#
Step 14
If you attempt to apply an interface that is not
present, the following error is displayed:
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.
Repeat Step 13 to apply additional interfaces.
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4) SP1(1)
8
OL-22484-01
Limitations and Restrictions
S e n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
Step 15
Command
Purpose
enable [primary | secondary]
Initiates the configuration of the virtual service blade
and then enables it.
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)#
Step 16
Step 17
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
show virtual-service-blade name
Displays the new virtual service blade for verification.
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
VB Type Name : VSM_SV1_3
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)#
While the switch is configuring the virtual service
blade, the switch output for this command progresses
from in progress to powered on.
copy running-config startup-config
Saves the running configuration persistently through
reboots and restarts by copying it to the startup
configuration.
Example:
switch(config-vsb-config)# copy
running-config startup-config
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4) SP1(1)
OL-22484-01
9
Caveats
Se n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
Connecting Uplinks for High Availability
In order to achieve high availability and redundancy with your Cisco Nexus 1010 virtual services
appliance, you must connect the ports from both your active appliance and your standby appliance to an
upstream switch. If you only connect the ports from one of the appliances, then your Cisco Nexus 1010
is operational, but does not have redundancy. For example, if your topology requires ports 1 and 2 to be
connected to the upstream switch, then you must connect ports 1 and 2 from the active appliance, and
and then connect ports 1 and 2 from the standby appliance, to the upstream switch. Use the guidelines
in the Cisco Nexus 1010 Virtual Services Appliance Installation Guide for choosing a topology and
connecting ports to the upstream switch.
Caveats
The following are descriptions of the caveats in Cisco Nexus 1010 Release 4.0(4)SP1(1). The Bug ID
will link you into the Cisco Bug Toolkit.
Bug ID
Caveat Headline
CSCti40301
A Cisco Nexus 1010 standby VSB is not provisioned if you add a description when creating a pair of
HA virtual service blades.
For more information, see HA Failure If Description is Added When Creating VSB, page 4.
CSCte96836
VSB type name is not seen for the standby CPPA manager in show virt name vsb command output.
CSCtf36866
KVM console to show state when Enter pressed
CSCte90627
Incorrect management IP (iPV6) address shown in show virtual-service-blade command output.
CSCti71155
The svs mode L3 command is not supported on the Cisco Nexus 1010.
Available Documents
This section lists the documents used with the Cisco Nexus 1000V and Cisco Nexus 1010 and available
on Cisco.com at the following urls:
http://www.cisco.com/en/US/products/ps9902/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/ps12752/tsd_products_support_series_home.html
General Information
Cisco Nexus 1000V Documentation Roadmap, Release 4.0(4) SV1(3)
Cisco Nexus 1000V Release Notes, Release 4.0(4)SV1(3)
Cisco Nexus 1000V Compatibility Information, Release 4.0(4)SV1(3)
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4)SP1(1)
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4) SP1(1)
10
OL-22484-01
Caveats
S e n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
Install and Upgrade
Cisco Nexus 1000V Software Installation Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1000V Software Upgrade Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1000V VEM Software Installation and Upgrade Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1010 Virtual Services Appliance Hardware Installation Guide
Configuration Guides
Cisco Nexus 1000V License Configuration Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1000V Getting Started Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1000V High Availability and Redundancy Configuration Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1000V Interface Configuration Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1000V Quality of Service Configuration Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1000V Security Configuration Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1000V System Management Configuration Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1010 Software Configuration Guide, Release 4.0(4)SP1(1)
Programming Guide
Cisco Nexus 1000V XML API User Guide, Release 4.0(4)SV1(3)
Reference Guides
Cisco Nexus 1000V Command Reference, Release 4.0(4)SV1(3)
Cisco Nexus 1000V MIB Quick Reference
Cisco Nexus 1010 Command Reference, Release 4.0(4)SP1(1)
Troubleshooting and Alerts
Cisco Nexus 1000V Troubleshooting Guide, Release 4.0(4)SV1(3)
Cisco Nexus 1000V Password Recovery Guide
Cisco NX-OS System Messages Reference
Network Analysis Module Documentation
Cisco Network Analysis Module Software Documentation Guide, 4.2
Cisco Nexus 1000V NAM Virtual Service Blade Installation and Configuration Guide
Network Analysis Module Command Reference Guide, 4.2
User Guide for the Cisco Network Analysis Module Virtual Service Blades, 4.2
Cisco Network Analysis Module Software Release Notes, 4.2
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4) SP1(1)
OL-22484-01
11
Caveats
Se n d d o c u m e n t c o m m e n t s t o n ex u s 1 k - d o c f e e d b a ck @ c i s c o . c o m .
This document is to be used in conjunction with the documents listed in the “Available Documents” section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of
Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The
use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Internet Protocol (IP) addresses and phone numbers that are used in the examples, command display output, and figures within this document are for
illustration only. If an actual IP address or phone number appears in this document, it is coincidental.
© 2010 Cisco Systems, Inc. All rights reserved.
Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4) SP1(1)
12
OL-22484-01