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

[Rafal O.]

Hello

I  think  same  errors  happend  to  everyone  after  some time  to all
redbacks.   stat_ppa_counter_data_negative_check_brief   is   possibly
counter overflow, some happend to me more often when lots of multicast
traffic was sent/received.

I  also  receiving  same errors from QOS, like 1-3 per
day.
%PPAQOS-3-QOS_ERROR: 3fb30f4e/0001160244/745800000:06/EPPA/EU00:For cct 255/22:13:58/6/2/279050 policy type 200 failed to process parameter 6, error code 1 - 001a5eee 003a30cc 001a512e 0016f84e 0003f30e 0020f94c 0021348c 0003dbae 0039ebcc 0039eb80 00000000
Lots  of  these  errrors  at short time indicates problem with QOS and
customers  traffic  policy  is affected. Mostly results as performance
degradation.  Only  fix  is  to reload all cards after some time, this
solves problem for like month, then it comes back.

Rafal




W liście datowanym niedziela, 11 czerwca 2023 (11:20:22) napisano:

> 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,




-- 
Pozdrowienia,
 Rafal O.