Boot-up errors with A9K-RSP-4G

[nesttech1]

We have noticed the following errors after completing the TURBOBOOT with Version 5.1.2.

We have several A9K-RSP-4G modules and these errors appear with some of these and do not appear with others.

All of the A9K-RSP-4G units seem to be similar, so we do not understand what is causing these errors and if they are siginifcant.

Once the router completes the boot sequence, all installed line cards look to be running OK.

Here are these errors:

LC/0/0/CPU0:Oct 23 18:37:04.956 : pfm_node_lc[290]: %PLATFORM-FCA-2-CLK_FAIL : Set|lda_server[45088]|0x1044000|Device driver for device 'STARKAD Mother Board FPGA' detected clock reference failure / DPLL unlock indicator on 'ZARLINK Bus'. GPIO reporting the problem is 0.
LC/0/0/CPU0:Oct 23 18:37:05.066 : pfm_node_lc[290]: %PLATFORM-FCA-2-MISC_ERROR : Set|lda_server[45088]|0x1045000|Device driver for device 'RAGNAR Daughter Board FPGA' detected the error 'Timestamp Block: PWM bit level decoding error decoder A'
LC/0/0/CPU0:Oct 23 18:37:06.137 : canb_upg_agt[132]: %PLATFORM-UPGRADE_FPD-4-DOWN_REV : cbc instance 0 is down-rev (V20.117), upgrade to (V20.118). Use the "upgrade hw-module fpd" CLI in admin mode.

Any comments will be appreciated.  Thank you.

[xthuijs · Accepted solution]

Looks like your FPD's are out of rev; the clock chip (aka DTI) receives messages it doesnt understand, the same applies to your canbus controller/CBC).

admin install the fpd pie and run the command admin upgrade hw-module fpd all location all.

that will resolve this problem.

cheers

xander

[nesttech1]

Xander,

Your recommendation solved this problem.  Thank you.

We also encountered the following message with one of the ASR-9006-AC-V2 chassis:

RP/0/RSP0/CPU0:Oct 28 20:26:08.874 : bpe[145]: %PLATFORM-BPE-3-ERR : I2C eeprom CRC mismatch, expect 0xa01a, got 0x34a7 , Corrupted file system detected(0x12e)  : pkg/bin/bpe : (PID=237668) :  -Traceback= 40003374 40003854 40000bac 4ba63328 4ba610b8 400002d8 40001100 40005cf4

This message does not appear with another chassis that we have.

Any suggestions for this one?

Thank you,

Michael.

[xthuijs]

Awesome Glad to hear!!

say this is maybe a back plane eprom of the chassis (BPE) that got wacked for whatever reason, very unusual.

you could try this:

go to  rommon

rommon 1> priv

rommon 2> bpcookie

and just enter through all the entries, dont change anything just to update the crc

and that might resolve the issue.

like what I said, never happens as BPE is never written to unless manually done...

if doesnt resolve, do a TAC case and possibly ask for a replacement, but this is not a hw failure pers-e.

xander

[nesttech1]

Xander,

When I enter the command "bpcookie", the the detail comes up at once and there is no place where I can confirm each line by line.

Let me know.

Thank you,

Michael.