This document describes the management of the HPE ProLiant for Microsoft Azure Stack
System. This document is intended for the person who installs, administers, and troubleshoots
servers and is skilled in network configuration and virtual environments.
Part Number: 876840-007
Published: June 2019
Edition: 7
Copyright 2017-2019 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 12.211 and 12.212, 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
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in
the U.S. and other countries.
Microsoft, Azure, Azure Stack, Windows, and Windows Server are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
CISCO® is a registered trademark of Cisco Systems, Inc. in the U.S. or certain other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
Acronyms and abbreviations...............................................................74
5
Product introduction
HPE ProLiant for Microsoft Azure Stack is a hybrid cloud solution that transforms on-premises data center
resources into flexible hybrid cloud services. These services provide a simplified development,
management, and security experience consistent with Azure public cloud services.
The HPE ProLiant for Microsoft Azure Stack hybrid cloud solution is co-engineered by Hewlett Packard
Enterprise and Microsoft. This collaboration allows businesses to:
•maintain data sovereignty
•run high performance analytics
•run big data and low-latency applications
•support edge and disconnected applications
•deploy applications to either the public or private cloud
Current version
About this document
This document provides user information about the HPE ProLiant for Microsoft Azure Stack solution.
Important changes included in this updated HPE ProLiant for Microsoft Azure Stack User Guide are:
•HPE Insight Remote Support information has been removed from this guide. HPE Insight RS is no
longer supported for any version of HPE ProLiant for Microsoft Azure Stack.
•The "Updates" section has been reorganized for a more logical flow and the role of HPE Solution
Update Bundle has been clarified.
•Information about managing HPE iLO credentials has been expanded and clarified.
HPE ProLiant for Microsoft Azure Stack solutions
Because the HPE ProLiant for Microsoft Azure Stack can consist of two distinct solutions, the following is
used to identify each solution in this document:
Table 1: HPE ProLiant for Microsoft Azure Stack solutions
Shipped before June 4, 2018Shipped after June 4, 2018
Solution recipe1.0.xxxx.x2.0.xxxx.x
Remote SupportHPE Insight Remote SupportHPE OneView Remote Support
Compute nodesHPE ProLiant Gen9HPE ProLiant Gen9 or Gen10
Management nodeHPE ProLiant Gen9HPE ProLiant Gen9 or Gen10
NOTE: The term "recipe" refers to the defined combination of hardware, firmware, and software
components that make up the complete HPE ProLiant for Microsoft Azure Stack solution. The recipe is
updated regularly when new components are available and is identified by a unique coded
“series.yearmonth.release” tag.
For the latest supported hardware, firmware, and software versions, see:
6 Product introduction
•HPE ProLiant for Microsoft Azure Stack Gen9 Software and Firmware Compatibility Matrix
•HPE ProLiant for Microsoft Azure Stack Gen10 Software and Firmware Compatibility Matrix
For information on enhancements and fixes, see the HPE ProLiant for Microsoft Azure Stack Release
Notes.
Revision history
RevisionDateDescriptionPart number
1November
2017
2April 2018Add support for Cisco switches.876840-002
3June 2018•Add Gen10 servers.
4July 2018•Clarify text concerning availability of 16-node support.
5October 2018 •Add support for Gen10 management node.
6March 2019•Add support for All-Flash solutions
Initial release of HPE ProLiant for Microsoft Azure Stack
User Guide
•Add HPE OneView RS support.
•Move legacy IRS content to separate chapter
•Add HPE OneView 4.0 support.
•Add content about soon to be supported add node
feature.
•Add instructions to find system information required to
add nodes.
•Add support for Arista switches.
876840-001
876840-003
876840-004
876840-005
876840-006
•Correct HLH updates from SPP to HPE solution
update bundle
•Reorganize the Updates section
•Enhance and correct information about managing iLO
credentials
•Remove Insight Remote Support information
7June 2019•Update locations of existing tools
•Add Cisco switch support for Gen10 systems
876840-007
Product introduction7
HPE ProLiant for Microsoft Azure Stack
solution overview
HPE ProLiant for Microsoft Azure Stack is a solution that uses a combination of:
•Hewlett Packard Enterprise hardware
•Hewlett Packard Enterprise and Microsoft software
•Hewlett Packard Enterprise services
•Hewlett Packard Enterprise and Microsoft support
This hybrid cloud solution is co-engineered by Hewlett Packard Enterprise and Microsoft to enable the
easy movement and deployment of applications. These features combine to meet security, compliance,
cost, and performance needs:
•Scaling from 4 to 12 Gen9 nodes, 4 to 16 Gen10 Hybrid nodes, or 4 to 8 Gen10 All-Flash nodes
•Based on industry-leading HPE ProLiant servers with core, memory, and storage configuration
flexibility
•Factory integrated for quality and faster time-to-value with onsite deployment to address your specific
data center needs.
Hardware overview
Your HPE ProLiant for Microsoft Azure Stack solution is engineered and factory-built in an HPE rack.
Standard rack options are available for this solution. The rack and power infrastructure choices include
basic and standard HPE PDUs and HPE iPDUs, and an optional 8 or 16-port KVM switch.
For Gen9 solutions, see HPE ProLiant for Microsoft Azure Stack Gen9 Software and FirmwareCompatibility Matrix.
For Gen10 solutions, see HPE ProLiant for Microsoft Azure Stack Gen10 Software and Firmware
Compatibility Matrix.
8 HPE ProLiant for Microsoft Azure Stack solution overview
Gen9 solutions
FrontRear
1
3
4
3
5
2
Figure 1: HPE ProLiant for Microsoft Azure Stack Gen9 rack view
2(1) HPE ProLiant DL360 Gen9 or Gen10 with Microsoft Azure Stack Hardware Lifecycle Host
management node.
3(4-16) HPE ProLiant DL380 Gen10 Microsoft Azure Stack Hybrid nodes.
(4-8) HPE ProLiant DL380 Gen10 Microsoft Azure Stack All-Flash nodes.
4(1) Optional 8 or 16-port KVM switch and optional LCD8500 Rackmount console
5(2 or 4) Vertical HPE G2 Standard or Metered power distribution units
Hardware Lifecycle Host Management node
The Hardware Lifecycle Host (HLH) is an HPE ProLiant DL360 Gen9 or Gen10 Server. The HLH is used
for solution deployment, monitoring, and management. The HLH is a Hyper-V host for HPE OneView
software management components.
NOTE: HPE ProLiant for Microsoft Azure Stack solutions ordered before June 4, 2018, are configured
with recipe 1.x and include Gen9 based Azure Stack compute nodes and upgraded with HPE OneView
Remote Support. HPE ProLiant for Microsoft Azure Stack solutions ordered after June 4, 2018, ship from
the factory with an updated solution recipe 2.x that includes Gen9 or Gen10 based Azure Stack compute
nodes and HPE OneView Remote Support. Therefore, HPE Insight Remote Support is no longer
available or used in HPE ProLiant for Microsoft Azure Stack solutions.
Management node hardware
The HLH Management node is composed of the following hardware components:
The Management node hosts the components for the installed recipe version as specified in the HPE
ProLiant for Microsoft Azure Stack Gen9 Software and Firmware Compatibility Matrix and HPE
ProLiant for Microsoft Azure Stack Gen10 Software and Firmware Compatibility Matrix.
The Management node acts as a Hyper-V host and hosts the HPE OneView instances that manage and
monitor the solution. During deployment and upgrade the HPE Solution Update Bundle and solution
custom SPP will typically be loaded onto the management node. Scripts residing on the Management
node orchestrate the delivery of those components to the rest of the solution. A typical recipe upgrade
scenario will extract an HPE Solution Update Bundle on the Management node and initiate an upgrade
script. The HPE Solution Update Bundle contains all the HPE components of the solution recipe.
(4) 600GB disks configured in a RAID
6 array
546FLR-SFP+ 10Gb640FLR-SFP+ 25Gb
Dedicated iLO 4 with the iLO
Advanced License
Azure Stack compute nodes
The Azure Stack compute nodes consist of HPE DL380 servers configured with the following:
Reflects capacity of (HDD) drives for Hybrid solutions. Hybrid solutions will additionally include cache (WI or MU
SSD) drives.
2
Advanced Premium Security edition.
1
40TB, 60TB, or 80TB
(Hybrid storage)
48TB, 72TB, 96TB, or 120TB
(Hybrid solutions)
12.8TB, 19.2TB, 25.6TB,
38.4TB, 51.2TB, 76.8TB, or
102.4TB (All-Flash solutions)
2
4-16 for Hybrid solutions
4-8 for All-Flash solutions
Solution switches
The HPE ProLiant for Microsoft Azure Stack solution supports the following Hewlett Packard Enterprise,
Cisco, or Arista switches.
12HPE ProLiant for Microsoft Azure Stack solution overview
The Top of Rack (ToR) switch pair is used by the Azure Stack nodes for solution production and storage
traffic. If used, the Baseboard Management Controller (BMC) switch is used primarily for management
connections—iLO, iPDU's. The ToR and BMC switches must be from the same switch family.
NOTE: For the latest supported firmware and software versions, see the HPE ProLiant for Microsoft
Azure Stack Software and Firmware Compatibility Matrix.
HPE switches
The HPE FlexFabric 5900 and 5950 switch series is a family of high performance and low-latency data
center switches. These switches can handle virtual environments and convergence of Ethernet and
storage traffic.
ComponentSolutionDescriptionQuantity
Gen9Gen10
HPE 5900AF 48XG 4QSFP+XToR switch2
HPE 5950AF 48SFP28 8QSFP28XToR switch2
HPE 5900AF 48G-4XG 2QSFP+XXBMC Switch1
Cisco switches
These high performance, low-latency Cisco switches are available as an optional alternative to the
standard Hewlett Packard Enterprise data center switches in Gen9 and Gen10 solutions.
ComponentSolutionDescriptionQuantity
Gen9Gen10
Nexus N3K-C3172PQ-XLXToR switch2
Nexus N3K-C3048-FA-L3XBMC Switch1
Nexus N9K-C93180YC-EXXToR switch2
Nexus N9K-C9348GC-FXPXBMC switch1
NOTE: Hewlett Packard Enterprise recommends purchasing a Cisco support agreement with a similar
level of support to the rest of the solution. At minimum, a support agreement allowing the ability to
download firmware is required for the specific models listed and FW version specified in the HPEProLiant for Microsoft Azure Stack Gen9 Software and Firmware Compatibility Matrix are
supported. See Support for products not branded Hewlett Packard Enterprise on page 71 for
information about support for Cisco switches.
Arista switches
These high performance, low-latency Arista switches are available as an optional alternative to the
standard Hewlett Packard Enterprise data center switches in Gen10 solutions. See the HPE ProLiant forMicrosoft Azure Stack Gen10 Software and Firmware Compatibility Matrix for the latest firmware
required for these switches.
ComponentSolutionDescriptionQuantity
Gen9Gen10
Arista DCS-7160-48YC6-RXToR switch2
Arista DCS-7020TRA-48-RXBMC Switch1
HPE ProLiant for Microsoft Azure Stack solution overview13
Network cabling
The solution is either shipped from the factory already cabled or is cabled by Hewlett Packard Enterprise
personnel. Do not remove, reroute, or otherwise change network cables. If a network cable fails, do not
replace the cable until a replacement is available.
Optional components
HPE G3 KVM analog switches
HPE KVM Analog Console Switches allow you to view and manage up to 256 rackmount servers across
your data center through a single user interface. This console utilizes a local On-Screen Display (OSD)
interface accessed through a rack console, such as the HPE LCD8500. The console provides intuitive
menus for accessing each attached server or serial managed device.
HPE G3 KVM Analog Console Switches support an optional USB Remote Access Key that allows you to
upgrade to KVM-over-IP functionality, providing remote access and management through the On-Board
Web Interface (OBWI). The new G3 models also support HPE Power Discovery Services and Location
Discovery Services when connected to the appropriate power distribution unit and KVM rack console.
HPE KVM Analog Console Switches are available in 8 and 16-port versions. Standard rack mounting of
the KVM Analog Console Switch shares 1U of front panel rack space with the HPE LCD8500 display
console.
For additional usage information, refer to the HPE G3 KVM Console Switch User Guide.
HPE Intelligent PDUs
The HPE Intelligent PDU brings state-of-the-art management and control to rack-mounted PDUs. This
management feature can be used to prevent over-provisioning of power that might restrict growth in your
data center. Using core and stick architecture, the HPE Intelligent PDU provides monitoring of power
consumption at the core, load segment, stick, and outlet level with unmatched precision and accuracy.
Remote management is built in and provides power cycle ability of individual outlets on the Intelligent
Extension Bars. Hewlett Packard Enterprise is the first to incorporate Power Discovery Services. When
combined with the HPE line of Platinum or Platinum Plus high efficiency power supplies, Power Discovery
Services communicates with the attached servers to collect asset information for the automatic mapping
of the power topology inside a rack. This speeds implementation time and greatly reduces the risk of
human errors that can cause power outages.
NOTE: iPDUs are only supported in Gen9 (recipe 1.x) solutions. iPDUs are not supported in Gen10
(recipe 2.x) solutions.
For additional usage information, refer to the HPE Intelligent Power Distribution Unit User Guide.
HPE G2 Metered PDUs
HPE G2 Metered Power Distribution Units (PDU) provide both local and remote rack power management
to meter or restrict outlet usage. Each PDU can be accessed and configured remotely through secure
Web, SNMP or SSH interfaces and supports multiple access levels for enhanced security. An LCD screen
provides local monitoring and alert indications.
The HPE G2 Metered PDUs are a low-profile design with multiple mounting options and offer complete
compatibility with HPE Advanced and Enterprise series racks. Up to four units can be daisy-chained to
share the network connection and IP address. The HPE G2 Metered PDU network management card can
be removed and replaced (hot swap) without affecting power distribution for zero downtime for network
connection issues.
14HPE ProLiant for Microsoft Azure Stack solution overview
For more information see the HPE G2 Series Metered, Switched, and Metered & Switched Power
Distribution Units User Guide and HPE G2 Metered Power Distribution Units QuickSpecs.
HPE Update Service for HPE ProLiant for Microsoft Azure Stack
You have an optional update service available called the "HPE Update Service for HPE ProLiant for
Microsoft Azure Stack." This update service allows you to engage HPE ProLiant for Microsoft Azure Stack
experts to implement HPE software and firmware updates quickly and efficiently, and reduce the
disruption to your environment.
Expansion and scaling
HPE ProLiant for Microsoft Azure Stack is designed to be upgraded and expanded in a controlled
environment. Refer to the table below for current information on availability of certain features.
For more information about each of these features, select the link in the table.
Expansion featureSupportedNot supported
Adding nodes to an existing scale unitX
Adding scale units or regions to an existing deploymentX
Expanding storage capacityX
Adding memoryX
Adding nodes to an existing scale unit
Hewlett Packard Enterprise recommends that you consider the CPU, memory, and storage growth rates
of your workload when performing solution sizing. Then purchase sufficient capacity in each scale unit to
meet future workload demands.
Adding nodes to an existing scale unit is supported subject to the following limitations:
•The existing scale unit has been updated to Microsoft Azure Stack 1807 or newer that supports the
"Add Node" capability. See the Microsoft release notes at https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-update-1807.
•The maximum number of Azure Stack compute nodes is limited to the current maximum for your
system: 8 (Gen10 All-Flash), 12 (Gen9), or 16 (Gen10 Hybrid).
•All Azure Stack nodes must be configured identically, including CPUs, memory, and storage
resources. For instructions on how to find the required information about existing Azure Stack nodes,
see Preparing for Add Node.
•The mandatory Add Node service from HPE Pointnext Operational Services must be used to provide
onsite node hardware installation into the rack and requisite updates to HPE Management tools and
switch configurations.
•The customer is responsible for the logical addition of the new Azure Stack nodes through the Azure
Stack user interface.
Adding scale units or regions to an existing deployment
Adding scale units or regions is not currently supported.
Based on the constraints of Microsoft Azure Stack software, at initial release, a single region is supported
and within that region a single scale unit is allowed.
HPE ProLiant for Microsoft Azure Stack solution overview15
At initial release, it is possible to increase capacity through the addition of new scale units. Each new
scale unit must be deployed as a separate instance of Microsoft Azure Stack with its own unique external
DNS domain.
Expanding storage capacity
HPE ProLiant for Microsoft Azure Stack does not directly support expansion of storage such as adding
drives or replacing lower capacity drives with higher capacity drives.
The Microsoft Azure Stack architecture currently requires all nodes in a scale unit to be configured using
an identical homogeneous configuration. For storage, consistent capacity cache drive sizes and
quantities must be consistent across the entire scale unit. This requirement prevents incrementally adding
or replacing disks in the solution with the exception of replacing drives that have failed with identically
sized replacements.
The solution is designed to support expanding storage capacity following a hyperconverged model of
creating additional nodes or scale units. However, neither is available at initial release. See Addingnodes to an existing scale unit or Adding scale units or regions to an existing deployment for
details.
Adding memory
Adding memory to an already deployed HPE ProLiant for Microsoft Azure Stack system is supported. This
feature will allow expansion of memory capacity without the need to redeploy.
The Microsoft Azure Stack architecture currently requires all nodes in a Scale Unit to have the same
physical amount of memory.
NOTE: When expanding, only options listed in the HPE ProLiant for Microsoft Azure Stack Gen9
Quickspecs or HPE ProLiant for Microsoft Azure Stack Gen10 Quickspecs are supported.
Depending on the original configuration, this may require removing previously installed memory to
prevent expanding to an unsupported configuration.
The minimum supported version of Microsoft Azure Stack for memory expansion is 1802.
For additional information on how to implement memory expansion, contact your Hewlett Packard
Enterprise account team or HPE Pointnext representative.
HPE OneView
Using HPE OneView with HPE ProLiant for Microsoft Azure Stack
HPE OneView is used as an infrastructure automation engine serving as the core element of the
hardware monitoring and life cycle management solution.
HPE OneView unified infrastructure management capabilities enable you to closely monitor the health of
your HPE ProLiant for Microsoft Azure Stack solution hardware, including iPDUs. The dashboards of HPE
OneView provide real-time status information and alerts, which are useful for tracking and maintaining the
health of your solution. Additionally, the HPE OneView API and broad composable environment, including
language bindings and expanding environment of third-party integrations, provide the opportunity to
integrate HPE ProLiant for Microsoft Azure Stack solution monitoring into your tool of choice. For more
information, see: https://www.hpe.com/us/en/solutions/developers/composable.html.
HPE OneView is used to increase reliability by integrating HPE OneView template-based management
capabilities to simplify life cycle management tasks. Each solution is deployed with an HPE OneView
server profile template designed and validated for use with Microsoft Azure Stack nodes.
16HPE ProLiant for Microsoft Azure Stack solution overview
NOTE: Do not create or modify the server profiles or server profile templates directly. To manage the
solution properly when performing daily monitoring, users are encouraged to use only user accounts with
read-only roles to avoid accidentally modifying server profiles or templates.
HPE OneView 4.0 provides enhanced remote support functionality as well as fully integrated hardware
monitoring, management, and remote support functions. This simplifies and streamlines basic system
maintenance functions, such as updates and backups. See HPE OneView Remote Support for more
information about HPE OneView Remote Support.
HPE OneView user guides, other manuals, and white papers are available on the Hewlett Packard
Enterprise Information Library: http://www.hpe.com/info/oneview/docs.
HPE OneView Remote Support
HPE OneView RS is a software solution that enables reactive and proactive remote support to improve
the availability of your HPE ProLiant for Microsoft Azure Stack solution.
HPE OneView RS enables enhanced delivery of your warranty or support services contract. To ensure
maximum system availability, HPE OneView RS supplements continuous system monitoring by providing
intelligent event diagnosis and automatic, secure submission of hardware event notifications to Hewlett
Packard Enterprise. This continuous monitoring initiates a fast and accurate resolution, based on your
product service level. If configured and available in your country/region, notifications may be sent to your
Hewlett Packard Enterprise Authorized Channel Partner for onsite service.
HPE OneView RS is included with your Proactive Care support agreement and is used as an automatic
service request submission for detected solution issues. Through the use of remote real-time hardware
event monitoring, HPE OneView RS can identify when a failure has happened or is about to occur. In
some cases, it proactively initiates a secure Internet event submission for a support experience and
automatically sends the replacement part to you. HPE OneView RS provides proactive care for each of
the solution hardware components, including:
•Hardware Lifecycle Host Management node
•Azure Stack Compute nodes
HPE OneView RS does not support PDUs or network switches.
Features and benefits
HPE OneView Remote Support supports HPE servers, providing you with the following features and
benefits:
•Preintegrated into the HPE ProLiant for Microsoft Azure Stack solution and easily configured to
monitor your environment.
•24x7 real-time hardware event monitoring and secure Internet event submission help you identify and
prevent potentially critical problems for your environment.
•Automatic service request submission saves time monitoring and reporting issues.
•Intelligent analysis of issues provides faster restoration of your monitored devices to operational
status.
•Support for Scope Based Access Control (SBAC) allows remote access control of subsets of
resources (Scope).
HPE ProLiant for Microsoft Azure Stack solution overview17
•HPE OneView RS can easily be configured to forward service events to a supported version of
Systems Insight Manager and offers integration into Insight Online.
•Collection of configuration information from your devices to help Hewlett Packard Enterprise resolve
problems more quickly and accurately.
NOTE: No business information is collected and the data is managed according to the Hewlett
Packard Enterprise Data Privacy policy.
HPE OneView RS checks every device to make sure it has a valid Hewlett Packard Enterprise warranty
or contract.
If a device does not have a Hewlett Packard Enterprise warranty or contract, the monitoring health
indicator in the HPE OneView RS console is red. When the indicator is red, no service events are
analyzed or sent to Hewlett Packard Enterprise.
Using HPE OneView RS with HPE ProLiant for Microsoft Azure Stack
HPE OneView RS is initially configured as part of the HPE ProLiant for Microsoft Azure Stack Deployment
Accelerator Service. If a monitored device requires replacement, the network configuration changes, or
the credentials of a monitored device are modified, the devices may need to be rediscovered to re-enable
monitoring. For more information about HPE OneView Remote Support, see the HPE OneView 4.0 UserGuide and the Settings: Remote support topics in HPE OneView 4.0 Help.
HPE OneView configuration and installation guides, user guides, other manuals, and white papers are
available at http://www.hpe.com/info/oneview/docs or in the Hewlett Packard Enterprise Information
Library.
18HPE ProLiant for Microsoft Azure Stack solution overview
Solution management
Monitoring and maintaining the HPE ProLiant for Microsoft Azure Stack solution hardware is an important
part of maintaining a healthy Microsoft Azure Stack deployment. The following sections outline the best
practices for hardware life cycle actions for the solution.
NOTE: See the Microsoft Azure Stack User Guide for Microsoft Azure Stack software life cycle
management details.
Recommended administrative activities
Adhere to the following guidelines to:
•simplify life cycle management tasks
•follow security best practices
•prevent data loss
•avoid solution administrator activities from causing a misconfiguration of the solution
Monitoring
•To prevent unintended interruptions in service, monitor the health of the system on a regular basis.
See Hardware monitoring on page 21 for details.
•For regular monitoring activities, use only accounts with minimal privileges, such as a read-only role
account when accessing HPE OneView or a Microsoft Windows user other than Administrator when
accessing the Hardware Lifecycle Host. See Monitoring health with HPE OneView on page 22 for
additional information.
Backup
Perform a backup prior to any maintenance such as updates. Transfer backup files to a location outside
of the solution. See Hardware Lifecycle Host backup and recovery process on page 31 for details.
Security
•Regularly rotate passwords. See Managing passwords for details.
•Regularly check the status of certificates. See Managing certificates for details.
•Regularly update encrypted data recovery keys: See Managing BitLocker recovery keys for details.
•Keep Microsoft Windows security features such as Device Guard and Windows Defender enabled and
up to date. See Managing Device Guard for details.
System administration guidelines
Administrators must take care to adhere to the following guidelines:
Solution management19
Avoid these actionsExplanation
Do not directly search for and download individual
firmware, drivers, or software updates for
components of the solution. This directive includes
Hardware Lifecycle Host Management node, Azure
Stack Compute nodes, switches, HPE OneView,
HPE iLO, iPDU or G2 Metered PDU.
Do not attempt to directly modify HPE OneView
server profiles or server profile templates unless
explicitly guided to do so.
Do not directly power-down the Azure Stack nodes. Before powering down, Azure Stack nodes must
Software, firmware, and drivers are pretested to be
compatible with all components in the HPE
ProLiant for Microsoft Azure Stack solution. When
updating the solution, use only the solution-specific
update bundles from Hewlett Packard Enterprise or
the Microsoft software update bundle from
Microsoft. These bundles contain the correct
software, firmware, and driver versions as specified
in the HPE ProLiant for Microsoft Azure Stack
Gen10 Software and Firmware Compatibility
Matrix.
Use read-only role accounts to avoid accidentally
changing server profiles. Use HPE OneView
integrations to accumulate health information from
multiple HPE ProLiant for Microsoft Azure Stack
deployments or to enable other automated
monitoring use cases. See https://
www.hpe.com/us/en/solutions/developers/
composable.html for more information on the
environment of HPE OneView Integrations.
first be put into maintenance mode and verified that
they are drained of active workloads (moved to
different nodes).
Do not modify system BIOS or boot order settings.BIOS settings have been tested and verified for
each HPE ProLiant for Microsoft Azure Stack
solution recipe release.
Do not modify the switch configuration.The switch configuration has been preconfigured in
the factory and refined as needed as part of the
initial setup and delivery. Necessary updates are
provided as part of solution update bundles for the
HPE ProLiant for Microsoft Azure Stack solution.
Accessing the HPE management portions of the solution
Solution component IP Addresses
User access to individual solution software applications is by static IP addresses. These IP addresses
have been provided to you at the conclusion of the deployment service. If these materials are lost,
c:\cdw\untagged\ip-iaddresses.csv
can be consulted for a listing of component IP addresses.
In some cases, an icon is also included on the Administrator desktop of the HLH as a direct link to the
application UI.
Solution component access
20Solution management
Accessing Hardware Lifecycle Host with Microsoft RDP
Microsoft Remote Desktop Protocol (RDP) can be used to access the HLH Management node. Using
RDP requires the remote desktop to have an RDP client installed. Necessary access information such as
the IP address, user name, and password, is included in materials provided during the deployment
service.
Accessing HPE OneView
NOTE: Due to firewall restrictions, the HPE OneView dashboard can only be accessed from the HLH
Management node.
Access to the HPE OneView dashboard can be made through:
•A bookmark to the HPE OneView dashboard on the desktop of the HLH (requires network connection)
•Browse to https://<OneView VM IP address> (requires network connection)
•Using the Hyper-V console
Use this method if the network connection is not available.
1. Open the Hyper-V management console, right-click the HPE OneView VM, and select Connect.
2. Log on using your HPE OneView VM credentials.
Accessing Switches
NOTE: You can install an SSH client of your choice on the Hardware Lifecycle Host that allows you to
administer the switch from the HLH Management node. Putty is also available on the HLH and can be
used for switch administration access. If you encounter difficulty in establishing connectivity, you may
need to use console connectivity. Contact Hewlett Packard Enterprise support or your Hewlett Packard
Enterprise consultant for further assistance.
For detailed information about accessing and managing HPE switches in HPE ProLiant for Microsoft
Azure Stack systems, refer to the HPE FlexFabric 5900 or 5950 switch documentation.
For information about accessing and managing Cisco switches in HPE ProLiant for Microsoft Azure Stack
systems, refer to the Cisco Nexus 3000 Series NX-OS Fundamentals Configuration Guide, Release
6.x for Gen9 solutions or Cisco Nexus 9000 Series NX-OS Fundamentals Configuration Guide,
Release 7.x for Gen10 solutions.
For information about accessing and managing Arista switches in HPE ProLiant for Microsoft Azure Stack
systems, refer to the EOS System Configuration Guide.
Hardware monitoring
The Microsoft Azure Stack Health Resource Provider (HRP) performs basic hardware health monitoring
for the servers:
•Heartbeat monitoring of each node
•Per disk error reporting of SSD and HDD failures
To supplement the HRP, Hewlett Packard Enterprise has included HPE OneView integrated into the
solution to provide a complete hardware monitoring solution. See Monitoring health with HPE OneView
for guidance on configuring and using HPE OneView to monitor the solution hardware.
Solution management21
Monitoring health with HPE OneView
User roles and accounts for Monitoring
User roles allow the administrator to define the role of a user account by restricting permissions and
privileges based on the user's job responsibilities. Refer to About User roles in the HPE OneView 4.0Help for full detailed descriptions of each role and its permissions or privileges.
To monitor the Azure Stack node resources with HPE OneView, Hewlett Packard Enterprise recommends
only using a read-only account, which decreases the chance of making unwanted changes. To create and
check user account privileges in HPE OneView used for monitoring, follow these steps.
1. Navigate to Users and Groups page from the HPE OneView drop-down menu.
2. Click the +Add User button to the left side of the page.
3. Type in the user data and select the Read Only radio button.
4. Click Add when complete.
5. To test, log out and log in with the newly created user. Then navigate to a server-hardware page, click
Action, and notice "No authorization" text.
Accessing the HPE OneView help sidebar
At the top right corner of each page, there is a question mark in the banner. To open the Help sidebar,
click the question mark. The help sidebar provides:
•hyperlinks to the help system
•open-source code used in the product
•partner programs
•initial configuration procedures
•license agreement
•written offer
•online user forum
Useful help sidebar links:
1. Help on this page: Opens context-sensitive help for the current screen in a new browser window or
tab. This context-sensitive help is useful to browse through a page with items on the current screen
without referring to the HPE OneView 4.0 User Guide.
2. Browser help: Opens the top of the help contents in a new browser window. The new window enables
you to navigate to the entire table of contents for the UI help.
Dashboard page
The Dashboard is the first page displayed every time a user logs in. The Dashboard provides a visual
overview of managed resources including server hardware, server profile, and power devices. These
devices can be customized by adding custom or predefined panels that interest you. The panels can also
be rearranged in the order of your prioritization. The Dashboard page provides alerts and warnings to
help get the infrastructure attention of the manager. The user can go directly to the resource page that
needs attention by clicking the name of resource.
1. The dashboard chart colors indicate the following.
22Solution management
ColorIndication
GreenHealthy status.
YellowAn event has occurred that might require your attention.
RedA critical condition requires your immediate attention.
BlueFor a status graph, the resource instances that match the data being measured.
A solid blue chart indicates 100%.
Light grayResource instances do not match the data being measured. This indicator is
used in combination with blue to total 100%.
Dark grayIndicates that resource instances are Disabled or Unknown and also indicates
any status other than OK, Warning, or Critical.
2. Recommended resources are included in Dashboard view:
a. Server profiles
b. Server profiles templates
c. Server hardware
d. Appliance alerts
e. Activity
f. Power delivery devices
g. All resources
NOTE: For full details on how to customize the Dashboard page and interpret data, refer to the help page
within HPE OneView. To add or remove items from the Dashboard, see Dashboard in HPE OneView 4.0
Help.
Server profile page
A server profile is the configuration for a server instance when it gets added to the HPE OneView
appliance as a managed server. The Azure Stack Compute and Management nodes will be a part of rack
mount server hardware type. Only certain server profile features are applicable with this hardware type.
Supported features for rack mount server profile:
•Basic server identification information: server type, serial, power.
•Firmware versions: Specify the Service Pack for ProLiant version to apply.
•Local storage settings: Configure the disk drives directly connected to the integrated Smart Array
Controller.
•Boot settings: Specify boot order.
•BIOS settings: Specify the BIOS settings to apply.
Monitoring a server profile resource:
1. Navigate to the server hardware page from the main menu.
2. To the left side, there will be a list of server profiles by name, select one to monitor.
Solution management23
Loading...
+ 52 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.