Juniper EX9200 Features Manual page 24

Flow Monitoring Feature Guide for EX9200 Switches
10
down-on-flow-control;
dump-on-flow-control;
reset-on-flow-control;
}
}
}
Specify the physical and logical location of the flow-monitoring interface. You cannot
use unit 0 , because it is already used by internal processes. Specify the source and
destination addresses. The
filter or a filter group that you have already configured for this purpose. The
statement specifies the traffic direction:
The statement allows you to configure properties related to
multiservice-options
flow-monitoring interfaces:
Include the core-dump statement to enable storage of core files in
Include the statement to enable storage of system logging information in
syslog
/var/log .
NOTE: Boot images for monitoring services interfaces are specified at the
[edit chassis images pic]
configuration to make the flow monitoring feature operable:
[edit system]
ntp {
boot-server ntp.example.net;
server 172.17.28.5;
}
processes {
ntp enable;
}
For more information, see the Junos OS Administration Library for Routing
Devices.
Include the
flow-control-options
NOTE: Starting with Junos OS Release 15.1, the multiservices PIC
management daemon core file is generated when a prolonged flow control
failure occurs and when you configure the setting to generate a core dump
during prolonged flow control (by using the
with the flow-control-options
continues to generate a kernel core file in such scenarios. In Junos OS
Release 14.2 and earlier, an eJunos kernel core file is generated when a
prolonged flow control failure occurs and when you configure the setting
to generate a core dump during prolonged flow control.
statement allows you to associate an input or output
filter
input , output , or both.
hierarchy level. You must include the following
statement to configure flow control.
statement). The watchdog functionality
sampling
/var/tmp .
option
dump-on-flow-control
Copyright © 2017, Juniper Networks, Inc.