Juniper EX9200 Features Manual

Network management and monitoring feature guide

Hide thumbs Also See for EX9200:

Features manual (448 pages)

Manual (118 pages)

Overview manual (72 pages)

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

page of 176

/ 176
Contents
Table of Contents
Bookmarks

Table of Contents

Quick Links

Download this manual See also: Feature Manual

Network Management and Monitoring Feature

Guide for EX9200 Switches

Release

16.2

Modified: 2016-11-03

Table of Contents

Chapters

Table of Contents

Need help?

Do you have a question about the EX9200 and is the answer not in the manual?

Questions and answers

Summary of Contents for Juniper EX9200

Page 2 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.
Page 4 Network Management and Monitoring Feature Guide for EX9200 Switches sFlow Agent Address Assignment ........25 Configuring sFlow Technology for Network Monitoring (CLI Procedure) .
Page 11: About The Documentation
® 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.
Page 12: Merging A Full Example
Network Management and Monitoring Feature Guide for EX9200 Switches If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In this case, use the command. These procedures are load merge relative described in the following sections.
Page 13: Documentation Conventions
Table 2: Text and Syntax Conventions Convention Description Examples Bold text like this Represents text that you type. To enter configuration mode, type the configure command: user@host> configure Copyright © 2016, Juniper Networks, Inc. xiii...
Page 14 Network Management and Monitoring Feature Guide for EX9200 Switches Table 2: Text and Syntax Conventions (continued) Convention Description Examples Fixed-width text like this Represents output that appears on the user@host> show chassis alarms terminal screen. No alarms currently active Italic text like this...
Page 15: 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 , simply click the stars to rate the content, http://www.juniper.net/techpubs/index.html and use the pop-up form to provide us with information about your experience.
Page 16: Opening A Case With Jtac
Network Management and Monitoring Feature Guide for EX9200 Switches 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/...
Page 17: Configuring Network Management
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 Copyright © 2016, Juniper Networks, Inc.
Page 19: Configuring Ethernet Oam Link Fault Management
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. Copyright © 2016, Juniper Networks, Inc.
Page 20 Network Management and Monitoring Feature Guide for EX9200 Switches 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.
Page 21: Configuring Ieee 802.3Ah Oam Link-Fault Management
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 Copyright © 2016, Juniper Networks, Inc.
Page 22: Enabling Ieee 802.3Ah Oam Support
Network Management and Monitoring Feature Guide for EX9200 Switches Example: Configuring IEEE 802.3ah OAM Support on an Interface on page 21 Ethernet Interfaces Feature Guide for Routing Devices Enabling IEEE 802.3ah OAM Support To enable IEEE 802.3ah OAM support, include the...
Page 23: Configuring The Oam Pdu Threshold
[edit protocol oam ethernet link-fault-management interface interface-name] hierarchy level: [edit protocol oam ethernet link-fault-management interface interface-name] pdu-threshold threshold-value; The threshold value range is from 3 through 10. The default is three PDUs. Copyright © 2016, Juniper Networks, Inc.
Page 24: Configuring An Oam Action Profile
Network Management and Monitoring Feature Guide for EX9200 Switches Related pdu-threshold on page 64 Documentation 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...
Page 25 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.
Page 26: Configuring Threshold Values For Fault Events In An Action Profile
Network Management and Monitoring Feature Guide for EX9200 Switches Configuring Threshold Values for Fault Events in an Action Profile You can configure link event thresholds for received error events that trigger the action specified in the statement. You can then apply the action profile to one or more action interfaces.
Page 27: Setting A Remote Interface Into Loopback Mode
DTE). When you place a remote DTE into loopback mode, the interface receives the remote-loopback request and puts the interface into remote-loopback mode. When the interface is in remote-loopback mode, all frames Copyright © 2016, Juniper Networks, Inc.
Page 28: Monitoring The Loss Of Link Adjacency
Network Management and Monitoring Feature Guide for EX9200 Switches except OAM PDUs are looped back without any changes made to the frames. OAM PDUs continue to be sent to the management plane and processed. To configure remote loopback, include the...
Page 29: Monitoring Protocol Status
When the CCC-DOWN flag is signaled to the IEEE 802.3ah protocol, the system takes the action defined in the statement of the action profile. For additional information action about Layer 2 circuits, see the Junos OS Layer 2 Circuits Feature Guide, Junos OS VPNs Configuration Guide. Copyright © 2016, Juniper Networks, Inc.
Page 30 Network Management and Monitoring Feature Guide for EX9200 Switches To monitor the IEEE 802.3ah protocol, on the CE-facing PE interface, include the statement at the protocol-down [edit protocols oam ethernet link-fault-management hierarchy level: action-profile profile-name event] In configuration mode, go to the [edit protocols oam ethernet link-fault-management hierarchy level.
Page 31: Enabling Remote Loopback Support On The Local Interface
Applying an Action Profile on page 10 Setting a Remote Interface into Loopback Mode on page 11 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.
Page 32: Configuring Link Discovery
Network Management and Monitoring Feature Guide for EX9200 Switches Configuring Link Discovery When the IEEE 802.3ah OAM protocol is enabled on a physical interface, the discovery process is automatically triggered. The discovery process permits Ethernet interfaces to discover and monitor the peer on the link if it also supports the IEEE 802.3ah standard.
Page 33: Configuring Threshold Values For Local Fault Events On An Interface
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 Copyright © 2016, Juniper Networks, Inc.
Page 34: Disabling The Sending Of Link Event Tlvs
Network Management and Monitoring Feature Guide for EX9200 Switches Example: Configuring IEEE 802.3ah OAM Support on an Interface on page 21 Ethernet Interfaces Feature Guide for Routing Devices Disabling the Sending of Link Event TLVs You can disable the sending of link event TLVs.
Page 35: Specifying The Actions To Be Taken For Link-Fault Management Events
The actions are taken only when all of the events in the action profile are true. If more than one action is specified, all the actions are executed. Copyright © 2016, Juniper Networks, Inc.
Page 36 Network Management and Monitoring Feature Guide for EX9200 Switches You might want to set a lower threshold for a specific action such as logging the error and set a higher threshold for another action such as sending a critical event TLV.
Page 37: Example: Configuring Ieee 802.3Ah Oam Support On An Interface
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 Copyright © 2016, Juniper Networks, Inc.
Page 38 Network Management and Monitoring Feature Guide for EX9200 Switches 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...
Page 39: Configuring Sflow Monitoring Technology
The sFlow technology is a monitoring technology for high-speed switched or routed networks. sFlow monitoring technology randomly samples network packets and sends the samples to a monitoring station. You can configure sFlow technology on a Juniper Networks EX Series Ethernet Switch to continuously monitor traffic at wire speed on all interfaces simultaneously.
Page 40: Adaptive Sampling
Network Management and Monitoring Feature Guide for EX9200 Switches NOTE: sFlow technology on the switches samples only raw packet headers. A raw Ethernet packet is the complete Layer 2 network frame. An sFlow monitoring system consists of an sFlow agent embedded in the switch and a centralized collector.
Page 41: Sflow Agent Address Assignment
IP address of the configured Gigabit Ethernet interface, 10-Gigabit Ethernet interface, or the RVI is used as the source IP address. Related Example: Configuring sFlow Technology to Monitor Network Traffic on EX Series Documentation Switches on page 27 Copyright © 2016, Juniper Networks, Inc.
Page 42: Configuring Sflow Technology For Network Monitoring (Cli Procedure)
Network Management and Monitoring Feature Guide for EX9200 Switches Configuring sFlow Technology for Network Monitoring (CLI Procedure) on page 26 Monitoring Interface Status and Traffic Configuring sFlow Technology for Network Monitoring (CLI Procedure) sFlow technology is a network monitoring technology for high-speed switched or routed networks.
Page 43: Switches
Monitoring Traffic in Switched and Routed Networks. This example describes how to configure and use sFlow technology to monitor network traffic. Requirements on page 28 Overview and Topology on page 28 Configuration on page 28 Verification on page 30 Copyright © 2016, Juniper Networks, Inc.
Page 44: Figure 1: Sflow Technology Monitoring System
Network Management and Monitoring Feature Guide for EX9200 Switches Requirements This example uses the following hardware and software components: One EX Series switch Junos OS Release 9.3 or later for EX Series switches Overview and Topology sFlow technology samples network packets and sends the samples to a monitoring station.
Page 45 Specify the rate at which egress packets must be sampled: [edit protocols sflow] user@switch# set sample-rate egress 1000 NOTE: You can specify both egress and ingress sampling rates. If you set only the sampling rate, the sampling rate will be egress ingress disabled. Copyright © 2016, Juniper Networks, Inc.
Page 46 Network Management and Monitoring Feature Guide for EX9200 Switches NOTE: We recommend that you configure the same sampling rates on all the ports on a line card. If you configure different sampling rates are different, the lowest value is used for all ports. You could still configure different rates on different line cards.
Page 47 Related Configuring sFlow Technology for Network Monitoring (CLI Procedure) on page 26 Documentation Understanding How to Use sFlow Technology for Network Monitoring on an EX Series Switch on page 23 Copyright © 2016, Juniper Networks, Inc.
Page 49: Configuring Uplink Failure Detection
Configuring Interfaces for Uplink Failure Detection (CLI Procedure) on page 35 Understanding Uplink Failure Detection Uplink failure detection allows Juniper Networks EX Series Ethernet Switches to detect link failure on uplink interfaces and to propagate the failure to the downlink interfaces so that servers connected to those downlink interfaces can switch over to secondary interfaces.
Page 50: Failure Detection Pair
Network Management and Monitoring Feature Guide for EX9200 Switches Figure 2: Uplink Failure Detection Configuration on Switches Switch Switch link-to-monitor Switch 1 Switch 2 link-to-disable Server For uplink failure detection, you specify a group of uplink interfaces to be monitored and downlink interfaces to be brought down when an uplink fails.
Page 51: Configuring Interfaces For Uplink Failure Detection (Cli Procedure)
An interface can be configured as link-to-monitor in multiple groups. Add a downlink interface to the group: [edit protocols] user@switch# set uplink-failure-detection group group-name link-to-disable interface-name Repeat Step 4 for adding each downlink interface to the group. Copyright © 2016, Juniper Networks, Inc.
Page 52 Network Management and Monitoring Feature Guide for EX9200 Switches NOTE: After you have configured a group, use the show uplink-failure-detection group group-name command to verify that all interfaces in the group are up. Related Verifying That Uplink Failure Detection Is Working Correctly...
Page 53: Routine Monitoring
Down so-1/1/1 Down so-1/1/2 Down so-1/1/3 Down t3-1/2/0 Down t3-1/2/1 Down t3-1/2/2 Down t3-1/2/3 Down 211035 so-2/0/0 36778 so-2/0/1 192753 36782 so-2/0/2 211020 36779 so-2/0/3 211029 36776 so-2/1/0 189378 36349 so-2/1/1 Down 18747 Copyright © 2016, Juniper Networks, Inc.
Page 54: Switch
Network Management and Monitoring Feature Guide for EX9200 Switches so-2/1/2 Down 16078 so-2/1/3 80338 at-2/3/0 at-2/3/1 Down Bytes=b, Clear=c, Delta=d, Packets=p, Quit=q or ESC, Rate=r, Up=^U, Down=^D Meaning The sample output displays traffic data for active interfaces and the amount that each field has changed since the command started or since the counters were cleared by using key.
Page 55: Table 3: Output Control Keys For The Monitor Interface Command
Clear (zero) the current delta counters since was started. It monitor interface does not clear the accumulative counter. Stop the command. monitor interface See the for details on using match conditions with the CLI Explorer monitor traffic command. Copyright © 2016, Juniper Networks, Inc.
Page 57: Configuration Statements And Operational Commands
Configuration Statements: Ethernet OAM Link Fault Management on page 43 Configuration Statements: sFlow Technology on page 69 Configuration Statements: Uplink Failure Detection on page 75 Operational Commands on page 81 Operational Commands: Analyzer on page 157 Copyright © 2016, Juniper Networks, Inc.
Page 59: Configuration Statements: Ethernet Oam Link Fault Management
60 no-allow-link-events on page 60 oam on page 61 pdu-interval on page 63 pdu-threshold on page 64 protocol-down on page 64 remote-loopback on page 65 send-critical-event on page 65 symbol-period on page 66 Copyright © 2016, Juniper Networks, Inc.
Page 61: Link-Fault-Management
IEEE 802.3ah Operation, Administration, and Management (OAM) support. The remaining statements are explained separately. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Copyright © 2016, Juniper Networks, Inc.
Page 62: Action (Oam)
Network Management and Monitoring Feature Guide for EX9200 Switches Related Enabling IEEE 802.3ah OAM Support on page 6 Documentation action (OAM) Syntax action { link-down; send-critical-event; syslog; Hierarchy Level [edit protocols oam ethernet link-fault-management action-profile] Release Information Statement introduced in Junos OS Release 8.5.
Page 63: Action-Profile (Defining For Lfm)
—Name of the action profile. The remaining statements are explained separately. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring an OAM Action Profile on page 8 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 64: Allow-Remote-Loopback
Network Management and Monitoring Feature Guide for EX9200 Switches allow-remote-loopback Syntax allow-remote-loopback; Hierarchy Level [edit protocols oam link-fault-management interface interface-name negotiation-options] Release Information Statement introduced in Junos OS Release 8.4. Description Enable the remote loopback on IQ2 and IQ2-E Gigabit Ethernet interfaces, and Ethernet interfaces on the MX Series routers and EX Series switches.
Page 65: Ethernet (Protocols Oam)
{ convey-loss-threshold; hold-interval minutes; interface-status-tlv; interval (10m | 10s | 1m | 1s| 100ms); loss-threshold number; port-status-tlv; mep mep-id { auto-discovery; direction (up | down); interface interface-name (protect | working); Copyright © 2016, Juniper Networks, Inc.
Page 66 Network Management and Monitoring Feature Guide for EX9200 Switches lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect | rem-err-xcon | xcon ); priority number; remote-mep mep-id { action-profile profile-name; sla-iterator-profile profile-name { data-tlv-size size; iteration-count count-value; priority priority-value; evcs evc-id { evc-protocol cfm management-domain domain-id (management-association association-id | vpls (routing-instance instance-id);...
Page 67 Management (OAM) support. The remaining statements are explained separately. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Enabling IEEE 802.3ah OAM Support on page 6 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 68: Event (Lfm)
Network Management and Monitoring Feature Guide for EX9200 Switches event (LFM) Syntax event { link-adjacency-loss; link-event-rate frame-error count; frame-period count; frame-period-summary count; symbol-period count; protocol-down; Hierarchy Level [edit protocols oam ethernet link-fault-management action-profile] Release Information Statement introduced in Junos OS Release 8.5.
Page 69: Fast-Aps-Switch
LAN service (VPLS) environments. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Reducing APS Switchover Time in Layer 2 Circuits Documentation Copyright © 2016, Juniper Networks, Inc.
Page 70: Frame-Error
Network Management and Monitoring Feature Guide for EX9200 Switches frame-error Syntax frame-error count; Hierarchy Level [edit protocols oam ethernet link-fault-management action-profile event link-event-rate], [edit protocols oam link-fault-management interface interface-name event-thresholds] Release Information Statement introduced in Junos OS Release 8.4. Description Threshold for sending frame error events or taking the action specified in the action profile.
Page 71: Frame-Period
Related Configuring Threshold Values for Local Fault Events on an Interface on page 17 Documentation Configuring Threshold Values for Fault Events in an Action Profile on page 10 Copyright © 2016, Juniper Networks, Inc.
Page 72: Frame-Period-Summary
Network Management and Monitoring Feature Guide for EX9200 Switches frame-period-summary Syntax frame-period-summary count; Hierarchy Level [edit protocols oam ethernet link-fault-management action-profile event link-event-rate], [edit protocols oam link-fault-management interface interface-name event-thresholds] Release Information Statement introduced in Junos OS Release 8.4. Description Threshold for sending frame period summary error events or taking the action specified in the action profile.
Page 73: Interface (Oam Link-Fault Management)
OAM support. The remaining statements are described separately. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Enabling IEEE 802.3ah OAM Support on page 6 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 74: Link-Adjacency-Loss
Network Management and Monitoring Feature Guide for EX9200 Switches link-adjacency-loss Syntax link-adjacency-loss; Hierarchy Level [edit protocols oam ethernet link-fault-management action-profile event] Release Information Statement introduced in Junos OS Release 8.5. Description Loss of adjacency with IEEE 802.3ah link-fault management peer event. When included, the loss-of-adjacency event triggers the action specified under the statement.
Page 75: Link-Discovery
Configure the number of link-fault management events per second. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring Threshold Values for Fault Events in an Action Profile on page 10 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 76: Negotiation-Options
Network Management and Monitoring Feature Guide for EX9200 Switches negotiation-options Syntax negotiation-options { allow-remote-loopback; no-allow-link-events; Hierarchy Level [edit protocols oam link-fault-management interface interface-name] Release Information Statement introduced in Junos OS Release 8.4. Description Enable and disable IEEE 802.3ah Operation, Administration, and Management (OAM) features for Ethernet interfaces.
Page 77: Oam
{ auto-discovery; direction down; interface interface-name; remote-mep mep-id { action-profile profile-name; performance-monitoring { sla-iterator-profiles { profile-name { calculation-weight { delay delay-value; delay-variation delay-variation-value; cycle-time cycle-time-value; iteration-period iteration-period-value; measurement-type two-way-delay; passive; Copyright © 2016, Juniper Networks, Inc.
Page 78 Network Management and Monitoring Feature Guide for EX9200 Switches traceoptions { file filename <files number> <match regex> <size size> <world-readable | no-world-readable>; flag flag ; no-remote-trace; link-fault-management { action-profile profile-name; action { syslog; link-down; send-criticial-event event { link-adjacency-loss; link-event-rate { frame-error count;...
Page 79: Pdu-Interval
Range: 100 through 1000 milliseconds Default: 1000 milliseconds Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring the OAM PDU Interval on page 6 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 80: Pdu-Threshold
Network Management and Monitoring Feature Guide for EX9200 Switches pdu-threshold Syntax pdu-threshold threshold-value; Hierarchy Level [edit protocols oam ethernet link-fault-management interface interface-name] Release Information Statement introduced in Junos OS Release 8.2. Description For Ethernet interfaces on EX Series switches and M320, M120, MX Series, and T Series routers, specify the number of OAM PDUs to miss before an error is logged.
Page 81: Remote-Loopback
Send OAM PDUs with the critical event bit set. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Specifying the Actions to Be Taken for Link-Fault Management Events on page 19 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 82: Symbol-Period
Network Management and Monitoring Feature Guide for EX9200 Switches symbol-period Syntax symbol-period count; Hierarchy Level [edit protocols oam ethernet link-fault-management action-profile event, link-event-rate], [edit protocols oam link-fault-management interface interface-name event-thresholds] Release Information Statement introduced in Junos OS Release 8.4. Description Configure the threshold for sending symbol period events or taking the action specified in the action profile.
Page 83: Version-Ipfix (Services)
Level interface-control—To add this statement to the configuration. Related Configuring Inline Active flow Monitoring Documentation Configuring Flow Aggregation to Use IPFIX Flow Templates Configuring Inline Flow Monitoring on PTX Series Routers Copyright © 2016, Juniper Networks, Inc.
Page 85: Configuration Statements: Sflow Technology
IP address, you ensure that the IP address is not dynamic. You can specify an IPv4 or IPv6 address. Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Configuring sFlow Technology for Network Monitoring (CLI Procedure) on page 26 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 86: Collector
Network Management and Monitoring Feature Guide for EX9200 Switches collector Syntax collector { ip4/ipv6-address; udp-port port-number; Hierarchy Level [edit protocols sflow] Release Information Statement introduced in Junos OS Release 9.3 for EX Series switches. Description Configure a remote collector for sFlow network traffic monitoring. The switch sends sFlow UDP datagrams to this collector for analysis.
Page 87: Interfaces (Sflow Monitoring Technology)
Related Example: Configuring sFlow Technology to Monitor Network Traffic on EX Series Documentation Switches on page 27 Configuring sFlow Technology for Network Monitoring (CLI Procedure) on page 26 Copyright © 2016, Juniper Networks, Inc.
Page 88: Polling-Interval
Network Management and Monitoring Feature Guide for EX9200 Switches polling-interval Syntax polling-interval seconds; Hierarchy Level [edit protocols sflow], [edit protocols sflow interfaces interface-name] Release Information Statement introduced in Junos OS Release 9.3 for EX Series switches. Description Configure the interval (in seconds) that the switch waits between port statistics update messages.
Page 89: Sample-Rate
Related Configuring sFlow Technology for Network Monitoring (CLI Procedure) on page 26 Documentation Example: Configuring sFlow Technology to Monitor Network Traffic on EX Series Switches on page 27 Copyright © 2016, Juniper Networks, Inc.
Page 90: Source-Ip
Network Management and Monitoring Feature Guide for EX9200 Switches source-ip Syntax source-ip ip4/ipv6-address; Hierarchy Level [edit protocols sflow] Release Information Statement introduced in Junos OS Release 10.2 for EX Series switches. Description Configure the IP address to be used for the sFlow datagrams. By configuring an IP address, you ensure that the IP address is not dynamic.
Page 91: Configuration Statements: Uplink Failure Detection
—Generate a system log message. Required Privilege admin—To view this statement in the configuration. Level admin-control—To add this statement to the configuration. Related Configuring Interfaces for Uplink Failure Detection (CLI Procedure) on page 35 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 92: Group (Uplink Failure Detection)
Network Management and Monitoring Feature Guide for EX9200 Switches group (Uplink Failure Detection) Syntax group group-name { link-to-monitor interface-name; link-to-disable interface-name; Hierarchy Level [edit protocols uplink-failure-detection] Release Information Statement introduced in Junos OS Release 11.1 for EX Series switches. Description Configure a group of uplink and downlink interfaces for uplink failure detection.
Page 93: Link-To-Monitor
Required Privilege admin—To view this statement in the configuration. Level admin-control—To add this statement to the configuration. Related Configuring Interfaces for Uplink Failure Detection (CLI Procedure) on page 35 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 94: Traceoptions (Uplink Failure Detection)
Network Management and Monitoring Feature Guide for EX9200 Switches traceoptions (Uplink Failure Detection) Syntax traceoptions { file filename <files number> <no-stamp> <replace> <size size> <world-readable | no-world-readable>; flag flag; Hierarchy Level [edit protocols uplink-failure-detection] Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.
Page 95: Uplink-Failure-Detection
The remaining statements are explained separately. Required Privilege admin—To view this statement in the configuration. Level admin-control—To add this statement to the configuration. Related Configuring Interfaces for Uplink Failure Detection (CLI Procedure) on page 35 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 97: Operational Commands
CHAPTER 8 Operational Commands monitor traffic ping show oam ethernet link-fault-management show interfaces (Fast Ethernet) show interfaces (10-Gigabit Ethernet) show sflow collector show sflow show sflow interface traceroute traceroute monitor Copyright © 2016, Juniper Networks, Inc.
Page 98: Monitor Traffic
Network Management and Monitoring Feature Guide for EX9200 Switches monitor traffic Syntax monitor traffic <brief | detail | extensive> <absolute-sequence> <count count> <interface interface-name> <layer2-headers> <matching matching> <no-domain-names> <no-promiscuous> <no-resolve> <no-timestamp> <print-ascii> <print-hex> <resolve-timeout> <size size> Release Information Command introduced before Junos OS Release 7.4.
Page 100: Table 4: Match Conditions For The Monitor Traffic Command
Network Management and Monitoring Feature Guide for EX9200 Switches Table 4: Match Conditions for the monitor traffic Command Match Type Condition Description Entity Matches packets that contain the specified host [address | hostname] address or hostname. The protocol match conditions...
Page 101 Matches packets whose headers contain the proto ip-protocol-number specified IP protocol number. Matches all RARP packets. rarp Matches all TCP datagrams. Matches all UDP datagrams. To combine expressions, use the logical operators listed in Table 5 on page Copyright © 2016, Juniper Networks, Inc.
Page 102: Table 5: Logical Operators For The Monitor Traffic Command
Network Management and Monitoring Feature Guide for EX9200 Switches Table 5: Logical Operators for the monitor traffic Command Logical Operator (Highest to Lowest Precedence) Description Logical NOT. If the first condition does not match, the next condition is evaluated. &&...
Page 103: Table 6: Arithmetic And Relational Operators For The Monitor Traffic
If the first expression is greater than or equal to the second, the packet matches. < If the first expression is less than the second, the packet matches. > If the first expression is greater than the second, the packet matches. Copyright © 2016, Juniper Networks, Inc.
Page 104: Monitor Traffic Count
Network Management and Monitoring Feature Guide for EX9200 Switches Table 6: Arithmetic and Relational Operators for the monitor traffic Command (continued) Arithmetic or Relational Operator Description If the compared expressions are equal, the packet matches. If the compared expressions are unequal, the packet matches.
Page 105: Monitor Traffic Extensive (Absolute Sequence)
0 win 17680 (DF) [tos 0x10] (ttl 64, id 52376) monitor traffic interface user@host> monitor traffic interface fxp0 listening on fxp0.0 18:17:28.800650 In server.home.net.723 > host1-0.lab.home.net.log 18:17:28.800733 Out host2-0.lab.home.net.login > server.home.net.7 18:17:28.817813 In host30.lab.home.net.syslog > host40.home0 Copyright © 2016, Juniper Networks, Inc.
Page 106: Monitor Traffic Matching
Network Management and Monitoring Feature Guide for EX9200 Switches 18:17:28.817846 In host30.lab.home.net.syslog > host40.home0 monitor traffic matching user@host> monitor traffic matching "net 192.168.1.0/24" verbose output suppressed, use <detail> or <extensive> for full protocol decode Address resolution is ON. Use <no-resolve> to avoid any reverse lookup delay.
Page 107: Monitor Traffic (Qfx3500 Switch)
Listening on me0, capture size 96 bytes 09:23:17.728737 In IP 172.19.10.9 > 10.10.211.93: ICMP echo request, id 1, seq 322, length 40 09:23:17.728780 Out IP 10.10.211.93 > 172.19.10.9: ICMP echo reply, id 1, seq 322, length 40 Copyright © 2016, Juniper Networks, Inc.
Page 108: Monitor Traffic Matching Ip Protocol Number
Network Management and Monitoring Feature Guide for EX9200 Switches 09:23:18.735848 In IP 172.19.10.9 > 10.10.211.93: ICMP echo request, id 1, seq 323, length 40 09:23:18.735891 Out IP 10.10.211.93 > 172.19.10.9: ICMP echo reply, id 1, seq 323, length 40 09:23:19.749732 In IP 172.19.10.9 >...
Page 109: Monitor Traffic Matching Port
172.29.102.9.56714: P 1006:1542(536) ack 719 win 33320 13:14:19.734097 In IP 192.0.2.22.56714 > 10.19.300.05.22: . ack 1542 win 32768 13:14:19.843574 In IP truncated-ip - 508 bytes missing! 192.0.2.22.56714 > 10.94.211.93.22: P 719:1247(528) ack 1542 win 32768 Copyright © 2016, Juniper Networks, Inc.
Page 110: Ping
Network Management and Monitoring Feature Guide for EX9200 Switches ping List of Syntax Syntax on page 94 Syntax (QFX Series) on page 94 Syntax ping host <bypass-routing> <count requests> <detail> <do-not-fragment> <inet | inet6> <interface source-interface> <interval seconds> <logical-system logical-system-name>...
Page 111 Alternatively, enter the command and set cli logical-system logical-system-name then run the ping command. To return to the main router or switch, enter the clear command. cli logical-system Copyright © 2016, Juniper Networks, Inc.
Page 112 Network Management and Monitoring Feature Guide for EX9200 Switches —(Optional) Intermediate loose source route entry (IPv4). Open a set loose-source value of values. mac-address mac-address —(Optional) Ping the physical or hardware address of the remote system you are trying to reach.
Page 113: Output Fields
208 bytes from 192.0.2.0: icmp_seq=3 ttl=253 time=1.803 ms 208 bytes from 192.0.2.0: icmp_seq=4 ttl=253 time=17.898 ms --- device1.example.com ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 1.759/5.075/17.898 ms Copyright © 2016, Juniper Networks, Inc.
Page 114: Show Oam Ethernet Link-Fault-Management
Network Management and Monitoring Feature Guide for EX9200 Switches show oam ethernet link-fault-management Syntax show oam ethernet link-fault-management <brief | detail> <interface-name> Release Information Command introduced in Junos OS Release 8.2. Description On EX Series switches and M320, M120, MX Series, T320, and T640 routers, display Operation, Administration, and Management (OAM) link fault management information for Ethernet interfaces.
Page 115 Indicates that a loopback issue is either found, not found, or unknown when All levels Loop Status loopback tracking is enabled. Detect LOC Indicates that loss-of-continuity (LOC) detection is enabled or disabled. All levels Copyright © 2016, Juniper Networks, Inc.
Page 116 Network Management and Monitoring Feature Guide for EX9200 Switches Table 7: show oam ethernet link-fault-management Output Fields (continued) Field Name Field Description Level of Output Indicates that a LOC issue is either found, not found, or unknown when Detect All levels LOC status LOC is enabled.
Page 117 The number of symbol errors in the period reported in the transmitted event Errors in period detail PDU. Total errors The number of errored symbols reported in event TLVs that have been detail transmitted since the OAM sublayer was reset. Copyright © 2016, Juniper Networks, Inc.
Page 118 Network Management and Monitoring Feature Guide for EX9200 Switches Table 7: show oam ethernet link-fault-management Output Fields (continued) Field Name Field Description Level of Output OAM Current Symbol Error Event Information Events The number of symbol error TLVs that have been generated regardless of detail whether the threshold for sending event TLVs has been crossed.
Page 119 Errors in period: 0, Total errors: 0 Remote entity information: Remote MUX action: forwarding, Remote parser action: forwarding Discovery mode: active, Unidirectional mode: unsupported Remote loopback mode: supported, Link events: supported Variable requests: unsupported, Remote in ISSU Copyright © 2016, Juniper Networks, Inc.
Page 120: Show Interfaces (Fast Ethernet)
Network Management and Monitoring Feature Guide for EX9200 Switches show interfaces (Fast Ethernet) Syntax show interfaces interface-type <brief | detail | extensive | terse> <descriptions> <media> <snmp-index snmp-index> <statistics> Release Information Command introduced before Junos OS Release 7.4. Description Display status information about the specified Fast Ethernet interface.
Page 121 (10-Gigabit Ethernet dense wavelength-division multiplexing [DWDM] All levels interfaces) Displays the configured wavelength, in nanometers (nm). (10-Gigabit Ethernet DWDM interfaces only) Displays the frequency associated All levels Frequency with the configured wavelength, in terahertz (THz). Copyright © 2016, Juniper Networks, Inc.
Page 122 Network Management and Monitoring Feature Guide for EX9200 Switches Table 8: show interfaces Fast Ethernet Output Fields (continued) Field Name Field Description Level of Output Number of CoS queues configured. none CoS queues detail extensive (GigabitEthernet intelligent queuing 2 (IQ2) interfaces only) Number of CoS...
Page 123 —Number of FIFO errors in the receive direction that are reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably malfunctioning. —Sum of transmit drops. Resource errors Copyright © 2016, Juniper Networks, Inc.
Page 124 Network Management and Monitoring Feature Guide for EX9200 Switches Table 8: show interfaces Fast Ethernet Output Fields (continued) Field Name Field Description Level of Output Output errors on the interface. The following paragraphs explain the counters Output errors extensive whose meaning might not be obvious: —Number of times the interface has gone from...
Page 125 —The number of seconds during which at least one bit error rate (BER) occurred while the PCS receiver is operating in normal mode. Errored blocks —The number of seconds when at least one errored block occurred while the PCS receiver is operating in normal mode. Copyright © 2016, Juniper Networks, Inc.
Page 126 Network Management and Monitoring Feature Guide for EX9200 Switches Table 8: show interfaces Fast Ethernet Output Fields (continued) Field Name Field Description Level of Output statistics reported by the PIC's MAC subsystem, including MAC statistics Receive Transmit extensive the following: —Total number of octets and packets.
Page 127 —Number of times that the defect has gone from inactive to active. Count —State of the error. Any state other than indicates a problem. State Subfields are: —Phase-locked loop PHY Lock —Loss of optical signal PHY Light Copyright © 2016, Juniper Networks, Inc.
Page 128 Network Management and Monitoring Feature Guide for EX9200 Switches Table 8: show interfaces Fast Ethernet Output Fields (continued) Field Name Field Description Level of Output (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET error information: WIS section extensive —Number of seconds the defect has been active.
Page 129 —Path payload (signal) label mismatch ES-P —Errored seconds (near-end STS path) —Severely errored seconds (near-end STS path) SES-P —Unavailable seconds (near-end STS path) UAS-P —Severely errored seconds (far-end STS path) SES-PFE —Unavailable seconds (far-end STS path) UAS-PFE Copyright © 2016, Juniper Networks, Inc.
Page 130 (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET/SDH interfaces allow Received path extensive path trace bytes to be sent inband across the SONET/SDH link. Juniper Networks trace, Transmitted and other routing device manufacturers use these bytes to help diagnose path trace...
Page 131 SNMP interface index number for the logical interface. none SNMP ifIndex detail extensive Unique number for use by Juniper Networks technical support only. Generation detail extensive Information about the logical interface. Possible values are described in the All levels Flags “Logical Interface Flags”...
Page 132 Network Management and Monitoring Feature Guide for EX9200 Switches Table 8: show interfaces Fast Ethernet Output Fields (continued) Field Name Field Description Level of Output IP demultiplexing (demux) value that appears if this interface is used as the none Demux: detail extensive demux underlying interface.
Page 133 Local detail extensive Broadcast address of the logical interlace. none Broadcast detail extensive Unique number for use by Juniper Networks technical support only. Generation detail extensive Sample Output show interfaces (Fast Ethernet) user@host> show interfaces fe-0/0/0 Physical interface: fe-0/0/0, Enabled, Physical link is Up...
Page 134 Network Management and Monitoring Feature Guide for EX9200 Switches Protocol inet, MTU: 1500 Flags: None Addresses, Flags: Is-Preferred Is-Primary Destination: 203.0.113/24, Local: 203.0.113.1, Broadcast: 203.0.113.255 show interfaces brief (Fast Ethernet) user@host> show interfaces fe-0/0/0 brief Physical interface: fe-0/0/0, Enabled, Physical link is Up...
Page 135 Logical interface fe-0/0/0.0 (Index 66) (SNMP ifIndex 198) (Generation 67) Flags: SNMP-Traps Encapsulation: ENET2 Protocol inet, MTU: 1500, Generation: 105, Route table: 0 Flags: None Addresses, Flags: Is-Preferred Is-Primary Destination: 203.0.113/24, Local: 203.0.113.1, Broadcast: 203.0.113.255, Generation: 136 Copyright © 2016, Juniper Networks, Inc.
Page 136: Show Interfaces (10-Gigabit Ethernet)
Network Management and Monitoring Feature Guide for EX9200 Switches show interfaces (10-Gigabit Ethernet) Syntax show interfaces xe-fpc/pic/port <brief | detail | extensive | terse> <descriptions> <media> <snmp-index snmp-index> <statistics> Release Information Command introduced in Junos OS Release 8.0. Description (M320, M120, MX Series, and T Series routers only) Display status information about the specified 10-Gigabit Ethernet interface.
Page 137: Table 9: Show Interfaces Gigabit Ethernet Output Fields
Interface index detail extensive SNMP index number for the physical interface. none SNMP ifIndex detail extensive Unique number for use by Juniper Networks technical support only. Generation detail extensive Encapsulation being used on the physical interface. All levels Link-level type Maximum transmission unit size on the physical interface.
Page 138 Network Management and Monitoring Feature Guide for EX9200 Switches Table 9: show interfaces Gigabit Ethernet Output Fields (continued) Field Name Field Description Level of Output Information about the link. Possible values are described in the “Links Flags” All levels Link flags section under Common Output Fields Description.
Page 139 —Number of FIFO errors in the receive direction that are reported by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably malfunctioning. Resource errors —Sum of transmit drops. Copyright © 2016, Juniper Networks, Inc.
Page 140 Network Management and Monitoring Feature Guide for EX9200 Switches Table 9: show interfaces Gigabit Ethernet Output Fields (continued) Field Name Field Description Level of Output Output errors on the interface. The following paragraphs explain the counters Output errors extensive whose meaning might not be obvious: —Number of times the interface has gone from...
Page 141 Corrected Errors —The count of corrected errors in the last second. —The corrected error ratio in the last 25 seconds. For Corrected Error Ratio example, 1e-7 is 1 error per 10 million bits. Copyright © 2016, Juniper Networks, Inc.
Page 142 Network Management and Monitoring Feature Guide for EX9200 Switches Table 9: show interfaces Gigabit Ethernet Output Fields (continued) Field Name Field Description Level of Output OTN FEC excessive or degraded error alarms triggered on the interface. OTN FEC alarms detail extensive —OTU FEC Degrade defect.
Page 143 “invalid data symbol error.” APS/PCC0: 0x02, APS/PCC1: 0x11, APS/PCC2: 0x47, APS/PCC3: 0x58 Payload OTN Received extensive Type: 0x08 Overhead Bytes APS/PCC0: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00 OTN Transmitted extensive Payload Type: 0x08 Overhead Bytes Copyright © 2016, Juniper Networks, Inc.
Page 144 Network Management and Monitoring Feature Guide for EX9200 Switches Table 9: show interfaces Gigabit Ethernet Output Fields (continued) Field Name Field Description Level of Output statistics reported by the PIC's MAC address filter Filter statistics Receive Transmit extensive subsystem. The filtering is done by the content-addressable memory (CAM) on the PIC.
Page 145 —Bit error rate defect (signal degradation) BERR-SD ES-L —Errored seconds (near-end line) —Severely errored seconds (near-end line) SES-L —Unavailable seconds (near-end line) UAS-L —Errored seconds (far-end line) ES-LFE —Severely errored seconds (far-end line) SES-LFE UAS-LFE —Unavailable seconds (far-end line) Copyright © 2016, Juniper Networks, Inc.
Page 146 Network Management and Monitoring Feature Guide for EX9200 Switches Table 9: show interfaces Gigabit Ethernet Output Fields (continued) Field Name Field Description Level of Output (10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects, WIS path extensive plus counts of specific SONET errors with detailed information.
Page 147 (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET/SDH interfaces allow Received path extensive path trace bytes to be sent inband across the SONET/SDH link. Juniper Networks trace, Transmitted and other router manufacturers use these bytes to help diagnose path trace...
Page 148 Network Management and Monitoring Feature Guide for EX9200 Switches Table 9: show interfaces Gigabit Ethernet Output Fields (continued) Field Name Field Description Level of Output Information about the CoS queue for the physical interface. CoS information extensive —Queue number and its associated user-configured CoS transmit queue forwarding class name.
Page 149 Number of IPv6 transit bytes and packets received and transmitted on the IPv6 transit extensive logical interface if IPv6 statistics tracking is enabled. statistics Number and rate of bytes and packets destined to the routing device. Local statistics extensive Copyright © 2016, Juniper Networks, Inc.
Page 150 Network Management and Monitoring Feature Guide for EX9200 Switches Table 9: show interfaces Gigabit Ethernet Output Fields (continued) Field Name Field Description Level of Output Number and rate of bytes and packets transiting the switch. Transit statistics extensive NOTE: For Gigabit Ethernet intelligent queuing 2 (IQ2) interfaces, the logical interface egress statistics might not accurately reflect the traffic on the wire when output shaping is applied.
Page 151: Table 10: Gigabit Ethernet Iq Pic Traffic And Mac Statistics By Interface
Table 9: show interfaces Gigabit Ethernet Output Fields (continued) Field Name Field Description Level of Output Unique number for use by Juniper Networks technical support only. Generation detail extensive For Gigabit Ethernet IQ PICs, traffic and MAC statistics output varies.
Page 152: Input Bytes
Network Management and Monitoring Feature Guide for EX9200 Switches None, Source filtering: Enabled, Flow control: Enabled Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x4000 Link flags : None CoS queues : 8 supported, 4 maximum usable queues Schedulers...
Page 153: Bps
Output packets: IPv6 transit statistics: Input bytes Output bytes Input packets: Output packets: Local statistics: Input bytes Output bytes Input packets: Output packets: Transit statistics: Input bytes 0 bps Output bytes 0 bps Copyright © 2016, Juniper Networks, Inc.
Page 154: Input Packets: 0 Pps
Network Management and Monitoring Feature Guide for EX9200 Switches Input packets: 0 pps Output packets: 0 pps IPv6 transit statistics: Input bytes Output bytes Input packets: Output packets: Protocol inet, MTU: 1500, Generation: 253, Route table: 0 Addresses, Flags: Is-Preferred Is-Primary Destination: 192.0.2/24, Local: 192.0.2.1, Broadcast: 192.0.2.255,...
Page 155 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ....Transmitted path trace: orissa so-1/0/0 6f 72 69 73 73 61 20 73 6f 2d 31 2f 30 2f 30 00 orissa so-1/0/0. Packet Forwarding Engine configuration: Copyright © 2016, Juniper Networks, Inc.
Page 156: Pps
Network Management and Monitoring Feature Guide for EX9200 Switches Destination slot: 1 CoS information: CoS transmit queue Bandwidth Buffer Priority Limit bytes 0 best-effort 950000000 none 3 network-control 50000000 none show interfaces extensive (10-Gigabit Ethernet, DWDM OTN PIC) user@host> show interfaces ge-7/0/0 extensive...
Page 157 Defect Active TTIM 67164 Defect Active 67164 Defect Active TCA-ES TCA-SES TCA-UAS TCA-BBE Received DAPI: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ....Received SAPI: Copyright © 2016, Juniper Networks, Inc.
Page 158 Network Management and Monitoring Feature Guide for EX9200 Switches 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ....Transmitted DAPI: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ....
Page 159 Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps, Unidirectional: Rx-Only Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x4000 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Copyright © 2016, Juniper Networks, Inc.
Page 160 Network Management and Monitoring Feature Guide for EX9200 Switches Hold-times : Up 0 ms, Down 0 ms Current address: 00:00:5e:00:53:83, Hardware address: 00:00:5e:00:53:83 Last flapped : 2007-06-01 09:08:22 PDT (3d 02:31 ago) Statistics last cleared: Never Traffic statistics: Input bytes...
Page 161: Show Sflow Collector
UDP port number. All levels UDP port Number of samples sent to collector. All levels No of samples Sample Output show sflow collector IP-address UDP-Port No of samples 10.204.32.46 5600 1000 100.204.32.76 3400 1000 Copyright © 2016, Juniper Networks, Inc.
Page 162: Show Sflow
Network Management and Monitoring Feature Guide for EX9200 Switches show sflow Syntax show sflow <collector> <interface> Release Information Command introduced in Junos OS Release 9.3 for EX Series switches. Description Display default sFlow technology configuration information. Options —Display default sFlow technology configuration information.
Page 163 : Enabled Sample rate egress : 1:1000 Sample rate ingress : 1: 2048: Disabled Sample limit : 300 packets/second Polling interval : 20 seconds Agent ID : 10.93.54.7 Source IP address : 10.93.54.7 Copyright © 2016, Juniper Networks, Inc.
Page 164: Show Sflow Interface
Network Management and Monitoring Feature Guide for EX9200 Switches show sflow interface Syntax show sflow interface Release Information Command introduced in Junos OS Release 9.3 for EX Series switches. Description Display the interfaces on which sFlow technology is enabled and the sampling parameters.
Page 166: Traceroute
Network Management and Monitoring Feature Guide for EX9200 Switches traceroute List of Syntax Syntax on page 150 Syntax (QFX Series and OCX Series) on page 150 Syntax traceroute host <as-number-lookup> <bypass-routing> <clns> <gateway address> <inet | inet6> <interface interface-name> <logical system logical-system-name>...
Page 167 CE router does not show hop-by-hop information. —(Optional) Name of the routing instance for the routing-instance routing-instance-name traceroute attempt. source source-address —(Optional) Source address of the outgoing traceroute packets. Copyright © 2016, Juniper Networks, Inc.
Page 168: Table 14: Traceroute Output Fields
Network Management and Monitoring Feature Guide for EX9200 Switches —(Optional) Value to include in the IP type-of-service (ToS) field. The range of tos value values is through ttl value —(Optional) Maximum time-to-live value to include in the traceroute request. The range of values is...
Page 169 (Through an MPLS LSP) user@host> traceroute mpls1 traceroute to 10.168.1.224 (10.168.1.224), 30 hops max, 40 byte packets mpls1-sr0.company.net (10.168.200.101) 0.555 ms 0.393 ms 0.367 ms MPLS Label=1024 CoS=0 TTL=1 mpls5-lo0.company.net (10.168.1.224) 0.420 ms 0.394 ms 0.401 ms Copyright © 2016, Juniper Networks, Inc.
Page 170: Traceroute Monitor
Network Management and Monitoring Feature Guide for EX9200 Switches traceroute monitor List of Syntax Syntax on page 154 Syntax (QFX Series) on page 154 Syntax traceroute monitor host <count value> <inet | inet 6> <interval seconds> <no resolve> <size value>...
Page 171: Table 15: Traceroute Monitor Output Fields
Standard deviation of round-trip times, in milliseconds, to the router StDev at this hop. Sample Output traceroute monitor user@host> traceroute monitor 10.16.0.1 Loss% Last Best Wrst StDev Host 1. 10.17.41.254 0.0% 2. example.net 0.0% 3. example2.net 0.0% Copyright © 2016, Juniper Networks, Inc.
Page 174: Show Forwarding-Options Analyzer
Network Management and Monitoring Feature Guide for EX9200 Switches show forwarding-options analyzer Syntax show forwarding-options analyzer analyzer-name Release Information Hierarchy level [edit forwarding-options] introduced in Junos OS Release 13.2X50-D10 (ELS). Description Display information about analyzers configured for mirroring. Options analyzer-name —(Optional) Displays the status of a specific analyzer on the switch.

Juniper EX9200 Features Manual

Table of Contents

Chapter 1 Configuring Ethernet OAM Link Fault Management

Chapter 2 Configuring Sflow Monitoring Technology

Chapter 3 Configuring Uplink Failure Detection

Chapter 4 Routine Monitoring

Chapter 5 Configuration Statements: Ethernet OAM Link Fault Management

Configuration Statements: Sflow Technology

Chapter 6 Configuration Statements: Sflow Technology

Configuration Statements: Uplink Failure Detection

Chapter 7 Configuration Statements: Uplink Failure Detection

Chapter 8 Operational Commands

Monitor Traffic Count/Monitor Traffic Detail Count

Cos Information

Quick Links

Chapters

Need help?

Questions and answers

Related Manuals for Juniper EX9200

Summary of Contents for Juniper EX9200

Table of Contents