Replacing faulty memory for Cisco ASA-5520
In one of my older blog posts I wrote about one of my ASA firewalls, which is stuck during the boot process. See here for the older blog post: Cisco ASA5520 stuck at Booting system, please wait…
Now the replacement memory arrived and I replaced the faulty one.
After verifying the boot process with a console connection I saw the ASA-5520 came up with 2048 Mbyte RAM. However I’m going to verify the secondary with the show memory command.
xxxxxxxxxx-asa# sh mem
Free memory: 1618076032 bytes (75%)
Used memory: 529407616 bytes (25%)
------------- ------------------
Total memory: 2147483648 bytes (100%)
On the second ASA 5520 I verify the memory with the failover exec mate show memory command:
xxxxxxxxxx-asa# failover exec mate sh mem
Free memory: 1582448384 bytes (74%)
Used memory: 565035264 bytes (26%)
------------- ------------------
Total memory: 2147483648 bytes (100%)
Last but not least I verify the failover status with the show failover command:
xxxxxxxxxx-asa# sh failover
Failover On
Failover unit Secondary
Failover LAN Interface: failover GigabitEthernet0/3 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 2 of 160 maximum
Version: Ours n.n(n)n, Mate n.n(n)n
Last Failover at: 17:48:52 UTC Oct 26 2019
This host: Secondary - Active
Active time: 485 (sec)
slot 0: ASA5520 hw/sw rev (n.n/n.n(n)nn) status (Up Sys)
Interface outside (nnn.nnn.nnn.nnn): Normal (Waiting)
Interface inside (nnn.nnn.nnn.nnn): Normal (Waiting)
Interface management (nnn.nnn.nnn.nnn): Normal (Not-Monitored)
slot 1: empty
Other host: Primary - Standby Ready
Active time: 216081 (sec)
slot 0: ASA5520 hw/sw rev (n.n/n.n(n)nn) status (Up Sys)
Interface outside (0.0.0.0): Normal (Waiting)
Interface inside (0.0.0.0): Normal (Waiting)
Interface management (0.0.0.0): Normal (Not-Monitored)
slot 1: empty