That is my experience too. My understanding is that the exception recovery requires a reload. Router says otherwise:
RTR-1#sh log | i exception|EXCEPTION Jun 3 22:59:26.790 UTC: %MLSCEF-SP-4-FIB_EXCEPTION_THRESHOLD: Hardware CEF entry usage is at 95% capacity for MPLS protocol. Jun 3 23:00:02.414 UTC: %C6K_MPLS_LC-SP-5-TCAM_EXCEPTION: TCAM exception occured for MPLS, traffic will be software switched Jun 3 23:15:02.712 UTC: %C6K_MPLS_LC-SP-5-TCAMEXPRECOVER: TCAM exception recovered for MPLS, traffic will be hardware switched RTR-1#sh mls cef exception status detail Current IPv4 FIB exception state = FALSE Current IPv6 FIB exception state = FALSE *Current MPLS FIB exception state = FALSE* #IPv4 excep notified = 0 #IPv6 excep notified = 0 *#MPLS excep notified = 1* #IPv4 reloads done = 0 #IPv6 reloads done = 0 *#MPLS reloads done = 1* #Timer expired = 3 Timer poll period(sec) = 300 ERM timer running = FALSE Num. of ERM msgs = 1 Num. of ERM bool events = 1 On Wed, Jun 4, 2014 at 12:21 PM, Nick Hilliard <[email protected]> wrote: > On 04/06/2014 16:39, Antonio Soares wrote: > > Usually it doesn't recover by itself > > there's no "usually" - this is an unrecoverable problem and the only option > is to reboot. > > Nick > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > -- Tim:> _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
