> ## Documentation Index
> Fetch the complete documentation index at: https://docs-xcor.paloaltonetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot Palo Alto Networks Telemetry Pipeline installations on Linux

> Steps to troubleshoot Palo Alto Networks Telemetry Pipeline Linux installations

<Info>
  This information is for Palo Alto Networks Telemetry Pipeline, which is a standalone
  product separate from Palo Alto Networks Cortex XCOR.
</Info>

As part of the installation process, Palo Alto Networks Telemetry Pipeline performs
[health checks](/ingest/pipeline/v2/install/install-operator/linux#health-checks) on your behalf.
If you encounter any issues when trying to install Palo Alto Networks Telemetry Pipeline,
take the following troubleshooting steps.

1. Check for any warnings or errors in the output of the health checks
   that Palo Alto Networks Telemetry Pipeline ran on your behalf.

2. Confirm that you've met the
   [networking and OS requirements](/ingest/pipeline/v2/install/prereqs)
   for Palo Alto Networks Telemetry Pipeline.

3. Confirm that you've met the
   [K3s requirements](https://docs.k3s.io/installation/requirements).

4. Run the following command to disable FIPS mode, and then reboot:

   ```shell theme={null}
   fips-mode-setup --disable
   ```

5. Run the following command to disable your firewall:

   <Tabs>
     <Tab title="RHEL" id="disable-firewall-rhel">
       ```shell theme={null}
       systemctl disable firewalld --now
       ```
     </Tab>

     <Tab title="Ubuntu" id="disable-firewall-ubuntu">
       ```shell theme={null}
       ufw disable
       ```
     </Tab>
   </Tabs>

6. Verify that SELinux is either disabled or in permissive (not enforcing) mode.

7. For Red Hat Enterprise Linux only, verify that your cryptographic policy is set to
   either `default` or `legacy`.

8. For Red Hat Enterprise Linux only, run the following command to disable
   `nm-cloud-setup`, then reboot the node:

   ```shell theme={null}
   systemctl disable nm-cloud-setup.service nm-cloud-setup.timer
   reboot
   ```

9. Examine the following K3s network ranges to ensure they aren't conflicting
   with your network settings:

   * Pods are allocated in the CIDR range `10.42.0.0/16`. Use the
     `INSTALL_CALYPTIA_CLUSTER_CIDR` environment variable to override.
   * Services are allocated in the CIDR range `10.43.0.0/16`. Use the
     `INSTALL_CALYPTIA_SERVICE_CIDR` environment variable to override.
   * Cluster DNS is set to `10.43.0.10`. Use the `INSTALL_CALYPTIA_CLUSTER_DNS`
     environment variable to override.
   * The cluster domain suffix is set to `cluster.local`. Use the
     `INSTALL_CALYPTIA_CLUSTER_DOMAIN` environment variable to override.
   * Node ports are allocated in the range `30000` to `32767`. Use the
     `INSTALL_CALYPTIA_SERVICE_NODE_PORT_RANGE` environment variable to override
     during installation.

10. Examine your local `/etc/resolv.conf` configuration to ensure it isn't using
    a DNS server or specifying any override that might conflict with K3s.


## Related topics

- [Install a Core Operator on Linux](/ingest/pipeline/v2/install/install-operator/linux.md)
- [Installation prerequisites](/ingest/pipeline/v2/install/prereqs.md)
- [Upgrade Palo Alto Networks Telemetry Pipeline](/ingest/pipeline/v2/install/upgrade.md)
- [Configure Palo Alto Networks Telemetry Pipeline using Helm](/ingest/pipeline/v2/configure/helm.md)
- [Install Palo Alto Networks Telemetry Pipeline](/ingest/pipeline/v2/install.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.