Juniper EX2200 Hardware Manual

Juniper EX2200 Hardware Manual

Junos osfor exseries ethernetswitches
Hide thumbs Also See for EX2200:
Table of Contents

Advertisement

®
Junos
OS for EX Series Ethernet Switches
Network Interfaces for EX4300 Switches
Release
13.2X51
Published: 2015-02-24
Copyright © 2015, Juniper Networks, Inc.

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Summary of Contents for Juniper EX2200

  • Page 1 ® Junos OS for EX Series Ethernet Switches Network Interfaces for EX4300 Switches Release 13.2X51 Published: 2015-02-24 Copyright © 2015, 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

    Unicast RPF Packet Filtering ........20 Bootstrap Protocol (BOOTP) and DHCP Requests ....20 Copyright © 2015, Juniper Networks, Inc.
  • Page 4 Media MTU Sizes by Interface Type for J4300 and J6300 Platforms ..62 Media MTU Sizes by Interface Type for J4350 and J6350 Platforms ..63 Copyright © 2015, Juniper Networks, Inc.
  • Page 5 Configuring Local Link Bias (CLI Procedure) ......94 Copyright © 2015, Juniper Networks, Inc.
  • Page 6 Supported Statements in the [edit interfaces irb] Hierarchy Level ..134 Unsupported Statements in the [edit interfaces irb] Hierarchy Level ..137 Copyright © 2015, Juniper Networks, Inc.
  • Page 7 ........... . 191 Copyright © 2015, Juniper Networks, Inc.
  • Page 8 ..........254 show forwarding-options enhanced-hash-key ......259 viii Copyright © 2015, Juniper Networks, Inc.
  • Page 9 Legitimate Packets Are Discarded ....... . . 331 Diagnosing a Faulty Twisted-Pair Cable (CLI Procedure) ....332 Copyright © 2015, Juniper Networks, Inc.
  • Page 10 Network Interfaces for EX4300 Switches Copyright © 2015, Juniper Networks, Inc.
  • Page 11 Figure 4: Asymmetrically Routed Interfaces ......22 Copyright © 2015, Juniper Networks, Inc.
  • Page 12 Network Interfaces for EX4300 Switches Copyright © 2015, Juniper Networks, Inc.
  • Page 13 Series Routers ..........65 Copyright © 2015, Juniper Networks, Inc.
  • Page 14 Table 53: show lacp interfaces Output Fields ......322 Copyright © 2015, Juniper Networks, Inc.
  • Page 15: 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 16: Merging A Full Example

    /var/tmp on your routing platform. commit { file ex-script-snippet.xsl; } Move to the hierarchy level that is relevant for this snippet by issuing the following configuration mode command: Copyright © 2015, Juniper Networks, Inc.
  • Page 17: 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 © 2015, Juniper Networks, Inc. xvii...
  • Page 18 GUI Conventions Bold text like this Represents graphical user interface (GUI) In the Logical Interfaces box, select items you click or select. All Interfaces To cancel the configuration, click Cancel xviii Copyright © 2015, Juniper Networks, Inc.
  • Page 19: Documentation Feedback

    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/...
  • Page 20: 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 21: Overview

    PART 1 Overview Interfaces Overview on page 3 Copyright © 2015, Juniper Networks, Inc.
  • Page 22 Network Interfaces for EX4300 Switches Copyright © 2015, Juniper Networks, Inc.
  • Page 23: Interfaces Overview

    802.1Q VLANs Overview on page 26 EX Series Switches Interfaces Overview Juniper Networks EX Series Ethernet Switches have two types of interfaces: network interfaces and special interfaces. This topic provides brief information about these interfaces. For additional information, see the...
  • Page 24: Special Interfaces

    All EX Series switches have this software-only virtual interface that is always up. The loopback interface provides a stable and consistent interface and IP address on the switch. Management interface The Juniper Networks Junos operating system (Junos OS) for EX Series switches automatically creates the switch's management Ethernet interface, . The management Ethernet interface provides an out-of-band method for connecting to the switch.
  • Page 25 Understanding Global Management of a Virtual Chassis. EX8200 switches do not use a VME interface. An EX8200 Virtual Chassis is managed through the management Ethernet ( ) interface on the XRE200 External Routing Engine. Copyright © 2015, Juniper Networks, Inc.
  • Page 26: Understanding Interface Naming Conventions On Ex Series Switches

    Understanding Interface Naming Conventions on EX Series Switches Juniper Networks EX Series Ethernet Switches use a naming convention for defining the interfaces that is similar to that of other platforms running under Juniper Networks Junos operating system (Junos OS). This topic provides brief information about the naming conventions used for interfaces on EX Series switches.
  • Page 27 PIC Concentrator. EX Series interfaces use the following convention for the FPC number in interface names: On an EX2200 switch, an EX3200 switch, a standalone EX3300 switch, a standalone EX4200 switch, a standalone EX4300 switch, a standalone EX4500, and a standalone EX4550 switch, FPC refers to the switch itself.
  • Page 28: Logical Part Of An Interface Name

    If one member link fails, the LAG continues to carry traffic over the remaining links. Link Aggregation Control Protocol (LACP), a component of IEEE 802.3ad, provides additional functionality for LAGs. Copyright © 2015, Juniper Networks, Inc.
  • Page 29: Link Aggregation Group (Lag)

    (ports) with the link. All the interfaces must have the same speed and be in full-duplex mode. Juniper Networks Junos operating system (Junos OS) for EX Series Ethernet Switches assigns a unique ID and port priority to each interface.
  • Page 30: Link Aggregation Control Protocol (Lacp)

    LAG by default, whether the switch and peer are both in active or passive mode. When PDUs are not received, the partner is considered to be working in the passive mode. Therefore, LACP PDU transmissions are controlled by the transmitting link. Copyright © 2015, Juniper Networks, Inc.
  • Page 31: Ecmp Traffic

    Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic Juniper Networks EX Series and QFX Series use a hashing algorithm to determine how to forward traffic over a link aggregation group (LAG) bundle or to the next-hop device when equal-cost multipath (ECMP) is enabled.
  • Page 32: Ip (Ipv4 And Ipv6)

    Layer 2 header fields. If you want incoming IPv4, IPv6, and MPLS packets hashed by the source MAC address, destination MAC address, or EtherType fields, you must set the hash mode to Layer 2 header. Copyright © 2015, Juniper Networks, Inc.
  • Page 33: Table 6: Ipv4 And Ipv6 Hashing Fields

    (configurable) Next header (IPv6 only) (configurable) (configurable) (configurable) (configurable) Layer 4 Source Port (configurable) (configurable) (configurable) (configurable) Layer 4 Destination Port (configurable) (configurable) (configurable) (configurable) Χ Χ Χ Χ IPv6 Flow label (IPv6 only) Copyright © 2015, Juniper Networks, Inc.
  • Page 34: Mpls

    Protocol (for IPv4 packets) Χ Χ Next header (for IPv6 packets) Χ Χ Layer 4 Source Port Χ Χ Layer 4 Destination Port Χ Χ IPv6 Flow lab MPLS label 0 MPLS label 1 MPLS label 2 Copyright © 2015, Juniper Networks, Inc.
  • Page 35: Mac-In-Mac Packet Hashing

    Χ—Field is not used by the hashing algorithm, by default. (configurable)—Field can be configured to be used or not used by the hashing algorithm. Table 9: Layer 2 Header Hashing Fields Field EX4300 QFX5100 Source MAC (configurable) (configurable) Destination MAC (configurable) (configurable) Copyright © 2015, Juniper Networks, Inc.
  • Page 36: Understanding How Energy Efficient Ethernet Reduces Power Consumption On

    LAG bundle that is on the member switch that received the traffic. Because traffic is received and forwarded on the same member switch when local link bias is enabled, no VCP bandwidth is consumed by traffic traversing the VCPs to exit the Virtual Chassis or Copyright © 2015, Juniper Networks, Inc.
  • Page 37: Figure 1: Egress Traffic Flow With Local Link Bias

    Local link bias is disabled, by default. You should enable local link bias if you want to conserve VCP bandwidth by always forwarding egress unicast traffic on a LAG bundle out of a local link. You should not Copyright © 2015, Juniper Networks, Inc.
  • Page 38: Understanding Layer 3 Subinterfaces

    Layer 3 subinterfaces to route traffic among multiple VLANs along a single trunk line that connects a Juniper Networks EX Series Ethernet Switch to a Layer 2 switch. Only one physical connection is required between the switches. This topology is often called a router on a stick or a one-armed router when the Layer 3 device is a router.
  • Page 39: Understanding Unicast Rpf

    This is known as strict mode unicast RPF. NOTE: On Juniper Networks EX3200, EX4200, and EX4300 Ethernet Switches, the switch applies unicast RPF globally to all interfaces when unicast RPF is configured on any interface. For additional information, see “Limitations of the Unicast RPF Implementation on EX3200, EX4200, and...
  • Page 40: Unicast Rpf Implementation

    21. Symmetrical routing means that if an interface receives a packet, the switch uses the same interface to send a reply to the packet source (the receiving interface matches the forwarding-table entry for the best return path to the source). Copyright © 2015, Juniper Networks, Inc.
  • Page 41: When Not To Enable Unicast Rpf

    Switch interfaces face the network core. Core-facing interfaces are usually asymmetrically routed. An asymmetrically routed interface uses different paths to send and receive packets between the source and the destination, as shown in Figure 4 on page 22. This means Copyright © 2015, Juniper Networks, Inc.
  • Page 42: Limitations Of The Unicast Rpf Implementation On Ex3200, Ex4200, And Ex4300 Switches

    RPF filter does not examine the entire ECMP address block. Related Example: Configuring Unicast RPF on an EX Series Switch Documentation Configuring Unicast RPF (CLI Procedure) on page 97 Copyright © 2015, Juniper Networks, Inc.
  • Page 43: Understanding Ip Directed Broadcast For Ex Series Switches

    Layer 3 interface of the subnet’s VLAN. When the switch that is connected to that subnet receives a packet that has the subnet’s broadcast IP address as the destination address, the switch broadcasts the packet to all hosts on the subnet. Copyright © 2015, Juniper Networks, Inc.
  • Page 44: When To Enable Ip Directed Broadcast

    EX Series Switches. For ELS details, see Getting Started with Enhanced Layer 2 Software. You can use the interface ranges to group interfaces of the same type that share a common configuration profile. This helps reduce the time and effort in configuring Copyright © 2015, Juniper Networks, Inc.
  • Page 45 Chapter 1: Interfaces Overview interfaces on Juniper Networks EX Series Ethernet Switches. The configurations common to all the interfaces can be included in the interface range definition. The interface range definition contains the name of the interface range defined, the...
  • Page 46: 802.1Q Vlans Overview

    Example: Configuring a Layer 2 Circuit on a VLAN-Bundled Logical Interface Configuring a Logical Interface for Access Mode Configuring a Logical Interface for Trunk Mode Configuring the VLAN ID List for a Trunk Interface Copyright © 2015, Juniper Networks, Inc.
  • Page 47 Chapter 1: Interfaces Overview Configuring a Trunk Interface on a Bridge Network Ethernet Interfaces Copyright © 2015, Juniper Networks, Inc.
  • Page 48 Network Interfaces for EX4300 Switches Copyright © 2015, Juniper Networks, Inc.
  • Page 49: Configuration

    PART 2 Configuration Configuration Tasks on page 31 Configuration Statements on page 103 Copyright © 2015, Juniper Networks, Inc.
  • Page 50 Network Interfaces for EX4300 Switches Copyright © 2015, Juniper Networks, Inc.
  • Page 51: Configuration Tasks

    Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure) on page 87 Configuring Aggregated Ethernet Link Protection on page 89 Configuring Aggregated Ethernet Link Speed on page 90 Configuring Aggregated Ethernet Minimum Links on page 92 Copyright © 2015, Juniper Networks, Inc.
  • Page 52: Configuring Gigabit Ethernet Interfaces (Cli Procedure)

    VLAN named default . You can optionally configure another VLAN and use that instead of default . You Copyright © 2015, Juniper Networks, Inc.
  • Page 53: Configuring The Link Settings

    Disabled Enabled Full duplex 10 Gbps (using a fiber-optic cable) 40 gigabit Enabled Enabled Full duplex 40 Gbps (using a DAC cable) 40 gigabit Disabled Enabled Full duplex 40 Gbps (using a fiber-optic cable) Copyright © 2015, Juniper Networks, Inc.
  • Page 54: Configuring The Ip Options

    You might have to delete this or any other ethernet-switching user-configured family setting before changing the setting to family inet family inet6 Related Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 35 Documentation Monitoring Interface Status and Traffic on page 233 Copyright © 2015, Juniper Networks, Inc.
  • Page 55: Configuring Gigabit Ethernet Interfaces (J-Web Procedure)

    NOTE: In the J-Web interface, you cannot configure interface ranges and interface groups. Click and select the set of options you want to configure first: Edit Copyright © 2015, Juniper Networks, Inc.
  • Page 56 Repeat Steps 3 and 4 for the remaining option sets that you want to configure for the interface. NOTE: To enable or disable the administrative status of a selected interface, click Enable Port Disable Port Copyright © 2015, Juniper Networks, Inc.
  • Page 57: Table 11: Port Edit Options

    Type the VLAN ID for a new VLAN. port mode is set to access , and RSTP is enabled 2. Click to view CLI commands for this role. Details with the options. edge point-to-point 3. Click Copyright © 2015, Juniper Networks, Inc.
  • Page 58 2001:ab8:85a3::8a2e:370:7334. 3. Enter the subnet mask or address prefix. 4. Click NOTE: IPv6 is not supported on EX2200 VC switches. Layer 2 Uplink Applies the Layer 2 uplink role. For this port role, you can select a VLAN member and associate a native VLAN with the interface.
  • Page 59 Flow control is enabled by default. Media Type Specifies the media type selected. Select the check box to enable the media type. Then select Copper Fiber Copyright © 2015, Juniper Networks, Inc.
  • Page 60: Table 12: Recommended Cos Settings For Port Roles

    2001:ab8:85a3::8a2e:370:7334. 3. Enter the subnet mask or address prefix. 4. Click NOTE: IPv6 address is not supported on EX2200 and EX4500 switches. Table 12: Recommended CoS Settings for Port Roles CoS Parameter Recommended Settings Forwarding Classes There are four forwarding classes: voice —Queue number is set to 7.
  • Page 61: Port Role Configuration With The J-Web Interface (With Cli References)

    Desktop Set VLAN if new VLAN is specified. set vlans <vlan name> vlan-id <vlan-id> Set port family to ethernet-switching set interfaces interface unit 0 family ethernet-switching port-mode access Set Port Mode to Access Copyright © 2015, Juniper Networks, Inc.
  • Page 62 Set port family to set interfaces interface unit 0 family ethernet-switching ethernet-ewitching port-mode access Set port mode to Access Set VLAN on port stanza. set interfaces interface unit 0 family ethernet-switching vlan members vlan-members Copyright © 2015, Juniper Networks, Inc.
  • Page 63 Set class-of-service parameters. set class-of-service interfaces interfacescheduler-map juniper-port-profile-map SCHEDULER_MAP juniper-port-profile-map set class-of-service interfaces interface unit 0 classifiers ieee-802.1 juniper_ieee_classifier IEEE_CLASSIFIER juniper_ieee_classifier set class-of-service interfaces interfaceunit 0 classifiers dscp juniper-dscp-classifier DSCP_CLASSIFIER juniper_dscp_classifier Copyright © 2015, Juniper Networks, Inc.
  • Page 64: Table 14: Recommended Cos Settings For Port Roles

    The CLI commands are: set class-of-service schedulers best-effort-scheduler transmit-rate percent set class-of-service schedulers best-effort-scheduler buffer-size percent 40 set class-of-service schedulers best-effort-scheduler priority low Copyright © 2015, Juniper Networks, Inc.
  • Page 65: Adding A Logical Unit Description To The Configuration

    You can disable a physical interface, marking it as being down, without removing the interface configuration statements from the configuration. To do this, include the disable statement at the hierarchy level: [edit interfaces interface-name] [edit interfaces interface-name] disable; Copyright © 2015, Juniper Networks, Inc.
  • Page 66: Example: Disabling A Physical Interface

    Disabling the interface: [edit interfaces] user@host# set ge-0/3/2 disable Verifying the interface configuration: [edit interfaces] user@host# show ge-0/3/2 { disable; # Interface is marked as disabled. unit 0 { description CE2-to-PE1; family inet { address 20.1.1.6/24; Copyright © 2015, Juniper Networks, Inc.
  • Page 67: Disabling A Logical Interface

    On the Type 5 FPC, to prioritize control packets in case of ingress oversubscription, you must ensure that the neighboring peers support MAC flow control. If the peers do not support MAC flow control, then you must disable flow control. Related flow-control on page 181 Documentation Copyright © 2015, Juniper Networks, Inc.
  • Page 68: Configuring The Interface Address

    PPP properties to the remote end—Specify this in the destination-profile statement. You define the profile at the hierarchy level (for [edit access group-profile name ppp] point-to-point interfaces only). Copyright © 2015, Juniper Networks, Inc.
  • Page 69: Configuring Interface Ipv4 Addresses

    [edit interfaces] hierarchy level. NOTE: Juniper Networks routers and switches support destination prefixes when used in point-to-point Ethernet configurations; however, they are not supported by many other devices, such as hosts, hubs, routers, or switches. You must determine if the peer system also supports destination prefixes before configuration.
  • Page 70: Operational Behavior Of Interfaces When The Same Ipv4 Address Is Assigned To Them

    IPv4 address other than 200.1.1.1/24 user@host> show interfaces terse ge* Interface Admin Link Proto Local Remote ge-0/1/0 ge-0/1/0.0 inet 200.1.1.1/24 multiservice ge-0/1/1 down ge-3/0/0 down ge-3/0/1 ge-3/0/1.0 inet multiservice Copyright © 2015, Juniper Networks, Inc.
  • Page 71: Configuring Interface Ipv6 Addresses

    IPv6 is not currently supported for the QFX Series. You represent IP version 6 (IPv6) addresses in hexadecimal notation using a colon-separated list of 16-bit values. You assign a 128-bit IPv6 address to an interface by including the statement: address address aaaa:bbbb:...:zzzz/nn; Copyright © 2015, Juniper Networks, Inc.
  • Page 72: Configuring The Interface Bandwidth

    You can configure the logical unit to populate the variable by configuring a ifSpeed bandwidth value for the logical interface. The bandwidth statement sets an informational-only parameter; you cannot adjust the actual bandwidth of an interface with this statement. Copyright © 2015, Juniper Networks, Inc.
  • Page 73: Configuring The Media Mtu

    Media MTU Sizes by Interface Type for M160 Routers on page 59 Media MTU Sizes by Interface Type for M7i Routers with CFEB-E, M10i Routers with CFEB-E, and M320 and M120 Routers on page 59 Copyright © 2015, Juniper Networks, Inc.
  • Page 74: Media Mtu Overview

    Also, when you are configuring point-to-multipoint connections, all interfaces in the subnet must use the same MTU size. For details about encapsulation overhead, see “Encapsulation Overhead by Encapsulation Type” on page Copyright © 2015, Juniper Networks, Inc.
  • Page 75: How To Configure The Media Mtu

    You configure the protocol MTU by including the statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number family family] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family family] Copyright © 2015, Juniper Networks, Inc.
  • Page 76: Encapsulation Overhead By Encapsulation Type

    LAN service (VPLS) Ethernet over ATM Ethernet SNAP Ethernet translational cross-connect (TCC) Ethernet version 2 Extended virtual local area network (VLAN) CCC and VPLS Extended VLAN TCC Frame Relay VLAN CCC VLAN VPLS VLAN TCC Copyright © 2015, Juniper Networks, Inc.
  • Page 77: Media Mtu Sizes By Interface Type For M5 And M7I Routers With Cfeb, M10 And M10I Routers With Cfeb, And M20 And M40 Routers

    Table 17: Media MTU Sizes by Interface Type for M40e Routers Default Media Default IP Protocol Interface Type MTU (Bytes) Maximum MTU (Bytes) MTU (Bytes) Adaptive Services 9192 (MTU size not configurable) 4482 9192 4470 Copyright © 2015, Juniper Networks, Inc.
  • Page 78 9192 (4-port OC3) 9192 (4-port OC3c) 4500 (1-port OC12) 4500 (4-port OC12) 4500 (4-port OC12c) 4500 (1-port OC48) 9192 (2-port OC3) 9192 (2-port OC3c) 9192 (1-port OC12c) 9192 (1-port OC48c) 4500 (1-port OC192) 9192 (1-port OC192c) Copyright © 2015, Juniper Networks, Inc.
  • Page 79: Media Mtu Sizes By Interface Type For M160 Routers

    Maximum MTU Default IP Protocol Interface Type MTU (Bytes) (Bytes) MTU (Bytes) ATM2 IQ 4482 9192 4470 Channelized DS3 IQ 4471 4500 4470 Channelized E1 IQ 1504 4500 1500 Channelized OC12 IQ 4474 9192 4470 Copyright © 2015, Juniper Networks, Inc.
  • Page 80: Media Mtu Sizes By Interface Type For Mx Series Routers

    1488 (MPLS), 1497 (ISO) 10-Gigabit Ethernet 1514 9192 1500 (IPv4), 1488 (MPLS), 1497 (ISO) Multi-Rate Ethernet 1514 9192 1500 (IPv4), 1488 (MPLS), 1497 (ISO) Tri-Rate Ethernet 1514 9192 1500 (IPv4), 1488 (MPLS), 1497 (ISO) Copyright © 2015, Juniper Networks, Inc.
  • Page 81: Media Mtu Sizes By Interface Type For T320 Routers

    Table 22: Media MTU Sizes by Interface Type for T640 Platforms Default Media Maximum MTU Default IP Protocol Interface Type MTU (Bytes) (Bytes) MTU (Bytes) ATM2 IQ 4482 9192 4470 48-port Fast Ethernet 1514 1532 1500 (IPv4), 1497 (ISO) Copyright © 2015, Juniper Networks, Inc.
  • Page 82: Media Mtu Sizes By Interface Type For J2300 Platforms

    9150 4470 Dual-port Fast 1514 9192 1500 Ethernet (10/100) PIM Dual-port Serial PIM 1504 9150 1500 Dual-port T1 or E1 PIM 1504 9150 1500 Dual-port 1504 4500 1500 Channelized T1/E1 PIM (channelized to DS0s) Copyright © 2015, Juniper Networks, Inc.
  • Page 83: Media Mtu Sizes By Interface Type For J4350 And J6350 Platforms

    Dual-port T1 or E1 PIM 1504 9150 1500 Dual-port 1504 4500 1500 Channelized T1/E1 PIM (channelized to DS0s) Dual-port 1504 9150 1500 Channelized T1/E1 PIM (clear channel T1 or 4-port Fast Ethernet 1518 1518 1500 (10/100) ePIM Copyright © 2015, Juniper Networks, Inc.
  • Page 84 If you configure an MTU greater than 1518 bytes, the router does not accept the configuration and generates a system log error message similar to the following: /kernel: fe-3/0/1: Illegal media change. MTU invalid: 9192. Max MTU supported on this PIC: 1518 Copyright © 2015, Juniper Networks, Inc.
  • Page 85: Media Mtu Sizes By Interface Type For Ex Series Switches And Acx Series Routers

    “Configuring the Media MTU” on page To modify the MTU for a particular protocol family, include the statement: bytes; You can include this statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number family family] Copyright © 2015, Juniper Networks, Inc.
  • Page 86: Interface Ranges

    Member Interfaces Inheriting Configuration from Configuration Groups on page 71 Interfaces Inheriting Common Configuration on page 73 Configuring Inheritance Range Priorities on page 73 Configuration Expansion Where Interface Range Is Used on page 73 Copyright © 2015, Juniper Networks, Inc.
  • Page 87: Configuring Interface Ranges

    To specify the list of interface range members individually or for multiple interfaces using regex, use the member list of interface names statement. Example: Specifying an member ge-0/0/0; member ge-0/*/* Interface Range member ge-0/[1-10]/0; Member member ge-0/[1,2,3]/3; Copyright © 2015, Juniper Networks, Inc.
  • Page 88 TIP: To view an interface range in expanded configuration, use the (show | command. For more information, see the CLI User Guide. display inheritance) Copyright © 2015, Juniper Networks, Inc.
  • Page 89: Expanding Interface Range Member And Member Range Statements

    Interface Range interface-range range-1 { Member and Member member-range ge-0/0/0 to ge-4/0/20; Range Statements member ge-10/1/1; member ge-5/[0-5]/*; /*Common configuration is added part of the interface-range definition*/ mtu 256; hold-time up 10; ether-options { Copyright © 2015, Juniper Networks, Inc.
  • Page 90: Configuration Inheritance For Member Interfaces

    , it creates interface objects if they are not explicitly defined in the configuration. The common configuration is copied to all its member interfaces in the interface-range Copyright © 2015, Juniper Networks, Inc.
  • Page 91: Member Interfaces Inheriting Configuration From Configuration Groups

    Interface range member interfaces inherit the config-groups configuration like any other foreground configuration. interface-range is similar to any other foreground configuration statement. The only difference is that the interface-range goes through a member interfaces expansion before Junos OS reads this configuration. groups { Copyright © 2015, Juniper Networks, Inc.
  • Page 92 ## '10' was inherited from group 'global' hold-time up 10; ge-10/0/47 { ## '256' was expanded from interface-range 'range-1' mtu 256; ## 'hold-time' was inherited from group 'global' ## '10' was inherited from group 'global' hold-time up 10; Copyright © 2015, Juniper Networks, Inc.
  • Page 93: Interfaces Inheriting Common Configuration

    256 interface-range int-grp-one first. Configuration Expansion Where Interface Range Is Used In this example, interface-range range-1 is used under the protocols hierarchy: [edit] interfaces { interface-range range-1 { Copyright © 2015, Juniper Networks, Inc.
  • Page 94: Configuring Accounting For The Physical Interface

    Configuring Accounting for the Physical Interface Juniper Networks routers and switches can collect various kinds of data about traffic passing through the router and switch. You can set up one or more accounting profiles that specify some common characteristics of this data, including the following:...
  • Page 95: Applying An Accounting Profile To The Physical Interface

    { file if_stats { size 4m files 10 transfer-interval 15; archive-sites { "ftp://login:password@host/path"; interface-profile if_profile { interval 15; file if_stats { fields { input-bytes; output-bytes; input-packets; output-packets; input-errors; output-errors; [edit interfaces ge-1/0/1] accounting-profile if_profile; Copyright © 2015, Juniper Networks, Inc.
  • Page 96: Configuring Accounting For The Logical Interface

    Network Interfaces for EX4300 Switches Configuring Accounting for the Logical Interface Juniper Networks routers or switches can collect various kinds of data about traffic passing through the router or switch . You can set up one or more accounting profiles that specify...
  • Page 97: Configuring Ethernet Loopback Capability

    You can include the statements at the following hierarchy loopback no-loopback levels: [edit interfaces interface-name aggregated-ether-options] [edit interfaces interface-name ether-options] [edit interfaces interface-name fastether-options] [edit interfaces interface-name gigether-options] Related loopback on page 205 Documentation Ethernet Interfaces Overview Copyright © 2015, Juniper Networks, Inc.
  • Page 98: Configuring Gratuitous Arp

    [edit interfaces interface-name] [edit interfaces interface-name] no-gratuitous-arp-reply; Related gratuitous-arp-reply on page 182 Documentation no-gratuitous-arp-request on page 214 Ethernet Interfaces Overview EX Series Switches Interfaces Overview on page 3 Ethernet Interfaces Copyright © 2015, Juniper Networks, Inc.
  • Page 99: Configuring Static Arp Table Entries

    ARP entries in IPv4. Example: Configuring Static ARP Table Entries Configure two static ARP table entries on the router or switch’s management interface: [edit interfaces] fxp0 { unit 0 { family inet { address 10.10.0.11/24 { Copyright © 2015, Juniper Networks, Inc.
  • Page 100: Disabling The Transmission Of Redirect Messages On An Interface

    You can track the number of restricted or unrestricted proxy ARP requests processed by the router or switch by issuing the show system statistics arp operational mode command. Copyright © 2015, Juniper Networks, Inc.
  • Page 101: Enabling Or Disabling Snmp Notifications On Logical Interfaces

    You can include these statements at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] NOTE: Gigabit Ethernet interfaces on J Series routers do not support SNMP. Copyright © 2015, Juniper Networks, Inc.
  • Page 102: Configuring Aggregated Ethernet Links (Cli Procedure)

    Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200 Virtual Chassis Access Switch and an EX4200 Virtual Chassis Distribution Switch Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between an EX4200 Virtual Chassis Access Switch and an EX4200 Virtual Chassis Distribution Switch Copyright © 2015, Juniper Networks, Inc.
  • Page 103: Configuring Aggregated Ethernet Interfaces (J-Web Procedure)

    —Deletes the selected LAG. —Disables or enables the administrative status on the Disable Port Enable Port selected interface. Device Count —Configures the number of aggregated logical devices available to the switch. Select the number and click Copyright © 2015, Juniper Networks, Inc.
  • Page 104: Table 28: Aggregated Ethernet Interface Options

    LAG. Enable Log Specifies whether to enable generation Select the check box to enable log of log entries for the LAG. generation, or clear the check box to disable log generation. Copyright © 2015, Juniper Networks, Inc.
  • Page 105: Table 29: Vlan Options

    Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between an EX4200 Virtual Chassis Access Switch and an EX4200 Virtual Chassis Distribution Switch Verifying the Status of a LAG Interface on page 234 Configuring Aggregated Ethernet LACP (CLI Procedure) on page 86 Copyright © 2015, Juniper Networks, Inc.
  • Page 106: Configuring Aggregated Ethernet Lacp (Cli Procedure)

    Configure at least one side of the aggregated Ethernet link as active: [edit interfaces] user@switch# set aeX aggregated-ether-options lacp active Specify the interval at which the interfaces send LACP packets: [edit interfaces] user@switch# set aeX aggregated-ether-options lacp periodic interval Copyright © 2015, Juniper Networks, Inc.
  • Page 107: Configuring Lacp Link Protection Of Aggregated Ethernet Interfaces

    (either revertive or nonrevertive). Configuring LACP link configuration at the aggregated Ethernet level results in only the configured interfaces using the defined configuration. LACP interface configuration also enables you to override global (chassis) LACP settings. Copyright © 2015, Juniper Networks, Inc.
  • Page 108: Procedure)

    To specify revertive mode: [edit interfaces aeX aggregated-ether-options lacp link-protection] user@switch# set revertive To specify nonrevertive mode: [edit interfaces aeX aggregated-ether-options lacp link-protection] user@switch# set non-revertive (Optional)To configure LACP system priority for an aggregated Ethernet interface: Copyright © 2015, Juniper Networks, Inc.
  • Page 109: Configuring Aggregated Ethernet Link Protection

    Configure the link protection mode. [edit interfaces aex aggregated-ether-options] user@host# set link-protection Configuring Primary and Backup Links for Link Aggregated Ethernet Interfaces To configure link protection, you must specify a primary and a secondary, or backup, link. Copyright © 2015, Juniper Networks, Inc.
  • Page 110: Reverting Traffic To A Primary Link When Traffic Is Passing Through A Backup Link

    TX Matrix Plus routers: Member links of different modes (WAN and LAN) for 10-Gigabit Ethernet links. Member links of different rates: 10-Gigabit Ethernet, 40-Gigabit Ethernet, 50-Gigabit Ethernet, 100-Gigabit Ethernet, and OC192 (10-Gigabit Ethernet WAN mode) Copyright © 2015, Juniper Networks, Inc.
  • Page 111 Aggregated Ethernet links on EX Series switches can be configured to operate at one of the following speeds: —Links are 10 Mbps. —Links are 100 Mbps. 100m —Links are 1 Gbps. —Links are 10 Gbps. —Links are 50 Gbps. Copyright © 2015, Juniper Networks, Inc.
  • Page 112: Configuring Aggregated Ethernet Minimum Links

    On all other routers and on EX Series switches, other than EX8200 switches, the range of valid values for minimum-links number is 1 through 8. When the maximum value (8) is specified, all configured links of a bundle must be up for the bundle to be labeled Copyright © 2015, Juniper Networks, Inc.
  • Page 113: Configuring Energy Efficient Ethernet On Interfaces (Cli Procedure)

    By default, EEE is disabled on EEE-capable ports. Related Verifying That EEE Is Saving Energy on Configured Ports on page 235 Documentation Understanding How Energy Efficient Ethernet Reduces Power Consumption on Interfaces on page 16 Copyright © 2015, Juniper Networks, Inc.
  • Page 114: Configuring Local Link Bias (Cli Procedure)

    Configuring the Fields in the Algorithm Used To Hash LAG Bundle and ECMP Traffic (CLI Procedure) Juniper Networks EX Series and QFX Series switches use a hashing algorithm to determine how to forward traffic over a Link Aggregation group (LAG) bundle or to the next-hop device when equal-cost multipath (ECMP) is enabled.
  • Page 115: Configuring The Hashing Algorithm To Use Fields In The Layer 2 Header For Hashing

    Layer 2 payload. The default hash mode is Layer 2 payload. Configure the fields in the IP payload that the hashing algorithm uses for hashing: [edit forwarding-options enhanced-hash-key] user@switch# set inet {no-ipv4-destination-address | no-ipv4-source-address | no-l4-destination-port | no-l4-source-port | no-protocol | vlan-id} Copyright © 2015, Juniper Networks, Inc.
  • Page 116: Hashing

    You can include this statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] For more information about the statements, see “802.1Q VLANs vlan-tagging vlan-id Overview” on page Copyright © 2015, Juniper Networks, Inc.
  • Page 117: Configuring A Layer 3 Subinterface (Cli Procedure)

    NOTE: On EX3200, EX4200, and EX4300 switches, you can enable unicast RPF only globally—that is, on all switch interfaces. You cannot enable unicast RPF on a per-interface basis. Before you begin: Copyright © 2015, Juniper Networks, Inc.
  • Page 118 Related Example: Configuring Unicast RPF on an EX Series Switch Documentation Verifying Unicast RPF Status on page 239 Disabling Unicast RPF (CLI Procedure) on page 99 Copyright © 2015, Juniper Networks, Inc.
  • Page 119: Disabling Unicast Rpf (Cli Procedure)

    Related Example: Configuring Unicast RPF on an EX Series Switch Documentation Verifying Unicast RPF Status on page 239 Configuring Unicast RPF (CLI Procedure) on page 97 Understanding Unicast RPF on page 19 Copyright © 2015, Juniper Networks, Inc.
  • Page 120: Configuring Ip Directed Broadcast (Cli Procedure)

    Associate a Layer 3 interface with the VLAN: [edit vlans] user@switch# set v1 l3-interface (VLANs) irb.1 Enable the Layer 3 interface for the VLAN to receive IP directed broadcasts: [edit interfaces] user@switch# set irb.1 family inet targeted-broadcast Copyright © 2015, Juniper Networks, Inc.
  • Page 121: Tracing Operations Of An Individual Router Or Switch Interface

    By default, interface process operations are placed in the file named dcd and three 1-MB files of tracing information are maintained. You can specify the following flags in the interfaces traceoptions statement: —Log changes that produce configuration events. change-events config-states —Log the configuration state machine changes. Copyright © 2015, Juniper Networks, Inc.
  • Page 122 For general information about tracing, see the tracing and logging information in the Junos OS Administration Library for Routing Devices. Related Tracing Interface Operations Overview Documentation Tracing Operations of an Individual Router or Switch Interface on page 101 Copyright © 2015, Juniper Networks, Inc.
  • Page 123: Configuration Statements

    802.3ad on page 154 accounting-profile on page 155 address on page 156 aggregated-devices on page 158 aggregated-ether-options on page 159 arp (Interfaces) on page 160 auto-negotiation on page 161 bandwidth (Interfaces) on page 163 Copyright © 2015, Juniper Networks, Inc.
  • Page 124 (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet) on page 205 member (Interface Ranges) on page 206 member-range on page 207 members on page 208 mtu on page 210 native-vlan-id on page 213 no-gratuitous-arp-request on page 214 no-redirects on page 214 Copyright © 2015, Juniper Networks, Inc.
  • Page 125: [Edit Chassis] Configuration Statement Hierarchy On Ex Series Switches

    Supported Statements in the [edit chassis] Hierarchy Level on page 105 Supported Statements in the [edit chassis] Hierarchy Level The following hierarchy shows the configuration statements supported on [edit chassis] EX Series switches: chassis aggregated-devices ethernet device-count number; lacp { link-protection non-revertive; system-priority system-priority-number Copyright © 2015, Juniper Networks, Inc.
  • Page 126: Level

    Configuring Aggregated Ethernet Links (CLI Procedure) on page 82 Documentation Configuring the LCD Panel on EX Series Switches (CLI Procedure) Configuring Graceful Routing Engine Switchover in a Virtual Chassis (CLI Procedure) Configuring Power Supply Redundancy (CLI Procedure) Copyright © 2015, Juniper Networks, Inc.
  • Page 127: Switches

    (CLI) on the switch are supported on the switch and operate as documented with the following exceptions: Table 31: Unsupported [edit forwarding-options] Subhierarchies on EX Series Switches Subhierarchy Hierarchy Level accounting [edit forwarding-options] Copyright © 2015, Juniper Networks, Inc.
  • Page 128: [Edit Interfaces] Configuration Statement Hierarchy On Ex Series Switches

    Configuring a Layer 3 Subinterface (CLI Procedure) on page 97 Configuring Integrated Routing and Bridging Interfaces (CLI Procedure) Configuring the Virtual Management Ethernet Interface for Global Management of an EX Series Virtual Chassis (CLI Procedure) Copyright © 2015, Juniper Networks, Inc.
  • Page 129: Supported Statements In The [Edit Interfaces Ae] Hierarchy Level

    { tag-protocol-id identifiers; (flow-control | no-flow-control); lacp (active | passive); link-protection { disable; (revertive | non-revertive); periodic interval; system-priority number; (link-protection | no-link-protection); link-speed speed; local-bias; (loopback | no-loopback); minimum-links number; rebalance-periodic; description text; Copyright © 2015, Juniper Networks, Inc.
  • Page 130 { members [members]; family inet { accounting { destination-class-usage; source-class-usage { input; output; address ipv4-address { ip-address (mac | multicast-mac) mac-address <publish>; broadcast address; preferred; primary; vrrp-group group-number { Copyright © 2015, Juniper Networks, Inc.
  • Page 131 { accounting { destination-class-usage; source-class-usage { input; output; address address { eui-64; ndp ip-address (mac | multicast-mac) mac-address <publish>; preferred; primary; vrrp-inet6-group group-id { accept-data | no-accept-data; advertisements-threshold number; authentication-key key; Copyright © 2015, Juniper Networks, Inc.
  • Page 132 { loose; family iso { address interface-address; bytes; input-vlan-map action; output-vlan-map action; proxy-arp (restricted | unrestricted); (traps | no-traps); vlan-id vlan-id; vlan-id-list [vlan-id vlan-id–vlan-id]; vlan-id (VLAN Tagging and Layer 3 Subinterfaces) vlan-id-number; vlan-tagging; Copyright © 2015, Juniper Networks, Inc.
  • Page 133: Unsupported Statements In The [Edit Interfaces Ae] Hierarchy Level

    [edit interfaces ae unit family inet] simple-filter [edit interfaces ae unit family inet] targeted-broadcast [edit interfaces ae unit family inet] unnumbered-address [edit interfaces ae unit family inet] bandwidth-threshold [edit interfaces ae unit family inet address vrrp-group track interface] Copyright © 2015, Juniper Networks, Inc.
  • Page 134: [Edit Interfaces Et] Configuration Statement Hierarchy On Ex Series

    Supported Statements in the [edit interfaces et] Hierarchy Level The following hierarchy shows the [edit interfaces et] configuration statements supported on EX Series switches. interfaces { et-fpc/pic/port { accounting-profile name; description text; disable; encapsulation type; ether-options { 802.3ad aex; (backup | primary); Copyright © 2015, Juniper Networks, Inc.
  • Page 135 { filter { input filter-name; output filter-name; interface-mode (access | trunk); recovery-timeout seconds; storm-control profile-name; vlan { members (vlan-name |[-vlan-names] | all); family inet { accounting { destination-class-usage; Copyright © 2015, Juniper Networks, Inc.
  • Page 136 [addresses]; vrrp-inherit-from { active-group group-number; active-interface interface-name; filter input filter-name; output filter-name; bytes; no-neighbor-learn; no-redirects; primary; rpf-check { fail-filter filter-name; mode { loose; family inet6 { accounting { destination-class-usage; source-class-usage { input; output; Copyright © 2015, Juniper Networks, Inc.
  • Page 137 { active-group group-name; active-interface interface-name; (dad-disable | no-dad-disable); filter input filter-name; output filter-name; bytes; nd6-stale-time time; no-neighbor-learn; no-redirects; policer { input policer-name; output policer-name; rpf-check { fail-filter filter-name; mode { loose; Copyright © 2015, Juniper Networks, Inc.
  • Page 138: Unsupported Statements In The [Edit Interfaces Et] Hierarchy Level

    [edit interfaces et ether-options] no-source-filtering [edit interfaces et ether-options] accept-source-mac [edit interfaces et unit] layer2-policer [edit interfaces et unit] native-inner-vlan-id [edit interfaces et unit] vlan-id-range [edit interfaces et unit] vlan-tags [edit interfaces et unit] Copyright © 2015, Juniper Networks, Inc.
  • Page 139: [Edit Interfaces Ge] Configuration Statement Hierarchy On Ex Series

    This topic lists supported and unsupported configuration statements in the [edit interfaces hierarchy level on EX Series switches. Supported statements are those that you can use to configure some aspect of a software feature on the switch. Copyright © 2015, Juniper Networks, Inc.
  • Page 140: Supported Statements In The [Edit Interfaces Ge] Hierarchy Level

    { tag-protocol-id [tpids]; (flow-control | no-flow-control); ieee-802-3az-eee; (loopback | no-loopback); no-auto-mdix; flexible-vlan-tagging; (gratuitous-arp-reply | no-gratuitous-arp-reply); hold-time up milliseconds down milliseconds; link-mode full-duplex; bytes; native-vlan-id no-gratuitous-arp-request; speed speed; traceoptions flag flag; (traps | no-traps); Copyright © 2015, Juniper Networks, Inc.
  • Page 141 (mac | multicast-mac) mac-address <publish>; broadcast address; preferred; primary; vrrp-group group-number { (accept-data | no-accept-data); advertise–interval seconds; advertisements-threshold number; authentication-key key; authentication-type authentication; fast-interval milliseconds; (preempt | no-preempt) { hold-time seconds; priority number; Copyright © 2015, Juniper Networks, Inc.
  • Page 142 (mac | multicast-mac) mac-address <publish>; preferred; primary; vrrp-inet6-group group-id { accept-data | no-accept-data; advertisements-threshold number; authentication-key key; authentication-type authentication; fast-interval milliseconds; inet6-advertise-interval milliseconds; preempt | no-preempt { hold-time seconds; priority number; track { interface interface-name { priority-cost number; Copyright © 2015, Juniper Networks, Inc.
  • Page 143 { fail-filter filter-name; mode { loose; family iso { address interface-address; bytes; input-vlan-map action; interface-shared-with { psd-name; output-vlan-map action; proxy-arp (restricted | unrestricted); swap-by-poppush; (traps | no-traps); vlan-id vlan-id-number; vlan-id-list [vlan-id vlan-id–vlan-id]; vlan-tagging; Copyright © 2015, Juniper Networks, Inc.
  • Page 144: Unsupported Statements In The [Edit Interfaces Ge] Hierarchy Level

    [edit interfaces ge unit family] bridge-domain-type [edit interfaces ge unit family ethernet-switching] inner-vlan-id-list [edit interfaces ge unit family ethernet-switching] vlan-rewrite [edit interfaces ge unit family ethernet-switching] policer [edit interfaces ge unit family inet] Copyright © 2015, Juniper Networks, Inc.
  • Page 145: [Edit Interfaces Interface-Range] Configuration Statement Hierarchy On Ex Series

    Not all features are supported on all switch platforms. For detailed information about feature support on specific EX Series switch platforms, seeEX Series Switch Software Features Overview Copyright © 2015, Juniper Networks, Inc.
  • Page 146: Supported Statements In The [Edit Interfaces Interface-Range] Hierarchy

    (backup | primary); lacp force-up; (auto-negotiation | no-auto-negotiation); (flow-control | no-flow-control); (loopback | no-loopback); (gratuitous-arp-reply | no-gratuitous-arp-reply); hold-time up milliseconds down milliseconds; link-mode mode; member interface-name; member-range starting-interface name to ending-interface name; bytes; native-vlan-id Copyright © 2015, Juniper Networks, Inc.
  • Page 147 (mac | multicast-mac) mac-address <publish>; broadcast address; destination-class-usage; destination-profile; master-only; preferred; primary; vrrp-group group-number { (accept-data | no-accept-data); advertise–interval seconds; authentication-key key; authentication-type authentication; fast-interval milliseconds; (preempt | no-preempt) { hold-time seconds; priority number; Copyright © 2015, Juniper Networks, Inc.
  • Page 148 | no-preempt { hold-time seconds; priority number; track { interface interface-name { priority-cost number; priority-hold-time seconds; route ( address | routing-instance routing-instance-name ); virtual-inet6-address [addresses]; virtual-link-local-address ipv6–address; vrrp-inherit-from { Copyright © 2015, Juniper Networks, Inc.
  • Page 149: Table 35: Unsupported [Edit Interfaces Interface-Range] Configuration

    Statement Hierarchy NOTE: Variables, such as interface-range, are not shown in the statements or hierarchies. cesopsn-options [edit interfaces interface-range] container-options [edit interfaces interface-range] framing [edit interfaces interface-range] [edit interfaces interface-range] logical-tunnel-options [edit interfaces interface-range] Copyright © 2015, Juniper Networks, Inc.
  • Page 150 [edit interfaces interface-range ether-options] source-filtering [edit interfaces interface-range ether-options] accept-source-mac [edit interfaces interface-range unit] allow-any-vci [edit interfaces interface-range unit] atm-l2circuit-mode [edit interfaces interface-range unit] atm-scheduler-map [edit interfaces interface-range unit] cell-bundle-size [edit interfaces interface-range unit] Copyright © 2015, Juniper Networks, Inc.
  • Page 151 [edit interfaces interface-range unit] multicast-vci [edit interfaces interface-range unit] multilink-max-classes [edit interfaces interface-range unit] multipoint [edit interfaces interface-range unit] native-inner-vlan-id [edit interfaces interface-range unit] oam-liveness [edit interfaces interface-range unit] oam-period [edit interfaces interface-range unit] Copyright © 2015, Juniper Networks, Inc.
  • Page 152 [edit interfaces interface-range unit] [edit interfaces interface-range unit] mlfr-end-to-end [edit interfaces interface-range unit family] mlfr-uni-nni [edit interfaces interface-range unit family] mlppp [edit interfaces interface-range unit family] mpls [edit interfaces interface-range unit family] [edit interfaces interface-range unit family] Copyright © 2015, Juniper Networks, Inc.
  • Page 153 [edit interfaces interface-range unit family inet6] group [edit interfaces interface-range unit family inet6 filter] bandwidth-threshold [edit interfaces interface-range unit family inet6 address vrrp-group track interface] Related [edit interfaces] Configuration Statement Hierarchy on EX Series Switches on page 108 Documentation Copyright © 2015, Juniper Networks, Inc.
  • Page 154: Switches

    (traps | no-traps); unit logical-unit-number { accounting-profile name; bandwidth rate; description text; disable; family inet { accounting { destination-class-usage; source-class-usage { input; output; address ipv4-address { Copyright © 2015, Juniper Networks, Inc.
  • Page 155 { fail-filter filter-name; mode { loose; family inet6 { accounting { destination-class-usage; source-class-usage { input; output; address address { eui-64; ndp ip-address (mac | multicast-mac) mac-address <publish>; preferred; Copyright © 2015, Juniper Networks, Inc.
  • Page 156 { input policer-name; output policer-name; rpf-check { fail-filter filter-name; mode { loose; family iso { address interface-address; bytes; native-inner-vlan-id vlan-id; proxy-arp (restricted | unrestricted); (traps | no-traps); vlan-id-list [vlan-id’s]; vlan-id-range [vlan-id-range]; Copyright © 2015, Juniper Networks, Inc.
  • Page 157: Unsupported Statements In The [Edit Interfaces Irb] Hierarchy Level

    [edit interfaces] Configuration Statement Hierarchy on EX Series Switches on page 108 Documentation [edit interfaces lo] Configuration Statement Hierarchy on EX Series Switches This topic lists supported and unsupported configuration statements in the [edit interfaces hierarchy level on EX Series switches. Copyright © 2015, Juniper Networks, Inc.
  • Page 158: Supported Statements In The [Edit Interfaces Lo] Hierarchy Level

    { preferred; primary; vrrp-group group-number { (accept-data | no-accept-data); advertise–interval seconds; authentication-key key; authentication-type authentication; fast-interval milliseconds; (preempt | no-preempt) { hold-time seconds; priority number; track { interface interface-name { bandwidth-threshold bandwidth; priority-cost number; Copyright © 2015, Juniper Networks, Inc.
  • Page 159 { interface interface-name { bandwidth-threshold bandwidth priority-cost number; priority-cost number; priority-hold-time seconds; route ( address | routing-instance routing-instance-name ); virtual-inet6-address [addresses]; virtual-link-local-address ipv6–address; vrrp-inherit-from { active-group group-name; active-interface interface-name; Copyright © 2015, Juniper Networks, Inc.
  • Page 160: Unsupported Statements In The [Edit Interfaces Lo] Hierarchy Level

    [edit interfaces] Configuration Statement Hierarchy on EX Series Switches on page 108 [edit interfaces me] Configuration Statement Hierarchy on EX Series Switches This topic lists supported and unsupported configuration statements in the [edit interfaces hierarchy level on EX Series switches. Copyright © 2015, Juniper Networks, Inc.
  • Page 161: Supported Statements In The [Edit Interfaces Me] Hierarchy Level

    { filter { input filter-name; output filter-name; native-vlan-id vlan-id-number; port-mode (access | trunk); vlan { members [ members]; family inet { accounting { destination-class-usage; source-class-usage { input; output; Copyright © 2015, Juniper Networks, Inc.
  • Page 162 { eui-64; ndp ip-address (mac | multicast-mac) mac-address <publish>; preferred; primary; (dad-disable | no-dad-disable); filter group group-name; input filter-name; output filter-name; bytes; no-neighbor-learn; policer { input policer-name; output policer-name; rpf-check; family iso { Copyright © 2015, Juniper Networks, Inc.
  • Page 163: Unsupported Statements In The [Edit Interfaces Me] Hierarchy Level

    [edit interfaces me unit family inet] policer [edit interfaces me unit family inet] sampling [edit interfaces me unit family inet] service [edit interfaces me unit family inet] unnumbered-address [edit interfaces me unit family inet] Copyright © 2015, Juniper Networks, Inc.
  • Page 164: [Edit Interfaces Vme] Configuration Statement Hierarchy On Ex Series

    [edit interfaces vme] configuration statements supported on EX Series switches. interfaces { vme { accounting-profile name; description text; disable; (gratuitous-arp-reply | no-gratuitous-arp-reply); hold-time up milliseconds down milliseconds; bytes; no-gratuitous-arp-request; traceoptions flag flag; (traps | no-traps); Copyright © 2015, Juniper Networks, Inc.
  • Page 165 [ addresses ]; virtual-link-local-address address; vrrp-inherit-from { active-group group-number; active-interface interface-name; dhcp { client-identifier (ascii client-id | hexadecimal client-id); lease-time (seconds | infinte); retransmission-attempt number; retransmission-interval sections; server-address ip-address; update-server vendor-id filter Copyright © 2015, Juniper Networks, Inc.
  • Page 166 ( address | routing-instance routing-instance-name ); virtual-inet6-address [addresses]; virtual-link-local-address ipv6–address; vrrp-inherit-from { active-group group-name; active-interface interface-name; (dad-disable | no-dad-disable); filter group group-name; input filter-name; output filter-name; bytes; no-neighbor-learn; policer { Copyright © 2015, Juniper Networks, Inc.
  • Page 167: Unsupported Statements In The [Edit Interfaces Vme] Hierarchy Level

    Unsupported Statements in the [edit interfaces xe] Hierarchy Level on page 151 Supported Statements in the [edit interfaces xe] Hierarchy Level The following hierarchy shows the [edit interfaces xe] configuration statements supported on EX Series switches. Copyright © 2015, Juniper Networks, Inc.
  • Page 168 { filter { input filter-name; output filter-name; policer{ input policer-name; output policer-name; family ethernet-switching { filter { input filter-name; output filter-name; interface-mode (access | trunk) ; Copyright © 2015, Juniper Networks, Inc.
  • Page 169 { priority-cost number; priority-hold-time seconds; route ip-address/mask routing-instance instance-name priority-cost cost; virtual-address [addresses]; vrrp-inherit-from { active-group group-number; active-interface interface-name; filter input filter-name; output filter-name; bytes; no-neighbor-learn; no-redirects; primary; rpf-check fail-filter filter-name; mode { loose; Copyright © 2015, Juniper Networks, Inc.
  • Page 170 (address | routing-instance routing-instance-name); virtual-inet6-address [addresses]; virtual-link-local-address ipv6–address; vrrp-inherit-from { active-group group-name; active-interface interface-name; (dad-disable | no-dad-disable); filter input filter-name; output filter-name; bytes; no-neighbor-learn; no-redirects; policer { input policer-name; output policer-name; rpf-check fail-filter filter-name; mode { Copyright © 2015, Juniper Networks, Inc.
  • Page 171: Unsupported Statements In The [Edit Interfaces Xe] Hierarchy Level

    [edit interfaces xe ether-options] ignore-l3-incompletes [edit interfaces xe ether-options] mpls [edit interfaces xe ether-options] source-address-filter [edit interfaces xe ether-options] source-filtering [edit interfaces xe ether-options] no-source-filtering [edit interfaces xe ether-options] accept-source-mac [edit interfaces xe unit] Copyright © 2015, Juniper Networks, Inc.
  • Page 172: Switches

    [edit interfaces xe unit family inet6] bandwidth-threshold [edit interfaces xe unit family inet6 address vrrp-group track interface] group [edit interfaces xe unit family inet6 filter] [edit interfaces xe unit input-vlan-map] push [edit interfaces xe unit output-vlan-map] Copyright © 2015, Juniper Networks, Inc.
  • Page 173: Supported Statements In The [Edit Protocols Lacp] Hierarchy Level

    [edit protocols lacp] command-line interface (CLI) on the switch are supported on the switch and operate as documented. Related [edit protocols] Configuration Statement Hierarchy on EX Series Switches Documentation Copyright © 2015, Juniper Networks, Inc.
  • Page 174 Ethernet Interfaces on EX8200 Switches Configuring Aggregated Ethernet Links (CLI Procedure) on page 82 Configuring Aggregated Ethernet LACP (CLI Procedure) on page 86 Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure) on page 87 Copyright © 2015, Juniper Networks, Inc.
  • Page 175: Accounting-Profile

    Level interface-control—To add this statement to the configuration. Related Applying an Accounting Profile to the Physical Interface on page 75 Documentation Applying an Accounting Profile to the Logical Interface on page 76 Copyright © 2015, Juniper Networks, Inc.
  • Page 176: Address

    { priority; route ip-address/mask routing-instance instance-name priority-cost cost; virtual-address [ addresses ]; Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family], [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family family] Copyright © 2015, Juniper Networks, Inc.
  • Page 177 Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring the Protocol Family Documentation negotiate-address unnumbered-address (Ethernet) Junos OS Administration Library for Routing Devices family Copyright © 2015, Juniper Networks, Inc.
  • Page 178: Aggregated-Devices

    Configuring Aggregated Ethernet Links (CLI Procedure) on page 82 Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure) on page 87 Understanding Aggregated Ethernet Interfaces and LACP on page 8 Junos OS Ethernet Interfaces Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 179: Aggregated-Ether-Options

    Configuring Aggregated Ethernet Links (CLI Procedure) on page 82 Configuring Aggregated Ethernet LACP (CLI Procedure) on page 86 Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure) on page 87 Configuring Q-in-Q Tunneling (CLI Procedure) Junos OS Ethernet Interfaces Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 180: Arp (Interfaces)

    QFabric systems. edit logical-systems Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring Static ARP Table Entries on page 79 Documentation Configuring Static ARP Entries Copyright © 2015, Juniper Networks, Inc.
  • Page 181: Auto-Negotiation

    If autonegotiation is disabled, the link speed and link mode must be configured. NOTE: On T4000 routers, the auto-negotiation command is ignored for interfaces other than Gigabit Ethernet. Copyright © 2015, Juniper Networks, Inc.
  • Page 182 Related Gigabit Ethernet Autonegotiation Overview Documentation Configuring J Series Services Router Switching Interfaces Configuring Gigabit Ethernet Interfaces (CLI Procedure) Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Copyright © 2015, Juniper Networks, Inc.
  • Page 183: Bandwidth (Interfaces)

    1 cps = 384 bps. Range: Not limited. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring the Interface Bandwidth on page 52 Documentation Copyright © 2015, Juniper Networks, Inc.
  • Page 184: Broadcast

    QFabric systems. edit logical-systems Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring the Interface Address on page 48 Documentation Copyright © 2015, Juniper Networks, Inc.
  • Page 185: Chassis

    Statement introduced in Junos OS Release 9.0 for EX Series switches. Description Configure chassis-specific properties for the switch. 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 © 2015, Juniper Networks, Inc.
  • Page 186: Description (Interfaces)

    Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Configuring Gigabit and 10-Gigabit Ethernet Interfaces Enabling and Disabling Insertion of Option 82 Information Junos OS Network Interfaces Library for Routing Devices Example: Connecting Access Switches to a Distribution Switch Copyright © 2015, Juniper Networks, Inc.
  • Page 187: Device-Count

    Options number —Maximum number of aggregated Ethernet logical interfaces on the switch. Range: 1 through 32 for EX2200, EX3200, and standalone EX3300 switches and for EX3300 Virtual Chassis Range: 1 through 64 for standalone EX4200, standalone EX4500, and EX6200 switches...
  • Page 188: Disable (Interface)

    When you disable or deactivate an interface, then all the references made to the deactivated interface must be removed from the routing instance. WARNING: Do not stare into the laser beam or view it directly with optical instruments even if the interface has been disabled. Copyright © 2015, Juniper Networks, Inc.
  • Page 189 Chapter 3: Configuration Statements Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Disabling a Physical Interface on page 45 Documentation Disabling a Logical Interface on page 47 Copyright © 2015, Juniper Networks, Inc.
  • Page 190: Enhanced-Hash-Key

    When ECMP is enabled, the hashing algorithm determines how incoming traffic is forwarded to the next-hop device. 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 © 2015, Juniper Networks, Inc.
  • Page 191 (CLI Procedure) on page 94 Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic on page 11 hash-mode on page 183 inet on page 187 inet6 on page 189 layer2 on page 198 Copyright © 2015, Juniper Networks, Inc.
  • Page 192: Ether-Options

    Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 35 Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure) on page 87 Configuring Q-in-Q Tunneling (CLI Procedure) Junos OS Ethernet Interfaces Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 193: Ethernet (Aggregated Devices)

    For interfaces that carry IP version 6 (IPv6) traffic, automatically generate the host number portion of interface addresses. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring the Interface Address on page 48 Documentation Copyright © 2015, Juniper Networks, Inc.
  • Page 194: Family

    { destination-class-usage; source-class-usage { input; output; address ipv4-address { ip-address (mac | multicast-mac) mac-address <publish>; broadcast address; preferred; primary; vrrp-group group-number { (accept-data | no-accept-data); advertise–interval seconds; advertisements-threshold number; authentication-key key; authentication-type authentication; Copyright © 2015, Juniper Networks, Inc.
  • Page 195 [addresses]; vrrp-inherit-from { active-group group-number; active-interface interface-name; filter input filter-name; output filter-name; bytes; no-neighbor-learn; no-redirects; primary; rpf-check { fail-filter filter-name; mode { loose; Copyright © 2015, Juniper Networks, Inc.
  • Page 196 { active-group group-name; active-interface interface-name; (dad-disable | no-dad-disable); filter input filter-name; output filter-name; bytes; nd6-stale-time time; no-neighbor-learn; no-redirects; policer { input policer-name; output policer-name; rpf-check { fail-filter filter-name; mode { loose; Copyright © 2015, Juniper Networks, Inc.
  • Page 197 Interfaces on EX4300 switches are set to family ethernet-switching by the default factory configuration. Before you can change the family setting for an interface to another family type, you must delete this default setting or any user-configured family setting. Copyright © 2015, Juniper Networks, Inc.
  • Page 198: Table 40: Protocol Families And Supported Interface Types

    IPv6 protocol family inet6 Junos OS protocol family for IS-IS traffic 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 © 2015, Juniper Networks, Inc.
  • Page 199 Configuring a DHCP Server on Switches (CLI Procedure) Documentation Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Configuring Aggregated Ethernet Links (CLI Procedure) on page 82 Configuring Integrated Routing and Bridging Interfaces (CLI Procedure) Copyright © 2015, Juniper Networks, Inc.
  • Page 200: Filter

    Junos OS Services Interfaces Library for Routing Devices Routing Policy Feature Guide for Routing Devices Junos OS Administration Library for Routing Devices Configuring Gigabit Ethernet Interfaces (CLI Procedure) Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Copyright © 2015, Juniper Networks, Inc.
  • Page 201: Flow-Control

    Level interface-control—To add this statement to the configuration. Related Configuring Flow Control on page 47 Documentation Configuring Gigabit Ethernet Interfaces (CLI Procedure) Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Copyright © 2015, Juniper Networks, Inc.
  • Page 202: Force-Up

    Updating of the ARP cache is disabled on all Ethernet interfaces. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring Gratuitous ARP on page 78 Documentation no-gratuitous-arp-request on page 214 Copyright © 2015, Juniper Networks, Inc.
  • Page 203: Hash-Mode

    —Set the hashing algorithm to use fields in the Layer 2 header to make layer-2-header hashing decisions. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Copyright © 2015, Juniper Networks, Inc.
  • Page 204 (CLI Procedure) on page 94 Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic on page 11 enhanced-hash-key on page 170 inet on page 187 inet6 on page 189 layer2 on page 198 Copyright © 2015, Juniper Networks, Inc.
  • Page 205: Hold-Time (Physical Interface)

    Range: 0 through 4,294,967,295 milliseconds Default: 0 milliseconds (interface transitions are not damped) Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related advertise-interval Documentation interfaces (for EX Series switches) Copyright © 2015, Juniper Networks, Inc.
  • Page 206: Ieee-802-3Az-Eee

    EEE is disabled on EEE-capable interfaces. Required Privilege system—To view this statement in the configuration. Level system-control—To add this statement to the configuration. Related Configuring Energy Efficient Ethernet on Interfaces (CLI Procedure) on page 93 Documentation Copyright © 2015, Juniper Networks, Inc.
  • Page 207: Inet (Enhanced-Hash-Key)

    —Exclude the IPv4 destination address field from the hashing algorithm. —Exclude the IPv4 source address field from the hashing algorithm. no-ipv4-source-address no-l4-destination-port —Exclude the Layer 4 destination port field from the hashing algorithm. Copyright © 2015, Juniper Networks, Inc.
  • Page 208 Documentation (CLI Procedure) on page 94 Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic on page 11 enhanced-hash-key on page 170 hash-mode on page 183 inet6 on page 189 Copyright © 2015, Juniper Networks, Inc.
  • Page 209: Inet6 (Enhanced-Hash-Key)

    —Exclude the IPv6 destination address field from the hashing no-ipv6-destination-address algorithm. no-ipv6-source-address —Exclude the IPv6 source address field from the hashing algorithm. —Exclude the Layer 4 destination port field from the hashing no-l4-destination-port algorithm. Copyright © 2015, Juniper Networks, Inc.
  • Page 210: Interface (Multichassis Protection)

    (ICL-PL). The two switches hosting a multichassis link aggregation group (MC-LAG) use this link to pass Inter-Chassis Control Protocol (ICCP) and data traffic. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Copyright © 2015, Juniper Networks, Inc.
  • Page 211: Interface-Mode

    Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring a Logical Interface for Access Mode Documentation Configuring a Logical Interface for Trunk Mode Copyright © 2015, Juniper Networks, Inc.
  • Page 212 Network Interfaces for EX4300 Switches Example: Connecting Access Switches to a Distribution Switch Copyright © 2015, Juniper Networks, Inc.
  • Page 213: Interface-Range

    Release Information Statement introduced in Junos OS Release 10.0 for EX Series switches. Description Group interfaces that share a common configuration profile. NOTE: You can specify interface ranges only for Gigabit and 10-Gigabit Ethernet interfaces. Copyright © 2015, Juniper Networks, Inc.
  • Page 214 Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Understanding Interface Ranges on EX Series Switches Understanding Interface Ranges on EX Series Switches on page 24 EX Series Switches Interfaces Overview on page 3 Junos OS Interfaces Fundamentals Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 215: Lacp (Aggregated Ethernet)

    Default If you do not specify LACP as either , LACP remains passive. active passive Options —Initiate transmission of LACP packets. active admin-key number —Specify an administrative key for the router or switch. Copyright © 2015, Juniper Networks, Inc.
  • Page 216 Configuring Aggregated Ethernet LACP Documentation Configuring Aggregated Ethernet LACP (CLI Procedure) on page 86 Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between an EX4200 Virtual Chassis Access Switch and an EX4200 Virtual Chassis Distribution Switch Copyright © 2015, Juniper Networks, Inc.
  • Page 217: Lacp (802.3Ad)

    Configuring Aggregated Ethernet LACP (CLI Procedure) on page 86 Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure) on page 87 Understanding Aggregated Ethernet Interfaces and LACP on page 8 Junos OS Ethernet Interfaces Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 218: Layer2 (Enhanced-Hash-Key)

    Source MAC address Options —Exclude the destination MAC address field from the hashing no-destination-mac-address algorithm. no-ether-type —Exclude the Ethertype field from the hashing algorithm. —Exclude the source MAC address field from the hashing no-source-mac-address algorithm. Copyright © 2015, Juniper Networks, Inc.
  • Page 219 Configuring the Fields in the Algorithm Used To Hash LAG Bundle and ECMP Traffic Documentation (CLI Procedure) on page 94 Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic on page 11 enhanced-hash-key on page 170 hash-mode on page 183 Copyright © 2015, Juniper Networks, Inc.
  • Page 220: Link-Mode

    On EX4300 switches, the interfaces operate in full-duplex mode only. On EX Series switches, if no-auto-negotiation is specified in [edit interfaces , you can select only interface-name ether-options] full-duplex . If is specified, you can select any mode. half-duplex auto-negotiation Copyright © 2015, Juniper Networks, Inc.
  • Page 221 Related Configuring the Link Characteristics on Ethernet Interfaces Documentation Understanding Management Ethernet Interfaces Configuring Gigabit Ethernet Interfaces (CLI Procedure) Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Copyright © 2015, Juniper Networks, Inc.
  • Page 222: Link-Protection

    Level interface-control—To add this statement to the configuration. Related Configuring Aggregated Ethernet Link Protection on page 89 Documentation Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure) on page 87 Copyright © 2015, Juniper Networks, Inc.
  • Page 223: Link-Speed (Aggregated Ethernet)

    —Links are 100 Gbps. 100g —Links are 100 Mbps. 100m —Links are 10 Gbps. —Links are 1 Gbps. —Links are 40 Gbps. —Links are 50 Gbps. —Links are 80 Gbps. —Links are 8 Gbps. Copyright © 2015, Juniper Networks, Inc.
  • Page 224: Local-Bias

    Required Privilege system—To view this statement in the configuration. Level system-control—To add this statement to the configuration. Related Configuring Local Link Bias (CLI Procedure) on page 94 Documentation Understanding Local Link Bias on page 16 Copyright © 2015, Juniper Networks, Inc.
  • Page 225: Loopback (Aggregated Ethernet, Fast Ethernet, And Gigabit Ethernet)

    Gigabit Ethernet, and 10-Gigabit Ethernet interfaces connect to a remote system. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring Ethernet Loopback Capability on page 77 Documentation Copyright © 2015, Juniper Networks, Inc.
  • Page 226: Member (Interface Ranges)

    Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Understanding Interface Ranges on EX Series Switches Understanding Interface Ranges on EX Series Switches on page 24 EX Series Switches Interfaces Overview on page 3 Junos OS Interfaces Fundamentals Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 227: Member-Range

    Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Understanding Interface Ranges on EX Series Switches Understanding Interface Ranges on EX Series Switches on page 24 EX Series Switches Interfaces Overview on page 3 Junos OS Interfaces Fundamentals Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 228: Members

    —Specifies that this trunk interface is a member of all the VLANs that are configured on this switch. When a new VLAN is configured on the switch, this trunk interface automatically becomes a member of the VLAN. Copyright © 2015, Juniper Networks, Inc.
  • Page 229 Configuring VLANs for EX Series Switches (CLI Procedure) Configuring VLANs for EX Series Switches (CLI Procedure) Creating a Series of Tagged VLANs (CLI Procedure) Understanding Bridging and VLANs on EX Series Switches Junos OS Ethernet Interfaces Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 230: Mtu

    IRB interface or RVI, as well as on the IRB interface or RVI itself (the interface named irb or vlan, respectively). CAUTION: For EX Series switches, setting or deleting the jumbo MTU size on an IRB interface or RVI while the switch is transmitting packets might cause packets to be dropped. Copyright © 2015, Juniper Networks, Inc.
  • Page 231 Default: 1500 bytes (INET, INET6, and ISO families), 1448 bytes (MPLS), 1514 bytes (EX Series switch interfaces) Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Copyright © 2015, Juniper Networks, Inc.
  • Page 232 Configuring Routed VLAN Interfaces (CLI Procedure) Configuring Integrated Routing and Bridging Interfaces (CLI Procedure) Configuring the Media MTU on page 53 Configuring the MTU for Layer 2 Interfaces Setting the Protocol MTU on page 65 Copyright © 2015, Juniper Networks, Inc.
  • Page 233: Native-Vlan-Id

    Related Configuring Mixed Tagging Support for Untagged Packets Documentation Configuring a Logical Interface for Access Mode Configuring the Native VLAN Identifier (CLI Procedure) Understanding Bridging and VLANs on EX Series Switches Copyright © 2015, Juniper Networks, Inc.
  • Page 234: No-Gratuitous-Arp-Request

    Level interface-control—To add this statement to the configuration. Related Disabling the Transmission of Redirect Messages on an Interface on page 80 Documentation Junos OS Administration Library for Routing Devices Copyright © 2015, Juniper Networks, Inc.
  • Page 235: Periodic

    Configuring Aggregated Ethernet LACP Documentation Configuring Aggregated Ethernet LACP (CLI Procedure) on page 86 Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200 Virtual Chassis Access Switch and an EX4200 Virtual Chassis Distribution Switch Copyright © 2015, Juniper Networks, Inc.
  • Page 236: Preferred

    The lowest-numbered address on the subnet is the preferred address. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring the Interface Address on page 48 Documentation Copyright © 2015, Juniper Networks, Inc.
  • Page 237: Primary (Address On Interface)

    For unicast traffic, the primary address is the lowest non-127 (in other words, non-loopback) preferred address on the unit. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Configuring the Interface Address on page 48 Documentation Copyright © 2015, Juniper Networks, Inc.
  • Page 238: Proxy-Arp

    Configuring Restricted and Unrestricted Proxy ARP on page 80 Documentation Configuring Proxy ARP (CLI Procedure) Configuring Proxy ARP (CLI Procedure) Example: Configuring Proxy ARP on an EX Series Switch Configuring Gratuitous ARP on page 78 Copyright © 2015, Juniper Networks, Inc.
  • Page 239: Rpf-Check

    Related Example: Configuring Unicast RPF on an EX Series Switch Documentation Configuring Unicast RPF (CLI Procedure) on page 97 Disabling Unicast RPF (CLI Procedure) on page 99 Understanding Unicast RPF on page 19 Copyright © 2015, Juniper Networks, Inc.
  • Page 240: Speed (Ethernet)

    Related Configuring the Interface Speed Documentation Configuring the Interface Speed on Ethernet Interfaces Configuring Gigabit Ethernet Autonegotiation Configuring J Series Services Router Switching Interfaces Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Copyright © 2015, Juniper Networks, Inc.
  • Page 241: Traceoptions (Individual Interfaces)

    Then, the oldest trace file is overwritten. flag —Tracing operation to perform. To specify more than one tracing operation, include multiple statements. The following are the interface-specific tracing options. flag —All interface tracing operations —Interface events event Copyright © 2015, Juniper Networks, Inc.
  • Page 242 —Trace ISDN Q.921 frames q921 —Trace ISDN Q.931 frames q931 Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Related Tracing Operations of an Individual Router Interface Documentation Copyright © 2015, Juniper Networks, Inc.
  • Page 243: Traceoptions (Interface Process)

    —Log changes that produce configuration events change-events —Log the configuration state machine changes config-states —Log configuration IPC messages to kernel kernel —Log details of configuration messages to kernel kernel-detail no-world-readable —(Optional) Disallow any user to read the log file. Copyright © 2015, Juniper Networks, Inc.
  • Page 244: Transmit-Interval (Liveness Detection)

    The larger of the two numbers is accepted as the transmit interval for that peer. The remaining statements are explained separately. Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Copyright © 2015, Juniper Networks, Inc.
  • Page 245: Traps

    Level interface-control—To add this statement to the configuration. Related Enabling or Disabling SNMP Notifications on Physical Interfaces Documentation Enabling or Disabling SNMP Notifications on Logical Interfaces on page 81 Copyright © 2015, Juniper Networks, Inc.
  • Page 246: Unit

    Configuring Gigabit Ethernet Interfaces (CLI Procedure) Documentation Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Configuring Aggregated Ethernet Links (CLI Procedure) on page 82 EX Series Switches Interfaces Overview on page 3 Junos OS Ethernet Interfaces Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 247: Vlan (802.1Q Tagging)

    Example: Setting Up Bridging with Multiple VLANs for EX Series Switches Configuring Routed VLAN Interfaces (CLI Procedure) Configuring Integrated Routing and Bridging Interfaces (CLI Procedure) Understanding Bridging and VLANs on EX Series Switches Junos OS Ethernet Interfaces Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 248: Vlan-Id (Vlan Tagging And Layer 3 Subinterfaces)

    Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Configuring Gigabit Ethernet Interfaces (J-Web Procedure) on page 35 Configuring a Layer 3 Subinterface (CLI Procedure) on page 97 Configuring Q-in-Q Tunneling (CLI Procedure) Junos OS Ethernet Interfaces Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 249: Vlan-Tagging

    Configuring a Layer 3 Subinterface (CLI Procedure) on page 97 Configuring Tagged Aggregated Ethernet Interfaces on page 96 Configuring Interfaces for VPLS Routing Enabling VLAN Tagging 802.1Q VLANs Overview on page 26 vlan-id on page 228 Copyright © 2015, Juniper Networks, Inc.
  • Page 250 Network Interfaces for EX4300 Switches Copyright © 2015, Juniper Networks, Inc.
  • Page 251: Administration

    PART 3 Administration Routine Monitoring on page 233 Operational Commands on page 243 Copyright © 2015, Juniper Networks, Inc.
  • Page 252 Network Interfaces for EX4300 Switches Copyright © 2015, Juniper Networks, Inc.
  • Page 253: Routine Monitoring

    Action To view general interface information in the J-Web interface such as available interfaces, select Monitor > Interfaces. Click any interface to view details about its status. Copyright © 2015, Juniper Networks, Inc.
  • Page 254: Verifying The Status Of A Lag Interface

    Configuring Gigabit Ethernet Interfaces (CLI Procedure) Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32 Verifying the Status of a LAG Interface Purpose Verify that a LAG (ae0) has been created on the switch. Copyright © 2015, Juniper Networks, Inc.
  • Page 255: Verifying That Eee Is Saving Energy On Configured Ports

    (EX6200-48T) 150 W 12.17 W Total (non-PoE) Power allocated 950 W Total Power allocated for PoE Power Available (Redundant case) Total Power Available 1550 W On an EX4300 switch: user@switch>show chassis power-budget-statistics fpc 1 Copyright © 2015, Juniper Networks, Inc.
  • Page 256 SRE module, including PoE power. If you compare the values in the Power Used field before and after enabling EEE for FPC 3 and FPC 7, you will notice that power is saved when EEE is enabled. Copyright © 2015, Juniper Networks, Inc.
  • Page 257: Verifying That Lacp Is Configured Correctly And Bundle Members Are Exchanging Lacp Protocol Packets

    When LACP is enabled, at least one side must be set as active for the bundled link to be up. Verifying That LACP Packets Are Being Exchanged Purpose Verify that LACP packets are being exchanged between interfaces. Copyright © 2015, Juniper Networks, Inc.
  • Page 258: Verifying That Layer 3 Subinterfaces Are Working

    Interface Admin Link Proto Local Remote ge-0/0/0 ge-0/0/0.0 inet 1.1.1.1/24 ge-0/0/0.1 inet 2.1.1.1/24 ge-0/0/0.2 inet 3.1.1.1/24 ge-0/0/0.3 inet 4.1.1.1/24 Copyright © 2015, Juniper Networks, Inc.
  • Page 259: Verifying Unicast Rpf Status

    0 bps Input packets: 0 pps Output packets: 0 pps IPv6 transit statistics: Input bytes Output bytes Input packets: Output packets: Input errors: Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, Copyright © 2015, Juniper Networks, Inc.
  • Page 260 Logical interface ge-1/0/10.0 (Index 69) (SNMP ifIndex 59) (Generation 135) Flags: Device-Down SNMP-Traps 0x0 Encapsulation: ENET2 Traffic statistics: Input bytes Output bytes Input packets: Output packets: IPv6 transit statistics: Input bytes Output bytes Input packets: Output packets: Local statistics: Copyright © 2015, Juniper Networks, Inc.
  • Page 261: Verifying Ip Directed Broadcast Status

    Example: Configuring IP Directed Broadcast on an EX Series Switch. Related Configuring IP Directed Broadcast (CLI Procedure) Documentation Configuring IP Directed Broadcast (CLI Procedure) on page 100 Copyright © 2015, Juniper Networks, Inc.
  • Page 262 Network Interfaces for EX4300 Switches Example: Configuring IP Directed Broadcast on an EX Series Switch Copyright © 2015, Juniper Networks, Inc.
  • Page 263: Operational Commands

    Copyright © 2015, Juniper Networks, Inc.
  • Page 264: Monitor Interface

    To clear the accumulative counter, use clear interfaces interval command. Freezes the display, halting the display of updated statistics and delta counters. Displays information about a different interface. The command prompts you for the name of a specific interface. Copyright © 2015, Juniper Networks, Inc.
  • Page 265: Table 42: Output Control Keys For The Monitor Interface Traffic Command

    (QFX3500 Switch) on page 251 Output Fields Table 43 on page 246 describes the output fields for the monitor interface command. Output fields are listed in the approximate order in which they appear. Copyright © 2015, Juniper Networks, Inc.
  • Page 266: Table 43: Monitor Interface Output Fields

    —Number of bytes received on the interface. Input bytes Output bytes —Number of bytes transmitted on the interface. Input packets —Number of packets received on the interface. —Number of packets transmitted on the interface. Output packets Copyright © 2015, Juniper Networks, Inc.
  • Page 267 L2 channel errors: L2 mismatch timeouts: Carrier transitions: Output errors: Output drops: Aged packets: Active alarms : None Active defects: None SONET error counts/seconds: LOS count LOF count SEF count ES-S SES-S SONET statistics: BIP-B1 458871 Copyright © 2015, Juniper Networks, Inc.
  • Page 268 SA rejects Output MAC/Filter Statistics: Unicast packets Broadcast packets Multicast packets Packet pad count Packet error count OTN Link 0 OTN Alarms: OTU_BDI, OTU_TTIM, ODU_BDI OTN Defects: OTU_BDI, OTU_TTIM, ODU_BDI, ODU_TTIM OTN OC - Seconds Copyright © 2015, Juniper Networks, Inc.
  • Page 269 0 (0 bps) Input packets: 0 (0 pps) Output packets: 0 (0 pps) Error statistics: Input errors: Input drops: Input framing errors: Policed discards: L3 incompletes: L2 channel errors: L2 mismatch timeouts: Carrier transitions: Copyright © 2015, Juniper Networks, Inc.
  • Page 270 Output packets (pps) ge-0/0/0 Down ge-0/0/1 392187 392170 ge-0/0/2 Down ge-0/0/3 Down ge-0/0/4 Down ge-0/0/5 Down ge-0/0/6 Down ge-0/0/7 Down ge-0/0/8 Down ge-0/0/9 392184 392171 ge-0/0/10 Down ge-0/0/11 Down ge-0/0/12 Down ge-0/0/13 Down ge-0/0/14 Down Copyright © 2015, Juniper Networks, Inc.
  • Page 271 Down ge-0/0/12 Down ge-0/0/13 Down ge-0/0/14 Down ge-0/0/15 Down ge-0/0/16 Down ge-0/0/17 Down ge-0/0/18 Down ge-0/0/19 Down ge-0/0/20 Down ge-0/0/21 Down ge-0/0/22 392169 392184 ge-0/0/23 392182 392170 vcp-0 Down vcp-1 Down Down bme0 1568693 Copyright © 2015, Juniper Networks, Inc.
  • Page 272: Request Diagnostics Tdr

    The TDR test is supported on the following switches and interfaces: EX2200, EX3200, EX3300, and EX4200 switches—RJ-45 network interfaces. The TDR test is not supported on management interfaces and SFP interfaces.
  • Page 273: Table 44: Request Diagnostics Tdr Output Fields

    —The TDR test is not supported VCT not supported on interface-name on the interface. Sample Output request diagnostics tdr start interface ge-0/0/19 user@switch> request diagnostics tdr start interface ge-0/0/19 Interface TDR detail: Test status : Test successfully executed ge-0/0/19 Copyright © 2015, Juniper Networks, Inc.
  • Page 274: Show Diagnostics Tdr

    It can also detect polarity swaps, pair swaps, and excessive skew. The TDR test is supported on the following switches and interfaces: EX2200, EX3200, EX3300, and EX4200 switches—RJ-45 network interfaces. The TDR test is not supported on management interfaces and SFP interfaces.
  • Page 275: Table 45: Show Diagnostics Tdr Output Fields

    Distance fault Max distance fault When summary information for all interfaces is displayed, this value is the distance to the most distant fault if there is more than one twisted pair with a fault. Copyright © 2015, Juniper Networks, Inc.
  • Page 276 : ge-0/0/19 Test status : Passed Link status MDI pair : 1-2 Cable status : Normal Distance fault : 0 Meters Polartiy swap : Normal Skew time : 0 ns MDI pair : 3-6 Copyright © 2015, Juniper Networks, Inc.
  • Page 277 : N/A Downshift : N/A show diagnostics tdr (All Supported Interfaces) user@switch> show diagnostics tdr Interface Test status Link status Cable status Max distance fault ge-0/0/0 Not Started ge-0/0/1 Not Started ge-0/0/2 Started ge-0/0/3 Started Copyright © 2015, Juniper Networks, Inc.
  • Page 278 Passed ge-0/0/10 Passed ge-0/0/11 Passed ge-0/0/12 Passed ge-0/0/13 Passed ge-0/0/14 Passed ge-0/0/15 Passed ge-0/0/16 Passed ge-0/0/17 Passed ge-0/0/18 Passed ge-0/0/19 Passed ge-0/0/20 Passed Down Fault ge-0/0/21 Passed Down Fault ge-0/0/22 Passed ge-0/0/23 Passed Copyright © 2015, Juniper Networks, Inc.
  • Page 279: Show Forwarding-Options Enhanced-Hash-Key

    Indicates whether the Destination IPv4 Addr field is or is not used by the hashing Addr algorithm: Yes or No. Source IPv4 Addr Indicates whether the Source IPv4 Addr field is or is not used by the hashing algorithm: Yes or No. Copyright © 2015, Juniper Networks, Inc.
  • Page 280 Hash settings- --------------------- inet6 packet fields Next Hdr : Yes Destination L4 Port : Yes Source L4 Port : Yes Destination IPv6 Addr : Yes Source IPv6 Addr : Yes Vlan id : No Copyright © 2015, Juniper Networks, Inc.
  • Page 281 Slot 0 Current Hash Settings ---------------------- Hash-Mode : layer2-header layer2 Hash settings- ---------------------- layer2 packet fields Ether Type : Yes Destination MAC Address : Yes Source MAC Address : Yes VLAN ID : No Copyright © 2015, Juniper Networks, Inc.
  • Page 282: Show Interfaces Diagnostics Optics

    Output fields are listed in the approximate order in which they appear. Table 47: show interfaces diagnostics optics Output Fields Field Name Field Description Displays the name of the physical interface. Physical interface Copyright © 2015, Juniper Networks, Inc.
  • Page 283 Displays whether the laser output power low alarm is Laser output power low alarm (Not available for QSFP+ transceivers) Displays whether the laser output power high warning is Laser output power high warning (Not available for QSFP+ transceivers) Copyright © 2015, Juniper Networks, Inc.
  • Page 284 Displays whether the module voltage high warning is Module voltage high warning (Not available for XFP and QSFP+ transceivers) Displays whether the module voltage low warning is Module voltage low warning (Not available for XFP and QSFP+ transceivers) Copyright © 2015, Juniper Networks, Inc.
  • Page 285 Displays whether the checksum fault alarm is Checksum fault alarm (Not available for SFP, SFP+, XFP, and QSFP+ transceivers) Displays whether the Tx laser disabled alarm is Tx laser disabled alarm (Not available for SFP, SFP+, XFP, and QSFP+ transceivers) Copyright © 2015, Juniper Networks, Inc.
  • Page 286 Displays the vendor-specified threshold for the laser output power high alarm. (Not available for QSFP+ transceivers) Laser output power low alarm threshold Displays the vendor-specified threshold for the laser output power low alarm. (Not available for QSFP+ transceivers) Copyright © 2015, Juniper Networks, Inc.
  • Page 287 Laser rx power low alarm threshold low alarm. (Not available for QSFP+ transceivers) Displays the vendor-specified threshold for the laser rx power Laser rx power high warning threshold high warning. (Not available for QSFP+ transceivers) Copyright © 2015, Juniper Networks, Inc.
  • Page 288 Laser receiver power high warning (Not available for SFP, SFP+, and XFP transceivers) Displays whether the laser receiver power low warning is Laser receiver power low warning (Not available for SFP, SFP+, and XFP transceivers) Copyright © 2015, Juniper Networks, Inc.
  • Page 289 Laser rx power high warning Laser rx power low warning Laser bias current high alarm threshold 15.000 mA Laser bias current low alarm threshold 1.000 mA Laser bias current high warning threshold : 12.000 mA Copyright © 2015, Juniper Networks, Inc.
  • Page 290 Module temperature low alarm threshold -5 degrees C / 23 degrees F Module temperature high warning threshold : 70 degrees C / 158 degrees F Module temperature low warning threshold 0 degrees C / 32 degrees F Copyright © 2015, Juniper Networks, Inc.
  • Page 291 0.8912 mW / -0.50 dBm Laser rx power low alarm threshold 0.0912 mW / -10.40 dBm Laser rx power high warning threshold 0.7943 mW / -1.00 dBm Laser rx power low warning threshold 0.1023 mW / -9.90 dBm Copyright © 2015, Juniper Networks, Inc.
  • Page 292 Laser bias current low warning Laser receiver power high alarm Laser receiver power low alarm Laser receiver power high warning Laser receiver power low warning Tx loss of signal functionality alarm Rx loss of signal alarm Copyright © 2015, Juniper Networks, Inc.
  • Page 293 0.000 mA Lane 0 Laser bias current 131.684 mA Laser output power 1.002 mW / 0.01 dBm Laser temperature 54 degrees C / 128 degrees F Laser receiver power 0.497 mW / -3.03 dBm Copyright © 2015, Juniper Networks, Inc.
  • Page 294 50 degrees C / 122 degrees F Laser receiver power 0.540 mW / -2.67 dBm Laser bias current high alarm Laser bias current low alarm Laser bias current high warning Laser bias current low warning Laser output power high alarm Copyright © 2015, Juniper Networks, Inc.
  • Page 295 Laser receiver power low warning Tx loss of signal functionality alarm Tx CDR loss of lock alarm Rx loss of signal alarm Rx CDR loss of lock alarm APD supply fault alarm TEC fault alarm Wavelength unlocked alarm Copyright © 2015, Juniper Networks, Inc.
  • Page 296: Show Interfaces Ge

    285 Output Fields Table 48 on page 277 lists the output fields for the show interfaces ge- command. Output fields are listed in the approximate order in which they appear. Copyright © 2015, Juniper Networks, Inc.
  • Page 297: Table 48: Show Interfaces Ge- 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 Optional user-specified description. Description brief detail extensive Encapsulation being used on the physical interface.
  • Page 298 —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 © 2015, Juniper Networks, Inc.
  • Page 299 —There are no active defects or alarms. None —Interface has lost its link state, which usually means that the cable is Link unplugged, the far-end system has been turned off, or the PIC is malfunctioning. Copyright © 2015, Juniper Networks, Inc.
  • Page 300 —Number of times an event caused the PHY to indicate “Data Code violations reception error” or “invalid data symbol error.” statistics reported by the PIC's MAC address filter Filter Statistics Receive Transmit extensive subsystem. Copyright © 2015, Juniper Networks, Inc.
  • Page 301 ID of the switch. On switches with line cards or on Virtual Chassis composed of switches with line cards, the slot number refers to the line card slot number on the switch or Virtual Chassis. Logical Interface Copyright © 2015, Juniper Networks, Inc.
  • Page 302 Index detail extensive 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. All levels Flags Encapsulation on the logical interface.
  • Page 303 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 ge-0/0/0 user@switch> show interfaces ge-0/0/0 Physical interface: ge-0/0/0, Enabled, Physical link is Down...
  • Page 304 1 assured-forw 5 expedited-fo 7 network-cont Active alarms : None Active defects : None Logical interface ge-0/0/0.0 (Index 65) (SNMP ifIndex 235) (Generation 130) Flags: SNMP-Traps Encapsulation: ENET2 Bandwidth: 0 Traffic statistics: Input bytes Copyright © 2015, Juniper Networks, Inc.
  • Page 305 FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0 Egress queues: 8 supported, 4 in use Queue counters: Queued packets Transmitted packets Dropped packets 0 best-effort 1 assured-forw 5 expedited-fo Copyright © 2015, Juniper Networks, Inc.
  • Page 306 Output bytes 4107883 Input packets: Output packets: 24307 Transit statistics: Input bytes 0 bps Output bytes 0 bps Input packets: 0 pps Output packets: 0 pps IPv6 transit statistics: Input bytes Output bytes Copyright © 2015, Juniper Networks, Inc.
  • Page 307 Chapter 5: Operational Commands Input packets: Output packets: Protocol eth-switch, Generation: 159, Route table: 0 Flags: None Input Filters: f2, Output Filters: f1,,,, Copyright © 2015, Juniper Networks, Inc.
  • Page 308: Show Interfaces Irb

    Level of Output Physical Interface Physical interface Name of the physical interface. All levels Enabled State of the physical interface. Possible values are described in the “Enabled All levels Field” section under Common Output Fields Description. Copyright © 2015, Juniper Networks, Inc.
  • Page 309 Last flapped: year-month-day hours:minutes:seconds timezone . For example, (hours:minutes:seconds ago) Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago) Time when the statistics for the interface were last set to zero. Statistics last detail extensive cleared Copyright © 2015, Juniper Networks, Inc.
  • Page 310 ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism. —Number of packets whose size exceeded the MTU of the MTU errors interface. —Sum of transmit drops. Resource errors Logical Interface Copyright © 2015, Juniper Networks, Inc.
  • Page 311 SNMP interface index number of the logical interface. SNMP ifIndex detail extensive none Generation Unique number for use by Juniper Networks technical support only. detail extensive Flags Information about the logical interface. Possible values are described in the detail extensive “Logical Interface Flags”...
  • Page 312 Table 49: show interfaces irb Output Fields (continued) Field Name Field Description Level of Output Unique number for use by Juniper Networks technical support only. Generation detail extensive Routing table in which the logical interface address is located. For example,...
  • Page 313 Routing Instance: customer_0 Bridging Domain: bd0 Input packets : 0 Output packets: 0 Protocol inet, MTU: 1500 Addresses, Flags: Dest-route-down Is-Preferred Is-Primary Destination: 10.51.1/24, Local: 10.51.1.2, Broadcast: 10.51.1.255 Protocol multiservice, MTU: 1500 Flags: Is-Primary Copyright © 2015, Juniper Networks, Inc.
  • Page 314: Show Interfaces Me0

    Name of the physical interface. All levels Physical interface State of the interface: All levels Enabled Enabled Disabled Index number of the physical interface, which reflects its initialization sequence. none Interface index detail extensive Copyright © 2015, Juniper Networks, Inc.
  • Page 315 Field Description Level of Output 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 Optional user-specified description. Description brief detail extensive Information about the type of functional interface.
  • Page 316 ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism. MTU errors —Number of packets whose size exceeded the MTU of the interface. —Sum of transmit drops. Resource errors Copyright © 2015, Juniper Networks, Inc.
  • Page 317 Index detail extensive 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. All levels Flags Encapsulation on the logical interface.
  • Page 318 Physical info : Unspecified Hold-times : Up 0 ms, Down 0 ms Current address: 00:1f:12:35:3c:bf, Hardware address: 00:1f:12:35:3c:bf Alternate link address: Unspecified Last flapped : 2010-07-31 23:45:50 PDT (5d 00:37 ago) Statistics last cleared: Never Copyright © 2015, Juniper Networks, Inc.
  • Page 319 Current address: 00:1f:12:38:58:bf, Hardware address: 00:1f:12:38:58:bf Alternate link address: Unspecified Last flapped : 2010-08-15 06:27:33 UTC (03:06:22 ago) Statistics last cleared: Never Traffic statistics: Input bytes 82310392 Output bytes 1966952 Input packets: 110453 Output packets: 17747 IPv6 transit statistics: Copyright © 2015, Juniper Networks, Inc.
  • Page 320 Output bytes 1966952 Input packets: 110453 Output packets: 17747 Protocol inet, Generation: 1, Route table: 0 Flags: Is-Primary Input Filters: mgmt_filter, Addresses, Flags: Is-Default Is-Preferred Is-Primary Destination: 10.204.96/20, Local: 10.204.96.234, Broadcast: 10.204.111.255, Generation: 1 Copyright © 2015, Juniper Networks, Inc.
  • Page 321: Show Interfaces Queue

    Configuring CoS Traffic Classification for Ingress Queuing on Oversubscribed Ports on EX8200 Line Cards (CLI Procedure) List of Sample Output show interfaces queue ge-0/0/0 (EX2200 Switch) on page 303 show interfaces queue xe-6/0/39 (Line Card with Oversubscribed Ports in an EX8200 Switch) on page 304...
  • Page 322 Egress Queues Information Number of output queues supported and in use on the specified interface. Egress queues CoS queue number. Queue This counter is not supported on EX Series switches. Queued Copyright © 2015, Juniper Networks, Inc.
  • Page 323 The queue statistics reflect the traffic flowing on all the interfaces in the port group. Sample Output show interfaces queue ge-0/0/0 (EX2200 Switch) user@switch> show interfaces queue ge–0/0/0 Physical interface: ge-0/0/0, Enabled, Physical link is Down...
  • Page 324 Tail-dropped packets : Queue: 5, Forwarding classes: expedited-forwarding Queued: Transmitted: Packets Bytes Tail-dropped packets : Queue: 6, Forwarding classes: mcast-af Queued: Transmitted: Packets Bytes Tail-dropped packets : Queue: 7, Forwarding classes: network-control Queued: Transmitted: Copyright © 2015, Juniper Networks, Inc.
  • Page 325 RED-dropped bytes High Queue: 4, Forwarding classes: mcast-ef Queued: Transmitted: Packets Bytes Tail-dropped packets : RED-dropped packets High RED-dropped bytes High Queue: 5, Forwarding classes: expedited-forwarding Queued: Transmitted: Packets Bytes Tail-dropped packets : RED-dropped packets Copyright © 2015, Juniper Networks, Inc.
  • Page 326 Queue: 6, Forwarding classes: mcast-af Queued: Transmitted: Packets Bytes Tail-dropped packets : RED-dropped packets High RED-dropped bytes High Queue: 7, Forwarding classes: network-control Queued: Transmitted: Packets 97990 Bytes 14987506 Tail-dropped packets : RED-dropped packets High RED-dropped bytes High Copyright © 2015, Juniper Networks, Inc.
  • Page 327: Show Interfaces Xe

    Monitoring Interface Status and Traffic on page 233 Documentation Troubleshooting Network Interfaces on EX3200 Switches Troubleshooting Network Interfaces on EX4200 Switches Troubleshooting an Aggregated Ethernet Interface on page 329 Junos OS Ethernet Interfaces Configuration Guide Copyright © 2015, Juniper Networks, Inc.
  • Page 328: Table 52: Show Interfaces Xe- Output Fields

    Index number of the physical interface, which reflects its initialization sequence. Interface index detail extensive none SNMP index number for the physical interface. SNMP ifIndex detail extensive none Unique number for use by Juniper Networks technical support only. Generation detail extensive Copyright © 2015, Juniper Networks, Inc.
  • Page 329 Source filtering status: Source filtering Enabled Disabled brief detail extensive none Flow control Flow control status: Enabled Disabled brief detail extensive none Device flags Information about the physical device. brief detail extensive none Copyright © 2015, Juniper Networks, Inc.
  • Page 330 Output bytes per second. —Number of packets received on the interface and rate in Input packets packets per second. —Number of packets transmitted on the interface and rate in Output packets packets per second. Copyright © 2015, Juniper Networks, Inc.
  • Page 331 —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 © 2015, Juniper Networks, Inc.
  • Page 332 —Number of queued packets. This counter is not supported Queued packets on EX switches and always contains 0. —Number of transmitted packets. Transmitted packets —Number of packets dropped by the ASIC's RED mechanism. Dropped packets Copyright © 2015, Juniper Networks, Inc.
  • Page 333 ID of the switch. On switches with line cards or on Virtual Chassis composed of switches with line cards, the slot number refers to the line card slot number on the switch or Virtual Chassis. Copyright © 2015, Juniper Networks, Inc.
  • Page 334 The decrypted bytes counter is incremented for received traffic that was encrypted using MACSec. Fields for Logical Interfaces Copyright © 2015, Juniper Networks, Inc.
  • Page 335 Index detail extensive none SNMP interface index number for the logical interface. SNMP ifIndex detail extensive none Unique number for use by Juniper Networks technical support only. Generation detail extensive User-configured description of the interface. Description brief detail extensive none Information about the logical interface.
  • Page 336 Broadcast address of the logical interlace. Broadcast detail extensive none Unique number for use by Juniper Networks technical support only. Generation detail extensive Sample Output show interfaces xe-4/1/0 user@switch show interfaces xe-4/1/0 Physical interface: xe-4/1/0, Enabled, Physical link is Up Interface index: 387, SNMP ifIndex: 369 Copyright ©...
  • Page 337 Statistics last cleared: Never Traffic statistics: Input bytes 4945644 48576 bps Output bytes 0 bps Input packets: 3258 4 pps Output packets: 0 pps IPv6 transit statistics: Input bytes Output bytes Input packets: Output packets: Copyright © 2015, Juniper Networks, Inc.
  • Page 338 Statistics last cleared: Never Traffic statistics: Input bytes 49625962140160 4391057408 bps Output bytes 47686985710805 4258984960 bps Input packets: 387702829264 4288139 pps Output packets: 372554570944 4159166 pps IPv6 transit statistics: Input bytes Output bytes Input packets: Copyright © 2015, Juniper Networks, Inc.
  • Page 339 CoS information: Direction : Output CoS transmit queue Bandwidth Buffer Priority Limit usec 0 best-effort 7500000000 none 2 mcast-be 2000000000 none 7 network-cont 500000000 none Logical interface xe-6/0/39.0 (Index 1810) (SNMP ifIndex 2238) (Generation 1923) Copyright © 2015, Juniper Networks, Inc.
  • Page 340 Output bytes 9375416 Input packets: Output packets: 48901 Transit statistics: Input bytes 0 bps Output bytes 0 bps Input packets: 0 pps Output packets: 0 pps Protocol eth-switch, Generation: 1937, Route table: 0 Flags: Trunk-Mode Copyright © 2015, Juniper Networks, Inc.
  • Page 341: Show Lacp Interfaces

    (QFX Series) on page 324 Output Fields Table 53 on page 322 lists the output fields for the command. Output show lacp interfaces fields are listed in the approximate order in which they appear. Copyright © 2015, Juniper Networks, Inc.
  • Page 342: Table 53: Show Lacp Interfaces Output Fields

    Activity Passive LAC PDUs unless its partner’s control value is indicates the port’s preference to Active Active participate in the protocol regardless of the partner’s control value. Copyright © 2015, Juniper Networks, Inc.
  • Page 343 —The multiplexer state machine is in a holding process, awaiting an outcome. Waiting Sample Output show lacp interfaces (EX Series Switches) user@switch> show lacp interfaces ae5 Aggregated interface: ae5 LACP state: Role Dist Aggr Timeout Activity xe-2/0/7 Actor Fast Active xe-2/0/7 Partner Fast Passive Copyright © 2015, Juniper Networks, Inc.
  • Page 344 (QFX Series) user@switch> show lacp interfaces nodegroup1:ae0 extensive Aggregated interface: nodegroup1:ae0 LACP state: Role Dist Aggr Timeout Activity node1:xe-0/0/1FUP Actor Fast Active node1xe-0/0/1FUP Partner Fast Passive node2:xe-0/0/2 Actor Fast Active node2:xe-0/0/2 Partner Fast Passive Copyright © 2015, Juniper Networks, Inc.
  • Page 345 Chapter 5: Operational Commands LACP protocol: Receive State Transmit State Mux State node1:xe-0/0/1FUP Current Fast periodic Collecting distributing node2:xe-0/0/2 Current Fast periodic Collecting distributing node1:xe-0/0/1 (active) Current Fast periodic Collecting distributing node2:xe-0/0/2 (standby) Current Fast periodic WAITING Copyright © 2015, Juniper Networks, Inc.
  • Page 346: Test Interface Restart-Auto-Negotiation

    List of Sample Output test interface restart-auto-negotiation on page 326 Output Fields Use the command to see the state for auto-negotiation. show interfaces extensive Sample Output test interface restart-auto-negotiation user@host> test interface restart-auto-negotiation fe-1/0/0 Copyright © 2015, Juniper Networks, Inc.
  • Page 347: Troubleshooting

    PART 4 Troubleshooting Troubleshooting Procedures on page 329 Copyright © 2015, Juniper Networks, Inc.
  • Page 348 Network Interfaces for EX4300 Switches Copyright © 2015, Juniper Networks, Inc.
  • Page 349: Troubleshooting Procedures

    Verify that the LAG members belong to the same switch (or the same Virtual Chassis). Logical Interface Statistics Do Not Reflect All Traffic Problem Description: The traffic statistics for a logical interface do not include all of the traffic. Copyright © 2015, Juniper Networks, Inc.
  • Page 350: Ipv6 Interface Traffic Statistics Are Not Supported

    Click . The Port Troubleshooting wizard is displayed. Click Troubleshoot Port Next Select the ports to troubleshoot. Select the test cases to be executed on the selected port. Click Next Copyright © 2015, Juniper Networks, Inc.
  • Page 351: Troubleshooting Unicast Rpf

    If the best return path uses a different interface than the interface that received the packet, the switch discards the packet. Copyright © 2015, Juniper Networks, Inc.
  • Page 352: Diagnosing A Faulty Twisted-Pair Cable (Cli Procedure)

    Detects and reports pair swaps, pair polarity reversals, and excessive pair skew. The TDR test is supported on the following switches and interfaces: EX2200, EX3200, EX3300, and EX4200 switches—RJ-45 network interfaces. The TDR test is not supported on management interfaces and SFP interfaces.
  • Page 353 You can terminate a running TDR test before it completes by using the request command. The test terminates with no diagnostics tdr abort interface interface-name results, and the results from any previous test are cleared. Copyright © 2015, Juniper Networks, Inc.
  • Page 354 Not Started ge-0/0/21 Not Started ge-0/0/22 Passed ge-0/0/23 Not Started Related Troubleshooting Interface Configuration and Cable Faults on page 330 Documentation request diagnostics tdr on page 252 show diagnostics tdr on page 254 Copyright © 2015, Juniper Networks, Inc.

Table of Contents

Save PDF