Juniper EX9200 Series Specification sheet

Flow Monitoring Feature Guide for EX9200
Switches
Modified: 2017-01-24
Copyright © 2017, Juniper Networks, Inc.

Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
Flow Monitoring Feature Guide for EX9200 Switches
Copyright © 2017, Juniper Networks, Inc.
All rights reserved.
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the
year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks
software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.
Copyright © 2017, Juniper Networks, Inc.ii

Table of Contents
AbouttheDocumentation............................................ix
DocumentationandReleaseNotes..................................ix
SupportedPlatforms.............................................ix
UsingtheExamplesinThisManual..................................ix
MergingaFullExample........................................x
MergingaSnippet............................................x
DocumentationConventions.......................................xi
Documentation Feedback........................................xiii
RequestingTechnicalSupport.....................................xiii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
OpeningaCasewithJTAC.....................................xiv
Part 1 Overview
Chapter1 UnderstandingFlowMonitoring......................................3
ActiveFlowMonitoringOverview........................................3
Part 2 Configuring Flow Monitoring
Chapter 2 Configuring Basic Flow Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
ConfiguringFlowMonitoring...........................................9
Configuring Flow-Monitoring Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Configuring Flow-Monitoring Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Directing Traffic to Flow-Monitoring Interfaces . . . . . . . . . . . . . . . . . . . . . 11
Exporting Flows .............................................12
Configuring Time Periods When Flow Monitoring Is Active and
Inactive.................................................12
Example: Configuring Flow Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 3 Configuring Active Flow Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Configuring Inline Active Flow Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Part 3 Configuration Statements and Operational Commands
Chapter4 ConfigurationStatements..........................................23
address(Interfaces).................................................24
cflowd(DiscardAccounting)..........................................25
core-dump ........................................................26
destination(Interfaces)..............................................27
engine-id(ForwardingOptions).......................................28
engine-type .......................................................29
export-format .....................................................30
iiiCopyright © 2017, Juniper Networks, Inc.

family(Monitoring)..................................................31
filter..............................................................32
flow-active-timeout.................................................33
flow-export-destination .............................................34
flow-inactive-timeout ...............................................35
flow-table-size.....................................................36
input-interface-index ................................................37
interface(AccountingorSampling)....................................37
ipv4-flow-table-size ................................................38
ipv6-flow-table-size ................................................39
monitoring ........................................................40
multiservice-options.................................................41
output-interface-index...............................................41
output(Monitoring).................................................42
port(FlowMonitoring)...............................................43
sampling (Interfaces) ...............................................43
source-address (Forwarding Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
syslog ............................................................44
unit ..............................................................45
Chapter5 Operational Commands ...........................................47
show services accounting aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
show services accounting aggregation template . . . . . . . . . . . . . . . . . . . . . . . . . . 52
showservicesaccountingerrors.......................................54
showservicesaccountingflow........................................58
show services accounting flow-detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
showservicesaccountingmemory.....................................68
show services accounting packet-size-distribution . . . . . . . . . . . . . . . . . . . . . . . . 70
showservicesaccountingstatus.......................................72
showservicesaccountingusage.......................................75
Copyright © 2017, Juniper Networks, Inc.iv
Flow Monitoring Feature Guide for EX9200 Switches

List of Figures
Part 1 Overview
Chapter1 UnderstandingFlowMonitoring......................................3
Figure 1: Active Monitoring Configuration Topology . . . . . . . . . . . . . . . . . . . . . . . . . 5
vCopyright © 2017, Juniper Networks, Inc.

Copyright © 2017, Juniper Networks, Inc.vi
Flow Monitoring Feature Guide for EX9200 Switches

List of Tables
AbouttheDocumentation..........................................ix
Table1:NoticeIcons..................................................xi
Table2:TextandSyntaxConventions...................................xi
Part 3 Configuration Statements and Operational Commands
Chapter5 Operational Commands ...........................................47
Table 3: show services accounting aggregation Output Fields . . . . . . . . . . . . . . . 49
Table 4: show services accounting aggregation template Output Fields . . . . . . . 52
Table 5: show services accounting errors Output Fields . . . . . . . . . . . . . . . . . . . . 54
Table 6: show services accounting flow Output Fields . . . . . . . . . . . . . . . . . . . . . 58
Table 7: show services accounting flow-detail Output Fields . . . . . . . . . . . . . . . . 64
Table 8: show services accounting memory Output Fields . . . . . . . . . . . . . . . . . . 68
Table 9: show services accounting packet-size-distribution Output Fields . . . . . 70
Table 10: show services accounting status Output Fields . . . . . . . . . . . . . . . . . . . . 72
Table 11: show services accounting usage Output Fields . . . . . . . . . . . . . . . . . . . . 75
viiCopyright © 2017, Juniper Networks, Inc.

Copyright © 2017, Juniper Networks, Inc.viii
Flow Monitoring Feature Guide for EX9200 Switches

About the Documentation
•Documentation and Release Notes on page ix
•Supported Platforms on page ix
•Using the Examples in This Manual on page ix
•Documentation Conventions on page xi
•Documentation Feedback on page xiii
•Requesting Technical Support on page xiii
Documentation and Release Notes
To obtain the most current version of all Juniper Networks®technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
If the information in the latest release notes differs from the information in the
documentation, follow the product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject
matter experts. These books go beyond the technical documentation to explore the
nuances of network architecture, deployment, and administration. The current list can
be viewed at http://www.juniper.net/books.
Supported Platforms
For the features described in this document, the following platforms are supported:
•EX Series
Using the Examples in This Manual
If you want to use the examples in this manual, you can use the load merge or the load
merge relative command. These commands cause the software to merge the incoming
configuration into the current candidate configuration. The example does not become
active until you commit the candidate configuration.
If the example configuration contains the top level of the hierarchy (or multiple
hierarchies), the example is a full example. In this case, use the load merge command.
ixCopyright © 2017, Juniper Networks, Inc.

If the example configuration does not start at the top level of the hierarchy, the example
isasnippet. In this case, use the load merge relative command. These procedures are
described in the following sections.
Merging a Full Example
To merge a full example, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration example into a
text file, save the file with a name, and copy the file to a directory on your routing
platform.
For example, copy the following configuration to a file and name the file ex-script.conf.
Copy the ex-script.conf file to the /var/tmp directory on your routing platform.
system {
scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces {
fxp0 {
disable;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
2. Merge the contents of the file into your routing platform configuration by issuing the
load merge configuration mode command:
[edit]
user@host# load merge /var/tmp/ex-script.conf
load complete
Merging a Snippet
To merge a snippet, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration snippet into a text
file, save the file with a name, and copy the file to a directory on your routing platform.
For example, copy the following snippet to a file and name the file
ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory
on your routing platform.
commit {
file ex-script-snippet.xsl; }
2. Move to the hierarchy level that is relevant for this snippet by issuing the following
configuration mode command:
Copyright © 2017, Juniper Networks, Inc.x
Flow Monitoring Feature Guide for EX9200 Switches