[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eThis document guides you through the setup and configuration of a Google Distributed Cloud (GDC) air-gapped appliance at a customer site.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves decrypting the appliance drives using YubiKeys, which are shipped separately and must remain in the server post-installation until the system is returned.\u003c/p\u003e\n"],["\u003cp\u003eYou'll configure the appliance using the \u003ccode\u003egdcloud appliance configure\u003c/code\u003e command, answering questions about DNS, BGP, data plane networks, uplinks, and optional external NTP and HSM information.\u003c/p\u003e\n"],["\u003cp\u003eYou have the option to connect the appliance to your existing identity provider (IdP) or use the automatically installed Keycloak IdP, and if you choose to use the Keycloak IdP it is crucial to save the credentials provided during the installation process.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ecellcfg\u003c/code\u003e directory, generated during configuration, must be backed up, as it is necessary for updating and patching the appliance.\u003c/p\u003e\n"]]],[],null,["# Configure the appliance and install software\n\nThis page describes how to set up and configure Google Distributed Cloud (GDC) air-gapped appliance\nat the customer site.\n\nOn first boot, the drives are unlocked without human intervention.\n| **Important:** To access the URLs on this page, you must connect to the internet. The URLs are provided for use when you have such access.\n\nDecrypt the drive and boot the machine\n--------------------------------------\n\nEach GDC air-gapped appliance is shipped with Yubikeys inserted into each blade. Ensure that the yubikeys are correctly inserted with the gold side facing up. Once the key is inserted it is paired with that server and cannot be moved to a different server.\nThese Yubikeys must be in their original slots in the corresponding server blade\nin order for the GDC air-gapped appliance to boot.\n| **Important:** The Yubikeys must be inserted in each blade prior to executing the bootstrapping process. Incorrectly following this step will result in a failed bootstrap.\n\nConfigure the appliance\n-----------------------\n\nVerify all fields of the input configuration file are accurate. Once the file is copied to the server blade in the following steps, the final configuration begins automatically and cannot easily be stopped.\n\n1. Transfer the input configuration file to the path\n `/var/lib/assets/ciq_configure_input.yaml` on the server blade assigned the\n `198.18.0.6` IP address.\n\n scp configuration-input.yaml applianceusr@198.18.0.6:/var/lib/assets/ciq_configure_input.yaml\n\n2. The configuration starts automatically and saves output in the\n `/var/log/gdch-install.txt` file.\n\n3. Configuration is expected to take 4-5 hours. Monitor progress with one of the following:\n\n - Monitor the `/var/log/gdch-install.txt` file with the following:\n\n ssh applianceusr@198.18.0.6 'tail -f /var/log/gdch-install.txt'\n\n The install is complete when the cleanup phase has completed. The log shows a line like the following: \n\n \u003c\u003c\u003c Completed phase: cleanup\n\n - Alternatively, you can look for the status of the installation service, with the following:\n\n ssh applianceusr@198.18.0.6 'systemctl status gdch-app-install'\n\n The output indicates the status of the installation. In particular, the `Active` field indicates if the install is ongoing, failed, or inactive. When the line indicates that the install process is inactive and has a status of `0/SUCCESS`, the installation is complete.\n\nBack up the credentials\n-----------------------\n\nRetrieve the device emergency credentials and store them in a secure location\n\n1. Create a backup archive of the access credentials by running the following, enter the `applianceusr` password when prompted:\n\n ssh applianceusr@198.18.0.6 'sudo -S /var/lib/release/gdcloud appliance install --phase=postinstall'\n\n2. Copy the credential backup to the bootstrapper by running the following, enter the `applianceusr` password when prompted:\n\n ssh applianceusr@198.18.0.6 'sudo -S setfacl -m u:applianceusr:rwx /var/lib/assets/credentials.tar.gz'\n scp applianceusr@198.18.0.6:/var/lib/assets/credentials.tar.gz .\n\n3. Verify the contents of this archive include, the cellcfg backup, identity provider credentials, switch credentials, and SSH keys for the server blade assigned to the `198.18.0.6` IP address.\n\n4. Store the archive on a separate, secure medium (such as a USB drive) for\n emergency access.\n\nDelete appliance user and stop appliance install services\n---------------------------------------------------------\n\nAfter the backup of emergency credentials is completed, run the following\ncommand on the server blade assigned the `198.18.0.6` IP address to delete the\ndefault appliance user account and stop install services. In order to use the server blade assigned the `198.18.0.6` IP address in the future, you can use [emergency credentials](/distributed-cloud/hosted/docs/latest/appliance/admin/setup#back_up_emergency_credentials).\n\n1. Execute the following to remove the default user access and secure the device\n\n ssh applianceusr@198.18.0.6 'sudo -S /usr/local/bin/cleanup_appliance_user.sh'\n\nManage YubiKeys\n---------------\n\nAfter the installation completes, the YubiKeys must stay in the server until you\n[return the system](/distributed-cloud/hosted/docs/latest/appliance/admin/return-device)."]]