05-24-2022 01:32 PM
Hello dear Genius community members,
C9300 can function like a L3 device (as flat ip router or mpls PE). Per the datasheet it can handle at least 32.000 routes (24.000 direct routes + 8.000 indirect routes). Unfortunately when reaching around 7.000 routes (direct+indirect) we experience some forwarding issues related with logging messages like lake of resources. We did suspect TCAM overflow that has been confirmed by Cisco TAC. The only workaround is to make routes summarization in order to lower routing table. My thoughts is that indication from datasheet is a bit diffrent than the reality. Did someone face an issue like this?
Solved! Go to Solution.
05-27-2022 02:25 AM
Thanks to all of you for the links provided. I have already seen all of them when i was troubleshooting my issues and how to overcome it. As i said before, things are like all information going to hardware limitations like Cisco told us. The oak of solution is to lower down vpnv4 prefixes by aggregate them. I have already tested on one PE and the TCAM went lower than before.
05-24-2022 01:57 PM
1-TCAM is HW and have specific size, BUT there is something called SDM template,
where some costumer use template for MAC or unicast or net flow,
2- One route not meaning it allocate one TCAM spaces, the algorithm is complex as cisco mention in below statement.
In the example, the IP indirectly-connected routes resource is full even though the output shows only 2047 of 2048 maximum as in use.
05-24-2022 02:15 PM
Thanks for your quick feedback.
We already tried SDM option but Only 2 template are available: Access and NAT.
The walue are almost the same apart QOS and PBR row.
If we could get the cli to decrease MAC's room and increase Unicast'one.
As i understood it is a hardware limitations. No way to give more room even if we purchase a license.
05-24-2022 02:23 PM
Yes it hardware limitations and license do not give more room.
05-24-2022 11:24 PM
- You may look at this command (if available) hardware access-list tcam region ? , look at the available options.
M.
05-25-2022 06:03 AM
Hello marce1000, But it seems that the command is related to Nexus hardware. My limitation is on catalyst 9300.
By the way thanks for all.
05-25-2022 10:18 AM
- FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvg60292
You may also find this document useful : https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9500-series-switches/217703-understand-hardware-resources-on-catalys.html
M.
05-25-2022 12:57 PM
check this doc. at it end some detail bout TCAM utilize.
05-27-2022 02:25 AM
Thanks to all of you for the links provided. I have already seen all of them when i was troubleshooting my issues and how to overcome it. As i said before, things are like all information going to hardware limitations like Cisco told us. The oak of solution is to lower down vpnv4 prefixes by aggregate them. I have already tested on one PE and the TCAM went lower than before.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide