Sda Standard Compliant Sd Host Controller Driver Download For Windows 7

Ricoh SD Bus Host Adapter Driver 6.13.3.2 Important: - These drivers/utilities come already preinstalled on your VAIO computer. If you are still using the originally preinstalled Operating System, you can reinstall any of these drivers/utilities by using the Vaio Recovery Center program on your VAIO computer. - These drivers/utilities are not updated versions.

SDA Standard Compliant SD Host Controller - Driver Download. Updating your drivers with Driver Alert can help your computer in a number of ways. From adding new functionality and improving performance, to fixing a major bug. Windows 8.1 32-Bit Driver. Windows 8.1 32-Bit 32-bit. Total Driver Versions: 12. Update your computer's drivers using DriverMax, the free driver update tool - SDHost - SDA Standard Compliant SD Host Controller Vendor - SDA Standard. SD Bus Host Adapter. Driver Manufacturer, Ricoh Company. Driver Type, hdc. Driver Version, 6.13.3.4. Driver Date, 5-12-2010. Windows, Windows 7 (6.1) 64 bit.

If you are looking for updated drivers/utilities, please visit the 'Updates' section of this website or use the VAIO Update program if your computer has this functionality. - Some VAIO preinstalled programs are not provided for download due to copyright restrictions. Exit all running programs. Download this file and save it to your hard drive. When the download is completed, locate the downloaded file in the location you specified.

Right-click the file downloaded in previous step and choose 'Extract All'. Follow the on-screen instructions to extract the compressed file.

Open Device Manager (Start >type without quotes 'Device Manager' in the Start Search box >press 'Enter') 7. Right click 'SDA Standard Compliant SD Host Controller' under 'SD host adapters' and click 'Update driver software'. Click 'Browse my computer for driver software'. Click 'browse' and select the folder which you extracted in step 5 above. Click 'OK' and click 'Next'. Wait while the driver is being installed.

Click 'Close' and restart your computer if prompted.

Cisco HyperFlex 2.5 for Virtual Server Infrastructure Deployment Guide for Cisco HyperFlex 2.5 for Virtual Server Infrastructure NOTE: Works with document’s Advanced Properties “First Published” property. Click File Properties Advanced Properties Custom. Last Updated: September 7, 2017 NOTE: Works with document’s Advanced Properties “Last Updated” property.

Click File Properties Advanced Properties Custom. About the Cisco Validated Design (CVD) Program The CVD program consists of systems and solutions designed, tested, and documented to facilitate faster, more reliable, and more predictable customer deployments. For more information visit:. ALL DESIGNS, SPECIFICATIONS, STATEMENTS, INFORMATION, AND RECOMMENDATIONS (COLLECTIVELY, 'DESIGNS') IN THIS MANUAL ARE PRESENTED 'AS IS,' WITH ALL FAULTS.

CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE WARRANTY 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 THE DESIGNS, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE DESIGNS ARE SUBJECT TO CHANGE WITHOUT NOTICE. USERS ARE SOLELY RESPONSIBLE FOR THEIR APPLICATION OF THE DESIGNS.

THE DESIGNS DO NOT CONSTITUTE THE TECHNICAL OR OTHER PROFESSIONAL ADVICE OF CISCO, ITS SUPPLIERS OR PARTNERS. USERS SHOULD CONSULT THEIR OWN TECHNICAL ADVISORS BEFORE IMPLEMENTING THE DESIGNS.

RESULTS MAY VARY DEPENDING ON FACTORS NOT TESTED BY CISCO. With the proliferation of virtualized environments across most IT landscapes, other technology stacks which have traditionally not offered the same levels of simplicity, flexibility, and rapid deployment as virtualized compute platforms have come under increasing scrutiny. In particular, networking devices and storage systems have lacked the agility of hypervisors and virtual servers. With the introduction of Cisco HyperFlex, Cisco has brought the dramatic enhancements of hyperconvergence to the modern datacenter. Cisco HyperFlex systems are based on the Cisco UCS platform, combining Cisco HX-Series x86 servers and integrated networking technologies via the Cisco UCS Fabric Interconnects, into a single management domain, along with industry leading virtualization hypervisor software from VMware, and next-generation software defined storage technology. The combination creates a complete virtualization platform, which provides the network connectivity for the guest virtual machine (VM) connections, and the distributed storage to house the VMs, spread across all of the Cisco UCS x86 servers, versus using specialized storage or networking components.

The unique storage features of the HyperFlex log based filesystem enable rapid cloning of VMs, snapshots without the traditional performance penalties, and inline data deduplication and compression. All configuration, deployment, management, and monitoring of the solution can be done with existing tools for Cisco UCS and VMware, such as Cisco UCS Manager and VMware vCenter. This powerful linking of advanced technology stacks into a single, simple, rapidly deployed solution makes Cisco HyperFlex a true second generation hyperconverged platform. New, with the introduction of Cisco HyperFlex HXDP 2.5, are enterprise class data protection features, including snapshot-based virtual machine replication, and data-at-rest encryption.

Virtual machine replication allows for easy configuration of a secondary HyperFlex site for disaster recovery. Data-at-rest encryption keeps all data on the disks encrypted to protect against accidental data loss or theft. Customers can choose to deploy SSD-only All-Flash HyperFlex clusters for improved performance, increased density, and reduced latency, or use HyperFlex hybrid clusters which combine high-performance SSDs and low-cost, high-capacity HDDs to optimize the cost of storing data. Further enhancements include an all-new HTML5 based native HyperFlex Connect management tool with role-based access control, support for 40 GbE connectivity, larger scale 16-node clusters, and support for NVMe based SSDs in place of SAS-based SSDs for the caching disks. The Cisco HyperFlex System provides an all-purpose virtualized server platform, with hypervisor hosts, networking connectivity, and virtual server storage across a set of Cisco UCS HX-Series x86 rack mount servers. Legacy datacenter deployments have relied on a disparate set of technologies, each performing a distinct and specialized function, such as network switches connecting endpoints and transferring Ethernet network traffic, and Fibre Channel (FC) storage arrays providing block based storage via a dedicated storage array network (SAN). Each of these systems had unique requirements for hardware, connectivity, management tools, operational knowledge, monitoring, and ongoing support.

A legacy virtual server environment was often divided up into areas commonly referred to as silos, within which only a single technology operated, along with their correlated software tools and support staff. Silos could often be divided between the x86 computing hardware, the networking connectivity of those x86 servers, SAN connectivity and storage device presentation, the hypervisors and virtual platform management, and finally the guest VM themselves along with their OS and applications. This model proves to be inflexible, difficult to navigate, and is susceptible to numerous operational inefficiencies. A more modern datacenter model was developed called a converged infrastructure. Converged infrastructures attempt to collapse the traditional silos by combining these technologies into a more singular environment, which has been designed to operate together in pre-defined, tested, and validated designs. A key component of the converged infrastructure was the revolutionary combination of x86 rack and blade servers, along with converged Ethernet and Fibre Channel networking offered by the Cisco UCS platform. Converged infrastructures leverage Cisco UCS, plus new deployment tools, management software suites, automation processes, and orchestration tools to overcome the difficulties deploying traditional environments, and do so in a much more rapid fashion.

These new tools place the ongoing management and operation of the system into the hands of fewer staff, with more rapid deployment of workloads based on business needs, while still remaining at the forefront of flexibility to adapt to workload needs, and offering the highest possible performance. Cisco has had incredible success in these areas with our various partners, developing leading solutions such as Cisco FlexPod, SmartStack, VersaStack, and VBlock architectures. Despite these advances, because these converged infrastructures contained some legacy technology stacks, particularly in the storage subsystems, there often remained a division of responsibility amongst multiple teams of administrators. Alongside, there is also a recognition that these converged infrastructures can still be a somewhat complex combination of components, where a simpler system would suffice to serve the workloads being requested. Significant changes in the storage marketplace have given rise to the software defined storage (SDS) system.

Legacy FC storage arrays often contained a specialized subset of hardware, such as Fibre Channel Arbitrated Loop (FC-AL) based controllers and disk shelves along with optimized Application Specific Integrated Circuits (ASIC), read/write data caching modules and cards, plus highly customized software to operate the arrays. With the rise of Serial Attached SCSI (SAS) bus technology and its inherent benefits, storage array vendors began to transition their internal hardware architectures to SAS, and with dramatic increases in processing power from recent x86 processor architectures, they also used fewer or no custom ASICs at all. As disk physical sizes shrank, x86 servers began to have the same density of storage per rack unit (RU) as the arrays themselves, and with the proliferation of NAND based flash memory solid state disks (SSD), they also now had access to input/output (IO) devices whose speed rivaled that of dedicated caching devices.

If servers themselves now contained storage devices and technology to rival many dedicated arrays on the market, then the major differentiator between them was the software providing allocation, presentation and management of the storage, plus the advanced features many vendors offered. This has led to the rise of software defined storage, where the x86 servers with the storage devices ran software to effectively turn one or more of them, working cooperatively, into a storage array much the same as the traditional arrays were.

In a somewhat unexpected turn of events, some of the major storage array vendors themselves were pioneers in this field, recognizing the technological shifts in the market, and attempting to profit from the software features they offered versus their specialized hardware, as had been done in the past. Some early uses of SDS systems simply replaced the traditional storage array in the converged architectures as described earlier.

That configuration still had a separate storage system from the virtual server hypervisor platform, and depending on the solution provider, still remained separate from the network devices. If the servers that hosted the VMs, and also provided the SDS environment were in fact the same model of server, could they simply do both things at once and collapse the two functions into one? This ultimate combination of resources becomes what the industry has given the moniker of a hyperconverged infrastructure. Hyperconverged infrastructures coalesce the computing, memory, hypervisor, and storage devices of servers into a single platform for virtual servers.

There is no longer a separate storage system, as the servers running the hypervisors also provide the software defined storage resources to store the virtual servers, effectively storing the virtual machines on themselves. Now nearly all the silos are gone, and a hyperconverged infrastructure becomes something almost completely self-contained, simpler to use, faster to deploy, easier to consume, yet still flexible and with very high performance.

Many hyperconverged systems still rely on standard networking components, such as on-board network cards in the x86 servers, and top-of-rack switches. The Cisco HyperFlex system combines the convergence of computing and networking provided by Cisco UCS, along with next-generation hyperconverged storage software, to uniquely provide the compute resources, network connectivity, storage, and hypervisor platform to run an entire virtual environment, all contained in a single monolithic system. Some key advantages of hyperconverged infrastructures are the simplification of deployment, day to day management operations, as well as increased agility, thereby reducing the amount operational costs. Since hyperconverged storage can be easily managed by an IT generalist, this can also reduce technical debt going forward that is often accrued by implementing complex systems that need dedicated management teams and skillsets. The intended audience for this document includes, but is not limited to, sales engineers, field consultants, professional services, IT managers, partner engineering, and customers deploying the Cisco HyperFlex System. External references are provided wherever applicable, but readers are expected to be familiar with VMware specific technologies, infrastructure concepts, networking connectivity, and security policies of the customer installation. This document describes the steps required to deploy, configure, and manage a Cisco HyperFlex system.

The document is based on all known best practices using the software, hardware and firmware revisions specified in the document. As such, recommendations and best practices can be amended with later versions. This document showcases the installation, configuration and expansion of Cisco HyperFlex standard and also extended clusters, including both converged nodes and compute-only nodes, in a typical customer datacenter environment. While readers of this document are expected to have sufficient knowledge to install and configure the products used, configuration details that are important to the deployment of this solution are provided in this CVD. The Cisco HyperFlex system has several new capabilities and enhancements in version 2.5: Native replication of virtual machine snapshots between two Cisco HyperFlex clusters, enabling recovery of a single VM, multiple VMs, or an entire site as a disaster recovery.

Data-at-rest encryption using hardware based self-encrypting disks (SED) to protect data written on the disks, preventing accidental data loss or data theft. Support for larger scale clusters; up to 16 converged nodes and up to 16 compute-only nodes per all-flash cluster, and support for managing up to 100 Cisco HyperFlex clusters per VMware vCenter instance. Support for using NVMe based SSDs as the caching disk in the Cisco HyperFlex all-flash converged nodes. The new HyperFlex Connect native HTML5 management GUI, with role-based access control. A fully supported release of the HyperFlex REST API, allowing programmatic management and monitoring of the cluster, and its features. HXAF240c-M4SX nodes now can scale to a full allotment of 23 capacity SSDs per node.

Expanded Cisco UCS blade and rack-mount server model options for compute-only nodes. Smart Licensing FIPS/CC Certification VMware vSphere 6.5 support For the comprehensive documentation suite, refer to the following location on the Cisco UCS HX-Series Documentation Roadmap. Note: A login is required for the Documentation Roadmap. Hyperconverged Infrastructure web link: The Cisco HyperFlex system provides a fully contained virtual server platform, with compute and memory resources, integrated networking connectivity, a distributed high-performance log based filesystem for VM storage, and the hypervisor software for running the virtualized servers, all within a single Cisco UCS management domain. The Cisco Unified Computing System (Cisco UCS) is a next-generation data center platform that unites compute, network, and storage access. The platform, optimized for virtual environments, is designed using open industry-standard technologies and aims to reduce total cost of ownership (TCO) and increase business agility.

The system integrates a low-latency, lossless 10 Gigabit Ethernet or 40 Gigabit Ethernet unified network fabric with enterprise-class, x86-architecture servers. It is an integrated, scalable, multi chassis platform in which all resources participate in a unified management domain. The main components of Cisco Unified Computing System are: Computing: The system is based on an entirely new class of computing system that incorporates rack-mount and blade servers based on Intel Xeon Processors. Network: The system is integrated onto a low-latency, lossless, 10-Gbps or 40-Gbps unified network fabric.

This network foundation consolidates LANs, SANs, and high-performance computing networks which are often separate networks today. The unified fabric lowers costs by reducing the number of network adapters, switches, and cables, and by decreasing the power and cooling requirements. Virtualization: The system unleashes the full potential of virtualization by enhancing the scalability, performance, and operational control of virtual environments. Cisco security, policy enforcement, and diagnostic features are now extended into virtualized environments to better support changing business and IT requirements. Storage access: The system provides consolidated access to both SAN storage and Network Attached Storage (NAS) over the unified fabric. By unifying storage access, the Cisco Unified Computing System can access storage over Ethernet, Fibre Channel, Fibre Channel over Ethernet (FCoE), and iSCSI.

This provides customers with their choice of storage protocol and physical architecture, and enhanced investment protection. In addition, the server administrators can pre-assign storage-access policies for system connectivity to storage resources, simplifying storage connectivity, and management for increased productivity.

Management: The system uniquely integrates all system components which enable the entire solution to be managed as a single entity by the Cisco UCS Manager (UCSM). The Cisco UCS Manager has an intuitive graphical user interface (GUI), a command-line interface (CLI), and a robust application programming interface (API) to manage all system configuration and operations. The Cisco Unified Computing System is designed to deliver: A reduced Total Cost of Ownership and increased business agility.

Increased IT staff productivity through just-in-time provisioning and mobility support. A cohesive, integrated system which unifies the technology in the data center. The system is managed, serviced and tested as a whole.

Scalability through a design for hundreds of discrete servers and thousands of virtual machines and the capability to scale I/O bandwidth to match demand. Industry standards supported by a partner ecosystem of industry leaders. The Cisco UCS Fabric Interconnect is a core part of the Cisco Unified Computing System, providing both network connectivity and management capabilities for the system. Depending on the model chosen, the Cisco UCS Fabric Interconnect offers line-rate, low-latency, lossless 10 Gigabit or 40 Gigabit Ethernet, Fibre Channel over Ethernet (FCoE) and Fibre Channel connectivity. Cisco UCS Fabric Interconnects provide the management and communication backbone for the Cisco UCS C-Series, S-Series and HX-Series Rack mount Servers, Cisco UCS B-Series Blade Servers and Cisco UCS 5100 Series Blade Server Chassis.

All servers and chassis, and therefore all blades, attached to the Cisco UCS Fabric Interconnects become part of a single, highly available management domain. In addition, by supporting unified fabrics, the Cisco UCS Fabric Interconnects provide both the LAN and SAN connectivity for all servers within its domain.

From a networking perspective, the Cisco UCS 6200 Series uses a cut-through architecture, supporting deterministic, low latency, line rate 10 Gigabit Ethernet on all ports, up to 1.92 Tbps switching capacity and 160 Gbps bandwidth per chassis, independent of packet size and enabled services. The product family supports Cisco low-latency, lossless 10 Gigabit Ethernet unified network fabric capabilities, which increase the reliability, efficiency, and scalability of Ethernet networks. The Fabric Interconnect supports multiple traffic classes over the Ethernet fabric from the servers to the uplinks. Significant TCO savings come from an FCoE-optimized server design in which network interface cards (NICs), host bus adapters (HBAs), cables, and switches can be consolidated. The Cisco UCS 6300 Series offers the same features while supporting even higher performance, low latency, lossless, line rate 40 Gigabit Ethernet, with up to 2.56 Tbps of switching capacity.

Backward compatibility and scalability are assured with the ability to configure 40 Gbps quad SFP (QSFP) ports as breakout ports using 4x10GbE breakout cables. Existing UCS servers with 10GbE interfaces can be connected in this manner, although Cisco HyperFlex nodes must use a 40GbE VIC adapter in order to connect to a Cisco UCS 6300 Series Fabric Interconnect. The Cisco UCS 6248UP Fabric Interconnect is a one-rack-unit (1RU) 10 Gigabit Ethernet, FCoE and Fiber Channel switch offering up to 960 Gbps throughput and up to 48 ports. The switch has 32 1/10-Gbps fixed Ethernet, FCoE, or 1/2/4/8 Gbps FC ports, plus one expansion slot. Figure 2 Cisco UCS 6248UP Fabric Interconnect The Cisco UCS 6296UP Fabric Interconnect is a two-rack-unit (2RU) 10 Gigabit Ethernet, FCoE, and native Fibre Channel switch offering up to 1920 Gbps of throughput and up to 96 ports.

The switch has 48 1/10-Gbps fixed Ethernet, FCoE, or 1/2/4/8 Gbps FC ports, plus three expansion slots. Figure 3 Cisco UCS 6296UP Fabric Interconnect The Cisco UCS 6332 Fabric Interconnect is a one-rack-unit (1RU) 40 Gigabit Ethernet and FCoE switch offering up to 2560 Gbps of throughput. The switch has 32 40-Gbps fixed Ethernet and FCoE ports. Up to 24 of the ports can be reconfigured as 4x10Gbps breakout ports, providing up to 96 10-Gbps ports. Figure 4 Cisco UCS 6332 Fabric Interconnect The Cisco UCS 6332-16UP Fabric Interconnect is a one-rack-unit (1RU) 10/40 Gigabit Ethernet, FCoE, and native Fibre Channel switch offering up to 2430 Gbps of throughput. The switch has 24 40-Gbps fixed Ethernet and FCoE ports, plus 16 1/10-Gbps fixed Ethernet, FCoE, or 4/8/16 Gbps FC ports.

