Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Anda dapat menjalankan Uji Konektivitas langsung dari Flow Analyzer untuk memvalidasi konektivitas antara dua endpoint. Anda juga dapat menjalankan pengujian ini
untuk memahami jalur antara dua resource. Saat Anda menjalankan Uji Konektivitas,
perhatikan bahwa pengujian menggunakan konfigurasi yang ada. Jadi, jika Anda menjalankan pengujian dua minggu setelah peristiwa log sebenarnya, Uji Konektivitas tidak menggunakan konfigurasi historis.
Saat menjalankan pengujian, atribut berikut digunakan dalam definisi pengujian:
IP Sumber
Project Sumber
Jaringan Sumber (untuk alamat IP internal)
IP tujuan (untuk alamat IP internal)
Project Tujuan (untuk alamat IP internal)
Jaringan Tujuan (untuk alamat IP internal)
Port Tujuan
Protokol
Jika parameter ini tidak tersedia dalam informasi traffic, Uji Konektivitas akan gagal. Misalnya, jika Anda mengelompokkan traffic di
Flow Analyzer hanya menurut VPC Sumber dan VPC
Tujuan, informasi ini
tidak cukup untuk menjalankan Uji Konektivitas.
Uji Konektivitas dapat gagal karena alasan berikut:
Jika resource yang ditampilkan di Log Aliran VPC tidak ada lagi.
Jika pengujian dijalankan dari server ke klien dan traffic ke arah tersebut (selain traffic kembali) tidak dapat dimulai.
Sebelum memulai
In the Google Cloud console, on the project selector page,
select or create a Google Cloud project.
Pastikan peran pengguna memiliki izin berikut:
compute.networks.list
Karena pengujian dijalankan melalui API internal, hasilnya bersifat sementara dan
pengguna tidak ditagih untuk menjalankan pengujian. Hasil tidak disimpan
dan tidak dapat diakses setelah menutup panel hasil.
Menjalankan Uji Konektivitas
Untuk menjalankan Uji Konektivitas dari Flow Analyzer, lakukan hal berikut:
Konsol
Di konsol Google Cloud , buka halaman Flow Analyzer.
Pilih bucket log. Secara default, log alur disimpan di bucket log _Default dan dapat diakses di tampilan log _Default.
Pilih rentang waktu yang ingin Anda jalankan kuerinya.
Di menu Traffic, pilih salah satu opsi berikut:
Sumber - Tujuan: Menggabungkan traffic dari sumber ke tujuan.
Klien - Server: Gabungkan traffic di kedua arah dengan
mempertimbangkan resource dengan nomor port yang lebih rendah dan definisi
layanan sebagai server.
Opsional: Di daftar Filter, pilih satu atau beberapa filter.
Atur hasil kueri menggunakan daftar Atur alur menurut.
Kolom berikut wajib diisi:
Alamat IP Sumber
ID project jaringan VPC atau jaringan VPC sumber
Alamat IP tujuan
Klik Run new query.
Di tabel Semua alur data, klik Jalankan untuk alur apa pun.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[],[],null,["# Run Connectivity Tests\n\nYou can run Connectivity Tests directly from Flow Analyzer to\nvalidate the connectivity between two endpoints. You can also run these tests\nto understand the path between two resources. When you run Connectivity Tests,\nnote that the tests uses the existing configuration. So, if you run the tests\ntwo weeks after the actual log event, Connectivity Tests does not use\nthe historical configuration.\n\nWhile running a test, the following attributes are used in the test\ndefinition:\n\n- Source IP\n- Source Project\n- Source Network (for internal IP addresses)\n- Destination IP (for internal IP addresses)\n- Destination Project (for internal IP addresses)\n- Destination Network (for internal IP addresses)\n- Destination Port\n- Protocol\n\nIf these parameters are not available in the traffic information, the\nConnectivity Test fails. For example, if you group traffic in\nFlow Analyzer only by Source VPC and Destination\nVPC, this information\nis not sufficient to run Connectivity Tests.\n| **Note:** The existing resource configuration is used to perform the analysis.\n\nConnectivity Tests can fail due to the following reasons:\n\n- If the resources shown in VPC Flow Logs no longer exist.\n- If the test is executed from server to client and traffic in that direction (other than return traffic) cannot be initiated.\n\nBefore you begin\n----------------\n\n1. In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n2. [Enable the Network Management API](/network-intelligence-center/docs/connectivity-tests/reference/enable-api).\n\n3. Make sure the user role has the following permissions:\n `compute.networks.list`\n\n Because the tests are run through internal API, the results are ephemeral and\n users are not billed for running the tests. The results are not stored\n and are not accessible after closing the results panel.\n\nRun Connectivity Tests\n----------------------\n\nTo run Connectivity Tests from Flow Analyzer, do the following: \n\n### Console\n\n1. In the Google Cloud console, go to the **Flow Analyzer** page.\n\n [Go to Flow Analyzer](https://console.cloud.google.com/net-intelligence/flow-analyzer)\n2. Select a log bucket. By default, flow logs are stored in\n the **_Default** log bucket and accessible in the **_Default** log view.\n\n3. Select the time range for which you want to run the query.\n\n4. In the **Traffic** menu, select one of the following options:\n\n - **Source - Destination:** Aggregate the traffic from the source to the destination.\n - **Client - Server:** Aggregate the traffic in both directions by considering the resources with lower port numbers and service definitions as servers.\n5. Optional: In the **Filter** lists, select one or more filters.\n\n6. Organize the query results by using the **Organize flows by** lists.\n The following fields are required:\n\n - Source IP address\n - Source VPC network or VPC network project ID\n - Destination IP address\n7. Click **Run new query**.\n\n8. In the **All data flows** table, click **Run** for any flow.\n\nWhat's next\n-----------\n\n- [Analyze your traffic flows](/network-intelligence-center/docs/flow-analyzer/analyze-traffic-flows)\n- [Monitor your traffic flows](/network-intelligence-center/docs/flow-analyzer/monitor-traffic-flows)\n- [Troubleshoot data issues in Flow Analyzer](/network-intelligence-center/docs/flow-analyzer/manage-flow-analyzer)"]]
