Traffic Management: Ingress Rules

Endpoints

• Display ingress rules : GET /api2/tm/rulesets/<set_id>/ingress_rules viewer
  • Json structure
• Create new ingress rule : POST /api2/tm/rulesets/<set_id>/ingress_rules user
  • Json structure
• Edit ingress rule : PUT /api2/tm/rulesets/<set_id>/ingress_rules/<ingress_rule_id> user
  • Json structure
• Delete ingress rule : DELETE /api2/tm/rulesets/<set_id>/ingress_rules/<ingress_rule_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 Ingress Rule json structure

{
    "port":{"type":"INF", "id":1},
    "type":"ingress_vlan_strip",
    "data":{}
}

Data

Back to X2-SERIES API Home