← Back to Articles
Validate PNM file transfer
Last Updated: June 30, 2026
NOTE: For some CMTS vendors, PNM features need to be enabled. Contact your vendor customer support for more information.
If your PNM files do not transfer correctly, use the following tips to help debug the problem.
NOTE: A ServAssure TFTP Receiver is a ServAssure Poller designated as a dedicated TFTP node. You can use these steps to debug PNM file transfer issues on a ServAssure TFTP Receiver and on a ServAssure Poller.
  1. Copy an existing file from your CMTS to the ServAssure Poller or ServAssure TFTP Receiver through TFTP using the CMTS CLI interface.

    Successful transfer of a file verifies TFTP connectivity.

  2. Enable logging on the ServAssure Poller or ServAssure TFTP Receiver.
    On the ServAssure Poller or ServAssure TFTP Receiver, edit the file, docsis-poller.logback.xml, and change the following:
    <logger name="KeepTmpFiles.TFTP" level="trace"/>

    This change keeps the received TFTP binary files on the ServAssure Poller or ServAssure TFTP Receiver in the directory /opt/arris/docsis-poller/tmp, and will accept and log ANY files it receives.

  3. Enable more detailed logging on the ServAssure Poller or ServAssure TFTP Receiver.
    On the ServAssure Poller or ServAssure TFTP Receiver, edit the docsis-poller.logback.xml file, and change the following:
    <logger name="tftp-datagram" level="trace"/>

    This provides large amounts of information for every TFTP packet received, formatted as an octet dump. The output is useful for advanced debugging.