This article explains the meaning of the syslog messages that appear while performing packet dump of a PECHIP Trapstat.

The following log messages appear while dumping a PECHIP trapstat on any PTX/QFX device having PE Chipset:

Mar 10 04:56:32 PTX1000 : %PFE-3: fpc0 jprds_sample_trap_params_set_hw : 1650 sanity failed  
Mar 10 04:56:32 PTX1000 : %PFE-3: fpc0 jprds_sample_trap_params_set : 1713 prds_sample_trap_params_set_hw failed  
Mar 10 04:56:52 PTX1000 : %PFE-3: fpc0 jprds_sample_trap_params_set_hw : 1650 sanity failed  
Mar 10 04:56:52 PTX1000 : %PFE-3: fpc0 jprds_sample_trap_params_set : 1713 prds_sample_trap_params_set_hw failed 

The syslogs messages are non-impacting. They appear when dumping a trapcode in PTX1000 chassis because the user entered an invalid PFE-ID. The PTX1000 PECHIP has 6 PFE's with ID 0 to 5. Change the PFE-ID to a number between 0 to 5, then the syslog messages will no longer appear.

Below are the syslog messages from the local lab.
 

FPC0(LAB vty)# show jspec client   

 ID    Name

 1    PECHIP[0]    

 2    PECHIP[1]    

 3    PECHIP[2]    

 4    PECHIP[3]    

 5    PECHIP[4]    

 6    PECHIP[5]

-------------------

FPC0(LAB vty)# set jsample pfe 8 trapcode 149 enable sample-id 3 enable >> Entered PFE ID 8

-------------------

Mar 13 00:52:10 lab_ptx fpc0 jprds_sample_trap_params_set_hw : 1650 sanity failed

Mar 13 00:52:10 lab_ptx fpc0 jprds_sample_trap_params_set : 1713 prds_sample_trap_params_set_hw failed

2023-05-04: Initial publication