Feedback
Table Of Contents
Cisco Nexus Virtual Services Appliance Software Installation
Information About Software Install
Verifying the CIMC Software Version
Gathering Information About the Management Software
Setting up the Primary Cisco Nexus Virtual Services Appliance
Setting up the Secondary Cisco Nexus Virtual Services Appliance
Example for Network Uplink Configuration
Verifying the Cisco Nexus Virtual Services Appliance Configuration
Getting Started With Cisco Nexus Virtual Services Appliance
Feature History for Software Installation
Cisco Nexus Virtual Services Appliance Software Installation
This chapter describes how to install the Cisco Nexus Virtual Services Appliance software, and includes the following sections:
•
Information About Software Install
•
•
•
•
•
•
•
Note
For an overview of the Cisco Nexus Virtual Services Appliance product family and procedures for configuring the software after it is installed, see the Cisco Nexus Virtual Services Appliance Software Configuration Guide, Release 4.2(1)SP1(5.1).
Information About Software Install
Cisco Nexus Virtual Services Appliance software is pre installed as an ISO image. Use this procedure to install the Cisco Nexus Virtual Services Appliance software. The installation involves the following steps:
Step 1
Step 2
Step 3
Step 4
Prerequisites
Before installing Cisco Nexus Virtual Services Appliance Release 4.2(1)SP1(5.1a), you must know or do the following:
•
•
•
The install fails if an earlier version of CIMC is installed.
•
Guidelines and Limitations
Follow these guidelines and limitations when setting up the Cisco Nexus Virtual Services Appliance product family:
•
•
•
•
•
•
•
•
CIMC And BIOS Information
Use the following guidelines for installing the latest software version of CIMC and for updating the CIMC and BIOS firmware.
•
•
The upgrade or install fails if an earlier version of CIMC is installed.
•
–
–
–
–
–
–
–
–
•
For more information on the Cisco UCS Host Upgrade Utility tool documentation, see
http://www.cisco.com/en/US/partner/products/ps10493/products_user_guide_list.html
•
–
–
•
Verifying the CIMC Software Version
Use this procedure to verify the CIMC software version installed on your Cisco Nexus Virtual Services Appliance.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
•
•
•
Step 1
•
Look in the Switch Hardware ID information for the PID.•
Example:switch# show hardwareunsetSoftwareloader: version unsetkickstart: version unsetsystem: version unsetkickstart image file is: unsetkickstart compile time: unset [unset]system image file is: unsetsystem compile time: unset [unset]Hardwarecisco unset ("unset")unset with unset unset of memory.Processor Board ID unsetDevice name: unsetbootflash: unset kBDisk Storage capacity for VM virtual disks: 345945 MBNumber of physical 1Gbps ethernet ports: 6Number of CPU Cores: 16CPU Cores details:model name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzKernel uptime is unset day(s), unset hour(s), unset minute(s), unset second(s)pluginCore Plugin, Ethernet Plugin, Virtualization Plugin--------------------------------Switch hardware ID information--------------------------------Switch is booted upSwitch type is : Nexus 1110-S (Virtual Services Appliance) 2 slot ChassisModel number is Nexus 1110-SPID-VID-SN: N1K-C1110-S-2.0-1846886525134693056--------------------------------Chassis has 2 Module slots--------------------------------Module1 okModule type is : Cisco Virtual Services Appliance0 submodules are presentModel number is Nexus 1110-SH/W version is 2.0UUID is 0F823778-D54A-4970-E999-2077C67F0133Manufacture date is 02/22/2012Serial number isModule2 okModule type is : Cisco Virtual Services Appliance0 submodules are presentModel number is Nexus 1110-SH/W version is 2.0UUID is 68143FE5-207B-4989-F297-0937998C9424Manufacture date is 02/22/2012Serial number is QCI1410A4LPFigure 2-1 CIMC Window with Product ID (PID)
Step 2
•
•
Gathering Information About the Management Software
Before you begin the installation, you will need the following information for your Cisco Nexus Virtual Services Appliance:
Administrator Credentials
When you set up the system software, you are required to create an administrator password. Table 2-1 lists password strength guidelines:
HA Redundancy Role
The Cisco Nexus Virtual Services Appliance product family is provided in redundant pairs for high availability. When setting up the device, you configure a high availability role—primary or secondary. Table 2-2 describes these roles.
Note
HA Redundancy States
Table 2-3 describes the HA redundancy states.
Domain ID
The primary and secondary Cisco Nexus Virtual Services Appliances use the domain ID to identify each other. The Cisco Nexus Virtual Services Appliances must be in the same switching domain, and share the same management IP address.
Network Uplinks
Cisco Nexus Virtual Services Appliance product family supports two types of network uplink configurations to connect to the network.
•
•
As a result you can connect your system to the network using one of the following five supported uplink types.
•
•
•
•
•
Note
See the Cisco Nexus Virtual Services Appliance Software Configuration Guide, Release 4.2(1)SP1(5.1) for more information about network uplink types.
During the installation of Cisco Nexus Virtual Services Appliance product family you can setup the flexible network uplink type or the static network uplink type. If you modify the uplink type, a reload is required each time the uplink type is modified for it to take effect.
See the Cisco Nexus Virtual Services Appliance Software Configuration Guide, Release 4.2(1)SP1(5.1) for information about migrating the network uplink types.
Table 2-4 Table 2-4 shows the four supported network uplink types and the ports that carry each type of VLAN traffic.
VLANs
Control, and management VLANs are used by the Cisco Nexus Virtual Services Appliance product family for management and communication with its virtual service blades. These VLANs are added as a part of the initial setup of the management software. Control and packet VLANs are also added to each virtual service blade when it is created. The management VLAN is inherited from the Cisco Nexus Virtual Services Appliance product family by each virtual service blade.
If you modify a control, packet, or management VLAN on the Cisco Nexus Virtual Services Appliance product family, the change is effective immediately. A reload is required to effect the change of control and management VLAN on Cisco Nexus Virtual Services Appliance. However, for service continuity, you must configure the same control and packet VLANs on the hosted VSMs. Otherwise the Cisco Nexus Virtual Services Appliance loses communication with its VSMs.
This section includes the following additional topics:
Management VLAN
The management VLAN is the VLAN that forwards traffic for the management port of the Cisco Nexus Virtual Services Appliance. If your virtual service blade uses the management class of traffic, it inherits the management VLAN from the Cisco Nexus Virtual Services Appliance.
The management VLAN is used by the outside world to reach the Cisco Nexus Virtual Services Appliance management 0 interface.
The Cisco Nexus Virtual Services Appliance 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 Virtual Services Appliance, if you change management VLAN for Cisco Nexus Virtual Services Appliance, then the change is applied to both the Cisco Nexus Virtual Services Appliance 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 Virtual Services Appliance host.
Control VLAN
The control VLAN is a Layer 2 interface used for communication between the redundant Cisco Nexus Virtual Services Appliances. This interface handles low-level control packets such as heartbeats as well as any configuration data that needs to be exchanged between the Cisco Nexus Virtual Services Appliances.
Setting up the Primary Cisco Nexus Virtual Services Appliance
You can use this procedure to set up the management software for the following:
•
It is a recommended Cisco best practice to configure a primary Cisco Nexus Virtual Services Appliance with a secondary backup. Although you can configure a primary Cisco Nexus Virtual Services Appliance without a secondary backup, this configuration in a production environment is not supported.
BEFORE YOU BEGIN
•
–
–
If you do not specify an HA role, then the role is configured as primary.–
–
–
–
–
This is the IP address of the management interface that appears as the mgmt0 port on the appliance.–
–
DETAILED STEPS
Step 1
The setup wizard starts automatically.
•
Example:telnet 172.25.182.99 2005Trying 172.25.182.99...Connected to 172.25.182.99.Escape character is '^]'switch#---- System Admin Account Setup ---- Enter the password for "admin":Confirm the password for"admin":•
Example:ssh admin@172.25.182.230admin@172.25.182.230's password:switch# connect hostCISCO Serial Over LAN:Close Network Connection to Exit---- System Admin Account Setup ---- Enter the password for "admin":Confirm the password for"admin":Step 2
Example:
---- System Admin Account Setup ---- Enter the password for "admin":Confirm the password for"admin":Step 3
Example:
---- System Admin Account Setup ---- Enter the password for "admin":primary
Note
Step 4
Note
Example:Enter network-uplink type <1-5>:1. Ports 1-2 carry all management, control and data vlans2. Ports 1-2 management and control, ports 3-6 data3. Ports 1-2 management, ports 3-6 control and data4. Ports 1-2 management, ports 3-4 control, ports 5-6 data5. Flexible5Step 5
Example:
Enter control vlan <1-3967, 4048-4093>: 347Step 6
Example:
Enter control uplink <1-6>: 1Step 7
Example:
Enter the domain id<1-4095>: 3477Step 8
Example:
Enter management vlan<1-3967,4048-4093>: 180Step 9
Example:
Enter management uplink <1-6>: 2Step 10
The new configuration is saved into nonvolatile storage, after which the running and the startup copies of the configuration are identical.
Saving boot configuration. Please wait...[########################################] 100%System is going to reboot to configure network uplinksAfter reboot, the default static or flexible topology will be configured. See Figure 2-2 for default flexible network uplink configuration. For more information, see the Cisco Nexus Virtual Services Appliance Software Configuration Guide, Release 4.2(1)SP1(5.1).
Figure 2-2
Default Flexible Network Uplink Configuration without vPC /VSS
Figure 2-3
Default Flexible Network Uplink Configuration with vPC /VSS
Step 11
Example:Would you like to enter the basic configuration dialog (yes/no): yes---- Basic System Configuration Dialog ----This setup utility will guide you through the basic configuration ofthe system. Setup configures only enough connectivity for managementof the system.*Note: setup is mainly used for configuring the system initially,when no configuration is present. So setup always assumes systemdefaults and not the current system configuration values.Press Enter at anytime to skip a dialog. Use ctrl-c at anytimeto skip the remaining dialogs.Step 12
Example:
Create another login account (yes/no) [n]:noStep 13
Example:
Configure read-only SNMP community string (yes/no) [n]:noStep 14
Example:Configure read-write SNMP community string (yes/no) [n]:Step 15
Example:Enter the VSA name [Nexus1110]:Step 16
This is the IP address of the management interface that appears as the mgmt0 port on the appliance.
Example:Continue with Out-of-band (mgmt0) management configuration? [yes/no] [y]:yes Mgmt0 IP address type V4/V6? (V4): V6Mgmt0 IPv6 address: 1:a:0::2Mgmt0 IPv6 netmask prefix (1-128): 64Step 17
Example:Configure the default-gateway: (yes/no) [y]:yes IPv6 address of the default gateway: 1:a:0::1Step 18
Example:Configure Advanced IP options (yes/no)? [n]:noStep 19
Example:Enable the telnet service? (yes/no) [y]:yesStep 20
Example:Enable the ssh service? (yes/no) [y]:yes Type of ssh key you would like to generate (dsa/rsa) : rsa Number of key bits <768-2048> : 1024Step 21
The configuration is summarized.
Example:Configure NTP server? (yes/no) [n]:noThe following configuration will be applied:Switchname n1010interface Mgmt0ip address 172.28.15.152 255.255.255.0no shutdowntelnet server enablessh key rsa 1024 forcessh server enablesvs-domaincontrol vlan 260domain id 152Step 22
•
•
Example:Would you like to edit the configuration? (yes/no) [n]:noStep 23
Caution
Example:Use this configuration and save it? (yes/no) [y]:yes[########################################] 100%The new configuration is saved into nonvolatile storage, after which the running and the startup copies of the configuration are identical.
Note
Step 24
show running configuration
!Command: show running-config!Time: Mon Sep 10 21:31:34 2012version 4.2(1)SP1(5.1)feature telnetusername admin password 5 $1$8oEF.umL$mRRZTm3.sWL2ED5KZydz61 role network-adminbanner motd #Cisco VSA#ip domain-lookupip domain-lookuphostname N1110-Ssnmp-server user admin network-admin auth md5 0xb64ad6879970f0e57600c443287a79f0 priv 0xb64ad6879970f0e57600c443287a79f0 localizedkeysnmp-server community public group network-adminvrf context managementip route 0.0.0.0/0 10.78.109.97vlan 1,1352,1360port-channel load-balance ethernet source-macport-profile default max-ports 32vdc N1110-S id 1limit-resource vlan minimum 16 maximum 2049limit-resource monitor-session minimum 0 maximum 2limit-resource vrf minimum 16 maximum 8192limit-resource port-channel minimum 0 maximum 768limit-resource u4route-mem minimum 32 maximum 32limit-resource u6route-mem minimum 16 maximum 16limit-resource m4route-mem minimum 58 maximum 58limit-resource m6route-mem minimum 8 maximum 8network-uplink type 4interface GigabitEthernet1interface GigabitEthernet2interface GigabitEthernet3interface GigabitEthernet4interface GigabitEthernet5interface GigabitEthernet6interface PortChannel1interface PortChannel2interface PortChannel3virtual-service-blade VSM1virtual-service-blade-type name VSM-1.1interface control vlan 1361interface packet vlan 1362ramsize 2048disksize 3numcpu 1cookie 1555871292no shutdowninterface VsbEthernet1/1interface VsbEthernet1/2interface VsbEthernet1/3virtual-service-blade NAMC-1virtual-service-blade-type name NAM-1.1interface data vlan 1352ramsize 2048disksize 53numcpu 2cookie 753232953no shutdown secondaryinterface VsbEthernet2/1virtual-service-blade DCNM61virtual-service-blade-type name DCNM-VSB-6.1interface eth1 vlan 0ramsize 8192disksize 80numcpu 2cookie 969732378no shutdown primaryinterface VsbEthernet3/1virtual-service-blade VSG12virtual-service-blade-type name VSG-1.2interface data vlan 1365interface ha vlan 1364ramsize 2048disksize 3numcpu 1cookie 2051820775no shutdown primaryno shutdown secondaryinterface VsbEthernet4/1interface VsbEthernet4/2interface VsbEthernet4/3virtual-service-blade VSM-OVAvirtual-service-blade-type name VSM-1.2interface control vlan 1364interface packet vlan 1366ramsize 2048disksize 3numcpu 1cookie 448734513no shutdown primaryno shutdown secondaryinterface VsbEthernet5/1interface VsbEthernet5/2interface VsbEthernet5/3virtual-service-blade VSG-OVAvirtual-service-blade-type name VSG-1.2interface data vlan 1356interface ha vlan 1355ramsize 2048disksize 3numcpu 1cookie 2105102293no shutdowninterface VsbEthernet6/1interface VsbEthernet6/2interface VsbEthernet6/3interface mgmt0ip address 10.78.109.100/28interface control0line consoleboot kickstart bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.5.1.binboot system bootflash:/nexus-1010-mz.4.2.1.SP1.5.1.binboot kickstart bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.5.1.binboot system bootflash:/nexus-1010-mz.4.2.1.SP1.5.1.binsvs-domaindomain id 2222control vlan 1360management vlan 1352svs mode L2
Setting up the Secondary Cisco Nexus Virtual Services Appliance
You can use this procedure to set up the management software for the secondary Cisco Nexus Virtual Services Appliance in a redundant pair.
It is recommended to configure the same domain ID, uplink type, control VLAN, management VLAN, control uplink, management uplink for both primary and secondary Cisco Nexus Virtual Services Appliances.
DETAILED STEPS
Step 1
Example:
"admin":Confirm the password for---- System Admin Account Setup ----
Enter the password for "admin":Step 2
Example:
"admin":secondaryStep 3
Note
Example:Enter network-uplink type <1-5>:1. Ports 1-2 carry all management, control and data vlans2. Ports 1-2 management and control, ports 3-6 data3. Ports 1-2 management, ports 3-6 control and data4. Ports 1-2 management, ports 3-4 control, ports 5-6 data5. Flexible5Step 4
Example:
Enter control vlan <1-3967, 4048-4093>: 347Step 5
Example:
Enter control uplink <1-6>: 1Step 6
Example:
Enter the domain id<1-4095>: 3477Step 7
Example:
Enter management vlan<1-3967,4048-4093>: 180Step 8
Example:
Enter management uplink <1-6>: 2The following things occur on the switch:
•
•
•
Example:Saving boot configuration. Please wait...[########################################] 100%System is going to reboot to configure network uplinksHA mode set to secondary. Rebooting now...Step 9
show running configuration.
Example for Network Uplink Configuration
The following example shows how to configure flexible network uplink configuration during installation:
---- System Admin Account Setup ----Enter the password for "admin":Confirm the password for "admin":Enter HA role[primary/secondary]: secondary_Enter network-uplink type <1-5>:1. Ports 1-2 carry all management, control and data vlans2. Ports 1-2 management and control, ports 3-6 data3. Ports 1-2 management, ports 3-6 control and data4. Ports 1-2 management, ports 3-4 control, ports 5-6 data5. Flexible5_Enter control vlan <1-3967, 4048-4093>: 347Enter control uplink <1-6>: 1_Enter the domain id<1-4095>: 3477_Enter management vlan <1-3967, 4048-4093>: 180Enter management uplink <1-6>: 2_Saving boot configuration. Please wait...[########################################] 100%System is going to reboot to configure network uplinksThe following example shows how to configure static network uplink configuration during installation:
---- System Admin Account Setup ----Enter the password for "admin":Confirm the password for "admin":Enter HA role[primary/secondary]: secondary_Enter network-uplink type <1-5>:1. Ports 1-2 carry all management, control and data vlans2. Ports 1-2 management and control, ports 3-6 data3. Ports 1-2 management, ports 3-6 control and data4. Ports 1-2 management, ports 3-4 control, ports 5-6 data5. Flexible1_Enter control vlan <1-3967, 4048-4093>: 300_Enter the domain id<1-4095>: 300_Enter management vlan <1-3967, 4048-4093>: 233_Saving boot configuration. Please wait...[########################################] 100%System is going to reboot to configure network uplinks
Verifying the Cisco Nexus Virtual Services Appliance Configuration
To verify the Cisco Nexus Virtual Services Appliance configuration, use the following commands:
show running-configuration
Displays the Cisco Nexus Virtual Services Appliance running configuration.
See Example 2-1.
show system redundancy status
Displays the redundancy state (active or standby) and the redundancy role (primary or secondary) for the Cisco Nexus Virtual Services Appliances.
See Example 2-2.
show svs domain
Displays the domain information for the Cisco Nexus Virtual Services Appliance:
See Example 2-3.
show network cdp neighbors
Displays uplink connectivity for the active or standby Cisco Nexus Virtual Services Appliance.
See Example 2-4.
Example 2-1 Setup Configuration
This example shows how to display and verify the Cisco Nexus Virtual Services Appliance setup configuration:
show running-config!Command: show running-config!Time: Mon Sep 10 21:31:34 2012version 4.2(1)SP1(5.1)feature telnetusername admin password 5 $1$8oEF.umL$mRRZTm3.sWL2ED5KZydz61 role network-adminbanner motd #Cisco VSA#ip domain-lookupip domain-lookuphostname N1110-Ssnmp-server user admin network-admin auth md5 0xb64ad6879970f0e57600c443287a79f0 priv 0xb64ad6879970f0e57600c443287a79f0 localizedkeysnmp-server community public group network-adminvrf context managementip route 0.0.0.0/0 10.78.109.97vlan 1,1352,1360port-channel load-balance ethernet source-macport-profile default max-ports 32vdc N1110-S id 1limit-resource vlan minimum 16 maximum 2049limit-resource monitor-session minimum 0 maximum 2limit-resource vrf minimum 16 maximum 8192limit-resource port-channel minimum 0 maximum 768limit-resource u4route-mem minimum 32 maximum 32limit-resource u6route-mem minimum 16 maximum 16limit-resource m4route-mem minimum 58 maximum 58limit-resource m6route-mem minimum 8 maximum 8network-uplink type 4interface GigabitEthernet1interface GigabitEthernet2interface GigabitEthernet3interface GigabitEthernet4interface GigabitEthernet5interface GigabitEthernet6interface PortChannel1interface PortChannel2interface PortChannel3virtual-service-blade VSM1virtual-service-blade-type name VSM-1.1interface control vlan 1361interface packet vlan 1362ramsize 2048disksize 3numcpu 1cookie 1555871292no shutdowninterface VsbEthernet1/1interface VsbEthernet1/2interface VsbEthernet1/3virtual-service-blade NAMC-1virtual-service-blade-type name NAM-1.1interface data vlan 1352ramsize 2048disksize 53numcpu 2cookie 753232953no shutdown secondaryinterface VsbEthernet2/1virtual-service-blade DCNM61virtual-service-blade-type name DCNM-VSB-6.1interface eth1 vlan 0ramsize 8192disksize 80numcpu 2cookie 969732378no shutdown primaryinterface VsbEthernet3/1virtual-service-blade VSG12virtual-service-blade-type name VSG-1.2interface data vlan 1365interface ha vlan 1364ramsize 2048disksize 3numcpu 1cookie 2051820775no shutdown primaryno shutdown secondaryinterface VsbEthernet4/1interface VsbEthernet4/2interface VsbEthernet4/3virtual-service-blade VSM-OVAvirtual-service-blade-type name VSM-1.2interface control vlan 1364interface packet vlan 1366ramsize 2048disksize 3numcpu 1cookie 448734513no shutdown primaryno shutdown secondaryinterface VsbEthernet5/1interface VsbEthernet5/2interface VsbEthernet5/3virtual-service-blade VSG-OVAvirtual-service-blade-type name VSG-1.2interface data vlan 1356interface ha vlan 1355ramsize 2048disksize 3numcpu 1cookie 2105102293no shutdowninterface VsbEthernet6/1interface VsbEthernet6/2interface VsbEthernet6/3interface mgmt0ip address 10.78.109.100/28interface control0line consoleboot kickstart bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.5.1.binboot system bootflash:/nexus-1010-mz.4.2.1.SP1.5.1.binboot kickstart bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.5.1.binboot system bootflash:/nexus-1010-mz.4.2.1.SP1.5.1.binsvs-domaindomain id 2222control vlan 1360management vlan 1352svs mode L2Example 2-2 Redundancy Status
switch# show system redundancy statusRedundancy role---------------administrative: primaryoperational: primaryRedundancy mode---------------administrative: HAoperational: NoneThis supervisor (sup-1)-----------------------Redundancy state: ActiveSupervisor state: ActiveInternal state: Active with no standbyOther supervisor (sup-2)------------------------Redundancy state: Not present---- ----switch#Example 2-3 Domain
switch# show svs domainSVS domain config:Domain id: 3555Control vlan: 305Management vlan: 233L2/L3 Control mode: L2L3 control interface: NAStatus: Config not pushed to VC.switch#Example 2-4 CDP neighbors (standby)
switch# show network cdp neighbors....Device-ID Local Intrfce Hldtme Capability Platform Port IDsfish-cat3k-K5-stack2 eth2 166 R T B S I r cisco WS-C375 GigabitEthernet1/0/23switch#Getting Started With Cisco Nexus Virtual Services Appliance
After you complete the software installation, you can configure the Cisco Nexus Virtual Services Appliance product family. See the Cisco Nexus Virtual Services Appliance Software Configuration Guide, Release 4.2(1)SP1(5.1) for more information
The following are the basic steps in the software configuration process.
Step 1
Step 2
Step 3
•
•
Feature History for Software Installation
This section provides the software installation and upgrade release history.
