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.
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
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
eRaclSize | platform:tcamRegionSize (scalar:Uint32) | Egress RACL TCAM region size | RANGE: [0 , 2147483647] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
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.
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
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
vpcConvergenceSize | platform:tcamRegionSize (scalar:Uint32) | VPC TCAM region size | RANGE: [0 , 2147483647] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
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.
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
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
ifaclLiteSize | platform:tcamRegionSize (scalar:Uint32) | Interface ACL Lite TCAM region size | RANGE: [0 , 2147483647] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring TCAM Region
Configuring TCAM Region
POST http://<mgmt0_IP>/api/node/mo/sys/pltfm/tcamRegion.json
{
"topSystem": {
"children": [
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"ifaclLiteSize": "0"
},
"children": [
{
"platformTcamRegionExtended": {
"attributes": {
"ingIpv6ifaclLiteSize": "0",
"ingRedirectSize": "0"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
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 ing-redirect
- hardware access-list tcam region ing-ifacl-ipv4-lite
- hardware access-list tcam region ing-ifacl-ipv6-lite
Note: The property information for this example was added in Release 10.4(2).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
TcamRegionExtended | sys/pltfm/tcamRegion |
TcamRegionExtended | sys/pltfm/tcamRegion/tcamregionextd |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Hardware Rate Limiter
Configuring Hardware Rate Limiter
POST http://<mgmt0_IP>/api/node/mo/sys/pltfm/tcamRegion.json
{
"platformRateLimiterMod": {
"attributes": {
"module": "1",
"ratenetflow": "999",
"ratessx": "888"
}
}
}
{
imdata:[]
}
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 rate-limiter layer-3 glean
- hardware rate-limiter layer-3 multicast local-groups
- hardware rate-limiter access-list-log
- hardware rate-limiter bfd
- hardware rate-limiter fex
- hardware rate-limiter span
- hardware rate-limiter sflow
- hardware rate-limiter vxlan-oam
- hardware rate-limiter 100M-Ethports
- hardware rate-limiter span-egress
- hardware rate-limiter DOT1X
- hardware rate-limiter mpls-oam
- hardware rate-limiter netflow
- hardware rate-limiter ssx
- hardware rate-limiter ucs-mgmt
- hardware rate-limiter mdns
Note: The property information for this example was added in Release 10.4(2).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformRateLimiterMod | sys/pltfm/ratelimitermod-1 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
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.
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
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
ipv6IfaclSize | platform:tcamRegionSize (scalar:Uint32) | IPv6 Interface ACL TCAM region size | RANGE: [0 , 2147483647] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
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.
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
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
eIpv6RaclSize | platform:tcamRegionSize (scalar:Uint32) | Egress IPv6 RACL TCAM region size | RANGE: [0 , 2147483647] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
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.
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
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
raclLiteSize | platform:tcamRegionSize (scalar:Uint32) | RACL TCAM region size | RANGE: [0 , 2147483647] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
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.
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
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
raclSize | platform:tcamRegionSize (scalar:Uint32) | RACL TCAM region size | RANGE: [0 , 2147483647] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
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.
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
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
qosSize | platform:tcamRegionSize (scalar:Uint32) | QOS TCAM region size | RANGE: [0 , 2147483647] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
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.
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
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
eVaclSize | platform:tcamRegionSize (scalar:Uint32) | Egress VACL TCAM region size | RANGE: [0 , 2147483647] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
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.
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
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
ifaclSize | platform:tcamRegionSize (scalar:Uint32) | Interface ACL TCAM region size | RANGE: [0 , 2147483647] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
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.
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
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
vaclSize | platform:tcamRegionSize (scalar:Uint32) | Virtual ACL TCAM region size | RANGE: [0 , 2147483647] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring a Default Template As Reference
Configuring a Default Template As Reference
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamTemplate": {
"attributes": {
"name": "SampleString_123",
"refTemplate": "l3"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<template-items>
<TcamTemplate-list>
<name>SampleString_123</name>
<refTemplate>l3</refTemplate>
</TcamTemplate-list>
</template-items>
</pltfm-items>
</System>
Note: This example was added in Release 9.3(3).
CLI Commands
The CLI commands are 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. Click the YANG tab to view the XML payload.
hardware profile tcam resource template SampleString_123 ref-template l3
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamTemplate | sys/pltfm/template-SampleString_123 |
platformTcamTemplate Properties
The following table contains information about the platformTcamTemplate properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | platform:TcamTemplateName (string:Basic) | Name of the user-defined tcam template | MAX SIZE: 40 |
refTemplate | platform:RefTemplate (scalar:Enum8) | Select a default template as reference | SELECTION: 0 - unspecified 1 - l3 2 - l2-l3 3 - nfe 4 - nfe2 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring TCP NAT Region Within NAT Region
Configuring TCP NAT Region Within NAT Region
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"tcpNatSize": "100"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<tcpNatSize>100</tcpNatSize>
</tcamRegion-items>
</pltfm-items>
</System>
Note: This example was added in Release 9.3(3).
CLI Commands
The CLI commands are 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. Click the YANG tab to view the XML payload.
hardware access-list tcam region tcp-nat 100
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
tcpNatSize | platform:TcpNatTcamRegionSize (scalar:Uint16) | TCP NAT TCAM region size | RANGE: [0 , 100] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting TCP NAT Region Within NAT Region
Deleting TCP NAT Region Within NAT Region
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamRegion": {
"attributes": {
"tcpNatSize": "0"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<tcamRegion-items>
<tcpNatSize>0</tcpNatSize>
</tcamRegion-items>
</pltfm-items>
</System>
Note: This example was added in Release 9.3(3).
CLI Commands
The CLI commands are 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. Click the YANG tab to view the XML payload.
no hardware access-list tcam region tcp-nat 100
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamRegion | sys/pltfm/tcamRegion |
platformTcamRegion Properties
The following table contains information about the platformTcamRegion properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
tcpNatSize | platform:TcpNatTcamRegionSize (scalar:Uint16) | TCP NAT TCAM region size | RANGE: [0 , 100] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring NFE2 TCAM Carving Parameters
Configuring NFE2 TCAM Carving Parameters
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformTcamTemplate": {
"attributes": {
"name": "SampleString_123",
"refTemplate": "nfe2"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<template-items>
<TcamTemplate-list>
<name>SampleString_123</name>
<refTemplate>nfe2</refTemplate>
</TcamTemplate-list>
</template-items>
</pltfm-items>
</System>
Note: This example was added in Release 9.3(3).
CLI Commands
The CLI commands are 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. Click the YANG tab to view the XML payload.
hardware profile tcam resource template SampleString_123 ref-template nfe2
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
platformEntity | sys/pltfm |
platformTcamTemplate | sys/pltfm/template-SampleString_123 |
platformTcamTemplate Properties
The following table contains information about the platformTcamTemplate properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | platform:TcamTemplateName (string:Basic) | Name of the user-defined tcam template | MAX SIZE: 40 |
refTemplate | platform:RefTemplate (scalar:Enum8) | Select a default template as reference | SELECTION: 0 - unspecified 1 - l3 2 - l2-l3 3 - nfe 4 - nfe2 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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: