Solved: %IOSXE-3-PLATFORM: R0/0: cmand: Clocking device Parity Error occured

psymonds7769 · ‎07-21-2023

Has anyone seen this log message in a Cisco ASR 920 before?

Peter Paluch · ‎07-21-2023

Hi Flavio, hi psymonds7769,

The document referred to Flavio is a nice general introduction to parity errors but it is specific to ASR9000 IOS-XR devices while here, the router is an ASR920 running IOS XE.

I've checked internally - on RSP2, there is a clocking chip providing clocking signal to some of the hardware components. IOS XE periodically verifies if the processor of this clocking chip responds correctly to a status poll. If it does not, IOS XE produces the "Clocking device Parity Error occured" message. I would even say that the

parity error

is a little misleading here but that is just my personal opinion.

Usually, this is a transient error that is resolved by a reload, and is unlikely to reoccur. However, if it reappears even after a reload, it is best to open a TAC case for this, as it might be necessary to RMA the device.

So, if you can afford a reload in a maintenance window, consider giving it a try, and let's take it from there.

Best regards,
Peter

View solution in original post

Flavio Miranda · ‎07-21-2023

Hi @psymonds7769

Seems to be related to bugs. There is a cisco docs discussing regarding this.

https://www.cisco.com/c/en/us/support/docs/routers/asr-9000-series-aggregation-services-routers/211255-Parity-errors-seen-on-ASR9k.html

Peter Paluch · ‎07-21-2023

Hi Flavio, hi psymonds7769,

The document referred to Flavio is a nice general introduction to parity errors but it is specific to ASR9000 IOS-XR devices while here, the router is an ASR920 running IOS XE.

I've checked internally - on RSP2, there is a clocking chip providing clocking signal to some of the hardware components. IOS XE periodically verifies if the processor of this clocking chip responds correctly to a status poll. If it does not, IOS XE produces the "Clocking device Parity Error occured" message. I would even say that the

parity error

is a little misleading here but that is just my personal opinion.

Usually, this is a transient error that is resolved by a reload, and is unlikely to reoccur. However, if it reappears even after a reload, it is best to open a TAC case for this, as it might be necessary to RMA the device.

So, if you can afford a reload in a maintenance window, consider giving it a try, and let's take it from there.

Best regards,
Peter

Joseph W. Doherty · ‎07-21-2023

From your description,

parity error

does seem a bit of a misnomer.

marce1000 · ‎07-21-2023

- FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvp32921

M.

-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Peter Paluch · ‎07-21-2023

Hi ; ),

Indeed, there were a few software defects related to the same symptom - but the one you have mentioned is related to a stateful switchover (SSO). This is not applicable to ASR920 since these do not have redundant RSPs, and so they cannot perform a SSO which is the trigger for the defect above.

Best regards,
Peter