Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini berisi detail tentang cara memecahkan masalah jaringan umum.
Pemecahan Masalah Bootstrap Jaringan
Bagian ini menunjukkan beberapa error umum yang mungkin Anda alami saat menyelesaikan proses bootstrap jaringan.
Error pembuatan konfigurasi
Untuk menyelesaikan penginstalan jaringan, file konfigurasi jaringan diinstal di mesin bootstrapper. Jika Anda mengalami error pembuatan konfigurasi, periksa
file YAML yang ada di /root/cellcfg untuk konfigurasi tombol yang gagal.
Bootstrap terhenti di ping fase 1
Jika proses bootstrap jaringan terhenti pada ping fase 1, ikuti langkah-langkah berikut untuk menemukan masalahnya:
Dapatkan lokasi konfigurasi penggantian yang dihasilkan dari log bootstrap: /tmp/network-bootstrap/ID
Temukan pengalihan yang terhenti dengan melihat file konfigurasi switch dengan
alamat IP.
Login ke switch dan periksa log operasi.
Bootstrap terhenti di ping tahap 2
Jika proses bootstrap jaringan terhenti pada ping fase 2, ikuti langkah-langkah berikut untuk menemukan masalahnya:
Dapatkan lokasi konfigurasi penggantian yang dihasilkan dari log bootstrap: /tmp/network-bootstrap/ID
Temukan switch yang terhenti dengan melihat file konfigurasi switch dengan alamat IP pengelolaan.
Periksa konfigurasi switch pengelolaan untuk mengetahui potensi masalah akses di jaringan pengelolaan.
[[["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."],[[["\u003cp\u003eThis page details how to troubleshoot common network bootstrap errors.\u003c/p\u003e\n"],["\u003cp\u003eA configuration generation error can be troubleshot by checking the YAML files at \u003ccode\u003e/root/cellcfg\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eIf the bootstrap stalls at phase 1 ping, check the switch configuration file in \u003ccode\u003e/tmp/network-bootstrap/<ID>\u003c/code\u003e and the switch's operation log.\u003c/p\u003e\n"],["\u003cp\u003eIf the bootstrap stalls at phase 2 ping, review the management switch configuration file in \u003ccode\u003e/tmp/network-bootstrap/<ID>\u003c/code\u003e for management network access issues.\u003c/p\u003e\n"]]],[],null,["# Networking troubleshooting\n\nThe page contains details on how to troubleshoot common networking issues.\n\nNetwork Bootstrap Troubleshooting\n---------------------------------\n\nThis section shows some of the common errors you might face when completing the\nnetwork bootstrap process.\n\n### Configuration generation error\n\nTo complete the network installation, network configuration files are installed\non the bootstrapper machine. If you face a configuration generation error, check\nthe YAML files located at `/root/cellcfg` for the failed switch configuration.\n\n### Bootstrap stalled at phase 1 ping\n\nIf the network bootstrap process gets stalled at phase 1 ping, follow these\nsteps to find the issue:\n\n1. Get the generated switch configuration location from the bootstrap log: `/tmp/network-bootstrap/`\u003cvar translate=\"no\"\u003eID\u003c/var\u003e\n2. Find the stalled switch by looking at the switch configuration file with the IP address.\n3. Sign in to the switch and check the operation log.\n\n### Bootstrap stalled at phase 2 ping\n\nIf the network bootstrap process gets stalled at phase 2 ping, follow these\nsteps to find the issue:\n\n1. Get the generated switch configuration location from the bootstrap log: `/tmp/network-bootstrap/`\u003cvar translate=\"no\"\u003eID\u003c/var\u003e\n2. Find the stalled switch by looking at the switch configuration file with the management IP address.\n3. Check the management switch configuration for any potential access issues in the management network."]]
