Juniper EX9200 Series Specification sheet

Network Management and Monitoring Feature
Guide for EX9200 Switches
Release
16.2
Modified: 2016-11-03
Copyright © 2016, 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.
Network Management and Monitoring Feature Guide for EX9200 Switches
16.2
Copyright © 2016, 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 © 2016, Juniper Networks, Inc.ii

Table of Contents
AbouttheDocumentation............................................xi
DocumentationandReleaseNotes..................................xi
SupportedPlatforms.............................................xi
UsingtheExamplesinThisManual..................................xi
MergingaFullExample.......................................xii
MergingaSnippet............................................xii
DocumentationConventions......................................xiii
DocumentationFeedback.........................................xv
RequestingTechnicalSupport.....................................xv
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
OpeningaCasewithJTAC.....................................xvi
Part 1 Configuring Network Management
Chapter 1 Configuring Ethernet OAM Link Fault Management . . . . . . . . . . . . . . . . . . . . . 3
IEEE 802.3ah OAM Link-Fault Management Overview . . . . . . . . . . . . . . . . . . . . . . 3
Configuring IEEE 802.3ah OAM Link-Fault Management . . . . . . . . . . . . . . . . . . . . . 5
EnablingIEEE802.3ahOAMSupport....................................6
ConfiguringtheOAMPDUInterval......................................6
ConfiguringtheOAMPDUThreshold....................................7
ConfiguringanOAMActionProfile......................................8
Configuring Threshold Values for Fault Events in an Action Profile . . . . . . . . . . . . 10
ApplyinganActionProfile............................................10
Setting a Remote Interface into Loopback Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
MonitoringtheLossofLinkAdjacency...................................12
MonitoringProtocolStatus............................................13
Enabling Remote Loopback Support on the Local Interface . . . . . . . . . . . . . . . . . 15
ConfiguringLinkDiscovery............................................16
Configuring Threshold Values for Local Fault Events on an Interface . . . . . . . . . . . 17
Disabling the Sending of Link Event TLVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
DetectingRemoteFaults.............................................18
Specifying the Actions to Be Taken for Link-Fault Management Events . . . . . . . . 19
Example: Configuring IEEE 802.3ah OAM Support on an Interface . . . . . . . . . . . . 21
Chapter 2 Configuring sFlow Monitoring Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Understanding How to Use sFlow Technology for Network Monitoring on an EX
SeriesSwitch...................................................23
Sampling Mechanism and Architecture of sFlow Technology on EX Series
Switches...................................................23
AdaptiveSampling..............................................24
iiiCopyright © 2016, Juniper Networks, Inc.

sFlowAgentAddressAssignment..................................25
Configuring sFlow Technology for Network Monitoring (CLI Procedure) . . . . . . . . 26
Example: Configuring sFlow Technology to Monitor Network Traffic on EX Series
Switches ......................................................27
Chapter 3 Configuring Uplink Failure Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Understanding Uplink Failure Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
UplinkFailureDetectionOverview..................................33
FailureDetectionPair............................................34
Configuring Interfaces for Uplink Failure Detection (CLI Procedure) . . . . . . . . . . . 35
Chapter4 RoutineMonitoring................................................37
Monitoring Traffic Through the Router or Switch . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Displaying Real-Time Statistics About All Interfaces on the Router or
Switch.....................................................37
Displaying Real-Time Statistics About an Interface on the Router or
Switch ....................................................38
Part 2 Configuration Statements and Operational Commands
Chapter 5 Configuration Statements: Ethernet OAM Link Fault Management . . . . . . 43
link-fault-management..............................................45
action(OAM)......................................................46
action-profile(DefiningforLFM).......................................47
allow-remote-loopback .............................................48
apply-action-profile.................................................48
ethernet(ProtocolsOAM)............................................49
event(LFM).......................................................52
event-thresholds ...................................................52
fast-aps-switch ....................................................53
frame-error........................................................54
frame-period ......................................................55
frame-period-summary..............................................56
interface (OAM Link-Fault Management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
link-adjacency-loss .................................................58
link-down .........................................................58
link-discovery......................................................59
link-event-rate .....................................................59
negotiation-options.................................................60
no-allow-link-events................................................60
oam..............................................................61
pdu-interval .......................................................63
pdu-threshold .....................................................64
protocol-down.....................................................64
remote-loopback...................................................65
send-critical-event .................................................65
symbol-period .....................................................66
syslog(OAMAction)................................................66
version-ipfix (Services) ..............................................67
Copyright © 2016, Juniper Networks, Inc.iv
Network Management and Monitoring Feature Guide for EX9200 Switches

Chapter 6 Configuration Statements: sFlow Technology . . . . . . . . . . . . . . . . . . . . . . . . 69
agent-id ..........................................................69
collector ..........................................................70
interfaces (sFlow Monitoring Technology) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
polling-interval .....................................................72
sample-rate .......................................................73
source-ip..........................................................74
udp-port ..........................................................74
Chapter 7 Configuration Statements: Uplink Failure Detection . . . . . . . . . . . . . . . . . . . 75
action(UplinkFailureDetection).......................................75
group(UplinkFailureDetection).......................................76
link-to-disable .....................................................76
link-to-monitor .....................................................77
traceoptions (Uplink Failure Detection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
uplink-failure-detection..............................................79
Chapter8 OperationalCommands............................................81
monitor traffic .....................................................82
ping..............................................................94
show oam ethernet link-fault-management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
showinterfaces(FastEthernet)......................................104
show interfaces (10-Gigabit Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
showsflowcollector................................................145
showsflow.......................................................146
showsflowinterface...............................................148
traceroute ........................................................150
traceroutemonitor.................................................154
Chapter 9 Operational Commands: Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
showforwarding-optionsanalyzer....................................158
vCopyright © 2016, Juniper Networks, Inc.
Table of Contents

Copyright © 2016, Juniper Networks, Inc.vi
Network Management and Monitoring Feature Guide for EX9200 Switches

List of Figures
Part 1 Configuring Network Management
Chapter 2 Configuring sFlow Monitoring Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 1: sFlow Technology Monitoring System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 3 Configuring Uplink Failure Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 2: Uplink Failure Detection Configuration on Switches . . . . . . . . . . . . . . . . 34
viiCopyright © 2016, Juniper Networks, Inc.

Copyright © 2016, Juniper Networks, Inc.viii
Network Management and Monitoring Feature Guide for EX9200 Switches

List of Tables
AbouttheDocumentation..........................................xi
Table1:NoticeIcons.................................................xiii
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Part 1 Configuring Network Management
Chapter4 RoutineMonitoring................................................37
Table 3: Output Control Keys for the monitor interface Command . . . . . . . . . . . . 39
Part 2 Configuration Statements and Operational Commands
Chapter8 OperationalCommands............................................81
Table 4: Match Conditions for the monitor traffic Command . . . . . . . . . . . . . . . . 84
Table 5: Logical Operators for the monitor traffic Command . . . . . . . . . . . . . . . . 86
Table 6: Arithmetic and Relational Operators for the monitor traffic
Command .....................................................87
Table 7: show oam ethernet link-fault-management Output Fields . . . . . . . . . . . 98
Table 8: show interfaces Fast Ethernet Output Fields . . . . . . . . . . . . . . . . . . . . . 104
Table 9: show interfaces Gigabit Ethernet Output Fields . . . . . . . . . . . . . . . . . . . . 121
Table 10: Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface
Type .........................................................135
Table 11: show sflow collector Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Table12:showsflowOutputFields....................................146
Table 13: show sflow interface Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Table14:tracerouteOutputFields.....................................152
Table 15: traceroute monitor Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Chapter 9 Operational Commands: Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Table 16: show forwarding-options analyzer Output Fields . . . . . . . . . . . . . . . . . 158
ixCopyright © 2016, Juniper Networks, Inc.

Copyright © 2016, Juniper Networks, Inc.x
Network Management and Monitoring Feature Guide for EX9200 Switches

About the Documentation
•Documentation and Release Notes on page xi
•Supported Platforms on page xi
•Using the Examples in This Manual on page xi
•Documentation Conventions on page xiii
•Documentation Feedback on page xv
•Requesting Technical Support on page xv
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.
xiCopyright © 2016, 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 © 2016, Juniper Networks, Inc.xii
Network Management and Monitoring Feature Guide for EX9200 Switches

[edit]
user@host# edit system scripts
[edit system scripts]
3. Merge the contents of the file into your routing platform configuration by issuing the
load merge relative configuration mode command:
[edit system scripts]
user@host# load merge relative /var/tmp/ex-script-snippet.conf
load complete
For more information about the load command, see CLI Explorer.
Documentation Conventions
Table 1 on page xiii defines notice icons used in this guide.
Table 1: Notice Icons
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Indicates a situation that might result in loss of data or hardware damage.Caution
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
Indicates helpful information.Tip
Alerts you to a recommended use or implementation.Best practice
Table 2 on page xiii defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
ExamplesDescriptionConvention
To enter configuration mode, type the
configure command:
user@host> configure
Represents text that you type.Bold text like this
xiiiCopyright © 2016, Juniper Networks, Inc.
About the Documentation

Table 2: Text and Syntax Conventions (continued)
ExamplesDescriptionConvention
user@host> show chassis alarms
No alarms currently active
Represents output that appears on the
terminal screen.
Fixed-width text like this
•A policy term is a named structure
that defines match conditions and
actions.
•Junos OS CLI User Guide
•RFC 1997, BGP Communities Attribute
•Introduces or emphasizes important
new terms.
•Identifies guide names.
•Identifies RFC and Internet draft titles.
Italic text like this
Configure the machine’s domain name:
[edit]
root@# set system domain-name
domain-name
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
Italic text like this
•To configure a stub area, include the
stub statement at the [edit protocols
ospf area area-id] hierarchy level.
•The console port is labeled CONSOLE.
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy levels;
or labels on routing platform
components.
Text like this
stub <default-metric metric>;Encloses optional keywords or variables.< > (angle brackets)
broadcast | multicast
(string1 |string2 |string3)
Indicates a choice between the mutually
exclusive keywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
| (pipe symbol)
rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the
same line as the configuration statement
to which it applies.
# (pound sign)
community name members [
community-ids ]
Encloses a variable for which you can
substitute one or more values.
[ ] (square brackets)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Identifies a level in the configuration
hierarchy.
Indention and braces ( { } )
Identifies a leaf statement at a
configuration hierarchy level.
; (semicolon)
GUI Conventions
•In the Logical Interfaces box, select
All Interfaces.
•To cancel the configuration, click
Cancel.
Represents graphical user interface (GUI)
items you click or select.
Bold text like this
Copyright © 2016, Juniper Networks, Inc.xiv
Network Management and Monitoring Feature Guide for EX9200 Switches

Table 2: Text and Syntax Conventions (continued)
ExamplesDescriptionConvention
In the configuration editor hierarchy,
select Protocols>Ospf.
Separates levels in a hierarchy of menu
selections.
>(bold right angle bracket)
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can provide feedback by using either of the following
methods:
•Online feedback rating system—On any page of the Juniper Networks TechLibrary site
at http://www.juniper.net/techpubs/index.html, simply click the stars to rate the content,
and use the pop-up form to provide us with information about your experience.
Alternately, you can use the online feedback form at
http://www.juniper.net/techpubs/feedback/.
•E-mail—Send your comments to [e-mail]. Include the document
or topic name, URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or Partner Support Service
support contract, or are covered under warranty, and need post-sales technical support,
you can access our tools and resources online or open a case with JTAC.
•JTAC policies—For a complete understanding of our JTAC procedures and policies,
review the JTAC User Guide located at
http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
•Product warranties—For product warranty information, visit
http://www.juniper.net/support/warranty/.
•JTAC hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with the
following features:
•Find CSC offerings: http://www.juniper.net/customers/support/
•Search for known bugs: http://www2.juniper.net/kb/
•Find product documentation: http://www.juniper.net/techpubs/
•Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
xvCopyright © 2016, Juniper Networks, Inc.
About the Documentation

•Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
•Search technical bulletins for relevant hardware and software notifications:
http://kb.juniper.net/InfoCenter/
•Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
•Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
•Use the Case Management tool in the CSC at http://www.juniper.net/cm/.
•Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
For international or direct-dial options in countries without toll-free numbers, see
http://www.juniper.net/support/requesting-support.html.
Copyright © 2016, Juniper Networks, Inc.xvi
Network Management and Monitoring Feature Guide for EX9200 Switches

PART 1
Configuring Network Management
•Configuring Ethernet OAM Link Fault Management on page 3
•Configuring sFlow Monitoring Technology on page 23
•Configuring Uplink Failure Detection on page 33
•Routine Monitoring on page 37
1Copyright © 2016, Juniper Networks, Inc.

Copyright © 2016, Juniper Networks, Inc.2
Network Management and Monitoring Feature Guide for EX9200 Switches

CHAPTER 1
Configuring Ethernet OAM Link Fault
Management
•IEEE 802.3ah OAM Link-Fault Management Overview on page 3
•Configuring IEEE 802.3ah OAM Link-Fault Management on page 5
•Enabling IEEE 802.3ah OAM Support on page 6
•Configuring the OAM PDU Interval on page 6
•Configuring the OAM PDU Threshold on page 7
•Configuring an OAM Action Profile on page 8
•Configuring Threshold Values for Fault Events in an Action Profile on page 10
•Applying an Action Profile on page 10
•Setting a Remote Interface into Loopback Mode on page 11
•Monitoring the Loss of Link Adjacency on page 12
•Monitoring Protocol Status on page 13
•Enabling Remote Loopback Support on the Local Interface on page 15
•Configuring Link Discovery on page 16
•Configuring Threshold Values for Local Fault Events on an Interface on page 17
•Disabling the Sending of Link Event TLVs on page 18
•Detecting Remote Faults on page 18
•Specifying the Actions to Be Taken for Link-Fault Management Events on page 19
•Example: Configuring IEEE 802.3ah OAM Support on an Interface on page 21
IEEE 802.3ah OAM Link-Fault Management Overview
Ethernet interfaces capable of running at 100 Mbps or faster on EX Series switches, MX
Series, M Series (except M5 and M10 routers), and T Series routers support the IEEE
802.3ah standard for Operation, Administration, and Management (OAM). You can
configure IEEE 802.3ah OAM on Ethernet point-to-point direct links or links across Ethernet
repeaters. The IEEE 802.3ah standard meets the requirement for OAM capabilities as
Ethernet moves from being solely an enterprise technology to being a WAN and access
technology, as well as being backward-compatible with existing Ethernet technology.
Junos OS supports IEEE 802.3ah link-fault management.
3Copyright © 2016, Juniper Networks, Inc.

The features of link-fault management are:
•Discovery
•Link monitoring
•Remote fault detection
•Remote loopback
The following features are not supported:
•Ethernet running on top of a Layer 2 protocol, such as Ethernet over ATM, is not
supported in OAM configurations.
•Remote loopback is not supported on the 10-Gigabit Ethernet LAN/WAN PIC with
SFP+.
•The remote loopback feature mentioned in section 57.2.11 of IEEE 802.3ah is not
supported on T4000 routers.
NOTE: Aggregated Ethernet member links will now use the physical MAC
address as the source MAC address in 802.3ah OAM packets.
Related
Documentation
Configuring IEEE 802.3ah OAM Link-Fault Management on page 5•
•Enabling IEEE 802.3ah OAM Support on page 6
•Configuring Link Discovery on page 16
•Configuring the OAM PDU Interval on page 6
•Configuring the OAM PDU Threshold on page 7
•Configuring Threshold Values for Local Fault Events on an Interface on page 17
•Disabling the Sending of Link Event TLVs on page 18
•Detecting Remote Faults on page 18
•Configuring an OAM Action Profile on page 8
•Specifying the Actions to Be Taken for Link-Fault Management Events on page 19
•Monitoring the Loss of Link Adjacency on page 12
•Monitoring Protocol Status on page 13
•Configuring Threshold Values for Fault Events in an Action Profile on page 10
•Applying an Action Profile on page 10
•Setting a Remote Interface into Loopback Mode on page 11
•Enabling Remote Loopback Support on the Local Interface on page 15
•Example: Configuring IEEE 802.3ah OAM Support on an Interface on page 21
•Ethernet Interfaces Feature Guide for Routing Devices
Copyright © 2016, Juniper Networks, Inc.4
Network Management and Monitoring Feature Guide for EX9200 Switches