HPE Synergy Image Streamer 4.0 User Guide

Transcription

1 HPE Synergy Image Streamer 4.0 User Guide Abstract This guide describes the Image Streamer architecture, features, interfaces, and working environment. It describes the server deployment process using Image Streamer, the purpose, and life cycle of Image Streamer artifacts and the actions you can perform using them. It also includes information about recommendations for using Image Streamer resources, authentication, authorization and troubleshooting information for Image Streamer. Part Number: P Published: December 2017 Edition: 1

2 Copyright 2017 Hewlett Packard Enterprise Development LP Notices The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such 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 contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. Acknowledgments Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

3 Contents HPE Synergy Image Streamer first-time setup... 7 Introduction to Image Streamer... 8 Image Streamer overview...8 Image Streamer appliance terminology...8 Image Streamer building blocks... 9 Image Streamer architecture User roles for Image Streamer Deployment using Image Streamer...12 Artifacts About Plan Scripts...14 About custom attributes...14 Types of custom attributes...14 String...15 Password IPv4 address...15 Hostname...15 FQDN...16 Number Option Network Interface Controller (NIC)...17 Rules for custom attributes...20 System attributes...21 About OS Build Plans...21 About Golden Images...22 Recommendations...24 About Deployment Plans...24 About artifact bundles...24 Factory-provided artifact bundles Best Practices for using Artifacts...25 Use existing artifacts as templates Use Hewlett Packard Enterprise naming convention...26 Deployment About deployment...27 Deployment using Image Streamer OS volumes...27 Deployment Groups...28 Deployment Appliances...28 Primary deployment appliance About changing a primary deployment appliance...28 Scenarios while changing a primary deployment appliance Features...31 Contents 3

4 Stateless Experience...31 High Availability High availability for OS volumes...31 High availability for appliance and artifact management Capture...32 Capture using the Image Streamer appliance Advanced Management Virtual Machine...33 Appliance management Reimaging Image Streamer...34 Preparing a USB flash drive for reimaging an appliance...34 Reimaging the appliance with the preloaded USB drive...35 Reinserting Image Streamer...37 Guidelines for removing an Image Streamer appliance...38 Guidelines for inserting an Image Streamer appliance...41 Known issues during Image Streamer appliance removal or insertion...43 Loss of storage quorum renders OS volumes inaccessible...43 Updating Image Streamer Update process...45 Updating Image Streamer in a single frame configuration...46 Update scenarios...48 Update of active and standby appliances is successful...48 Update attempt returns a validation error Active appliance update fails Storage update fails during the active appliance update Active appliance update fails but storage update succeeds Active appliance and storage update succeeds but standby appliance update fails Backup, restore and recovery...49 Backup...49 Restore and recovery Restore artifacts...50 Recovery when an Image Streamer primary appliance pair fails and a secondary appliance pair is available...51 Recovery when the Image Streamer primary appliance pair fails and no secondary appliance pair is available Impact of restoring HPE OneView on Image Streamer Image Streamer Maintenance Console...53 About the Maintenance console Access the appliance maintenance console...54 Access the appliance maintenance console through an SSH connection...55 Access the appliance maintenance console from an HPE Synergy Frame Link Module Access the appliance maintenance console through a notebook or laptop...56 Log in to the appliance maintenance console About the appliance maintenance console password About the factory reset operation Appliance maintenance console main menu screen details...58 Appliance maintenance console details screen details Appliance maintenance console appliance states...60 View the appliance details Reset the appliance maintenance console password Reset the administrator password with the appliance maintenance console Shut down the appliance using the appliance maintenance console Restart the appliance using the appliance maintenance console Contents

5 Create a support dump file from the appliance maintenance console...65 Perform a factory reset using the appliance maintenance console...66 About changing the MGMT port purpose Configure MGMT port for management network connectivity Configure MGMT port for deployment network connectivity...69 MGMT port repurpose for a single enclosure setup Manual activation of an appliance Security...71 Assumptions...71 Authentication...71 Roles and Authorization Communication...72 Appliance Discovery...72 Data Protection...72 Password Storage Network Security Audit Logs...73 Compliance...73 Deployment and Maintenance...73 Known issues Troubleshooting Image Streamer...75 Basic troubleshooting techniques...75 OS deployment fails after primary Image Streamer appliance is removed and reinserted Active-standby Image Streamer appliance pair is not highly available...76 Changes to compute module settings are not updated onto Image Streamer Compute module waits in PXE boot mode due to unavailability of OS volume from Image Streamer...77 Creation of OS deployment server (Image Streamer) fails due to conflict in IP address Creation of server profile for a server hardware may fail if attempted immediately after logical enclosure creation for the bounded enclosure group HPE OneView does not claim Image Streamer appliance after a reset OS deployment server creation fails due to communication issues between HPE OneView and Image Streamer...79 Image Streamer appliance loses management network connectivity in single enclosure setup Image Streamer AMVM is unavailable Image Streamer primary appliance is not responding...81 Image Streamer restore operation stops abruptly OS deployment using Image Streamer fails...82 Problems in the functioning of the Image Streamer standby appliance Unable to access Image Streamer appliance from HPE OneView...83 Unable to include support dump for a standby Image Streamer appliance...84 Unable to power on an Image Streamer appliance on a remote enclosure in a multi-enclosure setup...85 Documentation and troubleshooting resources for HPE Synergy HPE Synergy documentation HPE Synergy Configuration and Compatibility Guide...86 HPE Synergy Frame Link Module User Guide HPE OneView User Guide for HPE Synergy...86 HPE OneView Global Dashboard...86 HPE Synergy Image Streamer User Guide Contents 5

6 HPE Synergy Image Streamer GitHub HPE Synergy Software Overview Guide HPE Synergy Firmware Update Overview...87 Best Practices for HPE Synergy Firmware and Driver Updates...87 HPE OneView Support Matrix for HPE Synergy...87 HPE Synergy Image Streamer Support Matrix...87 HPE Synergy Glossary...87 HPE Synergy troubleshooting resources...87 Troubleshooting within HPE OneView...88 HPE Synergy Troubleshooting Guide...88 Error Message Guide for HPE ProLiant Gen10 servers and HPE Synergy HPE OneView Help, HPE OneView REST API Scripting Help, and HPE OneView API Reference HPE Synergy QuickSpecs...88 HPE Synergy document overview (documentation map) Websites Support and other resources Accessing Hewlett Packard Enterprise Support...92 Accessing updates Customer self repair Remote support...93 Warranty information Regulatory information Documentation feedback Contents

7 HPE Synergy Image Streamer first-time setup HPE Synergy Image Streamer deployment workflow consists of a number of steps that involve: Hardware setup Network configuration Deployment server setup Deployment infrastructure setup Artifact management OS deployment These steps of the deployment workflow are documented in the interactive HPE Synergy Image Streamer Deployment Workflow guide available at the Hewlett Packard Enterprise Information Library. HPE Synergy Image Streamer first-time setup 7

8 Introduction to Image Streamer Image Streamer overview HPE Synergy Image Streamer is an HPE Synergy management appliance used to host, configure, and serve operating systems to the HPE Synergy compute modules. The Image Streamer appliance is managed by HPE OneView and must be in the same subnet as HPE OneView. To access the Image Streamer user interface, you must use single sign-on through HPE OneView. The Image Streamer appliance uses the following artifacts to deploy and configure the operating systems for HPE Synergy compute modules: Plan Script OS Build Plan Golden Image Deployment Plan Image Streamer also provides a capture functionality using OS Build Plans and Plan Scripts to capture a Golden Image from an installed OS volume. Stateless servers Image Streamer permits a stateless server deployment experience for compute modules. Stateless servers are physical servers without storage for application data. Stateless servers might still contain temporary local storage such as swap space. However, the applications running on the server use remote storage. The compute modules boot and run from the OS volumes hosted on the Image Streamer appliance. Image Streamer achieves OS deployment on stateless servers by maintaining the OS deployment state as part of the HPE OneView server profile. The server profile holds the logical hardware and software state of the server separately from the physical server. The logical state in the server profile can then be assigned to a physical server as required. The software state contains the firmware configuration, network connections, boot settings, and the ilo configuration. The deployed state contains the Golden Image (a combination of a bootable operating system, applications, and I/O driver version) and personality (hostname, IP configuration) and is stored in the Image Streamer OS volume. This stateless experience helps in achieving consistent software deployment and update and easy repair or replacement of the servers. Image Streamer preserves OS volumes when server profiles are assigned to physical servers, unassigned, and moved between physical servers. There are some scenarios when Image Streamer does not preserve OS volumes. These exceptions are explained in the OS volumes chapter of this user guide. Image Streamer redeploys Golden Images to handle any OS configuration changes. More information Image Streamer appliance terminology on page 8 Image Streamer building blocks on page 9 OS volumes on page 27 Image Streamer appliance terminology An HPE Synergy Composer domain can have multiple Image Streamer appliance pairs. An Image Streamer appliance pair serves a single logical enclosure, and a single logical enclosure can have at most one Image Streamer appliance pair. One Image Streamer appliance pair is designated as the primary appliance pair, and all other appliance pairs are designated as secondary appliance pairs. For an Image Streamer appliance pair, 8 Introduction to Image Streamer

9 An Active-Standby management cluster serves the artifact management and OS deployment functions. An Active-Active storage cluster serves the OS volume storage. All Image Streamer appliances managed by an HPE OneView instance operate as one deployment server. The Image Streamer deployment server acts as a single interface for management of all Image Streamer appliance pairs including deployment and capture of OS volumes residing in any appliance pair. It also manages the artifacts that provide details about for deployment and capture and replicates the artifacts on multiple appliance pairs when needed. A special single frame configuration with one Image Streamer appliance can be used for development or testing environments. Hewlett Packard Enterprise requires a three frame configuration as a minimum for production environment. The following list describes the appliance and cluster concepts: Image Streamer appliance An individual HPE Synergy Image Streamer module placed in HPE Synergy frames or a pair of Image Streamer modules that function together to form a highly available redundant pair. Primary Image Streamer appliance The primary appliance pair for a deployment server. The primary appliance pair is responsible for managing the server deployment, creating artifacts, and providing storage for the OS volumes for the compute modules in its logical enclosure. Secondary Image Streamer appliance The secondary appliance pair provides storage for the OS volumes for the compute modules in its logical enclosure. If the primary appliance becomes unavailable, the Infrastructure administrator can designate a secondary appliance as the primary appliance to manage the deployment process. Primary active Image Streamer appliance This appliance provides the deployment server user interface, artifact management, and deployment control. You can assign the primary appliance. Primary standby Image Streamer appliance When an active appliance becomes unavailable, the standby appliance takes over the management function of the active appliance and becomes the active appliance. The secondary appliances contain a copy of artifacts as available on the primary appliance and assist with deployment of OS volumes. If required, the standby appliances provide redundant artifact storage and deployment functionality. Standby appliances also have an active OS volume storage. Image Streamer building blocks Image Streamer has four artifacts that serve as the basic building blocks of Image Streamer. The artifacts include Plan Script, OS Build Plan, Golden Image, and Deployment Plan. The illustration shows the building blocks of Image Streamer with a single Deployment Plan scenario. Image Streamer building blocks 9

10 Deployment Plan Golden Image OS Build Plan Plan Scripts Figure 1: Building blocks of Image Streamer Plan Script A guestfish script that deploys an operating system for compute modules or captures a Golden Image from an operating system volume. OS Build Plans use the Plan Scripts for deployment and capture. OS Build Plans A set of Plan Scripts ordered as steps used to add, modify, or remove the configuration of an OS volume during the deployment or capture process. Golden Image A block-for-block copy of a previously deployed OS volume that is used to deploy and configure operating systems for compute modules. A previously deployed OS volume can consist of a bootable operating system, applications, and I/O driver version. Deployment Plan A combination of a Golden Image and OS Build Plan that serves as an input for a server profile. The server profile is then used for OS deployment. Artifact Bundles A bundle of artifacts that allows other artifacts to be packaged into a single archive file. This packaging allows the artifacts to be moved between different Image Streamer appliances across different HPE Synergy Composer domains. This format is used for the release of artifacts provided by Hewlett Packard Enterprise. Use the sample artifacts provided by Hewlett Packard Enterprise for OS deployment or to help development of customized artifacts. Copy these sample artifacts to customize functionality and include additional custom attributes for configuration settings. For more information on sample artifacts provided by Hewlett Packard Enterprise, see To get technical support, always use Hewlett Packard Enterprise provided artifacts for deployment activity. More information Artifacts on page Introduction to Image Streamer

11 Image Streamer architecture The Image Streamer appliance is placed in one of the Composable Infrastructure Manager (CIM) slots on HPE Synergy. The following diagram illustrates the different components of Image Streamer appliance architecture. Image Streamer User Interface and API Image Streamer artifact and deployment management Image Streamer artifact repository Deployment and OS volume management Compute modules Operating System volumes Solid State Drive Image Streamer Appliance HPE Synergy Frame Figure 2: Image Streamer Architecture The Image Streamer appliance has the following components: Image Streamer User Interface and Application Programming Interface Image Streamer User Interface and API enable the administrators to access and manage the artifacts in the appliance including capture of Golden Images from OS volumes. Image Streamer artifact and deployment management The Image Streamer user interface and API control: Artifact management including replications of artifacts between appliance pairs. Deployment of Golden Images including locating the OS volumes in the correct appliance pair. Image Streamer artifact repository Image Streamer artifact repository is the repository for Image Streamer artifacts. Image Streamer architecture 11

12 User roles for Image Streamer The following user roles exist for configuring and accessing Image Streamer using HPE OneView: Infrastructure administrator Infrastructure administrator has complete administrative privileges to configure HPE OneView and Image Streamer. Some of the actions that an Infrastructure administrator performs are: Image Streamer setup Firmware update Addition, replacement, and removal of appliances Server administrator Server administrator performs server provisioning and OS deployment from the server profile in HPE OneView. Software administrator Software administrator can perform the following actions: Create and manage artifacts such as Plan Scripts, OS Build Plans, Golden Images, and Deployment Plans. Manage and load artifact bundles. Capture Golden Images from OS volumes. Set default configuration settings that Server administrators might need for deployment. Determine the configuration settings that Software administrators may customize. Backup administrator Backup administrator can perform the following actions: Create and download backup files, view the appliance settings and activities. Has the authority to use scripts to log in to the appliance and run scripts to back up the appliance. For information on other user roles in HPE OneView, see HPE OneView Help for HPE Synergy available at the Hewlett Packard Enterprise Information Library. Deployment using Image Streamer Deployment is installing and configuring an operating system for servers. NOTE: Compute modules and servers are used synonymously while referring to the HPE Synergy servers. To perform a deployment: The Infrastructure administrator configures the HPE Synergy Composer and Image Streamer appliances in an enclosure. The Software administrator creates the artifacts and the custom attributes in the appliance using REST API or user interface. 12 User roles for Image Streamer

13 The Server administrator specifies the OS deployment settings using the server profiles in HPE OneView. The Image Streamer appliance creates an OS volume and performs the OS deployment with the specified user settings on the OS volume. Once the deployment is successfully completed, the compute module is powered on. It boots and runs from the OS volume. After successful deployment, the server profile is updated with the details of the OS volume. More information About deployment on page 27 Introduction to Image Streamer 13

14 Artifacts Artifacts are entities that are used to perform: Deployment of operating systems and applications into OS volumes for provisioning compute modules Capture of operating system and appliance Golden Images for OS volumes In an Image Streamer appliance, artifacts include Plan Script (PS), OS Build Plan (BP), Golden Image (GI), and Deployment Plan (DP). About Plan Scripts A Plan Script is one of the building blocks of the Image Streamer appliance and plays an important role in the Deploy and Capture processes. Plan Scripts are guestfish scripts that perform personalization (deployment) or generalization (capture). Plan Scripts are of three Types: Deploy Plan Scripts that are used for deployment Capture Plan Scripts that are used for capture General Plan Scripts that are used for deployment or capture Plan Scripts of Type Deploy contain custom attributes that are used to specify server-specific configuration information. A Plan Script must be referenced by an OS Build Plan to use it in a deployment or capture process. You cannot delete a Plan Script that is in use by an OS Build Plan. Plan Scripts provided by Hewlett Packard Enterprise are read-only. However, you can make a copy and edit them. More information About custom attributes on page About custom attributes Custom attributes are used to specify server-specific configuration information in the artifacts. You can add the custom attributes only in Plan Scripts of type Deploy. You can specify a default value for the custom attributes in Plan Scripts. You can modify the custom attribute default values in OS Build Plans, and Deployment Plans in Image Streamer and specify the final values to be used in server profiles in HPE OneView. A custom attribute has a name, type, value, and constraints that are applicable for each type of custom attribute. Specify the custom attribute name and optionally, the value in the Plan Script. Specify the type, constraints of the custom attribute, and optionally, an overriding default value in the OS Build Plan screen. Custom attribute constraints are used to constrain the custom attribute values in OS Build Plans, Deployment Plans, and server profiles in HPE OneView. You can use Deployment Plans to control the custom attributes that are visible to the server profile and those that are read-only. The syntax for a custom attribute in a Plan Script Custom attributes with default values can be specified Types of custom attributes 14 Artifacts

15 String A String type custom attribute can have any value unless a regular expression constraint is specified in the OS Build Plan. Constraints for a String custom attribute value: Regular Expression Length The specified value must match the regular expression. For example, a regular expression constraint ^[A-Za-z0-9]+$ implies that the custom attribute value must contain only uppercase alphabets, lowercase alphabets and numbers. To match the entire string, always remember to specify ^ as the starting character and $ as the ending character. If left blank, the custom attribute value is not validated. Can be up to 4095 characters in length. Password The password value is encrypted for storage and is masked while you enter it. Constraints for a Password custom attribute value: Regular Expression Minimum length Maximum length The password must match if the regular expression constraint is specified. To match the entire string, always remember to specify ^ as the starting character and $ as the ending character. Minimum number of characters required. Maximum number of characters required. IPv4 address Hostname The IPv4 address type is used for specifying other servers, such as a cluster controller, that are used by the operating system that is being deployed. NIC type custom attributes are used for configuring the network interfaces of the specified server. The value of a custom attribute of type IPv4 address must contain a valid IPv4 address. The value of a custom attribute of type Hostname must contain a valid hostname. String 15

16 Constraints for a Hostname custom attribute value: Length Allowed characters Can be up to 254 characters in length. Cannot contain period (.). Can contain alphabets, numbers, hyphen (-) and underscore(_). Cannot start with hyphen (-) or underscore(_). FQDN The value of a custom attribute of type FQDN must be a valid Fully Qualified Domain Name. Constraints for a FQDN custom attribute value: Length Allowed characters Can be up to 254 characters in length. Must contain at least one period (.). Can contain alphabets, numbers, hyphen (-) and underscore(_). Cannot start with hyphen (-) or underscore(_). Number The value of a custom attribute of type Number can be an integer or decimal. For example, 42 or Constraints for Number custom attributes: Minimum Maximum Minimum value allowed Maximum value allowed Table Continued 16 FQDN

17 Increment Number by which the value is increased or decreased. The increment or decrement options are used on the following screens: Create Deployment Plan Edit Deployment Plan Copy Deployment Plan Create Server Profile Edit Server Profile Copy Server Profile Create Server Profile Template Edit Server Profile Template Copy Server Profile Template Create Server Profile from Template Unit Unit corresponding to the number. For example, GiB or MiB. The unit for a number custom attribute is optional. Option Restricts the custom attribute values to the user-specified values. Network Interface Controller (NIC) Plan Scripts can contain Network Interface Controller (NIC) attributes. NIC attributes are complex custom attributes and contain network interface configuration parameters. A NIC attribute follows the format: <name>.<parameter>. A custom attribute is automatically recognized as NIC by the.<parameter> configuration parameter syntax. The type of NIC custom attributes cannot be changed. NIC attribute parameters are grouped in the OS Build Plan and Deployment Plan under a single attribute name and are of type NIC. A NIC attribute can be of two types: Teamed Unteamed Teamed NIC attributes Teamed network connections are used to ensure that servers have continuous network connectivity during HPE Synergy maintenance operations. They are also used to provide increased availability. Teamed NIC attributes can contain the following parameters: ipaddress1 - This parameter is mandatory when you use mac1 parameter. ipaddress2 mac1 - If the mac1 attribute is not set to any value, it expands to none in the Plan Script. Option 17

18 mac2 - If the mac2 attribute is not set to any value, it expands to none in the Plan Script. dns1 dns2 dns3 netmask gateway dhcp - A value of True for this parameter indicates that DHCP is selected in the server profile. networkuri - The value of this parameter indicates the network associated with the connection. NICs having matching networkuri values are connected to the same network. ipv4disable - A value of True for this parameter indicates that IPv4 networking is disabled on the NIC. Unteamed NIC attributes Unteamed NIC attributes can contain the following parameters: ipaddress mac - If the mac attribute is not set to any value, it expands to none in the Plan Script. dns1 dns2 dns3 netmask gateway dhcp - A value of True for this parameter indicates that DHCP is selected in the server profile. networkuri - The value of this parameter indicates the network associated with the connection. NICs having matching networkuri values are connected to the same network. ipv4disable - A value of True for this parameter indicates that IPv4 networking is disabled on the NIC. IMPORTANT: NIC attribute settings from the server profile and the way network connections are configured are correlated with OS settings for the correct network adapter functions using MAC address. Hence, Plan Scripts must include.mac subtype for each NIC attribute. IPv4 configuration options The server profile provides the <name>.<parameter> values that indicate the network configuration requested for OS deployment. If a network configuration parameter is not used in Plan Scripts, the server profile does not prompt for the same. You can set the IPv4 configuration in the Edit custom attribute dialog on the OS Build Plan screen to constrain the configuration choices allowed in the server profile. 18 Artifacts

19 Allow static This option indicates that the server profile can request the NIC to be configured with a static IP address. If not set, the server profile does not allow static IP configuration. If static IP configuration is allowed, you can enter the static IP configuration or it can be allocated from a pool if HPE OneView has an IP pool for the network. Allow DHCP This option indicates that the server profile can request the NIC to be configured for DHCP. Specifically, the.dhcp value may be true for this option. If not set, the server profile does not allow DHCP to be selected. Allow no network connection This option indicates that the server profile is allowed to provide no connection for the NIC. If set, the.mac or.mac1 and.mac2 values expand to none in the Plan Script. If not set, a network connection must be given in the server profile for the NIC attribute. Allow no network teaming This option indicates that the server profile is allowed to provide a single connection for the teamed NIC. If set,.mac2 value expands to none in the Plan Script. If not set, the server profile would not allow only a single network connection for the teamed NIC. These settings can be combined to restrict the server profile to permit only those network configurations which conform to a specific data center policy or the capability of the OS being deployed. Table 1: Example options for an unteamed NIC Allow static Allow DHCP Allow no network connection Selected Selected Not selected A network connection must be provided, either static or DHCP configuration can be given. Not selected Selected Selected The network connection is optional. If a connection is given, DHCP configuration will be used. Selected Selected Selected The network connection is optional. If a connection is given, DHCP or static configuration may be used. Artifacts 19

20 Table 2: Example options for a teamed NIC Allow no network connection Allow no network teaming Not selected Not selected Multiple connections are required to allow teamed configuration. Selected Not selected The NIC may not be connected in the server profile, but if connected multiple connections for teaming are required. Not selected Selected The NIC must have a connection, but a single connection or multiple connections are allowed. The server profile is allowed to determine if the connection is teamed. Selected Selected The server profile is allowed to leave the NIC unconnected, provide a single connection, or provide multiple connections for teaming. The Plan Script for a teamed NIC may or may not choose to use.ipaddress2. If.ipaddress2 is used, a second IP address will be configured for a static configuration. If.ipaddress2 is not used, a single IP address will be given for the teamed NIC even when multiple connections are made. Often only a single IP address is required for the OS to configure NIC teaming. Constraints for NIC custom attributes: Default values NIC attributes cannot have default values. The value can either be automatically populated from the IP pool if auto mode is enabled in the server profile in HPE OneView or specified by the user. Rules for custom attributes Prior to Plan Script execution, custom attributes are replaced with values provided by the server profile or default values. This action is called attribute expansion. The custom attribute name cannot contain spaces or special characters. It can contain numbers, underscores, and dashes. The custom attribute default value cannot character. Adjacent custom attributes can be used in the To character in a Plan Script, The custom attribute value can contain special characters and spaces. Hence custom attributes need to be enclosed in single or double quotes when used in guestfish or bash commands in the Plan Script. The custom attribute default value given in a Plan Script may not contain character. A default value which includes character, such as an address, may be placed in the OS Build Plan or Deployment Plan as a default value. The custom attribute default value can be left blank. 20 Rules for custom attributes

21 References to other custom attributes in a custom attribute value are not supported. NIC custom attributes cannot have default values. System attributes Image Streamer allows you to access the OS volume and iscsi initiator details using system attributes in Plan Scripts. System attributes have a similar syntax as that of custom attributes. During personalization, the system attributes are retrieved from Image Streamer or HPE OneView and are replaced with the corresponding attributes mentioned in the Plan Script. The system attributes that are supported for accessing OS volume details are: _Target.dev _Target.name _Target.ip _Target.port _Target.lun Device id of the OS volume that is mounted during personalization. This system attribute has a fixed value of/dev/sda Name of the OS volume IP address of the OS volume Port of the OS volume The logical unit number of the OS volume The system attributes that are supported for accessing iscsi initiator volume details are: iscsi Initiator 1 _Initiator1.mac MAC address of Initiator 1 _Initiator1.name IQN of initiator 1 _Initiator1.ip IP address of Initiator 1 _Initiator1.netmask Subnet mask of Initiator 1 iscsi Initiator 2 _Initiator2.mac MAC address of Initiator 2 _Initiator2.name IQN of initiator 2 _Initiator2.ip IP address of Initiator 2 _Initiator2.netmask Subnet mask of Initiator 2 If the Plan Script contains system attributes that correspond to iscsi initiator 2 for a single frame configuration which has a single interconnect module, they are left unexpanded. For in a single frame configuration is not expanded. About OS Build Plans An OS Build Plan specifies an execution sequence for the Plan Scripts to add, modify, or delete serverspecific content of an OS volume. System attributes 21

22 Deploy type Build Plans clone a Golden Image to create an OS Volume and modify the contents of the OS volume to personalize for a specific compute module based on settings specified in the server profile. Capture type Build Plans clone an OS volume to create a temporary copy which is then modified to remove server-specific content. After this generalization, the modified OS volume is captured into a new Golden Image. OS Build Plans also contain custom attributes that allow you to specify any configuration information. OS Build Plans are used by Deployment Plans to perform deployment. You cannot delete an OS Build Plan that is referenced by a Deployment Plan. About Golden Images A Golden Image is a block-for-block copy of an already installed operating system that is generalized to remove any server-specific configuration. It is always in the form of a compressed file. For deployment, you can customize the image by specifying server-specific configuration using custom attributes. For capture, you can generalize the image by removing any server-specific configuration and obtain an image from an OS volume. Life-cycle of a Golden Image Typically a Golden Image is captured from one server and later is deployed to one or more compute modules. The Golden Image can be transferred among one or more OS deployment servers as a compressed file by download and add processes. It can also be included in an artifact bundle and then transferred by download and extract of the artifact bundle. A Golden Image can be added to the OS deployment server by using one of the following operations: Add - To upload a golden image in the form of a compressed file Create - To create a new Golden Image from an OS Volume capture Import from an artifact bundle - Import a Golden Image from an artifact bundle The image in the appliance is a ready to use form of Golden Image, and can be used for deployment, download, and export. The following diagram describes the different ways to add or import, capture, download or export, and deploy a Golden Image to the appliance. 22 About Golden Images

23 Figure 3: Life cycle of a Golden Image Artifacts 23

24 Table 3: Golden Image life cycle sequence of events Sequence Operation Description 1 Add Adds a Golden Image from your laptop. 1 Capture 1 Creates a Golden Image either from a deployed server or from an OS volume. 1 Import Adds the Golden Image to the appliance from an imported artifact bundle. 2 Deploy Deploys a Golden Image on a compute module, using a Deployment Plan. 3 Export Copies the Golden Image to the artifact bundle, which can be later imported on another Image Streamer appliance. 3 Download Downloads a Golden Image to your laptop as a simple compressed file having the block-for-block copy of the generalized OS volume content. 4 Delete Deletes the Golden Image. 1 Capture is the process of creating a golden image. Recommendations Hewlett Packard Enterprise recommends the following while using Golden Images in the Image Streamer appliance: Recommendations for creating the first Golden Image To create the first Golden Image, you need an empty OS volume into which you can install the operating system and additional software. To create an empty OS volume, use the special Deployment Plan HPE - Foundation - create empty OS Volume. This Deployment Plan is available as a part of HPE Foundation Artifact Bundle in Image Streamer appliance storage. After OS (the operating system you wish to capture) installation, you can make configurational changes in the operating system. Any configuration information that is not specific to the compute module must be completed in the OS before server shutdown and Golden Image capture. Configuration settings for different compute modules can be handled by using a different set of Golden Images or by customizing the OS Build Plans. About Deployment Plans A Deployment Plan contains the OS Build Plan and Golden Image. The server profile in HPE OneView uses the Deployment Plan for server deployment. Generally, a Software administrator creates a Deployment Plan and a Server administrator uses it in the server profile for deployment. You cannot edit or delete a Deployment Plan that is in use by an HPE OneView server profile. About artifact bundles Artifact bundles are provided by Hewlett Packard Enterprise or user created zip files that contain artifacts. The artifacts in the bundles can be user created, provided by Hewlett Packard Enterprise, or a combination of both. The artifact bundles are created from existing artifacts on the appliance. 24 Recommendations

25 Actions on Artifact bundles You can create multiple artifact bundles on the appliance. You can download artifact bundles to your local system or upload artifact bundles to a primary active Image Streamer appliance. You can extract and import artifacts from the bundles into the appliance. The Import operation copies and expands the artifacts from the bundle. You can set the read-only attribute for the artifacts in the bundle to prevent modification after loading on another appliance. To edit read-only artifacts, you can copy them to another location to create editable copies. Extracting Artifact bundles When you extract an artifact bundle, the extract dialog displays a summary of all artifacts with name conflicts. If existing artifacts on the appliance match the artifacts that are extracted from the bundle, they are not copied to the appliance. They are copied to the appliance only after you confirm to rename the artifacts in the bundle. Factory-provided artifact bundles Always use the latest artifacts that are available at However, if you do not have access to the Internet, use factory-provided artifact bundles available in the Image Streamer appliance. For a new Image Streamer appliance or after a factory reset of the Image Streamer appliance, the foundation and support artifact bundles are automatically created and available. The factory-provided artifact bundles are created while creating the OS deployment server on the primary Image Streamer appliance. You can view the factory-provided artifact bundles on the Artifact Bundles screen after creating an OS deployment server using HPE OneView. Foundation bundle The foundation artifact bundle consists of artifacts that enable you to perform basic Image Streamer operations. Basic Image Streamer operations include creation of an empty OS volume, deployment of operating systems without any personalization, and capture of operating systems. Support bundle The support artifact bundle consists of artifacts that enable you to validate deployment and capture features of the Image Streamer appliance using a sample Golden Image. The sample Golden Image (HPE - Support UEFI Test Image ) provided in the Support artifact bundle requires UEFI support. The factory-provided artifact bundles are read-only and are not extracted automatically. To use the default artifacts, extract the factory-provided artifact bundles. Factory-provided artifact bundles remain unaffected by a factory reset operation. During an appliance upgrade, the existing factory-provided artifact bundles are replaced, if the upgrade includes a newer version of the factory-provided artifact bundles. Best Practices for using Artifacts For information on best practices for using Image Streamer artifacts, see HPE Synergy Image Streamer Artifacts Development Best Practices at Use existing artifacts as templates Hewlett Packard Enterprise provides artifact bundles that include OS Build Plans. The existing OS Build Plans can be used as is and also as templates. For more information about the artifacts provided by Hewlett Packard Enterprise, see the documentation for Image Streamer artifacts available at Factory-provided artifact bundles 25

26 HewlettPackard/image-streamer-tools. Artifacts provided by Hewlett Packard Enterprise are read-only. However, you can make a copy and edit them. For more information on copying artifacts to allow modifications, see HPE Synergy Image Streamer Online Help. Use Hewlett Packard Enterprise naming convention Hewlett Packard Enterprise uses the following naming convention for the artifacts provided with the Image Streamer appliance: Organization OS and version Action Modifiers Organization To avoid naming conflicts, names of artifacts provided by Hewlett Packard Enterprise begin with the organization name. Hence, do not use HPE for artifacts that are not provided by Hewlett Packard Enterprise. OS and version The organization name precedes the operating system name and version. Along with the OS and version details, the name can also contain information about layered application software. Typically, this file naming convention is useful for naming Golden Images. Action The operating system and version details precede the action that an artifact performs in the file name. Typically, this file naming convention is useful for naming Plan Scripts. Modifiers Modifiers can contain any other information that describes the artifact. Typically, this part of the file naming convention is useful for naming Plan Scripts. For more information, see and HPE Synergy Image Streamer Artifacts Development Best Practices at 26 Use Hewlett Packard Enterprise naming convention

27 Deployment About deployment Server deployment is the process of installing an operating system on the server and configuring it for use. Conventional server deployment tools run on the target server using an in-memory operating system called service OS. The service OS typically matches the operating system to be deployed on the target server. The deployment tool boots the service OS, then the service OS sets the storage layout, installs the operating system software, and configures the operating system settings. Once the configuration is completed, the server reboots and runs the deployed operating system. Deployment using Image Streamer The deployment using Image Streamer starts with a block-for-block copy of the Golden Image to create an OS volume. This copy is created in less than 5 seconds irrespective of the OS volume size. Once the OS volume is created, the Plan Scripts run in a contained environment to personalize the OS volume for the target server. During the execution of Plan Scripts, the custom attributes are replaced with their values. NOTE: OS volumes Since the contained environment is unrelated to the deployed operating system, personalization can be complex. Hence, it is important to consider strategies that reduce the complexity and efforts for customizing each compute module. A simple partition layout and configuration for deployment is useful to reduce the complexity of personalizing each server. Image Streamer creates OS volumes as a result of the deployment process. An OS volume is associated with an HPE OneView server profile and can be assigned to a physical server as needed. Image Streamer preserves OS volumes whenever possible when server profiles are assigned to physical servers, unassigned from the server hardware, and moved between servers. An OS volume can be retained, deleted, or regenerated based on the actions performed on server profiles and logical enclosures. Table 4: OS volumes status scenarios Scenario A server profile is assigned to or unassigned from physical server hardware A server profile is assigned to a logical enclosure that is moved to a different enclosure group A server profile is unassigned and the corresponding logical enclosure is subsequently deleted A server profile is assigned to a server hardware that cannot access the OS volume since it is in a different logical enclosure. Server Harware Type of a server profile is modified OS volume status OS volume is retained OS volume is retained OS volume is deleted OS volume is deleted and regenerated from the OS Deployment Plan OS volume is deleted and regenerated from the OS Deployment Plan Deployment 27

28 Deployment Groups A Deployment Group is a group of Image Streamer appliances in an HPE Synergy Composer domain. There can be only one deployment group in one HPE Synergy Composer domain at a time. Deployment Appliances A Deployment Appliance is a single Image Streamer appliance inserted in the CIM slot. A single deployment appliance pair contains an active and a standby appliance to achieve high availability. Using the Deployment Appliances screen of the Image Streamer user interface, you can view the overall health status of the appliance pair, location and details of active and standby appliances, create a support dump, and perform update, restart, and shutdown operations on the Image Streamer appliance. When an Image Streamer appliance is inserted in the CIM slot, a claim process is triggered in HPE OneView. You can view the claim status of the Image Streamer appliance in the Activity screen in HPE OneView user interface. If HPE OneView fails to claim the Image Streamer appliance, an alert on the Enclosures screen in HPE OneView user interface notifies you about the error. The alert redirects you to first perform a factory reset of the Image Streamer appliance and then click a refresh link to retrigger the claim process. Primary deployment appliance The primary deployment appliance is the cluster where the Image Streamer user interface runs. It provides the interface for managing artifacts and detailed status and maintenance of Image Streamer appliances. It also coordinates deployment as directed by the server profile. The primary appliance is selected when the Image Streamer deployment server is added. Any Image Streamer appliance can be selected as the primary appliance. Changing the primary appliance does not disrupt server access to OS volumes. About changing a primary deployment appliance In an HPE Synergy Composer domain that has multiple frames, there can be many Image Streamer appliances. All Image Streamer appliances that are not designated as the primary appliance are considered secondary appliances. A secondary appliance hosts and serves the operating system volumes for the compute modules in its logical enclosure. It also acts as a backup in case the primary appliance fails. If there are issues with the primary appliance, a need to remove or decommission the primary appliance can arise. In such a scenario, another Image Streamer can be selected as the primary appliance by editing the deployment server. OS deployment is not possible until the deployment server is edited to select a new primary appliance. The new primary appliance requires time to reconfigure and take control of the group of appliances. During this time, servers continue to have uninterrupted access to OS volumes. Before the primary appliance is physically removed, a new primary appliance must be selected. If the primary appliance is removed before selecting a new primary appliance, it will not be possible to manage artifacts and OS deployment will fail. Once a new primary appliance is selected, normal operation will resume. To avoid problems, the general sequence for changing a primary deployment appliance must be in the following sequence: 1. Back up all the Image Streamer artifacts manually. 2. Ensure that there is at least one hour when the primary appliance is functioning but is not used to perform any tasks. 3. Ensure selection of a secondary appliance as the new primary appliance. The secondary appliance that you select must have a logical enclosure configured and must be functioning without any issues. To select a secondary appliance as the new primary appliance, use the OS Deployment Server screen in HPE OneView user interface. 28 Deployment Groups

29 For prerequisites and instructions for changing a primary deployment appliance using the HPE OneView user interface, see HPE OneView Help. Scenarios while changing a primary deployment appliance Changing a primary deployment appliance requires caution and understanding the scenarios that might arise when you perform the task. The following topics describe the various actions that you might perform and the result of those actions. Changing a primary deployment appliance to a secondary appliance without a logical enclosure Action You change a primary deployment appliance to a secondary appliance that does not have a logical enclosure created. Consequence Changing the primary deployment appliance fails with the following error: Logical enclosure for new primary is yet not configured. What can I do? You can manually bring back the old primary appliance by performing the following tasks in HPE OneView user interface: 1. Delete the server profile that is served from the primary appliance pair. 2. Reconfigure the enclosure group to remove Image Streamer intent. 3. Click Update from group in logical enclosure screen. 4. Delete the OS deployment server using the Delete action on OS Deployment Server screen. 5. Replace primary Image Streamer appliance pairs with new secondary appliances and reinsert the secondary appliances. For detailed instructions on each on these steps, see HPE OneView Help. Recently created artifacts are unavailable after changing the primary appliance Action The primary appliance fails suddenly and you successfully change the primary appliance to a functioning one. Consequence The new primary appliance might not contain the artifacts created just before the failure. What can I do? It is a best practice to take manual backups of the artifacts at regular intervals. If you failed to take a backup and the primary appliance fails suddenly, recently created artifacts might not be available in the new primary appliance. You will be required to manually recreate the missing artifacts in the absence of a backup. Changing a primary appliance soon after uploading a Golden Image Action You attempt to change the primary appliance soon after uploading a Golden Image. Scenarios while changing a primary deployment appliance 29

30 Consequence OS volume deployment using an OS Deployment Plan that uses the recently uploaded Golden Image might fail. What can I do? Upload the Golden Image again to the new primary appliance and recreate the OS Deployment Plan. Booting compute modules from a failed primary appliance Action You boot the compute modules from a failed primary appliance. Consequence Compute modules booted from a failed primary appliance can never be operational until the server profiles are unassigned and reassigned. What can I do? 1. Change the primary appliance to another appliance that is functional. 2. Unassign and reassign the server profiles for the compute modules. For instructions on how to assign and unassign server profiles, see HPE OneView Help. A primary appliance can function but is currently shut down Action A primary appliance can function but is currently shut down. Consequence Changing the primary appliance does not convert this old primary appliance as a new secondary appliance. What can I do? 1. Power on the primary appliance. 2. Change the primary appliance to another functional appliance. By performing these steps, the original primary appliance becomes a secondary appliance. 30 Deployment

31 Features Stateless Experience The Image Streamer appliance permits a truly stateless experience for deployment of operating systems on HPE Synergy compute modules. To achieve statelessness, the software state of the compute module and the deployed state of the OS volume are maintained separately. The software state contains the firmware configuration, network connections, boot settings and the ilo configuration, and is stored in the server profiles available in HPE OneView. The deployed OS volume contains the Golden Image (a combination of a bootable operating system, applications, and I/O driver version) and personality (hostname, IP configuration), and is stored in the Image Streamer OS volume. The servers do not have any storage for application data. These compute modules boot from the OS volumes stored in the Image Streamer appliance. This stateless server experience helps achieve faster deployment of operating systems. NOTE: If you choose to use persistent local storage, the Image Streamer appliance cannot provide stateless compute modules. You can use a temporary local storage such as swap space with a stateless approach. High Availability The Image Streamer appliance works in pairs to achieve high availability. Additionally, multiple pairs of the appliance can be accommodated in a single HPE Synergy Composer domain to enhance the scalability of this appliance. If both the active and standby appliances of the primary appliance pair fail, a secondary appliance is designated as the new primary pair. The storage on the appliance forms an Active-Active cluster. This mode helps in ensuring continuity in serving OS volumes if an active appliance fails. For an Image Streamer appliance pair, the artifact management and OS deployment function is served by an Active-Standby management cluster, whereas the OS volume storage is served by an Active-Active Storage cluster. More information Image Streamer appliance terminology on page 8 High availability for OS volumes The Image Streamer appliance uses a virtual storage appliance to provide an Active-Active storage cluster for the compute modules. This Active-Active cluster uses an active-standby data path for the OS volumes that achieves high availability of OS volumes. The Image Streamer appliance uses alerts to notify the user, when any of the storage nodes in the cluster is not available. High availability for appliance and artifact management An HPE Synergy Composer domain can have multiple Image Streamer appliance pairs. An Image Streamer appliance pair serves a single logical enclosure, and a single logical enclosure can have at most one Image Streamer appliance pair. One of the Image Streamer appliance pair is designated as the primary appliance, and all other appliance pairs are designated as secondary appliances. An Image Streamer appliance works as an Active-Standby appliance pair to achieve high-availability for appliance and artifact management through the user interface. If an active appliance fails, the standby appliance in the appliance pair can take over the user interface and artifact management in less than 3 minutes. If both the active and standby appliances of the primary appliance fail, then one of the available secondary appliances must be designated as the new primary appliance. To view the details of active and Features 31

