Skip to content

[acl] PACKET_COLOR_ACTION (SAI_ACL_ENTRY_ATTR_ACTION_SET_PACKET_COLOR) not supported in the generic CONFIG_DB ACL pipeline #4716

Description

@AnantKishorSharma

Description

The SAI ACL entry action SAI_ACL_ENTRY_ATTR_ACTION_SET_PACKET_COLOR (set a packet's color to GREEN/YELLOW/RED) is only reachable today through the P4Orch/P4RT path (orchagent/p4orch/). The standard CONFIG_DB AclOrch pipeline has no mapping for it, so a CONFIG_DB ACL rule cannot set packet color even on platforms whose SAI advertises the action.

Steps to reproduce

Define a custom ACL_TABLE_TYPE whose ACTIONS should set packet color, and an ACL_RULE using it. There is no recognized CONFIG_DB action string, so AclOrch never programs SAI_ACL_ENTRY_ATTR_ACTION_SET_PACKET_COLOR.

Expected behavior

A CONFIG_DB ACL rule action (PACKET_COLOR_ACTION = GREEN/YELLOW/RED) maps to SAI_ACL_ENTRY_ATTR_ACTION_SET_PACKET_COLOR, gated by the platform's queried ACL action capability (so platforms that do not support it simply reject the table, no behavior change for anyone else).

Notes

Verified on Broadcom TH5 (SAI advertises SET_PACKET_COLOR on ingress): the rule programs the action in ASIC_DB and the corresponding field-processor action in hardware. Correctly capability-gated on platforms that do not advertise it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions