PUT /api2/tm/ user
GET /api2/tm/ viewer
POST /api2/tm/rulesets/$/clone user
{
"active_ruleset": 5
}{
"active_ruleset": null,
"state": {
"rule_counters": [],
"resource_use": 0,
"resource_use_entries": 0,
"ingress_resource_use": 0,
"ingress_resource_use_entries": 0,
"ptp_state": {
"active": true,
"ptp_master_mac": "aa:aa:aa:aa:aa:aa",
"ptp_master_ip": "10.10.10.33",
"clock_offset": 0,
"path_delay": 0,
"time_sync": 1231231231,
"clk_id": 12312,
"sync_state": "sync_freerun"
}
},
"available_filters": {
"vlan_group": true,
"ipv4_fragments": false,
"l4_group": true,
"configurable_filters": true
},
"available_actions": [
"drop",
"vlan_tag",
"vlan_strip",
"slicing",
"gtp_ip_drop",
"gtp_ip6_drop",
"gtp_ip_allow",
"gtp_ip6_allow",
"erspan_strip",
"erspan_tunnel",
"vxlan_strip",
"mpls_strip"
],
"available_ingress_actions": [
"ingress_vlan_tag",
"ingress_vlan_strip"
],
"available_time_port": false,
"available_deduplication": false,
"family": "x2",
"max_ingress_vlan_tag_id": 4035,
"max_resource_entries": 511,
"max_ingress_resource_entries": 0
}The state.resource_use* fields report the live hardware TCAM usage of the active ruleset. Predicted per-ruleset values (what a ruleset would consume if activated) are available on the Rule-Set endpoints.