When the collector is doing a snmpbulkwalk for data points it is timing out with Reason: (genError) A general failure occurred”.
Note that it is not been triggered on a certain OID, it’s random.
We have restarted the snmpd/mib2/chassisd/FPC1.
Error message seen :
/home/c798977 > c798977@vusno238: snmpbulkwalk -Cr20 -v2c -Os -c epi-read wqbv-e-071
…
ifInOctets.1430 = Counter32: 0
Error in packet.
Reason: (genError) A general failure occured
Failed object: ifInOctets.1430
AFT Ingress queueing is not supported on 21.4 branch, but this has been enabled on fpc4 and fpc8 which is MPC10E. traffic-manager mode ingress-and-egress configs has to be removed from FPC4 as well as FPC8. And restart FPC4 and FPC8. FPC 4 MPC10E 3D MRATE-15xQSFPP FPC 8 MPC10E 3D MRATE-15xQSFPP fpc 4 { pic 0 { traffic-manager { mode ingress-and-egress; --> not supported } port 0 { speed 100g; } port 3 { number-of-sub-ports 4; speed 10g; } port 4 { number-of-sub-ports 4; speed 10g; } } pic 1 { traffic-manager { mode ingress-and-egress; --> not supported } port 2 { speed 100g; } port 3 { number-of-sub-ports 4; speed 10g; } port 4 { number-of-sub-ports 4; speed 10g; } } pic 2 { traffic-manager { mode ingress-and-egress; --> not supported } port 0 { speed 100g; } port 3 { number-of-sub-ports 4; speed 10g; } } flexible-queuing-mode; } fpc 8 { pic 0 { traffic-manager { mode ingress-and-egress; --> not supported } port 0 { speed 100g; } port 3 { number-of-sub-ports 4; speed 10g; } port 4 { number-of-sub-ports 4; speed 10g; } } pic 1 { traffic-manager { mode ingress-and-egress; --> not supported } port 2 { speed 100g; } port 3 { number-of-sub-ports 4; speed 10g; } port 4 { number-of-sub-ports 4; speed 10g; } } pic 2 { traffic-manager { mode ingress-and-egress; --> not supported } port 0 { speed 100g; } port 3 { number-of-sub-ports 4; speed 10g; } } flexible-queuing-mode; }