CISCO-ASA - Cluster Factory Reset - Revision history

Admin: /* Important Notes */

2026-02-18T10:03:18Z

Important Notes

← Older revision		Revision as of 10:03, 18 February 2026
Line 152:		Line 152:
	== Important Notes ==		== Important Notes ==

	- Backup Configuration: Always backup your configuration before performing a factory reset or removing contexts. Use the following command to back up the configuration:		Backup Configuration: Always backup your configuration before performing a factory reset or removing contexts. Use the following command to back up the configuration:

	<nowiki>		<nowiki>
	copy running-config tftp://<TFTP_server_IP>/backup.cfg</nowiki>		copy running-config tftp://<TFTP_server_IP>/backup.cfg</nowiki>

	- Impact: Resetting the device or removing contexts will erase all configurations associated with the context or unit, including interfaces, security policies, routing, and VPN configurations.		Impact: Resetting the device or removing contexts will erase all configurations associated with the context or unit, including interfaces, security policies, routing, and VPN configurations.

	- Multi-Context Licensing: Ensure that your device is licensed for multi-context operation if you plan to use multiple contexts. The reset or removal of contexts will impact how interfaces and resources are allocated.		Multi-Context Licensing: Ensure that your device is licensed for multi-context operation if you plan to use multiple contexts. The reset or removal of contexts will impact how interfaces and resources are allocated.

	== Useful Links ==		== Useful Links ==

Admin: /* Verify Cluster Synchronization */

2026-02-18T10:02:57Z

Verify Cluster Synchronization

← Older revision		Revision as of 10:02, 18 February 2026
Line 128:		Line 128:
	After re-enabling failover, verify that both units in the cluster are synchronized and that the failover is working correctly:		After re-enabling failover, verify that both units in the cluster are synchronized and that the failover is working correctly:

	<nowiki>		<nowiki>
	show failover</nowiki>		show failover</nowiki>

Admin: /* Break the Failover */

2026-02-18T10:02:38Z

Break the Failover

← Older revision		Revision as of 10:02, 18 February 2026
Line 92:		Line 92:
	To reset the cluster configuration, you must first break the failover between the active and standby units. Enter the following command on both units:		To reset the cluster configuration, you must first break the failover between the active and standby units. Enter the following command on both units:

	<nowiki>no failover</nowiki>		<nowiki>
			no failover</nowiki>

	==== Erase the Configuration ====		==== Erase the Configuration ====

Admin: /* Check Cluster Configuration */

2026-02-18T10:02:26Z

Check Cluster Configuration

← Older revision		Revision as of 10:02, 18 February 2026
Line 86:		Line 86:
	Before performing the reset, check the cluster status to ensure you are on the correct member:		Before performing the reset, check the cluster status to ensure you are on the correct member:

	<nowiki>show failover</nowiki>		<nowiki>
			show failover</nowiki>

	==== Break the Failover ====		==== Break the Failover ====

Admin at 10:02, 18 February 2026

2026-02-18T10:02:01Z

← Older revision		Revision as of 10:02, 18 February 2026
Line 10:		Line 10:

	1. Access the ASA CLI:		1. Access the ASA CLI:
	- Log in to the ASA device using SSH, console, or other access methods.		Log in to the ASA device using SSH, console, or other access methods.

	2. Enter Privileged Exec Mode:		2. Enter Privileged Exec Mode:
	- Once logged in, enter privileged exec mode:		Once logged in, enter privileged exec mode:

	<nowiki>		<nowiki>
Line 19:		Line 19:

	3. Enter Configuration Mode:		3. Enter Configuration Mode:
	- Enter configuration mode to make changes:		Enter configuration mode to make changes:

	<nowiki>		<nowiki>
Line 25:		Line 25:

	4. Switch to System Context:		4. Switch to System Context:
	- Since you are working in a multi-context setup, you need to enter the system context (the default context):		Since you are working in a multi-context setup, you need to enter the system context (the default context):

	<nowiki>		<nowiki>
Line 31:		Line 31:

	5. Remove the Context:		5. Remove the Context:
	- Use the following command to remove the context:		Use the following command to remove the context:

	<nowiki>		<nowiki>
Line 37:		Line 37:

	Example:		Example:
	- If the context name is `Sales`, use:		If the context name is `Sales`, use:

	<nowiki>		<nowiki>
Line 43:		Line 43:

	6. Verify the Removal:		6. Verify the Removal:
	- After the context is removed, verify it has been deleted using:		After the context is removed, verify it has been deleted using:

	<nowiki>		<nowiki>
	show context</nowiki>		show context</nowiki>

	This will list all remaining contexts. The context you removed should no longer appear.		This will list all remaining contexts. The context you removed should no longer appear.

	7. Return to the System Context:		7. Return to the System Context:
	- If you were previously in a specific context, return to the system context using:		If you were previously in a specific context, return to the system context using:

	<nowiki>		<nowiki>
Line 57:		Line 57:

	8. Save the Configuration:		8. Save the Configuration:
	- Once the context is removed, save the configuration to ensure changes are persistent:		Once the context is removed, save the configuration to ensure changes are persistent:

	<nowiki>		<nowiki>

Admin: Created page with "Category:Wiki '''''[https://it-arts.net/index.php/Category:Wiki Return to Wiki Index]''''' == Removing Contexts in a Cisco ASA Cluster == In a multi-context configuration on Cisco ASA devices, each context functions as a virtual firewall with its own configuration, interfaces, and policies. If you need to remove a context from your ASA, follow the steps below. === Steps to Remove a Context === 1. Access the ASA CLI: - Log in to the ASA device using S..."

2026-02-18T10:00:56Z