32 standby appliances in an appliance pair, navigate to the Deployment Appliances screen on the Image Streamer user interface. The Image Streamer appliance uses alerts to notify the user when the appliance is not highly available. Frame 1 HPE OneView 1 2 MGMT 3 LINK Frame 2 HPE OneView Image Streamer Frame 3 Image Streamer Legend: Management Network Link Network Interconnects Figure 4: High availability in a 3-frame setup 1-6 Device bays 7-8 Interconnects The illustration is an example of Image Streamer high availability in a 3-frame setup. In a 3-frame setup with two Image Streamer appliances: Two Image Streamer appliances are required to ensure high availability. A minimum of three frames are required for a pair of Image Streamer appliances. In Frame 2 where HPE OneView and Image Streamer coexist, the appliances can be placed interchangeably in any of the CIM slots. For a pair of Image Streamer appliances, there must be a pair of interconnects. The position of the interconnects must be symmetrical. In the example illustration, the interconnects are present in the device bays 3 and 6 of Frame 2 and Frame 3 respectively. Capture 32 Capture

33 Capture using the Image Streamer appliance The capture functionality in the Image Streamer appliance enables you to capture an existing instance of the operating system on the compute module. The Image Streamer resource management interface removes all server-specific information before creating a Golden Image from the installed operating system. This process is also called generalization. When you are creating a Golden Image for the first time, you need an empty Image Streamer OS volume to install the operating system. Hewlett Packard Enterprise provides a special Deployment Plan in the Image Streamer appliance storage to create an empty volume. IMPORTANT: Attempts to capture a Golden Image from an OS volume which is in use may result in a corrupt Golden Image. Advanced Management Virtual Machine Advanced Management Virtual Machine (AMVM) is primarily used to validate Image Streamer artifacts and the related custom attributes present in Plan Scripts and OS Build Plans. AMVM is created during the logical enclosure creation in HPE OneView. The AMVM is available as long as the logical enclosure exists. To use AMVM, you must have the privileges of any of the following user roles: Infrastructure administrator Server administrator Software administrator AMVM provides a debugging environment that enables an administrator to perform the following operations: Validate artifacts and custom attributes present in Plan Scripts and OS Build Plans. Access the in-use OS volume before booting the compute module. Execute scripts to perform commands to create or import artifacts. AMVM has the following features: Ability to troubleshoot a compute module if it fails to boot due to an erroneous Golden Image in the Image Streamer appliance. Ability to access the OS volume and verify the contents of the OS volume before booting the compute module. Capture using the Image Streamer appliance 33

34 Appliance management Reimaging Image Streamer Preparing a USB flash drive for reimaging an appliance IMPORTANT: Hewlett Packard Enterprise recommends that you prepare a USB flash drive immediately after installing and after updating the appliance firmware so that you always have a USB flash drive that matches the currently installed version of the appliance image. For environments with multiple versions, create separate USB drives, one for each version. Prerequisites Computer running either Linux or a Microsoft Windows operating system USB flash drive with 4 GB of memory, or greater Internet connection Preparing a USB drive for reimaging an appliance Procedure 1. Identify the version of the appliance image. View the firmware version: In the appliance maintenance console using the View option. In HPE OneView, view the Installed firmware version for Member Appliance by using the OS Deployment Servers screen. Under General, select the hyperlink to the deployment server interface, then select Deployment Appliances. The firmware version that is displayed is the version of the image that you will download in step 5 and include on the USB drive. 2. Insert the USB flash drive in the computer USB port. 3. If necessary, delete any unnecessary partitions to ensure adequate disk space. 4. Format the USB flash drive for one FAT32 or W95 FAT32 partition using these guidelines: For a Linux operating system, use /sbin/fdisk /dev/sdx command, where x represents the numerical drive of the USB port used. For a Windows operating system, right-click the USB icon in the Computer window and select Format. Specify a label for your USB drive. It can be any name you want, except EMBEDDED, which is a reserved name. Consider using the date as part of the label. Create only one primary partition. Delete any existing partitions. If prompted, specify the following parameters: 34 Appliance management

35 Capacity: maximum value Allocation unit size: 4096 bytes First and last block: default values 5. Download the recovery image (.zip file) from the website The recovery image that you download must match the version determined in step 1. Make sure that you download the complete image for recovery for the USB. The firmware update for existing images does not contain a complete image. 6. Unzip the compressed image. 7. Copy the contents of the image file to the USB flash drive. IMPORTANT: Do not rename the files. 8. Optionally, remove the USB flash drive and store it for future use. Reimaging the appliance with the preloaded USB drive Reimaging the appliance is required if you replace the disk or, in a clustered configuration, if the firmware on the appliance that you are reinserting does not match the firmware of the appliance currently in operation. CAUTION: This operation destroys data on the reimaged appliance. Prerequisites The system is prepared for removal of the appliance. Preloaded USB flash drive. Access to the front panel of the appliance. Reimaging the appliance with the preloaded USB flash drive Procedure 1. Identify the appliance to be reimaged. If you are reinserting a repaired appliance, insert it now and allow 15 to 20 minutes for it to restart. 2. Insert the preloaded USB flash drive into the USB port of the appliance to be reimaged. Reimaging the appliance with the preloaded USB drive 35

36 Figure 5: Inserting a preloaded USB drive in the appliance Item Description 1 USB ports in the appliance 3. Hewlett Packard Enterprise recommends installing an HPE Synergy console to monitor the reimaging and rebooting operations: a. Connect a keyboard, video, and mouse to the DisplayPort and USB ports located: On the Front Panel of the frame or On either HPE Synergy Frame Link Module at the rear of the frame On connection, the HPE Synergy console is displayed. b. Click the monitor icon at the top right of the screen. c. Select the appliance to monitor from the Appliances submenu. A serial console window opens. d. Press Enter. 4. Locate the Power/Reset LED indicator on the HPE Synergy appliance front panel. 5. Use the applicator to depress the pinhole button (located inside of the Power/Reset LED indicator) for more than 10 seconds. 36 Appliance management

37 Figure 6: Button and Indicator panel Item Description 1 Pinhole button within Power/Reset indicator 2 Power/Reset LED indicator 3 Active LED indicator Momentarily depressing the pinhole button causes the appliance to reboot, but does not reimage it. After 10 seconds, the Active LED starts to flash, and the Power/Reset LED indicator turns amber, which means that the reimage process was triggered. 6. Release the pinhole button as soon as you see the flashing Active LED. If connected, the HPE Synergy console shows progress messages. The front panel UID flashes blue throughout the reimage process. After reimaging, the appliance reboots, updates the firmware to the version stored on the preloaded USB drive, and starts HPE OneView. Reimaging is completed in approximately one hour; at which time the initial HPE OneView login screen appears in the HPE Synergy console. For Image Streamer, the administrator must log in to the appliance maintenance console, shut down the Image Streamer appliance and reseat it. Reseating the appliance triggers the discovery, claim, and eventual cluster formation. 7. Verify that the appliance is reimaged by examining the firmware version number either on the Appliance panel of the Settings screen or by using the View details command of Maintenance console. 8. Optionally, remove the preloaded USB flash drive and store it for possible future use. Reinserting Image Streamer When an appliance component fails or an appliance is removed, alerts notify you about the failure or removal on the Activity screen of the Image Streamer user interface. Reinserting Image Streamer 37

38 NOTE: You must shut down an appliance using the Maintenance console before removing it. If you are powering down an active or standby appliance, use the Maintenance console. If you are powering down both the appliances, you can use the Image Streamer user interface on the maintenance console. When you reinsert a repaired appliance or the same appliance, the OS Deployment Servers screen in HPE OneView displays a progress bar to show the progress of the insert operation. NOTE: The OS Deployment Servers screen displays the progress bar only if you have already created an OS deployment server. If you have not created an OS deployment server yet, check for the removal task status in Enclosures screen using HPE OneView user interface. Do not attempt to remove the inserted appliance before the insert operation is complete because doing so might interrupt cluster formation. Removing an appliance during the cluster formation process might render existing OS volumes inaccessible. The following sections describe the guidelines and special considerations while replacing an existing appliance with a new appliance or while removing and reinserting the same appliance. For instructions on how to replace an Image Streamer appliance, see HPE Synergy Appliances Maintenance and Service Guide for HPE Synergy Composer and HPE Synergy Image Streamer available at the Hewlett Packard Enterprise Information Library. Guidelines for removing an Image Streamer appliance Before removing an Image Streamer appliance from the CIM slot, verify if the Image Streamer appliance cluster health and OS volume status are healthy. The Deployment Appliances screen on the Image Streamer user interface displays the cluster health and OS volume status. If you remove the appliance without verifying the cluster health or OS volume status, you might lose access to the OS volume. Before removing an Image Streamer appliance, verify that there are no outstanding warnings on the Enclosures screen, OS Deployment Servers screen in HPE OneView, or on the Deployment Appliances screen in Image Streamer. For example, the warning can read as: Changes made on <enclosure1> appliance bay<number> are being synchronized to <enclosure2> appliance bay<number> If one of the appliances is already faulty, critical alerts are displayed on these screens. Follow the resolutions mentioned in the alerts to resolve the error. If the issue persists even after following the resolution, contact your authorized support representative. Before removing an appliance, shut down the appliance using the Maintenance console. When an appliance is removed from the CIM slot, it might take up to 20 minutes for the removal operation to complete. You can track the progress of the removal operation on the OS Deployment Servers screen in HPE OneView. Wait until the removal operation is complete before inserting a repaired or another appliance in the same CIM slot. NOTE: The OS Deployment Servers screen displays the progress bar only if you have already created an OS deployment server. If you have not created an OS deployment server yet, check for the removal task status in Enclosures screen using HPE OneView user interface. The appliance removal operation is complete when the progress bar on the OS Deployment Servers screen in HPE OneView user interface shows that the removal operation is complete. 38 Guidelines for removing an Image Streamer appliance

39 Once an appliance is removed successfully, the Member Appliances section in the Deployment Appliances screen displays information only about the existing appliance. When an appliance is removed, an alert displays on the HPE OneView Enclosures screen, after 3 to 4 minutes. This alert displays as soon as the appliance removal operation starts and notifies you that the expected Image Streamer appliance is missing. This alert indicates that the appliance removal operation has started. The resolution message mentions a user action to insert an appliance but do not insert an appliance until the removal operation completes successfully. When the appliance removal operation is in progress, ignore the following alert that appears in the Deployment Appliances screen in Image Streamer user interface. Appliance management 39

40 When the appliance removal operation is in progress, ignore the following alert that appears in the OS Deployment Servers screen in HPE OneView user interface. If the Remove Image Streamer Appliance task on OS Deployment Servers screen terminates with an error, follow the resolution suggested as part of the error message. If an active appliance is removed, the standby appliance takes over. It might take 3 to 5 minutes for the failover to complete. Rarely, this failover operation might take up to 10 minutes to complete. During this time, the Image Streamer user interface displays the following screen: 40 Appliance management

41 If a standby appliance is removed, the Image Streamer user interface continues to be accessible. Guidelines for inserting an Image Streamer appliance When an Image Streamer appliance is inserted, it takes up to 1 hour for the inserted appliance to be ready to operate in high availability mode. Do not remove the appliance until the insert operation is complete because it might interrupt cluster formation. You can track the progress of the insert operation on the OS Deployment Servers screen in HPE OneView user interface. NOTE: The OS Deployment Servers screen displays the progress bar only if you have already created an OS deployment server. If you have not created an OS deployment server yet, check for the removal task status in Enclosures screen using HPE OneView user interface. After you insert an appliance, the Enclosures screen in the HPE OneView user interface displays an alert about the interconnect link topology with state as Cleared. This state update might take up to 6 minutes from the time you insert the appliance. Guidelines for inserting an Image Streamer appliance 41

42 After you insert an appliance and cluster formation starts, a quorum configuration alert might appear on the Deployment Appliances screen in the Image Streamer user interface. Ignore this alert because it is a part of the cluster formation process. Once the cluster is formed, the alert automatically clears. If this alert stays active for more than 30 minutes, contact your authorized support representative. The appliance insertion is complete when the Update Image Streamer activity completes successfully and the Deployment Appliances screen displays information about two member appliances. Do not remove the inserted appliance until this message is displayed. 42 Appliance management

43 When the same appliance which was removed earlier is reinserted, the reinserted appliance undergoes a factory reset and powers off. Then, you must manually power it on, perform a factory reset and click the refresh link on the Enclosures screen in HPE OneView user interface. You might encounter GEC errors during the process. Follow the recommendations provided in the alert until it is cleared. It might require you to refresh the enclosure and reinsert the appliance a few times. Once the GEC errors are resolved, appliance configuration and clustering take up to 1 hour to complete so that high availability is restored. Known issues during Image Streamer appliance removal or insertion Contact your authorized support representative with a support dump of HPE OneView and Image Streamer appliances when: The Insert Image Streamer Appliance or Remove Image Streamer Appliance tasks on the OS Deployment Servers screen report errors and direct you to contact your authorized support representative. Critical alerts persist for more than an hour after you insert an appliance and the message resolution directs you to contact support. Loss of storage quorum renders OS volumes inaccessible Symptom After you insert an appliance: A quorum configuration alert appears on the Deployment Appliances screen in the Image Streamer user interface and persists for more than 30 minutes. Known issues during Image Streamer appliance removal or insertion 43

44 Compute modules shut down immediately. NOTE: Compute modules running Linux might shut down immediately. The compute modules running VMware ESXi might continue functioning from memory and don t access the OS volume for a long time. Because there is no alert to notify you that the OS volumes are inaccessible, you might not see this symptom for compute modules running VMware ESXi. New OS deployments using Image Streamer fail and display the error: Unable to deploy OS volume. Any further attempt to remove or insert an appliance fails. Cause The existing appliance is not able to reach the newly inserted appliance due to technical issues such as network connectivity. This might cause the storage to lose quorum. If the storage loses quorum, the corresponding OS volumes become inaccessible and the compute modules using these OS volumes are impacted. Action Contact your authorized support representative after creating a support dump from HPE OneView and Image Streamer appliances. Updating Image Streamer New versions of Image Streamer firmware include new or updated features and fixes. For details about a new version, see the HPE Synergy Image Streamer Release Notes available at the Hewlett Packard Enterprise Information Library. Image Streamer firmware versions have compatibility requirements for HPE Synergy Composer firmware versions. For information on compatibility between the versions, see HPE Synergy Image Streamer Support Matrix available at the Hewlett Packard Enterprise Information Library. 44 Updating Image Streamer

45 The recommended sequence for a firmware update is: 1. Update HPE OneView. 2. Update the firmware in the primary Image Streamer appliance pair. 3. Update the firmware in each secondary Image Streamer appliance pair, one at a time. 4. Update Frame Link Module and Interconnect Modules. IMPORTANT: Do not attempt to update the Frame Link Module and Interconnect Modules if: If the Image Streamer appliance cluster is not healthy. If the OS volume status is not healthy. You can verify the Image Streamer appliance cluster status and OS volume status using the Deployment Appliances screen in Image Streamer user interface. NOTE: Allow an Image Streamer appliance pair to complete the update process before updating the next pair. The individual Image Streamer appliances in an appliance pair are automatically updated so that servers have nondisruptive OS volume access during the update process. Appliance storage is synchronized after the update process is complete. Hence, it is important to allow update of the standby appliance, followed by the synchronization of the appliances in the appliance pair. As a result, the time required to complete the update process for an appliance pair may vary. During the update process, different Image Streamer appliance pairs will have different firmware versions. Image Streamer appliances are designed to provide nondisruptive access to OS volumes when they operate in this mode. Image Streamer appliances do not support deployment or artifact management during the update process or when the appliance pairs have different firmware versions. It is important that servers are correctly configured for network teaming. This configuration ensures that OS issues do not occur when firmware updates in various parts of HPE Synergy temporarily interrupt a part of the network. This includes the deployment network connection used for OS volume access as well as connections to other networks. However, firmware update of single Image Streamer configurations used for artifact development and testing is disruptive to server operations. Servers using Image Streamer OS volumes must be shut down before Image Streamer firmware update is done. For instructions on how to update Image Streamer to a new version, see HPE Synergy Image Streamer Online Help. Update process The process of updating an Image Streamer appliance pair proceeds in the following sequence: 1. Validating the new firmware file for integrity and compatibility with HPE OneView firmware and the current Image Streamer firmware. 2. Updating active appliance management software. 3. Updating the active appliance storage software. 4. Updating standby appliance storage software. Update process 45

46 5. Updating standby appliance management software. 6. Synchronizing storage between the appliances in the pair. You can view the alert messages and notifications on the Activity screen of the Image Streamer user interface for a successful or a failed update. You can monitor the status of the standby appliance update process using the Activity screen in the Image Streamer user interface. If an update fails on an active appliance, Image Streamer is reverted to the version before the update started. To be able to perform deployments using Image Streamer, the current HPE OneView firmware version and the reverted Image Streamer version must be compatible. Otherwise, you must first fix the issue with the update process to complete the update successfully which will render the versions compatible. Updating Image Streamer in a single frame configuration Hewlett Packard Enterprise recommends a 3-frame configuration as a minimum requirement for production environment. A special single frame configuration with one Image Streamer appliance can be used for development or testing environments. However, updating an Image Streamer appliance in a single frame configuration is not supported. IMPORTANT: This procedure causes a downtime of at least 6-7 hours and you will lose all existing configurations. Prerequisites You have Image Streamer configured in a single frame setup for testing or artifact development purposes. AND A requirement to update this test or developmental setup to a later version. Procedure 1. Create a backup bundle to backup all Image Streamer artifacts. Image Streamer user interface action: Deployment Groups > Actions > Create backup bundle 2. Download the backup bundle that you created to the local machine so that you can use it to restore the artifacts later. Image Streamer user interface action: Deployment Groups > Actions > Download backup bundle 3. Edit all server profiles and server profile templates that use OS Deployment Plans: HPE OneView user interface action: Server Profiles > Actions > Edit HPE OneView user interface action: Server Profile Templates > Actions > Edit a. Choose none in the Deployment Plan section. b. Remove the associated Deployment Network iscsi boot connections. c. Uncheck Manage boot order under Boot Settings and click OK. NOTE: A warning about the deletion of associated OS volume will appear. Click OK to proceed. 46 Updating Image Streamer in a single frame configuration

47 4. Remove the Image Streamer intent from the logical enclosure: a. Edit the enclosure group to set the Deployment network type to none and remove the logical interconnect group from the logical enclosure. HPE OneView user interface action: Enclosure Groups > Actions > Edit b. Edit the logical interconnect group to remove the Image Streamer uplink set. HPE OneView user interface action: Logical Interconnect Groups > Actions > Edit c. Edit the enclosure group to add the logical interconnect group that you removed earlier. HPE OneView user interface action: Enclosure Groups > Actions > Edit d. Edit the logical enclosure to update from group. HPE OneView user interface action: Logical Enclosures > Actions > Update from group NOTE: Wait for the Update from group operation to complete before proceeding to the next step. 5. Delete the OS deployment server. HPE OneView user interface action: OS Deployment Servers > Actions > Remove 6. Update HPE OneView to a version that supports the Image Streamer version that you require. For instructions on how to update HPE OneView to a later version, see HPE OneView Help. 7. Reimage Image Streamer with the required version. IMPORTANT: The new Image Streamer version must be compatible with the updated HPE OneView version in Step Remove and reinsert the Image Streamer appliance after reimaging. This action ensures that HPE OneView discovers and claims the Image Streamer appliance afresh. 9. Create the OS deployment server after HPE OneView discovers and claims the Image Streamer appliance. HPE OneView user interface action: OS Deployment Servers > +Add OS deployment servers 10. Add the Image Streamer intent to the logical enclosure: a. Edit the enclosure group to remove the logical interconnect group from the logical enclosure. HPE OneView user interface action: Enclosure Groups > Actions > Edit b. Edit the logical interconnect group to create the Image Streamer uplink set. HPE OneView user interface action: Logical Interconnect Groups > Actions > Edit c. Edit the enclosure group to set the Deployment network type to External, the Deployment network to the network you created for deployment and add the logical interconnect group that you removed earlier. HPE OneView user interface action: Enclosure Groups > Actions > Edit d. Edit the logical enclosure to update from group. HPE OneView user interface action: Logical Enclosures > Actions > Update from group Appliance management 47

48 11. Restore the backup bundle that you downloaded in Step 2 using the Image Streamer user interface. Image Streamer user interface action: Deployment Groups > Actions > Restore from backup bundle 12. Edit the server profiles and server profile templates to use OS Deployment Plans: HPE OneView user interface action: Server Profiles > Actions > Edit HPE OneView user interface action: Server Profile Templates > Actions > Edit a. Choose the OS Deployment Plan in OS Deployment section. The iscsi boot connection is created automatically. b. Click OK. Update scenarios During an attempt to update the appliance, the following scenarios may occur: Update of active and standby appliances is successful on page 48 Update attempt returns a validation error on page 48 Active appliance update fails on page 49 Storage update fails during the active appliance update on page 49 Active appliance update fails but storage update succeeds on page 49 Active appliance and storage update succeeds but standby appliance update fails on page 49 Update of active and standby appliances is successful The update is successful and no further action is required. TIP: After an Image Streamer update, verify the status of the update in the Activity screen on the Image Streamer user interface. After the status displays complete, wait for approximately minutes before proceeding to Golden Image creation. This wait time allows the Image Streamer appliance cluster to reform. You can check the cluster status using the [V] View details option in the maintenance console before proceeding. Update attempt returns a validation error An attempt to update the appliance returns a validation error if: The selected update.bin file is corrupted. The existing version of the appliance is the same as or later than the selected update.bin version. Updating an appliance to an earlier version of firmware requires reimaging the appliance, which is only recommended when adding or replacing appliances in an existing Image Streamer configuration. The selected update.bin does not support update from the existing version. 48 Update scenarios

49 Active appliance update fails When the update of an active appliance fails: The update of the standby appliance does not start. The active appliance is reverted to the version before update. The Image Streamer appliance pair continues to work in high-availability mode after active appliance revert and storage synchronization. This action might take approximately minutes. To troubleshoot why the update failed, contact your authorized support representative. Storage update fails during the active appliance update When the storage update fails during the active appliance update: The update of the standby appliance does not start. The active appliance reverts to the version before update. The storage software reverts to the version before update. Generally, the Image Streamer appliances will continue to provide uninterrupted access to OS volumes when storage update fails. However, you must not attempt further update operations that might disrupt the servers without fixing the issue. To troubleshoot why the update failed, contact your authorized support representative. Active appliance update fails but storage update succeeds When the active appliance update fails but the storage update succeeds: The active appliance is reverted to the version before update but the updated storage version is retained. No action is required unless the updated storage version in incompatible with the existing appliance version. If a compatibility issue arises, contact your authorized support representative. Active appliance and storage update succeeds but standby appliance update fails When the active appliance update and storage update succeeds but the standby appliance update fails: The active-standby cluster cannot be formed since the standby appliance version is incompatible with the active appliance version. High-availability is affected because standby appliance is unusable. Reimage the standby appliance to the same version as the active appliance and reinsert it. Backup, restore and recovery Backup Image Streamer backup is considered as a backup of two aspects: Active appliance update fails 49

50 Backup of artifacts You can back up all the artifacts in Image Streamer by using Deployment Groups > Actions > Create backup bundle. The backup bundle contains all the artifacts that are available on the Image Streamer appliance at the time of backup. Backup of configuration data Configuration data consists of information about the active and standby appliances of the Image Streamer appliance pair, IP addresses, and details of primary and secondary appliances. The configuration information is available in HPE OneView and is backed up as part of HPE OneView backup. To create a backup in HPE OneView, navigate to Settings > Create backup from the HPE OneView main menu. For more information on creating an HPE OneView backup, see HPE OneView Help for HPE Synergy. Hewlett Packard Enterprise recommends that you back up the artifacts and configuration information whenever you make significant changes to them. Creating an HPE OneView backup and an Image Streamer backup ensures that both the configuration and artifact information are preserved. Restore and recovery There are different situations when you must consider restoring or recovering the Image Streamer appliance: Restore artifacts If you want to restore the artifacts to the instance when the last backup bundle was created, use the Deployment Groups > Actions > Restore from backup bundle option. When you restore from a backup bundle, the following actions are performed based on the status of the artifacts in the backup bundle and in the Image Streamer appliance: Artifact status Same artifacts are available in the backup bundle and the Image Streamer appliance and the artifacts in the Image Streamer appliance have not been modified after the backup. Same artifacts are available in the backup bundle and the Image Streamer appliance and the artifacts in the Image Streamer appliance have been modified after the backup. Artifacts are present only in the backup bundle but are not available in the Image Streamer appliance. Artifacts are available only in the Image Streamer appliance and are not available in the backup bundle. Action performed by Image Streamer restore operation The restore operation does not perform any action. The restore operation restores the artifacts in the backup bundle onto the Image Streamer appliance. The restore operation restores such artifacts in the backup bundle onto the Image Streamer appliance. The restore operation deletes such artifacts that are available only on the Image Streamer appliance. It is important to note that an Import artifact bundle operation is different from the Restore from backup bundle operation. An artifact bundle contains only those artifacts that you chose to include during artifact bundle creation. A backup bundle contains all the artifacts in the appliance at the time of backup bundle creation. When you perform an Import artifact bundle operation, if the same artifact is available in the artifact bundle and in the Image Streamer appliance, the artifact is imported into the Image Streamer appliance with a different name. The imported artifact name is appended with the sequence number to show the difference. 50 Restore and recovery

51 However, while performing a Restore from backup bundle operation, restoring an artifact that is available in the backup bundle and the Image Streamer appliance depends on whether the artifact has been modified since the backup. Typically, Import artifact bundle operation can be used when artifacts from another source such as another Image Streamer configuration or sample artifacts provided by Hewlett Packard Enterprise are required to be imported into an Image Streamer appliance. Recovery when an Image Streamer primary appliance pair fails and a secondary appliance pair is available This recovery option is applicable only for a multi-enclosure configuration with more than one Image Streamer appliance pair. This option must be used only if the current primary appliance stops functioning or is decommissioned and there are no options to recover it. When the Image Streamer primary appliance pair fails or is decommissioned and there is a secondary appliance pair available in the enclosure, you can change the primary Image Streamer appliance pair using the HPE OneView user interface. For information on how to change the primary Image Streamer appliance pair, see HPE OneView Help for HPE Synergy. Recovery when the Image Streamer primary appliance pair fails and no secondary appliance pair is available This recovery option is applicable when you have, A single enclosure configuration with a single Image Streamer appliance pair. A multi-enclosure configuration with a single Image Streamer appliance pair. You must follow this sequence of tasks to perform the recovery when the primary appliance pair fails and no secondary appliance pair is available. 1. From the HPE OneView main menu, navigate to the Server Profiles screen and note the list of available server profiles and their values. 2. Delete the server profiles in the logical enclosure to which the primary Image Streamer appliance pair belongs. 3. From the HPE OneView main menu, navigate to the Logical Enclosures screen. 4. Delete the logical enclosure to which the primary Image Streamer appliance belongs. 5. Remove the Image Streamer appliances from the CIM slot. 6. From the HPE OneView main menu, navigate to OS Deployment Servers screen and delete the OS deployment server. 7. Insert new Image Streamer appliances in the CIM slot. 8. From the HPE OneView main menu, navigate to OS Deployment Servers screen and create a new OS deployment server. 9. From the HPE OneView main menu, navigate to OS Deployment Servers screen and click on the Image Streamer UI link to open Image Streamer user interface. 10. From the Image Streamer main menu, navigate to Deployment Groups > Actions > Restore from backup bundle to perform a restore operation. Recovery when an Image Streamer primary appliance pair fails and a secondary appliance pair is available 51

