Cisco Cisco Firepower Management Center 4000
6-32
FireSIGHT System User Guide
Chapter 6 Managing Devices
Clustering Devices
Step 3
Click
Yes
to confirm maintenance mode or click
No
to cancel.
Step 4
Click the toggle maintenance mode icon (
) again to bring the device out of maintenance mode.
Replacing a Device in a Clustered Stack
License:
Control
Supported Devices:
Series 3
After you place a stack that is a cluster member into maintenance mode, you can replace a secondary
device in the stack for another device. You can only select devices that are not currently stacked or
clustered. The new device must follow the same guidelines for establishing a device stack. See
device in the stack for another device. You can only select devices that are not currently stacked or
clustered. The new device must follow the same guidelines for establishing a device stack. See
.
To replace a device in a clustered stack:
Access:
Admin/Network Admin
Step 1
Select
Devices > Device Management
.
The Device Management page appears.
Step 2
Next to the stack member you want to place into maintenance mode, click the toggle maintenance mode
icon (
icon (
).
The Confirm Maintenance Mode pop-up window appears.
Step 3
Click
Yes
to confirm maintenance mode or click
No
to cancel.
Step 4
Click the replace device icon (
).
The Replace Device pop-up window appears.
Step 5
Select the
Replacement Device
from the drop-down list.
Step 6
Click
Replace
to replace the device or click
Cancel
to keep the current device and return to the Device
Management page.
Step 7
Click the toggle maintenance mode icon (
) again to bring the stack immediately out of maintenance
mode.
You do not need to reapply the device configuration.
Establishing Clustered State Sharing
License:
Control
Supported Devices:
Series 3
Clustered state sharing allows clustered devices or clustered stacks to synchronize as much state as
necessary, so that if either device or stack fails, the other peer can take over with no interruption to traffic
flow. Without state sharing, the following features may not fail over properly:
necessary, so that if either device or stack fails, the other peer can take over with no interruption to traffic
flow. Without state sharing, the following features may not fail over properly:
•
Strict TCP enforcement
•
Unidirectional access control rules