Closed viniarck closed 1 year ago
PUT /trace is always requiring dl_vlan in the body, which can turn into an issue if you're trying to trace a port-based circuit, for instance this payload isn't considered valid:
PUT /trace
dl_vlan
{ "trace": { "switch": { "dpid": "00:00:00:00:00:00:00:01", "in_port": 1 }, "eth": {} } }
{ "result": { "error": "Error: dl_vlan not provided" } }
But, in practice it should work, if you're trying to trace this port-based circuit:
{ "request": { "trace": { "eth": {}, "switch": { "dpid": "00:00:00:00:00:00:00:01", "in_port": 1 } } }, "request_id": 30002, "result": [ { "dpid": "00:00:00:00:00:00:00:01", "port": 1, "time": "2022-02-14 18:24:11.854740", "type": "starting" }, { "dpid": "00:00:00:00:00:00:00:02", "port": 2, "time": "0:00:00.509496", "type": "trace" }, { "dpid": "00:00:00:00:00:00:00:03", "port": 2, "time": "0:00:01.019950", "type": "trace" }, { "msg": "none", "reason": "done", "time": "0:00:02.534195", "type": "last" } ], "start_time": "2022-02-14 18:24:11.854740", "total_time": "0:00:02.534750" }
PUT /trace
is always requiringdl_vlan
in the body, which can turn into an issue if you're trying to trace a port-based circuit, for instance this payload isn't considered valid:But, in practice it should work, if you're trying to trace this port-based circuit: