Skip to content

how would one define a underlay route that will do hair-pinning ? #405

@mgheorghe

Description

@mgheorghe

lets take the scenario with a DPU with 8 ports 8x25G, or 8x50G or 8x100G fanout or anything with more than 1 port.

if SAI_ROUTE_ENTRY_ATTR_NEXT_HOP_ID is SAI_NULL_OBJECT_ID we hairpin if it is defined we respect it ?

    {
        "name": "default_route",
        "op": "create",
        "type": "SAI_OBJECT_TYPE_ROUTE_ENTRY",
        "key": {
            "switch_id": "$SWITCH_ID",
            "vr_id": "$VR_ID",
            "destination": "0.0.0.0/0"
        },
        "attributes": [
            "SAI_ROUTE_ENTRY_ATTR_NEXT_HOP_ID",
            "SAI_NULL_OBJECT_ID"
        ]
    }

if we specify port 3, 7 ... we respect the route

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions