Configuring TCAM
Ternary content-addressable memory (TCAM) is a type of high-speed memory that can be entirely searched in a single clock cycle. The term “ternary” refers to the memory's ability to store and query data using three different inputs: 0, 1 and X.
The TCAM stores access control-lists (ACLs) which are ordered sets of rules that you can use to filter your network traffic. Each rule specifies a set of conditions that a packet must satisfy to match the rule. When the device determines that an ACL applies to a packet, it tests the packet against the conditions of all rules. The first matching rule determines whether the packet is permitted or denied. If there is no match, the device applies the applicable implicit rule. The device continues processing packets that are permitted and drops packets that are denied. The egress TCAM size is 1K, divided into four 256 entries.
TCAM space is limited. The choice for what is best for your implementation depends on the specific use.
By default, all TCAM space is already allocated, so you need to decide where you want to 'steal' TCAM space from in order to allocate elsewhere.
Configuring ACL TCAM Region with e-racl TCAM Carving
Configuring ACL TCAM Region with e-racl TCAM Carving
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"eRaclSize": "256"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<eRaclSize>256</eRaclSize>
</tcamRegion-items>
</pltfm-items>
</System>
Configures the size of the IPv4 egress router ACL (ERACL) TCAM region.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware access-list tcam region e-racl 256
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring ACL TCAM Region with vpc-convergence TCAM Carving
Configuring ACL TCAM Region with vpc-convergence TCAM Carving
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"vpcConvergenceSize": "0"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<vpcConvergenceSize>0</vpcConvergenceSize>
</tcamRegion-items>
</pltfm-items>
</System>
Configures the size of the vPC convergence TCAM region.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware access-list tcam region vpc-convergence 0
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring ACL TCAM Region with racl-lite TCAM Carving
Configuring ACL TCAM Region with racl-lite TCAM Carving
POST http://<mgmt0_IP>/api/node/mo/sys/pltfm/tcamRegion.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"ifaclLiteSize": "256"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<eRaclSize>256</eRaclSize>
</tcamRegion-items>
</pltfm-items>
</System>
Configures the size of the IPv4 RACL lite TCAM region.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware access-list tcam region racl-lite 256
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring ACL TCAM Region with ipv6-ifacl TCAM Carving
Configuring ACL TCAM Region with ipv6-ifacl TCAM Carving
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"ipv6IfaclSize": "256"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<ipv6IfaclSize>256</ipv6IfaclSize>
</tcamRegion-items>
</pltfm-items>
</System>
Configures the size of the IPv6 port ACL TCAM region.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware access-list tcam region ipv6-ifacl 256
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring ACL TCAM Region Size with e-ipv6-racl TCAM Carving
Configuring ACL TCAM Region Size with e-ipv6-racl TCAM Carving
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"eIpv6RaclSize": "256"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<eIpv6RaclSize>256</eIpv6RaclSize>
</tcamRegion-items>
</pltfm-items>
</System>
Configures the size of the IPv6 egress router ACL (ERACL) TCAM region.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware access-list tcam region e-ipv6-racl 256
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring ACL TCAM Region with ifacl-lite TCAM Region Size
Configuring ACL TCAM Region with ifacl-lite TCAM Region Size
POST http://<mgmt0_IP>/api/node/mo/sys/pltfm/tcamRegion.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"raclLiteSize": "256"
}}}]}}
{
imdata:[]
}
Configures the size of the IPv4 port ACL lite TCAM region.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right.
hardware access-list tcam region ifacl-lite 256
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Max-Host Routing Mode
Configuring Max-Host Routing Mode
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"platformEntity": {
"attributes": {
"routingMode": "TOR_MAX_L3"
}
}
}
]
}
}
{
imdata:[]
}
<System>
<pltfm-items>
<routingMode>TOR_MAX_L3</routingMode>
</pltfm-items>
</System>
Puts the line cards in Broadcom T2 mode 2 and the fabric modules in Broadcom T2 mode 3 to increase the number of supported hosts.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
system routing max-mode l3
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring ALPM for IPv6
Configuring ALPM for IPv6
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"platformEntity": {
"attributes": {
"IPV6alpmCarveValue": "4096"
}
}
}
]
}
}
{
imdata:[]
}
<System>
<pltfm-items>
<IPV6alpmCarveValue>4096</IPV6alpmCarveValue>
</pltfm-items>
</System>
Enables /128 IPv6 routes and carves the LPM table for all IPv6 entries.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware profile ipv6 alpm carve-value 4096
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Enabling the SCP Server
Enabling the SCP Server
POST http://<mgmt0_IP>/api/mo/sys/fm.json
{
"fmEntity": {
"children": [
{
"fmScpServer": {
"attributes": {
"adminSt": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<fm-items>
<scpserver-items>
<adminSt>enabled</adminSt>
</scpserver-items>
</fm-items>
</System>
Enables the scp-server feature.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
feature scp-server
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring anycast gateway MAC
Configuring anycast gateway MAC
POST http://<mgmt0_IP>/api/mo/sys/hmm.json
{
"hmmEntity": {
"children": [
{
"hmmFwdInst": {
"attributes": {
"amac": "CA:BB:D3:69:0C:60"
}}}]}}
{
imdata:[]
}
<System>
<hmm-items>
<fwdinst-items>
<amac>CA:BB:D3:69:0C:60</amac>
</fwdinst-items>
</hmm-items>
</System>
Configures anycast gateway MAC of the switch.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
fabric forwarding anycast-gateway-mac cabb.d369.0c60
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring description for VRF
Configuring description for VRF
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"l3Inst": {
"attributes": {
"descr": "Default VRF for user L3 routing shutdown",
"name": "switchpool-default"
}
}
}
]
}
}
{
imdata:[]
}
<System>
<inst-items>
<Inst-list>
<name>switchpool-default</name>
<descr>Default VRF for user L3 routing shutdown</descr>
</Inst-list>
</inst-items>
</System>
Creates a description of the VRF.
Note: This example was added in Release 7.0(3)I6(1).
CLI Commands
The CLI commands and options listed below are the equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
vrf context switchpool-default
description Default VRF for user L3 routing shutdown
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring MOTD Banner
Configuring MOTD Banner
POST http://<mgmt0_IP>/api/mo/sys/userext.json
{
"aaaUserEp": {
"children": [
{
"aaaPreLoginBanner": {
"attributes": {
"delimiter": "_",
"message": ""
}}}]}}
{
imdata:[]
}
<System>
<userext-items>
<preloginbanner-items>
<delimiter>_</delimiter>
<message></message>
</preloginbanner-items>
</userext-items>
</System>
Configures the MOTB (message-of-the-day) banner.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
banner motd __
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring BFD Interval
Configuring BFD Interval
POST http://<mgmt0_IP>/api/mo/sys/bfd/inst/if-{[id]}.json
{
"bfdIf": {
"attributes": {
"id": "eth1/1"
},
"children": [
{
"bfdKaP": {
"attributes": {
"detectMult": "3",
"minRxIntvl": "50",
"minTxIntvl": "50"
}}}]}}
{
imdata:[]
}
<System>
<bfd-items>
<inst-items>
<if-items>
<If-list>
<id>eth1/1</id>
<ka-items>
<detectMult>3</detectMult>
<minRxIntvl>50</minRxIntvl>
<minTxIntvl>50</minTxIntvl>
</ka-items>
</If-list>
</if-items>
</inst-items>
</bfd-items>
</System>
Configures the BFD session parameters for all BFD sessions on the device. This command overrides these values by configuring the BFD session parameters on an interface.
Note: This example was added in Release 7.0(3)I6(1).
CLI Commands
The CLI commands and options listed below are the equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
interface ethernet1/1
bfd interval 50 min_rx 50 multiplier 3
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Hardware Profile racl TCAM Region Size
Configuring Hardware Profile racl TCAM Region Size
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"raclSize": "3072"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<raclSize>3072</raclSize>
</tcamRegion-items>
</pltfm-items>
</System>
Configures the size of the router ACL (RACL) TCAM region.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware profile tcam region racl 3072
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Hardware Profile QoS TCAM Region Size
Configuring Hardware Profile QoS TCAM Region Size
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"qosSize": "256"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<qosSize>256</qosSize>
</tcamRegion-items>
</pltfm-items>
</System>
Configures the size of the quality of service (QoS) TCAM region.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware profile tcam region qos 256
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Hardware Profile e-vacl TCAM Region Size
Configuring Hardware Profile e-vacl TCAM Region Size
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"eVaclSize": "0"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<eVaclSize>0</eVaclSize>
</tcamRegion-items>
</pltfm-items>
</System>
Configures the size of the egress VLAN ACL (EVACL) TCAM region.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware profile tcam region e-vacl 0
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Hardware Profile ifacl TCAM Region Size
Configuring Hardware Profile ifacl TCAM Region Size
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"ifaclSize": "0"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<ifaclSize>0</ifaclSize>
</tcamRegion-items>
</pltfm-items>
</System>
Configures the size of the interface ACL (ifacl) TCAM region.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware profile tcam region ifacl 0
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Hardware Profile vacl TCAM Region Size
The following is an example of configuring the vacl TCAM region in the hardware.
Configuring Hardware Profile vacl TCAM Region Size
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"vaclSize": "0"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<vaclSize>0</vaclSize>
</tcamRegion-items>
</pltfm-items>
</System>
Configures the size of the VLAN ACL (VACL) TCAM region.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware profile tcam region vacl 0
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Hardware QoS Min-buffer
Configuring Hardware QoS Min-buffer
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"platformEntity": {
"attributes": {
"qosMinBuffer": "default"
}
}
}
]
}
}
{
imdata:[]
}
<System>
<pltfm-items>
<qosMinBuffer>default</qosMinBuffer>
</pltfm-items>
</System>
Configures the QoS buffer.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
hardware qos min-buffer qos-group default
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Disabling URPF (Unicast Reverse Path Forwarding)
The following is an example of (global) disabling Unicast Reverse Path Forwarding (URPF).
Disabling URPF (Unicast Reverse Path Forwarding)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"platformEntity": {
"attributes": {
"urpfStatus": "disabled"
}
}
}
]
}
}
{
imdata:[]
}
<System>
<pltfm-items>
<urpfStatus>disabled</urpfStatus>
</pltfm-items>
</System>
Globally disables URPF.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
system urpf disable
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Logging Level to Match Entries in ACL Log
Configuring Logging Level to Match Entries in ACL Log
POST http://<mgmt0_IP>/api/mo/sys.json
{
"acllogInst": {
"children": [
{
"acllogLogCache": {
"attributes": {
"matchLevel": "6"
}}}]}}
{
imdata:[]
}
<System>
<acllog-items>
<inst-items>
<log-items>
<matchLevel>6</matchLevel>
</log-items>
</inst-items>
</acllog-items>
</System>
Specifies the minimum severity level to log ACL matches. The default is 6 (informational). The range is from 0 (emergency) to 7 (debugging).
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
acllog match-log-level 6
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring TFTP Source Interface
Configuring TFTP Source Interface
POST http://<mgmt0_IP>/api/mo/sys/ipSrcIf.json
{
"srcintfEntity": {
"children": [
{
"srcintfTftp": {
"attributes": {
"srcIf": "po4",
"vrf": "default"
}}}]}}
{
imdata:[]
}
<System>
<ipSrcIf-items>
<tftp-items>
<Tftp-list>
<vrf>default</vrf>
<srcIf>po4</srcIf>
</Tftp-list>
</tftp-items>
</ipSrcIf-items>
</System>
Configures the source interface for all TFTP packets.
Note: This example was added in Release 7.0(3)I6(1).
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.
ip tftp source-interface po4 vrf default
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html