Connecting to HPE OneSphere for the first time

Last updated 18 April, 2019

Connecting HPE OneSphere 

Connecting to your VMware vSphere, KVM, or HPE OneView environment allows you to configure the initial connection between HPE OneSphere and your environment.

After the connection has been made, you can deploy virtual machines from HPE OneSphere to a VMware vCenter cluster or KVM server in a specified region and zone, and for VMware vCenter and HPE OneView, collect cost and usage information about your private cloud.

Downloading HPE OneSphere Connect and adding a private cloud zone

Use the following procedure to add a zone in HPE OneSphere to connect to your existing private cloud environment. You can then launch deployments from HPE OneSphere to a VMware vCenter cluster or KVM hypervisor(s) in a specified region.

Prerequisites
  • An account on the HPE OneSphere portal with administrator privileged access

  • The administrator configured a VMware vCenter or KVM environment for use with HPE OneSphere. (If you plan to connect an HPE OneView environment, see Downloading HPE OneSphere Connect and adding an appliance.)

For detailed configuration and prerequisites information, see Network configuration for HPE OneSphere Connect, Network configuration for KVM servers, and the HPE OneSphere Support Matrix.

Procedure
  1. Launch the HPE OneSphere URL in a supported web browser.

    The HPE OneSphere URL and login information is provided in an email sent by Hewlett Packard Enterprise after your account has been created. If you do not have this information, contact your Hewlett Packard Enterprise representative.

  2. Enter the username provided by Hewlett Packard Enterprise to log in to your HPE OneSphere account. For more information, see Setting up your account and managing users.
  3. From the HPE OneSphere main menu, select Providers.
  4. From the Providers screen, select Private Zones.
  5. From the Private Zones screen, click the green plus icon.
  6. Click the following option on the Create Zone panel.

    Connect Existing Clusters/Servers

    Connect existing VMware clusters or KVM servers that are already in use outside of HPE OneSphere.

  7. Click Download Connect for Windows or Download Connect for Mac.
  8. Save the HPE OneSphere Connect file for Windows (HPE-OneSphere-Connect-1.0.0-(x)-win.zip) or Mac OS X (HPE-OneSphere-Connect-1.0.0-(x)-mac.zip). The size of the zip file is approximately 32 MB.
  9. After saving the HPE OneSphere Connect file, you can use it to connect to your VMware vSphere private cloud or connect to your KVM private cloud.

Downloading HPE OneSphere Connect and adding an appliance 

Use the following procedure to add an appliance in HPE OneSphere to provide access to the server resources managed by HPE OneView. An appliance is an onboarded HPE OneView instance.

  • If you have not already created a region, you will launch the HPE OneSphere Connect application to create a region to connect to your HPE OneView appliance(s). A region provides a communication channel to one or more connected HPE OneView appliances.

  • If you already created a region (for example, to connect to a VMware vSphere environment), you can use the existing region to connect your HPE OneView appliance(s).

Prerequisites
  • An account on the HPE OneSphere portal with administrator privileges

  • Login credentials for an HPE OneView user that is assigned Infrastructure Administrator and Software Administrator roles

For detailed configuration and prerequisites information, see Network configuration for HPE OneSphere Connect and the HPE OneSphere Support Matrix.