52 11. From the HPE OneView main menu, navigate to Logical Enclosures > Create logical enclosure to create a logical enclosure. 12. From the HPE OneView main menu, navigate to Server Profiles > Create server profile to create a server profile. For more information on how to perform each of the tasks in the sequence using the HPE OneView user interface and Image Streamer user interface, see HPE OneView Help and HPE Synergy Image Streamer Help. Impact of restoring HPE OneView on Image Streamer Whenever a restore operation is performed on the HPE OneView instance that manages Image Streamer, Image Streamer performs a post-restore validation of its state and configuration against the restored state of HPE OneView. The recovery process follows a sequence: 1. User performs a restore operation on the HPE OneView instance that manages Image Streamer. 2. Image Streamer refreshes its state and configuration by validating against the restored state of HPE OneView. 3. An alert notifies you: If there is a mismatch between OS Deployment Server configuration in HPE OneView and the Image Streamer configuration. You can choose to continue with the mismatched configuration or perform corrective actions to resolve the configuration mismatch. If there is a mismatch between logical enclosure configuration in HPE OneView and the Image Streamer configuration. You can choose to continue with the mismatched configuration or perform corrective actions to resolve the configuration mismatch. If there is a mismatch between HPE OneView server profile OS deployments and the OS volumes residing in Image Streamer. You can delete the orphaned OS volumes in Image Streamer that do not have a corresponding server profile in HPE OneView after the restore operation. 4. Deployment Plans are synced automatically between HPE OneView and Image Streamer after the HPE OneView restore operation is complete. 52 Impact of restoring HPE OneView on Image Streamer

53 Image Streamer Maintenance Console About the Maintenance console The appliance maintenance console, shown in the example, provides a limited set of administrative commands for an appliance. The appliance maintenance console is an important tool for troubleshooting appliance issues when the HPE OneView UI or Image Streamer UI is not available. The appliance maintenance console is always available from the front panel console or from an SSH session if maintenance IPs are configured. In the upper left of most appliance maintenance console screens, the local appliance is identified by its location (enclosure identifier and appliance bay number) or its host name. Figure 7: Example of the Maintenance console main menu The appliance maintenance console displays an icon and a message about the state of the appliance, which can indicate one of the following actions is occurring: Normal operation Appliance is offline Appliance is being updated Appliance is synchronizing with the other appliance in the cluster Appliance is starting up, shutting down, restarting, or temporarily unavailable Image Streamer Maintenance Console 53

54 Appliance is being restored from a backup file Appliance is being reset to factory default settings Commands The body of the main menu contains commands that can be used: To view the appliance details. To restart the local appliance. To shut down the appliance. To perform a factory reset of the appliance. To reset the Maintenance console password. To launch a service console, which an authorized technical support can use to diagnose or repair a problem. To configure the MGMT port for deployment network connectivity. To configure the MGMT port for management network connectivity. To log out of the Maintenance console. Be sure to log out before removing a console (monitor, keyboard, and mouse). Otherwise, you might be leaving the Maintenance console ready to perform a command like Shutdown the next time a console is attached and the Enter key is pressed. NOTE: More information The commands displayed by the Maintenance console depend on the current state of the appliance and how the Maintenance console was accessed. Log in to the appliance maintenance console on page 56 Reset the administrator password with the appliance maintenance console on page 63 Perform a factory reset using the appliance maintenance console on page 66 Access the appliance maintenance console on page 54 Access the appliance maintenance console Access the appliance maintenance console through one of the following options. NOTE: Use the credentials of a local user with the Infrastructure administrator role when prompted. You can reset the administrator password from the appliance maintenance console. Access the appliance maintenance console through an SSH connection. Access the appliance maintenance console from an HPE Synergy Frame Link Module. Access the appliance maintenance console through a notebook or laptop. 54 Access the appliance maintenance console

55 Access the appliance maintenance console through an SSH connection NOTE: Hewlett Packard Enterprise recommends the use of these tools for accessing the appliance maintenance console through an SSH connection: PuTTY MTPuTTY Procedure 1. Invoke one of the recommended tools on your local computer. 2. Access the appliance by specifying its fully qualified domain name or its IP address. 3. Enter the user name maintenance at the login prompt. 4. Log in to the appliance maintenance console. Access the appliance maintenance console from an HPE Synergy Frame Link Module Procedure 1. Connect a keyboard, video, and mouse using the monitor port and USB ports located: On the front panel of the frame (illustration on left) On an HPE Synergy Frame Link Module at the rear of the frame (illustration on right) On connection, the Synergy console is displayed. 2. Select Actions > Serial consoles > Appliances and choose the appliance you want to access. 3. Enter the user name maintenance at the login prompt. 4. Log in to the appliance maintenance console to access the appliance maintenance console. Access the appliance maintenance console through an SSH connection 55

56 Access the appliance maintenance console through a notebook or laptop Prerequisites You have physical access to the frame You have configured the notebook computer Ethernet port for DHCP and enabled auto-negotiation A CAT5 cable Procedure 1. Connect the CAT5 cable to the Ethernet port on the notebook computer. 2. Connect the CAT5 cable to the notebook port on the front of the frame, on the front panel module (see illustration). 3. On the notebook computer, launch a VNC client application to connect to the HPE Synergy console. If prompted by the VNC client, enter the IP address (including port 5900) of the HPE Synergy frame to use for the connection: The HPE Synergy console is now available using the VNC client connection. 5. Log in to the appliance maintenance console to access the appliance maintenance console. Log in to the appliance maintenance console When you access the appliance console, you are presented with either a login screen or the appliance maintenance console main menu: Procedure 1. Access through the appliance console presents the appliance maintenance console main menu immediately. After you enter your first command and before it runs, the login screen is presented. 56 Access the appliance maintenance console through a notebook or laptop

57 Two exceptions are the Reset password and Launch service console, which require a challenge/ response authorization. 2. Access through SSH presents the login screen immediately. 3. Enter the user name and password of a local Infrastructure administrator account on this appliance. NOTE: You cannot log in using an Infrastructure administrator account that is authenticated by an authentication directory service. The appliance maintenance console login remains valid for one hour. After one hour of inactivity, you must reenter the password. The appliance maintenance console session closes after 24 hours of inactivity. About the appliance maintenance console password The appliance maintenance console has no initial password. To set it, see Reset the appliance maintenance console password on page 62. Appliance maintenance console passwords must meet the following minimum requirements: Fourteen (14) characters long One uppercase alpha character One lowercase alpha character One numeric character One special character Backup operations do not back up the appliance maintenance console password. Ensure that you can remember or retrieve the appliance maintenance console password in some other way. IMPORTANT: You can only reset the password by resetting the appliance to its original factory settings, which reverts the appliance maintenance console password to its initial setting, none. Considerations for an appliance cluster The active appliance and the standby appliance can have different appliance maintenance console passwords. The appliance maintenance console passwords are not synchronized between the active appliance and the standby appliance. More information About the Maintenance console on page 53 About the factory reset operation on page 57 Reset the appliance maintenance console password on page 62 About the factory reset operation A factory reset restores the appliance to the original factory settings, but does not change the installed firmware version. The factory reset operation can only be performed from the Image Streamer maintenance console. About the appliance maintenance console password 57

58 Use the factory reset operation for either of these reasons: To decommission the appliance so that you can migrate the hardware. If you intend to decommission the appliance, perform the factory reset without preserving the network settings and logs. If the HPE Synergy appliance is not highly available, you must reset the frame link module from the front panel display module to regain access to HPE OneView. Performing a factory reset operation on the frame link module disrupts running work loads. To return the appliance to a known state for reuse (for example, to restore the appliance from a backup file). If the appliance is highly available (the View details command on the appliance maintenance console show both active and standby as operational), the factory reset operation fails. Hence, you must always remove the standby appliance from the appliance cluster before proceeding to perform a factory reset. CAUTION: Ensure that you have a recent backup file before performing a factory reset. Never choose to preserve network settings while performing a factory reset operation. Always choose to perform a full factory reset. Appliance maintenance console main menu screen details References to the local appliance indicate the appliance that you logged into through the appliance maintenance console. Screen component Title Appliance identifier Icon State text Description Identifies the appliance maintenance console. For an appliance cluster, this text identifies the local appliance by its enclosure and appliance bay number. This text identifies a standalone appliance by its host name. Is located directly beneath the Title. Indicates the general state of the appliance. The icon is located in the upper right of the console screen. Displays one to three lines of additional text to elaborate on the state indicated by the icon. Example states include: Restoring from backup Starting Active Standby / Synchronizing Table Continued 58 Appliance maintenance console main menu screen details

59 Screen component Notification banner Commands Description Notifies or warns of a situation regarding the appliance or appliance cluster. The Notification banner spans the width of the appliance maintenance console. If no notification is pending, the Notification banner does not display. Lists the available commands that are appropriate to the state of the appliance. Examples include: View details Restart Shut down Reset password Support dump Factory reset Launch service console More information About the Maintenance console on page 53 Access the appliance maintenance console through an SSH connection on page 55 Log in to the appliance maintenance console on page 56 View the appliance details on page 62 Create a support dump file from the appliance maintenance console on page 65 Reset the administrator password with the appliance maintenance console on page 63 Appliance maintenance console details screen details The View Details command displays this screen. References to the local appliance indicate the appliance that you logged into through the appliance maintenance console. Peer appliance refers to the other appliance, regardless of its role, in an appliance cluster. Screen component Title Appliance identifier Icon Description Identifies the appliance maintenance console. For an appliance cluster, this text identifies the local appliance by its enclosure and appliance bay number. This text identifies a standalone appliance by its host name. Located directly beneath the Title. Indicates the general status of the appliance in the upper right. Table Continued Appliance maintenance console details screen details 59

60 Screen component State text Notification banner Host name IP address Model Firmware Appliances Description Displays one to three lines of additional text to elaborate on the icon state. State text examples include: Restoring from backup Starting Active Standby / Synchronizing Notifies or warns of a situation regarding the appliance or appliance cluster. The Notification banner spans the width of the appliance maintenance console. If no notification is pending, the Notification banner does not display. Displays the host name of the appliance. Displays the IP address of the appliance. The model number of the appliance running Image Streamer. The version number of the firmware running on the Image Streamer appliance and the date the firmware was last updated. For an appliance cluster, the following items are displayed first for the local appliance and then for the peer appliance. For a standalone appliance, the following items are only displayed once. Identifier State IP address Serial number Identifies the individual appliance by its enclosure and appliance bay. Icon and text indicating the state of the appliance from the perspective of the local appliance. For example, the state for a peer appliance could be Not connected, but that could not apply to a local appliance. The maintenance IP address associated with the individual appliance. The maintenance IP address is used to connect to the appliance maintenance console, but not with the UI. The serial number of the appliance hardware. Appliance maintenance console appliance states The appliance maintenance console displays an icon and a message in the upper right corner about the state of the appliance. The state might depend on the situation, especially for a highly available appliance cluster, and an action might also be required. 60 Appliance maintenance console appliance states

61 State Situation Action Active Active Disk has failed Active Standby is synchronizing Active Standby is unreachable Unsynchronized changes Standby Standby Disk has failed Standby Synchronizing Offline Manual action required The local appliance is the active appliance of the appliance cluster and is running normally. Not an appliance cluster. The disk of the active appliance has failed. The standby appliance assumes control as the single appliance. The disk of the standby appliance has failed. The active appliance continues operating as a single appliance. The local appliance is running normally. The peer appliance is being synchronized. It cannot be activated if a failure occurs before the synchronization completes. The local appliance is running normally but cannot reach the peer appliance. The peer appliance cannot become the active appliance in case of a failure. The local appliance is the standby appliance in the appliance cluster and is running normally. The disk on the local appliance failed. The local appliance can no longer serve as the standby appliance in the appliance cluster. The disk on the peer appliance failed. The local appliance is currently the standby appliance, but it will be activated automatically. The local appliance is the standby appliance and it is being synchronized. It cannot be activated if a failure occurs before synchronization completes. The local appliance cannot be activated automatically because it cannot confirm that the peer appliance is not running. Contact your authorized technical support to replace the failed disk Contact your authorized technical support to replace the failed disk Contact your authorized technical support to replace the failed disk See the alerts listed in the Activity screen for more details and a resolution. Contact your authorized technical support to replace the failed disk Contact your authorized technical support to replace the failed disk Table Continued Image Streamer Maintenance Console 61

62 State Situation Action Offline Unrecoverable error Offline Unusable (incomplete data) Resetting Restarting Restoring from backup Starting Shutting down Temporarily unavailable Updating The appliance failed with an unrecoverable error. The local appliance cannot be activated because it lacks a complete copy of the appliance data. The appliance is being reset to factory default settings. In an appliance cluster, this operation occurs before the standby appliance becomes the active appliance. The appliance is restarting and will be available shortly. The appliance will be restarted after the restoration completes. The appliance is starting up and will be available shortly. The local appliance is shutting down. The local appliance is in a transition, and its state will change. The local appliance is undergoing a software update. For information on resolving this issue, see the "Appliance error screen" in the online help. View the appliance details Use this procedure to display appliance details such as state, host name, IP address, model, firmware, and, for an appliance cluster, the state of the peer appliance. For more information, see Appliance maintenance console details screen details on page 59. Procedure 1. Access the appliance maintenance console main menu. 2. Select View details. The appliance maintenance console details screen is displayed. Reset the appliance maintenance console password Prerequisites 62 View the appliance details

63 Create a new password that fulfills the password requirements. If the current appliance maintenance console password is forgotten, perform and download a backup and then perform a factory reset of the appliance. Procedure 1. Access the appliance maintenance console main menu. 2. Log in with the user name maintenance and password (if set) at the login prompt. 3. Select Reset maintenance console password. 4. Enter the current password and the new password twice, once for verification. 5. Select OK. Reset the administrator password with the appliance maintenance console IMPORTANT: The request code is valid only while you are on the Password reset screen of the appliance maintenance console. If you return to the main menu or end the appliance maintenance console session, the request code will be invalid. You will need to start this procedure over again to acquire a new request code. You will need to contact your authorized support representative, who will send an authorization code (also known as a response code) after verifying your information. You must enter the authorization code within one hour or it becomes invalid. NOTE: This operation resets the password for a local administrator account on the appliance. It does not apply to administrator accounts authenticated by a directory service. In an appliance cluster, this operation resets the password for the administrator account on both appliances. This operation allows you to set a single-use password for the local administrator account. Use that single-use password the next time you log in to the UI with this account. You will be prompted to set a new password. Prerequisites If you lose or forget the local administrator password and can access the appliance maintenance console through the virtual console, use the following procedure to reset it. This operation provides a unique request code that you use when contacting your authorized support representative. NOTE: If you accessed the appliance maintenance console through SSH, use the User interface (UI) to reset the administrator password. Reset the administrator password with the appliance maintenance console 63

