03-10-2014 06:32 PM - edited 03-11-2019 08:55 PM
Hi Everyone,
I have ASA in active/standby mode.
Need to upgrade IOS on both.
i have copied the IOS to the active ASA.
I logged in to standby ASA and ran the same command to copy the ios using FTP but got error
too many process.
I tried to copy the IOS from Active ASA via going to config mode and using the command
failover exec standby copy ftp user name password IP /filename disk0: no luck.
Need to know is it possible to copy the IOS to standby mode ?
Does anyone know if any of the 2 methods above work?
Regards
MAhesh
Solved! Go to Solution.
03-11-2014 08:08 AM
Hi Mahesh,
We sometimes see the "no more processes" unhelpful error message with some of the latest 9.1 images when trying to copy a new image. I'm still a bit unclear on the root cause - I think it's related to the upgrade caveats in the release notes.
The workaround I have found is to move up only one .x(y) release (e.g 9.1(1) to 9.1(2)) from the current version when copying new ASA system software images.
What are your exact version numbers of ASA software on the Primary and Standby unit?
03-12-2014 09:17 PM
Yikes. 8.0(5). That's an old one. What release are you trying to move to?
I haven't seen that error on the older versions. Can you possibly try copying using ASDM (log into secondary unit and try file transfer from local PC to ASA)? ASDM will use http transfer.
If you don't have a standby IP address you can failover and then try the copy directly to the Secondary - Active unit.
03-10-2014 07:31 PM
Hello, Mahesh.
Both methods should work fine, but you probably have issues with the cpu utilization and process count. Execute commands show cpu utilization and show processes, and send us the result.
03-10-2014 07:45 PM
Hi,
Error is %Error reading ftp:///.................. (No more processes)
sh cpu usage
CPU utilization for 5 seconds = 0%; 1 minute: 0%; 5 minutes: 0%
sh processes
PC SP STATE Runtime SBASE Stack Process
Lwe 08051abc 6a90ce4c 09ba45f8 0 6a90af38 7920/8192 block_diag
Mrd 08181014 6a93d934 09ba3f3c 21823 6a91dac0 127192/131072 Dispatch Unit
Mwe 08370e95 6a942b2c 09ba3d2c 0 6a940d38 7528/8192 CF OIR
Mwe 089942c0 6a944d8c 09ad5750 0 6a942ea8 7872/8192 lina_int
Mwe 08064da5 6a9b4584 09ba3d2c 0 6a9b26e0 7704/8192 Reload Control Thre ad
Mwe 080698f6 6a9bf4e4 09ba5e58 1 6a9bb930 13020/16384 aaa
Mwe 08092ab6 6a9c638c 09ba5eb4 0 6a9c2498 15712/16384 CMGR Server Proce ss
Mwe 08092fc5 6a9c849c 09ba3d2c 0 6a9c6608 7760/8192 CMGR Timer Process
Lwe 08180131 6a9d2c3c 09bb0ee4 0 6a9d0d38 7376/8192 dbgtrace
Msi 083fd57c 6a9db34c 09ba3d2c 1110 6a9d9438 7808/8192 557mcfix
Msi 083fd39e 6a9dd4bc 09ba3d2c 0 6a9db5a8 7776/8192 557statspoll
Mwe 08b908fd 6ac169fc 09ba3d2c 8 6a9fb0e8 7132/8192 netfs_thread_init
Mwe 0919b985 6aa09694 09ba3d2c 0 6aa07810 7672/8192 Chunk Manager
Msi 0882215e 6aa14c4c 09ba3d2c 1589 6aa12d58 7692/8192 PIX Garbage Collect or
Mwe 088157d4 6aa22af4 09ac696c 0 6aa20bf0 7904/8192 IP Address Assign
Mwe 089dfac6 6abb59e4 09b080b8 0 6abb3ae0 7904/8192 QoS Support Module
Mwe 08895bef 6abb7b8c 09ac7a10 0 6abb5c88 7904/8192 Client Update Task
Lwe 091dadc8 6abba44c 09ba3d2c 109361 6abb85b8 7696/8192 Checkheaps
Mwe 089e2d55 6abc0754 09ba3d2c 0 6abbeaf0 6624/8192 Quack process
Mwe 08a38f82 6abc8ad4 09ba3d2c 150 6abc0c60 31888/32768 Session Manager
Mwe 08b3ec05 6abd361c 6bbcf9a0 5 6abcfbc8 14296/16384 uauth
Mwe 08adc2a5 6abd5bf4 09b150a4 0 6abd3cf0 7376/8192 Uauth_Proxy
Msp 08b1204c 6abdda64 09ba3d2c 75 6abdbb50 7808/8192 SSL
Mwe 08b3cb46 6abdfb94 09b1abc4 0 6abddcc0 7240/8192 SMTP
Mwe 08b314ad 6abe3bd4 09b1ab48 4 6abdfe30 12308/16384 Logger
Mwe 08b32748 6abe5d74 09ba3d2c 0 6abe3fa0 7568/8192 Syslog Retry Threa d
Mwe 08b2d8ae 6abe7fa4 09ba3d2c 0 6abe6110 7344/8192 Thread Logger
Mwe 08d0b822 6abf6a04 09b4da28 0 6abf4b20 7040/8192 vpnlb_thread
Mwe 08243e9d 6abfd4cc 09ba3d2c 0 6abfb648 7672/8192 TLS Proxy Inspector
Msi 08a52b23 6ac88a7c 09ba3d2c 1538 6ac86b78 7792/8192 emweb/cifs_timer
Mwe 08627d87 6acdb744 09abd0ac 0 6acd9850 7520/8192 netfs_mount_handler
Msi 084dd008 6a9cc7bc 09ba3d2c 5361 6a9ca8e8 7168/8192 arp_timer
Mwe 084e692c 6a9d917c 09bc4f48 0 6a9d72c8 7824/8192 arp_forward_thread
Mwe 0854b5e5 6a9df59c 09bc9d40 0 6a9dd718 7808/8192 Lic TMR
Mwe 08b41bb1 6aa07594 09b1ae40 0 6aa056a0 7776/8192 tcp_fast
Mwe 08b44d20 6af5e974 09b1ae40 0 6af5ca90 7760/8192 tcp_slow
Mwe 08b6f839 6af6c664 09b22d48 1 6af6a770 7776/8192 udp_timer
Mwe 080ebd38 6a9ff194 09ba3d2c 0 6a9fd300 7760/8192 CTCP Timer process
Mwe 08cbbbf3 6aa013d4 09ba3d2c 0 6a9ff560 7728/8192 L2TP data daemon
Mwe 08cbc9c3 6b5016e4 09ba3d2c 0 6b4ff860 7744/8192 L2TP mgmt daemon
Mwe 08ca8a7b 6b53981c 09b47964 364 6b535968 16048/16384 ppp_timer_thread
Msi 08d0bca7 6b53b864 09ba3d2c 2030 6b539990 7744/8192 vpnlb_timer_thread
Mwe 081019a7 6a9ce8ec 6aa03370 1 6a9cca58 7576/8192 IPsec message handl er
Msi 0811407c 6b581a64 09ba3d2c 38260 6b57dba0 14088/16384 CTM message handl er
Mwe 088f2fa9 6a9d0a2c 09ba3d2c 2 6a9cebc8 5324/8192 NAT security-level reconfiguration
Mwe 08a0de58 6b72676c 09ba3d2c 0 6b7248c8 7776/8192 ICMP event handler
Mwe 0877b763 6b72a92c 09ba3d2c 2022 6b726a88 14860/16384 IP Background
Mwe 08175b99 6b79236c 09a9aa38 10834 6b772528 121020/131072 tmatch compile thread
Mwe 0891fe85 6bc9761c 09ba3d2c 0 6bc93768 15912/16384 Crypto PKI RECV
Mwe 0892351a 6bc9d364 09ba3d2c 0 6bc994d0 15880/16384 Crypto CA
Mwe 08958e53 6bca14e4 09ba3d2c 0 6bc9d640 15896/16384 CERT API
Lsi 08833c28 6bcd98bc 09ba3d2c 20 6bcd79a8 7808/8192 uauth_urlb clean
Lwe 0881b60f 6bee979c 09ba3d2c 7137 6bee7928 4212/8192 pm_timer_thread
Mwe 0846dfd9 6beedb5c 09ba3d2c 4871 6bee9cc8 15888/16384 IKE Timekeeper
Mwe 08461afb 6bef3064 09ab84b4 1789 6beef490 12920/16384 IKE Daemon
Mwe 08aeebaa 6bef6d1c 09b197b4 0 6bef4e38 7872/8192 RADIUS Proxy Event Daemon
Mwe 08abdd0b 6bef8d4c 6abf7cc8 2 6bef6fa8 7032/8192 RADIUS Proxy Listen er
Mwe 08aed7a7 6befafac 09ba3d2c 0 6bef9118 7760/8192 RADIUS Proxy Time K eeper
Mwe 084cddfc 6befde04 09bc4ec8 0 6befbfc0 7024/8192 Integrity FW Task
Mwe 0819552b 6bf38eb4 096d7ebc 1879 6bf196c0 121876/131072 ci/console
Mwe 083a72b5 6bf3b6c4 09ba3d2c 1 6bf39830 4368/8192 fover_thread
Mwe 08c90825 6bf3d834 09d4a990 62 6bf3b9a0 7500/8192 lu_ctl
Msi 08855a1c 6bf3f804 09ba3d2c 26291 6bf3db10 6072/8192 update_cpu_usage
Msi 08850cdc 6bf49c5c 09ba3d2c 62398 6bf47e28 5804/8192 NIC status poll
Mwe 083963ac 6abbc5b4 09bb7e60 5593 6abba810 4128/8192 fover_rx
Mwe 083925f3 6abec28c 09bb87f4 4284 6abea3d8 6384/8192 fover_tx
Mwe 083916ae 6a9fae3c 09bc55a8 9250 6a9f8f58 6240/8192 fover_ip
Mwe 083a76b1 6bf61f84 09bb8808 0 6bf5e2a0 15552/16384 fover_rep
Mwe 0839ff6d 6bf69e7c 09bb8810 20754 6bf622c8 21316/32768 fover_parse
Mwe 083813d4 6bf6c194 09bb7938 1 6bf6a2f0 5584/8192 fover_ifc_test
Mwe 08384835 6bf6e1ac 09ba3d2c 90194 6bf6c318 3388/8192 fover_health_monito ring_thread
Mwe 083b9b90 6bf723fc 09ba3d2c 947 6bf70568 4804/8192 ha_trans_ctl_tx
Mwe 083b9b90 6bf8544c 09ba3d2c 0 6bf835b8 7760/8192 ha_trans_data_tx
Mwe 083b1097 6bf8d484 09ba3d2c 2 6bf855e0 29920/32768 fover_FSM_thread
Mwe 08c9024b 6bf90484 09bc5008 0 6bf8e580 7832/8192 lu_rx
Lwe 08c9017c 6bf924bc 09d4a840 0 6bf905a8 7920/8192 lu_dynamic_sync
Mwe 08a850d3 6bf97444 09b0c960 11 6bf95550 5724/8192 SNMP Notify Thread
Mwe 08b908fd 6c013c3c 09ba3d2c 156 6bf97578 24816/32768 rtcli async execu tor process
Mwe 084d83a6 6c28130c 09bc5614 15096 6c27d438 15592/16384 IP Thread
Mwe 084decbe 6c283354 09bc4fc8 6420 6c281460 4756/8192 ARP Thread
Mwe 08402ece 6c2852dc 09bc5600 0 6c283488 5060/8192 icmp_thread
Mwe 08b707b6 6c287344 09ba3d2c 152 6c2854b0 7660/8192 udp_thread
Mwe 08b46cfc 6c28922c 09bc561c 0 6c2874d8 7472/8192 tcp_thread
Mwe 08b50bf3 6c28b394 09ba3d2c 0 6c289500 7320/8192 npshim_thread
Mwe 08abdd0b 6c3e9bdc 6c3e6928 3 6c3e7e28 7368/8192 EAPoUDP-sock
Mwe 081bb9c5 6c3eb9b4 09ba3d2c 0 6c3e9e50 6872/8192 EAPoUDP
Mwe 0888b235 6c682e4c 09ba3d2c 84 6c67efa8 15800/16384 Time Range Proces s
Lwe 08188ee6 6c68918c 09ba3d2c 17 6c6872f8 7696/8192 dns_cache_timer
Mwe 08186a9a 6c68b2e4 09ba3d2c 0 6c6894b0 7592/8192 dns_process
Mwe 089ee7a3 6d8f9cac 09b08908 3 6d8f7e28 4556/8192 radius_snd
Mwe 08b6f8e8 6d8fb6ac 6af6a4b4 0 6d8f9f98 4632/8192 radius_rcv_auth
Mwe 08b6f8e8 6d8fd81c 6af6a3fc 0 6d8fc108 5336/8192 radius_rcv_acct
Lsi 08c8d1dc 6e3cc9d4 09ba3d2c 16 6e3caac0 7808/8192 websns_clean_cache
Msi 08c8b617 6e3ce9ac 09ba3d2c 640 6e3ccae8 7728/8192 websns_keepalive
Mwe 08b3ec05 6e3d0a0c 6bbcf9c8 0 6e3ceba8 7744/8192 websns_rcv_tcp
Mwe 08c8c90f 6e3d2c0c 09b267e8 0 6e3d0d18 7888/8192 websns_snd
Mwe 08b6f8e8 6e3d4cec 6af6a344 0 6e3d2e88 7208/8192 websns_rcv_udp
Mwe 08b6f8e8 6e3d6e5c 6af6a28c 0 6e3d4ff8 7208/8192 n2h2_rcv_udp
Mwe 08b6f8e8 6e83ef04 6af6a11c 269 6e83d6f0 4068/8192 snmp
Mwe 08abdd0b 6e867534 6e8c1128 2 6e865790 7352/8192 IKE Receiver
Mwe 0819dc81 6e8d082c 09ba3d2c 20 6e8ce988 7712/8192 DHCPD Timer
Mwe 0819f7de 6e8d89dc 09ba3d2c 78 6e8d6b98 7176/8192 dhcp_daemon
Mwe 08cec25d 6ead22bc 09b4d748 1 6eaca3c8 29804/32768 vpnfol_thread_msg
Msi 08cf22d2 6ead488c 09ba3d2c 1478 6ead29a8 7760/8192 vpnfol_thread_timer
Mwe 08cf0772 6ead6e1c 09b4d8c0 0 6ead4f88 7792/8192 vpnfol_thread_sync
Msi 08cf1dfc 6ead944c 09ba3d2c 4065 6ead7568 7760/8192 vpnfol_thread_unsen t
Mwe 084ca188 6abfac94 09ba3d2c 0 6abf8e00 7760/8192 Integrity Fw Timer Thread
Lwe 08887bb0 6edc0b74 09ba3d2c 41 6edbed10 7648/8192 vPif_stats_cleaner
Mwe 08b908fd 6d00b9bc 09ba3d2c 1392 6cffe3c8 4012/8192 Unicorn Admin Threa d
Mwe 08b51d14 6d0e8b3c 6d0e4100 0 6d0e6e88 6760/8192 listen/ssh
Mwe 08c8771e 6d0f85ec 09ba3d2c 0 6d0f6828 7048/8192 WCCP V2 Protocol
Mwe 087133c3 6d109e64 09ba3d2c 3619 6d107fd0 4364/8192 NTP
Msi 08627e5c 6ec6ba94 09ba3d2c 88 6ec69bb0 7752/8192 netfs_vnode_reclaim
Mwe 08b0327b 6a9c1934 09ba3d2c 0 6a9bfaa0 6128/8192 ssh/timer
M* 08afce3c 6546c91c 09ba3f3c 115 6cd64100 23972/32768 ssh
- - - - 566364582 - - scheduler
- - - - 566843660 - - total elapsed
03-10-2014 09:46 PM
Hello,
First of all, where is the FTP server?
Can you ping it from the secondary box?
Normally this errors are becuase you wrote down something on the wrong way.
So check the copy command one, two and three times.
Regards
03-11-2014 07:41 AM
Hi Julio,
FTP server is pingable from the standby switch.
Its on different subnet not connected directly to ASA.
Same syntax works fine from Active ASA.
Regards
Mahesh
03-11-2014 08:08 AM
Hi Mahesh,
We sometimes see the "no more processes" unhelpful error message with some of the latest 9.1 images when trying to copy a new image. I'm still a bit unclear on the root cause - I think it's related to the upgrade caveats in the release notes.
The workaround I have found is to move up only one .x(y) release (e.g 9.1(1) to 9.1(2)) from the current version when copying new ASA system software images.
What are your exact version numbers of ASA software on the Primary and Standby unit?
03-11-2014 09:16 AM
Hi Marvin,
Active and standby ASA has version asa805-28-k8.bin.
Regards
03-12-2014 09:17 PM
Yikes. 8.0(5). That's an old one. What release are you trying to move to?
I haven't seen that error on the older versions. Can you possibly try copying using ASDM (log into secondary unit and try file transfer from local PC to ASA)? ASDM will use http transfer.
If you don't have a standby IP address you can failover and then try the copy directly to the Secondary - Active unit.
03-13-2014 10:56 AM
Hi Marvin,
I am trying to move to asa825-46-k8.bin
I tried from ASDM and copy the IOS from Local PC to ASA and it worked.
Need to confirm if it uses port 443 to copy from PC to ASA?
Regards
MAhesh
12-17-2016 01:34 PM
I just had this issue in 9.1(7). I found by shortening the source filename the copy worked fine, I went from a filename with 35 characters to one with 17 the error disappeared.
I was using copy ftp: start to push a new startup config.
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