[[["容易理解","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 page details the configuration of network settings for backup/recovery appliances, including self-service network setup, DNS and NTP modification, network troubleshooting, and host resolution.\u003c/p\u003e\n"],["\u003cp\u003eYou can configure DNS and NTP settings for the appliance, ensuring valid and reachable IP addresses without firewall interference, with fields left empty reverting to DHCP values.\u003c/p\u003e\n"],["\u003cp\u003eThe troubleshooting section provides tools like Ping, IP route get, Traceroute, TCP Connection Test, and Test DNS to diagnose network connectivity issues.\u003c/p\u003e\n"],["\u003cp\u003eHost resolution allows overriding DNS resolution with static entries, enabling connections to hosts with multiple IPs or names not available in DNS.\u003c/p\u003e\n"],["\u003cp\u003eYou can validate connectivity between the backup/recovery appliance and the Backup and DR agent by running a TCP connection test on port 5106, which can reveal if the agent is running, firewalls are blocking traffic, or if there are network issues.\u003c/p\u003e\n"]]],[],null,["# Configure backup/recovery appliance network settings\n\nThis page explains how to configure network settings for any\nbackup/recovery appliance managed by your management console.\n\nFrom this page, you can:\n\n- [Configure Self Service Network for backup/recovery appliances](#self-service-network)\n\n- Modify [DNS and NTP](#dns-ntp)\n\n- Perform [Network Troubleshooting](#troubleshoot)\n\n- Create and modify [Host Resolution](#host-resolution)\n\nConfigure self service network for backup/recovery appliances\n-------------------------------------------------------------\n\n1. Click the **Manage** tab and select the **Appliances**\n option from the drop-down list.\n\n2. Right-click an appliance and select **Configure Appliance Networking** to\n open the System Management page.\n\n3. On the **DNS and NTP** tab, enter or modify the DNS or NTP settings or both.\n See [DNS and NTP](#dns-ntp). Any field you leave empty will revert\n to DHCP provided values.\n\n4. Click the **IP \\& Interfaces** tab to view the a list of\n configured IP addresses. You cannot edit any information,\n it is view only.\n\n5. Click the **Troubleshooting** tab and troubleshoot problematic\n network connections. See [Network Troubleshooting](#troubleshoot)\n for additional information.\n\n6. Click the **Host Resolution tab** to override DNS resolution\n for specific hosts. See [Host Resolution](#host-resolution)\n for additional information.\n\nDNS and NTP\n-----------\n\nChanges made on this page can have a significant impact on the operation of\nyour backup/recovery appliance. Ensure IP addresses for DNS and NTP are valid\nand reachable, without firewalls blocking the traffic. This may be tested using\nthe TCP connection test on the **Troubleshooting** tab.\n\n- **DNS Domain**: Enter the domain of the hosts connected to this appliance.\n\n If you have additional hosts on other domains, you can set up a\n **DNS Suffix Search** to ensure the appliance can find them\n by their short names.\n | **Note:** If you set any entries in DNS Suffix Search, then the DNS Domain will NOT be searched. To search both the manual entries AND the DNS domain, include the DNS domain in the DNS Suffix Search.\n- **Primary DNS**: Enter the IP address of your primary DNS server.\n\n- **Secondary DNS**: Enter the IP address of your\n secondary DNS server (optional).\n\n- **NTP Server**: Enter the IP address or hostname of your NTP server.\n We recommend leaving this blank or set to metadata.google.internal\n which is provided by Google Cloud and is always reachable.\n\nTroubleshooting\n---------------\n\nUse this page to troubleshoot problematic network connections.\nUnder **Utility** , select the troubleshooting tool to use, enter\nthe necessary parameters, and then click **Run Test**. The results\nappear in the Test Results box.\n\n**Ping**: Runs a ping to determine reachability of a target host,\nreturning the output as a plain text stream. This command sends 4 ICMP echo\npackets.\nEnter:\n\n- **Source IP**: The default value of Auto Select is generally the best\n choice. If your appliance has multiple IP addresses, you may select\n which will be used for the outbound ICMP traffic by selecting it here.\n\n- **Destination IP**: A valid IPv4 address.\n\n Example Ping result: \n\n PING 1.2.3.4 (1.2.3.4) 56(84) bytes of data.\n --- 1.2.3.4 ping statistics ---\n 4 packets transmitted, 0 received, 100% packet loss, time 3001ms\n\n**IP route get**: Queries the routing tables for the selected\nDestination IP address without sending any packets.\nEnter:\n\n- **Source IP**: The default value of Auto Select is generally the best\n choice. If your appliance has multiple IP addresses, you may select\n which will be used for the routing request by selecting it here.\n\n- **Destination IP**: The IP address of a target host.\n\n Example IP route get result: \n\n test or routeget 1.2.3.4\n 1.2.3.4 using 172.17.1.2 dev eth0 src 172.17.134.80\n cache mtu 1500 advmss 1460 hoplimit 64\n\n**Traceroute**: Runs a traceroute to the given IP address by sending\na series of UDP probes, returning the output as a plain text stream.\nThis can take up to 2 minutes to run. Use Traceroute to identify\nintervening networks on the path. Traceroute cannot accept a source\nIP parameter, so it is not useful for testing the behavior of\nreply packets. Only outgoing connections can be diagnosed with this tool.\n\n- **Destination IP**: The IP address of a target host.\n\n- **UDP Port**: See Specifies the base port to use for the test.\n Leave blank to use the default 33434. Note: the number of ports used\n will be equal to the number of hops.\n\n Example Traceroute result: \n\n test or traceroute 8.8.8.8\n 1: dev134-86.dev.acme.com (172.17.134.86) 0.092ms\n pmtu 1500\n 1: devgw-waln5k02.dev.acme.com (172.17.0.3) 4.287ms\n 1: devgw-waln5k02.dev.acme.com (172.17.0.3) 1.287ms\n 2: e-1-20-walpalo.core.acme.com (192.168.255.21) 2.805ms\n 3: ge-0-0-1-walasr.edge.acme.com (192.43.242.209) 2.769ms\n 4: 205.158.44.81.ptr.us.xo.net (205.158.44.81) 9.247ms asymm 14\n 5: vb1020.rar3.nyc-ny.us.xo.net (216.156.0.25) 10.080ms asymm 12\n 6: 207.88.12.104.ptr.us.xo.net (207.88.12.104) 8.537ms asymm 12\n 7: 207.88.13.35.ptr.us.xo.net (207.88.13.35) 8.175ms asymm 11\n 8: no reply\n 9: no reply\n .\n .\n .\n 31: no reply\n Too many hops: pmtu 1500\n Resume: pmtu 1500\n\n**TCP Connection Test**: Attempts a TCP connection to the target IP and port.\nIf successful, the connection is closed immediately without\ntransferring any data. If not successful it returns a failure message.\nMost commonly used to verify if firewalls are blocking traffic, or if\na destination host is listening on a specific TCP port.\n\n- **Source IP**: The default value of Auto Select is generally the best\n choice. If your appliance has multiple IP addresses, you can select\n which will be used for the TCP connection test by selecting it here.\n\n- **Destination IP**: The IP address of a target host.\n\n- **TCP Port**: Specify the TCP port on the destination to use when\n attempting to make a connection.\n\n Example TCP Connection Test result: \n\n test/TCP ConnectionTest\n Connection to 10.138.200.3:443 succeeded!\n\nTo validate the connectivity from appliance to Backup and DR agent, see [Validate backup/recovery appliance to Backup and DR agent connectivity](#validate).\n\n**Test DNS**: Attempts to use the configured DNS server to resolve a name or IP\naddress.\n\n- In **Resolve**, select Name to resolve a name to an IP address, or select IP to resolve IP address to name using PTR records (reverse DNS lookup).\n- In **Name to Resolve**, enter the name you want to attempt to resolve using the configured DNS server.\n- In **IP to Resolve**, enter the IP address you want to attempt to resolve to a name using PTR records (reverse DNS lookup).\n\nHost resolution\n---------------\n\nSometimes, it is necessary to manually create static entries for name\nresolution. This may be required for hosts with multiple IP addresses,\nwhere you want to resolve to an IP that is different from what is\nregistered in DNS. You can also resolve names that are not\navailable in DNS at all with the static entries creation.\n\nFrom this tab you can Add, Modify, or Delete IP/Name pairs.\nWhen added, these are resolved as if they were stored in /etc/hosts on a\nstandard linux platform. One or more aliases may also be specified for each\nrow in the table (multiple aliases are separated by a space).\n| **Note:** It is not allowed to specify multiple rows in the table with the same name, but different IP addresses. If it is necessary to resolve a name to multiple IP addresses, using a DNS server is the only way to achieve this.\n\nValidate backup/recovery appliance to Backup and DR agent connectivity\n----------------------------------------------------------------------\n\nTo validate that the backup/recovery appliance is connect to the Backup and DR agent\nrunning on a host, you can run the connectivity test. You need the IP\naddress of the target host to perform the connectivity test.\n\n1. From the management console, go to **Manage** \\\u003e **Appliances**.\n2. Right select the relevant appliance and select **Configure Appliance Networking** . The **System Management** page opens in a new tab.\n3. Go to the **Troubleshooting** tab.\n4. Select **TCP Connection Test** from the **Utility** drop-down.\n5. Leave the **Source IP** to **Auto Select**.\n6. In the **Destination IP** box, enter the IP address of the target host.\n7. In the **TCP Port** box, enter the value 5106.\n8. Select **Run Test**.\n\n The **Test Results** display three possible results (your IP will be different) as follows:\n - **Successful result** : `Connection to 10.0.0.5:5106 succeeded!`\n\n This means that the agent is running on the host and that the firewall is\n not blocking connection. If the Certificate Status for the host in\n **Manage** \\\u003e **Hosts** is shown as invalid, then you must create a\n new secret key using the Backup and DR agent on the host and then adding that\n key by editing the host entry in **Manage** \\\u003e **Hosts**.\n - **Unsuccessful result (time out)** : `Connection to 10.0.0.5:5106 failed: Connection timed out.`\n\n The reason for connection timed out can be any of the following:\n - The host is not powered on.\n - The Backup and DR agent is not installed.\n - The Backup and DR agent is installed but not running.\n - The firewall for the VPC is not allowing ingress traffic to port 5106 on that host.\n - There is no network connectivity between the appliance and host.\n - **Unsuccessful result (refused)** : `Connection to 10.0.0.5:5106 refused`\n\n The reason for connection refused can be any of the following:\n - The Backup and DR agent is not installed.\n - The Backup and DR agent is installed but not running.\n - You are connecting to a wrong IP address."]]
