Cisco HX Data Platform Preinstallation Checklist Form
Cisco HX Data Platform Preinstallation Checklist Form
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE
PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT
YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the
UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
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:
http://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)
Contents
Contents
Checklist Instructions
This is a preengagement checklist for Cisco HyperFlex Systems sales, services, and partners to send to customers. Cisco uses this
form to create a configuration file for the initial setup of your system enabling a timely and accurate installation.
Important: You CANNOT fill in the checklist using the HTML page.
Contact Information
Customer Account Team and Contact Information
Name Title E-mail Phone
Attention Name/Dept
Street Address #1
Street Address #2
Attention Name/Dept
Street Address #1
Street Address #2
Software Requirements
The software requirements include verification that you are using compatible versions of Cisco HyperFlex Systems (HX) components
and VMware vSphere components.
Verify that the preconfigured HX servers have the same version of Cisco UCS server firmware installed. If the Cisco UCS Fabric
Interconnects (FI) firmware versions are different, see the Cisco HyperFlex Systems Upgrade Guide for steps to align the
firmware versions.
For new hybrid or All Flash (Cisco HyperFlexHX240c M4 or HX220c M4) deployments, verify that Cisco UCS Manager 3.1(2g)
or later is installed. Contact Cisco TAC for guidance.
For SED based HyperFlex systems, ensure that the A (Infrastructure) and C (Rack server) bundles are at Cisco UCS Manager
version 3.1(3c).
To reinstall an HX server, download supported and compatible versions of the software. See the Cisco HyperFlex Systems Getting
Started Guide for the requirements and steps.
HyperFlex Release HX Data Platform Installer HX Data Platform Recommended UCS FI Firmware
2.5(1b) 2.5(1b) 2.5(1b) 3.1(3c) required for SED systems and
recommended for non-SED systems.
HyperFlex Licensing
As of version 2.5(1a), HyperFlex uses a smart licensing mechanism to apply your licenses. See the Cisco HyperFlex Systems Getting
Started Guide for details and steps.
2.5(1a) 6.0 U1b, 6.0 U2, 6.0 U2 Patch 3, 6.0 U2 Patch 4, Enterprise, Enterprise Plus, Standard, Essentials Plus,
6.0 U3, 6.5 Patch 1a ROBO
2.1(1b) 6.0 U1b, 6.0 U2, 6.0 U2 Patch 3, 6.0 U2 Patch 4, Enterprise, Enterprise Plus, Standard, Essentials Plus,
6.0 U3 ROBO
2.0(1a) 6.0 U1b, 6.0 U2, 6.0 U2 Patch 3, 6.0 U2 Patch 4 Enterprise, Enterprise Plus, Standard, Essentials Plus,
ROBO
1.8(1f) 6.0 U1b, 6.0 U2, 6.0 U2 Patch 3 Enterprise, Enterprise Plus, Standard, Essentials Plus,
ROBO
1.8(1e) 6.0 U1b, 6.0 U2, 6.0 U2 Patch 3 Enterprise, Enterprise Plus, Standard, Essentials Plus,
ROBO
1.8(1c) 6.0 U1b, 6.0 U2, 6.0 U2 Patch 3 Enterprise, Enterprise Plus, Standard, Essentials Plus,
ROBO
1.8(1b) 6.0 U1b, 6.0 U2, 6.0 U2 Patch 3 Enterprise, Enterprise Plus, Standard, Essentials Plus,
ROBO
1.8(1a) 6.0 U1b, 6.0 U2, 6.0 U2 Patch 3 Enterprise, Enterprise Plus, Standard, Essentials Plus,
ROBO
Note:
The SD cards have the OEM licenses preinstalled. If you delete or overwrite the content of the SD cards after receiving
the HX servers, you also delete the factory-installed licenses from the SD cards.
OEM license keys is a new VMware vCenter 6.0 U1b feature. Earlier versions do not support OEM licenses.
All factory-installed HX nodes share the same OEM license key. With vSphere OEM keys, the " Usage count can exceed
the Capacity value.
When you add an HX host to vCenter through the Add Host wizard, in the Assign license section, select the OEM
license.
We obfuscate the actual vSphere OEM license key; for example, 0N085-XXXXX-XXXXX-XXXXX-10LHH
Standard, Essentials Plus, and ROBO editions are not available preinstalled on HX servers.
Physical Requirements
Physical Server Requirements
For a HX220c Cluster:
Two rack units (RU) for the UCS 6248UP Fabric Interconnects (FI) or four RU for the UCS 6296UP FI
HX220c Nodes are one RU each; for example, for a three-node cluster, three RU are required; for a four-node cluster, 4 RU
are required
If a Top-of-Rack switch is included in the install, add at least two additional RU of space for the switch.
Two RU for the UCS 6248UP FI or four RU for the UCS 6296UP FI
HX240c Nodes are two RU each; for example, for a three-node cluster, six RU are required; for a four-node cluster, eight RU
are required
If a Top-of-Rack switch is included in the install, add at least two additional RU of space for the switch.
Although there is no requirement for contiguous rack space, it makes installation easier.
The system requires two C13/C14 power cords connected to a 15-amp circuit per device in the cluster. At a minimum, there are
three HX nodes and two FI, and it can scale to eight HX nodes, two FI, and blade chassis.
Up to 2 - 4x uplink connections for UCS Fabric Interconnects.
Each FI requires either 2x10 Gb optical connections in an existing network, or 2x10 Gb Twinax cables. Each HX node requires
two Twinax cables for connectivity (10 Gb optics can be used).
Network Requirements
Verify your environment adheres to the following best practices:
Management traffic networkFrom the VMware vCenter, handles hypervisor (ESXi server) management and storage cluster
management.
Data traffic networkHandles the hypervisor and storage data traffic.
vMotion network
VM network
You can add/remove VLANs on the corresponding vNIC templates in Cisco UCS Manager, and create port groups on the
vSwitch.
Note:
Port Requirements
A minimum of two ports is requiredone for the Storage management network and one for the Storage data network. For redundancy
and failover, we highly recommend that you have four portstwo each for the Storage management network and the Storage data
network.
If your network is behind a firewall, in addition to the standard port requirements, VMware recommends ports for VMware ESXi and
VMware vCenter. Verify that the following firewall ports are open:
Tip: If you do not have standard configurations and need different port settings, refer to Table C-5 Port Literal Values for customizing
your environment.
Deployment Information
Before deploying Cisco HX Data Platform and creating a cluster, collect the following information about your system.
FI cluster IP address
Password
VLAN Information
Tag the VLAN IDs to the Fabric Interconnects.
Note: HX Data Platform, release 1.7Document and configure all customer VLANs as native on the FI prior to installation.
HX Data Platform, release 1.8 and laterDefault configuration of all customer VLANs is non-native.
VLAN for VMware ESXi and Hypervisor Management Used for management traffic among
Cisco HyperFlex (HX) management Network ESXi, HX, and VMware vCenter;
must be routable
Hypervisor Data Network
VLAN for HX storage traffic Storage controller management Used for storage traffic and requires
network L2
Storage controller data network
Network IP Addresses
Management Network IP Addresses Data Network IP Addresses
(must be routable) (does not have to be routable)
Important: Data and management networks must be on different subnets or installation fails.
ESXi Hostname* Hypervisor Management Storage Controller Hypervisor Data Storage Controller
Network Management Network Network Data Network
Server 1:
Server 2:
Server 3:
Server 4:
Server 5:
* Verify DNS forward and reverse records are created for each host. If no DNS records exist, hosts are added to vCenter by IP address
instead of FQDN.
Hypervisor Credentials
root username root
root password
Note: HyperFlex communicates with vCenter through standard ports. Port 80 is used for reverse HTTP proxy and may be changed
with TAC assistance. Port 443 is used for secure communication to the vCenter SDK and may not be changed.
* SSO Server URL can be found in vCenter at vCenter Server > Manage > Advanced Settings, key config.vpxd.sso.sts.uri.
Network Services
Note:
DNS and NTP servers should reside outside of the HX storage cluster.
Use an internally-hosted NTP server to provide a reliable source for the time.
DNS Servers
<Primary DNS Server IP address,
Secondary DNS Server IP address, >
NTP servers
<Primary NTP Server IP address,
Secondary NTP Server IP address, >
Time zone
Example: US/Eastern, US/Pacific
Auto Support
Enable Auto Support?
Yes or No required
For S1 or S2 support cases or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 support cases consist
of production network issues, such as a severe degradation or outage.) S1 and S2 support cases have Cisco TAC engineers assigned
immediately to ensure your business operations continue to run smoothly.
To open a support case by telephone, use one of the following numbers:
For a complete list of Cisco TAC contacts for Enterprise and Service Provider products, see
http://www.cisco.com/c/en/us/support/web/tsd-cisco-worldwide-contacts.html.
For a complete list of Cisco Small Business Support Center (SBSC) contacts, see http://www.cisco.com/c/en/us/support/web/tsd-cisco-
small-business-support-center-contacts.html.