> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/s2gw-installation-manual/quick_installation/s2gw_setup/s2-pc-node-preparation.md). # S2 PC node preparation The S2 PC node must be configured to use a correct radio network group ID. If the S2 radio group is migrated from B2 then the existing S2 PC node shall be used without any modifications. In case there is yet no S2 PC node for some reason, the S2 PC node must have the correct radio network set as described in [S2 Init Node](/s2-radio-system-manual/tools/s2-init-node.md). Please observe that all the nodes belonging to a given radio network must have the same group ID. --- # 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://help.boomerang3.com/s2gw-installation-manual/quick_installation/s2gw_setup/s2-pc-node-preparation.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.