无
客户反馈1/0/0/39、1/0/0/40等端口的流量计数突然不再增长,清空计数后,发现流量计数一直为0,但是流量可以正常转发,对端设备流量计数正常。
(1) 查看端口流量计数,发现流量不增长(已将端口计数reset):
FUZHOU_S12510-probe]dis int ten 1/0/0/39
Input (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input (normal): 0 packets, - bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, - overruns, 0 aborts
- ignored, - parity errors
Output (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output (normal): 0 packets, - bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, - no carrier
(2) 1/0/0/39底层端口名是XE14,查看xe14发下返回报错,说明counter任务已经异常停止了:
[FUZHOU_S12510-probe]bcm c 1 s 0 c 1 show/c/xe14
NOTE: counter collection is not running
[FUZHOU_S12510-probe]bcm c 1 s 0 c 1 show/c/xe14
NOTE: counter collection is not running
[FUZHOU_S12510-probe]bcm c 1 s 0 c 1 show/c/xe16
UC_QUEUE_PEAK(3).xe16 : 1
NOTE: counter collection is not running
(3) 在local logbuffer中有对应2月10日的parity error报错:
Feb 09 2020 16:22:12:741777:
LINE:1160-TASK:DPC1-FUNC:DRV_SDK_Printk:
unit 1 RX Debug Counter port 15 RDBGC6 entry 61463 parity error
Feb 10 2020 01:27:39:974603:
LINE:1160-TASK:DPC1-FUNC:DRV_SDK_Printk:
unit 1 RX Debug Counter port 15 RDBGC6 entry 61463 parity error
说明端口计数表发生parity error,是一种芯片软失效。这种表没有恢复机制。
(4) 再继续查看对应counter表的ingress和egress方向的两个表,都会报出parity error,而且该条表项有时有,有时无:
1) ING_SERVICE_COUNTER_TABLE_x:
[FUZHOU_S12510-probe]bcm c 1 s 0 c 1 d/chg/ING_SERVICE_COUNTER_TABLE_x
ING_SERVICE_COUNTER_TABLE_X.ipipe0[0]: <PACKET_COUNTER=0xf3fb6e3,EVEN_PARITY=1,BYTE_COUNTER=0x1b573e750>
[FUZHOU_S12510-probe]bcm c 1 s 0 c 1 d/chg/ING_SERVICE_COUNTER_TABLE_x
ING_SERVICE_COUNTER_TABLE_X.ipipe0[0]: <PACKET_COUNTER=0x10dea912,BYTE_COUNTER=0xa54e490c6>
2) ING_SERVICE_COUNTER_TABLE:
[FUZHOU_S12510-probe]bcm c 1 s 0 c 1 d/chg/ING_SERVICE_COUNTER_TABLE
ING_SERVICE_COUNTER_TABLE.ipipe0[0]: <PACKET_COUNTER=0x17273f0b,BYTE_COUNTER=0xbc25480bc>
[FUZHOU_S12510-probe]bcm c 1 s 0 c 1 d/chg/ING_SERVICE_COUNTER_TABLE
ING_SERVICE_COUNTER_TABLE.ipipe0[0]: <PACKET_COUNTER=0x179cd864,EVEN_PARITY=1,BYTE_COUNTER=0xe33f072ab>
3) EGR_SERVICE_COUNTER_TABLE_x:
[FUZHOU_S12510-probe]bcm c 1 s 0 c 1 d/chg/EGR_SERVICE_COUNTER_TABLE_x
EGR_SERVICE_COUNTER_TABLE_X.epipe0[0]: <PACKET_COUNTER=0x4830be8,BYTE_COUNTER=0xe886e4306>
[FUZHOU_S12510-probe]bcm c 1 s 0 c 1 d/chg/EGR_SERVICE_COUNTER_TABLE_x
EGR_SERVICE_COUNTER_TABLE_X.epipe0[0]: <PACKET_COUNTER=0x49c7f4b,EVEN_PARITY=1,BYTE_COUNTER=0xf11c48b9c>
4) EGR_SERVICE_COUNTER_TABLE
[FUZHOU_S12510-probe]bcm c 1 s 0 c 1 d/chg/EGR_SERVICE_COUNTER_TABLE
EGR_SERVICE_COUNTER_TABLE.epipe0[0]: <PACKET_COUNTER=0x175d0964,EVEN_PARITY=1,BYTE_COUNTER=0x446bab332>
[FUZHOU_S12510-probe]bcm c 1 s 0 c 1 d/chg/EGR_SERVICE_COUNTER_TABLE
EGR_SERVICE_COUNTER_TABLE.epipe0[0]: <PACKET_COUNTER=0x1775ad4d,BYTE_COUNTER=0x4cbb52738>
(5) 说明是由于parity error导致端口对应芯片的计数进程异常关闭。
重启对应单板来复位芯片回复已经发生且无法自动修复的parity error。
该案例暂时没有网友评论
✖
案例意见反馈
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作