This read-create INTEGER selects, per its source description, where a BFD session using this admin-table template terminates: cpmNp(1) forces termination on the CPM card's Network Processor, while auto(2) lets the system choose a termination point other than the CPM Network Processor (implicitly, iomHw(3) points to IOM hardware-based termination). Admins pick cpmNp for sessions needing centralized software-based BFD handling, or auto/iomHw for distributed, hardware-accelerated BFD better suited to high session counts. For example, choosing iomHw(3) for a template applied to many high-speed links would offload BFD processing to line-card hardware instead of the central CPM.