Juniper EX9200 Features Manual
  1. Manuals
  2. Brands
  3. Juniper Manuals
  4. Network Router
  5. EX9200 Series
  6. Features manual

Juniper EX9200 Features Manual

Flow monitoring feature guide ex series
Hide thumbs Also See for EX9200:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Feature Manual
Flow Monitoring Feature Guide for EX9200
Switches
Modified: 2017-01-24
Copyright © 2017, Juniper Networks, Inc.

Advertisement

Table of Contents
loading

Related Manuals for Juniper EX9200

Summary of Contents for Juniper EX9200

  • Page 1 Flow Monitoring Feature Guide for EX9200 Switches Modified: 2017-01-24 Copyright © 2017, Juniper Networks, Inc.
  • 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 3: Table Of Contents

    ........... . . 30 Copyright © 2017, Juniper Networks, Inc.
  • Page 4 Flow Monitoring Feature Guide for EX9200 Switches family (Monitoring) ..........31 filter .

  • Page 5: List Of Figures

    Understanding Flow Monitoring ........3 Figure 1: Active Monitoring Configuration Topology ......5 Copyright © 2017, Juniper Networks, Inc.
  • Page 6 Flow Monitoring Feature Guide for EX9200 Switches Copyright © 2017, Juniper Networks, Inc.
  • Page 7 Table 10: show services accounting status Output Fields ....72 Table 11: show services accounting usage Output Fields ....75 Copyright © 2017, Juniper Networks, Inc.
  • Page 8 Flow Monitoring Feature Guide for EX9200 Switches viii Copyright © 2017, Juniper Networks, Inc.

  • Page 9: 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 10: Merging A Full Example

    Flow 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 11: 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 © 2017, Juniper Networks, Inc.
  • Page 12 Flow 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 13: 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 14: Opening A Case With Jtac

    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 15: Overview

    PART 1 Overview Understanding Flow Monitoring on page 3 Copyright © 2017, Juniper Networks, Inc.
  • Page 16 Flow Monitoring Feature Guide for EX9200 Switches Copyright © 2017, Juniper Networks, Inc.

  • Page 17: Understanding Flow Monitoring

    Active Flow Monitoring Overview on page 3 Active Flow Monitoring Overview Using a Juniper Networks M Series Multiservice Edge or T Series Core router or EX9200, a selection of PICs (including the Monitoring Services PIC, Adaptive Services [AS] PIC, Multiservices PIC, or Multiservices DPC) and other networking hardware, you can monitor traffic flow and export the monitored traffic.
  • Page 18 Flow Monitoring Feature Guide for EX9200 Switches Starting with Junos OS Release 11.4, support for active monitoring is extended to logical systems running on T Series and MX Series routers. A logical system is a partition created from a physical router that performs independent routing tasks. Several logical systems in a single router with their own interfaces, policies, instances, and routing tables can perform functions handled by several different routers.
  • Page 19 All other traffic is port-mirrored to the Monitoring Services PIC. Port mirroring copies each packet and sends the copies to the port-mirroring next hop (in this case, a Monitoring Services PIC). The original packets are forwarded out of the router as usual. Copyright © 2017, Juniper Networks, Inc.
  • Page 20 Flow Monitoring Feature Guide for EX9200 Switches Related Configuring Flow Monitoring on page 9 Documentation Directing Replicated Flows to Multiple Flow Servers Configuring Services Interface Redundancy with Flow Monitoring Example: Configuring Active Monitoring on Logical Systems Copyright © 2017, Juniper Networks, Inc.

  • Page 21: Configuring Flow Monitoring

    PART 2 Configuring Flow Monitoring Configuring Basic Flow Monitoring on page 9 Configuring Active Flow Monitoring on page 15 Copyright © 2017, Juniper Networks, Inc.
  • Page 22 Flow Monitoring Feature Guide for EX9200 Switches Copyright © 2017, Juniper Networks, Inc.

  • Page 23: Configuring Basic Flow Monitoring

    { unit logical-unit-number { family inet { address address { destination address; filter group filter-group-number; input filter-name; output filter-name; sampling [ input output ]; multiservice-options (core-dump | no-core-dump); (syslog | no-syslog); flow-control-options { Copyright © 2017, Juniper Networks, Inc.
  • Page 24 Flow Monitoring Feature Guide for EX9200 Switches down-on-flow-control; dump-on-flow-control; reset-on-flow-control; Specify the physical and logical location of the flow-monitoring interface. You cannot unit 0 , because it is already used by internal processes. Specify the source and destination addresses. The...

  • Page 25: Configuring Flow-Monitoring Properties

    SNMP index of the input interface. You can override the default by including a specific value. The input-interface-index values are exported in fields present in the cflowd version 5 flow output-interface-index format. Copyright © 2017, Juniper Networks, Inc.

  • Page 26: Exporting Flows

    Flow Monitoring Feature Guide for EX9200 Switches Exporting Flows To direct traffic to a flow collection interface, include the flow-export-destination statement. For more information about flow collection, see “Active Flow Monitoring Overview” on page To configure the cflowd version number, include the...

  • Page 27: Example: Configuring Flow Monitoring

    1; input-interface-index 45; output-interface-index 55; source-address 192.168.245.1; interface mo-4/2/0.1 { engine-id 3; engine-type 1; input-interface-index 46; output-interface-index 56; source-address 192.168.245.1; interface mo-4/3/0.1 { engine-id 4; engine-type 1; input-interface-index 47; output-interface-index 57; source-address 192.168.245.1; Copyright © 2017, Juniper Networks, Inc.
  • Page 28 Flow Monitoring Feature Guide for EX9200 Switches Release History Table Release Description 15.1 Starting with Junos OS Release 15.1, the multiservices PIC management daemon core file is generated when a prolonged flow control failure occurs and when you configure the setting to generate a core dump during prolonged flow control (by...

  • Page 29: Configuring Active Flow Monitoring

    IPv4 table is assigned a default value of fifteen 256K areas. The IPv6 table is assigned a default value of 1024, and the VPLS table is assigned a default value of 1024. When anticipated traffic volume requires larger tables, allocate larger tables. Copyright © 2017, Juniper Networks, Inc.
  • Page 30 Flow Monitoring Feature Guide for EX9200 Switches NOTE: The functionality to log the cflowd records in a log file before they are exported to a cflowd server (by including the statement at the local-dump [edit forwarding-options sampling instance instance-name family (inet |inet6...
  • Page 31 This statement is not required for ingress and egress VLAN ID reporting on interfaces. The following example shows the sampling configuration for an instance that supports inline active flow monitoring on family inet and PIC-based sampling on family inet6 Copyright © 2017, Juniper Networks, Inc.
  • Page 32 Flow Monitoring Feature Guide for EX9200 Switches [edit forwarding-options] sampling { instance { sample-ins1 { input { rate 1; family inet { output { flow-server 192.0.2.2 { port 2055; version-ipfix { template { ipv4; inline-jflow { source-address 10.11.12.13; family inet6 { output { flow-server 192.0.2.2 {...
  • Page 33 Starting in Junos OS Release 16.1R1 and 15.1F2, any change in the configured size of flow hash table sizes does not initiate an automatic reboot of the FPC. Related Configuring Inline Active Flow Monitoring on MX80 Routers Documentation inline-jflow Copyright © 2017, Juniper Networks, Inc.
  • Page 34 Flow Monitoring Feature Guide for EX9200 Switches Copyright © 2017, Juniper Networks, Inc.

  • Page 35: Configuration Statements And Operational Commands

    PART 3 Configuration Statements and Operational Commands Configuration Statements on page 23 Operational Commands on page 47 Copyright © 2017, Juniper Networks, Inc.
  • Page 36 Flow Monitoring Feature Guide for EX9200 Switches Copyright © 2017, Juniper Networks, Inc.

  • Page 37: Configuration Statements

    41 output (Monitoring) on page 42 port (Flow Monitoring) on page 43 sampling (Interfaces) on page 43 source-address (Forwarding Options) on page 44 syslog on page 44 unit on page 45 Copyright © 2017, Juniper Networks, Inc.

  • Page 38: Address (Interfaces)

    Flow Monitoring Feature Guide for EX9200 Switches address (Interfaces) Syntax address address { destination address; Hierarchy Level [edit interfaces interface-name unit logical-unit-numberfamily family] Release Information Statement introduced before Junos OS Release 7.4. Description Configure the interface address. Options address —Address of the interface.

  • Page 39: Cflowd (Discard Accounting)

    —IP address or identifier of the host system (the workstation running the cflowd utility). 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 Flow Aggregation Documentation Copyright © 2017, Juniper Networks, Inc.

  • Page 40: Core-Dump

    Flow Monitoring Feature Guide for EX9200 Switches core-dump Syntax (core-dump | no-core-dump); Hierarchy Level [edit interfaces mo-fpc/pic/port multiservice-options] Release Information Statement introduced before Junos OS Release 7.4. Description A useful tool for isolating the cause of a problem. Core dumping is enabled by default.

  • Page 41: Destination (Interfaces)

    Related Configuring Linear RED Profiles on ATM Interfaces Documentation Multilink and Link Services Logical Interface Configuration Overview Configuring Encryption Interfaces Configuring Traffic Sampling Configuring Flow Monitoring on page 9 Configuring Unicast Tunnels Copyright © 2017, Juniper Networks, Inc.

  • Page 42: Engine-Id (Forwarding Options)

    Flow Monitoring Feature Guide for EX9200 Switches engine-id (Forwarding Options) Syntax engine-id number; Hierarchy Level [edit forwarding-options accounting name output interface interface-name], [edit forwarding-options monitoring name output interface interface-name], [edit forwarding-options sampling instance instance-name family (inet | inet6 | mpls) output...

  • Page 43: Engine-Type

    —Platform-specific accounting interface type. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring Traffic Sampling Documentation Configuring Flow Monitoring on page 9 Configuring Discard Accounting Copyright © 2017, Juniper Networks, Inc.

  • Page 44: Export-Format

    Flow Monitoring Feature Guide for EX9200 Switches export-format Syntax export-format format; Hierarchy Level [edit forwarding-options monitoring name output] Release Information Statement introduced before Junos OS Release 7.4. Description Flow monitoring export format. Options format —Format of the flows. Values: 5 or 8...

  • Page 45: Family (Monitoring)

    Specify input and output interfaces and properties for flow monitoring. Only IPv4 ( inet is supported. The 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 Flow Monitoring on page 9 Documentation Copyright © 2017, Juniper Networks, Inc.

  • Page 46: Filter

    Flow Monitoring Feature Guide for EX9200 Switches filter Syntax filter { input filter-name; output filter-name; group filter-group-number; Hierarchy Level [edit interfaces interface-name unit logical-unit-number family inet] Release Information Statement introduced before Junos OS Release 7.4. Description Apply a firewall filter to an interface. You can also use filters for encrypted traffic.

  • Page 47: Flow-Active-Timeout

    Level interface-control—To add this statement to the configuration. Related Configuring Time Periods When Flow Monitoring Is Active and Inactive on page 12 Documentation Configuring the Version 9 Template Properties Copyright © 2017, Juniper Networks, Inc.

  • Page 48: Flow-Export-Destination

    Flow Monitoring Feature Guide for EX9200 Switches Configuring Flow Aggregation to Use IPFIX Flow Templates flow-export-destination Syntax flow-export-destination { (cflowd-collector | collector-pic); Hierarchy Level [edit forwarding-options monitoring group-name family inet output] Release Information Statement introduced before Junos OS Release 7.4.

  • Page 49: Flow-Inactive-Timeout

    Related Configuring Time Periods When Flow Monitoring Is Active and Inactive on page 12 Documentation Configuring the Version 9 Template Properties Configuring Flow Aggregation to Use IPFIX Flow Templates Copyright © 2017, Juniper Networks, Inc.

  • Page 50: Flow-Table-Size

    Flow Monitoring Feature Guide for EX9200 Switches flow-table-size Syntax flow-table-size { ipv4-flow-table-size units; ipv6-extended-attrib; ipv6-flow-table-size units; mpls-flow-table-size units; vpls-flow-table-size units; Hierarchy Level [edit chassis fpc slot-number inline-services] Release Information Statement introduced in Junos OS Release 12.1. option added in Junos OS Release 14.2 for MX Series routers.

  • Page 51: Input-Interface-Index

    —Name of the interface. interface-name 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 Discard Accounting Documentation Configuring Traffic Sampling Copyright © 2017, Juniper Networks, Inc.

  • Page 52: Ipv4-Flow-Table-Size

    Flow Monitoring Feature Guide for EX9200 Switches ipv4-flow-table-size Syntax ipv4-flow-table-size units; Hierarchy Level [edit chassis fpc slot-number inline-services flow-table-size] Description Configure the size of the IPv4 flow table in units of 256K entries. NOTE: Prior to Junos OS Release 16.1R1 and 15.1F2, any changes in the configured size of the flow table initiates an automatic reboot of the FPC, and we recommend that you run this command in a maintenance window.

  • Page 53: Ipv6-Flow-Table-Size

    Default: If number of units is not specified, 1024 flow entries are allocated for IPv6. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring Inline Active Flow Monitoring on page 15 Documentation Copyright © 2017, Juniper Networks, Inc.

  • Page 54: Monitoring

    Flow Monitoring Feature Guide for EX9200 Switches monitoring Syntax monitoring name { family inet { output cflowd hostname port-number; export-format cflowd-version-5; flow-active-timeout seconds; flow-export-destination (cflowd-collector | collector-pic); flow-inactive-timeout seconds; interface interface-name { number; engine-type number; input-interface-index number; output-interface-index number; source-address address;...

  • Page 55: Multiservice-Options

    Specify a value for the output interface index that overrides the default supplied by SNMP. Options —Output interface index value. number Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring Flow Monitoring on page 9 Documentation Copyright © 2017, Juniper Networks, Inc.

  • Page 56: Output (Monitoring)

    Flow Monitoring Feature Guide for EX9200 Switches output (Monitoring) Syntax output { cflowd hostname port port-number; export-format format; flow-active-timeout seconds; flow-export-destination (cflowd-collector | collector-pic); flow-inactive-timeout seconds; interface interface-name { engine-id number; engine-type number; input-interface-index number; output-interface-index number; source-address address; Hierarchy Level...

  • Page 57: Port (Flow Monitoring)

    Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Junos OS Services Interfaces Library for Routing Devices Documentation Configuring Flow Monitoring on page 9 Copyright © 2017, Juniper Networks, Inc.

  • Page 58: Source-Address (Forwarding Options)

    Flow Monitoring Feature Guide for EX9200 Switches source-address (Forwarding Options) Syntax source-address address; Hierarchy Level [edit forwarding-options accounting name outputinterface interface-name], [edit forwarding-options monitoring namefamilyfamily inet output interface interface-name], [edit forwarding-options sampling instance instance-name family (inet |inet6 |mpls | vpls)

  • Page 59: Unit

    Related Junos OS Network Interfaces Library for Routing Devices for other statements that do Documentation no affect services interfaces. Junos OS Network Interfaces Library for Routing Devices Copyright © 2017, Juniper Networks, Inc.
  • Page 60 Flow Monitoring Feature Guide for EX9200 Switches Copyright © 2017, Juniper Networks, Inc.

  • Page 61: Operational Commands

    Copyright © 2017, Juniper Networks, Inc.

  • Page 62: Show Services Accounting Aggregation

    Flow Monitoring Feature Guide for EX9200 Switches show services accounting aggregation Syntax show services accounting aggregation aggregation-type <aggregation-value> <detail | extensive | terse> <limit limit-value> < name service-name> <order (bytes | packets)> Release Information Command introduced before Junos OS Release 7.4.

  • Page 63: Table 3: Show Services Accounting Aggregation Output Fields

    Destination prefix length. Destination prefix length SNMP index of the interface the packet came in on. Input SNMP interface index SNMP index of the interface the packet went out on. Output SNMP interface index Copyright © 2017, Juniper Networks, Inc.
  • Page 64 Flow Monitoring Feature Guide for EX9200 Switches Table 3: show services accounting aggregation Output Fields (continued) Field Name Field Description Actual time when the packet in this aggregation was first seen. Start time Actual time when the packet in this aggregation was last seen.
  • Page 65 Interface state: Accounting Source Destination Input Output Flow Packet Byte prefix prefix interface interface count count count 10.1.0.0/20 192.168.3.0/24 ge-5/0/1.0 ge-5/0/0.0 639822 40948608 10.1.0.0/20 192.168.2.67/32 ge-5/0/1.0 ge-5/0/0.0 2485 159040 10.1.0.0/20 192.168.2.92/32 ge-5/0/1.0 ge-5/0/0.0 2485 Copyright © 2017, Juniper Networks, Inc.

  • Page 66: Show Services Accounting Aggregation Template

    Flow Monitoring Feature Guide for EX9200 Switches show services accounting aggregation template Syntax show services accounting aggregation template <template-name template-name> Release Information Command introduced in Junos OS Release 8.3. Description Display information for flow aggregation version 9 templates. Options none —Display information for all flow aggregation version version 9 templates.
  • Page 67 Chapter 5: Operational Commands Copyright © 2017, Juniper Networks, Inc.

  • Page 68: Show Services Accounting Errors

    Flow Monitoring Feature Guide for EX9200 Switches show services accounting errors Syntax show services accounting errors <inline-jflow | name (* | all | service-name)> Release Information Command introduced before Junos OS Release 7.4. Description Display active flow error statistics. Options none —Display error statistics for all services accounting instances.
  • Page 69 Service name: (default sampling) Error information Packets dropped (no memory): 0, Packets dropped (not IP): 0 Packets dropped (not IPv4): 0, Packets dropped (header too small): 0 Memory allocation failures: 0, Memory free failures: 0 Copyright © 2017, Juniper Networks, Inc.
  • Page 70 Flow Monitoring Feature Guide for EX9200 Switches Memory free list failures: 0 Memory overload: No, PPS overload: No, BPS overload: No Sample Output show services accounting errors (Service PIC interface) user@host> show services accounting errors Service Accounting interface: sp-0/1/0 Service name: (default sampling)
  • Page 71 IPv4 Route Record Lookup Failures: 0, IPv4 AS Lookup Failures: 0 IPv4 Export Packet Failures: 0 IPv6: IPv6 Flow Creation Failures: 0 IPv6 Route Record Lookup Failures: 0, IPv6 AS Lookup Failures: 0 IPv6 Export Packet Failures: 0 Copyright © 2017, Juniper Networks, Inc.

  • Page 72: Show Services Accounting Flow

    Flow Monitoring Feature Guide for EX9200 Switches show services accounting flow Syntax show services accounting flow <inline-jflow fpc-slot slot-number | logical-system (all | logical-system) | name (* | all | service-name)> Release Information Command introduced before Junos OS Release 7.4.
  • Page 73 Flow packets: 87168293, Flow bytes: 5578770752 Flow packets 10-second rate: 45762, Flow bytes 10-second rate: 2928962 Active flows: 1000, Total flows: 2000 Flows exported: 19960, Flows packets exported: 582 Flows inactive timed out: 1000, Flows active timed out: 29000 Copyright © 2017, Juniper Networks, Inc.
  • Page 74 Flow Monitoring Feature Guide for EX9200 Switches show services accounting flow (Flow Aggregation v9 Configuration) user@host> show services accounting flow Flow information Service Accounting interface: sp-7/1/0, Local interface index: 149 Flow packets: 0, Flow bytes: 0 Flow packets 10-second rate: 0, Flow bytes 10-second rate: 0...
  • Page 75 VPLS Flow Packets: 0, VPLS Flow Bytes: 0 VPLS Active Flows: 0, VPLS Total Flows: 0 VPLS Flows Exported: 0, VPLS Flow Packets Exported: 0 VPLS Flows Inactive Timed Out: 0, VPLS Flows Active Timed Out: 0 Copyright © 2017, Juniper Networks, Inc.
  • Page 76 Flow Monitoring Feature Guide for EX9200 Switches show services accounting flow inline-jflow (MX80 Router with IPv4 and IPv6 Configuration) user@host> show services accounting flow inline-jflow Flow information TFEB Slot: 0 Flow Packets: 0, Flow Bytes: 0 Active Flows: 0, Total Flows: 0...

  • Page 77: Show Services Accounting Flow-Detail

    Use a wildcard character, specify all services, or provide a specific services name. order (bytes | packets) —(Optional) Display the flow with the ordering of the highest number, either by byte count or by packet count. Copyright © 2017, Juniper Networks, Inc.

  • Page 78: Table 7: Show Services Accounting Flow-Detail Output Fields

    Flow Monitoring Feature Guide for EX9200 Switches Additional Information When no PIC is active, or when no route record has been downloaded from the PIC, this command reports no flows, even though packets are being sampled. This command displays information about two concurrent sessions only. If a third session is attempted, the command pauses with no output until one of the previous sessions is completed.
  • Page 79 Output interface address port interface... tcp(6) ge-5/0/1.0 192.0.2.2 ge-5/0/0.0 tcp(6) ge-5/0/1.0 192.0.2.2 ge-5/0/0.0 Destination Destination Packet Byte Time since last address port count count active timeout... 198.51.100.149 2660 170240 00:00:58 198.51.100.138 2660 170240 00:00:58 Copyright © 2017, Juniper Networks, Inc.
  • Page 80 Flow Monitoring Feature Guide for EX9200 Switches Packet count for Byte count for last active timeout last active timeout 2805 179520 2805 179520 show services accounting flow-detail limit In this sample, the output is split into three sections, with ellipses (...) indicating where the sections are continued.
  • Page 81 Service Accounting interface: mo-0/2/0, Local interface index: 145 Service name: cf-2 Protocol: udp(17), Source address: 10.10.10.1, Source port: 1173, Destination address: 203.0.113.20, Destination port: 69 Start time: 62425, End time: 811115, Packet count: 142438, Byte count: 8118966 Copyright © 2017, Juniper Networks, Inc.

  • Page 82: Show Services Accounting Memory

    Flow Monitoring Feature Guide for EX9200 Switches show services accounting memory Syntax show services accounting memory Release Information Command introduced before Junos OS Release 7.4. Description Display memory and flow record statistics. Options This command has no options. Required Privilege...
  • Page 83 Total memory free (in bytes): 587147696 Service Accounting interface: sp-1/0/0 Memory utilization Allocation count: 1000, Free count: 0 Allocations per second: 0, Frees per second: 0 Total memory used (in bytes): 218157592 Total memory free (in bytes): 587148376 Copyright © 2017, Juniper Networks, Inc.

  • Page 84: Show Services Accounting Packet-Size-Distribution

    Flow Monitoring Feature Guide for EX9200 Switches show services accounting packet-size-distribution Syntax show services accounting packet-size-distribution <name (* | all | service-name)> Release Information Command introduced before Junos OS Release 7.4. Description Display a packet size distribution histogram. Options none —Display a packet size distribution histogram of all accounting services.
  • Page 85 Chapter 5: Operational Commands Range start Range end Number of packets Percentage packets 2924 Copyright © 2017, Juniper Networks, Inc.

  • Page 86: Show Services Accounting Status

    —(Optional) Display inline flow accounting status for the inline-jflow fpc-slot slot-number specified FPC. For a two-member MX Series Virtual Chassis or EX9200 Virtual Chassis, the master router or switch uses FPC slot numbers 0 through 11 with no offset; the backup router or switch uses FPC slot numbers 12 through 23, with an offset of 12.
  • Page 87 Service Accounting interface: mo-2/0/0, Local interface index: 468 Service name: count1 Interface state: Accounting Group index: 0 Export interval (in seconds): 60, Export format: cflowd v8 Protocol: IPv4, Engine type: 55, Engine ID: 5 Copyright © 2017, Juniper Networks, Inc.
  • Page 88 Flow Monitoring Feature Guide for EX9200 Switches Sample Output show services accounting status name (Service PIC Interface) user@host> show services accounting status name Service Accounting interface: sp-0/1/0 Interface state: Accounting Export format: 9, Route record count: 0 IFL to SNMP index count: 7, AS count: 0...

  • Page 89: Show Services Accounting Usage

    Load (1 minute) CPU load on the PIC, averaged more than 1 minute. The number is a percentage obtained by dividing the time spent on active tasks by the total elapsed time. Copyright © 2017, Juniper Networks, Inc.
  • Page 90 Flow Monitoring Feature Guide for EX9200 Switches Sample Output show services accounting usage (Monitoring PIC Interface) user@host> show services accounting usage Service Accounting interface: mo-1/1/0, Local interface index: 15 Service name: (default sampling) CPU utilization Uptime: 600413856 milliseconds, Interrupt time: 2403 microseconds...

Table of Contents