This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Connection to HPE Moonshot
Create and manage connections and resources describes the wizards that create a connection. The following information covers details specific to HPE Moonshot.
Note:
Before creating a connection to HPE Moonshot, you need to first finish setting up your HPE account. See HPE Moonshot virtualization environments.
Create a connection
You can create a connection to HPE Moonshot using:
- Studio
- PowerShell commands
Create a connection using Studio
- In the Add Connection and Resources page, select the HPE Moonshot as the connection type.
- Enter the connection address of your Moonshot iLO Chassis Manager. You can use an IP address, host name, or FQDN for the address.
- Enter your chassis administrative credentials and a friendly connection name.
Connection setup stops when either of the situations occurs:
- DaaS receives a public CA-signed certificate with errors: An error message appears. Follow the on-screen instructions to fix the issue. Otherwise, you can’t proceed with connection creation.
- DaaS receives a private CA-signed certificate. A warning page appears. Compare the received thumbprint with the server’s for the certificate validity. If it’s valid, select Trust certificate and click OK to proceed with connection creation. DaaS will then trust the certificate and store the thumbprint for future validation.
Create a connection using PowerShell commands
When you create a connection using PowerShell command, provide the following information:
- IP: HPE Server IP Address
- Username: HPE username
- Password: HPE password
For example:
New-Item -ConnectionType "Custom" -HypervisorAddress $IP -Metadata @{"Citrix_Orchestration_Hypervisor_Secret_Allow_Edit"="false"} -Path @("XDHyp:\Connections\$connectionName") -Persist -PluginId "HPMoonshotFactory" -Scope @() -SecurePassword $Password -UserName $UserName -sslthumbprint $SslThumbprint New-BrokerHypervisorConnection -HypHypervisorConnectionUid $HypervisorConnectionID
<!--NeedCopy-->
Note:
The
sslthumbprint
parameter is required for only Private CA-signed certificates.
Certificate and thumbprint validation
For creating a successful connection to HPE Moonshot, the certificate must not have errors and the thumbprint must have a correct value. Following are the use cases related to the certificate and thumbprint validation:
- Public CA-signed certificate has errors. The connection is not created successfully. See the error details and resolve the issue.
- Public CA-signed certificate without errors. The connection is created successfully, and the
SslThumbprints
value is Null. - Private CA-signed certificate without errors and a
sslthumbprint
value. The connection is created successfully with a correctSslThumbprints
value. - Private CA-signed Certificate with an incorrect thumbprint value. The connection is not created successfully.
- Private CA-signed Certificate without errors. The connection is created successfully. The
SSlThumbprints
is Null when creating the connection. TheSSlThumbprints
value is updated to a value by the site service.
Manage connections
This section details how you can manage connections:
- Fix certificate issues using Studio
- Update thumbprint value using PowerShell command
Fix certificate issues
DaaS blocks an HPE Moonshot connection when certificate issues arise, preventing you from delivering and managing workloads on associated HPE Moonshot nodes. You’ll see an error icon next to the connection in the Host connections list. See the following table for specific issues and solutions.
Issue | Solution |
---|---|
A certificate error occurs to the public CA-signed certificate | Click the connection and select the Troubleshoot tab. View the error details and resolve the issue. |
The received certificate is private CA-signed or expired. | Edit the host connection to update the certificate thumbprint. Details steps |
|
|
|
|
|
|
|
|
|
Update thumbprint value
After creating the connection, you can update the thumbprint value of a connection using the Set-Item
PowerShell command. For example, run the following commands:
-
Get the connection details of a connection. For example:
Get-Item -LiteralPath xdhyp:\connections\SinMoonshot-101 <!--NeedCopy-->
-
Update the thumbprint value. For example:
Set-Item -LiteralPath xdhyp:\connections\SinMoonshot-101 -Username Administrator -SslThumbprint xxxxxxxxxxx12AD048480631BB7AB10D69xxxxx <!--NeedCopy-->
-
Check the updated thumbprint value. For example:
Get-Item -LiteralPath xdhyp:\connections\SinMoonshot-101 <!--NeedCopy-->
Note:
The update fails if you provide an incorrect thumbprint value in the
Set-Item
command.
Where to go next
- If you’re in the initial deployment process, see Create machine catalogs.
- For HPE Moonshot specific information, see Create an HPE Moonshot machine catalog.
More information
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.