Description

This article describes the log messages: "PE Chip: PE-2[2]: FABRORD[2-GNT]:ecc: 0x0007f800: Timeout timestamp database (URI: /fpc/0/pfe/0/cm/0/PE_Chip/2/PECHIP_CMERROR_DT_COMPLETE_DGSN_SKIP)" and provides solution for the same.

Symptoms

1) Below log messages are observed in the device:

fpc0 Cmerror Op Set: PE Chip: PE-2[2]: FABRORD[2-GNT]:ecc: 0x0007f800: Timeout timestamp database (URI: /fpc/0/pfe/0/cm/0/PE_Chip/2/PECHIP_CMERROR_DT_COMPLETE_DGSN_SKIP)
fpc0 Cmerror Op Set: PE Chip: PE-2[2]: FABRORD[2-GNT]:ecc: 0x0007f800: Timeout timestamp database (URI: /fpc/0/pfe/0/cm/0/PE_Chip/2/PECHIP_CMERROR_DT_COMPLETE_DGSN_SKIP)
fpc0 Cmerror Op Set: PE Chip: PE-2[2]: FABRORD[2-GNT]:ecc: 0x0007f800: Timeout timestamp database (URI: /fpc/0/pfe/0/cm/0/PE_Chip/2/PECHIP_CMERROR_DT_COMPLETE_DGSN_SKIP)
Jun 13 01:06:41 2025 deprwi0201h fpc0 Cmerror Op Set: PE Chip: PE-2[2]: FABRORD[2-GNT]:ecc: 0x0007f800: Timeout timestamp database (URI: /fpc/0/pfe/0/cm/0/PE_Chip/2/PECHIP_CMERROR_DT_COMPLETE_DGSN_SKIP)
fpc0 Cmerror Op Set: PE Chip: PE-2[2]: FABRORD[2-GNT]:ecc: 0x0007f800: Timeout timestamp database (URI: /fpc/0/pfe/0/cm/0/PE_Chip/2/PECHIP_CMERROR_DT_COMPLETE_DGSN_SKIP)
fpc0 Cmerror Op Set: PE Chip: PE-2[2]: FABRORD[2-GNT]:ecc: 0x0007f800: Timeout timestamp database (URI: /fpc/0/pfe/0/cm/0/PE_Chip/2/PECHIP_CMERROR_DT_COMPLETE_DGSN_SKIP)
fpc0 Cmerror Op Set: PE Chip: PE-2[2]: FABRORD[2-GNT]:ecc: 0x0007f800: Timeout timestamp database (URI: /fpc/0/pfe/0/cm/0/PE_Chip/2/PECHIP_CMERROR_DT_COMPLETE_DGSN_SKIP)
fpc0 Cmerror Op Set: PE Chip: PE-2[2]: FABRORD[2-GNT]:ecc: 0x0007f800: Timeout timestamp database (URI: /fpc/0/pfe/0/cm/0/PE_Chip/2/PECHIP_CMERROR_DT_COMPLETE_DGSN_SKIP)
fpc0 Cmerror Op Set: PE Chip: PE-2[2]: FABRORD[2-GNT]:ecc: 0x0007f800: Timeout timestamp database (URI: /fpc/0/pfe/0/cm/0/PE_Chip/2/PECHIP_CMERROR_DT_COMPLETE_DGSN_SKIP)
fpc0 Cmerror Op Set: PE Chip: PE-2[2]: FABRORD[2-GNT]:ecc: 0x0007f800: Timeout timestamp database (URI: /fpc/0/pfe/0/cm/0/PE_Chip/2/PECHIP_CMERROR_DT_COMPLETE_DGSN_SKIP)



2) Alarms may not necessarily be present.
------------------------------------------------------
user@labroot> show chassis alarms no-forwarding 
No alarms currently active




Solution

The said log messages are due to timeout occurred when accessing the timestamp database during Fabric cell Re-ordering.

In general, Fabric cell Re-ordering usually refers to the operation of reordering Cell models in Fabric. If there is a delay during this period, it may lead to an inconsistent order of Cell arriving at the destination, so it needs to be reordered.

 

1) When the logs are observed, do check for any historical records of the same, and if found none, and the error logs stopped immediately, without any impact, the reason of timeout could be related to transient memory error.

 

2) If the logs are not just a single occurrence, and you see them recurring, then proceed with soft FPC reboot in a maintenance window.

Modification History

2025-06-24 : Article Created