> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/plan-and-deploy/implementation-guide/pre-installation.md). # Pre-installation checklist Checklist of prerequisites, hardware BIOS settings, and network configurations to verify before beginning a VergeOS installation. ## Prerequisites * [ ] Bootable USB drive with VergeOS ISO using these instructions: [Bootable Media](/plan-and-deploy/implementation-guide/install-media.md) * [ ] Encryption Key USB installed and ready (if enabling at-rest encryption) * [ ] Nodes powered up with ISO booted to VergeOS Install screen ## Hardware * [ ] Hardware burn-in complete * [ ] All Drives setup for JBOD, **NO RAID** * [ ] BIOS set to proper boot settings (Legacy / Dual / UEFI) **UEFI required if all drives are NVMe** * [ ] BIOS hardware assisted virtualization enabled * [ ] BIOS hyperthreading enabled * [ ] BIOS all processor cores enabled * [ ] BIOS clocks set correctly * [ ] BIOS Secure Boot disabled * [ ] Redundant Power supplies setup and connected (recommended) * [ ] IPMI ports patched and configured * [ ] IPMI setup / configured / tested * [ ] Latest IPMI firmware (recommended) * [ ] Test IPMI remote console capability (in case of incorrect licensing) ## Network * [ ] All switches online and tested * [ ] All cables patched * [ ] All VLANs configured (core - required, external - optional) * [ ] Each Core switch should be on a dedicated VLAN (ex 101 for core 1, 102 for core 2) * [ ] All switch ports configured (core and external) * [ ] External Bond ports setup correctly if bonding external (do not bond Core) * [ ] 2 NICs per node minimum and separate switches * [ ] Correct Supported SFP modules (if applicable) * [ ] Correct IPs validated and available * [ ] Correct Gateway IP tested/pingable --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.verge.io/plan-and-deploy/implementation-guide/pre-installation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.