We are testing SR-TE telemetry on a PTX10008 running Junos OS Evolved 26.2R1.7.

The following OpenConfig root path is subscribed:

/network-instances/network-instance/segment-routing/te-policies

The device is configured with:

set protocols source-packet-routing telemetry statistics per-source per-segment-list

We tested both gNMI dial-in and gRPC dial-out. The same behavior is observed in both modes.

Assistance Requested

1. Please confirm the supported SR-TE OpenConfig operational-state leaves for PTX10008 /PTX10016

2. Please confirm whether any additional configuration is required for RPD to publish these leaves.

3. If the leaves are supported, please investigate whether this behavior is a software defect.

Current Observations

1. SR-TE forwarding and operational state appear healthy on the device.

The output of "show spring-traffic-engineering lsp detail" shows that the SR-TE LSPs and paths are Up. ERO Valid is true, segment-list IDs such as 128, 256 and 384 are present, and the corresponding SID labels are displayed.

2. PFE-originated telemetry is exported successfully.

The AFT/PFE components (component IDs 1, 3, 4, 5 and 6) export the policy keys, candidate-path keys, segment-list IDs and per-segment-list counters. The packet and octet counters are received and increase as traffic passes through the policies.

Junos native SR-TE counter sensors also export packet and byte data successfully. This confirms that the telemetry connection and data collection pipeline are operational.

3. RPD-originated OpenConfig operational-state data is missing.

For the same OpenConfig subscription, component ID 65535, component "rpd", periodically sends updates containing only timestamps. No actual operational-state leaves are included in the RPD payload.

The missing information includes, where supported and applicable:

- TE policy operational state

- Candidate-path preference

- Candidate-path active and valid state

- Segment-list operational state and validity

- SID index and SID value

- Other RPD-originated candidate-path and segment-list state leaves

This behavior is identical in both tests:

- Dial-in: the subscription is established successfully and PFE counter data is received, but the RPD payload is empty.

- Dial-out: the device exports PFE and Junos native counter data successfully, but the RPD payload again contains timestamps only.

Expected Behavior

For an existing and operational SR-TE policy, the supported OpenConfig operational-state leaves under the subscribed te-policies root should be exported by RPD in both dial-in and dial-out modes.

Actual Behavior

PFE-originated policy keys and counters are exported, but the RPD-originated operational-state payload contains no state data. The issue is independent of whether dial-in or dial-out transport is used.

We observed same behaviour in lab as well.

There was one uncolored test tunnel in config. On removing the uncolored tunnel "srte-test" from lab, we are able to see all the required fields in output.

Engineering updated that uncolored tunnels are not supported for the subscription. The presence of this test tunnel was causing issue to other colored tunnels.

This will get fixed via PR 1978382.