[rbak-nsp] %QOS-0-RCM: qos rcm error: Could not locate card in slot error code 3

[Wojciech Wrona]

Nice to hear someone have seen it. Is there any way to pinpoint which
card is creating this trouble? I have to mention that this is the first
time we're seeing this log. So i suppose it can be a hardware thing. We
have a lot of spare ones so it won't be a problem but i don't like doing
a blind test on production traffic.

BTW. Perhaps You also seen those: we're seeing 2 more strange logs, but
those 2 are since years, and since we didn't see any real issue behind
this we just ignored them. We have note in our internal docs that those
appeared just after upgrade from SEOS-12.1.1.11p7 to SEOS-12.1.1.12-p15.

Jun 11 02:01:24: [255/22:13:58/1/1/12]: %STAT-3-ERR_GEN:
[stat_ppa_counter_data_negative_check_brief] tx_bytes
-4311197817822996298 level 0
Jun 11 02:01:24: [255/22:13:58/1/1/12]: %STAT-3-ERR_GEN:
[stat_ppa_counter_data_negative_check_brief] tx_packets
-4340387178800811508 level 0

Jun 11 03:13:50: %PPAQOS-3-QOS_ERROR:
783d250a/0090530813/975500000:01/EPPA/EU00:For cct
255/22:13:58/6/2/38926 policy type 200 failed to process parameter 6,
error code 1 - 001a5eee 003a30cc 001a512e 0016f84e 0003f30e 0020f94c
0021348c 0003dbae 0039ebcc 0039eb80 00000000
Jun 11 03:13:50: %PPAQOS-3-QOS_ERROR:
0a11acd5/0090516483/765900000:02/EPPA/EU00:For cct
255/22:13:58/6/2/38926 policy type 200 failed to process parameter 6,
error code 1 - 001a5eee 003a30cc 001a512e 0016f84e 0003f30e 0020f94c
0021348c 0003dbae 0039ebcc 0039eb80 00000000

We've even considered coming back to SEOS-12.1.1.11p7 because it was
very stable a no strange things was found in logs, but BGP fix which was
introduced in this version was more important.

Best regards,

-- 
Wojciech Wrona

W dniu 11.06.2023 o 01:20, Rafal O. pisze:
> Hey
>
> It's  about  linecard.  some  of  qos  settings could not be passed to
> linecard due to bug/hardware fault. This mostly result as improper
> qos appiled to circut,subscriber etc.
> Reloading cards fix these bugs but they will come back.
> It mostly happend after some errors like this (you may not see them by
> default logging)
> [xfp_Task]scc:ERROR:HI:krSclHubErrorRecovery(krakenScl.c,1663):
> %LOG-6-TDM_CONS:     Unable to read or clear HUB interrupts or bring up an scl link on linecard slot  6. (error 0x0003/0x004d) (hub_reset 0)
> %LOG-6-TDM_CONS: 2023/5/11 21:0:26[xfp_Task]pktLayer:ERROR:HI:hubRegRead1BFSlow(hubAccess.c,1639):
> %LOG-6-TDM_CONS:     xfpDrv_Rd1B:309:hubRegRead1BFSlow(slot 5, asic 19, addr 0xd3de, count 1) failed 0x0003004d
>
> Maybe XFP module faulty but didn't found way to resolve it.
>
>
> Rafal
>
>
>
>
> W liście datowanym niedziela, 11 czerwca 2023 (00:40:55) napisano:
>
>> Hi everyone,
>> I know... i should consider turning this equipment off already. But it
>> is still working almost fine :) No it is working great in fact, but
>> started putting this strange line in log file:
>> Jun 10 23:55:41: [255/27:1:28/1/2/4282]: %QOS-0-RCM:  qos rcm error:
>> Could not locate card in slot  error code 3
>> What card ? CF card ? Line Card ? But all the line cards are in and
>> working. Where can I look for more information ?
>> Best regards,
>
>
>