Configuring Services Interface Redundancy with Flow Monitoring
Active monitoring services configurations on AS, Multiservices
PICs, and Multiservices DPCs support redundancy. To configure redundancy,
you specify a redundancy services PIC (rsp) interface in
which the primary AS or Multiservices PIC is active and a secondary
PIC is on standby. If the primary PIC fails, the secondary PIC becomes
active, and all service processing is transferred to it. If the primary
PIC is restored, it remains on standby and does not preempt the secondary
PIC; you need to manually restore the services to the primary PIC.
To determine which PIC is currently active, issue the show interfaces
redundancy command.
On flow-monitoring configurations, the only service option supported is warm standby, in which one backup PIC supports multiple working PICs. Recovery times are not guaranteed, because the configuration must be completely restored on the backup PIC after a failure is detected. However, configuration is preserved and available on the new active PIC.
As with the other services that support warm standby, you can
issue the request interfaces (revert | switchover) command
to switch manually between the primary and secondary flow monitoring
interfaces.
For more information, see Configuring AS or Multiservices PIC Redundancy. For information on operational mode commands, see the CLI Explorer.
A sample configuration follows.
interface {
rsp0 {
redundancy-options {
primary sp-0/0/0;
secondary sp-1/3/0;
}
unit 0 {
family inet;
}
}
}
interface {
ge-0/2/0 {
unit 0 {
family inet {
filter {
input as_sample;
}
}
address 10.58.255.49/28;
}
}
}
forwarding-options {
sampling {
instance instance1 { # named instances of sampling parameters
input {
rate 1;
run-length 0;
max-packets-per-second 65535;
}
family inet {
output {
flow-server 10.10.10.2 {
port 5000;
version 5;
}
flow-active-timeout 60;
interface rsp0 {
source-address 10.10.10.1;
}
}
}
}
}
}
firewall {
filter as_sample {
term t1 {
then {
sample;
accept;
}
}
}
}