Bug: Syncd failure when configuring SAI_QUEUE_STAT_BYTES on HFT #24351
Description
Is it platform specific
mellanox
Importance or Severity
Critical
Description of the bug
When using HFT to retrieve SAI_QUEUE_STAT_BYTES, SAI returns an error due to the fact that SAI_TAM_TEL_TYPE_ATTR_SWITCH_ENABLE_OUTPUT_QUEUE_STATS is not set to true.
Steps to Reproduce
- redis-cli -n 4 HSET "HIGH_FREQUENCY_TELEMETRY_GROUP|queue_profile|QUEUE" "object_names" "Ethernet16|0" "object_counters" "BYTES"
- redis-cli -n 4 HSET "HIGH_FREQUENCY_TELEMETRY_PROFILE|queue_profile" "poll_interval" "10000" "stream_state" "enabled"
Actual Behavior and Expected Behavior
BYTES counter should be configured with no errors
Relevant log output
2025 Oct 22 08:12:37.880271 r-sn5640-16 NOTICE syncd#SDK: [SAI_TAM.NOTICE] ./src/mlnx_sai_tam.c[4496]- mlnx_tam_tel_type_parse_attrs_and_prefill_db: Create TAM_TEL_TYPE: #0 TAM_TELEMETRY_TYPE=COUNTER_SUBSCRIPTION #1 SWITCH_ENABLE_PORT_STATS=true #2 SWITCH_ENABLE_PORT_STATS_INGRESS=true #3 SWITCH_ENABLE_PORT_STATS_EGRESS=true #4 SWITCH_ENABLE_MMU_STATS=true #5 MODE=SINGLE_TYPE #6 REPORT_ID=TAM_REPORT [OID:0x1600000049] [ID:0]
2025 Oct 22 08:12:37.880271 r-sn5640-16 NOTICE syncd#SDK: [SAI_TAM.NOTICE] ./src/mlnx_sai_tam.c[4412]- mlnx_create_tam_telemetry_type: Created TAM_TEL_TYPE [OID:0x140000004B] [ID:0]
2025 Oct 22 08:12:37.883089 r-sn5640-16 NOTICE syncd#SDK: [SAI_UTILS.NOTICE] ./src/mlnx_sai_utils.c[2047]- set_dispatch_attrib_handler: Set TAM_TYPE_LIST, key:TAM_TELEMETRY [OID:0x120000004D] [ID:0], val:1 : [ 0x140000004B]
2025 Oct 22 08:12:37.891475 r-sn5640-16 NOTICE syncd#SDK: [SAI_TAM.NOTICE] ./src/mlnx_sai_tam.c[3038]- mlnx_tam_cs_parse_attrs_and_prefill_db: Create TAM_COUNTER_SUBSCRIPTION: #0 TEL_TYPE=TAM_TEL_TYPE [OID:0x140000004B] [ID:0] #1 OBJECT_ID=QUEUE [OID:0x101F900000015] [log_port:0x101F9, index:0] #2 STAT_ID=1 #3 LABEL=1 #4 STATS_MODE=READ
2025 Oct 22 08:12:37.891486 r-sn5640-16 ERR syncd#SDK: [SAI_TAM.ERR] ./src/mlnx_sai_tam.c[3150]- mlnx_tam_cs_validate: TAM_TEL_TYPE output queue stats are not enabled.
2025 Oct 22 08:12:37.891486 r-sn5640-16 ERR syncd#SDK: [SAI_TAM.ERR] ./src/mlnx_sai_tam.c[3082]- mlnx_tam_cs_apply: Failed to validate TAM_CS.
2025 Oct 22 08:12:37.891505 r-sn5640-16 ERR syncd#SDK: [SAI_TAM.ERR] ./src/mlnx_sai_tam.c[2782]- mlnx_create_tam_counter_subscription: Failed to apply configuration.
2025 Oct 22 08:12:37.891505 r-sn5640-16 ERR syncd#SDK: :- sendApiResponse: api SAI_COMMON_API_CREATE failed in syncd mode: SAI_STATUS_FAILURE
2025 Oct 22 08:12:37.892059 r-sn5640-16 ERR syncd#SDK: :- processQuadEvent: attr: SAI_TAM_COUNTER_SUBSCRIPTION_ATTR_TEL_TYPE: oid:0x4b000000005ac8
2025 Oct 22 08:12:37.892059 r-sn5640-16 ERR syncd#SDK: :- processQuadEvent: attr: SAI_TAM_COUNTER_SUBSCRIPTION_ATTR_OBJECT_ID: oid:0x150000000004ad
2025 Oct 22 08:12:37.892080 r-sn5640-16 ERR syncd#SDK: :- processQuadEvent: attr: SAI_TAM_COUNTER_SUBSCRIPTION_ATTR_STAT_ID: 1
2025 Oct 22 08:12:37.892080 r-sn5640-16 ERR syncd#SDK: :- processQuadEvent: attr: SAI_TAM_COUNTER_SUBSCRIPTION_ATTR_LABEL: 1
2025 Oct 22 08:12:37.892087 r-sn5640-16 ERR syncd#SDK: :- processQuadEvent: attr: SAI_TAM_COUNTER_SUBSCRIPTION_ATTR_STATS_MODE: SAI_STATS_MODE_READ
2025 Oct 22 08:12:37.892802 r-sn5640-16 WARNING swss#orchagent: :- handleSaiCreateStatus: SAI_STATUS_SUCCESS is not expected in handleSaiCreateStatus
2025 Oct 22 08:12:37.892802 r-sn5640-16 ERR swss#orchagent: :- create: create status: SAI_STATUS_FAILURE
2025 Oct 22 08:12:37.892802 r-sn5640-16 ERR swss#orchagent: :- handleSaiCreateStatus: Encountered failure in create operation, exiting orchagent, SAI API: SAI_API_TAM, status: SAI_STATUS_FAILURE
2025 Oct 22 08:12:37.892802 r-sn5640-16 NOTICE swss#orchagent: :- notifySyncd: sending syncd: SYNCD_INVOKE_DUMP
2025 Oct 22 08:12:37.894075 r-sn5640-16 NOTICE syncd#SDK: :- processNotifySyncd: Invoking SAI failure dumpOutput of show version, show techsupport
Attach files (if any)
No response