Procedure
  1. Launch the HPE OneSphere URL in a supported web browser.

    The HPE OneSphere URL and login information are provided in an email sent by Hewlett Packard Enterprise after your account has been created. If you do not have this information, contact your Hewlett Packard Enterprise representative.

  2. Enter the username provided by Hewlett Packard Enterprise to log in to your HPE OneSphere administrator account. For more information, see Setting up your account and managing users.
  3. From the HPE OneSphere main menu, click Providers.
  4. From the Providers screen, click Appliances.
  5. From the Appliances screen, click the green plus icon.
  6. From the Add Appliance screen, in the Region drop-down list, select an existing region, or select Create New Region.

    If there is no region listed on the Region drop-down list, you must create a region using HPE OneSphere Connect to set up the communication channel. After the region is created, it will appear in the drop-down list.

    If you select an existing Region that does not have an HPE OneSphere Region Controller virtual machine (but might have an HPE OneSphere Zone Controller virtual machine that connects HPE OneSphere to a VMware vSphere environment), you must use HPE OneSphere Connect to deploy an HPE OneSphere Region Controller VM in the existing region before communications will be established with the remote HPE OneView system.

    NOTE:

    If a region with an associated HPE OneSphere Region Controller virtual machine already exists, select the region and skip to step 10.

  7. Click Download Connect for Windows or Download Connect for Mac.
  8. Save the HPE OneSphere Connect file for Windows (HPE-OneSphere-Connect-1.0.0-(x)-win.zip) or Mac OS X (HPE-OneSphere-Connect-1.0.0-(x)-mac.zip). The size of the zip file is approximately 32 MB.

    Launch HPE OneSphere Connect to create a region to connect to your HPE OneView appliance.

    Once the region is created, it will appear in the drop-down list.

  9. After running HPE OneSphere Connect, navigate to the Providers screen, then click Appliances and click the green plus icon.
  10. From the Add Appliance screen, select the newly created region from the Region drop-down list.
  11. Enter the name of the HPE OneView appliance.

    The appliance name can contain only alphanumeric characters and hyphens (-). It cannot contain spaces or special characters, for example: (), <>={}(),";& .

  12. In the HPE OneView section, enter the hostname or IP address of the HPE OneView appliance that will be connected to your private cloud.
  13. Enter the username and the password for an Infrastructure Administrator, Server Administrator, Server Profile Administrator, or Server Profile Architect account on the HPE OneView appliance.
  14. Click Add Appliance. It takes approximately five minutes for the appliances to be added.

During this process the state of the appliance will be updated.

  • If the state clears, the appliance was successfully added.

  • If the state becomes Error Enabling Comms, HPE OneSphere is unable to access the HPE OneView system.

    Check the IP address of the HPE OneView system. If it is incorrect, delete the appliance and recreate it with the correct HPE OneView details.

    A state of Error Enabling Comms might mean that there network connectivity issues between HPE OneSphere and the HPE OneView system.

  • If the state becomes Error Validating Creds, HPE OneSphere is unable to access the HPE OneView system using the credentials provided.

    Check the specified credentials. If they are incorrect, delete the appliance and recreate it with the correct HPE OneView details.

Using HPE OneSphere Connect to connect to your VMware vSphere private cloud

Use the following procedure to connect HPE OneSphere to an existing ESXi cluster.

Prerequisites

The administrator:

Procedure
  1. Launch the HPE OneSphere .exe or .app file.

    HPE OneSphere Connect is downloaded from the HPE OneSphere Create Zone screen.

  2. Click Get Started.
  3. In HPE OneSphere Account, enter the HPE OneSphere portal URL provided by Hewlett Packard Enterprise, then click Continue.

    Example: https://[your-account].hpeonesphere.com

  4. Sign in using the username and password for your HPE OneSphere Account.
  5. On the Connection Types screen, select Connect Existing Clusters/Servers.
  6. On the Infrastructure Location in HPE OneSphere screen:
    1. Click the Region drop-down list and select an existing region.
    2. Click the Type of Zone drop-down list and select the zone type.
    3. Click the Private Zone drop-down list and select the existing zone.

    Or, create a region by selecting Create New Region, then enter the following details.

    1. Enter a name for the region where your VMware environment is located, for example, US-Denver.
      NOTE:

      The region name cannot contain spaces, and it cannot contain more than 18 characters.

    2. Drag the dot on the map to the approximate location of your private cloud.
    3. Click the Type of Zone drop-down list and select the zone type, such as vCenter.
    4. Enter a name for the name of the zone, for example, ESXi-US-Zone.
      NOTE:

      The zone name cannot contain underscores and spaces, and it cannot contain more than 18 characters.

  7. Click Continue.
  8. On the vCenter Sign-In screen, enter the vCenter hostname or IP address and the vCenter login credentials for the account that manages your VMware ESXi private cloud platform.

    If you plan to connect multiple data centers, then specify data center Administrator credentials.

    If you enter a hostname (short name or long name) and the error "Invalid IP or URL supplied" is returned, then enter the IP address.

    See Required permissions for VMware vSphere user accounts and ensure that the vCenter administrator or data center administrator account is assigned the required permissions.

    NOTE:

    Ensure that the vCenter cluster name does not contain special characters, and is created outside of a folder in vSphere. If the cluster is already created inside of a folder, move the cluster outside of the folder before enabling the cluster. (You enable the cluster after connecting it to HPE OneSphere.)

    HPE OneSphere currently supports connecting to a vCenter Server that is configured with port 443 only.

  9. Click Sign In.
  10. On the vCenter VM Location screen:
    1. Enter a name for the HPE OneSphere Controller virtual machine instance to be deployed.

      You will see an immediate response if the name is different than any names previously used. If the name already exists, HPE OneSphere will hang with no errors.

    2. Check Reset HPE OneSphere controller virtual machine password, then enter a password.

      Hewlett Packard Enterprise recommends that you enter a password. If you do not enter a password, a default password is set. Contact HPE Support to change the default password after the virtual machine is deployed.

      IMPORTANT:

      Be sure to securely retain the new password. If the password is lost, it cannot be reset by you or by HPE Support. In that case, the HPE OneSphere Controller will need to be removed from your environment and redeployed.

    3. Select the Cluster, shared Datastore, and Network where the virtual machine instance will be deployed.

      Hewlett Packard Enterprise recommends connecting the HPE OneSphere Controller virtual machine to a VMware vSphere Distributed Switch (vDS)-based port group network that has connectivity to the Internet and the vCenter server, and is isolated from the port group network used for deployment of virtual machines. This virtual machine establishes a secure https communication channel between your vCenter private cloud platform and the HPE OneSphere cloud management service.

  11. Click Continue.
  12. On the vCenter vSphere Data Network screen, select vSphere Distributed Switch from the drop-down list and select the vSphere Distributed Switch that is connected to all hosts within a vCenter data center. The port groups on the selected VDS are imported as networks in HPE OneSphere and will be used for VM deployments.
    NOTE:

    HPE OneSphere Connect lists all the vSphere Distributed Switches available in the vCenter. Log in to vCenter and note the name of the VDS for the specified data center before selecting it on the vCenter VM Location screen.

  13. Click Continue.
  14. On the HPE OneSphere Controller screen, configure the network settings of the virtual machine so that the virtual machine in the vCenter can communicate with HPE OneSphere.
    1. Click the IP address assignment drop-down list and select the IP address assignment type (DHCP or Static) depending on your requirements. If you select Static, enter the network details including IP address, Subnet mask, Gateway, and DNS server.
    2. (Optional) Enter a proxy to establish a connection between the vCenter and HPE OneSphere. (Do not enter the system proxy, which is configured from your local Windows client PC to other networks.)
  15. Click Continue.
  16. On the HPE Private Cloud Infrastructure Connection Summary screen, review the connection details.
    1. To change any information, click Back (green return icon at the top-left corner) of the Summary screen and edit the information before connecting.
    2. If the displayed information on the Summary screen is correct, click Connect.
      NOTE:

      Do not close the Connect screen during this operation.

Troubleshooting

The page navigates to Connecting all the bits for your HPE Private Cloud. The progress bar provides the percentage of time taken to establish a connection between vCenter and HPE OneSphere.

This process may take up to 90 minutes. If after 90 minutes the screen appears hung, open the log file using a text editor. In Windows, the HPE OneSphere Connect log file is located in C:\Users\<windowsLoginusername>\hpeConnect\HPEconnect.log. In macOS, the log file is located in %userprofile%\HPEconnect\HPEconnect.log.

New log entries are written at least once every minute. If the application errors out or the log file is no longer being updated, you must troubleshoot the problem.

  • If the application displays a timeout or not responding error message, click Back several times, then click Connect to try again.

  • If the application stops working after a few minutes with no error message displayed and the last hpeConnect.log entry is “Connection 404,” the problem may be caused by using the same virtual machine name that was used on a previous connection attempt. Clean up remnant information in vCenter, rename the log file with a date stamp, and if a “zones” folder exists, delete it. Then try again.

  • If the application stops working after an hour or more with no error message displayed and the last hpeConnect.log entry is:

    • "Waiting for the OneSphere controller to boot”—The problem might be remnant images or other content in vCenter from a previous connection attempt. Clean up vCenter and try again.

    • “Waiting for virtual machine to boot”—The problem might be incorrect network or IP address information. Make sure that the information you entered is correct and try again.

After a successful connection, the You're all set! screen appears. Click Take me there to proceed to the HPE OneSphere portal log in screen; otherwise, click Connect another environment to establish a new connection.

Using HPE OneSphere Connect to connect to your KVM private cloud

Use the following procedure to connect to an existing KVM environment.

