This article describes that why TAWMP Inline-timestamp services is available only on MX platforms upto MPC7E cards only & not any higher line cards.
When you configure the TWAMP inline-timestamp services on MPC10E or any higher version then MPC7E card below error logs will be seen :
Oct 19 19:02:29.000 2024 MX_RE : %PFE-3: fpc10 user.err aftd-trio: [Error] DFW Dfw Action creation failed
Oct 19 19:02:29.000 2024 MX_RE : %PFE-3: fpc10 user.err aftd-trio: [Error] DFW Unable to clear Action Table: __TwampReflector:2 ,0
Oct 19 19:02:29.000 2024 MX_RE : %PFE-3: fpc10 user.err aftd-trio: [Error] DFW ERROR: Failed to addAction for ActionType:TwampReflector
Oct 19 19:02:29.000 2024 MX_RE : %PFE-3: fpc2 user.err aftd-trio: [Error] DFW Dfw Action creation failed
Oct 19 19:02:29.000 2024 MX_RE : %PFE-3: fpc2 user.err aftd-trio: [Error] DFW Unable to clear Action Table: __TwampReflector:2 ,0
Oct 19 19:02:29.000 2024 MX_RE : %PFE-3: fpc2 user.err aftd-trio: [Error] DFW ERROR: Failed to addAction for ActionType:TwampReflector
Oct 19 19:07:54.000 2024 MX_RE : %PFE-3: fpc10 user.err aftd-trio: [Error] DFW Unable to clear Action Table: __TwampReflector:0 ,0
Oct 19 19:07:54.000 2024 MX_RE : %PFE-3: fpc10 user.err aftd-trio: [Error] DFW ERROR: Failed to addAction for ActionType:TwampReflector
Oct 19 19:07:54.000 2024 MX_RE : %PFE-3: fpc2 user.err aftd-trio: [Error] DFW Dfw Action creation failed
Oct 19 19:07:54.000 2024 MX_RE : %PFE-3: fpc2 user.err aftd-trio: [Error] DFW Unable to clear Action Table: __TwampReflector:0 ,0
Oct 19 19:07:54.000 2024 MX_RE : %PFE-3: fpc2 user.err aftd-trio: [Error] DFW ERROR: Failed to addAction for ActionType:TwampReflector
Oct 19 19:24:37.589 2024 MX_RE chassisd[14043]: %DAEMON-6-CHASSISD_PARSE_COMPLETE: Using new configuration
Oct 19 19:24:46.659 2024 MX_RE alarmd[14503]: %DAEMON-4: Alarm set: License id=0, color=YELLOW, class=CHASSIS, reason=Real-time Performance Monitoring(97) usage requires a license
Oct 19 19:24:46.659 2024 MX_RE craftd[14047]: %DAEMON-4: Minor alarm set, Real-time Performance Monitoring(97) usage requires a license
Oct 19 19:25:19.000 2024 MX_RE : %PFE-3: fpc10 user.err aftd-trio: [Error] DFW Dfw Action creation failed
Oct 19 19:25:19.000 2024 MX_RE : %PFE-3: fpc10 user.err aftd-trio: [Error] DFW Unable to clear Action Table: __TwampReflector:0 ,0
Oct 19 19:25:19.000 2024 MX_RE : %PFE-3: fpc10 user.err aftd-trio: [Error] DFW ERROR: Failed to addAction for ActionType:TwampReflector
Oct 19 19:25:19.000 2024 MX_RE : %PFE-3: fpc2 user.err aftd-trio: [Error] DFW Dfw Action creation failed
We have two ways of TWAMP support at client and server side. Upto MPC7, we support TWAMP using ukern timestamp (timestamp at host PFE) and inline timestamp (timestamp at LU chip). In case of AFT based trinity line cards MPC10E (Ferrari), MPC11E (RedBull), LC9600 (Alfa Romeo), and Bugatti, we support only ukern timestamps(packetIO)
1. TWAMP using ukern timestamp (timestamp at host PFE)
for ukern timestamps, we don't need to configure the si-* interfaces and destination-interface TWAMP client side.
Based on the route to the target-addess, source-address is selected from the list of available interfaces.
This scenario is applicable for all the physical interfaces and loopback interfaces. This feature is available on all the line cards (MPC1 to MPC11, Alfa Romeo and Bugatti) and on most of the platforms (MX, PTX, ACX, EX, and QFX)using Junos.
2. Inline-timestamp (timestamp at LU chip) on MX platforms using JUNOS
This feature is available only on MX platforms upto MPC7E cards. On other platforms this feature is not supported.
For this feature to support, inline service interface( si-*) is needed and destination-interface is required under TWAMP client.
This feature is available only on in house Junos trinity PFE chipset upto MPC7E cards using MX platforms.
On AFT based trinity line cards MPC10E (Ferrari), MPC11E (RedBull), LC9600 (Alfa Romeo), and Bugatti, this feature is not implemented yet.
As mentioned above this feature is not supported in MPC10E cards & supported only till MPC7E due to which you had no issues when MPC7E was used in place of MPCE10E.