Installing the Cisco Nexus Cloud Services Platform Software

This chapter contains the following sections:

Information About the Software Installation

The Cisco Nexus Cloud Services Platform software is preinstalled as an ISO image.

Prerequisites

Before you install the Cisco Nexus Cloud Services Platform Release 5.2(1)SP1(7.1), you must know or do the following:
  • Have the latest firmware release ready.
  • Ensure that the appropriate version of the CIMC software is installed before installing the Cavium NITROX card. Select a CIMC software version from the following options:
    • Version 1.5(4e) for the Cisco Nexus 1110 product family.
    • Version 1.4(3s) for the Cisco Nexus 1010 product family. To verify that you have the appropriate CIMC version installed, see the Verifying the CIMC Software Version.

    Caution
    We recommend that you upgrade the firmware using the Cisco Host Upgrade Utility (HUU). Failing to do so might result in a network setup failure and/or system reboots. When you use the HUU upgrade menu, choose the option to upgrade the CIMC, BIOS, and all other components of the hardware. For information about the Cisco HUU, see the Cisco Host Upgrade Utility Information.
  • For firmware releases prior to 1.4(3), the Cisco HUU does not support the Cisco Nexus 1010 and Cisco Nexus 1010-X. In such cases, use the Cisco Nexus Virtual Services Appliance CIMC GUI to manually update to CIMC version 1.4(3), and then use the Cisco Host Upgrade Utility to upgrade to firmware 1.5(4e).
  • For firmware release 1.5(4e) or later releases, the Cisco UCS Host Upgrade Utility tool supports the Cisco Nexus Virtual Services Appliance. For more information. see the Cisco Host Upgrade Utility tool documentation.
  • Starting this release, the recommended BIOS settings for process and memory configuration on a Cisco Nexus 1110-X are in the Low Latency Optimized (Turbo ON) mode. See the Recommended BIOS Settings for the Cisco Nexus 1110-X section for the recommended BIOS configuration settings on the Cisco Nexus 1110-X .

Guidelines and Limitations

The Cisco Nexus Cloud Services Platform product family guidelines and limitations are as follows:

  • The domain ID must be unique within the control VLAN.
  • If other Cisco Nexus Cloud Services Platforms or Cisco Nexus 1000Vs are in the same control VLAN, the domain ID must also be unique across all of them.
  • The Cisco Nexus Cloud Services Platform is not supported in the non-HA mode.
  • We recommend that you configure a primary Cisco Nexus Cloud Services Platform with a secondary backup. Although you can configure a primary Cisco Nexus Cloud Services Platform without a secondary backup, this configuration in a production environment is not supported.
  • You must configure the same domain ID, control VLAN, management VLAN, control uplink, and management uplink for both the primary and secondary Cisco Nexus Cloud Services Platforms.
  • The pairing of the Cisco Nexus Cloud Services Platform must match the hardware platform. For example, a Cisco Nexus 1010-X will only pair with another Cisco Nexus 1010-X and a Cisco Nexus 1110-X will only pair with a Cisco Nexus 1110-X. You cannot pair a Cisco Nexus 1010 with a Cisco Nexus 1010-X or pair a Cisco Nexus 1110-S with a Cisco Nexus 1110-X or any other model. Asymmetric pairing is allowed when a Cisco Nexus 1010 is paired with a Cisco Nexus 1110-S, and a Cisco Nexus 1010-X is paired with a Cisco Nexus 1110-X, but in such cases, only the minimum possible configuration will be available.

    Note

    We recommend that you always use symmetric pairing.

  • Release doe not support asymmetric hardware configurations of the 10 Gbps interface, the Cavium NITROX Security processor card, and the 1 Gbps NICs.
  • The 10 Gbps interface is not enabled in the following hardware configurations in this release:
    • Asymmetric pairing of a Cisco Nexus 1010-X and Cisco Nexus 1110-X.
    • When a 10 Gigabit interface is present in one and not on the other, in a high availabiity (HA) pair.

Note
  • If you want to install the Cavium NITROX Security Processor card or switch it with the Cisco UCS VIC 1225 card or the Intel quad port cards, you must do so and power the appliance on before you enable or configure them using the Cisco Nexus Cloud Services Platform software CLI.
  • If you want to use the Cavium NITROX Security processor card on the Cisco Nexus 1110-X, you must have the CIMC software version 1.5(4) installed.

Cisco Host Upgrade Utility Information

The Cisco Host Upgrade Utility (HUU) is a tool that you can use to upgrade the firmware on one or multiple Cisco UCS C-Series servers. The HUU detects the current version of the following components that you have already installed and guides you to upgrade them to the latest version.

  • Cisco Integrated Management Controller (CIMC)
  • System BIOS
  • LAN on Motherboard (LOM)
  • RAID controllers
  • Cisco UCS VIC 1225
  • Network adapters
  • Cavium NITROX CNN3550-C20-NHB-2.0-G security processor card
