ASR 1K Error - %PLATFORM-3-ELEMENT_CRITICAL: R0/0: smand: RP/0: Committe d Memory value 98% exceeds critical level 95%

[morris.villa]

Hi.

Approximately every month the ASR 1K freezes and the traffic stops to pass and some logs appear. Logs below are presenting in console:

Dec 21 22:47:07 COL: %PLATFORM-3-ELEMENT_CRITICAL: R0/0: smand:  RP/0: Committed Memory value 98% exceeds critical level 95%

.Dec 21 22:48:15 COL: %ASR1000_RP_SPA-4-IFCFG_CMD_TIMEOUT: Interface configuration command (0xF) to slot 0/0 timed out

-Traceback= 1#a97a59dd5e49e95772aee50db0dd88fc  :400000+6BF203 :400000+2BD45BC :

400000+2BD4E04 :400000+43ED561 :400000+43EC76D :400000+43E884C :400000+43F1BCC :

400000+43F1ADF

.Dec 21 22:49:15 COL: %ASR1000_RP_SPA-4-IFCFG_CMD_TIMEOUT: Interface configuration command (0xF) to slot 0/0 timed out

-Traceback= 1#a97a59dd5e49e95772aee50db0dd88fc  :400000+6BF203 :400000+2BD45BC :

400000+2BD4E04 :400000+43ED561 :400000+43EC76D :400000+43E884C :400000+43F1BCC :

400000+43F1ADF

Do you have any idea of a workaround for this case ?

The ASR version is 12.2(33)XNE1.

Thanks.

[nkarpysh]

Hi,

This seems to be this DDTS :

CSCtc21042  cman_fp crashes on ASR RP2

    Symptom:

     Chassis-manager process on RP2 gets stuck and router becomes unresponsive to

     user commands. All the FPs and CCs keep rebooting, with console logs showing

     repeated FP code downloads.

     This problem is specific to RP2.

    Conditions:

     No particular scenario is known. Problem is caused by OBFL logging of messages

     on RP2.

    Workaround:

     Following workaround greatly reduces the probability of this

     issue occurring again, but does not completely eliminate it.

     Disable onboard logging of messages on RPs as follows:

      "hw-module slot r0/r1 logging onbaord disable"

     Router#hw-module slot r0 logging onboard disable

     To verify that onboard logging has been disabled:

      Router#sh logging onboard slot r0 status        

      Status: Disabled

     Note that this command is not saved in the config so is not preserved

     across router reloads.

Please consider the workaround above and also upgrade in future as DDTS not fixed in your OS. It is fixed in 12.2(33)XNF 12.2(33)XNE02 12.2(33)XND03

BTW you can also open a TAC case to confirm this and get more specific recomendations. That also would be useful for tracking purposes.

Hope this helps.

Nik

[morris.villa]

Hi Nikolay.

Thanks for your feedback !

I ´ll do the workaround right now to see the behavior.

Regards.

[nkarpysh]

Hi Morris,

If that will work you can close this thread marking as a right answwer for it to be usefull in future.

Thanks,