Prerequisites
Procedure
  1. Launch the HPE OneSphere Connect .exe or .app file.

    HPE OneSphere Connect is downloaded from the HPE OneSphere Create Zone screen.

  2. Click Get Started.
  3. In HPE OneSphere Account, enter the HPE OneSphere web portal URL provided by Hewlett Packard Enterprise, then click Continue.

    Example: your-account.hpeonesphere.com

  4. Sign in using the administrator user name and password for your HPE OneSphere Account.
  5. On the Infrastructure Location in HPE OneSphere screen, click the Region drop-down list and create a new region by selecting Create New Region, then enter the following details.
    1. Enter a name for the region where your KVM hypervisor is located, or use an existing region. For example: US-Denver.

      NOTE:

      Region name cannot contain spaces. It cannot be more than 18 characters.

    2. Drag the dot on the map to the approximate location of your private cloud region.
    3. Click the Type of Zone drop-down list and select KVM.
    4. Enter a name for the zone, for example, KVM-US-Zone.

      NOTE:

      Zone name cannot contain underscore and spaces. It cannot be more than 18 characters.

    5. Click Continue.
  6. On the KVM Host Sign-In screen: 
    1. Click Add Host to enter host details.
    2. If you are connecting one KVM host, enter the hostname or IP address of the first KVM host and the username and password for the account that manages your KVM private cloud platform, then skip to step 6f.
    3. If you are connecting two to ten KVM hosts that are not in a consecutive IP address range, enter the hostname or IP address of the first KVM host and the username and password for the account that manages your KVM private cloud platform.
    4. (Optional) Check Use the same credentials for next host/IP to pre-populate the username and password for each additional host.
    5. (Optional) Click IP Range if the IP addresses of your KVM hosts are consecutive. Enter the Starting IP address and the Ending IP address of the KVM hosts in the range, and the login credentials.

      The username and password must be the same for all KVM hosts in the IP range.

    6. Click Sign In.
    7. (Optional) Click Add Host again to enter details about the next KVM host.
    8. (Optional) To remove any hosts that you do not want to connect to HPE OneSphere, click the X icon next to the host name or IP address.
    9. When you have finished adding KVM hosts, click Continue.
  7. On the KVM Host Configuration screen, enter the proxy details and optional credentials to establish a connection between the KVM hypervisor and HPE OneSphere, then click Sign In.

    NOTE:

    Do not enter the system proxy as configured on your client PC or host. The system proxy that you specify in this step is the proxy used on the local network consumed by the KVM host that you are connecting to HPE OneSphere.

  8. On the HPE Private Cloud Infrastructure Connection Summary screen, review the connection details.
    1. To change any information, click Back (green return icon at the top left corner) of the Summary screen and edit the information before connecting.
    2. If the displayed information on the Summary screen is correct, click Connect.

      NOTE:

      Do not close the Connect screen during this operation.

The page navigates to Connecting all the bits for your HPE Private Cloud. The progress bar provides the percentage of time taken to establish a connection between KVM hypervisor and HPE OneSphere.

If any errors occur during this onboarding process, see the log file for more information.  In Windows, the HPE OneSphere Connect log file is located in C:\Users\<windowsLoginusername>\hpeConnect\HPEconnect.log. In macOS, the log file is located in %userprofile%\HPEconnect\HPEconnect.log.

After a successful connection, You're all set! screen appears. Click Take me there to proceed to the HPE OneSphere application log in screen; otherwise, click Connect another environment to establish a new connection.

Using HPE OneSphere Connect to create a region to connect to your HPE OneView environment 

Connecting to your HPE OneView appliance creates a region connector VM called the HPE OneSphere Controller and establishes a secure connection between HPE OneSphere and your environment. After the connection has been made, HPE OneSphere will collect cost and usage information about the resources managed by your HPE Oneview appliance.

NOTE:

After you connect to an HPE OneView appliance, see Managing private cloud providers: HPE OneView to complete the configuration.

Prerequisites

The administrator:

  • Downloaded the HPE OneSphere Connect .zip file on the Add Appliance screen, and extracted the .exe or .app file.

  • Ensured that a VMware vSphere environment is available. The HPE OneSphere region controller VM will be deployed to this environment. The same VMware vSphere environment can also be connected to HPE OneSphere as a private zone.

  • Ensured that time synchronization with HPE OneView appliances is properly configured.

Procedure
  1. Launch the HPE OneSphere Connect .exe or .app file.

    HPE OneSphere Connect is downloaded from the HPE OneSphere Add Appliance screen.

  2. Click Get Started.
  3. In HPE OneSphere Account, enter the HPE OneSphere Portal URL provided by Hewlett Packard Enterprise, then click Continue.

    Example: https://[your-account].hpeonesphere.com

  4. Sign in using the username and password for your HPE OneSphere Account.
  5. On the Connection Types screen, select Connect an Appliance.

    This option connects HPE OneSphere to an HPE OneView appliance.

  6. On the Infrastructure Location in HPE OneSphere screen, click the Region drop-down list.
    1. If a region does not exist, select Create New Region, then enter the following details.
      • Enter a name for the new region where your HPE OneView appliance is located. For example, US-Denver.

        NOTE:

        The region name cannot contain spaces, and it cannot contain more than 18 characters.

      • Drag the dot on the map to the approximate location of your HPE OneView appliance.

      • Click Continue.

    2. If a region already exists but it does not contain an HPE OneSphere Region Controller virtual machine, select the existing region.

      If you select an existing region in which you previously deployed an HPE OneSphere Region Controller VM that has been removed, HPE OneSphere Connect informs you that a region connection already exists, and asks if you want to continue. Click Yes.

  7. On the vCenter Sign-In screen, enter the vCenter hostname or IP address and the vCenter login credentials for the account that manages your VMware ESXi private cloud platform.
  8. Click Sign In.
  9. On the vCenter VM Location screen, enter a Name for the HPE OneSphere Controller virtual machine to be deployed, and select the Cluster, shared Datastore, and Network where the virtual machine will be deployed.

    Hewlett Packard Enterprise recommends connecting the HPE OneSphere Controller virtual machine to a VMware vSphere Distributed Switch (vDS)-based portgroup network that has connectivity to the Internet and the vCenter Server. HPE also recommends selecting a highly available datastore, such as a shared datastore. This virtual machine instance establishes a secure communication channel between your HPE OneView Appliance and the HPE OneSphere cloud management service.

  10. Click Continue.
  11. On the HPE OneSphere Controller screen, configure the network settings of the virtual machine so that the virtual machine in the vCenter can communicate with HPE OneSphere and to time services.
    1. Click the IP address assignment drop-down list and select the IP address assignment type (DHCP or Static) depending on your requirements. If you select Static, enter the network details including IP Address, Subnet Mask, Gateway, and DNS Server.
    2. Enter the URL of a Proxy to establish a connection between the vCenter and HPE OneSphere, and optionally a username and password for the proxy server. (Do not enter the system proxy, which is configured from your local client PC to other networks.)
  12. Click Continue.
  13. On the HPE Private Cloud Infrastructure Connection Summary screen, review the connection details.
    1. To change any information, click Back (green return icon at the top left corner) of the Summary screen and edit the information before connecting.
    2. If the displayed information on the Summary screen is correct, click Connect.

      NOTE:

      Do not close the Connect screen during this operation.

    The page navigates to Connecting all the bits for your HPE Private Cloud. The progress bar provides the percentage of time taken to establish a connection between HPE OneSphere and the HPE OneSphere Region Controller VM.

    If any errors occur during this onboarding process, see the log file for more information.  In Windows, the HPE OneSphere Connect log file is located in C:\Users\<windowsLoginusername>\hpeConnect\HPEconnect.log. In macOS, the log file is located in %userprofile%\HPEconnect\HPEconnect.log.

    After a successful connection, You're all set! screen appears. Click Take me there to proceed to the HPE OneSphere portal login screen; otherwise, click Connect another environment to establish a new connection.

    NOTE:

    After you connect to an HPE OneView region, see Managing private cloud providers: HPE OneView to complete the configuration.

Results of running HPE OneSphere Connect

