[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-12。"],[],[],null,["# Test connections\n\nBefore you can use your Dedicated Interconnect connections, Google must\nverify that your connections to Google's edge network are working. To do this,\nGoogle sends you an IP address configuration that you must apply to your\non-premises router.\n\nThis configuration differs depending on whether you order one circuit\n(one 10-Gbps circuit or one 100-Gbps circuit) or more than one circuit\n(multiple 10-Gbps circuits or multiple 100-Gbps circuits).\n\nThe following sections describe two different testing procedures. The first is\nfor a single-circuit connection and the second is for a multi-circuit\nconnection.\n\nFor definitions of terms used on this page, see\n[Cloud Interconnect key terms](/network-connectivity/docs/interconnect/concepts/terminology).\n\nTo help you solve common issues that you might encounter when using\nDedicated Interconnect, see\n[Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting).\n\nTest a single-circuit connection (one 10-Gbps or 100-Gbps circuit)\n------------------------------------------------------------------\n\n1. Google polls its edge device every 24 hours, checking for light on the port to your on-premises router. Receiving light indicates that your connection has been installed. After detecting this light, Google sends you an email containing an IP address that Google uses to ping your on-premises router to test the circuit.\n2. Configure the interface of your on-premises router with the correct\n link-local IP address and configure LACP on that interface. Even though\n there is only one circuit in your Dedicated Interconnect connection,\n you must still use LACP.\n\n The following example shows an IP address configuration similar to the one\n that Google sends you for the test. Replace these values with the values\n that Google sends you for your network.\n\n3. Apply the test IP address that Google sends you to the interface of your\n on-premises router that connects to Google. For testing, you must\n configure this interface in *access mode* with no VLAN tagging. For a\n sample configuration, see [Configure on-premises routers\n for testing](/network-connectivity/docs/interconnect/how-to/dedicated/configuring-onprem-routers#testing).\n\n4. Google tests your connection by pinging the link-local IP address with LACP\n enabled. Google tests once, 30 minutes after detecting light, and then every\n 1 hour thereafter.\n\n - After a successful test, Google sends you an email notifying you that your connection is ready to use.\n - If a test fails, Google automatically retests the connection once an hour for 30 days.\n\nTo fix issues, see the guidance for single-link bundles in the\n[Troubleshooting guide](/network-connectivity/docs/interconnect/support/troubleshooting#cant-ping-during-connection-provisioning).\n\nTest a multi-circuit connection (multiple 10-Gbps or 100-Gbps circuits)\n-----------------------------------------------------------------------\n\nWhen you order a Dedicated Interconnect connection that has multiple circuits, Google\nperforms ping tests on the final bundled connection with LACP enabled.\n\n### Ping test\n\n1. Google polls its edge device every 24 hours, checking for light on the port\n to your on-premises router. Receiving light indicates that your connections\n have been installed. After detecting this light, Google sends you\n an email with instructions for the ping test.\n\n2. On your on-premises router, configure all the circuits into a bundle with\n LACP enabled and configure the IP address on the bundled interface.\n\n The following example shows an IP address configuration similar to the one that\n Google sends you for the test. Replace these values with the values that\n Google sends you for your network.\n\n3. Apply the test IP address that Google sends you to the bundled interface of\n your on-premises router that connects to Google. For testing, you must\n configure this interface in *access mode* with no VLAN tagging. For a\n sample configuration, see [Configure on-premises routers\n for testing](/network-connectivity/docs/interconnect/how-to/dedicated/configuring-onprem-routers#testing).\n\n4. Google tests each connection once every 1 hour. After a successful test,\n Google notifies you that your connection is ready to use.\n\nTo fix issues, see the guidance for multiple-link bundles in the\n[Troubleshooting guide](/network-connectivity/docs/interconnect/support/troubleshooting#cant-ping-during-connection-provisioning).\n\nUse your Dedicated Interconnect connection\n------------------------------------------\n\nAfter all tests have passed, your Dedicated Interconnect connection is ready to use, and\nGoogle starts billing for it. To view the status of your connection, see\n[View connection details](/network-connectivity/docs/interconnect/how-to/dedicated/viewing-interconnects).\n\nAt this stage, remove the test IP addresses from the interface or interfaces on\nyour on-premises router. To reconfigure your router for production, see\n[Configure on-premises routers\nfor production](/network-connectivity/docs/interconnect/how-to/dedicated/configuring-onprem-routers#production).\n\nYour connection can now carry traffic, but it isn't associated with any Google\nVirtual Private Cloud (VPC) networks.\n| **Note:** When you configure VLAN attachments on your on-premises router, the subnet size is different than when you configure a Dedicated Interconnect connection for a test. Make sure that you specify the correct subnet size, depending on what you're configuring. Google provides these values when you order a connection or create a VLAN attachment."]]