Up to 18 of the 40-Gbps ports can be reconfigured as 4x10Gbps breakout ports, providing up to 88 total 10-Gbps ports. Figure 5 Cisco UCS 6332-16UP Fabric Interconnect. Note: When used for a Cisco HyperFlex deployment, due to mandatory QoS settings in the configuration, the 6332 and 6332-16UP will be limited to a maximum of four 4x10Gbps breakout ports. A HyperFlex cluster requires a minimum of three HX-Series “converged” nodes (with disk storage).

Data is replicated across at least two of these nodes, and a third node is required for continuous operation in the event of a single-node failure. Each node that has disk storage is equipped with at least one high-performance SSD drive for data caching and rapid acknowledgment of write requests. Each node also is equipped with additional disks, up to the platform’s physical limit, for long term storage and capacity. This small footprint Cisco HyperFlex all-flash model contains two Cisco Flexible Flash (FlexFlash) Secure Digital (SD) cards that act as the boot drives, a single 120 GB or 240 GB solid-state disk (SSD) data-logging drive, a single 400 GB NVMe or a 400GB or 800 GB SAS SSD write-log drive, and six 960 GB or 3.8 terabyte (TB) SATA SSD drives for storage capacity. For configurations requiring self-encrypting drives, the caching SSD is replaced with an 800 GB SAS SED SSD, and the capacity disks are also replaced with 800 GB SAS SED SSDs. A minimum of three nodes and a maximum of sixteen nodes can be configured in one HX all-flash cluster. Figure 6 HXAF220c-M4S All-Flash Node This capacity optimized Cisco HyperFlex all-flash model contains two FlexFlash SD cards that act as boot drives, a single 120 GB or 240 GB solid-state disk (SSD) data-logging drive, a single 400 GB NVMe or a 400GB or 800 GB SAS SSD write-log drive, and six to twenty-three 960 GB or 3.8 terabyte (TB) SATA SSD drives for storage capacity.

For configurations requiring self-encrypting drives, the caching SSD is replaced with an 800 GB SAS SED SSD, and the capacity disks are also replaced with 800 GB SAS SED SSDs. A minimum of three nodes and a maximum of sixteen nodes can be configured in one HX all-flash cluster. Note: In all-flash configurations, either a 400 GB or 800 GB caching SAS SSD may be chosen. This option is provided to allow flexibility in ordering based on product availability, pricing and lead times. There is no performance, capacity or scalability benefit in choosing the larger disk. This small footprint Cisco HyperFlex hybrid model contains six 1.2 terabyte (TB) SAS HDD drives that contribute to cluster storage capacity, a 120 GB or 240 GB SSD housekeeping drive, a 480 GB SAS SSD caching drive, and two Cisco Flexible Flash (FlexFlash) Secure Digital (SD) cards that act as boot drives.

For configurations requiring self-encrypting drives, the caching SSD is replaced with an 800 GB SAS SED SSD, and the capacity disks are replaced with 1.2TB SAS SED HDDs. A minimum of three nodes and a maximum of eight nodes can be configured in one HX hybrid cluster. Figure 8 HX220c-M4S Node This capacity optimized Cisco HyperFlex hybrid model contains a minimum of six and up to twenty-three 1.2 TB SAS HDD drives that contribute to cluster storage, a single 120 GB or 240 GB SSD housekeeping drive, a single 1.6 TB SAS SSD caching drive, and two FlexFlash SD cards that act as the boot drives. For configurations requiring self-encrypting drives, the caching SSD is replaced with a 1.6 TB SAS SED SSD, and the capacity disks are replaced with 1.2TB SAS SED HDDs. A minimum of three nodes and a maximum of eight nodes can be configured in one HX hybrid cluster.

Note: In all configurations, either a 120 GB or 240 GB housekeeping disk may be chosen. This option is provided to allow flexibility in ordering based on product availability, pricing and lead times. There is no performance, capacity or scalability benefit in choosing the larger disk. S The Cisco UCS Virtual Interface Card (VIC) 1227 is a dual-port Enhanced Small Form-Factor Pluggable (SFP+) 10-Gbps Ethernet and Fibre Channel over Ethernet (FCoE)-capable PCI Express (PCIe) modular LAN-on-motherboard (mLOM) adapter installed in the Cisco UCS HX-Series Rack Servers. The VIC 1227 is used in conjunction with the Cisco UCS 6248UP or 6296UP model Fabric Interconnects.

The Cisco UCS VIC 1387 Card is a dual-port Enhanced Quad Small Form-Factor Pluggable (QSFP+) 40-Gbps Ethernet and Fibre Channel over Ethernet (FCoE)-capable PCI Express (PCIe) modular LAN-on-motherboard (mLOM) adapter installed in the Cisco UCS HX-Series Rack Servers. The VIC 1387 is used in conjunction with the Cisco UCS 6332 or 6332-16UP model Fabric Interconnects. The mLOM slot can be used to install a Cisco VIC without consuming a PCIe slot, which provides greater I/O expandability. It incorporates next-generation converged network adapter (CNA) technology from Cisco, providing investment protection for future feature releases. The card enables a policy-based, stateless, agile server infrastructure that can present up to 256 PCIe standards-compliant interfaces to the host, each dynamically configured as either a network interface card (NICs) or host bus adapter (HBA).

The personality of the interfaces is set programmatically using the service profile associated with the server. The number, type (NIC or HBA), identity (MAC address and World Wide Name [WWN]), failover policy, adapter settings, bandwidth, and quality-of-service (QoS) policies of the PCIe interfaces are all specified using the service profile.

Figure 11 Cisco VIC 1387 mLOM Card. Note: Hardware revision V03 or later of the Cisco VIC 1387 card is required for the Cisco HyperFlex HX-series servers. HyperFlex 2.5 expands the number of options available for using standard model Cisco UCS Rack-Mount and Blade Servers as compute-only nodes. All current model Cisco UCS M4 generation servers, except the C880 M4, may be used as compute-only nodes connected to a Cisco HyperFlex cluster, along with a limited number of previous M3 generation servers.

Any valid CPU and memory configuration is allowed in the compute-only nodes, and the servers can be configured to boot from SAN, local disks, or internal SD cards. Component Hardware Required Fabric Interconnects Two Cisco UCS 6248UP Fabric Interconnects, or Two Cisco UCS 6296UP Fabric Interconnects, or Two Cisco UCS 6332 Fabric Interconnects, or Two Cisco UCS 6332-16UP Fabric Interconnects Servers Three to Sixteen Cisco HyperFlex HXAF220c-M4S All-Flash rack servers, or Three to Sixteen HyperFlex HXAF240c-M4SX All-Flash rack servers, or Three to Eight Cisco HyperFlex HX220c-M4S Hybrid rack servers, or Three to Eight Cisco HyperFlex HX240c-M4SX Hybrid rack servers Table 2 lists some of the available processor models for the Cisco HX-Series servers. For a complete list and more information please refer to the links below: Compare models: HXAF220c-M4S Spec Sheet: HXAF240c-M4S Spec Sheet: HX220c-M4S Spec Sheet: HX240c-M4SX Spec Sheet. Model Cores Clock Speed Cache RAM Speed E5-2699 v4 22 2.2 GHz 55 MB 2400 MHz E5-2698 v4 20 2.2 GHz 50 MB 2400 MHz E5-2697 v4 18 2.3 GHz 45 MB 2400 MHz E5-2690 v4 14 2.6 GHz 35 MB 2400 MHz E5-2683 v4 16 2.1 GHz 40 MB 2400 MHz E5-2680 v4 14 2.4 GHz 35 MB 2400 MHz E5-2667 v4 8 3.2 GHz 25 MB 2400 MHz E5-2660 v4 14 2.0 GHz 35 MB 2400 MHz E5-2650 v4 12 2.2 GHz 30 MB 2400 MHz E5-2640 v4 10 2.4GHz 25 MB 2133 MHz E5-2630 v4 10 2.2 GHz 25 MB 2133 MHz E5-2620 v4 8 2.1 GHz 20 MB 2133 MHz Table 3 lists the hardware component options for the HXAF220c-M4S server model.

HXAF240c-M4SX Options Hardware Required Processors Chose a matching pair from the previous table of CPU options. HX220c-M4S Options Hardware Required Processors Chose a matching pair from the previous table of CPU options.

HX240c-M4SX Options Hardware Required Processors Chose a matching pair from the previous table of CPU options. Note: Cisco UCS Firmware 3.1(2g) is the minimum required for non-encrypting clusters, but 3.1(3c) is required to enable use of SED disks. Using version 3.1(3c) or later is highly recommended. The software revisions listed in Table 7 are the only valid and supported configuration at the time of the publishing of this validated design. Special care must be taken not to alter the revision of the hypervisor, vCenter server, Cisco HX platform software, or the Cisco UCS firmware without first consulting the appropriate release notes and compatibility matrixes to ensure that the system is not being modified into an unsupported configuration.

This document does not cover the installation and configuration of VMware vCenter Server for Windows, or the vCenter Server Appliance. The vCenter Server must be installed and operational prior to the installation of the Cisco HyperFlex HX Data Platform software. The following best practice guidance applies to installations of HyperFlex 2.5: Do not modify the default TCP port settings of the vCenter installation. Using non-standard ports can lead to failures during the installation. It is recommended to build the vCenter server on a physical server or in a virtual environment outside of the HyperFlex cluster. Building the vCenter server as a virtual machine inside the HyperFlex cluster environment is highly discouraged. There is a tech note for multiple methods of deployment if no external vCenter server is already available: Cisco HyperFlex clusters currently scale up from a minimum of 3 to a maximum of 16 converged nodes per all-flash cluster, i.e.

16 nodes providing storage resources to the HX Distributed Filesystem. For clusters with HX hybrid nodes, the limit is 8 converged nodes. For the compute intensive “extended” cluster design, a configuration with 3-16 Cisco HX-series all-flash converged nodes can be combined with up to 16 compute nodes. Since the quantity of compute-only nodes cannot exceed the quantity of converged nodes, in clusters with hybrid HX converged servers, the maximum number of compute-only nodes is 8.

Cisco blade servers and rack mount servers can be used for the compute only nodes. It is required that the number of compute-only nodes should always be less than or equal to number of converged nodes. Once the maximum size of a cluster has been reached, the environment can be “scaled out” by adding additional HX model servers to the Cisco UCS domain, installing an additional HyperFlex cluster on them, and controlling them via the same vCenter server. A maximum of 8 clusters can be created in a single UCS domain, and up to 100 HyperFlex clusters can be managed by a single vCenter server. Overall usable cluster capacity is based on a number of factors. The number of nodes in the cluster must be considered, plus the number and size of the capacity layer disks.

Caching disk sizes are not calculated as part of the cluster capacity. The replication factor of the HyperFlex HX Data Platform also affects the cluster capacity as it defines the number of copies of each block of data written. Disk drive manufacturers have adopted a size reporting methodology using calculation by powers of 10, also known as decimal prefix. As an example, a 120 GB disk is listed with a minimum of 120 x 10^9 bytes of usable addressable capacity, or 120 billion bytes. However, many operating systems and filesystems report their space based on standard computer binary exponentiation, or calculation by powers of 2, also called binary prefix. In this example, 2^10 or 1024 bytes make up a kilobyte, 2^10 kilobytes make up a megabyte, 2^10 megabytes make up a gigabyte, and 2^10 gigabytes make up a terabyte. As the values increase, the disparity between the two systems of measurement and notation get worse, at the terabyte level, the deviation between a decimal prefix value and a binary prefix value is nearly 10%.

The International System of Units (SI) defines values and decimal prefix by powers of 10 as follows: Table 8 SI Unit Values (Decimal Prefix). Value Symbol Name 1024 bytes KiB Kibibyte 1024 KiB MiB Mebibyte 1024 MiB GiB Gibibyte 1024 GiB TiB Tebibyte For the purpose of this document, the decimal prefix numbers are used only for raw disk capacity as listed by the respective manufacturers. For all calculations where raw or usable capacities are shown from the perspective of the HyperFlex software, filesystems or operating systems, the binary prefix numbers are used. This is done primarily to show a consistent set of values as seen by the end user from within the HyperFlex vCenter Web Plugin and HyperFlex Connect GUI when viewing cluster capacity, allocation and consumption, and also within most operating systems.

Table 10 lists a set of HyperFlex HX Data Platform cluster usable capacity values, using binary prefix, for an array of cluster configurations. These values are useful for determining the appropriate size of HX cluster to initially purchase, and how much capacity can be gained by adding capacity disks. The calculations for these values are listed in. The HyperFlex tool to help with sizing is listed in. Note: HyperFlex converged nodes configured with the Cisco VIC 1227 are not allowed to connect to the Cisco UCS 6332 or 6332-16UP model Fabric Interconnects. Using breakout ports for HyperFlex converged nodes is not allowed. In addition, HyperFlex converged nodes configured with the Cisco VIC 1227 are not allowed to connect to the 6332-16UP model Fabric Interconnect via the on-board 10 GbE unified ports.

HyperFlex extended clusters also incorporate 1-16 Cisco UCS blade servers for additional compute capacity. The blade chassis comes populated with 1-4 power supplies, and 8 modular cooling fans. In the rear of the chassis are two bays for installation of Cisco Fabric Extenders. The Fabric Extenders (also commonly called IO Modules, or IOMs) connect the chassis to the Fabric Interconnects. Internally, the Fabric Extenders connect to the Cisco VIC card installed in each blade server across the chassis backplane. The standard connection practice is to connect 1-8 10 GbE links, or 1-4 40 GbE links (depending on the IOMs and FIs purchased) from the left-side IOM, or IOM 1, to FI A, and to connect the same number of 10 GbE or 40 GbE links from the right-side IOM, or IOM 2, to FI B (Figure 18).

All other cabling configurations are invalid, and can lead to errors, discovery failures, and loss of redundant connectivity. HyperFlex extended clusters also incorporate 1-16 Cisco UCS rack-mount servers for additional compute capacity. The C-Series rack mount servers are connected directly to the Cisco UCS Fabric Interconnects in Direct Connect mode.

Internally the Cisco UCS C-Series servers are configured with the Cisco VIC 1227 or Cisco VIC 1387 network interface card (NIC) installed in a modular LAN on motherboard (MLOM) slot, which has dual 10 Gigabit Ethernet (GbE) ports or 40 Gigabit Ethernet (GbE) ports. The standard and redundant connection practice is to connect port 1 of the VIC card to a port on FI A, and port 2 of the VIC card to a port on FI B. Failure to follow this cabling practice can lead to errors, discovery failures, and loss of redundant connectivity. Figure 19 Cisco UCS C-Series Server Connectivity The Cisco HyperFlex system has communication pathways that fall into four defined zones (Figure 20): Management Zone: This zone comprises the connections needed to manage the physical hardware, the hypervisor hosts, and the storage platform controller virtual machines (SCVM).

These interfaces and IP addresses need to be available to all staff who will administer the HX system, throughout the LAN/WAN. This zone must provide access to Domain Name System (DNS) and Network Time Protocol (NTP) services, and allow Secure Shell (SSH) communication. In this zone are multiple physical and virtual components: - Fabric Interconnect management ports. - Cisco UCS external management interfaces used by the servers and blades, which answer via the FI management ports. - ESXi host management interfaces.

- Storage Controller VM management interfaces. - A roaming HX cluster management interface. - Storage Controller VM replication interfaces. - A roaming HX cluster replication interface. VM Zone: This zone comprises the connections needed to service network IO to the guest VMs that will run inside the HyperFlex hyperconverged system. This zone typically contains multiple VLANs, that are trunked to the Cisco UCS Fabric Interconnects via the network uplinks, and tagged with 802.1Q VLAN IDs.

These interfaces and IP addresses need to be available to all staff and other computer endpoints which need to communicate with the guest VMs in the HX system, throughout the LAN/WAN. Storage Zone: This zone comprises the connections used by the Cisco HX Data Platform software, ESXi hosts, and the storage controller VMs to service the HX Distributed Data Filesystem. These interfaces and IP addresses need to be able to communicate with each other at all times for proper operation. During normal operation, this traffic all occurs within the Cisco UCS domain, however there are hardware failure scenarios where this traffic would need to traverse the network northbound of the Cisco UCS domain. For that reason, the VLAN used for HX storage traffic must be able to traverse the network uplinks from the Cisco UCS domain, reaching FI A from FI B, and vice-versa. This zone is primarily jumbo frame traffic therefore jumbo frames must be enabled on the Cisco UCS uplinks. In this zone are multiple components: - A VMkernel interface used for storage traffic on each ESXi host in the HX cluster.

- Storage Controller VM storage interfaces. - A roaming HX cluster storage interface. VMotion Zone: This zone comprises the connections used by the ESXi hosts to enable vMotion of the guest VMs from host to host. During normal operation, this traffic all occurs within the Cisco UCS domain, however there are hardware failure scenarios where this traffic would need to traverse the network northbound of the Cisco UCS domain.

For that reason, the VLAN used for HX vMotion traffic must be able to traverse the network uplinks from the Cisco UCS domain, reaching FI A from FI B, and vice-versa. Refer to the following figure for an illustration of the logical network design. Installation of the HyperFlex system is primarily done through a deployable HyperFlex installer virtual machine, available for download at cisco.com as an OVA file.

The installer VM performs most of the Cisco UCS configuration work, it can be leveraged to simplify the installation of ESXi on the HyperFlex hosts, and also performs significant portions of the ESXi configuration. Finally, the installer VM is used to install the HyperFlex HX Data Platform software and create the HyperFlex cluster. Because this simplified installation method has been developed by Cisco, this CVD will not give detailed manual steps for the configuration of all the elements that are handled by the installer. Instead, the elements configured will be described and documented in this section, and the subsequent sections will guide you through the manual steps needed for installation, and how to utilize the HyperFlex Installer for the remaining configuration steps. Cisco UCS network uplinks connect “northbound” from the pair of Cisco UCS Fabric Interconnects to the LAN in the customer datacenter. All Cisco UCS uplinks operate as trunks, carrying multiple 802.1Q VLAN IDs across the uplinks. The default Cisco UCS behavior is to assume that all VLAN IDs defined in the Cisco UCS configuration are eligible to be trunked across all available uplinks.

Cisco UCS Fabric Interconnects appear on the network as a collection of endpoints versus another network switch. Internally, the Fabric Interconnects do not participate in spanning-tree protocol (STP) domains, and the Fabric Interconnects cannot form a network loop, as they are not connected to each other with a layer 2 Ethernet link. All link up/down decisions via STP will be made by the upstream root bridges. Uplinks need to be connected and active from both Fabric Interconnects. For redundancy, multiple uplinks can be used on each FI, either as 802.3ad Link Aggregation Control Protocol (LACP) port-channels, or using individual links. For the best level of performance and redundancy, uplinks can be made as LACP port-channels to multiple upstream Cisco switches using the virtual port channel (vPC) feature.