When you finish entering information about your on-premises environment in the HPE OneSphere Connect application and you click Connect, the application:

  • Connects the machine on which HPE OneSphere Connect is running (the jump server) to the HPE OneSphere management service.

  • For VMware vCenter environments:

    • Downloads the HPE OneSphere Controller image to the jump server. This image is a Linux virtual machine appliance OVA file with default credentials.

      IMPORTANT:

      HPE strongly recommends that you change the default credentials. See Managing the HPE OneSphere Controller.

    • (VMware vCenter only) Deploys the HPE OneSphere Controller OVA file to the newly created zone in the vCenter cluster.

    • Boots the HPE OneSphere Controller and pairs it with the HPE OneSphere management service.

    • (VMware vCenter only) Enables the target VMware ESXi cluster.

    • Discovers vSphere VM templates on the shared datastore (if they exist) and imports metadata into the HPE OneSphere Catalog.

  • For HPE OneView environments:

    • Downloads the HPE OneSphere Controller image to the jump server. This image is a Linux virtual machine appliance OVA file with default credentials.

      IMPORTANT:

      HPE strongly recommends that you change the default credentials. See Managing the HPE OneSphere Controller.

    • Deploys the HPE OneSphere Controller OVA file to the newly created region in the vCenter cluster.

    • Boots the HPE OneSphere Controller and pairs it with the HPE OneSphere management service.

    • Provides a network path from HPE OneSphere to onboarded HPE OneView appliances for gathering inventory and performance data.

  • For KVM environments:

    • Downloads a script to configure KVM nodes as KVM compute nodes.

    • Connects to each server and executes the script that downloads an RPM/deb for installing agents.

When the cluster or server is connected and enabled, any existing virtual machines running on the cluster, as well as existing vSphere Distributed Switch (VDS)-based networks and datastores (for ESXi) associated with the cluster or server are discovered automatically and become part of your HPE OneSphere environment.

NOTE:

You enable the cluster after connecting it to HPE OneSphere. See "Updating a zone" in Managing private cloud providers.

The administrator can now configure VM network IP address management (DHCP or HPE OneSphere static range of IP addresses).

(Optional) Creating multiple users to connect to VMware vSphere 

The following procedure describes an optional configuration that creates and configures two users in VMware vSphere. You can then create two zones in HPE OneSphere and connect each zone to the vCenter environment using a different user account. This configuration allows you to separate consumer access to resources in the same vCenter.

For example, if you have a vCenter datacenter with two clusters, and each cluster contains multiple datastores, you may want to restrict HPE OneSphere consumers from accessing all datastores.

By default, if you enter VMware vCenter Administrator credentials in HPE Connect when connecting HPE OneSphere to a private zone, then all clusters that belong to all datacenters in the vCenter are displayed in HPE OneSphere. If you enter Datacenter Administrator credentials, then only the clusters in that datacenter are displayed.

Prerequisites
  • HPE OneSphere account with administrator role

  • VMware vSphere account with administrator permissions

Procedure
  1. In VMware vSphere, create user A and user B.
  2. Assign root level permissions to both user A and user B in the vCenter and datacenter without propagating the permissions to children.
  3. Assign administrator permissions:
    1. To user A on cluster 1 and the cluster datastores. Propagate the permissions to children.
    2. To user B on cluster 2 and the cluster datastores. Propagate the permissions to children.
  4. In the folder containing the VMware vSphere Distributed Switch (VDS):
    1. Assign administrator permissions to user A and propagate to children.
    2. Assign administrator permissions to user B and propagate to children.
  5. Create two folders (template folder A and template folder B) for storing templates.
  6. Move all of the templates that belong to cluster 1 to template folder A.
  7. Move all the templates that belong to cluster 2 to template folder B.
  8. Assign administrator permissions:
    1. To user A on template folder A and propagate to children.
    2. To user B on template folder B and propagate to children.

Next step: Create two zones in HPE OneSphere and connect each zone to the vCenter environment using a different user account.

Managing the HPE OneSphere Controller

Connecting HPE OneSphere to a vCenter Server using HPE OneSphere Connect deploys a new Linux virtual machine as an Open Virtual Appliance (OVA) in the vCenter Server. This appliance is called the HPE OneSphere Controller (sometimes called the HPE VMware Gateway Appliance). The HPE OneSphere Controller is configured to connect your vSphere infrastructure and the HPE OneSphere management service.

The management services running in the HPE OneSphere Controller are fully monitored and managed by HPE OneSphere using a secure https channel communication agent that is included with the OVA. The HPE OneSphere Controller is completely stateless and allows HPE OneSphere to restart it if required. A stateless appliance means:

  • If the HPE OneSphere Controller is unavailable, the vSphere cluster continues running under the management of the vCenter servers. End users cannot deploy new resources through HPE OneSphere, because HPE OneSphere is no longer able to communicate with the on-premises vSphere infrastructure. However, new VMs can still be deployed and made available using vCenter/vSphere, and they will later be discovered by HPE OneSphere.
  • If the HPE OneSphere Controller needs to be restarted or even redeployed, no metadata will be lost because they do not persist in the HPE OneSphere Controller. The restarted or redeployed appliance will rediscover the current infrastructure and run normally.

