Juniper EX2200, EX4500, EX6210, EX8208, EX8216 Hardware Manual

...

Junos®OS for EX Series Ethernet Switches

Network Interfaces for EX4300 Switches

Release

13.2X51

Published: 2015-02-24

Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.

Junos®OS for EX Series Ethernet Switches Network Interfaces for EX4300 Switches

The information in this document is current as of the date on the title page.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.

END USER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at

http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of

that EULA.

Table of Contents

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Using the Examples in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Merging a Full Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Merging a Snippet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Part 1 Overview

Chapter 1 Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

EX Series Switches Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Special Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Understanding Interface Naming Conventions on EX Series Switches . . . . . . . . . . 6

Physical Part of an Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Logical Part of an Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Wildcard Characters in Interface Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Understanding Aggregated Ethernet Interfaces and LACP . . . . . . . . . . . . . . . . . . . 8

Link Aggregation Group (LAG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Link Aggregation Control Protocol (LACP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop

ECMP Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Understanding the Hashing Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

IP (IPv4 and IPv6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

MAC-in-MAC Packet Hashing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Layer 2 Header Hashing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Understanding How Energy Efficient Ethernet Reduces Power Consumption on

Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Understanding Local Link Bias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Understanding Layer 3 Subinterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Understanding Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Unicast RPF for Switches Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Unicast RPF Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Unicast RPF Packet Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Bootstrap Protocol (BOOTP) and DHCP Requests . . . . . . . . . . . . . . . . . 20

Network Interfaces for EX4300 Switches

Understanding IP Directed Broadcast for EX Series Switches . . . . . . . . . . . . . . . . 23

Understanding Interface Ranges on EX Series Switches . . . . . . . . . . . . . . . . . . . . 24

802.1Q VLANs Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Part 2 Configuration

Chapter 2 Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Configuring Gigabit Ethernet Interfaces (CLI Procedure) . . . . . . . . . . . . . . . . . . . . 32

Configuring Gigabit Ethernet Interfaces (J-Web Procedure) . . . . . . . . . . . . . . . . . 35

Port Role Configuration with the J-Web Interface (with CLI References) . . . . . . . . 41

Adding a Logical Unit Description to the Configuration . . . . . . . . . . . . . . . . . . . . . 45

Disabling a Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Disabling a Logical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring the Interface Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configuring the Interface Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Configuring the Media MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Default Route Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

When to Enable Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

When Not to Enable Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Limitations of the Unicast RPF Implementation on EX3200, EX4200, and

EX4300 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

IP Directed Broadcast for EX Series Switches Overview . . . . . . . . . . . . . . . . . 23

IP Directed Broadcast Implementation for EX Series Switches . . . . . . . . . . . 23

When to Enable IP Directed Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

When Not to Enable IP Directed Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Configuring VLAN Options and Interface Mode . . . . . . . . . . . . . . . . . . . . . . . . 32

Configuring the Link Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Configuring the IP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Example: Disabling a Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Configuring Interface IPv4 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Operational Behavior of Interfaces when the Same IPv4 Address is

Assigned to Them . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Configuring Interface IPv6 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Media MTU Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

How to Configure the Media MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Encapsulation Overhead by Encapsulation Type . . . . . . . . . . . . . . . . . . . . . . 56

Media MTU Sizes by Interface Type for M5 and M7i Routers with CFEB, M10

and M10i Routers with CFEB, and M20 and M40 Routers . . . . . . . . . . . . 57

Media MTU Sizes by Interface Type for M40e Routers . . . . . . . . . . . . . . . . . . 57

Media MTU Sizes by Interface Type for M160 Routers . . . . . . . . . . . . . . . . . . 59

Media MTU Sizes by Interface Type for M7i Routers with CFEB-E, M10i

Routers with CFEB-E, and M320 and M120 Routers . . . . . . . . . . . . . . . . 59

Media MTU Sizes by Interface Type for MX Series Routers . . . . . . . . . . . . . . . 60

Media MTU Sizes by Interface Type for T320 Routers . . . . . . . . . . . . . . . . . . . 61

Media MTU Sizes by Interface Type for T640 Platforms . . . . . . . . . . . . . . . . . 61

Media MTU Sizes by Interface Type for J2300 Platforms . . . . . . . . . . . . . . . . 62

Media MTU Sizes by Interface Type for J4300 and J6300 Platforms . . . . . . . 62

Media MTU Sizes by Interface Type for J4350 and J6350 Platforms . . . . . . . 63

Table of Contents

Media MTU Sizes by Interface Type for EX Series Switches and ACX Series

Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Media MTU Sizes by Interface Type for PTX Series Packet Transport

Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Setting the Protocol MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Interface Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configuring Interface Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Expanding Interface Range Member and Member Range Statements . . . . . 69

Configuration Inheritance for Member Interfaces . . . . . . . . . . . . . . . . . . . . . . 70

Member Interfaces Inheriting Configuration from Configuration Groups . . . . . 71

Interfaces Inheriting Common Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Configuring Inheritance Range Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Configuration Expansion Where Interface Range Is Used . . . . . . . . . . . . . . . . 73

Configuring Accounting for the Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . 74

Applying an Accounting Profile to the Physical Interface . . . . . . . . . . . . . . . . 75

Example: Applying an Accounting Profile to the Physical Interface . . . . . 75

Configuring Accounting for the Logical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Applying an Accounting Profile to the Logical Interface . . . . . . . . . . . . . . . . . 76

Example: Applying an Accounting Profile to the Logical Interface . . . . . 76

Configuring Ethernet Loopback Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Configuring Gratuitous ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Configuring Static ARP Table Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Example: Configuring Static ARP Table Entries . . . . . . . . . . . . . . . . . . . . . . . . 79

Disabling the Transmission of Redirect Messages on an Interface . . . . . . . . . . . . 80

Configuring Restricted and Unrestricted Proxy ARP . . . . . . . . . . . . . . . . . . . . . . . 80

Enabling or Disabling SNMP Notifications on Logical Interfaces . . . . . . . . . . . . . . 81

Configuring Aggregated Ethernet Links (CLI Procedure) . . . . . . . . . . . . . . . . . . . . 82

Configuring Aggregated Ethernet Interfaces (J-Web Procedure) . . . . . . . . . . . . . 83

Configuring Aggregated Ethernet LACP (CLI Procedure) . . . . . . . . . . . . . . . . . . . . 86

Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI

Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring LACP Link Protection at the Global Level . . . . . . . . . . . . . . . . . . 88

Configuring LACP Link Protection at the Aggregated Interface Level . . . . . . . 88

Configuring Aggregated Ethernet Link Protection . . . . . . . . . . . . . . . . . . . . . . . . . 89

Configuring Link Protection for Aggregated Ethernet Interfaces . . . . . . . . . . 89

Configuring Primary and Backup Links for Link Aggregated Ethernet

Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

RevertingTrafficto a Primary Link WhenTraffic is Passing Through aBackup

Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Disabling Link Protection for Aggregated Ethernet Interfaces . . . . . . . . . . . . 90

Configuring Aggregated Ethernet Link Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Configuring Aggregated Ethernet Minimum Links . . . . . . . . . . . . . . . . . . . . . . . . . 92

Configuring Energy Efficient Ethernet on Interfaces (CLI Procedure) . . . . . . . . . . 93

Enabling EEE on an EEE-Capable Base-T Copper Ethernet Port . . . . . . . . . . 93

Disabling EEE on a Base-T Copper Ethernet Port . . . . . . . . . . . . . . . . . . . . . . 93

Configuring Local Link Bias (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Network Interfaces for EX4300 Switches

Configuring the Fields in the Algorithm Used To Hash LAG Bundle and ECMP

Configuring Tagged Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . 96

Configuring a Layer 3 Subinterface (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . 97

Configuring Unicast RPF (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Disabling Unicast RPF (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Configuring IP Directed Broadcast (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . 100

Tracing Operations of an Individual Router or Switch Interface . . . . . . . . . . . . . . 101

Tracing Operations of the Interface Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Chapter 3 Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

[edit chassis] Configuration Statement Hierarchy on EX Series Switches . . . . . 105

[edit forwarding-options] Configuration Statement Hierarchy on EX Series

[edit interfaces] Configuration Statement Hierarchy on EX Series Switches . . . 108 [edit interfaces ae] Configuration Statement Hierarchy on EX Series

[edit interfaces et] Configuration Statement Hierarchy on EX Series

[edit interfaces ge] Configuration Statement Hierarchy on EX Series

[edit interfaces interface-range] ConfigurationStatementHierarchyon EX Series

[edit interfaces irb] Configuration Statement Hierarchy on EX Series

Traffic (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Configuring the Hashing Algorithm to Use Fields in the Layer 2 Header for

Hashing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Configuring the Hashing Algorithm to Use Fields in the IP Payload for

Hashing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Configuring the Hashing Algorithm to Use Fields in the IPv6 Payload for

Hashing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Supported Statements in the [edit chassis] Hierarchy Level . . . . . . . . . . . . 105

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Supported Subhierarchies in the [edit forwarding-options] Hierarchy

Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Unsupported Subhierarchies in the [edit forwarding-options] Hierarchy

Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Supported Statements in the [edit interfaces ae] Hierarchy Level . . . . . . . . 109

Unsupported Statements in the [edit interfaces ae] Hierarchy Level . . . . . . 113

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Supported Statements in the [edit interfaces et] Hierarchy Level . . . . . . . . . 114

Unsupported Statements in the [edit interfaces et] Hierarchy Level . . . . . . . 118

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Supported Statements in the [edit interfaces ge] Hierarchy Level . . . . . . . . 120

Unsupported Statements in the [edit interfaces ge] Hierarchy Level . . . . . . 124

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Supported Statements in the [edit interfaces interface-range] Hierarchy

Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Unsupported Statements in the [edit interfaces interface-range] Hierarchy

Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Supported Statements in the [edit interfaces irb] Hierarchy Level . . . . . . . . 134

Unsupported Statements in the [edit interfaces irb] Hierarchy Level . . . . . . 137

Table of Contents

[edit interfaces lo] Configuration Statement Hierarchy on EX Series

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Supported Statements in the [edit interfaces lo] Hierarchy Level . . . . . . . . 138

Unsupported Statements in the [edit interfaces lo] Hierarchy Level . . . . . . 140

[edit interfaces me] Configuration Statement Hierarchy on EX Series

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Supported Statements in the [edit interfaces me] Hierarchy Level . . . . . . . . 141

Unsupported Statements in the [edit interfaces me] Hierarchy Level . . . . . 143

[edit interfaces vme] Configuration Statement Hierarchy on EX Series

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Supported Statements in the [edit interfaces vme] Hierarchy Level . . . . . . 144

Unsupported Statements in the [edit interfaces vme] Hierarchy Level . . . . 147

[edit interfaces xe] Configuration Statement Hierarchy on EX Series

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Supported Statements in the [edit interfaces xe] Hierarchy Level . . . . . . . . 147

Unsupported Statements in the [edit interfaces xe] Hierarchy Level . . . . . . 151

[edit protocols lacp] Configuration Statement Hierarchy on EX Series

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Supported Statements in the [edit protocols lacp] Hierarchy Level . . . . . . . 153

Unsupported Statements in the [edit protocols lacp] Hierarchy Level . . . . . 153

802.3ad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

accounting-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

aggregated-devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

aggregated-ether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

arp (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

bandwidth (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

description (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

device-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

disable (Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

enhanced-hash-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

ether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

ethernet (Aggregated Devices) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

eui-64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

flow-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

force-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

gratuitous-arp-reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

hash-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

hold-time (Physical Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

ieee-802-3az-eee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

inet (enhanced-hash-key) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

inet6 (enhanced-hash-key) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

interface (Multichassis Protection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

interface-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Network Interfaces for EX4300 Switches

interface-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

lacp (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

lacp (802.3ad) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

layer2 (enhanced-hash-key) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

link-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

link-protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

link-speed (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

local-bias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

loopback (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet) . . . . . . . 205

member (Interface Ranges) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

member-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

mtu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

native-vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

no-gratuitous-arp-request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

no-redirects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

periodic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

primary (Address on Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

proxy-arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

rpf-check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

speed (Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

traceoptions (Individual Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

traceoptions (Interface Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

transmit-interval (Liveness Detection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

vlan (802.1Q Tagging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

vlan-id (VLAN Tagging and Layer 3 Subinterfaces) . . . . . . . . . . . . . . . . . . . . . . . 228

vlan-tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Part 3 Administration

Chapter 4 Routine Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Monitoring Interface Status and Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Verifying the Status of a LAG Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Verifying That EEE Is Saving Energy on Configured Ports . . . . . . . . . . . . . . . . . . . 235

VerifyingThat LACP IsConfiguredCorrectlyand Bundle Members Are Exchanging

Verifying That Layer 3 Subinterfaces Are Working . . . . . . . . . . . . . . . . . . . . . . . . 238

Verifying Unicast RPF Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Verifying IP Directed Broadcast Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Chapter 5 Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

monitor interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

request diagnostics tdr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

show diagnostics tdr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

show forwarding-options enhanced-hash-key . . . . . . . . . . . . . . . . . . . . . . . . . . 259

LACP Protocol Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Verifying the LACP Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Verifying That LACP Packets Are Being Exchanged . . . . . . . . . . . . . . . . . . . . 237

Table of Contents

show interfaces diagnostics optics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

show interfaces ge- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

show interfaces irb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

show interfaces me0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

show interfaces queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

show interfaces xe- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

show lacp interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

test interface restart-auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Part 4 Troubleshooting

Chapter 6 Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Troubleshooting an Aggregated Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . 329

Show Interfaces Command Shows the LAG is Down . . . . . . . . . . . . . . . . . . 329

Logical Interface Statistics Do Not Reflect All Traffic . . . . . . . . . . . . . . . . . . 329

IPv6 Interface Traffic Statistics Are Not Supported . . . . . . . . . . . . . . . . . . . 330

SNMP Counters ifHCInBroadcastPkts and ifInBroadcastPkts Are Always

0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Troubleshooting Interface Configuration and Cable Faults . . . . . . . . . . . . . . . . . 330

Interface Configuration or Connectivity Is Not Working . . . . . . . . . . . . . . . . 330

Troubleshooting Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Legitimate Packets Are Discarded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Diagnosing a Faulty Twisted-Pair Cable (CLI Procedure) . . . . . . . . . . . . . . . . . . . 332

Network Interfaces for EX4300 Switches

List of Figures

Part 1 Overview

Chapter 1 Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Figure 1: Egress Traffic Flow with Local Link Bias . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Figure 2: Egress Traffic Flow without Local Link Bias . . . . . . . . . . . . . . . . . . . . . . . . 17

Figure 3: Symmetrically Routed Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 4: Asymmetrically Routed Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Network Interfaces for EX4300 Switches

List of Tables

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Part 1 Overview

Chapter 1 Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Table 3: Network Interface Types and Purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Table 4: Special Interface Types and Purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Table 5: Maximum Interfaces per LAG and Maximum LAGs per Switch . . . . . . . . . 9

Table 6: IPv4 and IPv6 Hashing Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table 7: MPLS Hashing Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 8: MAC-in-MAC Hashing Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Table 9: Layer 2 Header Hashing Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Part 2 Configuration

Chapter 2 Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Table 10: Factory Default Configuration Link Settings for EX Series Switches . . . . 33

Table 11: Port Edit Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Table 12: Recommended CoS Settings for Port Roles . . . . . . . . . . . . . . . . . . . . . . 40

Table 13: Port Role Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Table 14: Recommended CoS Settings for Port Roles . . . . . . . . . . . . . . . . . . . . . . 44

Table 15: Encapsulation Overhead by Encapsulation Type . . . . . . . . . . . . . . . . . . 56

Table 16: Media MTU Sizes by Interface Type for M5 and M7i Routers with CFEB,

Table 17: Media MTU Sizes by Interface Type for M40e Routers . . . . . . . . . . . . . . . 57

Table 18: Media MTU Sizes by Interface Type for M160 Routers . . . . . . . . . . . . . . 59

Table 19: Media MTU Sizes by Interface Type for M7i Routers with CFEB-E, M10i

Table 20: Media MTU Sizes by Interface Type for MX Series Routers . . . . . . . . . . 60

Table 21: Media MTU Sizes by Interface Type for T320 Routers . . . . . . . . . . . . . . . 61

Table 22: Media MTU Sizes by Interface Type for T640 Platforms . . . . . . . . . . . . . 61

Table 23: Media MTU Sizes by Interface Type for J2300 Platforms . . . . . . . . . . . . 62

Table 24: Media MTU Sizes by Interface Type for J4300 and J6300

Table 25: Media MTU Sizes by Interface Type for J4350 and J6350

Table 26: Media MTU Sizes by Interface Type for EX Series Switches and ACX

M10 and M10i Routers with CFEB, and M20 and M40 Routers . . . . . . . . . . . . 57

Routers with CFEB-E, and M320 and M120 Routers . . . . . . . . . . . . . . . . . . . . 59

Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Network Interfaces for EX4300 Switches

Table 27: Media MTU Sizes by Interface Type for PTX Series Packet Transport

Table 28: Aggregated Ethernet Interface Options . . . . . . . . . . . . . . . . . . . . . . . . . 84

Table 29: VLAN Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Table 30: IP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Chapter 3 Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Table 31: Unsupported [edit forwarding-options] Subhierarchies on EX Series

Table 32: Unsupported [edit interfaces ae] Configuration Statements for EX

Table 33: Unsupported [edit interfaces et] Configuration Statements for EX

Table 34: Unsupported [edit interfaces ge] Configuration Statements for EX

Table 35: Unsupported [edit interfaces interface-range] Configuration

Table 36: Unsupported [edit interfaces irb] Configuration Statements for EX

Table 37: Unsupported [edit interfaces lo] Configuration Statements for EX

Table 38: Unsupported [edit interfaces me] Configuration Statements for EX

Table 39: Unsupported [edit interfaces xe] Configuration Statements for EX

Table 40: Protocol Families and Supported Interface Types . . . . . . . . . . . . . . . . 178

Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Statements for EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Part 3 Administration

Chapter 5 Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Table 41: Output Control Keys for the monitor interface Command . . . . . . . . . . 244

Table 42: Output Control Keys for the monitor interface traffic Command . . . . 245

Table 43: monitor interface Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Table 44: request diagnostics tdr Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Table 45: show diagnostics tdr Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Table 46: show forwarding-options enhanced-hash-key Output Fields . . . . . . . 259

Table 47: show interfaces diagnostics optics Output Fields . . . . . . . . . . . . . . . . 262

Table 48: show interfaces ge- Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Table 49: show interfaces irb Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Table 50: show interfaces me0 Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Table 51: show interfaces queue Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Table 52: show interfaces xe- Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Table 53: show lacp interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

About the Documentation

•

Documentation and Release Notes on page xv

•

Supported Platforms on page xv

•

Using the Examples in This Manual on page xv

•

Documentation Conventions on page xvii

•

Documentation Feedback on page xix

•

Requesting Technical Support on page xix

Documentation and Release Notes

To obtain the most current version of all Juniper Networks®technical documentation, see the product documentation page on the Juniper Networks website at

http://www.juniper.net/techpubs/.

If the information in the latest release notes differs from the information in the documentation, follow the product Release Notes.

Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts. These books go beyond the technical documentation to explore the nuances of network architecture, deployment, and administration. The current list can be viewed at http://www.juniper.net/books.

Supported Platforms

For the features described in this document, the following platforms are supported:

•

EX Series

Using the Examples in This Manual

If you want to use the examples in this manual, you can use the load merge or the load

merge relative command. These commands cause the software to merge the incoming

configuration into the current candidate configuration. The example does not become active until you commit the candidate configuration.

If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example is a full example. In this case, use the load merge command.

Network Interfaces for EX4300 Switches

If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In this case, use the load merge relative command. These procedures are described in the following sections.

Merging a Full Example

To merge a full example, follow these steps:

1. From the HTML or PDF version of the manual, copy a configuration example into a

text file, save the file with a name, and copy the file to a directory on your routing platform.

For example, copythe following configuration to a fileand namethe fileex-script.conf. Copy the ex-script.conf file to the /var/tmp directory on your routing platform.

system {

scripts {

commit {

file ex-script.xsl;

}

} interfaces {

fxp0 {

disable; unit 0 {

family inet {

address 10.0.0.1/24;

}

Merging a Snippet

2. Merge the contents of the file into your routing platform configuration by issuing the

load merge configuration mode command:

[edit] user@host# load merge /var/tmp/ex-script.conf load complete

To merge a snippet, follow these steps:

1. From the HTML or PDF version of the manual, copy a configuration snippet into a text

file, save the file with a name, and copy the file to a directory on your routing platform.

For example, copy the following snippet to a file and name the file

ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory

on your routing platform.

commit {

file ex-script-snippet.xsl; }

2. Move to the hierarchy level that is relevant for this snippet by issuing the following

configuration mode command:

[edit] user@host# edit system scripts [edit system scripts]

3. Merge the contents of the file into your routing platform configuration by issuing the

load merge relative configuration mode command:

[edit system scripts] user@host# load merge relative /var/tmp/ex-script-snippet.conf load complete

For more information about the load command, see the CLI User Guide.

Documentation Conventions

Table 1 on page xvii defines notice icons used in this guide.

Table 1: Notice Icons

About the Documentation

DescriptionMeaningIcon

Table 2 on page xvii defines the text and syntax conventions used in this guide.

Table 2: Text and Syntax Conventions

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardware damage.Caution

Alerts you to the risk of personal injury or death.Warning

Alerts you to the risk of personal injury from a laser.Laser warning

Indicates helpful information.Tip

Alerts you to a recommended use or implementation.Best practice

ExamplesDescriptionConvention

Represents text that you type.Bold text like this

To enter configuration mode, type the configure command:

user@host> configure

Network Interfaces for EX4300 Switches

Table 2: Text and Syntax Conventions (continued)

ExamplesDescriptionConvention

Fixed-width text like this

Italic text like this

Text like this

| (pipe symbol)

Represents output that appears on the terminal screen.

•

Introduces or emphasizes important new terms.

•

Identifies guide names.

•

Identifies RFC and Internet draft titles.

Represents variables (options for which you substitute a value) in commands or configuration statements.

Represents names of configuration statements, commands, files, and directories;configurationhierarchylevels; or labels on routing platform components.

Indicates a choice between the mutually exclusivekeywords or variables on either side of the symbol. The set of choices is often enclosed in parentheses for clarity.

user@host> show chassis alarms

No alarms currently active

•

A policy term is a named structure that defines match conditions and actions.

•

Junos OS CLI User Guide

•

RFC 1997, BGP Communities Attribute

Configure the machine’s domain name:

[edit] root@# set system domain-name

domain-name

•

To configure a stub area, include the

stub statement at the [edit protocols ospf area area-id] hierarchy level.

•

The console port islabeled CONSOLE.

stub <default-metric metric>;Encloses optional keywords or variables.< > (angle brackets)

broadcast | multicast

(string1 | string2 | string3)

# (pound sign)

[ ] (square brackets)

Indention and braces ( { } )

; (semicolon)

GUI Conventions

Bold text like this

same lineas the configuration statement to which it applies.

Encloses a variable for which you can substitute one or more values.

Identifies a level in the configuration hierarchy.

Identifies a leaf statement at a configuration hierarchy level.

Representsgraphicaluser interface (GUI) items you click or select.

rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the

community name members [ community-ids ]

[edit] routing-options {

static {

route default {

nexthop address; retain;

}

•

In the Logical Interfaces box, select

All Interfaces.

•

To cancel the configuration, click

Cancel.

Table 2: Text and Syntax Conventions (continued)

About the Documentation

ExamplesDescriptionConvention

> (bold right angle bracket)

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can provide feedback by using either of the following methods:

•

Online feedback rating system—On any page at the Juniper Networks Technical Documentation site at http://www.juniper.net/techpubs/index.html, simply click the stars to rate the content, and use the pop-upform to provideus withinformation about your experience. Alternately, you can use the online feedback form at

https://www.juniper.net/cgi-bin/docbugreport/.

•

E-mail—Sendyour comments to techpubs-comments@juniper.net. Include the document or topic name, URL or page number, and software version (if applicable).

Requesting Technical Support

Technical product supportis available throughthe JuniperNetworks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or JNASC support contract, or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.

Separates levels in a hierarchy of menu selections.

In the configuration editor hierarchy, select Protocols>Ospf.

•

JTAC policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User Guide located at

http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.

•

Product warranties—For product warranty information, visit

http://www.juniper.net/support/warranty/.

•

JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features:

•

Find CSC offerings: http://www.juniper.net/customers/support/

•

Search for known bugs: http://www2.juniper.net/kb/

•

Find product documentation: http://www.juniper.net/techpubs/

•

Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/

Network Interfaces for EX4300 Switches

•

Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

•

Search technical bulletins for relevant hardware and software notifications:

http://kb.juniper.net/InfoCenter/

•

Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

•

Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/

To verifyservice entitlement by product serial number, use our SerialNumber Entitlement (SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.

•

Use the Case Management tool in the CSC at http://www.juniper.net/cm/.

•

Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, see

http://www.juniper.net/support/requesting-support.html.

PART 1

Overview

•

Interfaces Overview on page 3

Network Interfaces for EX4300 Switches

CHAPTER 1

Interfaces Overview

•

EX Series Switches Interfaces Overview on page 3

•

Understanding Interface Naming Conventions on EX Series Switches on page 6

•

Understanding Aggregated Ethernet Interfaces and LACP on page 8

•

Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic on page 11

•

Understanding How Energy Efficient Ethernet Reduces Power Consumption on Interfaces on page 16

•

Understanding Local Link Bias on page 16

•

Understanding Layer 3 Subinterfaces on page 18

•

Understanding Unicast RPF on page 19

•

Understanding IP Directed Broadcast for EX Series Switches on page 23

•

Understanding Interface Ranges on EX Series Switches on page 24

•

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 Junos OS Interfaces Fundamentals

Configuration Guide.

For information about interface-naming conventions on EX Series switches, see

“Understanding Interface Naming Conventions on EX Series Switches” on page 6.

This topic describes:

•

Network Interfaces on page 3

•

Special Interfaces on page 4

Network Interfaces

Network interfaces connect to the network and carry network traffic. Table 3 on page 4 lists the types of network interfaces supported on EX Series switches.

Network Interfaces for EX4300 Switches

Table 3: Network Interface Types and Purposes

PurposeType

Aggregated Ethernet interfaces

All EX Series switches allow you to group Ethernet interfaces at the physical layer to form a single link layer interface, also known as a link aggregation group (LAG) or bundle. These aggregated Ethernet interfaces help to balance traffic and increase the uplink bandwidth.

LAN access interfaces

Power over Ethernet (PoE) interfaces

Trunk interfaces

Use these EX Series switch interfaces to connect a personal computer, laptop, file server, or printer to the network. When you power on an EX Series switch and use the factory-default configuration, the software automatically configures interfaces in access mode for each of the network ports. The default configuration also enables autonegotiation for both speed and link mode.

EX Series switches provide PoE network ports with various switch models. These ports can be used to connect voice over IP (VoIP) telephones, wireless access points, video cameras, and point-of-sale devices to safely receive power from the same access ports that are used to connect personal computers to thenetwork.PoE interfaces areenabled by default in thefactory configuration.

EX Series access switches can be connected to a distribution switch or customer-edge (CE) switches or routers. To use a port for this type of connection, you must explicitly configure the network interface for trunk mode. The interfaces from the distribution switch or CE switch to the access switches must also be configured for trunk mode.

Special Interfaces

Table 4 on page 4 lists the types of special interfaces supported on EX Series switches.

Table 4: Special Interface Types and Purposes

PurposeType

Console port

Each EX Series switch has a serial port, labeled CON or CONSOLE, for connecting tty-type terminals to the switch using standard PC-type tty cables. The console port does not have a physical address or IP address associated with it. However, it is an interface in the sense that it provides access to the switch. On an EX3300 Virtual Chassis, an EX4200 Virtual Chassis, or an EX4500Virtual Chassis, you canaccessthe master and configure all members of the Virtual Chassis through any member's console port. For more information about the console port in a Virtual Chassis, see Understanding Global Management of a Virtual Chassis.

Loopback

Management interface

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.

The Juniper Networks Junos operatingsystem (Junos OS) for EX Series switches automatically createsthe switch's management Ethernet interface, me0. The management Ethernet interface provides an out-of-band method for connecting to the switch. To use me0 as a management port, you must configure its logical port, me0.0, with a valid IP address. You can connect to the management interface over the network using utilities such as SSH or Telnet. SNMP can use the management interface to gather statistics from the switch. (The management interface

me0 is analogous to the fxp0 interfaces on routers running Junos OS.)

Table 4: Special Interface Types and Purposes (continued)

PurposeType

Integrated Routing and Bridging (IRB) Interface or Routed VLAN Interface (RVI)

EX Series switches use an integrated routing and bridging (IRB) interface or Routed VLAN Interface (RVI) to route traffic from one broadcast domain to another and to perform other Layer 3 functionssuch astrafficengineering. These functions aretypicallyperformed by a router interface in a traditional network.

The IRB interface or RVI functions as a logical router, eliminating the need for having both a switch and a router. These interfaces must be configured as part of a broadcast domain or virtual private LAN service (VPLS) routing instance for Layer 3 traffic to be routed from.

Chapter 1: Interfaces Overview

Virtual Chassis port (VCP) interfaces

Virtual Chassis ports (VCPs) are used to interconnect switches in a Virtual Chassis:

•

EX3300 switches—Port 2 and port 3 of the SFP+ uplink portsare preconfigured as VCPs and can be used to interconnect up to six EX3300 switches in an EX3300 Virtual Chassis. See Setting an Uplink Port on an EX Series Switch as a Virtual Chassis Port (CLI Procedure).

•

EX4200 and EX4500 switches—Each EX4200 switch or each EX4500 switch with a Virtual Chassis module installed has two dedicated VCPs onits rear panel. These ports can be used to interconnect up to ten EX4200 switches in an EX4200 Virtual Chassis, up to ten EX4500 switches in an EX4500 Virtual Chassis, and up to ten switches in a mixed EX4200 and EX4500 Virtual Chassis. When you power on switches that are interconnected in thismanner, the software automatically configures the VCP interfaces for the dedicated ports that have been interconnected. These VCP interfaces are not configurable or modifiable. See

Understanding the High-Speed Interconnection of the Dedicated Virtual Chassis Ports Connecting EX4200, EX4500, and EX4550 Member Switches.

You can also interconnect EX4200 and EX4500 switches by using uplink module ports. Using uplink ports allows you to connect switches over longer distances than you can by using the dedicated VCPs. To use the uplink ports as VCPs, you must explicitly configure the uplink module ports on the members you want to connect as VCPs. See Setting an Uplink

Port on an EX Series Switch as a Virtual Chassis Port (CLI Procedure) or Setting an Uplink Port as a Virtual Chassis Port on an EX4500 or EX4550 Switch (CLI Procedure).

•

EX4300 switches—All QSFP+ ports are configured as VCPs, by default. See Understanding EX4300 Virtual Chassis

You can also interconnect EX4300 switches into a Virtual Chassis by using SFP+ uplink module ports asVCPs.Using uplinkports as VCPs allowsyou to connect switches over longer distances than you can by using the QSFP+ ports as VCPs. To use the uplink ports as VCPs, you must explicitly configure the uplink module ports on the members you want to connect as VCPs. See Setting an Uplink Port on an EX Series Switch as a Virtual Chassis Port (CLI Procedure).

•

EX8200 switches—EX8200 switches can be connected to an XRE200 External Routing Engine to create an EX8200 Virtual Chassis. The XRE200 External Routing Engine has dedicatedVCPsthat connect to ports onthe internalRouting Engines ofthe EX8200switches and can connect to another XRE200 External Routing Engine for redundancy. These ports require no configuration.

You can also connect twomembers of an EX8200 Virtual Chassis so that they can exchange Virtual Chassis Control Protocol (VCCP) traffic. To do so, you explicitly configure network ports onthe EX8200 switches as VCPs. SeeUnderstanding Virtual Chassis Ports in an EX8200 Virtual Chassis.

Virtual management Ethernet (VME) interface

EX3300, EX4200, EX4300, andEX4500 switches have aVME interface.This is a logical interface that is used for Virtual Chassis configurations and allows you to manage all the members of the Virtual Chassis through the master. For more information about the VME interface, see 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 (me0) interface on the XRE200 External Routing Engine.

Network Interfaces for EX4300 Switches

Documentation

EX2200 Switches Hardware Overview•

• EX3200 Switches Hardware Overview

• EX3300 Switches Hardware Overview

• EX4200 Switches Hardware Overview

• EX4300 Switches Hardware Overview

• EX4500 Switches Hardware Overview

• EX6210 Switch Hardware Overview

• EX8208 Switch Hardware Overview

• EX8216 Switch Hardware Overview

• XRE200 External Routing Engine Hardware Overview

• Understanding PoE on EX Series Switches

• Understanding Aggregated Ethernet Interfaces and LACP on page 8

• Understanding Layer 3 Subinterfaces on page 18

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. For additional information, see the Junos OS Network Interfaces Configuration Guide.

This topic describes:

•

Physical Part of an Interface Name on page 6

•

Logical Part of an Interface Name on page 8

•

Wildcard Characters in Interface Names on page 8

Physical Part of an Interface Name

Network interfaces in Junos OS are specified as follows:

type-fpc / pic / port

EX Series switches apply this convention as follows:

•

type—EX Series interfaces use the following media types:

•

ge—Gigabit Ethernet interface

•

xe—10 Gigabit Ethernet interface

Chapter 1: Interfaces Overview

•

et—40 Gigabit Ethernet interface

•

fpc—Flexible PIC Concentrator. EX Series interfaces use the following convention for the FPC number in interface names:

•

On anEX2200 switch, an EX3200switch, a standaloneEX3300 switch, a standalone EX4200 switch, a standalone EX4300 switch, a standalone EX4500, and a standalone EX4550 switch, FPC refers to the switch itself. The FPC number is 0 by default on these switches.

•

On anEX3300 Virtual Chassis, an EX4200Virtual Chassis, an EX4300Virtual Chassis, an EX4500 Virtual Chassis, an EX4550 Virtual Chassis, or a mixed Virtual Chassis, the FPC number indicates the member ID of the switch in the Virtual Chassis.

•

On an EX6200 switch and a standalone EX8200 switch, the FPC number indicates the slot number of the line card that contains the physical interface. On an EX6200 switch, the FPC number also indicates the slot number of the Switch Fabric and Routing Engine (SRE) module that contains the uplink port.

•

On an EX8200Virtual Chassis, the FPC number indicates the slot number of the line card on the Virtual Chassis. The line card slots on Virtual Chassis member 0 are numbered 0 through 15; on member 1, they are numbered 16 through 31, and so on.

•

pic—EX Series interfaces use the following convention for the PIC (Physical Interface Card) number in interface names:

•

On EX2200, EX3200, EX3300, EX4200, EX4500 switch, and EX4550 switches, the PIC number is 0 for all built-in interfaces (interfaces that are not uplink ports).

•

On EX2200, EX3200, EX3300, and EX4200 switches, the PIC number is 1 for uplink ports.

•

On EX4300 switches, the PIC number is 0 for built-in network ports, 1 for built-in QSFP+ ports (located onthe rearpanel ofthe switch),and 2for uplinkmodule ports.

•

On EX4500 switches, the PIC number is 1 for ports on the left-hand uplink module and 2 for ports on the right-hand uplink module.

•

On EX4550switches, the PIC number is 1for ports in theexpansion module or Virtual Chassis module installed in the module slot on the front panel of the switch and 2 for those in the expansion module or Virtual Chassis module installed in the module slot on the rear panel of the switch.

•

On EX6200 and EX8200 switches, the PIC number is always 0.

•

port—EX Series interfaces use the following convention for port numbers:

•

On EX2200, EX3200, EX3300, EX4200, EX4300, EX4500, and EX4550 switches, built-in network portsare numbered from left to right. On modelsthat have two rows of ports, the ports on the top row start with 0 followed by the remaining even-numbered ports, and the ports on the bottom row start with 1 followed by the remaining odd-numbered ports.

•

Uplink ports in EX2200, EX3200, EX3300, EX4200, EX4300, EX4500, and EX4550 switches are labeled from left to right, starting with 0.

Network Interfaces for EX4300 Switches

•

On EX6200and EX8200switches, the networkports are numbered from leftto right on each line card. On line cards that have two rows of ports, the ports on the top row start with 0 followed by the remaining even-numbered ports, and the ports on the bottom row start with 1 followed by the remaining odd-numbered ports.

•

Uplink ports on an SRE module in an EX6200 switch are labeled from left to right, starting with 0.

Logical Part of an Interface Name

The logical unit part of the interface name corresponds to the logical unit number, which can be a number from 0 through 16384. In the virtual part of the name, a period (.) separates the port and logical unit numbers: type-fpc/pic/port.logical-unit-number. For example, if you issue the showethernet-switching interfaces command on a system with a default VLAN, the resulting display shows the logical interfaces associated with the VLAN:

Interface State VLAN members Blocking ge-0/0/0.0 down remote-analyzer unblocked ge-0/0/1.0 down default unblocked ge-0/0/10.0 down default unblocked

Wildcard Characters in Interface Names

In the show interfaces and clear interfaces commands, you can use wildcard characters in the interface-name option to specify groups of interface names without having to type each name individually. You must enclose all wildcard characters except the asterisk (*) in quotation marks (" ").

Documentation

EX Series Switches Interfaces Overview on page 3•

• Configuring Gigabit Ethernet Interfaces (CLI Procedure)

• Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 32

Understanding Aggregated Ethernet Interfaces and LACP

IEEE 802.3ad link aggregation enables you to group Ethernet interfaces to form a single link layer interface, also known as a link aggregation group (LAG) or bundle.

Aggregating multiple links between physical interfaces creates a single logical point-to-point trunk link or a LAG. The LAG balances traffic across the member links within an aggregated Ethernet bundle and effectively increases the uplink bandwidth. Another advantage of link aggregation is increased availability, because the LAG is composed of multiple member links. 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.

This topic describes:

•

Link Aggregation Group (LAG) on page 9

•

Link Aggregation Control Protocol (LACP) on page 10

Link Aggregation Group (LAG)

You configure a LAG by specifying the link number as a physical device and then associating a set of interfaces (ports) with the link. Allthe 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. The ID and priority are not configurable.

The number of interfaces that can be grouped into a LAG and the total number of LAGs supported on a switch varies according to switch model. Table 5 on page 9 lists the EX Series switches and the maximum number of interfaces per LAG and the maximum number of LAGs they support. MX Series devices can support up to 64 LAGs.

Table 5: Maximum Interfaces per LAG and Maximum LAGs per Switch

Chapter 1: Interfaces Overview

Chassis

Chassis, EX4550, andEX4550 Virtual Chassis

Maximum Interfaces per LAGSwitch

Maximum LAGs

328EX2200

328EX3200

1118EX3300 and EX3300 Virtual

1118EX4200 and EX4200 Virtual

11216EX4300 and EX4300 Virtual

1118EX4500, EX4500 Virtual

1118EX6200

25512EX8200

23912EX8200 Virtual Chassis

When configuring LAGs, consider the following guidelines:

•

You must configure the LAG on both sides of the link.

•

You must set the interfaces on either side of the link to the same speed.

•

You can configure and apply firewall filters on a LAG.

Network Interfaces for EX4300 Switches

•

You can optionally configure LACP for link negotiation.

•

You can optionally configure LACP for link protection.

You can combine physical Ethernet ports belonging to different member switches of a Virtual Chassis configuration to form a LAG. See Understanding EX Series Virtual Chassis Port Link Aggregation and Understanding Link Aggregation in an EX8200 Virtual Chassis.

A LAG hashing algorithm determineshow traffic entering a LAGis placed onto the bundle’s member links. The LAG hashing algorithm tries to manage bandwidth by evenly load-balancing all incoming traffic across the member links in the bundle. You can configure the fields used by the LAG hashing algorithm on some EX series switches. See

“Configuring the Fields in the Algorithm Used To Hash LAG Bundle and ECMP Traffic (CLI Procedure)” on page 94.

NOTE: The interfaces that are included within a LAG are sometimes referred

to as member interfaces. Do not confuse this term with member switches, which refers to switches that are interconnected as a Virtual Chassis. It is possible to create a LAG that is composed of member interfaces that are located in different member switches of a Virtual Chassis.

A LAG creates a single logical point-to-point connection. A typical deployment for a LAG would be to aggregate trunk links between an access switch and a distribution switch or customer edge (CE) router.

Link Aggregation Control Protocol (LACP)

When LACP is configured, it detects misconfigurations on the local end or the remote end of the link. Thus, LACP can help prevent communication failure:

•

When LACP is not enabled, a local LAG might attempt to transmit packets to a remote single interface, which causes the communication to fail.

•

When LACP is enabled, a local LAG cannot transmit packets unless a LAG with LACP is also configured on the remote end of the link.

By default, Ethernet links do not exchange LACP protocol data units (PDUs), which contain information aboutthe state of thelink. You canconfigure Ethernet linksto actively transmit LACP PDUs, or you can configure the links to passively transmit them, sending out LACP PDUs only when the Ethernet link receives them from the remote end. The transmitting link is known as the actor and the receiving link is known as the partner.

In a scenario where a dual-homed server is deployed with a switch, the network interface cards form a LAG with the switch. During a server upgrade, the server might not be able to exchange LACP PDUs. In such a situation, you can configure an interface to be in the

up state even if no PDUs are exchanged. Use the force-up statement to configure an

interfacewhen the peer has limited LACP capability. The interface selects the associated 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.

+ 324 hidden pages

Juniper EX2200, EX4500, EX6210, EX8208, EX8216 Hardware Manual

Specifications and Main Features

Frequently Asked Questions

User Manual