Using vPC uplinks allows all uplinks to be active passing data, plus protects against any individual link failure, and the failure of an upstream switch. Other uplink configurations can be redundant, but spanning-tree protocol loop avoidance may disable links if vPC is not available. All uplink connectivity methods must allow for traffic to pass from one Fabric Interconnect to the other, or from fabric A to fabric B. There are scenarios where cable, port or link failures would require traffic that normally does not leave the Cisco UCS domain, to now be forced over the Cisco UCS uplinks. Additionally, this traffic flow pattern can be seen briefly during maintenance procedures, such as updating firmware on the Fabric Interconnects, which requires them to be rebooted. The following sections and figures detail several uplink connectivity options. Single Uplinks to Single Switch This connection design is susceptible to failures at several points; single uplink failures on either Fabric Interconnect can lead to connectivity losses or functional failures, and the failure of the single uplink switch will cause a complete connectivity outage.

Figure 21 Connectivity with Single Uplink to Single Switch Port Channels to Single Switch This connection design is now redundant against the loss of a single link, but remains susceptible to the failure of the single switch. Single Uplinks or Port Channels to Multiple Switches This connection design is redundant against the failure of an upstream switch, and redundant against a single link failure. In normal operation, STP is likely to block half of the links to avoid a loop across the two upstream switches.

The side effect of this is to reduce bandwidth between the Cisco UCS domain and the LAN. If any of the active links were to fail, STP would bring the previously blocked link online to provide access to that Fabric Interconnect via the other switch. It is not recommended to connect both links from a single FI to a single switch, as that configuration is susceptible to a single switch failure breaking connectivity from fabric A to fabric B. For enhanced redundancy, the single links in the figure below could also be port-channels. Figure 23 Connectivity with Multiple Uplink Switches vPC to Multiple Switches This recommended connection design relies on using Cisco switches that have the virtual port channel feature, such as Catalyst 6000 series switches running VSS, Cisco Nexus 5000 series, and Cisco Nexus 9000 series switches. Logically the two vPC enabled switches appear as one, and therefore spanning-tree protocol will not block any links. This configuration allows for all links to be active, achieving maximum bandwidth potential, and multiple redundancy at each level.

For the base HyperFlex system configuration, multiple VLANs need to be carried to the Cisco UCS domain from the upstream LAN, and these VLANs are also defined in the Cisco UCS configuration. The hx-storage-data VLAN must be a separate VLAN ID from the remaining VLANs.

The following table lists the VLANs created by the HyperFlex installer in Cisco UCS, and their functions: Table 11 VLANs. Note: A dedicated network or subnet for physical device management is often used in datacenters. In this scenario, the mgmt0 interfaces of the two Fabric Interconnects would be connected to that dedicated network or subnet.

This is a valid configuration for HyperFlex installations with the following caveat; wherever the HyperFlex installer is deployed it must have IP connectivity to the subnet of the mgmt0 interfaces of the Fabric Interconnects, and also have IP connectivity to the subnets used by the hx-inband-mgmt VLANs listed above. All HyperFlex storage traffic traversing the hx-storage-data VLAN and subnet is configured by default to use jumbo frames, or to be precise, all communication is configured to send IP packets with a Maximum Transmission Unit (MTU) size of 9000 bytes. In addition, the default MTU for the hx-vmotion VLAN is also set to use jumbo frames. Using a larger MTU value means that each IP packet sent carries a larger payload, therefore transmitting more data per packet, and consequently sending and receiving data faster. This requirement also means that the Cisco UCS uplinks must be configured to pass jumbo frames. Failure to configure the Cisco UCS uplink switches to allow jumbo frames can lead to service interruptions during some failure scenarios, including Cisco UCS firmware upgrades, or when a cable or port failure would cause storage traffic to traverse the northbound Cisco UCS uplink switches. This section about Cisco UCS design will describe the elements within Cisco UCS Manager that are configured by the Cisco HyperFlex installer.

Many of the configuration elements are fixed in nature, meanwhile the HyperFlex installer does allow for some items to be specified at the time of creation, for example VLAN names and IDs, external management IP pools and more. Where the elements can be manually set during the installation, those items will be noted in >brackets. During the HyperFlex installation a Cisco UCS Sub-Organization is created.

You must specify a unique Sub-Organization name for each cluster during the installation, for example “hx1hybrid”, or “hx2sed”. The sub-organization is created underneath the root level of the Cisco UCS hierarchy, and is used to contain all policies, pools, templates and service profiles used by HyperFlex. This arrangement allows for organizational control using Role-Based Access Control (RBAC) and administrative locales at a later time if desired. In this way, control can be granted to administrators of only the HyperFlex specific elements of the Cisco UCS domain, separate from control of root level elements or elements in other sub-organizations. QoS System Classes Specific Cisco UCS Quality of Service (QoS) system classes are defined for a Cisco HyperFlex system.

These classes define Class of Service (CoS) values that can be used by the uplink switches north of the Cisco UCS domain, plus which classes are active, along with whether packet drop is allowed, the relative weight of the different classes when there is contention, the maximum transmission unit (MTU) size, and if there is multicast optimization applied. QoS system classes are defined for the entire Cisco UCS domain, the classes that are enabled can later be used in QoS policies, which are then assigned to Cisco UCS vNICs. The following table and figure details the QoS System Class settings configured for HyperFlex. Policy Priority Burst Rate Host Control Used by vNIC Template: Platinum Platinum 10240 Line-rate None storage-data-a storage-data-b Gold Gold 10240 Line-rate None vm-network-a vm-network-b Silver Silver 10240 Line-rate None hv-mgmt-a hv-mgmt-b Bronze Bronze 10240 Line-rate None hv-vmotion-a hv-vmotion-b Best Effort Best Effort 10240 Line-rate None N/A Multicast Policy A Cisco UCS Multicast Policy is configured by the HyperFlex installer, which is referenced by the VLANs that are created. The policy allows for future flexibility if a specific multicast policy needs to be created and applied to other VLANs, that may be used by non-HyperFlex workloads in the Cisco UCS domain.

The following table and figure details the Multicast Policy configured for HyperFlex. Name IGMP Snooping State IGMP Snooping Querier State HyperFlex Enabled Disabled VLANs VLANs are created by the HyperFlex installer to support a base HyperFlex system, with a VLAN for vMotion, and a single or multiple VLANs defined for guest VM traffic. Names and IDs for the VLANs are defined in the Cisco UCS configuration page of the HyperFlex installer web interface. The VLANs listed in Cisco UCS must already be present on the upstream network, and the Cisco UCS FIs do not participate in VLAN Trunk Protocol (VTP).

The following table and figure details the VLANs configured for HyperFlex. Name ID Type Transport Native VLAN Sharing Multicast Policy >LAN Ether No None HyperFlex >LAN Ether No None HyperFlex >LAN Ether No None HyperFlex >LAN Ether No None HyperFlex >LAN Ether No None HyperFlex Figure 28 Cisco UCS VLANs Management IP Address Pool A Cisco UCS Management IP Address Pool must be populated with a block of IP addresses. These IP addresses are assigned to the Cisco Integrated Management Controller (CIMC) interface of the rack mount and blade servers that are managed in the Cisco UCS domain. The IP addresses are the communication endpoints for various functions, such as remote KVM, virtual media, Serial over LAN (SoL), and Intelligent Platform Management Interface (IPMI) for each rack mount or blade server.

Therefore, a minimum of one IP address per physical server in the domain must be provided. The IP addresses are considered to be an “out-of-band” address, meaning that the communication pathway uses the Fabric Interconnects’ mgmt0 ports, which answer ARP requests for the management addresses. Because of this arrangement, the IP addresses in this pool must be in the same IP subnet as the IP addresses assigned to the Fabric Interconnects’ mgmt0 ports. A new IP pool, named “hx-ext-mgmt” is created in the HyperFlex sub-organization, and populated with a block of IP addresses, a subnet mask, and a default gateway by the HyperFlex installer. The default IP pool named “ext-mgmt”, in the root organization is no longer used as of HyperFlex 2.5 for new installations.

Figure 29 Management IP Address Pool MAC Address Pools One of the core benefits of the Cisco UCS and Virtual Interface Card (VIC) technology is the assignment of the personality of the card via Cisco UCS Service Profiles. The number of virtual NIC (vNIC) interfaces, their VLAN associations, MAC addresses, QoS policies and more are all applied dynamically as part of the service profile association process. Media Access Control (MAC) addresses use 6 bytes of data as a unique address to identify the interface on the layer 2 network. All devices are assigned a unique MAC address, which is ultimately used for all data transmission and reception. The Cisco UCS and VIC technology picks a MAC address from a pool of addresses, and assigns it to each vNIC defined in the service profile when that service profile is created. Best practices mandate that MAC addresses used for Cisco UCS domains use 00:25:B5 as the first three bytes, which is one of the Organizationally Unique Identifiers (OUI) registered to Cisco Systems, Inc.

The fourth byte (e.g. 00:25:B5: xx) is specified during the HyperFlex installation. The fifth byte is set automatically by the HyperFlex installer, to correlate to the Cisco UCS fabric and the vNIC placement order. Finally, the last byte is incremented according to the number of MAC addresses created in the pool. To avoid overlaps, when you define the values in the HyperFlex installer you must ensure that the first four bytes of the MAC address pools are unique for each HyperFlex cluster installed in the same layer 2 network, and also different from MAC address pools in other Cisco UCS domains which may exist. The following table details the MAC Address Pools configured for HyperFlex, and their default assignment to the vNIC templates created: Table 16 MAC Address Pools. Name CDP MAC Register Mode Action on Uplink Fail MAC Security Used by vNIC Template: HyperFlex-infra Enabled Only Native VLAN Link-down Forged: Allow hv-mgmt-a hv-mgmt-b hv-vmotion-a hv-vmotion-b storage-data-a storage-data-b HyperFlex-vm Enabled Only Native VLAN Link-down Forged: Allow vm-network-a vm-network-b vNIC Templates Cisco UCS Manager has a feature to configure vNIC templates, which can be used to simplify and speed up configuration efforts.

VNIC templates are referenced in service profiles and LAN connectivity policies, versus configuring the same vNICs individually in each service profile, or service profile template. VNIC templates contain all the configuration elements that make up a vNIC, including VLAN assignment, MAC address pool selection, fabric A or B assignment, fabric failover, MTU, QoS policy, Network Control Policy, and more. Templates are created as either initial templates, or updating templates. Updating templates retain a link between the parent template and the child object, therefore when changes are made to the template, the changes are propagated to all remaining linked child objects. An additional feature named “vNIC Redundancy” allows vNICs to be configured in pairs, so that the settings of one vNIC template, designated as a primary template, will automatically be applied to a configured secondary template.

For all HyperFlex vNIC templates, the “A” side vNIC template is configured as a primary template, and the related “B” side vNIC template is a secondary. In each case, the only configuration difference between the two templates is which fabric they are configured to connect through.

The following tables detail the initial settings in each of the vNIC templates created by the HyperFlex installer. VNIC Template Name: vm-network-b Setting Value Fabric ID B Fabric Failover Disabled Target Adapter Type Updating Template MTU 1500 MAC Pool vm-network-b QoS Policy gold Network Control Policy HyperFlex-vm VLANs >Native: no LAN Connectivity Policies Cisco UCS Manager has a feature for LAN Connectivity Policies, which aggregates all of the vNICs or vNIC templates desired for a service profile configuration into a single policy definition. This simplifies configuration efforts by defining a collection of vNICs or vNIC templates once, and using that policy in the service profiles or service profile templates. The HyperFlex installer configures a LAN Connectivity Policy named HyperFlex, which contains all of the vNIC templates defined in the previous section, along with an Adapter Policy named HyperFlex, also configured by the HyperFlex installer. The following table details the LAN Connectivity Policy configured for HyperFlex. Policy Name Use vNIC Template vNIC Name vNIC Template Used: Adapter Policy HyperFlex Yes hv-mgmt-a hv-mgmt-a HyperFlex hv-mgmt-b hv-mgmt-b hv-vmotion-a hv-vmotion-a hv-vmotion-b hv-vmotion-b storage-data-a storage-data-a storage-data-b storage-data-b vm-network-a vm-network-a vm-network-b vm-network-b Adapter Policies Cisco UCS Adapter Policies are used to configure various settings of the Converged Network Adapter (CNA) installed in the Cisco UCS blade or rack mount servers.

Various advanced hardware features can be enabled or disabled depending on the software or operating system being used. The following figures detail the Adapter Policy configured for HyperFlex: Figure 32 Cisco UCS Adapter Policy Resources BIOS Policies Cisco HX-Series servers have a set of pre-defined BIOS setting defaults defined in Cisco UCS Manager.

These settings have been optimized for the Cisco HX-Series servers running HyperFlex. The HyperFlex installer creates a BIOS policy named “HyperFlex”, with all settings set to the defaults, except for enabling the Serial Port A for Serial over LAN (SoL) functionality. This policy allows for future flexibility in case situations arise where the settings need to be modified from the default configuration. Boot Policies Cisco UCS Boot Policies define the boot devices used by blade and rack mount servers, and the order that they are attempted to boot from.

Cisco HX-Series rack mount servers have their VMware ESXi hypervisors installed to an internal pair of mirrored Cisco FlexFlash SD cards, therefore they require a boot policy defining that the servers should boot from that location. The HyperFlex installer configures a boot policy named “HyperFlex” specifying boot from the SD cards, which is used by the HyperFlex converged nodes, and should not be modified. The compute-only Cisco UCS blade servers and Cisco UCS rack mount servers can also boot from SD cards, or they can be configured to boot from local disks, boot from SAN, or via the network using PXE or iSCSI.

The HyperFlex installer configures a boot policy named “hx-compute”, which can be modified as needed for the boot method used by the compute-only nodes. The following figure details the HyperFlex Boot Policy configured to boot from SD card: Host Firmware Packages Cisco UCS Host Firmware Packages represent one of the most powerful features of the Cisco UCS platform; the ability to control the firmware revision of all the managed blades and rack mount servers via a policy specified in the service profile. Host Firmware Packages are defined and referenced in the service profiles.

Once a service profile is associated to a server, the firmware of all the components defined in the Host Firmware Package are automatically upgraded or downgraded to match the package. The HyperFlex installer creates a Host Firmware Package named “HyperFlex” which uses the simple package definition method, applying firmware revisions to all components that matches a specific Cisco UCS firmware bundle, versus defining the firmware revisions part by part. The following figure details the Host Firmware Package configured by the HyperFlex installer: Figure 35 Cisco UCS Host Firmware Package Local Disk Configuration Policies Cisco UCS Local Disk Configuration Policies are used to define the configuration of disks installed locally within each blade or rack mount server, most often to configure Redundant Array of Independent/Inexpensive Disks (RAID levels) when multiple disks are present for data protection. Since HX-Series converged nodes providing storage resources do not require RAID, the HyperFlex installer creates two Local Disk Configuration Policies, named “HyperFlex” and “hx-compute”, both of which allows any local disk configuration.

The policy also enables settings for the embedded FlexFlash SD cards used to boot the VMware ESXi hypervisor. The policy named “HyperFlex” is used by the service profile template named “hx-nodes”, which is for the HyperFlex converged servers, and should not be modified. Meanwhile, the policy named “hx-compute” is used by the service profile template named “compute-nodes”, which is used by compute-only nodes. The “hx-compute” policy can be modified as needed to suit the local disk configuration that will be used in compute-only nodes. The following figure details the Local Disk Configuration Policy configured by the HyperFlex installer: Maintenance Policies Cisco UCS Maintenance Policies define the behavior of the attached blades and rack mount servers when changes are made to the associated service profiles. The default Cisco UCS Maintenance Policy setting is “Immediate” meaning that any change to a service profile that requires a reboot of the physical server will result in an immediate reboot of that server. The Cisco best practice is to use a Maintenance Policy set to “user-ack”, which requires a secondary acknowledgement by a user with the appropriate rights within Cisco UCS Manager, before the server is rebooted to apply the changes.

The HyperFlex installer creates a Maintenance Policy named “HyperFlex” with the setting changed to “user-ack”. In addition, the On Next Boot setting is enabled, which will automatically apply changes the next time the server is rebooted, without any secondary acknowledgement. The following figure details the Maintenance Policy configured by the HyperFlex installer: Power Control Policies Cisco UCS Power Control Policies allow administrators to set priority values for power application to servers in environments where power supply may be limited, during times when the servers demand more power than is available. The HyperFlex installer creates a Power Control Policy named “HyperFlex” with all power capping disabled, and fans allowed to run at full speed when necessary. The following figure details the Power Control Policy configured by the HyperFlex installer: Figure 38 Cisco UCS Power Control Policy Scrub Policies Cisco UCS Scrub Policies are used to scrub, or erase data from local disks, BIOS settings and FlexFlash SD cards.

If the policy settings are enabled, the information is wiped when the service profile using the policy is disassociated from the server. The HyperFlex installer creates a Scrub Policy named “HyperFlex” which has all settings disabled, therefore all data on local disks, SD cards and BIOS settings will be preserved if a service profile is disassociated. The following figure details the Scrub Policy configured by the HyperFlex installer: Figure 39 Cisco UCS Scrub Policy Serial over LAN Policies Cisco UCS Serial over LAN (SoL) Policies enable console output which is sent to the serial port of the server, to be accessible via the LAN.

For many Linux based operating systems, such as VMware ESXi, the local serial port can be configured as a local console, where users can watch the system boot, and communicate with the system command prompt interactively. Since many blade servers do not have physical serial ports, and often administrators are working remotely, the ability to send and receive that traffic via the LAN is very helpful. Connections to a SoL session can be initiated from Cisco UCS Manager. The HyperFlex installer creates a SoL named “HyperFlex” to enable SoL sessions, and uses this feature to configure the ESXi hosts’ management networking configuration.

The following figure details the SoL Policy configured by the HyperFlex installer: vMedia Policies Cisco UCS Virtual Media (vMedia) Policies automate the connection of virtual media files to the remote KVM session of the Cisco UCS blades and rack mount servers. Using a vMedia policy can speed up installation time by automatically attaching an installation ISO file to the server, without having to manually launch the remote KVM console and connect them one-by-one. The HyperFlex installer creates a vMedia Policy named “HyperFlex” for future use, with no media locations defined.

Cisco UCS Manager has a feature to configure service profile templates, which can be used to simplify and speed up configuration efforts when the same configuration needs to be applied to multiple servers. Service profile templates are used to spawn multiple service profile copies to associate with a group of servers, versus configuring the same service profile manually each time it is needed.

