Below PECHIP logs are noticed on the FPC type LC1101 - 30C / 30Q / 96X
fpc0 pechip_q_cm_cpuvoq_stats_get:5823: PECHIP[4]: Error reading register: cm.stats.cpuvoq[234].s
fpc0 PE[4]Failed to get stats forlcpu=29 index=234
The below logs messages repeatedly on FPC
> show chassis alarms no-forwarding No alarms currently active log messages: fpc0 pechip_q_cm_cpuvoq_stats_get:5823: PECHIP[4]: Error reading register: cm.stats.cpuvoq[234].s fpc0 PE[4]Failed to get stats forlcpu=29 index=234 fpc0 trinity_pio: 1 PIO errors occurred fpc0 trinity_pio: Last error: 10 pe4 Paradise PCI 0x00000000 Write PCIe fpc0 pechip_q_cm_cpuvoq_stats_get:5823: PECHIP[4]: Error reading register: cm.stats.cpuvoq[234].s fpc0 PE[4]Failed to get stats forlcpu=29 index=234 fpc0 pechip_q_cm_cpuvoq_stats_get:5823: PECHIP[4]: Error reading register: cm.stats.cpuvoq[234].s fpc0 PE[4]Failed to get stats forlcpu=29 index=234
Workaround:
the PECHIP error happened when the FPC CPU was trying to read some data from one of the PFE ASICs via the PCI bus and failed to do so. This FPC CPU PFE ASIC data is only used for control-plane and/or management operations so it shouldn't affect data-plane forwarded traffic.
The cause for these errors is most likely a transient error which will be cleared by an FPC restart during the MW. > request chassis fpc slot <slot no> restartExecuting this command initiates a restart of the FPC, providing an opportunity for the system to reset and realign its components, potentially resolving the PECHIP error.