Created page with "Category:Wiki '''''[https://it-arts.net/index.php/Category:Wiki Return to Wiki Index]''''' == Removing Contexts in a Cisco ASA Cluster == In a **multi-context configuration** on Cisco ASA devices, each context functions as a virtual firewall with its own configuration, interfaces, and policies. If you need to remove a context from your ASA, follow the steps below. === Steps to Remove a Context === 1. **Access the ASA CLI**: - Log in to the ASA device using S..."

New page

[[Category:Wiki]]

'''''[https://it-arts.net/index.php/Category:Wiki Return to Wiki Index]'''''

== Removing Contexts in a Cisco ASA Cluster ==

In a **multi-context configuration** on Cisco ASA devices, each context functions as a virtual firewall with its own configuration, interfaces, and policies. If you need to remove a context from your ASA, follow the steps below.

=== Steps to Remove a Context ===

1. **Access the ASA CLI**:
- Log in to the ASA device using SSH, console, or other access methods.

2. **Enter Privileged Exec Mode**:
- Once logged in, enter privileged exec mode:

<nowiki>
enable</nowiki>

3. **Enter Configuration Mode**:
- Enter configuration mode to make changes:

<nowiki>
config terminal</nowiki>

4. **Switch to System Context**:
- Since you are working in a multi-context setup, you need to enter the **system context** (the default context):

<nowiki>
changeto system</nowiki>

5. **Remove the Context**:
- Use the following command to remove the context:

<nowiki>
no context <context_name></nowiki>

Example:
- If the context name is `Sales`, use:

<nowiki>
no context Sales</nowiki>

6. **Verify the Removal**:
- After the context is removed, verify it has been deleted using:

<nowiki>
show context</nowiki>

This will list all remaining contexts. The context you removed should no longer appear.

7. **Return to the System Context**:
- If you were previously in a specific context, return to the system context using:

<nowiki>
changeto system</nowiki>

8. **Save the Configuration**:
- Once the context is removed, save the configuration to ensure changes are persistent:

<nowiki>
write memory</nowiki>

=== Example CLI Session for Removing a Context ===

<nowiki>
ASA# enable
Password: ********

ASA# config terminal
ASA(config)# changeto system
ASA(system)# no context Sales
ASA(system)# show context
</nowiki>

== Factory Reset of a Cisco ASA Cluster ==

Performing a factory reset on a **Cisco ASA Cluster** (e.g., ASA 5500-X or other models) will erase all configurations, including interfaces, routing, VPN settings, and security policies, returning the device to its default settings. Follow the steps below to reset both the active and standby units of an ASA cluster.

=== Steps for Factory Reset of a Cisco ASA Cluster ===

==== Access the ASA CLI ====
Log in to each ASA unit in the cluster (both active and standby units) using SSH, console, or any other method.

==== Check Cluster Configuration ====
Before performing the reset, check the cluster status to ensure you are on the correct member:

<nowiki>show failover</nowiki>

==== Break the Failover ====
To reset the cluster configuration, you must first break the failover between the active and standby units. Enter the following command on both units:

<nowiki>no failover</nowiki>

==== Erase the Configuration ====
Erase the **startup configuration** on both units using:

<nowiki>
write erase</nowiki>

Or alternatively:

<nowiki>
erase startup-config</nowiki>

This will remove all configuration settings.

==== Reboot the ASA Unit ====
After erasing the configuration, reboot the ASA unit to apply the changes:

<nowiki>
reload</nowiki>

When prompted to save the configuration, select **No**, as you just erased it.

==== Repeat for Standby Unit ====
After performing the reset on the active unit, repeat the same steps on the **standby unit** in the cluster.

==== Re-enable Failover ====
Once both units are factory reset and rebooted, re-enable the failover process to restore the cluster:

<nowiki>
failover</nowiki>

==== Verify Cluster Synchronization ====
After re-enabling failover, verify that both units in the cluster are synchronized and that the failover is working correctly:

<nowiki>
show failover</nowiki>

=== Example CLI Session for Factory Reset ===

<nowiki>
ASA# enable
Password: ********

ASA# config terminal
ASA(config)# no failover
ASA(config)# write erase
ASA(config)# reload
</nowiki>

After performing the reset on both the active and standby units, re-enable failover and check synchronization:

<nowiki>
ASA(config)# failover
ASA(config)# show failover
</nowiki>

== Important Notes ==

- **Backup Configuration**: Always **backup your configuration** before performing a factory reset or removing contexts. Use the following command to back up the configuration:

<nowiki>
copy running-config tftp://<TFTP_server_IP>/backup.cfg</nowiki>

- **Impact**: Resetting the device or removing contexts will erase all configurations associated with the context or unit, including interfaces, security policies, routing, and VPN configurations.

- **Multi-Context Licensing**: Ensure that your device is licensed for multi-context operation if you plan to use multiple contexts. The reset or removal of contexts will impact how interfaces and resources are allocated.

== Useful Links ==

* [Cisco ASA Documentation](https://www.cisco.com/c/en/us/support/security/asa-5500-series-next-generation-firewalls/tsd-products-support-series-home.html)
* [Cisco ASA Configuration Guides](https://www.cisco.com/c/en/us/td/docs/security/asa/)
* [Cisco Knowledge Base](https://support.cisco.com/)
* [Cisco ASA Failover Configuration](https://www.cisco.com/c/en/us/td/docs/security/asa/asa914/configuration-guide/firewall/intro-failover.html)
* [Cisco ASA Cluster Configuration](https://www.cisco.com/c/en/us/td/docs/security/asa/asa92/configuration/firewall-cluster.html)

---

'''''[https://it-arts.net/index.php/Category:Wiki Return to Wiki Index]'''''