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!
Enabling NBD connections on Citrix Hypervisor
Citrix Hypervisor acts as a network block device (NBD) server and makes VDI snapshots available over NBD connections. However, to connect to Citrix Hypervisor over an NBD connection, you must enable NBD connections for one or more networks.
Important
We recommend that you use a dedicated network for your NBD traffic.
By default, NBD connections are not enabled on any networks.
Note:
Networks associated with a Citrix Hypervisor pool that have NBD connections enabled must either all have the
nbdpurpose or all have theinsecure_nbdpurpose. You cannot have a mix of normal NBD networks (FORCEDTLS) and insecure NBD networks (NOTLS). To switch the purpose of all networks, you must first disable normal NBD connections on all networks before enabling either normal or insecure NBD connections on any networks.
Enabling an NBD connection for a network (FORCEDTLS mode)
We recommend that you use TLS in your NBD connections.
When NBD connections with TLS are enabled, any NBD clients that attempt to connect to Citrix Hypervisor must use TLSv1.2.
The NBD server runs in FORCEDTLS mode with the “fixed newstyle” NBD handshake.
For more information, see the NBD protocol documentation.
To enable NBD connections with TLS, use the purpose parameter of the network.
Set this parameter to include the value nbd.
Ensure that you wait for the setting to propagate before attempting to use this network for NBD connections.
The time it takes for the setting to propagate depends on your network and is at least 10 seconds.
We recommend that you use a retry loop when making the NBD connection.
Examples
You can use any of our supported language bindings to enable NBD connections. The following examples show how to do it in Python and at the xe command line.
Python:
session.xenapi.network.add_purpose(<network_ref>, "nbd")
<!--NeedCopy-->
xe command line:
xe network-param-add param-name=purpose param-key=nbd uuid=<network-uuid>
<!--NeedCopy-->
Enabling an insecure NBD connection for a network (NOTLS mode)
We recommend that you do not enable insecure NBD connections.
Instead use FORCEDTLS NBD connections.
However, the ability to connect to the Citrix Hypervisor over an insecure NBD connection is provided for development and testing with the NBD server operating in NOTLS mode as described in the NBD protocol.
To enable insecure NBD connections, use the purpose parameter of the network.
Set this parameter to include the value insecure_nbd.
Ensure that you wait for the setting to propagate before attempting to use this network for NBD connections.
The time it takes for the setting to propagate depends on your network and is at least 10 seconds.
We recommend that you use a retry loop when making the NBD connection.
Examples
You can use any of our supported language bindings to enable insecure NBD connections. The following examples show how to do it in Python and at the xe command line.
Python:
session.xenapi.network.add_purpose(<network_ref>, "insecure_nbd")
<!--NeedCopy-->
xe command line:
xe network-param-add param-name=purpose param-key=insecure_nbd uuid=<network-uuid>
<!--NeedCopy-->
Disabling NBD connections for a network
To disable NBD connections for a network, remove the NBD values from the purpose parameter of the network.
Examples
You can use any of our supported language bindings to disable NBD connections. The following examples show how to do it in Python and at the xe command line.
Python:
session.xenapi.network.remove_purpose(<network_ref>, "nbd")
<!--NeedCopy-->
Or, for insecure NBD connections:
session.xenapi.network.remove_purpose(<network_ref>, "insecure_nbd")
<!--NeedCopy-->
xe command line:
xe network-param-remove param-name=purpose param-key=nbd uuid=<network-uuid>
<!--NeedCopy-->
Or, for insecure NBD connections:
xe network-param-remove param-name=purpose param-key=insecure_nbd uuid=<network-uuid>
<!--NeedCopy-->
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.