64 This capability is not available if you accessed the Maintenance console through SSH. If the password for another local Infrastructure administrator is known, use the User interface (UI) to reset the administrator password. You have access to the console of a standalone appliance or, for an appliance cluster, the console of either cluster member. Procedure 1. Access the appliance maintenance console. 2. Select Reset password. The appliance maintenance console displays a request code. 3. Telephone your authorized support representative and provide that person with the following information: The name of the person requesting the password to be reset. The name of the company that owns the appliance. The request code from the appliance maintenance console. The authorized support representative verifies the information and then sends a message to the authorized address on file. This message contains the authorization code. An ISO image, which is also the authorization code, is attached to the message. 4. Type the authorization code into the response field. 5. Determine a single-use administrator password. 6. When prompted, enter and re-enter the new password. 7. Select OK to set the single-use password. 8. Verify by logging out, then logging into this account with the new password. Shut down the appliance using the appliance maintenance console This procedure describes how to use the appliance maintenance console to perform a graceful shutdown of the appliance. This action shuts down only the local appliance of an appliance cluster. Prerequisites Ensure that all users are logged out and all ongoing work is completed. Procedure 1. Access the appliance maintenance console main menu. 2. Select Shut down in the main menu. 3. Confirm that you want to shut down the appliance. 4. Verify by observing the shutdown. 64 Shut down the appliance using the appliance maintenance console

65 Restart the appliance using the appliance maintenance console This procedure describes how to use the appliance maintenance console to shut down and then restart the appliance. This action affects only the local appliance of an appliance cluster. If the local appliance is the active appliance of an appliance cluster, restarting it (the local appliance) stops the services that were running on it. Until the peer appliance restarts those services, high availability is temporarily suspended. Prerequisites Ensure that all users are logged out and all ongoing work is completed. Procedure 1. Access the appliance maintenance console main menu. 2. Select Restart. 3. Confirm that you want to restart the appliance. 4. Verify by observing the restart. Create a support dump file from the appliance maintenance console This procedure describes how to use the appliance maintenance console to create a support dump file from the local appliance (the appliance on which the appliance maintenance console runs) and store it on a USB drive. If the local appliance is the active appliance in an appliance cluster and if the standby appliance is reachable, the support dump will contain the data for both cluster members. Otherwise, a support dump is created with data for the local appliance only. CAUTION: Creating the support dump file overwrites any existing backup file on the appliance. If possible, refrain from creating a support dump if you have not copied the backup file to an external location for safekeeping. Use the User interface to download the backup file. The support dump file is encrypted by default. Prerequisites Privileges: Infrastructure administrator Use a USB 2.0 or 3.0 device drive, formatted as an NTFS or FAT32 file system and with only one partition. If necessary, use a computer to format the USB drive. The USB drive must have enough free space (typically 1 GB to 4 GB) to store the support dump file. Restart the appliance using the appliance maintenance console 65

66 Procedure 1. Ensure that the USB drive is installed in the USB port of the local appliance. IMPORTANT: Do not remove the USB drive until the operation is complete and the appliance maintenance console advises that it is safe to remove the drive. 2. Use the appliance console to access the appliance maintenance console main menu. 3. Select Support dump. 4. A new set of commands appears. 5. Do one of the following: a. Select Create support dump to create a new support dump and copy it to the USB drive. b. Select Download existing support dump to copy a support dump from the appliance to the USB drive. 6. Wait until the support dump file is copied. There will be a message on the screen stating that the support dump was successfully completed and that it is safe to remove the USB drive. Perform a factory reset using the appliance maintenance console Prerequisites Ensure that all users are logged out and all ongoing work is completed. Back up all user files. Create a support dump file from the appliance maintenance console and save it to an external location for safekeeping. Procedure 1. Access the appliance maintenance console main menu. 2. Select Factory reset in the main menu. Always choose a full factory reset. 3. In the subsequent dialog box, do one of the following: a. Enter Y to continue the factory reset operation. CAUTION: This option erases the network settings and logs. Use this option to decommission an appliance. b. Enter N to cancel the factory reset operation and return to the main menu. 4. Confirm that you want to perform the factory reset in the subsequent dialog boxes. 5. In the next dialog box, do one of the following: 66 Perform a factory reset using the appliance maintenance console

67 a. Enter Y to continue the factory reset operation. b. Enter N to cancel the factory reset operation and return to the main menu. 6. Verify by observing the operation. NOTE: You can view details to see the progress in the top right corner of the screen. Reset successful displays when the reset has completed. About changing the MGMT port purpose The MGMT port repurpose options in the Maintenance console allow you to recover when the enclosure ring and its components are inaccessible due to management connectivity issues. Frame 1 HPE OneView 1 2 MGMT 3 LINK Frame 2 HPE OneView Image Streamer Frame 3 Image Streamer Legend: Management Network Link Network Interconnects Figure 8: A three enclosure setup 1-6 Device bays 7-8 Interconnects The illustration shows an example three enclosure setup configuration. One or both MGMT ports in a frame connect to the management network. When both MGMT ports in a frame are connected to the management network, only one of the two ports actively carries management network traffic. The other port stays in standby mode. If there is a connectivity issue on the MGMT port that carries the management network traffic, then the management network traffic is automatically switched to the standby MGMT port in the frame. About changing the MGMT port purpose 67

68 NOTE: When an Image Streamer appliance is removed from the frame, disconnect the deployment network connection for that frame. Removing the Image Streamer appliance enables the port to be available for a potential management network connection. If the frame with management network connectivity becomes unavailable or if all the MGMT ports connecting to the management network lose connectivity, the enclosure ring loses network connectivity. To recover from this state, any of the ports that are currently connected to the deployment network can be switched to connect to the management network. Switching the management network traffic to a port that previously carried deployment traffic, to regain connectivity to the enclosure ring, compromises high-availability. This state must be reverted to a high-availability state as soon as the faulty frame is recovered. Use either of the following options to change the MGMT port purpose from deployment traffic to management traffic: Connect the MGMT port of the Frame Link Module in the frame which has both Image Streamer and HPE OneView appliances to the management network. Connect the MGMT port of the Frame Link Module in the frame which has only an Image Streamer appliance to the management network. NOTE: More information The cabling must be changed when you configure the ports using the appliance Maintenance console based on the UID light indication. Configure MGMT port for deployment network connectivity on page 69 Configure MGMT port for management network connectivity on page 68 Configure MGMT port for management network connectivity This procedure is applicable for a setup with 3 enclosures or more. Prerequisites If you are performing this task from the Maintenance console of a standby Image Streamer appliance: 1. Verify if the connectivity between the active and standby appliances is healthy using the [V] View details option on the Maintenance console main menu. 2. If the connectivity between the active and standby appliances is not healthy, wait until the connectivity is restored or perform this task from the Maintenance console of an active Image Streamer appliance. Procedure 1. Connect to HPE OneView using the serial console and confirm if HPE OneView is functional. If HPE OneView is in the process of starting or failover, wait for the process to complete. 2. Access the Image Streamer Maintenance console main menu. 3. Select Configure MGMT port for management network connectivity. 4. A confirmation prompt appears. Select OK to proceed. This step powers on the UID light on the MGMT port of the enclosure that must be connected to the management network. 68 Configure MGMT port for management network connectivity

69 Figure 9: Configure MGMT port for management network connectivity 5. Connect the MGMT port to the management network based on the UID light indication. Configure MGMT port for deployment network connectivity This procedure is applicable for a setup with 3 enclosures or more. Prerequisites If you are performing this task from the Maintenance console of a standby Image Streamer appliance: 1. Verify if the connectivity between the active and standby appliances is healthy using the [V] View details option on the Maintenance console main menu. 2. If the connectivity between the active and standby appliances is not healthy, wait until the connectivity is restored or perform this task from the Maintenance console of an active Image Streamer appliance. Procedure 1. Connect to HPE OneView using the serial console and confirm if HPE OneView is functional. If HPE OneView is in the process of starting or failover, wait for the process to complete. 2. Access the Image Streamer Maintenance console main menu. 3. Select Configure MGMT port for deployment network connectivity. 4. A confirmation prompt appears. Select OK to proceed. This step powers on the blue UID light on the MGMT port of the enclosure that must be connected to the deployment network. Configure MGMT port for deployment network connectivity 69

70 Figure 10: Configure MGMT port for deployment network connectivity 5. Connect the MGMT port to the deployment network based on the UID light indication. 6. Navigate to Enclosures screen in HPE OneView user interface and reapply the configuration from Actions > Reapply configuration. MGMT port repurpose for a single enclosure setup If connectivity to single enclosure setup is lost, disconnect the cable connecting the enclosure to the HPE Virtual Connect SE 40Gb F8 Module for HPE Synergy interconnect module. This action redirects management traffic via the other MGMT port which is connected to the management network. The disconnected cable to the interconnect module can be connected after a few seconds. Manual activation of an appliance The Activate option is available in the maintenance console main menu when user intervention is required to manually designate a new active appliance. User intervention is required in a situation when the communication between active and standby appliances in an Image Streamer appliance pair is broken and the standby appliance is unable to confirm whether the active appliance is available. Figure 11: Activate option in the Maintenance console main menu 70 MGMT port repurpose for a single enclosure setup

71 Security Assumptions The Image Streamer appliance assumes that the following security aspects are met: The Image Streamer appliance operates in a secure HPE OneView managed environment and is connected to a secure management network. The Administrator obtains the Golden Images from trusted sources. The scripts used in the appliance for personalization or generalization are free from malware. The Golden Images reside on the Image Streamer OS deployment server. However, the OS deployment server does not create or manage sensitive data in the Golden Images. Authentication HPE OneView uses a secure communication channel to communicate with the Image Streamer appliance. During the creation of an OS deployment server, HPE OneView configures authentication settings for the appliance. After configuration, HPE OneView retains the credentials for accessing the appliance. When a user invokes an Image Streamer operation, HPE OneView uses the single sign-on authentication tokens to authenticate the user. Roles and Authorization HPE OneView provides authorization to Image Streamer users. Software administrator is the role that is defined in HPE OneView to authorize users to manage Image Streamer artifacts. The User roles and Authorization table illustrates the different user roles and their respective authorization levels for the artifacts and deployment process. NOTE: Image Streamer supports only the default global scope All Resources. Table 5: User roles and Authorization Role Image Streamer artifact management HPE OneView server profile with OS deployment Software Administrator Full Privileges View Only Server Administrator View Only Full Privileges Infrastructure Administrator Full Privileges Full Privileges Backup Administrator View Only No Access Network Administrator View Only No Access Table Continued Security 71

72 Role Image Streamer artifact management HPE OneView server profile with OS deployment Storage Administrator View Only No Access Scope Operator No Access No Access Scope Administrator No Access No Access Server Firmware Administrator No Access No Access Scope Based Access Control OS Deployment Plans can be scope limited so that different server administrators have access to different subsets of Deployment Plans. As new Deployment Plans are created or loaded into Image Streamer, HPE OneView scope management can be configured to determine which users can provision servers using those Deployment Plans. Artifacts in the Image Streamer appliance are not subject to scope control, as they are moved between HPE OneView instances. Artifact developers might require special consideration as they may frequently create new artifacts, and want to test deployment on servers. These operations require configuring scope and permission to modify a wide set of HPE Synergy resource types. Communication The following table lists the security mechanisms that protect the different types of data traffic. Table 6: Security mechanism Traffic REST API calls for Image Streamer management iscsi commands for booting the blade servers Security mechanism HTTPS IQN authorization Appliance Discovery Image Streamer appliances are identified using LLDP. The enclosure management interface uses the LLDP messages to establish an identity for Image Streamer appliances and HPE OneView reads the identities from the enclosure management interface. Data Protection HPE OneView protects Image Streamer artifacts from unauthorized access. The Image Streamer OS deployment server executes the Plan Scripts in a contained environment that protects the appliance from malicious scripts. The iscsi protocol has an access control mechanism based on initiator and target IQN s which restricts unauthorized access to iscsi storage volumes. The OS volumes are supported by the appliance s internal SAN technology. The SAN data storage is not encrypted. 72 Communication

73 Password Storage The Image Streamer OS deployment server randomly generates the passwords for management of OS Volumes and stores them in encrypted storage. Administrator credentials are stored and managed in HPE OneView and not in the Image Streamer appliance. Network Security The Image Streamer appliance secures different types of data using secure channels such as iscsi, the operating system s management network, the high availability feature of the operating system and RAID storage mechanism. The network traffic is further protected by the security mechanisms listed in the Security mechanism table. Audit Logs The Image Streamer appliance uses audit log to record events. The events recorded include: Startup of the appliance Shutdown of the appliance Creation, modification, or deletion of resources in the appliance Deployment or redeployment of stateless servers Changes to configuration Any authorization or authentication issues. You can download audit logs from the Actions menu on the Deployment Groups screen. Compliance The Image Streamer OS deployment server is compliant with the Hewlett Packard Enterprise security policies such as code signing and is free from malware and backdoors. Deployment and Maintenance The following factors secure the appliance and the underlying operating system: Image Streamer provides a nondisruptive software update mechanism for software updates. Image Streamer provides nondisruptive backup and restore mechanisms that do not affect the storage volumes. The backup file format is unique and proprietary to Hewlett Packard Enterprise. As an additional security measure, Hewlett Packard Enterprise recommends encrypting the backup file to protect sensitive data. Image Streamer provides a factory reset mechanism to erase the data on the appliance before any maintenance activities. Known issues There are some known security issues in the protocols used by Image Streamer. However, based on the assumptions listed for the HPE OneView and Image Streamer appliance environment and considering the security measures built into the appliance, the risks due to these security issues are low. Password Storage 73

74 The iscsi protocol used in the appliance storage volumes is a clear text protocol and relies on IQN and CHAP authorizations that are not considered as strong security mechanisms. The high availability and RAID communications are in cleartext. 74 Security

75 Troubleshooting Image Streamer Basic troubleshooting techniques Image Streamer OS deployment server has different troubleshooting mechanisms that help you to resolve issues. You can obtain a history of activity and encountered errors by examining the screens and activity logs using the Image Streamer user interface. Activity details provide additional information about actions and any issues that might have occurred. To view the activity details, from the main menu select Activity. Deployment failures might be related to script problems. Review the deployment and capture activity details to view the errors from script execution. You can download the deployment and capture logs using the download link available in the activity description. Refer to the alerts that you notice in the Image Streamer Deployment Appliances screen. You can also view the Image Streamer Dashboard to get the status of the various resources. You can refer to the alerts that you notice in HPE OneView to understand the issues with Image Streamer. If you are unable to troubleshoot an issue, then create a support dump to gather logs and other information required to debug. The support dump file can then be shared with your authorized support representative for analysis. For information on how to create a support dump, see HPE Synergy Image Streamer Online Help. OS deployment fails after primary Image Streamer appliance is removed and reinserted Symptom In a multienclosure setup, when you remove a primary Image Streamer appliance pair from the CIM slot: For continued management of already deployed OS Volumes and to support new deployments, invoke the Change Deployment Appliance operation from Edit OS Deployment Server screen in HPE OneView user interface. This action assigns an existing secondary Image Streamer appliance pair with a logical enclosure already configured, as the new primary Image Streamer appliance. A removed primary Image Streamer appliance can be reinserted in the respective CIM slot. After reinserting the old primary appliance, if you reconfigure a logical enclosure on this old primary appliance and reinvoke Change Deployment Appliance operation, the old primary appliance can be reassigned as the new primary appliance. This action ensures that the overall topology of the Image Streamer appliances remain unaffected in spite of the insertion/removal of the primary Image Streamer appliance pair. Once the reinserted appliance is assigned as the primary deployment appliance, you can resume OS deployments on the newly assigned primary appliance. However, when you perform the preceding sequence of tasks, you might encounter the following error when performing a new deployment: Unable to expand golden image Troubleshooting Image Streamer 75

76 Cause In an environment with multiple logical enclosures configured, newly uploaded Golden Images in the primary Image Streamer appliance pair are synced periodically to the secondary Image Streamer appliance pairs. This periodical synchronization is executed every 30 minutes. You might have invoked the Change Deployment Appliance operation before the newly uploaded Golden Images are synced to the secondary Image Streamer appliance pairs. Action 1. Always perform a backup of the Golden Images in your local repository before removing a primary Image Streamer appliance pair from the CIM slot. Save this backup of the Golden Images from the primary appliance to a preferred location. 2. Once the removed primary appliance is reinserted and restored to its primary status, you must restore the Golden Images from the backup before OS deployment. 3. If you did not restore the Golden Images before OS deployment and encounter the Unable to expand golden image error, restore the Golden Images from the backup and retry the OS deployment. Active-standby Image Streamer appliance pair is not highly available Symptom High availability is compromised. The active-standby appliances in an appliance pair are not highly available. Cause One of the appliances in the active-standby appliance pair is not functioning. In such a scenario when active appliance is nonfunctional, the standby appliance in the appliance pair will take over and become the new active appliance. Action 1. Ensure that the peer active appliance is in an operational and reachable enclosure. Use the maintenance console for detailed diagnostic information. 2. To restore high availability, remove and reinsert the nonfunctional appliance. Changes to compute module settings are not updated onto Image Streamer Symptom Changes to the compute module settings are not updated after reboot. Cause The downlink from the interconnect to the compute module is broken. 76 Active-standby Image Streamer appliance pair is not highly available

77 Action Ensure that the downlink from the interconnect to the compute module is working. Compute module waits in PXE boot mode due to unavailability of OS volume from Image Streamer Symptom After a downtime, the compute module powers on but waits in PXE boot mode. Cause When the enclosure is powered on after a downtime, the compute module powers on immediately, but the Image Streamer appliance requires minutes to boot. During this time, HPE ilo does not add the OS volume to the booting sequence. If you attempt to boot the compute module before Image Streamer is ready, the boot fails or causes the compute module to wait in PXE boot mode. NOTE: To avoid this issue, wait for 30 minutes after Image Streamer is powered on before booting the compute modules. Action 1. Identify if the Image Streamer appliance is available using any or all of the following steps: a. Navigate to the Server Profile screen in HPE OneView user interface. The Server Profile screen displays an alert about the unavailability of the OS volume. Wait for the alert to clear. b. Verify if the OS deployment server State displays Connected on the OS Deployment Servers screen in HPE OneView user interface. c. Verify if the Image Streamer appliance details are displayed in the Deployment Appliances screen in Image Streamer user interface. d. Verify if the Volume bar displays the available storage space for new OS volumes and the expanded Golden Images. The Volume bar can be seen in the Deployment Appliances screen in Image Streamer user interface. e. Navigate to the OS Volume screen in the Image Streamer user interface. The OS Volume screen displays an alert about the availability of the OS volume. Wait for the alert to clear. f. Verify if the following alert is displayed during the boot sequence: Unable to read storage system details. Wait for the alert to clear. 2. Reboot the compute module using the HPE OneView user interface. Creation of OS deployment server (Image Streamer) fails due to conflict in IP address Symptom Creation of OS deployment server in HPE OneView fails due to conflict in IP address. Compute module waits in PXE boot mode due to unavailability of OS volume from Image Streamer 77

78 Cause The IP address selected is already in use. Action 1. Ensure that the correct IP address range is specified and there are sufficient IP addresses that are available. 2. After checking the availability of IP addresses: a. Delete the failed OS deployment server. b. Reinsert the Image Streamer appliance pair in the CIM slot. c. Create a new OS deployment server using the Create option in the OS Deployment Servers screen in HPE OneView user interface. Creation of server profile for a server hardware may fail if attempted immediately after logical enclosure creation for the bounded enclosure group Symptom Creation of server profile in HPE OneView might fail when: You attempt to create a server profile with an OS Deployment Plan that was added immediately before the creation of the logical enclosure. AND You attempt the operation immediately after the logical enclosure is created. Cause The Golden Image for the selected OS Deployment Plan is not expanded. Action Retry creating the OS volume after minutes. HPE OneView does not claim Image Streamer appliance after a reset Symptom After you perform a factory reset of the Image Streamer appliance using the maintenance console, HPE OneView does not claim the Image Streamer appliance. You can identify this because the claim task on the Activity screen in HPE OneView user interface is not listed. Cause The active Image Streamer appliance was reset but is not yet claimed by HPE OneView. 78 Creation of server profile for a server hardware may fail if attempted immediately after logical enclosure creation for the bounded enclosure group

79 Action After a factory reset from the maintenance console, click the refresh link on the Enclosures screen in HPE OneView user interface. OS deployment server creation fails due to communication issues between HPE OneView and Image Streamer Symptom OS deployment server creation fails due to communication issues between HPE OneView and Image Streamer. Cause This issue can occur when: The communication between the Image Streamer appliance and HPE OneView is not working. Action 1. Perform a factory reset of the Image Streamer appliance using the Maintenance console. 2. Reinsert the Image Streamer appliance. 3. Refresh the enclosure. 4. Verify if the Image Streamer appliances are displayed on Create OS deployment server screen. 5. Delete the OS deployment server if it exists and recreate a new OS deployment server. Image Streamer appliance loses management network connectivity in single enclosure setup Symptom Image Streamer appliance loses management network connectivity in single enclosure setup Cause The management ports are switched to link network. Action See MGMT port repurpose for a single enclosure setup. Image Streamer AMVM is unavailable Symptom AMVM is unavailable. If AMVM is not installed on the appliance, the Appliance Virtual Machine section on the Deployment Appliances screen in HPE Image Streamer user interface displays the following message: Appliance Virtual machine is not available on the deployment appliance. OS deployment server creation fails due to communication issues between HPE OneView and Image Streamer 79

80 If the logical enclosure creation is not successful, when you try to edit the Appliance Virtual Machine settings from the Actions > Edit virtual machine settings, the user interface displays the following message: To create virtual machine settings, you must first create a logical enclosure for the deployment appliance. Solution 1 Cause AMVM is not created during creation of logical enclosure. Action 1. Verify the status message displayed in the description of Update Image Streamer task on Activity screen in Image Streamer. 2. Use the following API to reinstall the AMVM, if the Update Image Streamer task description displays the error message:failed to create amvm: a. Use the GET command to read the current network configuration: curl -ikg -H 'X-API-Version : 300' -H 'Auth : <Authtoken>' -X GET <ImageStreamerClusterIPFromBrowser>/rest/appliance/i3s/amvm GET response: {"managementipv4address": "MGMT_IP", "managementipv4gateway": "MGMT_GW", "dataipv4address": "DATA_IP", "managementipv4subnet": "MGMT_MASK", "dataipv4subnet": "DATA_MASK", "amvmstate": "shut off"} b. Use the DELETE command to uninstall AMVM. This command is useful when creation of logical enclosure attempted an AMVM installation but failed to install AMVM. curl -ikg -H 'X-API-Version : 300' -H 'Auth : <Authtoken>' -X DELETE DELETE response: {"status": "success", "reason": ""} To remove AMVM from the standby node of the Image Streamer appliance pair, append? ispeerrequest=true to the previously mentioned URL. c. Use the POST command to install and configure AMVM. Use the same IP details that you obtained using the GET command: curl -ikg -H 'X-API-Version:300' -H 'Content-Type:application/json' -H 'Auth: <Authtoken>' -X POST rest/appliance/i3s/amvm -d '{"mgmtipv4subnet": "MGMT_MASK","mgmtipv4gateway": "MGMT_GW","amvmhostname": "amvmhost","dataipv4": "DATA_IP","dataipv4subnet": "DATA_MASK", "mgmtipv4": "MGMT_IP"}' POST response: {"reason": "", "status": "success"} To install AMVM on the standby node of the Image Streamer appliance pair, append? ispeerrequest=true to the previously mentioned URL. IMPORTANT: AMVM installation takes approximately 2-3 minutes. Do not terminate the operation while it is in progress. 80 Troubleshooting Image Streamer

81 NOTE: At any instance, AMVM runs on only one of the cluster nodes, active or standby. Solution 2 Cause The active appliance hosting the virtual machine fails. Action Reissue the REST call for starting the virtual machine on the new active appliance. For information on how to reissue the REST call, see HPE Synergy Image Streamer Online Help. Image Streamer primary appliance is not responding Symptom The current primary appliance is not responding and hence, the management interface cannot be rendered. Cause The current primary appliance is not functioning or is decommissioned. To recover from this situation where no primary appliance is available, use the following steps in the Action section. Action 1. Check if there are alerts for the OS deployment server in HPE OneView. 2. If a secondary logical enclosure configured with an Image Streamer appliance is not available: a. Delete the OS deployment server and recreate it. For information on how to delete and create an OS deployment server, see HPE OneView Help. 3. If a secondary logical enclosure configured with an Image Streamer appliance is available: a. Wait for a minimum of 2 hours after the Image Streamer appliance is powered on before attempting to change the primary deployment appliance. This provides time for the scheduled backup operation and the latest backup will be available to restore the appliance. b. If a backup is available and you are ready to change the primary depoyment appliance, navigate to the Edit screen of the OS deployment server in HPE OneView user interface. c. Choose an appliance from the Deployment appliances drop-down menu. d. In the Change deployment appliance confirmation dialog, click Yes, change deployment appliance to restore the recently selected deployment appliance with the most recent backup and proceed with the primary deployment appliance change. Image Streamer primary appliance is not responding 81

82 Image Streamer restore operation stops abruptly Symptom Image Streamer restore operation stops abruptly. Solution 1 Cause The artifacts in the backup bundle already exist on the appliance. Action Delete existing artifacts in the Image Streamer appliance and retry the restore operation. Solution 2 Cause One of the artifacts in the backup bundle is a Deployment Plan without a Golden Image. Action Do not use a Deployment Plan without a Golden Image. A Deployment Plan without a Golden Image cannot be used for OS deployment. OS deployment using Image Streamer fails Symptom OS deployment using Image Streamer fails. Cause The Deployment Plan used for the OS deployment is invalid due to one or all of the following reasons: The Plan Scripts used for the deployment are invalid and contain errors. The connections created for the compute modules in the server profile are not valid. Action Ensure the Plan Scripts used for the deployment are valid. Ensure that the connections created for the compute modules in the server profile are valid. Download the deployment logs from the Activity screen on the Image Streamer user interface to check for errors. 82 Image Streamer restore operation stops abruptly

83 Problems in the functioning of the Image Streamer standby appliance Symptom The standby appliance is either unavailable or cannot be activated. Solution 1 Cause The synchronization between the active and standby appliances is in progress. This synchronization might be triggered when the active-standby cluster is reformed after a reboot or a reinsert of the appliance. Action No action required. Wait until the changes performed on the active appliance have synchronized with the standby appliance. The wait time depends on the amount of data undergoing synchronization. Typically, it might take minutes. Solution 2 Cause The appliance bay where the standby appliance is present is not functioning. Action 1. Check for appliance bay error messages in the Activity screen of HPE OneView user interface. 2. Move the standby appliance to a different enclosure in the same interconnect link topology with a similar configuration of the other standby appliances. Solution 3 Cause The standby appliance malfunctions. Action Replace the standby appliance. Unable to access Image Streamer appliance from HPE OneView Symptom Unable to access an Image Streamer appliance from HPE OneView. Problems in the functioning of the Image Streamer standby appliance 83

84 Solution 1 Cause The Image Streamer management network is not consistent with HPE OneView user interface settings. Action Check that the HPE OneView user interface network settings are not changed Solution 2 Cause The Image Streamer appliance is in the process of failover or reboot. Action 1. Wait for the failover or reboot to complete. It may take approximately minutes for a failover to complete successfully. 2. Verify the status of the failover operation using the Maintenance console. OR Action 1. NOTE: Use this option last after checking the other options provided. Check the primary appliance status using Maintenance console to ensure that the appliance is not amidst any operation. 2. If a secondary logical enclosure configured with an Image Streamer appliance exists, change the primary appliance from the HPE OneView OS deployment server screen. Unable to include support dump for a standby Image Streamer appliance Symptom The support dump created from the Image Streamer user interface or service console contains information only from the active appliance. Cause The active-standby cluster formation has issues and the support dump gets created only for the active appliance. 84 Unable to include support dump for a standby Image Streamer appliance

85 Action Create a standby appliance support dump using the service console of the standby appliance. Unable to power on an Image Streamer appliance on a remote enclosure in a multi-enclosure setup Symptom With a multi-enclosure setup, when you try to power on an Image Steamer appliance in a remote enclosure, the following error message appears on the Enclosures screen in HPE OneView. Figure 12: Error message when an Image Streamer appliance in a remote enclosure is powered on Action Power on the Image Streamer appliance manually. An Image Streamer appliance available in a remote enclosure cannot be powered on using HPE OneView. Unable to power on an Image Streamer appliance on a remote enclosure in a multi-enclosure setup 85