Compatible issue when using TDD vSWA version 10.3.x to work with MPC10E, and upgraded the deployment to 11.7.x to fix this issue, however, after the upgraded still not able to decode the telemetry data from MPC10E
Firewall counters on the MX960:
{master}
junipertdd@TOK-SGW-AR01-RE1> show firewall |match corero
Corero-Allowed-ae10.0-inet-i 479879302589825 632969429342
Corero-Allowed-ae3.0-inet-i 669612538246711 511401743206
Corero-Allowed-xe-0/0/6.599-inet-i 29201684826932 116772003374
Corero-Allowed6-ae10.0-inet6-i 629345802016 6339032556
Corero-Allowed6-ae3.0-inet6-i 1510130460751 5954124912
Corero-Allowed6-xe-0/0/6.599-inet6-i 318968547675 2895800306
CORERO-MITIGATE filter had been applied to ae0, which is an ae interface on MPC10E:
junipertdd@TOK-SGW-AR01-RE1> show configuration interfaces |display set | match ae3
set interfaces et-7/0/4 gigether-options 802.3ad ae3
......
set interfaces ae3 unit 0 family inet filter input-list CORERO-MITIGATE
set interfaces ae3 unit 0 family inet filter input-list Dummy-filter
set interfaces ae3 unit 0 family inet6 filter input-list CORERO-MITIGATE6
set interfaces ae3 unit 0 family inet6 filter input-list Dummy-filter-v6
junipertdd@TOK-SGW-AR01-RE1> show chassis hardware models | match "fpc 7"
FPC 7 REV 45 750-078633 CAPY2598 MPC10E-10C-X
Compare configurations on SWA for the non-working router to other routers listed and they are the same.
No issues were found with the KV store on vSWA and the KV store shows no errors.
The last telemetry update from the router was almost a couple of weeks before the upgrade
Upon further checking found that the Junos version on the MX was 21.4R3-S3.4.
Juniper changed the telemetry messages format which the vSWA could not parse and hence they had to release an updated MX version to 22.2R3-S3 and 22.4R2-S2 that could parse the messages correctly