PTX10008
24.4R2-S4.15-EVO
SR-TE Policy-level and Segment List-level traffic counters are not reported simultaneously on PTX10008.
Both tests used gNMI dial-out with gpb-gnmi encoding, a 5-second reporting interval, and the same subscription:
1. Basic statistics mode:
set protocols source-packet-routing telemetry statistics
Attachment: disable-per-segment-list.txt
Test window: September 10, 2026, 12:15:31–12:17:12.
Policy-level in-pkts/in-octets were reported:
2026/09/10 12:15:31 system_id: PTX82-DUT
2026/09/10 12:15:31 component_id: 1
2026/09/10 12:15:31 sensor_name: sensor_1006_1_3
2026/09/10 12:15:31 subscribed_path: /network-instances/network-instance/segment-routing/te-policies/
2026/09/10 12:15:31 streamed_path: /network-instances/network-instance/segment-routing/te-policies/
2026/09/10 12:15:31 component: evo-aftmand-bt
2026/09/10 12:15:31 prefix: /network-instances/network-instance[name='DEFAULT']/segment-routing/te-policies/te-policy[endpoint='10.255.255.2'][color='100']
2026/09/10 12:15:31 name: state
2026/09/10 12:15:31 name: counters
2026/09/10 12:15:31 name: in-pkts
2026/09/10 12:15:31 uint_val: 19843314
2026/09/10 12:15:31 name: in-octets
2026/09/10 12:15:31 uint_val: 9802597116
No Segment List-level counters or Policy-level out-pkts/out-octets were found in this test window.
2. Per-source, per-segment-list mode:
set protocols source-packet-routing telemetry statistics per-source per-segment-list
Attachment: enable-per-segment-list.txt
Test window: September 10, 2026, 12:18:43–12:20:19.
Segment List-level out-pkts/out-octets were reported:
2026/09/10 12:18:43 system_id: PTX82-DUT
2026/09/10 12:18:43 component_id: 1
2026/09/10 12:18:43 sensor_name: sensor_1007_1_1
2026/09/10 12:18:43 subscribed_path: /network-instances/network-instance/segment-routing/te-policies/
2026/09/10 12:18:43 streamed_path: /network-instances/network-instance/segment-routing/te-policies/
2026/09/10 12:18:43 component: evo-aftmand-bt
2026/09/10 12:18:43 prefix: /network-instances/network-instance[name='DEFAULT']/segment-routing/te-policies/te-policy[color='100'][endpoint='10.255.255.2']/candidate-paths/candidate-path[originator-asn='0'][protocol-origin='30'][originator-addr='0.0.0.0'][discriminator='0']/segment-lists/segment-list[id='128']
2026/09/10 12:18:43 name: counters
2026/09/10 12:18:43 name: out-pkts
2026/09/10 12:18:43 uint_val: 363435
2026/09/10 12:18:43 name: state
2026/09/10 12:18:43 name: out-octets
2026/09/10 12:18:43 uint_val: 179536890
No Policy-level counters were found in this test window.
Our tests show that Policy-level counters are reported in basic statistics mode, while only Segment List-level counters are reported with per-source per-segment-list enabled.
The customer needs visibility at both levels simultaneously. Could you confirm whether the observed behavior is by design and whether simultaneous reporting is supported? If supported, please advise how to enable it.
Below is my Telemetry config in lab test:
set services analytics zero-suppression no-zero-suppression
set services analytics streaming-server TELEMETRY_SER remote-address x.x.x.x
set services analytics streaming-server TELEMETRY_SER remote-port 54321
set services analytics export-profile TELEMETRY_PRO reporting-rate 5
set services analytics export-profile TELEMETRY_PRO format gpb-gnmi
set services analytics export-profile TELEMETRY_PRO transport grpc
set services analytics export-profile TELEMETRY_PRO routing-instance mgmt_junos
set services analytics sensor COUNTERS-V4 server-name TELEMETRY_SER
set services analytics sensor COUNTERS-V4 export-name TELEMETRY_PRO
set services analytics sensor COUNTERS-V4 resource /junos/system/linecard/interface/logical/family/ipv4/usage/
set groups elp-tel services analytics sensor SR-TE-POLICY-ALL server-name TELEMETRY_SER
set groups elp-tel services analytics sensor SR-TE-POLICY-ALL export-name TELEMETRY_PRO
set groups elp-tel services analytics sensor SR-TE-POLICY-ALL resource /network-instances/network-instance/segment-routing/te-policies
Static colored SR-TE policy SRTE-C100 (color 100 → y.y.y.y, BSID 800100) with two segment lists SL1/SL2, policy Up.
A. set protocols source-packet-routing telemetry statistics (tunnel-level)
Plain text
Name: SRTE-C100 State: Up
Telemetry statistics: <-- tunnel-level block
Sensor-name: y.y.y.y-64, Id: 3758096386 (ingress)
Sensor-name: c3564-y.y.y.y-64, Id: 3758096387 (transit/BSID)
Path: SL1 ... (no sensors)
Path: SL2 ... (no sensors)
B. add per-source per-segment-list
<tunnel-level "Telemetry statistics:" block is GONE>
Path: SL1
Telemetry Ingress statistics: y.y.y.y-64-1e-0-0.0.0.0-0-80 Id: 3758096388
Telemetry transit statistics: y.y.y.y-64-1e-0-0.0.0.0-0-80-c3564 Id: 3758096389
Path: SL2
Telemetry Ingress statistics: y.y.y.y-64-1e-0-0.0.0.0-0-100 Id: 3758096390
Telemetry transit statistics: y.y.y.y-64-1e-0-0.0.0.0-0-100-c3564 Id: 3758096391
Sensor IDs ...386/387 were destroyed and replaced by ...388–391. The policy-level counter object no longer exists, so the OC path te-policy[color][endpoint]/state/counters has nothing backing it while per-segment-list is enabled — exactly matching the CLI-reference note "Enabling the parameter per-segment-list will disable tunnel sensors."
Conclusion: policy/tunnel counters and segment-list counters are mutually exclusive by design — one counter set per steering route. Collector must sum the per-segment-list counters to derive the policy total.
Please refer to the document,
https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/source-packet-routing-edit-protocols.html#:~:text=source%2Dnat-,source%2Dpacket%2Drouting%20(Junos%20Telemetry%20Interface),-source%2Dpacket%2Drouting