Service profile templates contain all the configuration elements that make up a service profile, including vNICs, vHBAs, local disk configurations, boot policies, host firmware packages, BIOS policies and more. Templates are created as either initial templates, or updating templates. Updating templates retain a link between the parent template and the child object, therefore when changes are made to the template, the changes are propagated to all remaining linked child objects. The HyperFlex installer creates two service profile templates, named “hx-nodes” and “compute-nodes”, each with nearly the same configuration, except for the local disk configuration and boot policies. This simplifies future efforts if the configuration of the compute only nodes needs to differ from the configuration of the HyperFlex converged storage nodes.

The following tables detail the service profile templates configured by the HyperFlex installer: Table 27 Cisco UCS Service Profile Template Settings and Values. Note: ESXi VMDirectPath relies on a fixed PCI address for the passthrough devices.

If the configuration is changed by adding or removing vNICs or vHBAs, then the order of the devices seen in the PCI tree will change. The ESXi hosts will subsequently need to reboot one additional time in order to repair the configuration, which they will do automatically. The following sections detail the design of the elements within the VMware ESXi hypervisors, system requirements, virtual networking and the configuration of ESXi for the Cisco HyperFlex HX Distributed Data Platform. The Cisco HyperFlex system has a pre-defined virtual network design at the ESXi hypervisor level.

Four different virtual switches are created by the HyperFlex installer, each using two uplinks, which are each serviced by a vNIC defined in the Cisco UCS service profile. The vSwitches created are: vswitch-hx-inband-mgmt: This is the default vSwitch0 which is renamed by the ESXi kickstart file as part of the automated installation. The default VMkernel port, vmk0, is configured in the standard Management Network port group.

The switch has two uplinks, active on fabric A and standby on fabric B, without jumbo frames. A second port group is created for the Storage Platform Controller VMs to connect to with their individual management interfaces. A third port group is created for cluster to cluster VM snapshot replication traffic. The VLANs are not Native VLANs as assigned to the vNIC templates, and therefore they are defined in ESXi/vSphere. Vswitch-hx-storage-data: This vSwitch is created as part of the automated installation. A VMkernel port, vmk1, is configured in the Storage Hypervisor Data Network port group, which is the interface used for connectivity to the HX Datastores via NFS.

The switch has two uplinks, active on fabric B and standby on fabric A, with jumbo frames highly recommended. A second port group is created for the Storage Platform Controller VMs to connect to with their individual storage interfaces. The VLAN is not a Native VLAN as assigned to the vNIC templates, and therefore they are defined in ESXi/vSphere. Vswitch-hx-vm-network: This vSwitch is created as part of the automated installation. The switch has two uplinks, active on both fabrics A and B, and without jumbo frames. The VLANs are not Native VLANs as assigned to the vNIC templates, and therefore they are defined in ESXi/vSphere. Vmotion: This vSwitch is created as part of the automated installation.

The switch has two uplinks, active on fabric A and standby on fabric B, with jumbo frames highly recommended. The IP addresses of the VMkernel ports (vmk2) are configured during the post_install script execution.

The VLAN is not a Native VLAN as assigned to the vNIC templates, and therefore they are defined in ESXi/vSphere. The following table and figures help give more details into the ESXi virtual networking design as built by the HyperFlex installer by default. Note: The HyperFlex compute-only Cisco UCS server blades or rack-mount servers also place a lightweight storage controller VM on a 3.5 GB VMFS datastore, which can be provisioned from the SD cards, or placed on a VMFS partition alongside the boot volume if booting from SAN or local disk.

HyperFlex Datastores The new HyperFlex cluster has no default datastores configured for virtual machine storage, therefore the datastores must be created using the vCenter Web Client plugin or the HyperFlex Connect GUI. It is important to recognize that all HyperFlex datastores are thinly provisioned, meaning that their configured size can far exceed the actual space available in the HyperFlex cluster. Alerts will be raised by the HyperFlex system in HyperFlex Connect or the vCenter plugin when actual space consumption results in low amounts of free space, and alerts will be sent via auto support email alerts. Overall space consumption in the HyperFlex clustered filesystem is optimized by the default deduplication and compression features. CPU Resource Reservations Since the storage controller VMs provide critical functionality of the Cisco HX Distributed Data Platform, the HyperFlex installer will configure CPU resource reservations for the controller VMs.

This reservation guarantees that the controller VMs will have CPU resources at a minimum level, in situations where the physical CPU resources of the ESXi hypervisor host are being heavily consumed by the guest VMs. This is a soft guarantee, meaning in most situations the SCVMs are not using all of the CPU resources reserved, therefore allowing the guest VMs to use them.

The following table details the CPU resource reservation of the storage controller VMs. Number of vCPU Shares Reservation Limit 8 Low 10800 MHz unlimited Memory Resource Reservations Since the storage controller VMs provide critical functionality of the Cisco HX Distributed Data Platform, the HyperFlex installer will configure memory resource reservations for the controller VMs. This reservation guarantees that the controller VMs will have memory resources at a minimum level, in situations where the physical memory resources of the ESXi hypervisor host are being heavily consumed by the guest VMs. The following table details the memory resource reservation of the storage controller VMs.

Cisco HyperFlex systems are ordered with a factory pre-installation process having been done prior to the hardware delivery. This factory integration work will deliver the HyperFlex servers with the proper firmware revisions pre-set, a copy of the VMware ESXi hypervisor software pre-installed, and some components of the Cisco HyperFlex software already installed.

Once on site, the final steps to be performed are reduced and simplified due to the previous factory work. For the purpose of this document, the setup process is described as though this factory pre-installation work was done, thereby leveraging the tools and processes developed by Cisco to simplify the process and dramatically reduce the deployment time. Installation of the Cisco HyperFlex system is primarily done via a deployable HyperFlex installer virtual machine, available for download at cisco.com as an OVA file.

The installer VM performs the Cisco UCS configuration work, the configuration of ESXi on the HyperFlex hosts, the installation of the HyperFlex HX Data Platform software and creation of the HyperFlex cluster. Because this simplified installation method has been developed by Cisco, this CVD will not give detailed manual steps for the configuration of all the elements that are handled by the installer. The following sections will guide you through the prerequisites and manual steps needed prior to using the HyperFlex installer, how to utilize the HyperFlex Installer, and finally how to perform the remaining post-installation tasks.

Prior to beginning the installation activities, it is important to gather the following information: To install the HX Data Platform, an OVF installer appliance must be deployed on a separate virtualization host, which is not a member of the HyperFlex cluster. The HyperFlex installer requires one IP address on the management network and the HX installer appliance IP address must be able to communicate with Cisco UCS Manager, ESXi management IP addresses on the HX hosts, and the vCenter IP addresses where the HyperFlex cluster will be managed. Additional IP addresses for the Cisco HyperFlex system need to be allocated from the appropriate subnets and VLANs to be used. IP addresses that are used by the system fall into the following groups: Cisco UCS Manager: These addresses are used and assigned by Cisco UCS manager.

Three IP addresses are used by Cisco UCS Manager; one address is assigned to each Cisco UCS Fabric Interconnect, and the third IP address is a roaming address for management of the Cisco UCS cluster. In addition, at least one IP address per Cisco UCS blade or HX-series rack mount server is required for the hx-ext-mgmt IP address pool, which are assigned to the CIMC interface of the physical servers. Since these management addresses are assigned from a pool, they need to be provided in a contiguous block of addresses. These addresses must all be in the same subnet. HyperFlex and ESXi Management: These addresses are used to manage the ESXi hypervisor hosts, and the HyperFlex Storage Platform Controller VMs. Two IP addresses per node in the HyperFlex cluster are required from the same subnet, and a single additional IP address is needed as the roaming HyperFlex cluster management interface. These addresses can be assigned from the same subnet at the Cisco UCS Manager addresses, or they may be separate.

HyperFlex Replication: These addresses are used by the HyperFlex Storage Platform Controller VMs for clusters that are configured to replicate VMs to one another. One IP address per HX node is required, plus one additional IP address as a roaming clustered replication interface. These addresses are assigned to a pool as part of a post-installation activity described later in this document, and are not needed to complete the initial installation of a HyperFlex cluster. These addresses can be from the same subnet as the HyperFlex and ESXi management addresses, but it is recommended that the VLAN ID and subnet be unique.

HyperFlex Storage: These addresses are used by the HyperFlex Storage Platform Controller VMs, and as VMkernel interfaces on the ESXi hypervisor hosts, for sending and receiving data to/from the HX Distributed Data Platform Filesystem. Two IP addresses per node in the HyperFlex cluster are required from the same subnet, and a single additional IP address is needed as the roaming HyperFlex cluster storage interface. It is recommended to provision a subnet that is not used in the network for other purposes, and it is also possible to use non-routable IP address ranges for these interfaces.

Finally, if the Cisco UCS domain is going to contain multiple HyperFlex clusters, it is recommended to use a different subnet and VLAN ID for the HyperFlex storage traffic for each cluster. This is a safer method, guaranteeing that storage traffic from multiple clusters cannot intermix. VMotion: These IP addresses are used by the ESXi hypervisor hosts as VMkernel interfaces to enable vMotion capabilities. One or more IP addresses per node in the HyperFlex cluster are required from the same subnet.

Multiple addresses and VMkernel interfaces can be used if you wish to enable multi-nic vMotion, although this configuration would require additional manual steps. The following tables will assist with gathering the required IP addresses for the installation of an 8 node standard HyperFlex cluster, or a 4+4 extended cluster, by listing the addresses required, and an example configuration. Address Group: UCS Management HyperFlex and ESXi Management HyperFlex Storage VMotion VLAN ID: Subnet: Subnet Mask: Gateway: Device UCS Management Addresses ESXi Management Interface Storage Controller Management Interface Storage Controller Replication Network ESXi Hypervisor Storage VMkernel Interface Storage Controller Storage Interface VMotion VMkernel Interface Fabric Interconnect A Fabric Interconnect B UCS Manager HyperFlex Cluster HyperFlex Node #1 HyperFlex Node #2 HyperFlex Node #3 HyperFlex Node #4 HyperFlex Node #5 HyperFlex Node #6 HyperFlex Node #7 HyperFlex Node #8. Note: The Cisco UCS Management, and HyperFlex and ESXi Management IP addresses can come from the same subnet, or be separate, as long as the HyperFlex installer can reach them both.

By default, the HX installation will assign a static IP address to the management interface of the ESXi servers. Using Dynamic Host Configuration Protocol (DHCP) for automatic IP address assignment in not recommended.

DNS servers are highly recommended to be configured for querying Fully Qualified Domain Names (FQDN) in the HyperFlex and ESXi Management group. DNS records need to be created prior to beginning the installation. At a minimum, it is highly recommended to create A records and reverse PTR records for the ESXi hypervisor hosts’ management interfaces. Additional A records can be created for the Storage Controller Management interfaces, ESXi Hypervisor Storage interfaces, and the Storage Controller Storage interfaces if desired. The following tables will assist with gathering the required DNS information for the installation, by listing the information required, and an example configuration. Item Value NTP Server #1 171.68.38.65 NTP Server #2 171.68.38.66 Timezone (UTC-8:00) Pacific Time Prior to the installation, the required VLAN IDs need to be documented, and created in the upstream network if necessary.

At a minimum, there are 4 VLANs that need to be trunked to the Cisco UCS Fabric Interconnects that comprise the HyperFlex system; a VLAN for the HyperFlex and ESXi Management group, a VLAN for the HyperFlex Storage group, a VLAN for the VMotion group, and at least one VLAN for the guest VM traffic. If HyperFlex Replication is to be used, another VLAN must be created and trunked for the replication traffic. The VLAN IDs must be supplied during the HyperFlex Cisco UCS configuration step, and the VLAN names can optionally be customized.

The following tables will assist with gathering the required VLAN information for the installation by listing the information required, and an example configuration. Name ID hx-inband-mgmt 133 hx-inband-repl 150 hx-storage-data 51 vm-network 100 hx-vmotion 200 The Cisco UCS uplink connectivity design needs to be finalized prior to beginning the installation. One of the early manual tasks to be completed is to configure the Cisco UCS network uplinks and verify their operation, prior to beginning the HyperFlex installation steps.

Refer to the network uplink design possibilities in the Network Design section. The following tables will assist with gathering the required network uplink information for the installation by listing the information required, and an example configuration. Account Username Password HX Installer Administrator root Cisco123 UCS Administrator admin Cisco123 ESXi Administrator root Cisco123 HyperFlex Administrator root Cisco123!! VCenter Administrator administrator@vsphere.local!QAZ2wsx Install the Fabric Interconnects, the HX-Series rack mount servers, standard C-series rack mount servers, the Cisco UCS 5108 chassis, the Cisco UCS Fabric Extenders, and the Cisco UCS blades according to their corresponding hardware installation guides: Cisco UCS 6200 Series Fabric Interconnect: Cisco UCS 6300 Series Fabric Interconnect: HX220c M4 Server: HX240c M4 Server: Cisco UCS 5108 Chassis, Servers and Fabric Extenders: The physical layout of the HyperFlex system was previously described in section. The Fabric Interconnects, HX-series rack mount servers, Cisco UCS chassis and blades need to be cabled properly before beginning the installation activities. The following table provides an example cabling map for installation of a Cisco HyperFlex system, with eight HX220c-M4SX servers, and one Cisco UCS 5108 chassis.

Setting Value IP Address Subnet Mask Default Gateway DNS Server #1 NTP Servers To deploy the HyperFlex installer OVA, complete the following steps: 1. Open the vSphere Web Client webpage of a vCenter server where the installer OVA will be deployed, and log in with admin privileges. In the vSphere Web Client, from the Home view, click Hosts and Clusters. From the Actions menu, click Deploy OVF Template. Click the Local file option, then click Browse and locate the Cisco-HX-Data-Platform-Installer-v2.5.1b-26284.ova file, click the file and click Open.

Modify the name of the virtual machine to be created if desired, and click a folder location to place the virtual machine, then click Next. Click a specific host or cluster to locate the virtual machine and click Next. After the file validation, review the details and click Next. Select a Thin provision virtual disk format, and the datastore to store the new virtual machine, then click Next.

Modify the network port group selection from the drop-down list in the Destination Networks column, choosing the network the installer VM will communicate on, and click Next. If DHCP is to be used for the installer VM, leave the fields blank, except for the NTP server value and click Next. If static address settings are to be used, fill in the fields for the DNS server, Default Gateway, NTP Servers, IP address, and subnet mask, then click Next. Review the final configuration and click Finish. The installer VM will take a few minutes to deploy, once it has deployed, power on the new VM and proceed to the next step.

HyperFlex Installer Web Page The HyperFlex installer is accessed via a webpage using your local computer and a web browser. If the HyperFlex installer was deployed with a static IP address, then the IP address of the website is already known. If DHCP was used, open the local console of the installer VM.

In the console, you will see an interface similar to the example below, showing the IP address that was leased: Figure 46 HyperFlex Installer VM IP Address To access the HyperFlex installer webpage, complete the following steps: 1. Open a web browser on the local computer and navigate to the IP address of the installer VM. For example, open 2.

Click accept or continue to bypass any SSL certificate errors. At the login screen, enter the username: root 4. At the login screen, enter the default password: Cisco123 5. Verify the version of the installer in the lower right-hand corner of the Welcome page is the correct version. Check the box for “I accept the terms and conditions”, and click Login. The HX installer will guide you through the process of setting up your cluster.

It will configure Cisco UCS policies, templates, service profiles, and settings, as well as assigning IP addresses to the HX servers that come from the factory with ESXi hypervisor software preinstalled. The installer will load the HyperFlex controller VMs and software on the nodes, add the nodes to the vCenter cluster, then finally create the HyperFlex cluster and distributed filesystem. All of these processes can be completed via a single workflow from the HyperFlex Installer webpage. To install and configure a HyperFlex cluster, complete the following steps: 1. On the HyperFlex installer webpage select the workflow named “Cluster Creation with HyperFlex (FI)”. Enter the Cisco UCS Manager and vCenter DNS hostname or IP address, the admin usernames, and the passwords.

The default Hypervisor credential which comes installed from the factory is username: root with a password of “Cisco123” and these values are already entered in the installer. You can select the option to see the passwords in clear text. Optionally, you can import a JSON file that has the configuration information, except for the appropriate passwords. Click Continue. Select the Unassociated HX server models that are to be used in the new HX cluster and click Continue. If the Fabric Interconnect server ports were not enabled in the earlier step, you have the option to enable them here to begin the discovery process by clicking the Configure Server Ports link.

Note: The server discovery can take several minutes to complete, and it will be necessary to periodically click the Refresh button to see the unassociated servers appear once discovery is completed. Enter the VLAN names and VLAN IDs that are to be created in Cisco UCS, as well as the MAC Pool prefix, (Only enter the 4 th byte value, for example: 00:25:B5: ED). Multiple comma-separated VLAN IDs for different guest VM networks are allowed here.

Enter the IP address range to be used by the CIMC interfaces of the servers in this HX cluster. Enter a unique Org name for the HyperFlex Cluster.

Important: (Optional) If you need to add extra iSCSI vNICs and/or FC vHBAs to connect the HX nodes to an external iSCSI or FC array, enable iSCSI Storage and/or FC Storage here using the procedure described in the following section:. Click Continue. Enter the subnet mask, gateway, DNS, and IP addresses and hostnames for the Hypervisors. The IP addresses will be assigned via Serial over Lan (SoL) through Cisco UCS Manager to the ESXi host systems as their management IP addresses. Click Continue.

Assign the additional IP addresses for the Management and Data networks as well as the cluster IP addresses, then click Continue. Note: A default gateway is not required for the data network, as those interfaces normally will not communicate with any other hosts or networks, and the subnet can be non-routable. Enter the HX Cluster Name and Replication Factor setting. Enter the Password that will be assigned to the Controller VMs. Enter the Datacenter Name from vCenter, and vCenter Cluster Name. Enter the System Services information for DNS, NTP, and Time Zone. Enable Auto Support and enter the email address to receive Auto Support alerts, then scroll down.

Leave the defaults for Advanced Networking. Under Advanced Settings, validate that VDI is not checked (hybrid nodes only). Jumbo Frames should be enabled.

It is not necessary to select Clean up disk partitions for a new cluster installation. Validation of the configuration will now start. If there are warnings, you can review them and click “Skip Validation” if the warnings are acceptable. If there are no warnings, the installer will automatically continue on to the configuration process. Note: The initial validation will always fail when using Cisco UCS 6332 or 6332-16UP model Fabric Interconnects. This is due to the fact that changes to the QoS system classes require these models to reboot. If the validation is skipped, the HyperFlex installer will continue the installation and automatically reboot both Fabric Interconnects sequentially.

If this is an initial setup of these Fabric Interconnects, and no other systems are running on them yet, then it is safe to proceed. However, if these Fabric Interconnects are already in use for other workloads, then caution must be taken to ensure that the sequential reboots of both Fabric Interconnects will not interrupt those workloads, and that the QoS changes will not cause traffic drops. Contact Cisco TAC for assistance if this situation applies. The HX installer will now proceed to complete the deployment and perform all the steps listed at the top of the screen along with their status. The process can also be monitored in Cisco UCS Manager and vCenter while the profiles and cluster are created. Review the summary screen after the install completes by selecting Summary on the top right of the window. You can also review the details of the installation process after the install completes by selecting Progress on the top left of the window.

After the install completes, you may export the cluster configuration by clicking on the downward arrow icon in the top right of the screen. Click OK to save the configuration to a JSON file. This file can be imported to save time if you need to rebuild the same cluster in the future, and be kept as a record of the configuration options and settings used during the installation. After the installation completes, you can click the Launch HyperFlex Connect button to immediately log in to the new HTML5 GUI. To automate the post installation procedures and verify the HyperFlex Installer has properly configured Cisco UCS Manager, a script has been provided on the HyperFlex Installer OVA. These steps can also be performed manually in vCenter if preferred. The following procedure will use the script.

SSH to the installer OVA IP as root with password Cisco123, # ssh root@10.29.133.115 2. From the CLI of the installer VM, run the script named post_install. The installer will already have the information from the just completed HX installation and it will be used by the script.

Enter the HX Storage Controller VM root password for the HX cluster (use the one entered during the HX Cluster installation), as well as the vCenter user name and password. You can also enter the vSphere license or complete this task later. Enter “y” to enable HA/DRS. Enter “y” to disable SSH warning. Add the vMotion VMkernel interfaces to each node by entering “y”.

Input the netmask, the vMotion VLAN ID, and the vMotion IP addresses for each of the hosts as prompted. A vMotion VMkernel Port is created for each host in vCenter: 7. The main installer will have already created at least one vm-network port group and assigned the default VM network VLAN input from the cluster installation. Enter “n” to skip this step and use the group(s) that were created. If desired, additional VM network port groups can be created and the additional VLANs will be added to the vm-networks vSwitch. This option will also create the corresponding VLANs in Cisco UCS Manager, and assign the VLAN to the vm-network vNIC-Template.

This script can be rerun at later time as well to create additional VM networks and Cisco UCS VLANs. Example: Using this option in the script to show how to add more VM networks: VLANs are created in Cisco UCS: VLANs are assigned to vNICs: Port groups are created: 8. Enter “n” to skip testing the auto support email function, because the email configuration has not been completed yet. The post install script will now check the networking configuration and jumbo frames. The script will complete and provide a summary screen. Validate there are no errors and the cluster is healthy.

It is recommended to enable a syslog destination for permanent storage of the ESXi host logs. It is possible to use the vCenter server as the log destination in this case. To configure syslog, complete the following steps: 1. Log on to the ESXi host via SSH as the root user.

Enter the following commands, replacing the IP address in the first command with the IP address of the vCenter server that will receive the syslog logs: [root@hx220-01:~] esxcli system syslog config set --loghost='udp://10.29.133.120' [root@hx220-01:~] esxcli system syslog reload [root@hx220-01:~] esxcli network firewall ruleset set -r syslog -e true [root@hx220-01:~] esxcli network firewall refresh 3. Repeat for each ESXi host. Create a datastore for storing the virtual machines. This task can be completed by using the vSphere Web Client HX plugin, or by using the HyperFlex Connect HTML management webpage. To configure a new datastore, complete the following steps: 1. Use a web browser to open the HX cluster IP management URL, for example: 2. Enter a local credential, or a vCenter RBAC credential for the username, and the corresponding password.

Click Datastores in the left pane, and click Create Datastore. In the popup, enter the Datastore Name and size.

For most applications, leave the Block Size at the default of 8K. Click Create Datastore.

Alternatively, to create the datastore using the vSphere web client, select vCenter Inventory Lists, and select the Cisco HyperFlex System, Cisco HX Data Platform, cluster-name, manage tab and the plus (+) icon to create a datastore. Create a test virtual machine stored on your new HX datastore in order to take a snapshot and perform a cloning operation. Take a snapshot of the new virtual machine via the vSphere Web Client prior to powering it on. This can be scheduled as well. In the vSphere web client, right-click the VM, select Cisco HX Data Platform, then select Snapshot Now. Input the snapshot name and click OK. Create a few clones of our virtual machine.

Right-click the VM, and select Cisco HX Data Platform, then ReadyClones. Input the Number of clones and Prefix, then click OK to start the operation.

The clones will be created in seconds. Auto-Support should be enabled for all clusters during the initial HyperFlex installation.

Auto-Support enables Call Home to automatically send support information to Cisco TAC, and notifications of tickets to the email address specified. If the settings need to be modified, they can be changed in the HyperFlex Connect HTML management webpage.

To change Auto-Support settings, complete the following steps: 1. From the HyperFlex Connect webpage, click the gear shaped icon in the upper right-hand corner, and click Auto-Support Settings. Enable or disable Auto-Support as needed. Enter the email address to receive alerts when Auto-Support events are generated. Enable or disable Remote Support as needed. Remote support allows Cisco TAC to connect to the HX cluster and accelerate troubleshooting efforts.

Enter in the information for a web proxy if needed. Email notifications which come directly from the HyperFlex cluster can also be enabled. To enable direct email notifications, complete the following steps: 1. From the HyperFlex Connect webpage, click the gear shaped icon in the upper right-hand corner, and click Notifications Settings. Enter the DNS name or IP address of the outgoing email server or relay, the email address the notifications will come from, and the recipients. It is recommended that the default ESXi root passwords be changed for enhanced security. To change the root password of the ESXi host, complete the following steps: 1.

Log into the ESXi host via SSH. If the logon account used was not root, gain root privileges via su (you must know the root account password): su – 3. Change the root password: passwd root 4. Enter the new password and press Enter. Enter the new password again to confirm, and press Enter. Repeat steps 1-5 for each ESXi host.

Optionally, you can change the HX controller password via the “stcli security password set” command. HyperFlex 2.5 introduces Smart Licensing, which communicates with a Cisco Smart Account to validate and check out HyperFlex licenses to the nodes, from the pool of available licenses in the account. At the beginning, Smart Licensing is enabled but the HX storage cluster is unregistered and in a 90-day evaluation period or EVAL MODE. For the HX storage cluster to start reporting license consumption, it must be registered with the Cisco Smart Software Manager (SSM) through a valid Cisco Smart Account. Before beginning, verify that you have a Cisco Smart account, and valid HyperFlex licenses are available to be checked out by your HX cluster. To create a Smart Account, see Cisco Software Central >Request a Smart Account. To activate and configure smart licensing, complete the following steps: 1.

Log into a controller VM. Confirm that your HX storage cluster is in Smart Licensing mode. # stcli license show status Smart Licensing is ENABLED Registration: Status: UNREGISTERED Export-Controlled Functionality: Not Allowed License Authorization: Status: EVAL MODE Evaluation Period Remaining: 79 days, 8 hr, 52 min, 57 sec Last Communication Attempt: NONE Feedback should show Smart Licensing is ENABLED, Status: UNREGISTERED, and the amount of time left during the 90-day evaluation period (in days, hours, minutes, and seconds).

