Traffic Management: L4 Port Group

Endpoints

• Display l4 port groups : GET /api2/tm/rulesets/$/l4_port_group viewer
  • Json structure
• Display a specific l4 port group : GET /api2/tm/rulesets/$/l4_port_group/$ viewer
• Create new l4 port group : POST /api2/tm/rulesets/$/l4_port_group user
  • Json structure
• Edit l4 port group : PUT /api2/tm/rulesets/$/l4_port_group/$ user
  • Json structure
  • If the group is referenced by a rule in the active ruleset, the response also includes an nm_response field with the network module's redeployment result.
• Delete LAG : DELETE /api2/tm/rulesets/$/l4_port_group/$ user

Dry-run preview

PUT /api2/tm/rulesets/$/l4_port_group/$ accepts an optional ?dry_run=true query parameter. With the flag set, the handler runs all the same checks as the non-dry-run call but does not persist to the DAO and does not push to the network module. Returns 200 {} on success; error responses (status code and body) are identical to the non-dry-run call.

Json structures

L4 Port Group json structure

[
    {
        "id": 1,
        "name": "name",
        "set_id": 2,
        "type": "list",
        "data": {
            "values": [1, 2, 3]
        }
    }
]

or

[
    {
        "id": 1,
        "name": "name",
        "set_id": 2,
        "type": "range",
        "data": {
            "first": 100,
            "last": 200
        }
    }
]

Back to X2-SERIES API Home