[[["易于理解","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-20。"],[],[],null,["# Use case: Troubleshoot hybrid connectivity\n==========================================\n\nIn the following use cases, you're a network administrator supporting a network\nthat includes Interconnect connections, VPN tunnels, or router appliance instances to\non-premises networks. You want to view bandwidth to on-premises networks and\ndiagnose bottlenecks and other network problems. You want to learn about the\nnetwork utilization of the VPN tunnels, VLAN attachments and Interconnect\nconnections, or router appliance instances.\n\nThe following use cases demonstrate how Network Topology can help you\nquickly monitor and identify any issues in your network.\n\nInterconnect topology details\n-----------------------------\n\nIn this topology, the node `australia-southeast1` is expanded. You can\nsee the associated Interconnect connections and the (not-yet expanded) node\ncollecting VPN tunnels. In addition, one Interconnect connection is\nexpanded, and you can see the associated VLAN attachments. The Interconnect\nconnection is the enclosing entity and it includes VLAN attachments. Because the\nInterconnect connection and VLAN attachments are regional resources, they appear\nwithin the region where they are located. The Interconnect connection has two\nendpoints, one in the Google Cloud network and the other in the on-premises\nnetwork.\n\nThe following topology shows the hierarchy of the network topology.\n[](/static/network-intelligence-center/docs/network-topology/images/use-cases/auditing-hybrid.png) Network Topology example hybrid topology with VLAN attachments (click to enlarge)\n\n### Interconnect bandwidth throughput\n\nIn this scenario, you can perform the following actions:\n\n1. Monitor the utilization of your VLAN attachments and Interconnect\n connections so that you can make better-informed decisions when planning\n for network growth.\n\n2. Select a VLAN attachment. Click the traffic metrics, such as ingress bytes\n count, and see the traffic bandwidth traversing the VLAN attachment to\n Google Cloud from the on-premises network.\n\n3. Hold the pointer over an entity, such as a VLAN attachment. Click the traffic metrics,\n such as egress bytes count, to view the bandwidth throughput to on-premises\n networks and diagnose bottlenecks and any other network problems.\n\n4. For any entity metrics, expand the time series charts to the required\n time selection to view any bandwidth bottlenecks.\n\nVPN gateway topology details\n----------------------------\n\nIn this topology, a node that has a VPN gateway and a VPN tunnel is expanded.\nHierarchically in the Network Topology topology interface, within each\nCloud VPN gateway, you can see one or more VPN tunnels. The\nCloud VPN gateway has two endpoints, one in Google Cloud network and\nthe other in the on-premises network.\n\nThe following topology shows the hierarchy of the network topology with VPN\ntunnels:\n[](/static/network-intelligence-center/docs/network-topology/images/use-cases/auditing-vpn-onprem.png) Network Topology example hybrid topology with VPN tunnels (click to enlarge)\n\n### VPN bandwidth throughput\n\nIn this topology, the node `us-central1` is expanded, and you can see the\nassociated peering connections, gateways, and VPN tunnels connected to\non-premises networks. An on-premises network can refer to any remote network\nthat is outside the Google Cloud domain.\n\nIn this scenario, you can perform the following actions:\n\n1. Monitor the network utilization of the VPN tunnel to make empowered decisions\n for planning your network growth.\n\n2. Select the VPN tunnel. Click the traffic metrics, such as ingress bytes\n count, and see the traffic bandwidth traversing the VPN tunnel to\n Google Cloud from the on-premises network.\n\n3. Hold the pointer over the VPN tunnel. Click the traffic metrics, such\n as egress bytes count, to view the bandwidth throughput to on-premises\n networks and diagnose bottlenecks and any other network problems.\n\n4. For any entity metrics, expand the time series charts to the required\n time selection to view any bandwidth bottlenecks.\n\nRouter appliance details\n------------------------\n\nIn a typical topology that includes a router appliance instance connected to an on-premises\nnetwork, you can see the router appliance instance. Because the\nrouter appliance instances are regional resources, they appear\nwithin the region where they are located. The router appliance instance has two\nendpoints, one in the Google Cloud network and the other in the on-premises\nnetwork.\n\n### Router appliance bandwidth throughput\n\nIn this scenario, you can perform the following actions:\n\n1. Monitor usage of your router appliance instance so that you can\n make better-informed decisions when planning for network growth.\n\n2. Select a router appliance instance. Click the traffic metrics, such as ingress bytes\n count or egress bytes count, and see the traffic bandwidth traversing the\n router appliance instance between Google Cloud and the on-premises network.\n Diagnose bottlenecks and any other network problems.\n\n3. For any entity metrics, expand the time series charts to the required\n time selection to view any bandwidth bottlenecks.\n\nWhat's next\n-----------\n\n- [Monitor your networking configuration with Network Topology](/network-intelligence-center/docs/network-topology/how-to/audit-troubleshoot-networking-issues)\n- [Use case: Audit network performance](/network-intelligence-center/docs/network-topology/concepts/auditing-network-performance)\n- [Troubleshoot Network Topology](/network-intelligence-center/docs/network-topology/support/troubleshooting)\n- [Cloud Interconnect quotas and limits](/network-connectivity/docs/interconnect/quotas)\n- [Cloud VPN quotas and limits](/network-connectivity/docs/vpn/quotas)"]]
