Hello All,   I have a bunch of ASR901, and one of them got stuck, showing the following message in console:   pura_proc_mem_alloc:323:allocation failed pura_proc_mem_alloc:323:allocation failed pura_proc_mem_alloc:323:allocation failed pura_proc_mem_alloc:323:allocation failed pura_proc_mem_alloc:323:allocation failed pura_proc_mem_alloc:323:allocation failed pura_proc_mem_alloc:323:allocation failed   %% Low on memory; try again later   %% Low on memory; try again later   After reload, it show a message showing that the firmware was about to upgrade, it crashed and booted OK:   [MCU] Running version 01.16.04(15) [MCU] Running version 04.15 [MCU] New version is 05.04 [MCU] Firmware upgrade in progress...   Right now everything looks OK! Can anyone help me understand what append?   Thanks, Pedro ... View more

Hi, when configuring a policy-map in a ASR901 running 15.4(2)S2, I got the following messages: 000674: Jan 15 11:06:54.111 AST:  Data Qualify failed (2):Entry not found 000675: Jan 15 11:06:54.111 AST:  Error in programming Exp:Entry not found 000676: Jan 15 11:06:54.111 AST:  Error in configuring Policy-map 000677: Jan 15 11:06:54.115 AST:  Data Qualify failed (2):Entry not found 000678: Jan 15 11:06:54.115 AST:  Error in programming Exp:Entry not found 000679: Jan 15 11:06:54.115 AST:  Error in configuring Policy-map 000680: Jan 15 11:06:54.123 AST:  Data Qualify failed (2):Entry not found 000681: Jan 15 11:06:54.123 AST:  Error in programming Exp:Entry not found 000682: Jan 15 11:06:54.123 AST:  Error in configuring Policy-map 000683: Jan 15 11:06:54.127 AST:  Data Qualify failed (2):Entry not found 000684: Jan 15 11:06:54.127 AST:  Error in programming Exp:Entry not found 000685: Jan 15 11:06:54.127 AST:  Error in configuring Policy-map 000686: Jan 15 11:06:54.131 AST:  Data Qualify failed (2):Entry not found 000687: Jan 15 11:06:54.131 AST:  Error in programming Exp:Entry not found 000688: Jan 15 11:06:54.131 AST:  Error in configuring Policy-map Apparently everything is OK, as I see the traffic being correctly classified, but I would like to understand why am I getting these messages.   Thanks, Pedro ... View more

Hello All, We are doing some scalability tests with the new typhoon based hardware (24 x 10G - SE), and when configuring sub-interfaces with a egress service-policy applied got the following error message: % Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed' from this session to view the errors RP/0/RSP0/CPU0:A9K-LAB05(config-subif)#show configuration failed Fri Jul 11 09:44:59.268 WEST !! SEMANTIC ERRORS: This configuration was rejected by !! the system due to semantic errors. The individual !! errors with each failed configuration command can be !! found below. interface TenGigE0/2/0/5.43947  service-policy input SCH_IN_parent_L3_NG1_100M !!% 'prm_server' detected the 'warning' condition 'An operation that was requested was aborted - data integrity may be compromised.' ! end Service policy configuration is the following: policy-map SCH_OUT_parent_L3_NG1_100M  class class-default   service-policy SCH_OUT_child_L3_NG1_100M   shape average 100032 kbps  end-policy-map ! policy-map SCH_OUT_child_L3_NG1_100M  class EDGE-L3-VOICE   priority level 1   police rate 30 mbps  class EDGE-L3-VIDEO   priority level 2   police rate percent 45 class EDGE-L3-HIGH   bandwidth remaining percent 40   random-detect 128 kbytes 256 kbytes class EDGE-L3-MED   bandwidth remaining percent 30   random-detect 128 kbytes 256 kbytes class EDGE-L3-LOW   bandwidth remaining percent 20   random-detect 64 kbytes 128 kbytes class EDGE-L3-BE-NG1   bandwidth remaining percent 10   random-detect 32 kbytes 64 kbytes class class-default end-policy-map   If we configure more sub-interface without the service-policy, configuration is accepted. Right now we have around 17K sub-interfaces configured: RP/0/RSP0/CPU0:A9K-LAB05#sh int summary location 0/2/CPU0 Fri Jul 11 11:45:45.005 WEST Interface Type          Total    UP       Down     Admin Down --------------          -----    --       ----     ---------- ALL TYPES               17503    17485    0        18 -------------- IFT_TENGETHERNET        24       7        0        17 IFT_VLAN_SUBIF          17479    17478    0        1   We know that we are not hitting queue limits, but we don't know what kind of limit, if any, are we reaching. Can anyone help us understand what kind of limit are we reaching?   Thanks, Pedro ... View more