High availability of the HPE OneSphere Controller is provided using the vSphere HA feature, because the appliance is deployed as an OVA in a vSphere cluster. This means that if the ESXi host on which the HPE OneSphere Controller is running goes down, the HPE OneSphere Controller will automatically be restarted on another ESXi host (if the HPE OneSphere Controller is deployed on a shared datastore).

Status updates from the virtual machines will not be visible on the HPE OneSphere portal if the HPE OneSphere Controller is down. However, HPE monitors the status of the appliance and will inform customers if connectivity is lost for several hours.

NOTE:

The customer is responsible for documented manual configuration changes, including changing the HPE OneSphere Controller default password. Updating and patching the operating system on the HPE OneSphere Controller is performed by HPE Support.

Do not install additional software in the HPE OneSphere Controller unless it is documented by HPE.

IMPORTANT:

HPE recommends that you change the HPE OneSphere Controller default password before performing any configuration on the appliance.

Changing the HPE OneSphere Controller password

Using HPE OneSphere Connect, you can set the password for the HPE OneSphere Controller virtual machine when it is deployed in your VMware vCenter environment. If you do not specify a password in the Connect application, a default password is set for the virtual machine.

If you did not specify a password in HPE OneSphere Connect, HPE recommends that you contact HPE Support to change the default password, depending on your organization's security policies.

Procedure
  1. Contact HPE support to establish a remote or local session with your environment.

    HPE support will log in to the HPE OneSphere Controller in your environment using the default password, and will enter the change password command.

  2. Change the password to a new value.

    IMPORTANT:

    Be sure to securely retain the new password. If the password is lost, it cannot be reset. The HPE OneSphere Controller will need to be removed from your environment and redeployed.

Validating the connection

After connecting HPE OneSphere to your private cloud, validate that the connection was successful.

Procedure
  1. Monitor the progress of the OVA file download or KVM script in the HPE OneSphere Connect application or by viewing the log file.

    In Windows, the HPE OneSphere Connect log file is located in C:\Users\<windowsLoginusername>\hpeConnect\HPEconnect.log. In macOS, the log file is located in %userprofile%\HPEconnect\HPEconnect.log.

  2. (VMware vCenter only) As the file downloads, log in to vCenter and monitor the creation of the instance in the Datastore specified when you connected HPE OneSphere to your vCenter environment.
  3. Click Take me there from the HPE OneSphere Connect application or use a supported browser to access HPE OneSphere.
  4. Log in using the credentials provided by Hewlett Packard Enterprise.
  5. For VMware vSphere and KVM connections:
    1. From the HPE OneSphere main menu, select Providers.
    2. Click Private Zones.
    3. Select the newly created zone, then click Update Zone.
    4. Verify that Connect All Available Clusters is enabled.
  6. For HPE OneView connections:
    1. From the HPE OneSphere main menu, select Providers.
    2. Click Appliances.
    3. Wait for "Unknown" or other status to disappear from the area next to the name of the appliance.

Recovering the HPE OneSphere Controller VM

If the HPE OneSphere Controller VM crashes, you can recover the VM using HPE OneSphere Connect.

Prerequisites
  • HPE OneSphere Controller VM is deployed in a VMware vCenter private cloud environment

