The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to install the Cisco Nexus Cloud Services Platform software and includes the following sections:
NoteFor information about upgrading the Cisco Nexus 1000V software as a virtual service blade (VSB), see theCisco Nexus 1000V Software Installation and Upgrade Guide, Release 4.2(1)SV2(2.1).
For an overview of the Cisco Nexus Cloud Services Platform product family and procedures for configuring the software after it is installed, see the Cisco Nexus Cloud Services Platform Software Configuration Guide, Release 4.2(1)SP1(6.1) .
The Cisco Nexus Cloud Services Platform software is preinstalled as an ISO image.
Step 1 Verify that you have the correct Cisco Integrated Management Controller (CIMC) software installed. See the Verifying the CIMC Software Version.
Step 2 Gather information about the management software. See the Gathering Information About the Management Software.
Step 3 Set up the primary Cisco Nexus Cloud Services Platform. See the Setting up the Primary Cisco Nexus Cloud Services Platform
Step 4 Set up the secondary Cisco Nexus Cloud Services Platform. See the Setting up the Secondary Cisco Nexus Cloud Services Platform.
Before you install the Cisco Nexus Cloud Services Platform Release 4.2(1)SP1(6.1), you must know or do the following:
– Version 1.5(1f) for the Cisco Nexus 1110 product family
– Version 1.4(3s)4 for the Cisco Nexus 1010 product family
Note • 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 version 1.4(3s)4.
– Upgrade to the latest CIMC version using the manual procedure in the Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.4.
– Upgrade the BIOS firmware version using the manual procedure in the Cisco UCS C-Series Rack-Mount Server BIOS Upgrade Guide.
The Cisco Nexus Cloud Services Platform product family guidelines and limitations are as follows:
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:
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 Cisco Nexus Cloud Services Platform, Release 4.2(1)SP1(6.1).
You can verify the CIMC software version installed on your Cisco Nexus Cloud Services Platform.
Before beginning this procedure, you must know or do the following:
Step 1 From the Cisco Nexus Cloud Services Platform do one of the following to display the product ID (PID):
Figure 2-1 CIMC Window with Product ID (PID)
Step 2 Do one of the following:
Before you begin the installation, you must have the following information for your Cisco Nexus Cloud Services Platform:
When you set up the system software, you are required to create an administrator password. Table 2-1 lists password strength guidelines:
|
|
---|---|
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—primary or secondary. Table 2-2 describes these roles.
NoteThe 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.
Table 2-3 describes the HA redundancy states.
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.
The Cisco Nexus Cloud Services Platform 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 After you configure an uplink type, the only way to modify it is to reload the software.
See the Cisco Nexus Cloud Services Platform Software Configuration Guide, Release 4.2(1)SP1(6.1) , for more information about network uplink types.
During the installation of the Cisco Nexus Cloud Services Platform product family you can set up the flexible network uplink type or the static network uplink type. If you modify the uplink type, a reload is required each time that the uplink type is modified for it to take effect.
See the Cisco Nexus Cloud Services Platform Software Configuration Guide, Release 4.2(1)SP1(6.1) , for information about migrating the network uplink types.
Table 2-4 shows the four supported network uplink types and the ports that carry each type of VLAN traffic.
|
|
|
|
|
---|---|---|---|---|
Management, Control, and Data traffic are on three different uplinks |
||||
Control and management VLANs are used by the Cisco Nexus Cloud Services Platform product family to manage and communicate 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 the VSB is created. The management VLAN is inherited from the Cisco Nexus Cloud Services Platform product family by each virtual service blade.
If you modify a control, packet, or management VLAN on the Cisco Nexus Cloud Services Platform product family, the change is effective immediately. You must reload the switch so that any changes to the control and management VLANs can take effect on the Cisco Nexus Cloud Services Platform. However, for service continuity, you must configure the same control and packet VLANs on the hosted VSMs. Otherwise, the Cisco Nexus Cloud Services Platform loses communication with its VSMs.
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.
The Cisco Nexus Cloud Services Platform and its hosted Cisco Nexus 1000 Virtual Supervisor Modules (VSMs) share the same management VLAN in a static topology. Unlike the control and packet VLANs that 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. Because the management VLAN is inherited from the Cisco Nexus Cloud Services Platform, if you change management VLAN for the Cisco Nexus Cloud Services Platform, the change is applied to both the Cisco Nexus Cloud Services Platform and all of its hosted Cisco Nexus 1000 VSMs in the next reload.
However, this constraint does not exist in a flexible topology where the management VLAN of a VSB can be different from the Cisco Nexus Cloud Services Platform host.
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.
You can set up the management software for the following:
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.
– HA role (primary or secondary)
If you do not specify an HA role, the role is configured as primary.
– Management 0 IP address
This IP address appears as the mgmt0 port on the appliance.
Step 1 Log in to the Cisco Nexus Cloud Services Platform CLI using one of the following methods:.
---- System Admin Account Setup ----
Enter the password for "admin":
Confirm the password for "admin":
---- System Admin Account Setup ----
Enter the password for "admin":
Confirm the password for "admin":
Step 2 Enter and confirm the Administrator password.
---- System Admin Account Setup ----
Confirm the password for
Enter the password for "admin":
"admin":
Step 3 Enter the HA role. If you do not specify a role, the primary role is assigned.
Enter HA role[primary/secondary]:
primary
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
Step 4 Enter the uplink type.To specify a static network uplink, enter a value from 1 to 4. To specify a flexible network uplink, enter the value 5.
Note After you configure an uplink type, the only way to modify it is to reload the software.
Step 5 Enter the VLAN ID for the control VLAN.
Step 6 Enter the control uplink.
Step 8 Enter the VLAN ID for the management VLAN.
Step 9 Enter the management uplink.
When you have completed this process, the Cisco Nexus Cloud Services Platform software saves the configuration and automatically reboots to configure the network uplinks.
After the new configuration is saved into nonvolatile storage, the running and the startup copies of the configuration are identical.
After the switch reboot, the default static or flexible topology will be configured. See Figure 2-2 for an example of a default flexible network uplink configuration without a vPC and VSS. See Figure 2-3 for an example of a default flexible network configuration with a vPC and VSS.
Figure 2-2 Default Flexible Network Uplink Configuration without vPC and VSS
Figure 2-3 Default Flexible Network Uplink Configuration with vPC and VSS
For more information, see the Cisco Nexus Cloud Services Platform Software Configuration Guide, Release 4.2(1)SP1(6.1) .
Step 10 Enter yes if you want to enter the basic configuration dialog.
Step 11 Enter no if you do not want to create another login account.
Create another login account (yes/no) [n]: no
Step 12 Enter no if you do not want to configure a read-only SNMP community string.
Configure read-only SNMP community string (yes/no) [n]: no
Step 13 Enter no if you do not want to configure a read-write SNMP community string.
Configure read-write SNMP community string (yes/no) [n]:
Step 14 Enter a name for the appliance.
Step 15 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.
Continue with Out-of-band (mgmt0) management configuration? [yes/no] [y]: yes
Mgmt0 IP address type V4/V6? (V4): V4
Step 16 Answer yes if you want to configure the default gateway.
Configure the default-gateway: (yes/no) [y]: yes
IPv4 address of the default gateway: 45.45.45.1
Step 17 Enter no if you do not want to configure advanced IP options.
Configure Advanced IP options (yes/no)? [n]: no
Step 18 Enter no if you do not want to enable the Telnet service.
Enable the telnet service? (yes/no) [y]: no
Step 19 Enter yes if you want to enable the SSH service, and then enter the key type and number of key bits.
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
Step 20 Enter yes if you want to configure the HTTP server.
Step 21 Enter no if you do not want to configure the NTP server.
The configuration is summarized.
Configure NTP server? (yes/no) [n]: no
Step 22 Do one of the following:
Step 23 Enter yes if you want to use and save this configuration.
Use this configuration and save it? (yes/no) [y]: yes
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 Step 23 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 24 Verify the configuration :
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, uplink type, control VLAN, management VLAN, control uplink, management uplink for both primary and secondary Cisco Nexus Cloud Services Platforms.
Step 1 Enter and confirm the Administrator password.
---- System Admin Account Setup ----
Enter the password for "admin":
Enter HA role[primary/secondary]:
secondary
Note After you configure an uplink type, the only way you can modify it is to reload the software.
Step 4 Enter the VLAN ID for the control VLAN.
Step 5 Enter the control uplink type.
Step 7 Enter the VLAN ID for the management VLAN.
Step 8 Enter the management uplink type.
The following things occur on the switch:
Step 9 Verify the configuration using the following command:
This example shows how to configure a flexible network uplink configuration during installation:
This example shows how to configure a static network uplink configuration during installation:
To verify the Cisco Nexus Cloud Services Platform configuration, use the following commands:
|
|
---|---|
Displays the Cisco Nexus Cloud Services Platform running configuration. See Example 2-1 on page 2-19 . |
|
Displays the redundancy state (active or standby) and the redundancy role (primary or secondary) for the Cisco Nexus Cloud Services Platforms. See Example 2-2 on page 2-21 . |
|
Displays the domain information for the Cisco Nexus Cloud Services Platform. See Example 2-3 on page 2-22 . |
|
Displays the uplink connectivity for the active or standby Cisco Nexus Cloud Services Platform. See Example 2-4 on page 2-22 . |
Example 2-1 Setup Configuration
This example shows how to display and verify the Cisco Nexus Cloud Services Platform setup configuration:
Example 2-4 CDP neighbors (standby)
After you complete the software installation, you can configure the Cisco Nexus Cloud Services Platform product family.
Step 1 Configuring port channels for flexible network uplink. Use this procedure to configure port channels after you set up the flexible network uplink type.
Step 2 Setting 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:
See the Cisco Nexus Cloud Services Platform Software Configuration Guide, Release 4.2(1)SP1(6.1) for more information.
This section provides the software installation and upgrade release history.
|
|
|
---|---|---|