Description

What is causing the "RODR offset overflow count incremented" error in the messages log file when the FPC restarts?

Symptoms

Here are the sample logs:

Jan 28 10:48:20.050 2010 Router_A fpc3 NFAB(3/1): %PFE-3: RODR offset overflow count incremented (1)
Jan 28 10:48:20.050 2010 Router_A fpc3 CMALARM: %PFE-3: Error (code: 542, type:Minor) encountered, cmalarm_passive_alarm_signal
Jan 28 10:49:32.063 2010 Router_A fpc3 NFAB(3/0): %PFE-3: RODR offset overflow count incremented (1)
Jan 28 10:49:32.064 2010 Router_A fpc3 CMALARM: %PFE-3: Error (code: 542, type:Minor) encountered, cmalarm_passive_alarm_signal
Jan 28 10:54:03.052 2010 Router_A fpc3 NFAB(3/0): %PFE-3: RODR offset overflow count incremented (1)
Jan 28 10:54:03.053 2010 Router_A fpc3 CMALARM: %PFE-3: Error (code: 542, type:Minor) encountered, cmalarm_passive_alarm_signal

When one FPC restarts, another FPC might report these error logs.

Solution

This is a normal behavior when restarting the FPC in one slot.

Each destination PFE uses its own set of sequence numbers to reorder the cells it receives from across the switch fabric. After an FPC has been restarted, the Nf chip needs to resynchronize cell sequence numbers before it can start processing traffic again. This message is transient and should not be seen after a few reports and traffic resumes.