Procedure
  1. Launch the HPE OneSphere Connect .exe or .app file.
  2. Click Get Started.
  3. In HPE OneSphere Account, enter the HPE OneSphere portal provided by Hewlett Packard Enterprise, then click Continue.
  4. Sign in using the username and password for your HPE OneSphere Account.
  5. On the Infrastructure Location in HPE OneSphere screen:
    1. Click the Region drop-down list and select the region which corresponds to your zone.
    2. Click the Type of Zone drop-down list and select the vCenter zone type.
    3. Click the Private Zone drop-down list and select the existing zone that is already connected to the vCenter. 
  6. Click Continue to recover the HPE OneSphere Controller VM.
  7. On the vCenter Sign-In screen, the vCenter hostname or IP address appears by default. Enter the vCenter login credentials for the account that manages your VMware ESXi private cloud platform. If you plan to connect multiple data centers, then specify datacenter Administrator credentials.
  8. Click Sign In.
    A message is displayed stating that this environment is already connected. Click Sign In again to continue.
  9. On the vCenter VM Location screen, a name for the HPE OneSphere Controller virtual machine instance will be displayed by default. Select the cluster, shared datastore, and network where the virtual machine instance will be deployed. 

    NOTE:

    Select the same cluster for recovery. Choosing a different cluster will not remove the old VM and it will require manual cleanup.

  10. On the vCenter vSphere Data Network screen, select vSphere Distributed Switch from the drop-down list and select the vSphere Distributed Switch that is connected to all hosts within a vCenter datacenter. The port groups on the selected VDS are imported as networks in HPE OneSphere and will be used for VM deployments.
  11. Click Continue
  12. On the HPE OneSphere Controller screen, configure the network settings of the virtual machine so that the virtual machine in the vCenter can communicate with HPE OneSphere.
    1. Click the IP address assignment drop-down list and select the IP address assignment type (DHCP or Static) depending on your requirements. If you select Static, enter the network details including IP address, Subnet mask, Gateway, and DNS server.
    2. Enter a proxy to establish a connection between the vCenter and HPE OneSphere. (Do not enter the system proxy, which is configured from your local Windows client PC to other networks.)
  13. Click Continue
  14. On the HPE Private Cloud Infrastructure Connection Summary screen, review the connection details.
    1. To change any information, click Back (green return icon at the top left corner) of the Summary screen and edit the information before connecting.
    2. If the displayed information on the Summary screen is correct, click Connect.
    The page navigates to Connecting all the bits for your HPE Private Cloud. The progress bar provides the percentage of time taken to establish a connection between vCenter and HPE OneSphere.

    If any errors occur during this onboarding process, see the log file for more information. In Windows, the HPE OneSphere Connect log file is located in C:\Users\<windowsLoginusername>\hpeConnect\HPEconnect.log. In macOS, the log file is located in %userprofile%\HPEconnect\HPEconnect.log.

    After a successful connection, You're all set! screen appears. Click Take me there to proceed to the HPE OneSphere application log in screen; otherwise, click Connect another environment to establish a new connection.

Recovering services on a connected KVM server

You can recover services on a connected KVM server using HPE OneSphere Connect.

NOTE:

You can recover services on only one server at a time.

The recovery process brings up only services that are down. Those services must have been deployed during the activation of the KVM server.

Prerequisites
  • HPE OneSphere is connected to a KVM private cloud environment

Procedure
  1. Launch the HPE OneSphere Connect .exe or .app file.
  2. Click Get Started.
  3. In HPE OneSphere Account, enter the HPE OneSphere portal provided by Hewlett Packard Enterprise, then click Continue.
  4. Sign in using username and password for your HPE OneSphere Account.
  5. On the Infrastructure Location in HPE OneSphere screen:
    1. Click the Region drop-down list and select the region that corresponds to your zone.
    2. Click the Type of Zone drop-down list and select the KVM zone type.
    3. Click the Private Zone drop-down list and select the existing zone that is already connected to the server. 
    4. Click Continue.
  6. On the KVM Sign-In screen, enter the following details:
    1. Enter the hostname or the IP address of the server that must be recovered and the KVM login credentials for the account that manages your KVM private cloud platform.
    2. Enter the proxy details to establish a connection between the KVM hypervisor and HPE OneSphere.
  7. Click Sign In.
    A message is displayed stating that this serveris already connected. Click Sign In again to continue.
  8. On the HPE Private Cloud Infrastructure Connection Summary screen, review the connection details.
    1. To change any information, click Back (green return icon at the top left corner) of the Summary screen and edit the information before connecting.
    2. If the displayed information on the Summary screen is correct, click Connect.

    The page navigates to Connecting all the bits for your HPE Private Cloud. The progress bar provides the percentage of time taken to establish a connection between KVM hypervisor and HPE OneSphere.

    If any errors occur during this onboarding process, see the log file for more information. In Windows, the HPE OneSphere Connect log file is located in C:\Users\<windowsLoginusername>\hpeConnect\HPEconnect.log. In macOS, the log file is located in %userprofile%\HPEconnect\HPEconnect.log.

    After a successful connection, You're all set! screen appears. Click Take me there to proceed to the HPE OneSphere application log in screen; otherwise, click Connect another environment to establish a new connection.