There seems to be some discrepancy on Number of Supported Route Entries, by Platform
section for Broadcom Trident switches. The docs here show a max of 128K IPv4 or 20K IPv6. Some switch vendor docs, e.g. the edge-core AS6701-32X (data sheet
) with a BCM56850 Trident II shows 64K IPv4 routes and 20K IPv6 routes, so fewer IPv4 routes than the Cumulus docs. Other Trident II switches, e.g. the edge-core AS6712-32X (data sheet
), also with a BCM56850 Trident II (though with an Intel Atom rather than Freescale CPU) get more complicated, showing:
- 16K IPv4 routes (LPM) in TCAM
- 112K max. host entries
- 8K IPv6 routes (LPM) in TCAM
- 56K max. host entries
This seems to be regarding a Broadcom feature in Trident II and up that can keep host routes in CAM rather than TCAM (UFT?). If we take those IPv4 LPM and host entries combined we get 128K, like the Cumulus docs , but the combined IPv6 LPM and host routes add up to 64K, which is much higher than the 20K listed in the Cumulus docs.
Any guidance on which info is correct (as there even seems to be conflict between data sheets of the two different edge-core switches both using a BCM56850 Trident II chipset)? Aside from the CAM-carving profiles described here, can Cumulus take advantage of UFT?
Also: I'm assuming that the exact match routing in UFT applies to any /32 or /128 routes, not just direct adjacencies. As an example: In a container deployment in a regular routed/L3 container using something like calico, a /32 and/or /128 route is advertised per container. Am I correct in saying that those /32 and /128 routes should fit in the CAM via UFT rather than going into the more limited TCAM using longest prefix matching (LPM)?