Hyper Converged 250 System For VMware VSphere Installation Guide
Hyper Converged 250 System forVMware vSphere Installation GuideAbstractThis document describes how to install the Hyper Converged 250 System for VMwarevSphere and the ConvergedSystem 200–HC StoreVirtual system into a rack and configure itusing the preinstalled OneView InstantOn software.Part Number: 867788-003Published: December, 2016Edition: 8
ContentsOverview. 6Installing a new system.6Installing an expansion system. 6Preparing for a new system installation. 7Verifying physical hardware and connections. 7Network deployment. 7Verifying network information. 8Recording starting IP addresses. 8VLAN configuration (optional). 9VLAN configuration predeployment requirements. 9Configuring VLAN IDs before deployment. 9Recording VLAN IDs. 10Verifying the VLAN configuration. 10Verifying the switch configuration.10Recording iLO addresses. 10Recording system information.11License considerations.11Virtual Machine requirements. 12Management group quorum considerations. 13Preparing for an expansion system. 15Verifying physical hardware and connections. 15Network deployment. 15Verifying network information. 16Recording starting IP addresses. 16VLAN configuration (optional). 17VLAN configuration pre-expansion requirements. 17Configuring VLAN IDs before deployment. 17Recording VLAN IDs. 18Verifying the VLAN configuration. 18Recording iLO addresses. 18Licensing.19HC 250 hardware installation. 20Server warnings and cautions.20Space and airflow requirements. 20Temperature requirements.21Power requirements.21Grounding requirements. 22Installing the hardware.22Preparing the chassis.22Installing the chassis. 24Component installation.25Chassis options.26Disk drive numbering.272Contents
Cabling the system.28Configuring iLO. 32Powering on the system.32Related documentation. 32New system deployment. 33Configuring a new system.33Type of vCenter setup.33Remote vCenter setup options.33Prerequisites for remote vCenter setup. 34Configuring the Top-of-Rack switch. 36Configuring a laptop/workstation to access the system. 36Installing the VMware vCenter Server license (predeployment). 39OneView InstantOn. 40OneView InstantOn guidelines. 40Deploying a new system. 40Installing licenses.50Installing the VMware vCenter Server license. 50Installing the VMware vSphere license. 51Installing StoreVirtual VSA licenses. 51Completing post-deployment tasks.52Changing default passwords.52Managing storage. 52Verifying Quorum Witness (two-node configurations). 52Configuring VLAN IDs after deployment. 53Migrating the Management VM. 56Expansion system deployment. 57Configuring an expansion system.57Expansion requirements. 57Expansion scenarios.57Deploying an expansion system. 58Installing licenses.63Installing the VMware vSphere license. 63Installing StoreVirtual VSA licenses. 63Completing post-deployment tasks.64Changing default passwords.64Managing storage. 64Configuring EVC settings. 64Configuring VLAN IDs after deployment. 65Troubleshooting. 69Certificate error displays during login to vCenter Web Client.69Deployment process hangs during system configuration. 69Deployment process stalls with 57 seconds remaining and then times out after one hour. 70Network Connectivity Lost message displays on Host 1. 70A Health Status warning displays for the ESX cluster. 70Progress indicator for system configuration stops. 71HPE service communication error message displays.71Refresh cache error message displays.72Invalid user name and password message displays in vCenter. 74Manager is not running on all systems. 74Application performance on the Management VM decreases. 74Contents3
Online Help or Software Depot cannot be accessed. 75Updated Management VM IP address is not displayed. 75Node settings. 75Updating node boot options. 76Quick-reset.77Quick reset guidelines.77Performing a quick reset. 78Error message about vSphere HA support displays after a quick reset. 79Support and other resources.81Accessing Hewlett Packard Enterprise Support. 81Requesting support for HPE ConvergedSystem and HPE Hyper Converged products. 81Support Case Manager PINs. 83Customer self repair.84Remote support. 84Warranty information.84Regulatory information.85Belarus Kazakhstan Russia marking. 85Turkey RoHS material content declaration.86Ukraine RoHS material content declaration. 86Websites. 86Documentation feedback. 87System reference. 88System hardware. 88240-HC/242-HC hardware. 88HC 250 hardware. 89System software.91System documentation (in box). 92IP address requirements for expansion nodes. 92Network reference.94VLAN configuration example. 94Network mapping. 95CS 240-HC/242-HC hardware installation. 101Server warnings and cautions.101Space and airflow requirements. 101Temperature requirements.102Power requirements.102Grounding requirements. 103Installing the hardware.103Preparing the chassis.103Installing the chassis. 105Component installation.107Chassis options.108Disk drive numbering.109Cabling the system.109Configuring iLO.110Powering on the system. 110Related documentation.1114Contents
2016 Hewlett Packard Enterprise Development LPNoticesThe information contained herein is subject to change without notice. The only warranties for HewlettPackard Enterprise products and services are set forth in the express warranty statements accompanyingsuch products and services. Nothing herein should be construed as constituting an additional warranty.Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions containedherein.Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession,use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, ComputerSoftware Documentation, and Technical Data for Commercial Items are licensed to the U.S. Governmentunder vendor's standard commercial license.Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett PackardEnterprise has no control over and is not responsible for information outside the Hewlett PackardEnterprise website.AcknowledgmentsIntel , Itanium , Pentium , Intel Inside , and the Intel Inside logo are trademarks of Intel Corporation inthe United States and other countries.Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in theUnited States and/or other countries.Adobe and Acrobat are trademarks of Adobe Systems Incorporated.Java and Oracle are registered trademarks of Oracle and/or its affiliates.UNIX is a registered trademark of The Open Group.VMware , vCenter , and vSphere are registered trademarks or trademarks of VMware, Inc. in theUnited States and/or other jurisdictions.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
OverviewThe Hyper Converged 250 System for VMware vSphere system ("the system") is a virtualization systemthat combines compute and storage resources in the same chassis. It is designed to be deployed easilyand yet manage a variety of virtualized workloads in medium-sized businesses and enterprises.IMPORTANT:To ensure a successful deployment, review this installation guide first to gather the requiredinformation and prepare your networks. Failure to do so may result in deployment failure.Installing a new systemProcess overview:Procedure1. Prepare for the installation2. Install the hardware — HC 250 hardware or 240–HC/242–HC hardware3. Configure the new systemInstalling an expansion systemProcess overview:Procedure1. Prepare for the expansion2. Install the hardware — HC 250 hardware or 240–HC/242–HC hardware3. Configure the expansion system6Overview
Preparing for a new system installationComplete the following preparation tasks in their entirety. Hewlett Packard Enterprise suggests youcomplete all preparation tasks and gather all required settings before beginning the deployment. Failureto complete all preparation and installation tasks in order will likely result in deployment failure.Verifying physical hardware and connections Verify the following:You have either: Two 10 GbE network switches with four available ports per switchTwo 1 GbE network switches with eight available ports per switchNOTE:Hewlett Packard Enterprise does not provide the network switches as part of the productpurchase. Ensure that you purchase the switches in advance or use existing switches.The switches are IPv6-capable and are enabled for IPv6.NOTE:IPv6 is not required on the 1 GbE switch that may be used for iLO connections.If you use VLANs, the switches are configured to allow untagged traffic.You have the network cables for the connections between the system and the network switches.Hewlett Packard Enterprise does not provide these cables. For example: Eight 10 GbE DAC cablesEight patch cables and 16 SFP s16 CAT 5e (or better cables)You have two 220v power sources and power cables.You have a laptop or workstation that you can use to access OneView InstantOn on theManagement VM on Node 1.Network deploymentFor each network type (ESX, vSphere vMotion, Storage), you need to choose only the first IP address inthat group’s range. Once that IP address is chosen, OneView InstantOn automatically increments andcontiguously assigns the remaining IP addresses for that group.Preparing for a new system installation7
Verifying network information Complete the following:Confirm that you have the required number of contiguous IPv4 addresses for your configuration, asspecified in the table below.Verify that the 192.168.42.0/24 IPv4 address range is reserved and not used by other devices onyour network. The Hyper Converged system uses this IP address range for internal systemcommunication.If you are deploying multiple systems at the same time, verify that you have the required number ofIP addresses available for each system.For two-node systems: If you plan to expand to a three- or four-node system in the future, considerpreallocating the IP addresses for those nodes now (recommended but not required).The benefit is that you can configure those expansion nodes with IP addresses matching the othernode subnet ranges. If you choose not to preallocate IP addresses now, know that the expansionnodes will require IP addresses within the same subnet range used during initial systemdeployment.The table below shows the number of contiguous IP addresses that are required for each network in twonode, three-node, and four-node configurations.Table 1: Required number of contiguous IP addresses for a new systemNetwork typeTwo-nodeThree-nodeFour-nodeESX network345vSphere vMotion network234Storage network81114Total number of IP addresses131823Recording starting IP addressesIn the following table, record the starting IP address, which is the first IP address in a group's range, foreach network type.Network typeESX networkNOTE:When the IP addresses are assigned for the ESX network, theManagement VM IP address is assigned first.vSphere vMotion networkStorage network8Verifying network informationStarting IP address
VLAN configuration (optional)If VLANs are used, Hewlett Packard Enterprise recommends a minimum of three VLANs for the system.This does not include the number of VLANs that you may use for various production networks.If your network only supports tagged packets on 1 GbE or 10 GbE switches, and you plan to use VLANIDs, complete the steps in Configuring VLAN IDs before deployment on page 9. If you plan toconfigure VLAN IDs after deployment, see Configuring VLAN IDs after deployment on page 53.VLAN configuration predeployment requirements Required for networks where only tagged packets are supported on one or more switches.VLAN IDs from 0 - 4,095 are allowed.Use the vSphere ESX CLI to set the VLAN ID for the vSwitch VMkernel port ESXmgmt and thevSwitch Virtual Machine port group mgmtVMNetwork.Configure the vSphere hosts (system nodes) in the following order: Four-node system: vSphere host 4, 3, 2, 1 Three-node system: vSphere host 3, 2, 1 Two-node system: vSphere host 2, 1The Storage and vMotion VLAN IDs are configured during OneView InstantOn deployment of the newsystem.Configuring VLAN IDs before deploymentIf you are deploying more than one system chassis, complete the steps on each vSphere host in eachsystem chassis.Procedure1. Enable the Secure Shell and the EXSi Shell via either iLO or direct connection using an SUV cable:a. Log in to vSphere host 4.b. To access Customize System/View Logs, press F2.The Authorization Required dialog box appears.c. Enter root for the login name and hpcs200HC! for the password. Press Enter.The System Customization menu appears.d. Select Troubleshooting Mode Options and press Enter.The Troubleshooting Mode Options menu appears.e. Select Enable ESXi Shell and press Enter.NOTE:If the ESXi Shell is already enabled, the menu option displays Disable ESXi Shell.f. Select Enable SSH and press Enter.g. To exit Troubleshooting Mode Options, press Esc.h. To exit System Customization, press Esc.2. Add the VLAN ID via the ESXi Shell:a. To access the ESXi Shell, press Alt F1.b. Enter the username and password.c. Enter the following commands, where XXXX is the VLAN ID:esxcli network vswitch standard portgroup set –p mgmtVMNetwork –v XXXXesxcli network vswitch standard portgroup set –p ESXmgmt –v XXXXVLAN configuration (optional)9
NOTE:To query VLAN settings for all portgroups, enter the following command:esxcli network vswitch standard portgroup list3. To disable the Secure Shell and the ESXi Shell, repeat step 1 except select Disable ESXi Shell andDisable SSH.4. Repeat steps 1–3 for each vSphere host.Recording VLAN IDsvMotion VLAN IDManagement VLAN ID (ESXi, Management VM)NOTE:You must set this VLAN as untagged (PVID) on the switch portsused by the system.iSCSI VLAN ID (ESXi, Management VM, StoreVirtual VSA 2014)Verifying the VLAN configuration Complete the following:Configure the physical switch with the correct vMotion and iSCSI VLAN IDs before runningOneView InstantOn.Set the Management VM VLAN ID as untagged (PVID) on the switch ports used by the system.Verifying the switch configuration Complete the following:Configure the network switch ports to pass IPv6 traffic at layer 2.NOTE:IPv6 is not required on the 1 GbE switch that may be used for iLO connections.Enable IPv4 multicast on the network switch ports.Configure the network switches to allow untagged IPv6 and IPv4 traffic on the network switchports.Recording iLO addressesAlthough iLO is not required for daily use, Hewlett Packard Enterprise recommends that you configure itas part of the initial setup. iLO is required when recovering a node (see “Recovering a single node” in theuser guide).10Recording VLAN IDs
You must manually assign four IPv4 addresses. OneView InstantOn will not assign these IP addresses.IP address 1IP address 2IP address 3 (not used/required in a 2-nodeconfiguration)IP address 4 (not used/required in a 2-node or 3node configuration)Recording system informationGeneral settingsName of the StoreVirtual management group (required)NOTE:The default name is HP-HyperConv- xx , but you can change it.The guidelines for StoreVirtual management group names are: Up to 127 charactersMust begin with a letterAllowed characters: 0–9, a-z, A-Z, hyphen (-), underline ( ), andany of the following special characters \ ! @ # % & * ( ) \ \ ] }\[{?. DNS server IP address (required)NTP (optional)Mail settings (required)Server IP addressServer portSender addressRecipient addressLicense considerationsNOTE: VMware vSphere Essentials is supported for three-node configurations only.VMware vSphere Essentials does not support vMotion. It will be necessary to manually migratethe Management VM from the local datastore to the SAN volume after deployment.To access help documentation and complete the installation with fully licensed StoreVirtualVSAs, access to the Internet is required.Recording system information11
VMwareCentralizedManagementLicenseESXi Host License HC 250: Singlechassis (two orthree hosts)HC 250: Singlechassis (fourhosts)HC 250: Two,three, or fourchassis (6 - 16hosts)VMware vSphereEssentials KitVMware vSphereEssentialsNot SupportedNot SupportedNot SupportedVMware vSphere VMware vSphereEssentials Plus Kit Essentials PlusSupportedNot SupportedNot SupportedVMware vCenterServer StandardVMware vSphereStandardSupportedSupportedSupportedVMware vCenterServer StandardVMware vSphereRemote OfficeBranch Office andVMware vSphereRemote OfficeBranch OfficeAdvancedSupportedSupportedSupported1VMware vCenterServer StandardVMware vSphereEnterpriseSupportedSupportedSupportedVMware vCenterServer StandardVMware vSphereEnterprise PlusSupportedSupportedSupported1VMware vSphere Remote Office Branch Office and VMware vSphere Remote Office Branch OfficeAdvanced limit the number of Virtual Machines running per license pack. See Virtual machinerequirements to determine how many Virtual Machines the HC 250 system consumes on each host.Virtual Machine requirementsThe number of Virtual Machine licenses required varies when using VMware vSphere Remote OfficeBranch Office and VMware vSphere Remote Office Branch Office Advanced.Table 2: Number of VM licenses required per host for new system deployment andsystem expansionSystemHost numberNumber of Virtual Machinelicensed per host HC 250systemSystem 1Host 1 and Host 221Host 3 and Host 41Host 1 and Host 221Host 3 and Host 41System 2Table Cont
Hyper Converged 250 System for VMware vSphere Installation Guide Part Number: 867788-003 Published: December, 2016 Edition: 8 Abstract This document describes how to install the Hyper Converged 250 System for VMware vSphere and the ConvergedSystem 200-HC StoreVirtual system into a rack and configure it using the preinstalled OneView InstantOn .
ODMs). The driving force behind our two topics—converged and hyper-converged infrastructure—emerged from all of these trends. To understand where converged, hyper-converged and other solutions fit within the overall IT spending landscape, innovative all-flash array vendor SolidFire has an excellent graphic of where next-generation
Hyper-converged platforms deliver the high availability that organizations need for mission-critical workloads. Plus, hyper-converged infrastructure typically includes storage redundancy and the ability to mirror entire nodes or clusters. Organizations are also migrating their testing and development environments to hyper-converged infrastructure.
solution. It provides a step-by-step guidance on configuring a hyper-converged 2-node Hyper-V cluster using StarWind Virtual SAN to convert local storage of the Hyper-V hosts into a fault tolerant shared storage resource for Hyper-V. A full
HPE Hyper Converged 250 System. Réf. Libellé Prix Liste HT V. M0T03B Système HPE Hyper Converged 250 for VMware vSphere 2 668,00. N. Châssis de base pour 2 à 4 nœuds HPE Hyper Converged 250 ; inclut 2 alimentations 1400W, câbles d'alimentation, ventilation redondante,
Configuration Guide for Veeam ackup Replication ith the HPE Hyper Converged 250 System 2016 Veeam Software 3 Intended audience This guide is intended for those involved in the design, acquisition and implementation of data protection solutions for the Hewlett Packard Hyper Converged 250 System (HC 250) . It was written for IT generalists
the Powershell CLI commands, see Install the ASAv on Hyper-V Using the Command Line, page 68. For instructions to install using the Hyper-V Manager, see Install the ASAv on Hyper-V Using the Hyper-V Manager, page 68 . Hyper-V does not provide a serial console option. You can manage Hyper-V through SSH or ASDM over the management interface.
Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original
Tulang Humerus Gambar 2.1 Anatomi 1/3 Tulang Humerus (Syaifuddin, 2011) Sulcus Intertubercularis Caput Humeri Collum Anatomicum Tuberculum Minus Tuberculum Majus Collum Chirurgicum Crista Tubeculi Majoris Crista Tuberculi Majoris Collum Anatomicum Collum Chirurgicum Tuberculum Majus . 4. Otot-otot Penggerak Pada Bahu Menurut Syaifuddin (2011), otot- otot bahu terdiri dari : a. Gerakan fleksi .
