When running gNMI telemetry queries on Juniper MX and PTX routers, reserved-bandwidth values may appear in different units (bps vs kbps). This is not due to platform architecture but results from differences in Junos software versions. Starting in Junos 23.3R1, Juniper standardized telemetry schema to align with OpenConfig models, leading to a change in how bandwidth metrics are reported.

MX router running Junos 24.2R2.18 reports reserved-bandwidth in kilobits per second (kbps).

PTX router running Junos 23.2R2.21-EVO reports reserved-bandwidth in bits per second (bps).

Inconsistent telemetry output across platforms when queried via gNMI.

This behavior is expected and results from schema changes introduced in Junos 23.3R1 and later. To ensure consistent telemetry units across devices:

1. Upgrade both MX and PTX routers to a common Junos version 23.3R1 or later.
2. Verify that the telemetry schema reflects the standardized OpenConfig model, which reports reserved-bandwidth in kbps.

This update is part of Juniper’s ongoing effort to harmonize MPLS telemetry across platforms.