Navigate to Cisco Software Central ( and log in to your Smart Account. From Cisco Smart Software Manager, generate a registration token. In the License pane, click Smart Software Licensing to open Cisco Smart Software Manager. Click Inventory.

From the virtual account where you want to register your HX storage cluster, click General, and then click New Token. In the Create Registration Token dialog box, add a short Description for the token, enter the number of days you want the token to be active and available to use on other products, and check Allow export-controlled functionality on the products registered with this token.

Click Create Token. From the New ID Token row, click the Actions drop-down list, and click Copy. Log into a controller VM. Register your HX storage cluster, where idtoken-string is the New ID Token from Cisco Smart Software Manager.

# stcli license register --idtoken idtoken-string 12. Confirm that your HX storage cluster is registered. # stcli license show summary The cluster is now ready. You may run any other preproduction tests that you wish to run at this point. Additional vHBAs or vNICs From HXDP version 1.8 onward, customers have the flexibility to leverage third-party storage infrastructure by connecting external storage arrays to HX systems.

As an example, one can map and connect Fibre Channel LUNs from an IBM VersaStack or NFS volumes from a NetApp FlexPod system, and then easily perform a Storage vMotion of virtual machines into the HyperFlex system. Figure 47 External Storage in HX In order to connect to other storage systems such as FlexPod via iSCSI or NFS, or an FC SAN, it is recommended that the additional vHBAs or vNICs be added during the creation of the HX cluster. If these are added post cluster creation, the PCI enumeration can change causing PCI passthrough device configuration errors. With HXDP 2.5 and onward, the system can repair these changes automatically via an additional reboot of the ESXi hosts. It is recommended that you do not make such hardware changes after the HX cluster is created. A better option is to add vHBAs or vNICs as necessary while the cluster is created. Both of these processes are documented below.

In this section only the addition of FC vHBAs or iSCSI vNICs to HX hosts is documented (A more detailed procedure about connecting other iSCSI or NFS storage to HX cluster is in the ). Note: Although in this CVD we use iSCSI as example to connect HX to external IP storage devices, the vNICs created by this procedure could be used for connecting to NFS storage devices. From HXDP 2.0 onward, the HX installer supports adding supplemental vHBAs or vNICs as a part of the cluster creation.

An overview of this procedure is as follows: 1. Open the HyperFlex Installer from a web browser, login as root user. On the HyperFlex Installer webpage select a Workflow of Cluster Creation to start a fresh cluster installation. Continue with appropriate inputs until you get to the page for Cisco UCS Manager configuration.

Click the >carat to expand iSCSI Storage configuration. Check the box Enable iSCSI Storage if you want to create additional vNICs to connect to the external iSCSI storage systems. Enter a VLAN name and ID for Fabric A and B dual connections. Click the >carat to expand FC Storage configuration. Check the box Enable FC Storage if you want to create Fibre Channel vHBAs to connect to the external FC or FCoE storage systems. Enter WWxN Pool prefix (For example: 20:00:00:25:B5: ED, only enter the last byte value), VSAN names and IDs for Fabric A and B dual connections.

Continue and complete the inputs for all the remaining cluster configuration tasks, start the cluster creation and wait for the completion. Note that you can choose to enable either only iSCSI, only FC, or both according to your needs. After the install is completed, the additional dual vHBAs and/or dual vNICs are created for the Service Profile Templates named “hx-nodes” and “compute-nodes”. For each HX node, dual vHBAs and/or dual iSCSI vNICs are created as well.

Note: In Cisco UCS Manager, the additional vNICs are configured as standard vNICs, not as iSCSI vNICs, as iSCSI vNICs are specifically used for iSCSI boot adapters. In vCenter, a standard vSwitch vswitch-hx-iscsi is created on each HX ESXi host.

Further configuration to create iSCSI VMkernel ports needs to be done manually for storage connections (see ). Should you decide to add additional storage such as a FlexPod after you have already installed your cluster, the following procedure can be used for adding vHBAs or vNICs that could cause PCI re-enumeration upon an ESXi host reboot.

Beginning with HXDP 2.5, the DirectPath I/O configuration will repair itself automatically via an additional reboot of the node. Therefore, it is recommended you do not reboot multiple nodes at once after making these hardware changes, as it could lead to a cluster failure. Validate the health state of each host, and the HX cluster before rebooting or performing the procedure on subsequent nodes. In this example, we will be adding vHBAs after an HX cluster is created via the Cisco UCS service profile template. We will reboot one ESXi node at a time in a rolling upgrade fashion so there will be no outage. To add vHBAs or iSCSI vNICs, complete the following steps: 1.

Example of hardware change: Add vHBAs to the Service Profile Templates for HX (refer to Cisco UCS documentation for your storage device such as a FlexPod CVD for configuring the vHBAs). After adding the vHBAs to the templates, the servers will be in a Pending Reboot state and require a reboot to add the new interface. Do NOT reboot the HX servers at this time. Using HyperFlex Connect, or the vSphere Web Client, place one of the HX ESXi hosts in HX-Maintenance Mode. After the host has entered Maintenance Mode, reboot the associated node to complete the addition of the new hardware. After the node has rebooted, the HXDP software will detect that the DirectPath I/O configuration has changed, and must be reconfigured. This will result in one additional automatic reboot of the node.

After the second reboot, exit the ESXi host from maintenance mode, the SCVM should start automatically without errors. Check the health status of the cluster, validating that the cluster is healthy before proceeding to reboot the next node. The cluster health status can be viewed from HyperFlex Connect, or via the CLI.

Example: Run these command to the cluster IP for the HX Controllers “stcli cluster refresh” then “stcli cluster info grep -i health” 8. Continue checking or refreshing until the HX cluster is healthy. Repeat the process for each node in the cluster as necessary.

HX nodes come from the factory with a copy of the ESXi hypervisor pre-installed, however there are scenarios where it may be necessary to redeploy or reinstall ESXi on an HX node. In addition, this process can be used to deploy ESXi on rack mount or blade servers that will function as HX compute-only nodes. The HyperFlex system requires a Cisco custom ESXi ISO file to be used, which has Cisco hardware specific drivers pre-installed, and customized settings configured to ease the installation process. The Cisco custom ESXi ISO file is available to download at cisco.com.

The HX custom ISO is based on the Cisco custom ESXi 6.5 Patch 1a ISO release with the filename: HX-Vmware-ESXi-6-Cisco-Custom-6.5.0.3.iso and is available on the Cisco web site: The custom Cisco HyperFlex ESXi ISO will automatically perform the following tasks with no user interaction required: Accept the End User License Agreement. Configure the root password to: Cisco123 Install ESXi to the internal mirrored Cisco FlexFlash SD cards. Set the default management network to use vmnic0, and obtain an IP address via DHCP. Enable SSH access to the ESXi host. Enable the ESXi shell.

Enable serial port com1 console access to facilitate Serial over LAN access to the host. Configure the ESXi configuration to always use the current hardware MAC address of the network interfaces, even if they change. Rename the default vSwitch to vswitch-hx-inband-mgmt. A high-level example of a HX rebuild procedure would be: 1. Clean up the existing environment by: - Deleting existing HX virtual machines and HX datastores. - Removing the HX cluster in vCenter.

- Removing vCenter MOB entries for the HX extension. - Deleting HX sub-organization and HX VLANs in Cisco UCS Manager. Run HX installer, use the customized version of the installation workflow by selecting the “I know what I am doing” link.

Use customized workflow and only choose the “Run UCS Manager Configuration” option, click Continue. When the Cisco UCS Manager configuration is complete, HX hosts are associated with HX service profiles and powered on. Now perform a fresh ESXi installation using the custom ISO image and following the steps in section Cisco UCS vMedia and Boot Policies. When the ESXi fresh installations are all finished, use the customized workflow and select the remaining 3 options; ESXi Configuration, Deploy HX Software, and Create HX Cluster, to continue and complete the HyperFlex cluster installation. More information on the various installation methods can be found in the.

By using a Cisco UCS vMedia policy, the custom Cisco HyperFlex ESXi installation ISO file can be mounted to all of the HX servers automatically. The existing vMedia policy, named “HyperFlex” must be modified to mount this file, and the boot policy must be modified temporarily to boot from the remotely mounted vMedia file. Once these two tasks are completed, the servers can be rebooted, and they will automatically boot from the remotely mounted vMedia file, installing and configuring ESXi on the servers. WARNING: While vMedia policies are very efficient for installing multiple servers, using vMedia policies as described could lead to an accidental reinstall of ESXi on any existing server that is rebooted with this policy.

Please be certain that the servers being rebooted while the policy is in effect are the servers you wish to reinstall. Even though the custom ISO will not continue without a secondary confirmation, extreme caution is recommended. This procedure needs to be carefully monitored and the boot policy should be changed back to original settings immediately after the intended servers are rebooted, and the ESXi installation begins. Using this policy is only recommended for new installs or rebuilds.

Alternatively, you can manually select the boot device using the KVM console during boot, and pressing F6, instead of making the vMedia device the default boot selection. To configure the Cisco UCS vMedia and Boot Policies, complete the following steps: 1. Copy the HX-Vmware-ESXi-6-Cisco-Custom-6.5.0.3.iso file to the HX Installer VM via SCP or SFTP, placing it in the folder /var/www/localhost/images/. In Cisco UCS Manager, click the Servers button on the left-hand side of the screen. Expand Servers >Policies >root >Sub-Organizations >>>vMedia Policies, and click vMedia Policy HyperFlex.

In the configuration pane, click Create vMedia Mount. Enter a name for the mount, for example: ESXi. Select the CDD option. Select HTTP as the protocol.

Enter the IP address of the HyperFlex installer VM, for example: 10.29.133.115 9. Select None as the Image Variable Name. Enter HX-Vmware-ESXi-6-Cisco-Custom-6.5.0.3.iso as the Remote File. Enter /images/ as the Remote Path. Select Servers >Service Profile Templates >root >Sub-Organizations >>>Service Template hx-nodes.

In the configuration pane, click the vMedia Policy tab. Click Modify vMedia Policy. Chose the HyperFlex vMedia Policy from the drop-down selection and click OK twice. For Compute-Only nodes (if necessary), select Servers >Service Profile Templates >root >Sub-Organizations >>>Service Template compute-nodes.

In the configuration pane, click the vMedia Policy tab. Click Modify vMedia Policy. Chose the HyperFlex vMedia Policy from the drop-down selection and click OK twice.

Select Servers >Policies >root >Sub-Organizations >>>Boot Policy HyperFlex. In the navigation pane, expand the section titled CIMC Mounted vMedia. Click the entry labeled Add CIMC Mounted CD/DVD. Select the CIMC Mounted CD/DVD entry in the Boot Order list, and click the Move Up button until the CIMC Mounted CD/DVD entry is listed first. Click Save Changes and click OK.

To begin the installation after modifying the vMedia policy, Boot policy and service profile template, the servers need to be rebooted. To complete the reinstallation, it is necessary to open a remote KVM console session to each server being worked on. To open the KVM console and reboot the servers, complete the following steps: 1. In Cisco UCS Manager, click the Equipment button on the left-hand side. Expand Equipment >Rack mounts >Servers >Server 1.

In the configuration pane, click KVM Console. The remote KVM Console window will open in a new browser tab. Click Continue to any security alerts that appear, and click the hyperlink to start the remote KVM session. Repeat Steps 2-4 for all additional servers whose console you need to monitor during the installation. In Cisco UCS Manager, click the Equipment button on the left-hand side. Expand Equipment >Rack-Mount Servers >Servers. In the configuration pane, click the first server to be rebooted, then shift+click the last server to be rebooted, selecting all of the servers.

Right-click the mouse and click Reset. Select Power Cycle and click OK. The servers you are monitoring in the KVM console windows will now immediately reboot, and boot from the remote vMedia mount.

Alternatively, the individual KVM consoles can be used to perform a power cycle one-by-one. When the server boots from the installation ISO file, you will see a customized Cisco boot menu. In the Cisco customized installation boot menu, select “HyperFlex Converged Node – HX PIDs Only” and press enter.

Enter “yes” in all lowercase to confirm and install ESXi. There may be error messages seen on screen, but they can be safely ignored. (Optional) When installing Compute-Only nodes, the appropriate Compute-Only Node option for the boot location to be used should be selected. The “Fully Interactive Install” option should only be used for debugging purposes. Once all the servers have booted from the remote vMedia file and begun their installation process, the changes to the boot policy need to be quickly undone, to prevent the servers from going into a boot loop, constantly booting from the installation ISO file. To revert the boot policy settings, complete the following steps: 1.

Select Servers >Policies >root >Sub-Organizations >>>Boot Policy HyperFlex. Select the CIMC Mounted CD/DVD entry in the Boot Order list, and click Delete. Click Save Changes and click OK. The changes made to the vMedia policy and service profile template may also be undone once the ESXi installations have all completed fully, or they may be left in place for future installation work. The process to expand a HyperFlex cluster can be used to grow an existing HyperFlex cluster with additional converged storage nodes, or to expand an existing cluster with additional compute-only nodes to create an extended cluster. Expansion with Compute-Only Nodes The HX installer has a wizard for Cluster Expansion with converged nodes and compute-only nodes, however the compute-only node process requires some additional manual steps to install the ESXi hypervisor on the nodes.

To expand an existing HyperFlex cluster with compute-only nodes, creating an extended HyperFlex cluster, complete the following steps: 1. On the HyperFlex installer webpage select a Workflow of “Cluster Expansion”. Enter the Cisco UCS Manager and vCenter DNS hostname or IP address, the admin usernames, and the passwords. The default Hypervisor credential which comes installed from the factory is username: root with a password of “Cisco123” and are already entered in the installer. You can select the option to see the passwords in clear text. Optionally, you can import a JSON file that has the configuration information, except for the appropriate passwords.

Click Continue. Select the HX cluster to expand and click Continue. If the installer has been reset and does not show the previously installed cluster, enter the HX cluster management IP address instead. From the list of unassociated servers, select the blade or rack mount servers you wish to add to the cluster as compute-only nodes, then click Continue. On the Cisco UCS Manager Configuration page, enter the VLAN settings, Mac Pool Prefix, UCS hx-ext-mgmt IP Pool for CIMC, iSCSI Storage setting, FC Storage setting, and sub-organization name, making sure that all the values match the existing settings for the cluster being expanded. Click Continue.

Enter the subnet mask, gateway, DNS, and IP addresses for the Hypervisors (ESXi hosts) as well as host names. The IPs will be assigned through Cisco UCS Manager to the new ESXi hosts. Click Continue. Enter the additional IP addresses for the Hypervisor Data network of the new ESXi hosts.

Enter the current password that is set on the Controller VMs. Enable Jumbo Frames. Since compute-only nodes have no local storage disks, you do not need to select Clean up disk partitions.

(Optional) At this step you can manually add more servers for expansion if these servers already have service profiles associated and the hypervisor is ready, by clicking on Add Compute Server or Add Converged Server and then entering the IP addresses for the storage controller management and data networks. Validation of the configuration will now start. After validation, the installer will create the compute-only node service profiles and associate them with the selected servers. Once the service profiles are associated, the installer will move on to the Hypervisor Configuration step and display an error.

The error shown alerts you to the need to install the ESXi hypervisor onto the compute-only nodes. The following steps show how to install ESXi onto the new compute-only nodes. Click the Instructions button to see the steps in a PDF document.

If necessary, click the Launch UCS Manager button to log in to Cisco UCS Manager in another browser tab. Do not click Continue at this time. In Cisco UCS Manager, click the Servers button on the left-hand side. Expand Servers >Service Profiles >root >Sub-Organizations >.

Each new compute-only node will have a new service profile, for example: blade-1. Right-click the new service profile and click KVM Console.

The remote KVM console will open in a new browser tab. Accept any SSL errors or alerts, then click the link to launch the KVM console.

Repeat step 19 for each new service profile, that is associated with the new compute-only nodes. In the remote KVM tab, click the Virtual Media button in the top right-hand corner of the screen, then click Activate Virtual Devices. In the remote KVM tab, click the Virtual Media button in the top right-hand corner of the screen, then click the CD/DVD option. Click Choose File, browse for the Cisco custom ESXi ISO installer file, and click Open. Click Map Drive. Repeat steps 21-24 for all the new compute-only nodes. In the remote KVM tab, click the Server Actions button in the top right-hand corner of the screen, the click Reset.

Choose the Power Cycle option, then click OK. Observe the server going through the POST process until the following screen is seen. When it appears, press the F6 key to enter into the boot device selection menu. Select Cisco vKVM-mapped vDVD1.22, then press Enter. The server will boot from the remote KVM mapped ESXi ISO installer and display the following screen: 33. Select the appropriate installation option for the compute-only node you are installing, either installing to SD cards, local disks, or booting from SAN, then press Enter. Type “yes” and press Enter to accept the warning and continue the installation.

The ESXi installer will now automatically perform the installation to the boot media. As you watch the process, some errors may be seen, but they can be ignored. Once the new server has completed the ESXi installation, it will be waiting at the console status screen seen below.

Repeat steps 26-35 for all the additional new compute-only nodes being added to the HX cluster. Once all the new nodes have finished their fresh ESXi installations, return to the HX installer, where the error in step 15 was seen. Click Continue. Click Retry Hypervisor Configuration. The HX installer will now proceed to complete the deployment and perform all the steps listed at the top of the screen along with their status. When the expansion is completed, a summary screen showing the status of the expanded cluster and the expansion operation is shown. After the install has completed, the compute-only nodes are added to the cluster and now have access to the existing HX datastores, but some manual post installation steps are required.

Most steps can be done by running the post_install script from the HX Installer VM, similar to when performing a new installation, or via a custom script. A list of additional configuration steps necessary includes: Disable SSH warning Creation of the guest VM port groups Creation of the vMotion vmkernel port Syslog Server Configuration. Management HyperFlex Connect is the new, easy to use, and powerful primary management tool for HyperFlex clusters. HyperFlex Connect is an HTML5 web-based GUI tool which runs on all of the HX nodes, and is accessible via the cluster management IP address. Logging into HyperFlex Connect can be done using pre-defined local accounts. In order to log in with a local account prepend “local/” to the account name, for example, local/root. The password for the default root account is set during the cluster creation as the cluster password.

Using local access is only recommended when vCenter direct or SSO credentials are not available. HyperFlex Connect provides Role-Based Access Control (RBAC) via integrated authentication with the vCenter Server managing the HyperFlex cluster. Users can have two levels of rights and permissions within the HyperFlex cluster: Administrator: Users with administrator rights in the managing vCenter server will have read and modify rights within HyperFlex Connect. These users can make changes to the cluster settings and configuration. Read-Only: Users with read-only rights in the managing vCenter server will have read rights within HyperFlex Connect. These users cannot make changes to the cluster settings and configuration.

Users can log in to HyperFlex Connect using direct vCenter credentials, for example,, or using vCenter Single Sign-On (SSO) credentials, such as an Active Directory user, for example, domain user. Creation and management of RBAC users and rights must be done via the vCenter Web Client or vCenter 6.5 HTML5 vSphere Client. To manage the HyperFlex cluster using HyperFlex Connect, complete the following steps: 1. Using a web browser, open the HyperFlex cluster’s management IP address via HTTPS, for example,. Enter a local credential, or a vCenter RBAC credential for the username, and the corresponding password.

The Dashboard view will be shown after a successful login. From the Dashboard view, several elements are presented: Cluster operational status, overall cluster health, and the cluster’s current node failure tolerance. Cluster storage capacity, used and free space, compression and deduplication savings, and overall cluster storage optimization statistics.

Cluster size and individual node health. Cluster IOPs, storage throughput, and latency for the past 1 hour.

HyperFlex Connect provides for additional monitoring capabilities, including: Alarms: Cluster alarms can be viewed, acknowledged and reset. Event Log: The cluster event log can be viewed, specific events can be filtered for, and the log can be exported. Activity Log: Recent job activity, such as ReadyClones can be viewed and the status can be monitored. The historical and current performance of the HyperFlex cluster can be analyzed via the built-in performance charts. The default view shows read and write IOPs, bandwidth, and latency over the past 1 hour for the entire cluster.

Views can be customized to see individual nodes or datastores, and change the timeframe shown in the charts. HyperFlex Connect is used as the management tool for all configuration of HyperFlex Data Protection features, including VM replication and data-at-rest encryption. Configuration of these features is covered in later sections of this document.

HyperFlex Connect presents several views and elements for managing the HyperFlex cluster: System Information: Presents a detailed view of the cluster configuration, software revisions, hosts, disks, and cluster uptime. Support bundles can be generated to be shared with Cisco TAC when technical support is needed. Views of the individual nodes and the individual disks are available. In these views, nodes can be placed into HX Maintenance Mode, and disks can be securely erased, as described later in this document. Datastores: Presents the datastores present in the cluster, and allows for datastores to be created, mounted, unmounted, edited or deleted, as described earlier in this document as part of the cluster setup. Virtual Machines: Presents the VMs present in the cluster, and allows for the VMs to be cloned and protected via replication, as described later in this document.

Upgrade: Upgrades to the HXDP software, and Cisco UCS firmware can be initiated from this view. Web CLI: A web based interface, from which CLI commands can be issued and their output seen, as opposed to directly logging into the SCVMs via SSH. The Cisco HyperFlex vCenter Web Client Plugin is installed by the HyperFlex installer to the specified vCenter server or vCenter appliance. The plugin is accessed as part of the vCenter Web Client (Flash) interface, and is a secondary tool used to monitor and configure the HyperFlex cluster. This plugin is not integrated into the new vCenter 6.5 HTML5 vSphere Client. In order to manage a HyperFlex cluster via an HTML5 interface, i.e. Without the Adobe Flash requirement, use the new HyperFlex Connect management tool.

To manage the HyperFlex cluster using the vCenter Web Client Plugin, complete the following steps: 1. Open the vCenter Web Client, and login with admin rights. In the home pane, from the home screen click vCenter Inventory Lists. In the Navigator pane, click Cisco HX Data Platform.

In the Navigator pane, choose the HyperFlex cluster you want to manage and click the name. Summary From the Web Client Plugin Summary screen, several elements are presented: Overall cluster usable capacity, used capacity, free capacity, datastore capacity provisioned, and the amount of datastore capacity provisioned beyond the actual cluster capacity.

Deduplication and compression savings percentages calculated against the data stored in the cluster. The cluster operational status, the health state, and the number of node failures that can occur before the cluster goes into read-only or offline mode.

A snapshot of performance over the previous hour, showing IOPS, throughput, and latencies. From the Web Client Plugin Monitor tab, several elements are presented: Clicking the Performance button displays a larger view of the performance charts. If a full webpage screen view is desired, click the Preview Interactive Performance charts hyperlink. Enter the username (root) and the password for the HX controller VM to continue. Clicking the Events button displays a HyperFlex event log, which can be used to diagnose errors and view system activity events.

From the Web Client Plugin Manage tab, several elements are presented: Clicking the Cluster button displays an inventory of the HyperFlex cluster and the physical assets of the cluster hardware. Clicking the Datastores button allows datastores to be created, edited, deleted, mounted and unmounted, along with space summaries and performance snapshots of that datastore.

In this section, various best practices and guidelines are given for management and ongoing use of the Cisco HyperFlex system. These guidelines and recommendations apply only to the software versions upon which this document is based, listed in. For the best possible performance and functionality of the virtual machines that will be created using the HyperFlex ReadyClone feature, the following guidelines for preparation of the base VMs to be cloned should be followed: Base VMs must be stored in a HyperFlex datastore. All virtual disks of the base VM must be stored in the same HyperFlex datastore. Base VMs can only have HyperFlex native snapshots, no VMware redo-log based snapshots can be present. For very high IO workloads with many clone VMs leveraging the same base image, it might be necessary to use multiple copies of the same base image for groups of clones.

Doing so prevents referencing the same blocks across all clones and could yield an increase in performance. This step is typically not required for most Figure 48 HyperFlex Management - ReadyClones HyperFlex native snapshots are high performance snapshots that are space-efficient, crash-consistent, and application consistent, taken by the HyperFlex Distributed Filesystem, rather than using VMware redo-log based snapshots.

For the best possible performance and functionality of HyperFlex native snapshots, the following guidelines should be followed: Make sure that the first snapshot taken of a guest VM is a HyperFlex native snapshot, by using the “Cisco HX Data Platform” menu item in the vSphere Web Client, and choosing Snapshot Now or Schedule Snapshot. Failure to do so reverts to VMware redo-log based snapshots. (Figure 49) A Sentinel snapshot becomes a base snapshot that all future snapshots are added to, and prevents the VM from reverting to VMware redo-log based snapshots. Failure to do so can cause performance degradation when taking snapshots later, while the VM is performing large amounts of storage IO. Additional snapshots can be taken via the “Cisco HX Data Platform” menu, or the standard vSphere client snapshot menu.

As long as the initial snapshot was a HyperFlex native snapshot, each additional snapshot is also considered to be a HyperFlex native snapshot. Do not delete the Sentinel snapshot unless you are deleting all the snapshots entirely. Do not revert the VM to the Sentinel snapshot. (Figure 50) If large numbers of scheduled snapshots need to be taken, distribute the time of the snapshots taken by placing the VMs into multiple folders or resource pools. For example, schedule two resource groups, each with several VMs, to take snapshots separated by 15 minute intervals in the scheduler window. Snapshots will be processed in batches of 8 at a time, until the scheduled task is completed.

(Figure 51) The Cisco HyperFlex Distributed Filesystem can create multiple datastores for storage of virtual machines. While there can be multiple datastores for logical separation, all of the files are located within a single distributed filesystem. As such, performing storage vMotions of virtual machine disk files has little value in the HyperFlex system. Furthermore, storage vMotions create additional filesystem consumption and generate additional unnecessary metadata within the filesystem, which must later be cleaned up via the filesystem’s internal cleaner process. Note: It is recommended to not perform storage vMotions of the guest VMs between datastores within the same HyperFlex cluster. Storage vMotions between different HyperFlex clusters, or between HyperFlex and non-HyperFlex datastores are permitted.

HyperFlex clusters can create multiple datastores for logical separation of virtual machine storage, yet the files are all stored in the same underlying distributed filesystem. The only difference between one datastore and another are their names and their configured sizes.

Due to this, there is no compelling reason for a virtual machine’s virtual disk files to be stored on a particular datastore versus another. Note: All of the virtual disks that make up a single virtual machine must be placed in the same datastore. Spreading the virtual disks across multiple datastores provides no benefit, and can cause ReadyClone and Snapshot errors.

In HyperFlex Connect, from the System Information screen, in the Nodes view, the individual nodes can be placed into HX Maintenance Mode. Also, within the vCenter Web Client, a specific menu entry for “HX Maintenance Mode” has been installed by the HyperFlex plugin. This option directs the storage platform controller on the node to shutdown gracefully, redistributing storage IO to the other nodes with minimal impact. Using the standard Maintenance Mode menu in the vSphere Web Client, or the vSphere (thick) Client can be used, but graceful failover of storage IO and shutdown of the controller VM is not guaranteed.

HyperFlex 2.5 introduces new data protection features, including data-at-rest encryption. HyperFlex clusters can be ordered with self-encrypting disks (SED) which encrypt all of the data stored on them. A cluster using SEDs will store all of its data in an encrypted format, and the disks themselves perform the encryption and decryption functions. Since the hardware handles all the encryption and decryption functions, no additional load is placed on the CPUs of the HyperFlex nodes. Storing the data in an encrypted format prevents data loss and data theft, by making the data on the disk unreadable if it is removed from the system.

This protection of the data enables HyperFlex to be used in environments where high security is required, such as healthcare providers (HIPAA), financial accounting systems (SOX), credit card transactions (PCI), and more. Each SED contains a factory generated data encryption key (DEK) which is stored on the drive in a secured manner, and is used by the internal encryption circuitry to perform the encryption of the data.

In truth, an SED always encrypts the data, but the default operation mode is known as the unlocked mode, wherein the drive can be placed into any system and the data can be read from it. To provide complete security, the SED needs to be locked, and reconfigured into what is called auto-unlock mode. This is accomplished via software, using another encryption key, called the authentication key (AK). Ds1307 Bascom Programmer here.

The authentication key is generated externally from the SED and used to encrypt the DEK. When an SED operates in auto-unlock mode its DEK is encrypted, so when the SED is powered on, the AK must be provided by the system, via the disk controller, to decrypt the DEK, which then allows the data to be read. Once unlocked, the SED will continue to operate normally until it loses power, when it will automatically lock itself. If a locked SED is removed from the system, then there is no method for providing the correct AK to unlock the disk, and the data on the disk will remain encrypted and unreadable.

In order to configure a HyperFlex cluster for encryption, all of the disks on all of the nodes of the cluster must be SEDs. The authentication keys which are used to encrypt the data encryption keys on the disks must be supplied by the HyperFlex cluster. The authentication keys can be provided in one of three ways: Local keys in Cisco UCS Manager derived from an encryption passphrase. Local keys are simpler to configure, and are intended for use in testing, proof-of-concept builds, or environments where an external Key Management System (KMS) is not available. Local key configurations create a single authentication key (AK) which is used to encrypt all the disks on all the nodes of the cluster. Remote keys, where Cisco UCS Manager retrieves the keys via Key Management Interoperability Protocol (KMIP) from a remote KMS. The client/server communications between the HX nodes and the KMIP server are secured using trusted certificate authority (CA) signed keys, created from certificate signing requests (CSR).

Remote key configurations create a unique authentication key for each node, and that AK is used for all disks on that node, providing an even higher level of security. Remote keys, where Cisco UCS Manager retrieves the keys via Key Management Interoperability Protocol (KMIP) from a remote KMS, but the client/server communications between the HX nodes and the KMIP server are secured using self-signed certificates.

Cisco has tested remote and self-signed keys using KMS systems, including Gemalto SafeNet KeySecure, and Vormetric DSM. A large number of steps are required to perform the configuration of a certificate authority (CA), root certificates, and signing certificates. Additionally, these steps are significantly different depending on the KMS being used. Because of this, the specific steps needed to configure encryption with remote keys is not covered in this design document.

Note: The HyperFlex Connect encryption menu and configuration options are only available when the cluster contains encryption capable hardware on all of the nodes. To enable encryption using locally managed keys in Cisco UCS Manager, complete the following steps: 1. Open HyperFlex Connect and log in with admin privileges. Click Encryption in the menu on the left, then click the Configure encryption button.

Enter the Cisco UCS Manager IP address or hostname, an administrative username, and password, then click Next. Click the option for Local key, then click Next. Enter an encryption key passphrase, which must be exactly 32 characters long, then click Enable Encryption. At any time, it may be determined for security purposes that it is necessary to regenerate the authentication keys in the cluster, which are used to unlock the encrypted contents of the disks. A rekey operation can be run to regenerate the keys, in case the existing keys may have been compromised, or as part of company policy. A rekey operation is non-destructive to the existing data, and the data remains encrypted at all times.

To rekey the drives, complete the following steps: 1. Open HyperFlex Connect and log in with admin privileges. Click Encryption in the menu on the left, then click the Re-key button. Enter the Cisco UCS Manager IP address or hostname, an administrative username, and password, then click Next.

Enter the existing encryption passphrase, and a new 32 character encryption passphrase, then click Re-key. If an encrypted drive is failed, a predicted failure alarm is triggered, or if a drive is otherwise going to be removed from a node, the drive can be securely erased before its removal. Erasing a drive is a destructive event to the data on that disk, however the data still exists as replicas in other locations across the cluster. A disk secure erase will trigger an event in the cluster similar to a disk failure, and the lost data segments will be recreated in other online locations in the cluster, in order to return the data to its configured replication factor.

To securely erase a drive, complete the following steps: 1. Open HyperFlex Connect and log in with admin privileges. Click System Information in the menu on the left, then click Disks. Highlight the disk to be erased, then click Secure Erase.

For a cluster using local encryption keys, enter the encryption passphrase, for remote key configurations, no action is necessary. Click Secure Erase. Click “Yes, erase this disk” at the confirmation pop-up.

When complete, the disk status will change to “Ok to remove”. Remove the disk from the HX node. HyperFlex 2.5 introduces new data protection features, including snapshot-based VM level replication between two HyperFlex clusters. Replication can be used to migrate or recover a single VM in the secondary HX cluster, groups of VMs can be coordinated and recovered, or all VMs can be recovered as part of a disaster recovery scenario. In order to start using replication, two HyperFlex clusters must be installed and have network connectivity between them. The clusters must both be either extended clusters, or all-flash clusters, it is not possible to replicate between hybrid and all-flash clusters.

The clusters are allowed to use self-encrypting disks or standard disks in either location, both of them, or none of them, there is no restriction in that respect. To avoid complications with duplicate VM IDs, it is recommended that the two replicating HyperFlex clusters be managed by two different VMware vCenter servers.

After a HyperFlex cluster is installed, none of the networking configuration required for replication is in place. In order to use replication, the replication networking must first be configured in HyperFlex Connect, which automates the changes in Cisco UCS Manager, configures the ESXi port groups, and assigns the new replication IP addresses to the SCVMs. Once the networking configuration work is completed for both clusters that will replicate to each other, a partnership, or pairing between the two clusters is established in HyperFlex Connect. After this replication pair is established, VMs can be protected individually, or they can be placed into protection groups, which are created to protect multiple VMs with the same replication settings. VMs can be replicated in intervals as often as once per 15 minutes, up to once per 24 hours, which is analogous to the Recovery Point Objective (RPO).

Care must be taken to ensure that the two clusters have enough storage capacity to store the replicated snapshots of the remote cluster’s VMs, and also have enough CPU and RAM resources to run those VMs in case they must be recovered. HyperFlex Connect can be used to monitor the status of the protected VMs.

Protected VMs can be recovered in the secondary site via the HyperFlex CLI using the stcli command line tool. The two HyperFlex clusters that will replicate must have TCP/IP connectivity between them, and additional IP addresses must be provided to an internal IP address pool that the HX SCVMs will use. The minimum number of IP addresses required is the number of nodes in the cluster, plus 1 additional address. More addresses than are currently needed can be placed into the pool to allow for future growth of the HX cluster. An existing VLAN ID and subnet can be used, although it is more typical to configure a specific VLAN and subnet to carry replication traffic that will traverse the campus or WAN links between the two clusters. The VLANs that will be used for replication traffic must already be trunked to the Cisco UCS Fabric Interconnects from the northbound network by the upstream switches, and this configuration step must be done manually prior to beginning the HyperFlex Connect configuration.

The bandwidth usage of the replication traffic can be set to a limit so as not to saturate the interconnecting network links, or it may be left unlimited. The bandwidth consumption will be directly affected by the number of VMs being protected, and the frequency of their replication. The interconnection between the two clusters at the two sites can be done in several ways. In most cases, the uplinks from the HX clusters will carry all the needed VLAN IDs on the same set of interfaces, including HX management, vMotion, storage traffic, guest VM traffic, and the replication traffic.

In some cases, it is desired that the replication traffic will traverse a set of independent uplinks, which is referred to as a split L2 topology. Due to a technical limitation of implementing a split L2 topology, the configuration of replication networking cannot accommodate a split L2 configuration.

Specifically, a single UCS vNIC cannot carry multiple VLANs that traverse multiple uplink groups. Since the default configuration uses vmnic0 and vmnic1 to carry HX management traffic and replication traffic, both of those VLANs must arrive to UCS across a single set of uplinks. The replication subnets and VLANs used in the two sites can be different routed subnets, or they can be a single subnet if other technologies, such as OTV, are in use by the WAN. Replication traffic originates and terminates on the SCVMs running on each HX host. Figure 54 Replication Networking Configuring replication networking in HyperFlex Connect automates the following tasks: Creates the replication VLAN in Cisco UCS Manager. Adds the new replication VLAN to the VNIC templates named hv-mgmt-a and hv-mgmt-b in the appropriate sub-organization in Cisco UCS Manager. Sets the VLAN ID of the Storage Controller Replication Network port group on all ESXi nodes.

Creates a pool of IP addresses internal to the HyperFlex cluster, from which each SCVM will draw one IP address, plus 1 additional IP will be used as a roaming clustered address. Instructs the SCVMs to request an individual IP address, and configures the clustered IP address. To configure the replication network, complete the following steps: 1. Open HyperFlex Connect and log in with admin privileges.

Click Replication in the menu on the left, then click the Configure button. Enter the VLAN name and VLAN ID that will be created in Cisco UCS Manager, and assigned to the Storage Controller Replication Network port group on the ESXi hosts. Enter the Cisco UCS Manager IP address or hostname, an administrative username, and password. Enter the replication subnet in CIDR notation, i.e.

A.b.c.d/n, and the gateway IP address for the subnet. Enter the starting and ending IP addresses for the range that will be added to the pool assigned to the SCVMs, and click the Add button. If outbound bandwidth limits must be set, check the box to enable it and enter a value between 10 and 100,000 Mbps.

Cisco recommends limiting the bandwidth to 1000 Mbps or less. Click Configure. The two HyperFlex clusters that will be able to replicate VMs to each other must first be paired before the replication can begin. Prior to pairing, the replication networking on both clusters must be configured and datastores must have been created on both clusters. You must know the administrative login credentials of the remote cluster, and the remote cluster’s management IP address in order to proceed. To configure the replication pair, perform the following steps: 1. Open HyperFlex Connect and log in with admin privileges.

Click Replication in the menu on the left, then click the Create Replication Pair button. Enter a name for the replication pair, then click Next. Enter the cluster management IP address for the remote cluster, the username, and the password, then click Pair.

The username and password must have admin rights in the vCenter server managing the remote cluster. Pick the local datastore and remote datastore to pair on the two clusters, then click Next. At the summary screen, click Map Datastores. Once a replication pair is established, and datastores are mapped to each other across two HX clusters, VM Protection can be configured. VMs can be protected individually, or they can be added to a new or existing Protection Group.

Protection Groups can be created to allow for a common configuration of replication parameters to be applied to a collection of VMs, without configuring them individually. A good example would be creating multiple Protection Groups for several classes of protection, each with a different replication schedule, such as a “Gold” group with a 15-minute schedule, a “Silver” group with a 2 or 4 hour schedule, and a “Bronze” group with a 12 or 24 hour schedule. Migration or recovery operations can be carried out against an entire protection group. If a protection group is halted, marking it for recovery, then all VMs within the group must be recovered on the secondary, or target cluster. If a VM is a member of a protection group, it cannot be individually migrated or recovered. If an individual VM must be migrated or recovered, but it is a member of a protection group, that VM must be removed from the group, thereby unprotecting it, then it must be individually protected again. Care must be taken that the individual protection replicates at least one snapshot before attempting a migration or recovery.

To create a Protection Group, complete the following steps: 1. Open HyperFlex Connect and log in with admin privileges. Click Replication in the menu on the left, then click Protection Groups, then click Create Protection Group. Enter a name for the group.

Choose the replication interval from the drop-down menu. Choose a time for the replication to start, either immediately or at a future time. Check the box if you wish to quiesce the VM’s activity via VMware Tools during the snapshot, then click Create Protection Group.

Virtual machines can be configured for protection, i.e. Replication, individually, or be placed into a Protection Group.

The protection settings that can be configured on an individual VM are the same as the settings that are configured for a protection group. In most cases, it is easier to configure multiple Protection Groups, each with the settings that are required, and then add VMs to those groups.

This process simplifies operations and ensures that replication schedules are not set improperly. To protect a virtual machine, or group of virtual machines, complete the following steps: 1. Open HyperFlex Connect and log in with admin privileges. Click Virtual Machines in the menu on the left. Check the box next to one or more VMs in the list, then click Protect. Choose the option Add to an existing protection group, and choose the group to add the VM(s) to, then click Protect Virtual Machine.

Choose the option Protect this virtual machine independently, then choose the replication interval, choose a time for the replication to start, either immediately or at a future time, and choose if you would like to use the VMware Tools to quiesce the virtual machines, then click Protect Virtual Machine. Note: When selecting multiple VMs to protect, the only options available are to place those VMs into a protection group, or create a new protection group. To protect multiple VMs with individual settings, each VM must be configured for protection, one-by-one. The HyperFlex Connect HTML GUI can be used to monitor the status of ongoing VM protection and replication.

The Replications view shows the status of each individual snapshot replication operation. Figure 55 Source Replications View The Protected Virtual Machines View shows the protection status of all VMs which have been configured for protection. The green Protected icon indicates that the VM is being successfully protected according to the configured replication interval, or RPO.

Figure 56 Source Protected Virtual Machines The Protection Groups view will indicate the status of all VMs that are members of a Protection Group. The Protection Groups can be expanded by clicking on the carat on the left-hand side, to see the status of the individual VMs in that Protection Group. Figure 57 Source Protection Groups The Bandwidth Monitor in the upper right-hand corner can be hovered over to see a pop-up box indicating the replication bandwidth used, or the graph can be clicked on to see an expanded view of the bandwidth consumed by the outgoing or incoming replication traffic. Figure 58 Bandwidth Monitor Figure 59 Bandwidth Charts All of the replication monitoring views can also be accessed via the secondary, or target HX cluster, and the same VMs and protection groups will be presented, only as incoming VMs and groups instead of outgoing. Two paired HX clusters can replicate VMs in both directions, therefore the replication status of all VMs and Protection Groups, incoming and outgoing, are presented in the replication monitor of both clusters.

Once configured, replication will run continuously in the background according to the configured schedules for the VMs and Protection Groups. If it is necessary to pause replication, for example during a maintenance activity such as an upgrade, replication can be paused and resumed via the HyperFlex CLI. To pause replication, complete the following steps: 1. Log in to the HyperFlex cluster’s management IP address via SSH as root. At the command line, enter the command: stcli dp schedule pause. To resume replication, complete the following steps: 3. Log in to the HyperFlex cluster’s management IP address via SSH as root.

At the command line, enter the command: stcli dp schedule resume The snapshots taken by the HX Data Protection engine are separate from the HyperFlex native snapshots. Data Protection snapshots are triggered and tracked by the HX Data Platform software internally, and can only be used for the recovery of a virtual machine in the secondary, or target paired HX cluster. These snapshots are not visible in the snapshot manager of the VMware vSphere Web Client, the C# (thick) vSphere Client, or HTML5 vSphere Client, therefore they cannot be used to roll back a VM to an earlier state in the primary cluster location. In order to have the ability to roll back a VM to an earlier snapshot in the primary, or source location, HX snapshots must be scheduled on the VMs in addition to the Data Protection replication snapshots. When routine scheduled maintenance activities are required, or for other management purposes, virtual machines can be migrated from the source cluster to the target cluster. Migration of a virtual machine leaves the replication pairing between the two clusters in place, so that the VM can be protected again in the opposite direction of the original replication.

As an overview of the process, a VM migration includes: Stopping the replication of the specific VM to be migrated. Shutting down the VM in the primary, or source HX cluster. Performing a recovery of the VM on the secondary, or target cluster. Unprotecting the VM to remove the replication configuration of that VM. Deleting the original source VM.

Protecting the VM, replicating the VM from the secondary cluster, back to the original cluster. Virtual machine migration and recovery operations are executed via the HyperFlex CLI. To perform a virtual machine migration, complete the following steps: 1.

Log in to the secondary, or target HyperFlex cluster’s management IP address via SSH as root. List the virtual machines being replicated by entering the CLI command: stcli dp vm list --brief 2. Determine the VM to be migrated and copy the UUID listed from the output of the previous command.

Alternatively, the UUIDs for the Protection Group itself, and all the VMs in the group can be found in the output from running the following CLI command: stcli dp group list --groupname. VmGroupEr: type: dp_vmgroup id: 8b9fa36f-13a2-4199-9147-b39bc31b6162 name: Silver members: ---------------------------------------- idtype: 2 type: dp_vm id: 421a0ff3-a147-9ae8-881c-f91cf822e273 name: Silver1 ---------------------------------------- idtype: 2 type: dp_vm id: 421a38da-5c4a-e843-0728-583e317a7ad5 name: Bronze1 ---------------------------------------- 4. Halt the VM replication by entering the following command: stcli dp vm halt --vmid >5. Alternatively, if the VMs are part of a Protection Group, the Protection Group must be halted using the following command: stcli dp group halt --groupid. Warning: If a Protection Group is halted, all VMs in that group must be migrated or recovered.

There is no way to resume replication of a Protection Group once it has been halted. If a single VM needs to be migrated, and it is part of a Protection Group, the VM must be removed from the group and protected individually before attempting to migrate or recover the VM. Verify the status of the VM or Protection Group shows Halted in HyperFlex Connect of both the source and target clusters. Shut down the source VM in the primary, or source cluster, using the vSphere Web Client, or the HTML5 vSphere Client. Run the migration by entering the CLI command: stcli dp vm recover failover --vmid >Additional CLI syntax switches are available during a VM recovery operation. Option Required Description --vmid Yes Perform the recovery on the VM with the provided BIOS UUID.

--resourcepool-id No Place the recovered VM(s) in the resource pool with the specified ID. Specify a resource pool or folder, but not both. --resourcepool-name No Place the recovered VM(s) in the resource pool with the specified name. Specify a resource pool or folder, but not both. --folder-id No Place the recovered VM(s) in the folder with the specified ID.

Specify a resource pool or folder, but not both. --folder-name No Place the recovered VM(s) in the folder with the specified name. Specify a resource pool or folder, but not both. --network-mapping No Modify the source VM to recovered VM network port group mapping. Use the format: source_network:destination_network --poweron No Power on the recovered VM after the recovery job completes. --force No Force the recovery job to run without validation of the arguments.

Note: Protection Groups can be recovered; however, the process involves recovering all of the VMs within the group one at a time. Each VM recovery must be completed before beginning the next recovery, in a serial fashion. Parallel recovery operations of multiple VMs within the same Protection Group are not supported.

Recovery of multiple VMs in parallel can be done as long as each VM is a member of a separate Protection Group. For example, parallel recovery of 1 VM in the Bronze Protection Group and 1 VM in the Silver Protection Group can be done. The recovery failover command will output a job ID for the operation. To view the status of the recovery job, copy the job ID and enter the CLI command: stcli dp vm recover status --id >10. Once the job completes, verify the status of the VM shows Recovered in HyperFlex Connect of both the source and target clusters. Power on the migrated VM via the vSphere Web Client or the HTML5 vSphere Client to test its functionality.

1000 Ways To Make 1000 Dollars Pdf Free. Perform any necessary post-recovery tasks on the VM, such as changing IP addresses, or updating DNS records, in order to make the VM and its applications available on the network. From the HyperFlex Connect Replication page of the primary, or source cluster, click the Protected Virtual Machines menu, select the VM that was recovered, then click Unprotect.

Alternatively, the VM protection can be removed via the CLI from the primary, or source cluster, using the “stcli dp vm delete” command. Delete the source VM in the primary, or source cluster, using the vSphere Web Client, or the HTML5 vSphere Client.

Repeat steps 2 – 14 for each VM you wish to migrate. If an entire Protection Group was migrated, once all the VMs have been recovered in the secondary, or target cluster, the Protection Group status will show as Recovered. The Protection Group must be deleted from the primary, or source cluster, as it is no longer possible to add VMs to a recovered group, nor is it possible to make the group active again. Optionally, use HyperFlex Connect to reconfigure protection for the migrated VM(s), only now the protection would be in the opposite direction of the previous snapshots. Warning: If a Protection Group is halted, all VMs in that group must be migrated or recovered. There is no way to resume replication of a Protection Group once it has been halted. If a single VM needs to be migrated, and it is part of a Protection Group, the VM must be removed from the group and protected individually before attempting to migrate or recover the VM.

Verify the status of the VM or Protection Group shows Halted in HyperFlex Connect of the secondary, or target cluster. Run the recovery by entering the CLI command: stcli dp vm recover failover --vmid >Additional CLI syntax switches are available during a VM recovery operation. Option Required Description --vmid Yes Perform the recovery on the VM with the provided BIOS UUID. --resourcepool-id No Place the recovered VM(s) in the resource pool with the specified ID. Specify a resource pool or folder, but not both.

--resourcepool-name No Place the recovered VM(s) in the resource pool with the specified name. Specify a resource pool or folder, but not both.

--folder-id No Place the recovered VM(s) in the folder with the specified ID. Specify a resource pool or folder, but not both. --folder-name No Place the recovered VM(s) in the folder with the specified name. Specify a resource pool or folder, but not both. --network-mapping No Modify the source VM to recovered VM network port group mapping. Use the format: source_network:destination_network --poweron No Power on the recovered VM after the recovery job completes.

--force No Force the recovery job to run without validation of the arguments. Note: Protection Groups can be recovered; however, the process involves recovering all of the VMs within the group one at a time. Each VM recovery must be completed before beginning the next recovery, in a serial fashion.

Parallel recovery operations of multiple VMs within the same Protection Group are not supported. Recovery of multiple VMs in parallel can be done as long as each VM is a member of a separate Protection Group. For example, parallel recovery of 1 VM in the Bronze Protection Group and 1 VM in the Silver Protection Group can be done. The recovery failover command will output a job ID for the operation. To view the status of the recovery job, copy the job ID and enter the CLI command: stcli dp vm recover status --id >10.

Once the job completes, verify the status of the VM shows Recovered in HyperFlex Connect of the secondary, or target cluster. Repeat steps 3 – 10 for each VM you need to recover.

Power on the recovered VMs via the vSphere Web Client or the HTML5 vSphere Client to test their functionality. Perform any necessary post-recovery tasks on the VMs, such as changing IP addresses, or updating DNS records, in order to make the VMs and their applications available on the network. List the HX cluster peers, and find the name of the pairing by using the following CLI command: stcli dp peer list 15. Delete the replication pairing between the two clusters by using the following CLI command: stcli dp peer forget --name >16. From the HyperFlex Connect Replication page of the secondary, or target cluster, click the Protected Virtual Machines menu, select all the VMs that were recovered, then click Unprotect.

Alternatively, the VM protection can be removed via the CLI from the secondary, or target cluster, using the “stcli dp vm delete” or “stcli dp group vm delete” command. If an entire Protection Group was migrated, once all the VMs have been recovered in the secondary, or target cluster, the Protection Group status will show as Recovered.

The Protection Group must be deleted, as it is no longer possible to add VMs to a recovered group, nor is it possible to make the group active again. All the VMs in the group must be unprotected, as described in the previous step, before the group can be deleted. From the HyperFlex Connect Replication page of the secondary, or target cluster, click the Protection Groups menu, select Protection Groups that were recovered, then click Delete. Alternatively, the groups can be removed via the CLI from the secondary, or target cluster, using the “stcli dp group delete” command. Note: The initial group delete command may give an error if issued immediately after removing protection from the VMs within the group.

Wait a few minutes before retrying the command, and it should complete successfully. Note: The initial group delete command may give an error if issued immediately after removing protection from the VMs within the group. Wait a few minutes before retrying the command, and it should complete successfully. From the primary, or source cluster, list the HX cluster peers, and find the name of the pairing by using the following CLI command: stcli dp peer list 5. Delete the replication pairing between the two clusters by using the following CLI command: stcli dp peer forget --name >6. Delete the original source VMs on the primary, or source cluster.

At this point, the VMs have all been recovered, and both clusters have no replication pairing or configuration. The two clusters can be paired again, and the VMs can be migrated back to the original source cluster using the VM Migration steps documented earlier. Alternatively, the secondary, or target cluster, can be paired with a completely different cluster and replication can be established. This section provides a list of items that should be reviewed after the HyperFlex system has been deployed and configured. The goal of this section is to verify the configuration and functionality of the solution, and ensure that the configuration supports core availability requirements.

The following tests are critical to functionality of the solution, and should be verified before deploying for production: 1. Verify the expected number of converged storage nodes and compute-only nodes are members of the HyperFlex cluster in the vSphere Web Client plugin manage cluster screen. Verify the expected cluster capacity is seen in the vSphere Web Client plugin summary screen. Create a test virtual machine that accesses the HyperFlex datastore and is able to perform read/write operations. Perform the virtual machine migration (vMotion) of the test virtual machine to a different host on the cluster.

During the vMotion of the virtual machine, make sure the test virtual machine can perform a continuous ping to default gateway and to check if the network connectivity is maintained during and after the migration. The following redundancy checks can be performed to verify the robustness of the system. Network traffic, such as a continuous ping from VM to VM, or from vCenter to the ESXi hosts should not show significant failures (one or two ping drops might be observed at times). Also, all of the HyperFlex datastores must remain mounted and accessible from all the hosts at all times. Administratively disable one of the server ports on Fabric Interconnect A which is connected to one of the HyperFlex converged storage hosts. The ESXi virtual switch uplinks for fabric A should now show as failed, and the standby uplinks on fabric B will be in use for the management and vMotion virtual switches. Upon administratively re-enabling the port, the uplinks in use should return to normal.

Administratively disable one of the server ports on Fabric Interconnect B which is connected to one of the HyperFlex converged storage hosts. The ESXi virtual switch uplinks for fabric B should now show as failed, and the standby uplinks on fabric A will be in use for the storage virtual switch. Upon administratively re-enabling the port, the uplinks in use should return to normal. Place a representative load of guest virtual machines on the system.

Put one of the ESXi hosts in maintenance mode, using the HyperFlex HX maintenance mode option. All the VMs running on that host should be migrated via vMotion to other active hosts through vSphere DRS, except for the storage platform controller VM, which will be powered off. No guest VMs should lose any network or storage accessibility during or after the migration.

This test assumes that enough RAM is available on the remaining ESXi hosts to accommodate VMs from the host put in maintenance mode. The HyperFlex cluster will show in an unhealthy state. Reboot the host that is in maintenance mode, and exit it from maintenance mode after the reboot.

The storage platform controller will automatically start when the host exits maintenance mode. The HyperFlex cluster will show as healthy after a brief time to restart the services on that node. VSphere DRS should rebalance the VM distribution across the cluster over time. Note: Many vCenter alerts automatically clear when the fault has been resolved. Once the cluster health is verified, some alerts may need to be manually cleared.

Reboot one of the two Cisco UCS Fabric Interconnects while traffic is being sent and received on the storage datastores and the network. The reboot should not affect the proper operation of storage access and network traffic generated by the VMs. Numerous faults and errors will be noted in Cisco UCS Manager, but all will be cleared after the FI comes back online. A: Cluster Capacity Calculations A HyperFlex HX Data Platform cluster capacity is calculated as follows: ((( X 10^9) / 1024^3) X X X 0.92) / replication factor Divide the result by 1024 to get a value in TiB The replication factor value is 3 if the HX cluster is set to RF=3, and the value is 2 if the HX cluster is set to RF=2. The 0.92 multiplier accounts for an 8% reservation set aside on each disk by the HX Data Platform software for various internal filesystem functions. Calculation example: = 1200 for 1.2 TB disks = 15 for an HX240c-M4SX model server = 8 replication factor = 3 Result: (((1200*10^9)/1024^3)*15*8*0.92)/3 = / 1024 = 40.16 TiB B: HyperFlex Sizer HyperFlex sizer is a cloud based end-to-end tool that can help the customers and partners find out how many Cisco HyperFlex nodes are needed and how the nodes can be configured to meet their needs for the compute resources, storage capacity and performance requirements in the datacenter.

The sizing guidance of the HX system is calculated according to the information of workloads collected from the users. This cloud application can be accessed from anywhere at Cisco website ( CCO login required): Improvements in the sizing tool for HXDP 2.5 release include: Replication support: workloads can be sized to account for replication Encryption support: systems can be sized using self-encrypting disks Performance enhancements in HXDP 2.5, including NVMe caching disk support Fully populate the HXAF240 model server with all disks, and M10 GPU support Provide sizing estimates against the HX Workload Profiler tool output. Note: The HyperFlex Sizer tool is designed to provide general guidance in evaluating the optimum solution for using selected Cisco products. The tool is not intended to provide business, legal, accounting, tax or professional advice.

The tool is not intended as a substitute for your own judgment or for that of your professional advisors. Also available at the website is an updated HyperFlex Workload Profiler, version 2.3. The HyperFlex Workload Profiler tool is used to capture storage usage and performance statistics from an existing VMware ESX cluster, enabling you to use that data to assist with sizing a HyperFlex cluster which would assume that workload. The workload profiler is distributed as an OVA file, which can be deployed using static or DHCP assigned addressing, on an existing VMware ESXi host.

Once deployed, the profiler tool connects to an existing VMware vCenter server to gather storage statistics for the selected ESXi hosts. To capture performance data using the HyperFlex Workload Profiler, complete the following steps: 1. Deploy the HyperFlex Workload Profiler VM by using the Deploy OVF Template wizard, on the chosen existing ESXi host. Assign a static IP address or use DHCP addressing as part of the deployment wizard. Using a web browser, connect to the IP address assigned or leased by the Workload Profiler VM.

Enter the username and password, the default username and password is “monitoring”, then click Login. On first login, the Add Node wizard will run. Enter the vCenter server name or IP, a username with administrative rights, and the password, then click Connect. Once the vCenter server is connected, click Next to select the hosts to monitor.

Check the box next to the hosts to poll for data, then click Save. In the main screen, the vCenter server being polled will be listed.

Click the Start Profiling button. Choose a time interval to collect data on the system, then click OK. A 30-day collection is recommended for accurate sizing activities.

At any time during the collection polling, the data can be viewed by clicking on the View Collection button. The data for CPU and memory utilization, and storage statistics can be viewed, as an aggregate of all hosts, one host at a time, or from a per VM perspective. Once the collection is complete, the complete dataset can be exported as a comma-separated file, and the data can be automatically imported into the HyperFlex sizer tool to help with computing and storage sizing efforts, or otherwise analyzed to help with sizing decisions. Items Fabric A Fabric B iSCSI VLAN ID iSCSI Target Ports IP Address-A IP Address-B iSCSI IQN Name iSCSI Storage Controller #1 iSCSI Storage Controller #2 2. Follow to create HX cluster with the external storage adapters using the same VLAN ID’s obtained from Step 1 for both Fabric A and B. Upon completion of HX install two additional vNICs for iSCSI will be created for each HX host.

Open Cisco UCS Manager, expand LAN >LAN Cloud >Fabric A >VLANs, then Fabric B >VLANs to verify that the iSCSI VLANs are created and assigned to Fabric A and B. On the LAN tab, expand Policies >root >Sub-Organizations, go to the HX sub-organization just created, view the iSCSI templates that were created. In Cisco UCS Manager, Expand Servers >Service Profiles >root >Sub-Organizations, go to the HX sub-organization just created, verify the iSCSI vNICs on all HX servers.

Click one vNIC, view the properties of that iSCSI adapter. Make sure Jumbo MTU 9000 is set. Next set up the networking for the vSphere iSCSI switch. Login to vCenter and select the first node of the HX cluster in the left screen, then on the right screen select the Configuration tab, select Networking in the hardware pane, then scroll to the iSCSI switch. Click Properties. Select VMkernel and click Next.

Name iSCSI-A for the Network Label and input iSCSI VLAN ID for the A Fabric, then click Next. Add the IP address for subnet for Fabric-A and click Next. Click Finish to complete addition of iSCSI VMkernel port for A Fabric. Repeat Steps 7-11 to add VMkernel Port for iSCSI-B. Back to the vSwitch Properties page, highlight the vSwitch and click Edit. Change MTU for vSwitch to 9000.

Select the NIC Teaming tab and make both adapters active by moving the standby adapter up. Highlight the iSCSI-A VMkernel port and click Edit in the vSwitch Properties page. Change the port MTU t0 9000. Select the NIC Teaming tab.

Choose the option of Override switch failover order, highlight vmnic9 and move it to Unused Adapters as this adapter is for the iSCSI-B connection. Highlight the iSCSI-B VMkernel port and click Edit. Change the port MTU t0 9000. Select the NIC Teaming tab. Select the Override switch failover order, highlight vmnic8 and move it to Unused Adapters as this adapter is for the iSCSI-A connection.

Click Close and review the iSCSI vSwitch. Now you should have two IP addresses used in the vSwitch on separate VLANs. Repeat Steps 6-22 to configure the iSCSI vSwitch for the other HX nodes in the cluster. Add the software iSCSI adapters on HX hosts. Select the first node of the HX cluster in the left screen, then on the right screen select the Configuration tab, select Storage Adapters in the hardware pane and click Add, then click OK to Add Software iSCSI Adapters, and then click OK again.

Scroll down and right-click the newly created software initiator, right-click and select Properties. Click Configure to change the iSCSI IQN name to a customized name. Click the Network Configuration tab, and click Add to bind the VMkernel Adapters to the software iSCSI adapter. Select iSCSI-A and click OK. Click Add again, and select iSCSI-B and click OK.

Copy and record the initiator name, IP addresses of iSCSI-A and iSCSI-B VMkernel ports to the following table. Save these values for later use to add to the initiator group created on the storage array. Items Fabric A Fabric B iSCSI VLAN ID HX Hosts IP Address-A IP Address-B iSCSI IQN Name HX Server #1 iSCSI Initiator HX Server #2 iSCSI Initiator HX Server #3 iSCSI Initiator HX Server #4 iSCSI Initiator HX Server #5 iSCSI Initiator HX Server #6 iSCSI Initiator HX Server #7 iSCSI Initiator HX Server #8 iSCSI Initiator 31. Click the Dynamic Discovery tab and click Add and enter the first IP address that you recorded from your storage device network interface. Click Add again until all the interfaces for your storage controllers are entered. You do not need to rescan the host bus adapter at this point, so choose No to the scan popup. Repeat Steps 24-32 adding the software iSCSI adapters for the remaining HX nodes.

Now create iSCSI initiator groups and then create an iSCSI LUN on the storage system and map it to the HX system. In this example, we are using NetApp OnCommand System Manager GUI to create a LUN on a FAS3250 array. Please consult your storage documentation to accomplish the same tasks. It is assumed you have already configured your iSCSI storage as shown in the CVD. Open NetApp OnCommand System Manager GUI from the web browser, select the pre-configured iSCSI Storage Virtual Machine, expand Storage, then LUNs; from the right pane, click Create.

This will open Create LUN wizard. Click Next on the General Properties page, enter the LUN Name, Type and Size. Check “Select an existing volume or qtree for this LUN”, browse and select an existing volume, then click Next. On Initiators Mapping page, select Add Initiator Group. In Create Initiator Group wizard, on the General tab, enter Name, Operation System, and select Type of iSCSI for the Initiator Group to be created.

On Initiators tab, click Add then enter the iSCSI IQN Name of the first HX host (copy from Table 47), click OK. Repeat Step 40 until the IQN names of all HX iSCSI adapters are added.

Select Create to create the Initiator Group. The Create Initiator Group Wizard closes and reverts to the Initiators Mapping page of the Create LUN wizard. Select the HX initiator group that is just created, click Next three times then click Finish to complete the LUN creation. Check the iSCSI initiators mapped to this LUN.

With a mapped LUN, you can rescan the iSCSI software initiator. Login to the vCenter again, in the configuration tab, right-click the iSCSI software adapter and click Rescan or click Rescan All at the top of the pane (do this for each host). The iSCSI disk will show up in the details pane. Add the disk to the cluster by selecting Storage in the Hardware pane, then Add Storage in the Configuration tab. Leave Disk/LUN selected and click Next.

Now the NetApp iSCSI LUN will be detected. Highlight the disk and click Next, and then click Next again. Enter the new Datastore name and click Next then Finish. A new iSCSI datastore for the HX cluster will be created. You can now create VM’s on this new datastore and migrate data between HX and the iSCSI datastore. The HX installer can guide you through the process of setting up your HX cluster allowing you to leverage existing third-party storage via the Fibre Channel protocol. It will automatically configure Cisco UCS profiles, and HX cluster nodes with vHBAs, proper VSAN, and WWPN assignments, simplifying the setup.

The procedure is described in this CVD. It is assumed that the third-party storage system is already configured per a Cisco Validated Design and all networking configuration, including Fibre Channel for connecting via the upstream switches, is completed as well. In this example, we will be using Cisco MDS Fibre Channel switches that are connected to the Cisco UCS Fabric Interconnects, which are configured with Fibre Channel unified ports in End Host mode.

Changing the identity of unified ports on a Cisco UCS Fabric Interconnect requires that the FIs are rebooted, so this task should be completed prior to the installation of the HyperFlex cluster(s). The third-party storage is connected to the MDS switches. Note: It is required that you obtain the VSAN IDs being used in your current environment for the storage device that is already configured. This can be obtained from the SAN tab in Cisco UCS Manager, or from the upstream Fibre Channel switches. Follow for the HX cluster installation using the same VSAN IDs obtained from Step 1 for both Fabric A and B. Upon completion of HX install, two VSANs and two vHBAs (one for Fabric A and one for Fabric B) for each HX host will be created. Open Cisco UCS Manager, Expand SAN >SAN Cloud >Fabric A >VSANs, then Fabric B >VSANs, verify the right VSANs are generated: 3.

In Cisco UCS Manager, Expand Servers >Service Profiles >root >Sub-Organizations, go to the HX sub-organization you just created, verify vHBAs on all HX servers: 4. Record all the WWPN’s for each HX node in the following table. These values are needed later for the zone configuration on the FC switches. You can copy the WWPN value by clicking on the vHBA in Cisco UCS Manager and the in the right pane, right-clicking the WWPN to copy. Items Value Fabric A Fabric B HX Server #1 WWPN Alias HX Server #2 WWPN Alias HX Server #3 WWPN Alias HX Server #4 WWPN Alias HX Server #5 WWPN Alias HX Server #6 WWPN Alias HX Server #7 WWPN Alias HX Server #8 WWPN Alias 5. Alternatively, you can copy the WWPN value on the ESXi host in vCenter on the Configuration tab >Storage Adapters >Cisco VIC FCoE HBA Driver >. The WWPNs for the storage ports will also be recorded.

These values are needed later for zone configuration on the FC switches. You can get that information from your storage device’s management tool. Value Fabric A Fabric B Storage Device Port #1 WWPN Alias Storage Device Port #2 WWPN Alias Storage Device Port #3 WWPN Alias Storage Device Port #4 WWPN Alias 7.

Login to the MDS switch for A Fabric (MDS A), verify all HX vHBAs for A fabric have login to the name server and verify they are in the same VSAN as the target storage ports. Brian Everitt, Technical Marketing Engineer, Cisco UCS Data Center Engineering Group, Cisco Systems, Inc. Brian is an IT industry veteran with over 19 years of experience deploying server, network, and storage infrastructures for companies around the world. During his tenure at Cisco, he has been a lead Advanced Services Solutions Architect for Microsoft solutions, virtualization, and SAP Hana on Cisco UCS. Currently his focus is on Cisco’s portfolio of Software Defined Storage (SDS) and Hyperconverged Infrastructure solutions. Brian has earned multiple certifications from Microsoft, Cisco, and VMware. Hui Chen, Technical Marketing Engineer, Cisco UCS Data Center Engineering Group, Cisco Systems, Inc.

Hui is a network and storage veteran with over 15 years of experience on Fibre Channel-based storage area networking, the LAN/SAN convergence systems, and how to build end-to-end; from the server to storage, and solutions in the data center. Currently he focuses on Cisco’s Software Defined Storage (SDS) and Hyperconverged Infrastructure (HCI) solutions. Hui is also a seasoned CCIE. Jeffery Fultz, Technical Marketing Engineer, Cisco UCS Data Center Engineering Group, Cisco Systems, Inc. Jeff has over 20 years of experience in both Information Systems and Application Development dealing in Data Center Management, Backup, and Virtualization Optimization related technologies.

Jeff works on design and test a wide variety of enterprise solutions encompassing Cisco, VMware, Hyper-V, SQL, and Microsoft Exchange. Jeff is a Microsoft Certified System Engineer with multiple patents filed in the Datacenter Solutions space. NOTE: Available paragraph styles are listed in the Quick Styles Gallery in the Styles group on the Home tab. Alternatively, they can be accessed via the Styles window (press Alt + Ctrl + Shift + S).