Posted on December 21, 2020 4:42 am
 |  Asked by Dan Feldman
Print Friendly, PDF & Email

LAB-7150-2#sh ver
Arista DCS-7150S-52-CL-R
Hardware version: 22.04
Serial number: SSJ164xxxxxx
System MAC address: 444c.xxxxxxxxx

Software image version: 4.19.1F-2GB
Architecture: i386
Internal build version: 4.19.1F-2GB-6161937.4191F
Internal build ID: 1b0d0992-c711-4eff-920a-491b86e84af1

Uptime: 4 weeks, 0 days, 10 hours and 44 minutes
Total memory: 3963676 kB
Free memory: 2237908 kB

LAB-7150-2#sh platform fm6000 tcam allocation
Switch: 0
IPv4 unicast: 23:23
IPv4 multicast: 6:23
IPv6 unicast: 6:23
IPv6 multicast: -1:-1
ACL: -1:-1

LAB-7150-2#sh ip access-lists | wc -l

^^ I have applied a lot of access-lists to this switch but the TCAM usage does not seem to show an increase in usage?
Is the eos we are running “post-embargo” code which works with drop tcam ACLs or do we need to upgrade ?

Posted by Aniket Bhowmick
Answered on December 21, 2020 8:52 am

Hi Dan,

The EOS-image 4.19.1F-2GB doesn't support the drop ACL rule in TCAM and Copp too. To use the ACL in TCAM feature, you need to upgrade the switch to an EOS image from where it is supported..

Please check the following Field Notice which describes the EOS images from where ACLs in TCAMs were reintroduced (along with Copp) :

You can upgrade to EOS-4.19.4M image (as per your current train) where it is supported.

Let us know if you have any query.

Thanks !



Posted by Marc Cox
Answered on January 11, 2021 5:45 am
While this platform is not officially monitored by Arista Networks, Arista affiliated persons, including Arista employees, does 4.19.1F-2GB on Arista DCS-7150S-52-CL-R Hardware version: 22.04 work with DROP ACL in tcam?

Post your Answer

You must be logged in to post an answer.