> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-and-integrated-pos/buypass-network-manager-and-reports-reference/network-manager/diagnostics.md). # Diagnostics Diagnostics functions available from the Network Menu include the following: * Check Host Status * POP Initialization ### Diagnostic Check Host Status Accessing Diagnostic Check Host Status function: **CSR Functions > Network Manager > Diagnostic Check Host Status** The Check Host Status function sends a request to the EPS to determine if the network is available. Select **\[Diagnostic Check Host Status]** from the POS Network Menu. If the connection to the Payment Processor is established, then a Payment Processor Online message is displayed. If the connection to the Payment Processor is not available, then a Payment Processor Offline error message is displayed. The POS display returns to the Network menu. ### Diagnostic POP Init Accessing Diagnostic POP Init function: **CSR Functions > Network Manager > Diagnostic POP Init** The POP Initialization function in the Diagnostics menu re-initializes the connection from the EPS to the POP PIN pad. Select **\[Diagnostic POP Init]** from the POS Network Menu. If the connection between the EPS and the POP PIN pad is available, then an Approved message is displayed. If the connection between the EPS and the POP PIN pad is not available, then a Failure message is displayed. The POS display returns to the Network menu. --- # 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.verifone.com/petroleum-docs/petro-and-c-store/commander-and-integrated-pos/buypass-network-manager-and-reports-reference/network-manager/diagnostics.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.