09-08-2017 03:31 AM - edited 03-08-2019 11:57 AM
Hello;
Am facing an issue where my Cisco ASR 1002-X keeps rebooting itself at random time. When i run the show version, i can see the reason for reload is: critical process fault, fman_fp_image, fp_0_0, rc=139
On my syslog server, i keep getting this error: %IOSXE-3-PLATFORM: SIP0: cpp_cp: QFP:0.0 Thread:171 TS:00000041045846946120 %IPSEC-3-HMAC_ERROR: IPSec SA receives HMAC error,
I dont know if that could be the reason of my router reload or if it's an IOS bug, am running asr1002x-universalk9.03.16.04b.S.155-3.S4b-ext.SPA.bin.
Your help will be highly appreciated.
09-08-2017 04:27 AM
@armand.ndayikeza1 wrote:
reason for reload is: critical process fault, fman_fp_image, fp_0_0, rc=139
If this is the case, then post the complete output to the command "dir" and "sh crashinfo".
09-08-2017 05:39 AM
09-08-2017 06:42 AM
09-08-2017 06:46 AM
09-08-2017 06:48 AM
09-14-2017 06:10 AM
Here is the logs i get before the router restarts itself.
2017-09-14 13:36:09 local3.alert #.#.#.# 265: *Sep 14 11:37:38.240: %IOSXE-1-PLATFORM: R0/0: kernel: QFP0.0: Fatal Fault: SW reported: Userspace fault
2017-09-14 12:54:42 local3.emergency #.#.#.# 296: *Sep 14 10:56:11.216: %PMAN-0-PROCFAILCRIT: SIP0: pvp.sh: A critical process fman_fp_image has failed (rc 139)
2017-09-14 11:43:18 local3.emergency #.#.#.# 2738: *Sep 14 09:44:47.530: %PMAN-0-PROCFAILCRIT: SIP0: pvp.sh: A critical process fman_fp_image has failed (rc 139) |
2017-09-14 11:43:18 local3.error #.#.#.# 2737: *Sep 14 09:44:47.436: %PMAN-3-PROCHOLDDOWN: SIP0: pman.sh: The process cpp_ha_top_level_server has been helddown (rc 69) |
2017-09-14 11:43:18 local3.error #.#.#.# 2736: *Sep 14 09:44:47.421: %PMAN-3-PROCHOLDDOWN: SIP0: pman.sh: The process fman_fp_image has been helddown (rc 139) |
2017-09-14 11:43:18 local3.alert #.#.#.# 2735: *Sep 14 09:44:47.323: %IOSXE-1-PLATFORM: R0/0: kernel: QFP0.0: Fatal Fault: SW reported: Userspace fault |
2017-09-14 11:43:18 local3.error #.#.#.# 2734: *Sep 14 09:44:47.295: %CPPDRV-3-LOCKDOWN_INITIATED: SIP0: cpp_ha: QFP0.0 CPP Driver LOCKDOWN being triggered due to fatal error. |
2017-09-14 11:43:18 local3.error #.#.#.# 2733: *Sep 14 09:44:47.294: %CPPOSLIB-3-ERROR_NOTIFY: SIP0: cpp_ha: cpp_ha encountered an error -Traceback= 1#ff47c47aa400ae1e261b0532453d046f errmsg: 7FB57B7B4000+121D cpp_common_os:7FB57F2C4000+DA3C cpp_common_os:7FB57F2C4000+1B5AE cpp_drv_cmn: 7FB57EAEF000+285B7 :400000+24438 :400000+23C1A :400000+14617 :400000+C0DE :400000+129AD :400000+F9E6 :400000+13B62 cpp_common_os:7FB57F2C4000+1257F evlib:7FB57A72E000+B937 evlib:7FB57A72E000+E200 cpp_common_os:7FB57F2C4000+13E42 :400000+DA85 c:7FB572FA1000+1E514 :400000+83E |
2017-09-14 11:43:18 local3.error #.#.#.# 2732: *Sep 14 09:44:47.294: %CPPHA-3-FAULT: SIP0: cpp_ha: CPP:0.0 desc:CPP Client process failed: FMAN-FP det:HA class:CLIENT_SW sev:FATAL id:1 cppstate:RUNNING res:UNKNOWN flags:0x0 cdmflags:0x0 |
2017-09-14 11:43:10 local3.error #.#.#.# 2731: *Sep 14 09:44:38.944: %SSH-3-RSA_SIGN_FAIL: Signature creation failed, status 21 |
2017-09-14 11:43:10 local3.error #.#.#.# 2730: *Sep 14 09:44:38.944: %SSH-3-RSA_SIGN_FAIL: Signature connection failed, status 3 |
2017-09-14 11:43:09 local3.error #.#.#.# 2729: *Sep 14 09:44:38.209: %SSH-3-RSA_SIGN_FAIL: Signature creation failed, status 21 |
2017-09-14 11:43:09 local3.error #.#.#.# 2728: *Sep 14 09:44:38.209: %SSH-3-RSA_SIGN_FAIL: Signature connection failed, status 3 |
2017-09-14 11:43:09 local3.error #.#.#.# 2727: *Sep 14 09:44:37.473: %CRYPTO-3-IKE_PAK_IN_Q_TIME_LIMIT _EXCEED: Pak spent too much time in the IKE input queues |
2017-09-14 11:43:09 local3.error #.#.#.# 2726: *Sep 14 09:44:37.470: %ACE-3-TRANSTO: IOSXE-ESP(14): IKEA trans 0x23E7; opcode 0x23; param 0x0; too many retries |
2017-09-14 11:43:06 local3.error #.#.#.# 2725: *Sep 14 09:44:35.712: %BGP-3-NOTIFICATION: sent to neighbor 154.70.156.109 4/0 (hold time expired) 0 bytes |
2017-09-14 11:43:04 local3.error #.#.#.# 2724: *Sep 14 09:44:33.664: %BGP-3-NOTIFICATION: sent to neighbor 154.70.198.2 4/0 (hold time expired) 0 bytes |
2017-09-14 11:43:01 local3.warning #.#.#.# 2723: *Sep 14 09:44:29.179: %IOSXE-4-PLATFORM: R0/0: kernel: copy_user_buffer: No copy done, status: 3 (0x3) |
2017-09-14 11:43:00 local3.warning #.#.#.# 2722: *Sep 14 09:44:28.178: %IOSXE-4-PLATFORM: R0/0: kernel: copy_user_buffer: No copy done, status: 3 (0x3) |
2017-09-14 11:43:00 local3.warning #.#.#.# 2721: *Sep 14 09:44:28.178: %IOSXE-4-PLATFORM: R0/0: kernel: copy_user_buffer: No copy done, status: 3 (0x3) |
2017-09-14 11:43:00 local3.warning #.#.#.# 2720: *Sep 14 09:44:28.178: %IOSXE-4-PLATFORM: R0/0: kernel: copy_user_buffer: No copy done, status: 3 (0x3) |
2017-09-14 11:43:00 local3.warning #.#.#.# 2719: *Sep 14 09:44:28.178: %IOSXE-4-PLATFORM: R0/0: kernel: copy_user_buffer: No copy done, status: 3 (0x3) |
2017-09-14 11:42:59 local3.error #.#.#.# 2718: *Sep 14 09:44:28.178: %ACE-3-TRANSERR: IOSXE-ESP(14): IKEA trans 0x23E4; opcode 0x23; param 0x0; error 0xA; retry cnt 3 |
2017-09-14 11:42:59 local3.error #.#.#.# 2717: *Sep 14 09:44:28.178: %ACE-3-TRANSERR: IOSXE-ESP(14): IKEA trans 0x23E3; opcode 0x23; param 0x0; error 0xA; retry cnt 3 |
2017-09-14 11:42:59 local3.warning #.#.#.# 2716: *Sep 14 09:44:27.176: %IOSXE-4-PLATFORM: R0/0: kernel: copy_user_buffer: No copy done, status: 3 (0x3) |
2017-09-14 11:42:59 local3.warning #.#.#.# 2715: *Sep 14 09:44:27.176: %IOSXE-4-PLATFORM: R0/0: kernel: copy_user_buffer: No copy done, status: 3 (0x3) |
2017-09-14 11:42:59 local3.warning #.#.#.# 2714: *Sep 14 09:44:27.176: %IOSXE-4-PLATFORM: R0/0: kernel: copy_user_buffer: No copy done, status: 3 (0x3) |
2017-09-14 11:42:59 local3.warning #.#.#.# 2713: *Sep 14 09:44:27.176: %IOSXE-4-PLATFORM: R0/0: kernel: copy_user_buffer: No copy done, status: 3 (0x3) |
2017-09-14 11:42:59 local3.warning #.#.#.# 2712: *Sep 14 09:44:27.176: %IOSXE-4-PLATFORM: R0/0: kernel: copy_user_buffer: No copy done, status: 3 (0x3) |
2017-09-14 11:42:56 local3.error #.#.#.# 2711: *Sep 14 09:44:25.173: %ACE-3-TRANSERR: IOSXE-ESP(14): IKEA trans 0x23E2; opcode 0x23; param 0x0; error 0xA; retry cnt 2 |
Any idea how to solve this.
09-14-2017 01:30 PM
09-08-2017 04:28 AM
Hello,
there are numerous bugs, but they are all configuration specific. Can you post your configuration ?
09-08-2017 05:42 AM - edited 09-08-2017 05:42 AM
05-20-2019 08:50 AM
Configuration does not cause any bugs.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide