Cisco Cisco Nexus 1010 Virtual Services Appliance Leaflet

Page of 6
 
 
© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 
Page 3 of 6 
Q.  Can I just use one Cisco Nexus 1010 or 1010-X? Why do I need two appliances? 
A.  As a best practice, the use of two Cisco Nexus 1010 or 1010-X appliances is recommended. Cisco does not 
support and the products do not allow the primary and secondary VSMs to be installed on the same Cisco 
Nexus 1010 or 1010-X. Having two appliances provides the necessary redundancy for a virtualized production 
environment. Note: Nexus 1010 and 1010-X VSAs cannot be mixed in a high-availability configuration. 
Q.  Can I have one VSM instance using Layer 2 communication and another VSM instance using Layer 3? 
A.  Yes. Each VSM can use whichever method of communication with the VEM is needed. 
Q.  Does the management VLAN for all VSMs on the Cisco Nexus 1010 or 1010-X have to be the same? 
A.  Yes. Every management interface on the VSMs must reside in the same management VLAN as the Cisco 
Nexus 1010 or 1010-X management VLAN. However, Cisco Prime NAM uses only data-class traffic, and its 
VLAN does not have to be same as the Cisco Nexus 1010 management VLAN; the user can choose any 
VLAN that he or she wants for Cisco Prime NAM. 
Q.  Do multiple VSMs on the Cisco Nexus 1010 or 1010-X appliance have to have different domain IDs? 
A.  If the VSMs are in Layer 2 mode and are using the same VLAN for the control or management VLAN, then 
their domain IDs must be unique. As a best practice, the domain IDs should be unique to identify the instances 
correctly, but this is not required if the VSMs are using different control VLANs. If the VSMs are using Layer 3 
communication, then the VSM instances must have unique domain IDs. 
Q.  Can multiple Cisco Nexus 1000V Series instances with unique domain IDs be active for the same VEM? 
A.  No. A VEM can belong to only a single Cisco Nexus 1000V Series instance, whether the Cisco Nexus 1000V 
Series instance is running on the Cisco Nexus 1010 or 1010-X VSA or whether it is a virtual machine on a 
VMware ESX or ESXi server. 
Q.  Can the Cisco Nexus 1000V Series Switch have the same domain ID as the Cisco Nexus 1010 or 1010-X? 
A.  No. The Cisco Nexus 1010 or 1010-X and all the VSMs share same management VLAN. Consequently, 
sharing the same domain ID can cause problems for high availability. 
Q.  How can I view the uplink connectivity on the Cisco Nexus 1010 or 1010-X? 
A.  The Cisco Nexus 1010 or 1010-X uplink supports Cisco Discovery Protocol, so you can use the Show Network 
CDP Neighbors command to see the upstream port connectivity. The Show Network and Show Network 
Summary commands display details about PortChannels and Ethernet ports on the Cisco Nexus 1010 or 
1010-X. 
Q.  How do I migrate a VSM running as a virtual appliance in a VMware ESX or ESXi cluster to the Cisco Nexus 
1010 or 1010-X? 
A.  The procedure can be found in our software configuration guide at the following link: 
Q.  How do I change the switch from primary to secondary or secondary to primary when running the Cisco Nexus 
1010 or 1010-X in high-availability mode? 
A.  Use the Write Erase command to change the roles. All configurations will be lost on the Cisco Nexus 1010 or 
1010-X appliance, and it will come up in the fresh install mode. The system redundancy role 
<primary|secondary> command cannot be used to change the role.