Cisco PIX 525 Spezifikationen PDF herunterladen (Seite 161)

11-29

Cisco Security Appliance Command Line Configuration Guide

OL-6721-01

Chapter 11 Configuring Failover

Configuring Failover

Configuring Failover Group Preemption

Assigning a primary or secondary priority to a failover group specifies which unit the failover group

becomes active on when both units boot simultaneously. However, if one unit boots before the other, then

both failover groups become active on that unit. When the other unit comes online, any failover groups

that have the unit as a priority do not become active on that unit unless manually forced over, a failover

occurs, or the failover group is configured with the preempt command. The preempt command causes

a failover group to become active on the designated unit automatically when that unit becomes available.

Enter the following commands to configure preemption for the specified failover group:

hostname(config)# failover group {1 | 2}

hostname(config-fover-group)# preempt [

delay

]

You can enter an optional delay value, which specifies the number of seconds the failover group remains

active on the current unit before automatically becoming active on the designated unit.

Enabling HTTP Replication with Stateful Failover

To allow HTTP connections to be included in the state information, you need to enable HTTP

replication. Because HTTP connections are typically short-lived, and because HTTP clients typically

retry failed connection attempts, HTTP connections are not automatically included in the replicated state

information. You can use the replication http command to cause a failover group to replicate HTTP state

information when Stateful Failover is enabled.

To enable HTTP state replication for a failover group, enter the following command. This command only

affects the failover group in which it was configured. To enable HTTP state replication for both failover

groups, you must enter this command in each group. This command should be entered in the system

execution space.

hostname(config)# failover group {1 | 2}

hostname(config-fover-group)# replication http

Disabling and Enabling Interface Monitoring

You can monitor up to 250 interfaces on a unit. By default, monitoring of physical interfaces is enabled

and the monitoring of subinterfaces is disabled. You can control which interfaces affect your failover

policy by disabling the monitoring of specific interfaces and enabling the monitoring of others. This lets

you exclude interfaces attached to less critical networks from affecting your failover policy.

To disable health monitoring on an interface, enter the following command within a context:

hostname/context(config)# no monitor-interface

if_name

To enable health monitoring on an interface, enter the following command within a context:

hostname/context(config)# monitor-interface

if_name

Configuring Interface and Unit Poll Times

You can configure the amount of time between hello messages when monitoring the health of the

interfaces in a failover group. Decreasing the interface poll time allows failover to occur faster when an

interface fails, but consumes more system resources.

To change the default interface poll time, enter the following commands:

hostname(config)# failover group {1 | 2}

hostname(config-fover-group)# polltime interface

seconds

1 2 ... 156 157 158 159 160 161 162 163 164 165 166 ... 603 604

Kommentare zu diesen Handbüchern

Keine Kommentare

Cisco PIX 525 Spezifikationen Seite 161

Kommentare zu diesen Handbüchern