You can obtain information about the minimum required version of the Cisco HUU and how to download the HUU ISO from the following sources:

You must use the instructions provided in the HUU documentation to upgrade the firmware before you install the current release of the Cisco Nexus Cloud Services Platform.


Caution
You must ensure that you are using the appropriate HUU versions to upgrade your firmware. You cannot use the HUU versions for the Cisco Nexus 1010 and Cisco Nexus 1110 product families interchangeably.

Verifying the CIMC Software Version

You can verify the CIMC software version installed on your Cisco Nexus Cloud Services Platform.

Before You Begin

Before beginning this procedure, you must know or do the following:

  • Log in to the Cisco Nexus Cloud Services Platform from the command-line interface (CLI) or a web browser.
  • If CIMC software 1.4(3s) or later versions is installed, you will see the product ID N1K-C1010 on the Cisco Nexus 1010 or the product ID N1K-C1010X on the Cisco Nexus 1010-X in the output of the show hardware command.
  • If CIMC software version 1.5(4e) or higher is installed, you will see the product ID N1K-1110-S on the Cisco Nexus 1110-S or the product ID N1K-1110-X on the Cisco Nexus 1110-S in the output of the show hardware command.
Procedure
    Step 1   From the Cisco Nexus Cloud Services Platform, do one of the following to display the product ID (PID):

    • From the command-line interface (CLI), enter the show hardware command. In the output, look in the Switch Hardware ID section for the PID.

    • From a web browser, open the Server Summary window and view the server properties. See the following figure for an example.
      Figure 1. CIMC Window with Product ID (PID)



    Step 2   Do one of the following:

    • If the PID displayed is N1K-1110-S on the Cisco Nexus 1110-S, N1K-1110-X on the Cisco Nexus 1110-X, N1K-C1010 on the Cisco Nexus 1010, or N1K-C1010-X on the Cisco Nexus 1010-X, you can proceed with the installation or upgrade to the Cisco Nexus Cloud Services Platform Release 5.2(1)SP1(7.1).

    • If the PIDs displayed are not as mentioned above, do not install or upgrade to Release 5.2(1)SP1(7.1). Instead, you must replace the Cisco Nexus Cloud Services Platform using the RMA process. For more information, see Replacing a Cisco Nexus Cloud Services Platform.

    This example shows the output for show hardware command. You can check the Switch Hardware ID section to verify the PID on the Cisco Nexus Cloud Services Platform. 

    switch# show hardware 
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie
s_home.html
Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.

Software
  kickstart: version 5.2(1)SP1(7.1)
  system:    version 5.2(1)SP1(7.1)
  kickstart image file is: bootflash:///nexus-1010-kickstart.5.2.1.SP1.7.1.bin
  kickstart compile time:  5/15/2014 1:00:00 [05/15/2014 10:02:45]
  system image file is:    bootflash:///nexus-1010.5.2.1.SP1.7.1.bin
  system compile time:     5/15/2014 1:00:00 [05/15/2014 10:13:48]


Hardware
  cisco Nexus 1010 (Virtual Services Appliance) 2 slot Chassis ("Cisco Virtual S
ervices Appliance")
   with 12582912 kB of memory.
  Processor Board ID T023D710B01

  Device name: switch
  bootflash:    3897832 kB
  Disk Storage capacity for VM virtual disks: 336264 MB
  Number of physical 1Gbps ethernet ports: 6
  Number of physical 10Gbps ethernet ports: 0
  Number of SSL accelerator card: 0
  Number of CPU Cores: 12
  CPU Cores details:
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
  model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz


System uptime is 0 days, 13 hours, 43 minutes, 55 seconds

Kernel uptime is 0 day(s), 13 hour(s), 44 minute(s), 56 second(s)


plugin
  Core Plugin, Ethernet Plugin, Virtualization Plugin
--------------------------------
Switch hardware ID information
--------------------------------

Switch is booted up
  Switch type is : Nexus 1010 (Virtual Services Appliance) 2 slot Chassis
  Model number is Nexus 1010
  PID-VID-SN: N1K-C1010-A-7911922711400115374

--------------------------------
Chassis has 2 Module slots
--------------------------------

Module1  ok
  Module type is : Cisco Virtual Services Appliance
  0 submodules are present
  Model number is Nexus 1010
  H/W version is A
  UUID is 03BB2905-E130-DF11-68A1-68EFBDF61D42
  Manufacture date is 12/21/2011
  Serial number is QCI1410A4WG

Module2  ok
  Module type is : Cisco Virtual Services Appliance
  0 submodules are present
  Model number is Nexus 1010
  H/W version is A
  UUID is 21E65B27-5432-DF11-44BB-68EFBDF6192E
  Manufacture date is 08/08/2010
  Serial number is QCI1410A4KV

    Recommended BIOS Settings for the Cisco Nexus 1110-X

    Use the recommended process and memory configuration settings listed in the following table to configure the BIOS settings on the Cisco Nexus 1110-X.

    Process Configuration

    Recommended BIOS Setting in the Low Latency Optimized (Turbo ON) Mode

    Intel Hyper Threading Technology

    Disabled

    Number of Enabled Cores

    All

    CPU Performance

    Custom

    Hardware Prefetcher

    Enabled

    Adjacent Cache Prefetcher

    Enabled

    DCU Streamer Prefetch

    Enabled

    DCU IP Prefetch

    Enabled

    Direct Cache Access

    Enabled

    Power Technology

    Custom

    Enhanced Intel SpeedStep(R) Technology

    Enabled

    Intel(R) Turbo Boost Technology

    Enabled

    Processor Power State C6

    Disabled

    Processor Power State C1 Enhanced

    Disabled

    Frequency Floor Override

    Disabled

    P- STATE Coordination

    HW_ALL

    Energy Performance

    Performance

    Memory Configuration

    Low Latency Optimized Mode (Turbo ON)

    Select Memory RAS

    Maximum Performance

    DRAM Clock Throttling

    Performance

    NUMA

    Enabled

    Low Voltage DDR Mode

    Performance Mode

    Patrol Scrub

    Disabled

    The following images show the BIOS settings on a Cisco Nexus 1110-X :
    Figure 2. BIOS Parameters - Recommended Process Configuration Settings



    Figure 3. BIOS Parameters - Recommended Memory Configuration Settings



    Gathering Information About the Management Software

    Before you begin the installation, you must have the following information for your Cisco Nexus Cloud Services Platform:

    • Administrator Credentials
    • HA Redundancy Role
    • HA Redundancy States
    • Domain ID
    • Network Uplinks
    • VLANs

    Administrator Credentials

    When you set up the system software, you are required to create an administrator password. The following table lists out the password strength guidelines:

    Strong Password Characteristics Weak Password Characteristics
    • At least eight characters
    • Uppercase letters
    • Lowercase letters
    • Numbers
    • Special characters
    • Consecutive characters, such as “abcd”
    • Repeating characters, such as “aaabbb”
    • Dictionary words
    • Proper names

    HA Redundancy Role

    The Cisco Nexus Cloud Services Platform product family is provided in redundant pairs for high availability. When setting up the device, you configure a high availability role as primary or secondary. The following table describes these roles.


    Note

    The HA standalone role is not supported for the Cisco Nexus Cloud Services Platform product family. The Cisco Nexus Cloud Services Platform is not supported in a non HA-mode.

    Role

    Description

    Primary

    • The primary role coordinates the active/standby redundancy state with the secondary Cisco Nexus Cloud Services Platform.
    • The primary role takes precedence during bootup when negotiating the active/standby redundancy state. If the secondary Cisco Nexus Cloud Services Platform is not in the active state at bootup, the primary Cisco Nexus Cloud Services Platform takes the active redundancy state.
    • You assign the primary role to the first Cisco Nexus Cloud Services Platform that you install in a dual system

    Secondary

    • The secondary role coordinates the active/standby state with the primaryCisco Nexus Cloud Services Platform.
    • You assign the secondary role to the second Cisco Nexus Cloud Services Platform that you install in a dual system.

    HA Redundancy States

    The following table describes the HA redundancy states.

    Redundancy States

    Description

    Active

    • Controls the system and is visible to the outside world.
    • The active system is remotely accessed through the network after the initial setup.
    • The user interface for managing the Cisco Nexus Cloud Services Platform is only available only through the active system.

    Standby

    • Synchronizes its configuration with the active Cisco Nexus Cloud Services Platform so that it is continuously ready to take over in case of a failure or manual switchover.
    • You cannot use Telnet or Secure Shell (SSH) protocols to communicate with the standby Cisco Nexus Cloud Services Platform.
    • The standby Cisco Nexus Cloud Services Platform is not network addressable and is accessed through the serial port.
    • The user interface for managing the Cisco Nexus Cloud Services Platform is not available through the standby system.

    Domain ID

    The primary and secondary Cisco Nexus Cloud Services Platforms use the domain ID to identify each other. The Cisco Nexus Cloud Services Platforms must be in the same switching domain, and share the same management IP address.

    Changes in the Supported Network Topology

    Starting in release 5.2(1)SP1(7.1), the Cisco Nexus Cloud Services Platform supports only a flexible network topology as the default topology type to connect to the network. As a result, all fresh installations of the Cisco Nexus Cloud Services Platform and upgrades from earlier versions are automatically configured in the flexible topology.

    The change in the supported network topology has the following benefits:

    • Reduces complexity in the network configuration.
    • Provides complete flexibility to connect the Cisco Nexus Cloud Services Platform product family to the network and allows you to achieve a maximum of six uplinks.
    • Eliminates the need to reboot either appliance in a pair for changing the topology type.

    Network Uplink Configuration

    The Cisco Nexus Cloud Services Platform product family supports a default flexible network uplink configuration to connect to the network. The flexible network configuration offers complete flexibility to connect the Cisco Nexus Cloud Services Platform product family to the network and allows you to achieve a maximum of six uplinks.

    Because of the changes in the supported topology type, the following changes occur in the network uplink configuration:
    • The initial setup script on the system manager module is modified to remove the option to select the network topology type. However, the questionnaire provides an option to configure port channels for control and management interfaces during a fresh installation of the Cisco Nexus Cloud Services Platform. For more information about setting up a primary or secondary Cisco Nexus Cloud Services Platform, see Setting up the Primary Cisco Nexus Cloud Services Platform or Setting up the Secondary Cisco Nexus Cloud Services Platform.
    • During the In-Service Software Upgrade (ISSU) process, the default network uplink type will be a Flexible topology. For more information about upgrading to the Cisco Nexus Cloud Services Platform Release 5.2(1)SP1(7.1), see Upgrading from earlier Software Releases.
    • The show network uplink type and network uplink type [number | flexible] commands are removed from the Cisco Nexus Cloud Services Platform Software CLI.

    After you upgrade to Cisco Nexus Cloud Services Platform Release 5.2(1)SP1(7.1), or migrate from the previously configured uplink type, the same port channels and other configurations are retained on the Cisco Nexus Cloud Services Platform.

    VLANs

    Control and management VLANs are used by the Cisco Nexus Cloud Services Platform product family to manage and communicate with its virtual service blades (VSB). These VLANs are added as a part of the initial setup of the management software. Control VLANs are added to each Virtual Service Blade (VSB) when the VSB is created. The management VLAN is inherited from the Cisco Nexus Cloud Services Platform product family by each VSB.

    If you modify a control or management VLAN on the Cisco Nexus Cloud Services Platform product family, you must enter the copy running-config startup-config command, and reload the switch for changes to take effect. To ensure service continuity, and to avoid a loss of communication between the VSB and the Cisco Nexus Cloud Services Platform, you must configure the control VLAN on the hosted VSB.

    Management VLAN

    The management VLAN is the VLAN that forwards traffic for the management port of the Cisco Nexus Cloud Services Platform. If your virtual service blade uses the management class of traffic, it inherits the management VLAN from the Cisco Nexus Cloud Services Platform. The management VLAN is used by the outside world to reach the Cisco Nexus Cloud Services Platform management 0 interface.

    When a VSB is deployed initially, the Cisco Nexus Cloud Services Platform and its hosted Cisco Nexus 1000 Virtual Supervisor Modules (VSMs), and the Virtual Service Blades (VSBs) share the same management VLAN. Unlike the control and packet VLANs that are set when a VSB is created, the management VLAN is inherited. However, the inherited management VLAN need not be the same as that of the Cisco Nexus Cloud Services Platform, and you can subsequently change the management VLAN to a different value.

    Control VLAN

    The control VLAN is a Layer 2 interface used for communication between the redundant Cisco Nexus Cloud Services Platforms. 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 Cloud Services Platforms.

    Setting up the Primary Cisco Nexus Cloud Services Platform

    You can set up the management software for the primary Cisco Nexus Cloud Services Platform in a redundant HA pair. We recommend that you configure a primary Cisco Nexus Cloud Services Platform with a secondary backup. Although you can configure a primary Cisco Nexus Cloud Services Platform without a secondary backup, this configuration in a production environment is not supported.


    Note
    Starting in Release, you can set up a primary Cisco Nexus Cloud Services Platform network configuration as a Flexible topology type.
    Before You Begin

    You have the following information available for this Cisco Nexus Cloud Services Platform:

    • Administrator password.
    • HA role (primary or secondary). If you do not specify an HA role, the role is configured as primary.
    • Control VLAN ID.
    • Domain ID.
    • Management VLAN ID.
    • Management 0 IP address—This IP address appears as the mgmt0 port on the appliance.
    • Default gateway IP address.
    • SSH service key type and number of key bits.
    Procedure
      Step 1   Log into the Cisco Nexus Cloud Services Platform CLI using one of the following methods:

      • Log in from a terminal server



      Example: 
      Example:
telnet 172.25.182.99 2005
Trying 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":

      • Log in from a Serial over LAN (SoL) connection through CIMC:



      Example: 
      Example:
ssh admin@172.25.182.230
admin@172.25.182.230's password:
switch# connect host
CISCO Serial Over LAN:
Close Network Connection to Exit

---- System Admin Account Setup ----
Enter the password for "admin": 
Confirm the password for "admin":

      The setup wizard starts automatically.

      Step 2   Enter and confirm the Administrator password.

      Example: 
      ---- System Admin Account Setup ----
Enter the password for "admin": 
Confirm the password for "admin":
      Step 3   Enter the HA role. If you do not specify a role, the primary role is assigned.
      Note   

      The HA standalone role is not supported for the Cisco Nexus Cloud Services Platform product family. The Cisco Nexus Cloud Services Platform is not supported in a non-HA mode.



      Example: 
      Enter HA role[primary/secondary]: primary
      Step 4   Enter the domain ID.

      Example: 
      Enter the domain ID<1-4095>: 1234
      Step 5   Enter the VLAN ID for the control VLAN.

      Example: 
      Enter the control vlan <1-3967, 4048-4093>: 2062
      Step 6   Setup the control channel.

      Example: 
      Choose Uplink <Gig:1,2,3,4,5,6 10Gig:7,8 NewPortChannel:0> :0
      Step 7   Choose the type of port channel.

      Example: 
      Choose type of portchannel <ha/lacp>: ha
      Step 8   Enter the uplinks for port channel 1.

      Example: 
      Choose uplinks <Gig:1,2,3,4,5,6 10Gig:7,8>:1,2
      Step 9   Enter the management VLAN.

      Example: 
      Enter the management vlan<1-3967, 4048-4093>:2061
      Step 10   Enter the management uplink.
      After the switch reboot, the default topology will be configured. See the following figures for examples of network configuration with and without a vPC and virtual switching system (VSS).
      Figure 4. Default Network Uplink Configuration without vPC and VSS



      Figure 5. Default Network Uplink Configuration with vPC and VSS



      For more information, see the Cisco Nexus Cloud Services Platform Software Configuration Guide.



      Example: 
      Choose Uplink: <Gig:3,4,5,6 10Gig:7,8 Po1:9 NewPortChannel:0>:9
Saving boot configuration. Please wait... 
[########################################] 100%
Copy complete, now saving to disk (please wait)...
      Step 11   Enter yes if you want to enter the basic configuration dialog.

      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 of
the system. Setup configures only enough connectivity for management
of the system.

*Note: setup is mainly used for configuring the system initially,
when no configuration is present. So setup always assumes system
defaults and not the current system configuration values.

Press Enter at anytime to skip a dialog. Use ctrl-c at anytime
to skip the remaining dialogs.
      Step 12   Enter no if you do not want to create another login account.

      Example: 
      Create another login account (yes/no) [n]: no
      Step 13   Enter no if you do not want to configure a read-only SNMP community string.

      Example: 
      Configure read-only SNMP community string (yes/no) [n]: no
      Step 14   Enter no if you do not want to configure a read-write SNMP community string.

      Example: 
      Configure read-write SNMP community string (yes/no) [n]:
      Step 15   Enter a name for the Cisco Nexus Cloud Services Platform appliance.

      Example: 
      Enter the CSP name [Nexus1010]:Nexus1010
      Step 16   Enter yes if you want to configure out-of-band management, and then enter the management 0 IPv4 or IPv6 address. This IP address 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): V4
Mgmt0 IPv4 address: 192.168.61.51
Mgmt0 IPv4 netmask prefix : 255.255.255.0
      Step 17   Answer yes if you want to configure the default gateway.

      Example: 
      Configure the default-gateway: (yes/no) [y]: yes
IPv4 address of the default gateway: 192.168.61.254
      Step 18   Enter no if you do not want to configure advanced IP options.

      Example: 
      Configure Advanced IP options? (yes/no) [n]: no
      Step 19   Enter no if you do not want to enable the Telnet service.

      Example: 
      Enable the telnet service? (yes/no) [y]: no
      Step 20   Enter yes if you want to enable the SSH service, and then enter the key type and number of key bits.

      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>[1024]: 1024
      Step 21   Enter yes if you want to enable the HTTP server.

      Example: 
      Enable http-server? (yes/no) [y]: yes
      Step 22   Enter no if you do not want to configure the NTP server. The configuration is summarized.

      Example: 
      Configure NTP server? (yes/no) [n]: no
The following configuration will be applied:
  switchname Nexus-CSP
  interface mgmt0
  ip address 192.168.61.51 255.255.255.0
  no system shutdown
  vrf context management
  ip route 0.0.0.0/0 192.168.61.254
  no telnet server enable
  ssh key rsa 1024 force
  ssh server enable
  feature http-server
      Step 23   Do one of the following:
      • If you do not want to edit the configuration, enter no and continue with the next step.
      • If you want to edit the configuration, enter yes and return to Step 11 to revisit each command. 
        Would you like to edit the configuration? (yes/no) [n] :no
      Step 24   Enter yes if you want to edit this configuration. 
      Would you like to edit the configuration? (yes/no) [n]:no
      Step 25   Enter yes if you want to use and save this configuration.
      Caution    If you do not save the configuration now, none of your changes are part of the configuration the next time that the switch is rebooted. Enter yes to save the new configuration to ensure that the kickstart and system images are also automatically configured.


      Example: 
      Use this configuration and save it? (yes/no) [y]: yes
[########################################] 100%
Copy complete, now saving to disk (please wait)... System is going to reboot to configure network uplinks.
      After the new configuration is saved into nonvolatile storage, the running and the startup copies of the configuration are identical.
      Note   

      You can use the setup routine to update the configuration that you made in Step 11 through Step23 at any time by entering the setup command in EXEC mode. After the setup begins, press Enter to skip a command. Press Ctrl–c to skip the remaining commands.

      Step 26   Verify the configuration: 
      telnet 172.25.182.99 2005
Trying 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":
ssh admin@172.25.182.230
admin@172.25.182.230's password:
switch# connect host
CISCO Serial Over LAN:
Close Network Connection to Exit

---- System Admin Account Setup ----
Enter the password for "admin": 
Confirm the password for "admin":

Enter HA role[primary/secondary]: primary

Enter the domain ID<1-4095>: 1234

Enter the control vlan <1-3967, 4048-4093>: 2062

Choose Uplink <Gig:1,2,3,4,5,6 10Gig:7,8 NewPortChannel:0> :0

Choose type of portchannel <ha/lacp>: ha
Choose uplinks <Gig:1,2,3,4,5,6 10Gig:7,8>:1,2

Enter the management vlan<1-3967, 4048-4093>:2061
Choose Uplink: <Gig:3,4,5,6 10Gig:7,8 Po1:9 NewPortChannel:0>:9
Saving boot configuration. Please wait... 
[########################################] 100%
Copy complete, now saving to disk (please wait)...

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 of
the system. Setup configures only enough connectivity for management
of the system.

*Note: setup is mainly used for configuring the system initially,
when no configuration is present. So setup always assumes system
defaults and not the current system configuration values.

Press Enter at anytime to skip a dialog. Use ctrl-c at anytime
to skip the remaining dialogs.

Create another login account (yes/no) [n]: no
Configure read-only SNMP community string (yes/no) [n]: no
Configure read-write SNMP community string (yes/no) [n]:
Enter the CSP name [Nexus1010]:Nexus1010
Continue with Out-of-band (mgmt0) management configuration? [yes/no] [y]: yes
Mgmt0 IP address type V4/V6? (V4): V4
Mgmt0 IPv4 address: 192.168.61.51
Mgmt0 IPv4 netmask prefix : 255.255.255.0
Configure the default-gateway: (yes/no) [y]: yes
IPv4 address of the default gateway: 192.168.61.254
Configure Advanced IP options? (yes/no) [n]: no
Enable the telnet service? (yes/no) [y]: no
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>[1024]: 1024
Enable http-server? (yes/no) [y]: yes
Configure NTP server? (yes/no) [n]: no

The following configuration will be applied:
  switchname Nexus-CSP
  interface mgmt0
  ip address 192.168.61.51 255.255.255.0
  no system shutdown
  vrf context management
  ip route 0.0.0.0/0 192.168.61.254
  no telnet server enable
  ssh key rsa 1024 force
  ssh server enable
  feature http-server

Would you like to edit the configuration? (yes/no) [n] :no
Would you like to edit the configuration? (yes/no) [n]:no
Use this configuration and save it? (yes/no) [y]: yes
[########################################] 100%
Copy complete, now saving to disk (please wait)... System is going to reboot to configure network uplinks.

      Setting up the Secondary Cisco Nexus Cloud Services Platform

      You can set up the management software for the secondary Cisco Nexus Cloud Services Platform in a redundant pair. We recommend that you configure the same domain ID, control VLAN, management VLAN, control uplink, management uplink for both primary and secondary Cisco Nexus Cloud Services Platforms.

      Procedure
        Step 1   Enter and confirm the Administrator password.

        Example: 
        ---- System Admin Account Setup ----
Enter the password for "admin":
        Step 2   Enter the HA role.

        Example: 
        Enter HA role[primary/secondary]: secondary
        Step 3   Enter the domain id.

        Example: 
        Enter the domain id<1-4095>: 1234
        Step 4   Enter the VLAN ID for the control VLAN.

        Example: 
        Enter the control vlan <1-3967, 4048-4093>: 2062
        Step 5   Enter the uplink type for the control channel setup.

        Example: 
        Choose uplink type <Gig:1,2,3,4,5,6 10Gig:7,8> : 6
        Step 6   Enter the new port channel for the control channel setup.

        Example: 
        Enter the new port channel:<ha/lacp>: ha
        Step 7   Enter the uplink for port channel 1.

        Example: 
        Choose the uplinks <Gig:1,2,3,4,5,6 10Gig:7,8>: 1,2
        Step 8   Enter the VLAN ID for the management VLAN.

        Example: 
        Enter management vlan<1-3967, 4048-4093>: 2061
        Step 9   Enter the uplink for the management channel setup.

        Example: 
        Choose the uplink <Gig:3,4,5,6 10Gig:7,8> :4
        Step 10   Enter the new port channel for the management channel set up.
        The following things occur on the switch:
        • After the new configuration is saved into nonvolatile storage, the running and the startup copies of the configuration are identical.
        • The system reboots to configure the network uplinks.
        • The system restarts and synchronizes its configuration with the primary Cisco Nexus 1000V.


        Example: 
        Choose new port channel:0>:9
 
  Saving boot configuration. Please wait... 

[########################################] 100%

Copy complete, now saving to disk (please wait)...
  System is going to reboot to configure network uplinks

        Configuration Example for Network Uplinks

        This example shows how to configure a 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 control vlan <1-3967, 4048-4093>: 347
  Enter control uplink <1-6>: 1
_
  Enter the domain id<1-4095>: 3477
_
  Enter management vlan <1-3967, 4048-4093>: 180
  Enter management uplink <1-6>: 2
_
  Saving boot configuration. Please wait... 
[########################################] 100%
  System is going to reboot to configure network uplinks

        Verifying the Cisco Nexus Cloud Services Platform Configuration

        To verify the Cisco Nexus Cloud Services Platform configuration, use the following commands:

        Command

        Purpose

        show running-configuration

        Displays the Cisco Nexus Cloud Services Platform running configuration.

        See show running configuration.

        show system redundancy status

        Displays the redundancy state (active or standby) and the redundancy role (primary or secondary) for the Cisco Nexus Cloud Services Platforms.

        See show system redundancy status.

        show svs domain

        Displays the domain information for the Cisco Nexus Cloud Services Platform.

        See show svs domain.

        show network cdp neighbors

        Displays the uplink connectivity for the active or standby Cisco Nexus Cloud Services Platform.

        See show network cdp neighbors.

        show running configuration

        This example shows how to display and verify the Cisco Nexus Cloud Services Platform setup configuration: 

        switch# show running-configuration

!Command: show running-config
!Time: Fri May 16 12:47:01 2014

version 5.2(1)SP1(7.1)
hostname switch

feature telnet
no feature http-server
feature scp-server

username admin password 5 $1$mu2Pt0OP$QngQ1hDbUG1x7Gaz/RIzS1  role network-admin
username admin role network-operator
username admin keypair rsa

banner motd #Cisco VSA
#

ip domain-lookup
ip host switch 172.23.180.184
errdisable recovery cause failed-port-state
snmp-server user admin network-operator auth md5 0xd8660132bb3eb73764f409f7d64ebb19 localizedkey
rmon event 1 log trap public description FATAL(1) owner PMON@FATAL
rmon event 2 log trap public description CRITICAL(2) owner PMON@CRITICAL
rmon event 3 log trap public description ERROR(3) owner PMON@ERROR
rmon event 4 log trap public description WARNING(4) owner PMON@WARNING
rmon event 5 log trap public description INFORMATION(5) owner PMON@INFO

vrf context management
  ip route 230.21.31.10/0 172.23.180.1
vlan 1,180,267

port-channel load-balance ethernet source-mac
port-profile default max-ports 32
port-profile default port-binding static
port-profile type vethernet N1K_Cloud_Default_Trunk
  switchport mode trunk
  no shutdown
  guid 65e71825-95da-4572-8019-97399f2c777f
  max-ports 64
  description Port Profile created for Nexus 1000V internal usage. Do not use.
  state enabled

system storage-loss log time 30
system inter-sup-heartbeat time 15
system trace 0xFFFFFFFF
logging level sysmgr 10
interface Ethernet1
interface Ethernet2
interface Ethernet3
interface Ethernet4
interface Ethernet5
interface Ethernet6
svs-domain
  control uplink Ethernet1
  management uplink Ethernet1
virtual-service-blade dcnm
  virtual-service-blade-type name DCNM-VSB-6.3
  interface eth0 vlan 180
  interface eth0 uplink Ethernet2
  interface eth1 vlan 0
  interface eth1 uplink
  ramsize 8192
  disksize 80
  numcpu 2
  cookie 2120424824
  no shutdown primary
interface VsbEthernet1/1
virtual-service-blade vsm
  virtual-service-blade-type name VSM_SV3-1.1
  interface control vlan 321
  interface control uplink Ethernet1
  interface management vlan 232
  interface management uplink Ethernet1
  interface packet vlan 321
  interface packet uplink Ethernet1
  ramsize 4096
  disksize 3
  numcpu 2
  cookie 514197755
  no shutdown primary
  no shutdown secondary
interface VsbEthernet2/1
interface VsbEthernet2/2
interface VsbEthernet2/3


interface mgmt0
  ip address 172.23.180.184/24

interface control0
line console
line vty
boot kickstart bootflash:/nexus-1010-kickstart.5.2.1.SP1.7.1.bin
boot system bootflash:/nexus-1010.5.2.1.SP1.7.1.bin
boot kickstart bootflash:/nexus-1010-kickstart.5.2.1.SP1.7.1.bin
boot system bootflash:/nexus-1010.5.2.1.SP1.7.1.bin
svs-domain
  domain id 267
  control vlan 267
  management vlan 180
  svs mode L2
  switch-guid c0a0c224-f8bc-494a-8585-77fe848e85e4

        show system redundancy status

        This example shows how to display redundancy status of the Cisco Nexus Cloud Services Platform setup configuration: 

        switch(config)# show system redundancy status
Redundancy role
---------------
      administrative:   primary
         operational:   primary

Redundancy mode
---------------
      administrative:   HA
         operational:   HA

This supervisor (sup-1)
-----------------------
    Redundancy state:   Active
    Supervisor state:   Active
      Internal state:   Active with HA standby

Other supervisor (sup-2)
------------------------
    Redundancy state:   Standby
    Supervisor state:   HA standby
      Internal state:   HA standby

        show svs domain

        This example shows how to display the domain information for the Cisco Nexus Cloud Services Platform: 

        switch# show svs domain
SVS domain config:
  Domain id:    267
  Control vlan: 267
  Management vlan:  180

        show network cdp neighbors

        This example shows how to display the uplink connectivity for the active or standby Cisco Nexus Cloud Services Platform: 
        switch# show network cdp neighbors
switch(config)# show network cdp neighbors
Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge
S - Switch, H - Host, I - IGMP, r - Repeater,
V - VoIP-Phone, D - Remotely-Managed-Device,
s - Supports-STP-Dispute


Device-ID Local Intrfce Hldtme Capability Platform Port ID

sfish-cat3k-K5-stack1 Ethernet2 164 S I cisco WS-C375 GigabitEt
hernet2/0/48
sfish-cat3k-K5-stack1 Ethernet3 164 S I cisco WS-C375 GigabitEt
hernet2/0/46
sfish-cat3k-K5-stack2 Ethernet4 158 S I cisco WS-C375 GigabitEt
hernet2/0/47
sfish-cat3k-K5-stack1 Ethernet5 164 S I cisco WS-C375 GigabitEt
hernet2/0/47
sfish-cat3k-K5-stack2 Ethernet6 158 S I cisco WS-C375 GigabitEt
hernet2/0/46
switch# ^C

        Getting Started with the Cisco Nexus Cloud Services Platform

        After you complete the software installation, you can configure the Cisco Nexus Cloud Services Platform product family.

        Procedure
          Step 1   Configure port channels for a flexible network uplink.

          Use this procedure to configure port channels after you set up the flexible network uplink type:

          Step 2   Set up remote management. Use this procedure to set up remote management in your startup configuration for use in recovering an unreachable Cisco Nexus Cloud Services Platform.
          Step 3   Do one of the following to add a service blade to the new Cisco Nexus Cloud Services Platform:

          • Create a new virtual service blade.

          • Migrate an existing VSM from a VM to the Cisco Nexus Cloud Services Platform.

            See the Cisco Nexus Cloud Services Platform Software Configuration Guide for more information.

          Feature History for Software Installation

          This section provides the software installation and upgrade release history:

          Feature Name

          Releases

          Feature Information

          Hardware support for SSL and Crypto acceleration

          5.2(1)SP1(7.1)

          This hardware was introduced.

          Static Topology

          5.2(1)SP1(7.1)

          This feature was removed.

          10 Gbps Interface Support

          5.2(1)SP1(7.1)

          This hardware was enabled.

          Cisco Nexus 1110-S and Cisco Nexus 1110-X

          4.2(1)SP1(5.1a))

          This hardware was introduced.

          Flexible Network Uplink

          4.0(4)SP1(4)

          This feature was introduced.

          Cisco Nexus 1010-X

          4.2(1)SP1(3)

          This hardware was introduced.

          Software upgrade

          4.2(1)SP1(2)

          This feature was introduced.