Re: [f-nsp] CER: IPv6 Route ADD: CAM entry creation FAILED
Youssef Bengelloun-Zahr <[email protected]> Wed, 6 Sep 2017 21:45:42 +0200
| Newsgroups | gmane.network.nsp.foundry |
|---|---|
| Message-ID | <[email protected]> |
Been there, suffer from it everyday. They might not have CAM profiles ala MLXe, but they still have CAMs... so they have limited and counted ressources. Best regards. > Le 6 sept. 2017 à 21:37, Brian Rak <[email protected]> a écrit : > > CER's don't have CAM profiles. From the information I can find, they don't actually use TCAM anyway. > >> On 9/6/2017 3:32 PM, Derek wrote: >> Did you check the CAM utilization? It's probably full, perhaps you can partition it differently. >> >>> On Wed, Sep 6, 2017 at 2:30 PM, Brian Rak <[email protected]> wrote: >>> Has anyone else seem problems with the CER's being unable to add routes before? We have multiple devices (all 2024C-4X) reporting one or both of these messages: >>> >>> IPv6 Route ADD: CAM entry creation FAILED >>> IPv4 Network Route ADD: CAM entry creation FAILED >>> >>> They're learning a full v4+v6 table, but we are well below the limits defined in `sh default values`. From past experience, a reload seems to be the only thing that will actually correct this, but that is a pretty annoying thing to have to do. >>> >>> Any ideas for what may be causing this? We're on 5.6.0m right now. >>> >>> _______________________________________________ >>> foundry-nsp mailing list >>> [email protected] >>> http://puck.nether.net/mailman/listinfo/foundry-nsp >> >> >> >> -- >> Be Well, >> >> Derek Labian > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp