The customer applied the internal FPC set trace-options commands, the packet loss between RE and FPC, for example, the customer could not access the device lo0 via SSH session. 

start shell pfe network fpc0

## Enable traces from PFE CLI caused the issue

set trace-options cfm control state enable

set trace-options cfm control state extensive

set trace-options cfm packet control  

set trace-options cfm packet port io

set trace-options cfm packet port port

set trace-options cfm packet port transport

set trace-options cfm packet state all enable extensive output verbose

set trace-options ppm control flags all module all state extensive

set trace-options ppm control state enable

set trace-options ppm control state extensive

set trace-options ppm packet all state extensive output verbose

set trace-options ppm packet all

set trace-options ppm packet all output brief

set trace-options ppm packet port level info

set trace-options host-path packet state extensive all enable    

exit

## Disable the trace-options resolved the issue:

set trace-options cfm control state disable

set trace-options ppm packet all state disable

set trace-options host-path packet state all disable

set trace-options ppm control state disable

 This issue we see when we enable all traces for cfmma, ppman, packetio together, this is expected because logging will happen at every level for each packet.