Traffic Management: LAGs

Endpoints

• Display LAGs : GET /api2/tm/rulesets/<set_id>/lags/ viewer
  • Json structure
• Create new LAG : POST /api2/tm/rulesets/<set_id>/lags/ user
  • Json structure
• Display single LAG : GET /api2/tm/rulesets/<set_id>/lags/<LAG_id> viewer
  • Json structure
• Edit LAG : PUT /api2/tm/rulesets/<set_id>/lags/<LAG_id> user
  • Json structure
• Delete LAG : DELETE /api2/tm/rulesets/<set_id>/lags/<LAG_id> user

Dry-run preview

The mutation endpoints above accept 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

Display Rule json structure

{
    "id": 1,
    "set_id": 10,
    "name": "lag_name",
    "ports": [{"id":0, "type":"INF"}, ...],
}

Back to X2-SERIES API Home