Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Understanding Interfaces

Junos OS supports different types of interfaces on which the devices function. The following topics provide information of types of interfaces used, the naming conventions and the usage of management interfaces by Juniper Networks.

Interfaces Overview for Switches

Juniper Networks devices 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 Network Interfaces Library for Routing Devices.

Network Interfaces for EX Series

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

Table 1: Network Interfaces Types and Purposes for EX Series
Type Purpose

Aggregated Ethernet interfaces

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

See Understanding Aggregated Ethernet Interfaces and LACP for Switches.

LAN access interfaces

Use these EX Series switch interfaces to connect the following to the network:

  • PC
  • Laptop
  • File server
  • Printer

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.

Power over Ethernet (PoE) interfaces

EX Series switches provide PoE network ports with various switch models. Use these ports to connect 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 the network. PoE interfaces are enabled by default in the factory configuration.

See Understanding PoE on EX Series Switches.

Trunk interfaces

You can connect EX Series access switches 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. You must also configure the interfaces from the distribution switch or CE switch to the access switches for trunk mode.

Special Interfaces for EX Series

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

Table 2: Special Interfaces Types and Purposes for EX Series
Type Purpose

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 since it provides access to the switch. On an EX3300 Virtual Chassis, an EX4200 Virtual Chassis, or an EX4500 Virtual Chassis, you can access the primary device 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

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, 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.)

See Understanding Management Interfaces.

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 functions such as traffic engineering. These functions are typically performed 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. Configure these interfaces as part of a broadcast domain or Virtual Private LAN Service (VPLS) routing instance for L3 traffic to be routed from.

See Understanding Integrated Routing and Bridging.

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 ports are 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 or QFX Series Switch as a Virtual Chassis Port.

  • EX4100, EX4100-24MP, EX4100-48MP, and EX4100-F switches—Each EX4100, EX4100-24MP, EX4100-48MP, or EX4100-F switch has dedicated VCP ports. You cannot use any other ports on EX4100 switches as VCPs. See EX4100/EX4100-F Switches in a Virtual Chassis.

  • EX4200 and EX4500 switches—Each EX4200 switch or each EX4500 switch with a Virtual Chassis module installed has two dedicated VCPs on its 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 this manner, 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 or QFX Series Switch as a Virtual Chassis Port .

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

    You can also interconnect EX4300 switches into a Virtual Chassis by using SFP+ uplink module ports as VCPs. Using uplink ports as VCPs allows you 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 or QFX Series Switch as a Virtual Chassis Port.

  • 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 dedicated VCPs that connect to ports on the internal Routing Engines of the EX8200 switches and can connect to another XRE200 External Routing Engine for redundancy. These ports require no configuration. .

    You can also connect two members of an EX8200 Virtual Chassis so that they can exchange Virtual Chassis Control Protocol (VCCP) traffic. To do so, you explicitly configure network ports on the EX8200 switches as VCPs.

Virtual management Ethernet (VME) interface

EX3300, EX4200, EX4300, and EX4500 switches have a VME 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 primary device. 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 EX4600, NFX Series, QFX Series, QFabric System

Network interfaces connect to the network and carry network traffic. Table 3 lists the types of network interfaces supported.

Table 3: Network Interfaces Types and Purposes for EX4600, NFX Series, QFX Series, QFabric System
Type Purpose

Aggregated Ethernet interfaces

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.

Channelized Interfaces

Depending on the device and software package, 40-Gbps QSFP+ ports can be configured to operate as the following types of interfaces:

  • 10-Gigabit Ethernet interfaces (xe)

  • 40-Gigabit Ethernet interfaces (et and xle)

  • 40-Gigabit data plane uplink interfaces (fte)

When an et port is channelized to four xe ports, a colon is used to signify the four separate channels. For example, on a QFX3500 standalone switch with port 2 on PIC 1 configured as four 10-Gigabit Ethernet ports, the interface names are xe-0/1/2:0, xe-0/1/2:1, xe-0/1/2:2, and xe-0/1/2:3

Note:

You cannot configure channelized interfaces to operate as Virtual Chassis ports.

Ethernet Interfaces

Configure Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet interfaces to connect to other servers, storage, and switches. You can configure 40-Gigabit data plane uplink ports to connect a Node device to an Interconnect devices as well as for Virtual Chassis ports (VCPs).

Fibre Channel interfaces

Use Fibre Channel interfaces to connect the switch to a Fibre Channel over Ethernet (FCoE) forwarder or a Fibre Channel switch in a storage area network (SAN). You can configure Fibre Channel interfaces only on ports 0 through 5 and 42 through 47 on QFX3500 devices. Fibre Channel interfaces do not forward Ethernet traffic.

See Overview of Fibre Channel.

LAN access interfaces

Use these interfaces to connect to other servers, storage, and switches. When you power on a QFX Series product and use the factory-default configuration, the software automatically configures interfaces in access mode for each of the network ports.

Multichassis aggregated Ethernet (MC-AE) interfaces

Group a LAG on one standalone switch with a LAG on another standalone switch to create a MC-AE. The MC-AE provides load balancing and redundancy across the two standalone switches.

Tagged-access mode interfaces

Use tagged-access interfaces to connect a switch to an access layer device. Tagged-access interfaces can accept VLAN-tagged packets from multiple VLANs.

Trunk interfaces

Use trunk interfaces to connect to other switches or routers. To use a port for this type of connection, you must explicitly configure the port interface for trunk mode. The interfaces from the switches or routers must also be configured for trunk mode. In this mode, the interface can be in multiple VLANs and accept tagged packets from multiple devices. Trunk interfaces typically connect to other switches and to routers on the LAN.

Virtual Chassis ports (VCPs)

You can use Virtual Chassis ports to send and receive Virtual Chassis Control Protocol (VCCP) traffic, and to create, monitor, and maintain the Virtual Chassis. On QFX3500, QFX3600, QFX5100, QFX5110, QFX5200, and EX4600 standalone switches, you can configure 40-Gigabit Ethernet QSFP+ uplink ports (non-channelized) or fixed SFP+ 10-Gigabit Ethernet ports as VCPs by issuing the request virtual-chassis-vc-port-set CLI command. QFX5110 switches also support configuring 100-Gigabit QSFP28 ports as VCPs.

Special Interfaces for EX4600, NFX Series, QFX Series, QFabric System

Table 4 lists the types of special interfaces supported.

Table 4: Special Interfaces Types and Purposes supported on EX4600, NFX Series, QFX Series, QFabric System
Type Purpose

Console port

Each device has a serial console port, labeled CON or CONSOLE, for connecting tty-type terminals to the switch. 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.

Loopback interface

A 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 management Ethernet interface provides an out-of-band method for connecting to a standalone switch and QFabric system.

Note:

On OCX Series switches, the em0 management interface always has the status up in show command outputs, even if the physical port is empty. The me0 interface is a virtual interface between Junos and the host operating system, therefore its status is independent from the status of the physical port.

Routed VLAN interfaces (RVI and IRB interfaces)

Layer 3 routed VLAN interfaces (called RVI in the original CLI, and called IRB in Enhanced Layer 2 Software) route traffic from one broadcast domain to another and perform other Layer 3 functions such as traffic engineering. These functions are typically performed by a router interface in a traditional network.

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

Network Interfaces for OCX Series

Network interfaces connect to the network and carry network traffic. Table 5 lists the types of network interfaces supported.

Table 5: Network Interfaces Types and Purposes for OCX Series
Type Purpose

Aggregated Ethernet interfaces

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.

Ethernet Interfaces

Configure Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet interfaces to connect to other servers, storage, and switches.

Special Interfaces for OCX Series

Table 6 lists the types of special interfaces supported.

Table 6: Special Interfaces Types and Purposes for OCX Series
Type Purpose

Console port

Each device has a serial console port, labeled CON or CONSOLE, for connecting tty-type terminals to the switch. 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.

Loopback interface

A 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 management Ethernet interface provides an out-of-band method for connecting to a standalone switch and QFabric system.

Note:

On OCX Series switches, the em0 management interface always has the status up in show command outputs, even if the physical port is empty. The me0 interface is a virtual interface between Junos and the host operating system, therefore its status is independent from the status of the physical port.

See Also

Understanding Interface Naming Conventions

The EX Series, QFX Series, NFX Series, OCX1100, QFabric System, and EX4600 devices use a naming convention for defining the interfaces that are similar to that of other platforms running under Juniper Networks Junos OS. This topic provides brief information about the naming conventions used for interfaces on the QFX Series and on EX4600 switches.

For detailed information on interface naming like physical part, logical part, and channel part of the interfaces, see Interface Naming Overview.

This topic describes:

Physical Part of an Interface Name for EX Series

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

    • mge—2.5/5/10 Gigabit Ethernet interface

    • xe—10 Gigabit Ethernet interface

    • et—25/40/100 Gigabit Ethernet interface

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

    • On an EX2200 switch, an EX2300, an EX3200 switch, a standalone EX3300 switch, a standalone EX3400 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 an EX3300 Virtual Chassis, an EX3400 Virtual Chassis, an EX4200 Virtual Chassis, an EX4300 Virtual 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 EX4100 and EX4100-F switches, the FPC number ranges from 0 to 9. On a standalone EX4100 or EX4100-F switch, FPC refers to the switch. The FPC number is 0 by default on the standalone switches.

    • On EX4100 and EX4100-F 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 EX8200 Virtual 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.

    • On EX9251 switch, the FPC number is always 0.

    • The EX9253 switch does not have actual FPCs—the line cards are the FPC equivalents on the switch. In FPC (n), n is a value in the range of 0-1. The value corresponds to the line card slot number in which the line card is installed.

    • On an EX29204 switch, switch does not have actual FPCs—the line cards are the FPC equivalents on the switch. The value ranges from 0-2, and it corresponds to the line card slot number in which the line card is installed.

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

    • On EX2200, EX2300, 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, EX2300, EX3200, EX3300, and EX4200 switches, the PIC number is 1 for uplink ports.

    • On EX3400 switches, the PIC number is 0 for built-in network ports, 1 for built-in QSFP+ ports (located on the rear panel of the switch), and 2 for uplink module ports.

    • On EX4100 and EX4100-F switches, the PIC number ranges from 0 to 2. The PIC number is 0 for built-in network ports, 1 for SFP28/SFP+ dedicated Virtual Chassis ports, and 2 for SFP/SFP+ uplink ports.

    • On EX4300 switches, the PIC number is 0 for built-in network ports, 1 for built-in QSFP+ ports (located on the rear panel of the switch), and 2 for uplink module 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 EX4550 switches, the PIC number is 1 for ports in the expansion 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.

    • On EX9251 and EX9253 switches, the PIC number is 0 for built-in network ports, 1 for built-in QSFP+ ports (located on the rear panel of the switch).

    • On EX9204 switches, the PIC number ranges from 0-3.

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

    • On EX2200, EX2300, EX3200, EX3300, EX3400, EX4200, EX4300, EX4500, and EX4550 switches, built-in network ports are numbered from left to right. On models 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 in EX2200, EX3200, EX3300, EX3400, EX4200, EX4300, EX4500, and EX4550 switches are labeled from left to right, starting with 0.

    • On EX4100 and EX4100-F switches, the uplink ports are labeled from 0 to 3. The Virtual Chassis ports are also labeled from 0 to 3. The downlink ports are labeled from 0 to 47 (for EX4100-48P, EX4100-48T, EX4100-F-48P, and EX4100-F-48T switches) and from 0 to 23 (for EX4100-24P, EX4100-24T, EX4100-F-24P and EX4100-F-24T switches).

    • On EX6200 and EX8200 switches, the network ports are numbered from left to 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.

    • EX9251 Switch has eight 10-Gigabit Ethernet ports and four rate-selectable ports that you can configure as 100-Gigabit Ethernet ports or 40-Gigabit Ethernet ports; each rate-selectable port can be configured as four 10-Gigabit Ethernet ports by using a breakout cable. The 10-Gigabit Ethernet ports support SFP+ transceivers and rate-selectable ports support QSFP28 and QSFP+ transceivers.

    • EX9253 contains six built-in QSFP+ ports, each of which can house QSFP+ pluggable transceivers and 12 built-in QSFP28 ports, each of which can house QSFP28 pluggable transceivers.

Logical Part of an Interface Name for EX Series

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 show ethernet-switching interfaces command on a system with a default VLAN, the resulting display shows the logical interfaces associated with the VLAN:

Wildcard Characters in Interface Names for EX Series

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 (" ").

Physical Part of an Interface Name for QFX series, NFX Series, EX4600, QFabric System

Interfaces in Junos OS are specified as follows:

device-name:type-fpc/pic/port

The convention is as follows (and platform support depends on the Junos OS release in your installation):

  • device-name—(QFabric systems only) The device-name is either the serial number or the alias of the QFabric system component, such as a Node device, Interconnect device, or QFabric infrastructure. The name can contain a maximum of 128 characters and cannot contain any colons.

  • type—The QFX Series and EX4600 device interfaces use the following media types:

    • fc—Fibre Channel interface

    • ge—Gigabit Ethernet interface

    • xe—10-Gigabit Ethernet interface

    • sxe—10-Gigabit Service interface. sxe is an internal interface and user must not configure this interface. It supports L2 and L3 configurations like VLANs and IP address.

    • xle—40-Gigabit Ethernet interface (QFX3500, QFX3600, and QFX5100 switches running a QFabric software package)

    • et—25-Gigabit Ethernet interface (QFX5120 and QFX5200 switches)

    • et—40-Gigabit Ethernet interface (QFX3500, QFX3600, QFX5100, QFX5200, QFX10000, and EX4600 switches running Enhanced Layer 2 Software)

    • et—100-Gigabit Ethernet interface (QFX5200 and QFX10000 switches running Enhanced Layer 2 Software)

    • fte—40-Gigabit data plane uplink interface (QFX3500, QFX3600, and QFX5100 switches running a QFabric software package)

    • me—Management interface

    • em—Management interface on QFX5100 and EX4600 switches.

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

    • On QFX3500, QFX3600, QFX5100 devices running a QFabric software package, and QFX10002 switches, the FPC number is always 0.

      The FPC number indicates the slot number of the line card that contains the physical interface.

    • On QFX3500, QFX3600, QFX5100, QFX5200, EX4600, QFX10002, QFX10008, and QFX10016 switches running Enhanced Layer 2 Software, the member ID of a member in a Virtual Chassis determines the FPC number.

      Note:

      Every member in a Virtual Chassis must have a unique member ID, otherwise the Virtual Chassis will not be created.

    • On standalone QFX5100, EX4600, and QFX10002 switches, the FPC number is always 0.

  • pic—QFX Series and EX4600 device interfaces use the following convention for the PIC (Physical Interface Card) number in interface names:

    Table 7: Naming Conventions for PICs
    Device with Software Package Convention

    QFX3500 switch with QFabric software package

    PIC 0 can support 48 ports, PIC 1 can support 16 10-Gigabit Ethernet ports, and PIC 2 can support 4 40-Gigabit Ethernet ports.

    QFX3500 switch with Enhanced Layer 2 software

    PIC 0 can support 48 ports, and PIC 1 can support 16 10-Gigabit Ethernet ports, and 4 40-Gigabit Ethernet ports.

    QFX3500 Node device with a QFabric software package

    PIC 0 can support 48 ports and PIC 1 can support four 40-Gigabit data plane uplink ports.

    QFX3600 switch with a QFabric software package

    PIC 0 can support 64 10-Gigabit Ethernet ports, and PIC 1 can support 16 40-Gigabit Ethernet ports.

    QFX3600 switch with Enhanced Layer 2 software

    PIC 0 can support 64 10-Gigabit Ethernet ports and can also support 16 40-Gigabit Ethernet ports.

    QFX3600 Node device running a QFabric software package

    PIC 0 can support 56 10-Gigabit Ethernet ports, and PIC 1 can support 8 40-Gigabit data plane uplink ports, and up to 14 40-Gigabit Ethernet ports.

    QFX5100-48S switch with Enhanced Layer 2 software

    PIC 0 provides six 40-Gbps QSFP+ ports and 48 10-Gigabit Ethernet interfaces.

    EX4600 device with Enhanced Layer 2 software

    PIC 0 provides 4 40-Gbps QSFP+ ports and 24 10-Gigabit Ethernet interfaces. There are two expansion bays (PIC 1 and PIC 2), and you can insert QFX-EM-4Q expansion modules and EX4600-EM-8F expansion modules. The QFX-EM-4Q expansion module provide 4 40-Gbps QSFP+ ports. The EX4600-EM-8F expansion module provides 8 10-Gbps SFP+ ports. You can insert any combination of expansion modules. For example, you can insert two EX4600-EM-8F expansion modules, two QFX-EM-4Q expansion modules, or one of each.

    QFX5100-48S switch with a QFabric software package

    PIC 1 provides six 40-Gbps QSFP+ ports, and PIC 0 provides 48 10-Gigabit Ethernet interfaces.

    QFX5100-24Q switch with Enhanced Layer 2 software

    PIC 0 provides 24 40-Gbps QSFP+ ports. PIC 1 and PIC 2 can each contain a QFX-EM-4Q expansion module, and each expansion module provides 4 40-Gbps QSFP+ ports

    QFX5100-96S switch with Enhanced Layer 2 software

    PIC 0 provides 96 10-Gigabit Ethernet interfaces and 8 40-Gbps QSFP+ ports .

    QFX5110-48S switch with Enhanced Layer 2 software

    PIC 0 can support 48 10-Gigabit Ethernet ports labeled 0 through 47, and 4 QSFP28 ports labeled 48 through 51. Ports 0 through 47 support either 1-Gbps small form-factor pluggable (SFP) or 10-Gbps small form-factor pluggable plus (SFP+) transceivers. You can also use SFP+ DAC cables and 10-Gbps active optical cables (AOC) in any access port. The default 100-Gigabit Ethernet ports can be configured as 40-Gigabit Ethernet, and in this configuration can either operate as dedicated 40-Gigabit Ethernet ports or can be channelized to 4 independent 10-Gigabit Ethernet ports using copper or fiber breakout cables.

    QFX5200-32C switch with Enhanced Layer 2 software

    PIC 0 provides 32 QSFP28 ports. The 100-Gigabit Ethernet ports can be channelized to two 50-Gigabit Ethernet or four 25-Gigabit Ethernet ports. The default 100-Gigabit Ethernet ports can be configured as 40-Gigabit Ethernet and operate as 40-Gigabit Ethernet or be channelized to four 10-Gigabit Ethernet ports.

    QFX10002-36Q switch with Enhanced Layer 2 software

    PIC 0 provides 144 10-Gigabit Ethernet interfaces, and 36 40-Gbps QSFP+ ports, and 12 100-Gigabit Ethernet interfaces.

    QFX10002-72Q switch with Enhanced Layer 2 software

    PIC 0 provides 288 10-Gigabit Ethernet interfaces, and 72 40-Gbps QSFP+ ports, and 24 100-Gigabit Ethernet interfaces.

    QFX10008 switch with Enhanced Layer 2 software

    PIC 0 provides one-thousand, one-hundred fifty two 10-Gigabit Ethernet interfaces, two-hundred eighty-eight 40-Gbps QSFP+ ports, or two-hundred forty 100-Gigabit Ethernet interfaces.

    QFX10016 switch with Enhanced Layer 2 software

    PIC 0 provides two-thousand, three-hundred and four 10-Gigabit Ethernet interfaces, five-hundred seventy-six 40-Gbps QSFP+ ports, or four-hundred eighty 100-Gigabit Ethernet interfaces.

  • port—Interfaces use the following convention for port numbers:

    Table 8: Naming Conventions for PORTs
    Device with Software Package Convention

    QFX3500 switch with a QFabric software package

    There are 48 network access ports (10-Gigabit Ethernet) labeled 0 through 47 on PIC 0 and, 16 network access ports labeled 0 through 15 on PIC 1, and four 40-Gbps QSFP+ ports labeled Q0 through Q3 on PIC 2. You can use the QSFP+ ports to connect the Node device to Interconnect devices.

    By default, the 40-Gbps QSFP+ ports are configured to operate as 10-Gigabit Ethernet ports. You can use QSFP+ to four SFP+ copper breakout cables to connect the 10-Gigabit Ethernet ports to other servers, storage, and switches. Optionally, you can choose to configure the QSFP+ ports as 40-Gigabit Ethernet ports (see Configuring the QSFP+ Port Type on QFX3500 Standalone Switches).

    QFX3500 switch with Enhanced Layer 2 software

    There are 48 network access ports labeled 0 through 47 on PIC 0 and 4 40-Gbps QSFP+ ports labeled Q0 through Q3 on PIC 1. See Channelizing Interfaces on QFX3500, QFX3600, QFX5100, QFX10002, QFX10008, QFX10016, and EX4600 Switches for information on how to configure and channelize the 40-Gbps QSFP+ ports.

    QFX3600 switch with a QFabric software package

    There are 64 network access ports (10-Gigabit Ethernet) labeled Q0 through Q15 on PIC 0, and there are 16 network access ports (40-Gigabit Ethernet) labeled Q0 through Q15 on PIC 1.

    By default, all the QSFP+ ports are configured to operate as 40-Gigabit Ethernet ports. Optionally, you can choose to configure the QSFP+ ports as 10-Gigabit Ethernet ports (see Configuring the Port Type on QFX3600 Standalone Switches) and use QSFP+ to four SFP+ copper breakout cables to connect the 10-Gigabit Ethernet ports to other servers, storage, and switches.

    QFX3600 Node device with a QFabric software package

    PIC 0 can support up to 56 10-Gigabit Ethernet ports labeled Q2 through Q15, and PIC 1 can support up to 8 40-Gigabit data plane uplink ports labeled Q0 through Q7, and up to 14 40-Gigabit Ethernet ports labeled Q2 through Q15.

    On a QFX3600 Node device, by default, four 40-Gbps QSFP+ ports (labeled Q0 through Q3) are configured for uplink connections between your Node device and your Interconnect devices, and twelve 40-Gbps QSFP+ ports (labeled Q4 through Q15) use QSFP+ to four SFP+ copper breakout cables to support up to 48 10-Gigabit Ethernet ports for connections to either endpoint systems (such as servers and storage devices) or external networks. Optionally, you can choose to configure the first eight ports (Q0 through Q7) for uplink connections between your Node device and your Interconnect devices, and ports Q2 through Q15 for 10-Gigabit Ethernet or 40-Gigabit Ethernet connections to either endpoint systems or external networks (see Configuring the Port Type on QFX3600 Node Devices).

    QFX3600 switch with Enhanced Layer 2 software

    PIC 0 can support 64 network access ports (10-Gigabit Ethernet ports) labeled Q0 through Q15 and 16 40-Gigabit Ethernet ports labeled Q0 through Q15. See Channelizing Interfaces on QFX3500, QFX3600, QFX5100, QFX10002, QFX10008, QFX10016, and EX4600 Switches for information on how to configure and channelize the 40-Gbps QSFP+ ports.

    QFX5100-48S switch with Enhanced Layer 2 software

    PIC 0 can support 48 network access ports (10-Gigabit Ethernet ports) labeled 0 through 47 and 6 40-Gbps QSFP+ ports labeled 48 through 53. See Channelizing Interfaces on QFX3500, QFX3600, QFX5100, QFX10002, QFX10008, QFX10016, and EX4600 Switches for information on how to configure and channelize the 40-Gbps QSFP+ ports.

    EX4600 switch with Enhanced Layer 2 software

    PIC 0 can support 24 network access ports (10-Gigabit Ethernet ports) labeled 0 through 23 and 4 40-Gbps QSFP+ ports labeled 24 through 27. There are two expansion bays (PIC 1 and PIC 2), and you can insert QFX-EM-4Q expansion modules and EX4600-EM-8F expansion modules. The QFX-EM-4Q expansion module provide 4 40-Gbps QSFP+ ports. The EX4600-EM-8F expansion module provides 8 10-Gbps SFP+ ports. You can insert any combination of expansion modules. For example, you can insert two EX4600-EM-8F expansion modules, two QFX-EM-4Q expansion modules, or one of each. See Channelizing Interfaces on QFX3500, QFX3600, QFX5100, QFX10002, QFX10008, QFX10016, and EX4600 Switches for information on how to configure and channelize the 40-Gbps QSFP+ ports.

    QFX5100-48S switch with a QFabric software package

    PIC 0 can support 48 network access ports (10-Gigabit Ethernet ports) labeled 0 through 47, and PIC 1 can support 6 40-Gbps QSFP+ ports labeled 0 through 5. See Configuring the QSFP+ Port Type on QFX5100 Devices for information on how to configure the port mode of 40-Gbps QSFP+ ports.

    QFX5100-24Q switch with Enhanced Layer 2 software

    PIC 0 can support 24 40-Gbps QSFP+ ports labeled 0 through 23. PIC 1 and PIC 2 each support 4 40-Gbps QSFP+ port, for a total of eight 40-Gbps QSFP+ ports. See Channelizing Interfaces on QFX3500, QFX3600, QFX5100, QFX10002, QFX10008, QFX10016, and EX4600 Switches for information on how to configure and channelize the 40-Gbps QSFP+ ports.

    Note:

    You cannot channelize the 40-Gbps QSFP+ ports provided in the two QFX-EM-4Q expansion modules. Also, even though there is a total of 128 physical ports, only 104 logical ports can be channelized.

    You can configure different system modes to achieve varying levels of port density on the QFX5100-24Q and QFX5100-96S switches. Depending on the system mode you configure, there are restrictions on which ports you can channelize. If you channelize ports that are restricted, the configuration is ignored. See Configuring the System Mode for information on how to configure the system mode.

    QFX5100-96S switch with Enhanced Layer 2 software

    PIC 0 can support 96 10-Gigabit Ethernet ports labeled 0 through 95, and 8 40-Gbps QSFP+ ports labeled 96 through 103. See Channelizing Interfaces on QFX3500, QFX3600, QFX5100, QFX10002, QFX10008, QFX10016, and EX4600 Switches for information on how to configure and channelize the 40-Gbps QSFP+ ports.

    Note:

    You can only channelize the 40-Gbps QSFP+ ports provided in ports 96 and 100, because only 104 logical ports can be channelized.

    You can configure different system modes to achieve varying levels of port density on the QFX5100-24Q and QFX5100-96S switches. Depending on the system mode you configure, there are restrictions on which ports you can channelize. If you channelize ports that are restricted, the configuration is ignored. See Configuring the System Mode for information on how to configure the system mode.

    QFX5110-48S switch with Enhanced Layer 2 software

    PIC 0 can support 48 10-Gigabit Ethernet ports labeled 0 through 47, and 4 QSFP28 ports labeled 48 through 51. These data ports (0 through 47) support either 1-Gbps small form-factor pluggable (SFP) or 10-Gbps small form-factor pluggable plus (SFP+) transceivers. You can also use SFP+ DAC cables and 10-Gbps active optical cables (AOC) in any access port.The default 100-Gigabit Ethernet ports can be configured as 40-Gigabit Ethernet, and in this configuration can either operate as dedicated 40-Gigabit Ethernet ports or can be channelized to 4 independent 10-Gigabit Ethernet ports using copper or fiber breakout cables.

    QFX5200-32C switch with Enhanced Layer 2 software

    There is support for both quad small-form-factor pluggable (QSFP+) and 28-Gbps QSFP+ (QSFP28) transceivers in the 32 QSFP28 sockets. The QSFP28 ports are configured as 100-Gigabit Ethernet ports by default, but can also be configured to speeds of 50, 40, 25, or 10 Gigabit Ethernet.

    The 100 Gigabit Ethernet ports can be channelized using breakout cables either to 2 independent downstream 50 Gigabit Ethernet or to 4 independent 25 Gigabit Ethernet ports. The default 100 Gigabit Ethernet ports can also be configured as 40 Gigabit Ethernet and in this configuration can either operate as dedicated 40 Gigabit Ethernet ports or can be channelized to 4 independent 10 Gigabit Ethernet ports using breakout cables. See Channelizing Interfaces on QFX5200-32C Switches for information on how to configure and channelize the interfaces.

    QFX10002-36Q switch with Enhanced Layer 2 software

    There are 36 quad small-form factor pluggable plus (QSFP+) ports that support 40-Gigabit Ethernet optical transceivers. Out of these 36 ports, 12 ports are QSFP28 capable, which are dual speed 40- or 100-Gigabit Ethernet optical transceivers.

    Each QSFP28 socket can be configured to support:

    • 100-Gigabit Ethernet using 28-Gbps QSFP28 optical transceivers. When a QSFP28 transceiver is inserted into the ports marked with a fine black line underneath the socket and the port is configured for 100-Gigabit Ethernet, the two adjacent ports are disabled and the QSFP28 is enabled for 100-Gigabit Ethernet.

    • 40-Gigabit Ethernet using QSFP+ optical transceivers.

    • 10-Gigabit Ethernet using breakout cables. When configured for channelization, a breakout cable converts the 40-Gigabit Ethernet port into 4 independent 10-Gigabit Ethernet ports.

      Any of the 36 ports 0 through 35 can be configured as either uplink or access ports. See Channelizing Interfaces on QFX3500, QFX3600, QFX5100, QFX10002, QFX10008, QFX10016, and EX4600 Switches for information on how to configure and channelize the 40-Gbps QSFP+ ports.

    Each of the 12 QSFP28 ports support:

    • 100-Gigabit Ethernet QSFP28 transceivers

    • 40-Gigabit Ethernet QSFP+ transceivers

    Each of the 36 QSFP+ ports support:

    • 40-Gigabit Ethernet QSFP+ transceivers

    • Access ports

    QFX10002-72Q switch with Enhanced Layer 2 software

    There are 72 quad small-form factor pluggable plus (QSFP+) ports that support 40-Gigabit Ethernet optical transceivers. Out of these 72 ports, 24 ports are QSFP28 capable, which are dual speed 40- or 100-Gigabit Ethernet optical transceivers.

    Each QSFP28 socket can be configured to support:

    • 100-Gigabit Ethernet using 28-Gbps QSFP28 optical transceivers. When a QSFP28 transceiver is inserted into the ports marked with a fine black line underneath the socket and the port is configured for 100-Gigabit Ethernet, the two adjacent ports are disabled and the QSFP28 is enabled for 100-Gigabit Ethernet.

    • 40-Gigabit Ethernet using QSFP+ optical transceivers.

    • 10-Gigabit Ethernet using breakout cables. When configured for channelization, a breakout cable converts the 40-Gigabit Ethernet port into 4 independent 10-Gigabit Ethernet ports.

      Any of the 72 ports 0 through 71 can be configured as either uplink or access ports. See Channelizing Interfaces on QFX3500, QFX3600, QFX5100, QFX10002, QFX10008, QFX10016, and EX4600 Switches for information on how to configure and channelize the 40-Gbps QSFP+ ports.

    Each of the 24 QSFP28 ports support:

    • 100-Gigabit Ethernet QSFP28 transceivers

    Each of the 72 QSFP+ ports support:

    • 40-Gigabit Ethernet QSFP+ transceivers

    Each of the 36 QSFP+ ports support:

    • 40-Gigabit Ethernet QSFP+ transceivers

    • Access ports

    • Uplink ports

    On a QFX10008 switch with Enhanced Layer 2 software, there are two line cards available:

    QFX10008 with Line Card QFX10000-36Q (ELS)

    QFX10000-36Q, a 36-port 40-Gigabit Ethernet quad small form-factor pluggable plus transceiver (QSFP+) or 12-port 100GbE QSFP28 line card

    The QFX10000-36Q line cards supports

    Each QSFP28 socket can be configured to support:

    • 100-Gigabit Ethernet using QSFP28 optical transceivers. When a QSFP28 transceiver is inserted into the ports marked with a fine black line underneath the socket and the port is configured for 100-Gigabit Ethernet, the two adjacent ports are disabled and the QSFP28 socket is enabled for 100-Gigabit Ethernet.

      • 40-Gigabit Ethernet using QSFP+ optical transceivers.

      • 10-Gigabit Ethernet using breakout cabling and attached optical transceivers. When configured for channelization, the system converts the 40-Gigabit Ethernet port into 4 independent 10-Gigabit Ethernet ports.

      Any of the 36 ports 0 through 35 can be configured as either uplink or access ports. See Channelizing Interfaces on QFX3500, QFX3600, QFX5100, QFX10002, QFX10008, QFX10016, and EX4600 Switches for information on how to configure and channelize the 40-Gbps QSFP+ ports.

    Each of the 12 QSFP28 ports supports:

    • 100-Gigabit Ethernet QSFP28 transceivers

    • 40-Gigabit Ethernet QSFP+ transceivers

    Each of the 12 QSFP28 ports supports:

    • 100-Gigabit Ethernet QSFP28 transceivers

      • 40-Gigabit Ethernet QSFP+ transceivers

      Each of the 36 QSFP+ ports support:

      • 40-Gigabit Ethernet QSFP+ transceivers

      • Access ports

      • Uplink ports

    QFX10008 with Line Card QFX10000-30C and QFX10000-30C-M (ELS)

    QFX10000-30C and QFX10000-30C-M, a 30-port 100-Gigabit or 40-Gigabit Ethernet QSFP28 line card

    • The QFX10000-30C and QFX10000-30C-M line cards support:

      Thirty 28-Gbps QSFP+ Pluggable Solution (QSFP28) cages that support either 40-Gigabit Ethernet or 100-Gigabit Ethernet optical transceivers. The QFX10000-30C and QFX10000-30C-M ports auto detect the type of transceiver installed and set the configuration to the appropriate speed.

      Each QSFP28 socket can be configured to support:

      • 100-Gigabit Ethernet using QSFP28 optical transceivers. When a QSFP28 transceiver is inserted into the ports marked with a fine black line underneath the socket and the port is configured for 100-Gigabit Ethernet, the two adjacent ports are disabled and the QSFP28 socket is enabled for 100-Gigabit Ethernet.

      • 40-Gigabit Ethernet using QSFP+ optical transceivers.

      See Channelizing Interfaces on QFX3500, QFX3600, QFX5100, QFX10002, QFX10008, QFX10016, and EX4600 Switches for information on how to configure and channelize the 40-Gbps QSFP+ ports.

      Each of the 30 QSFP28 ports supports:

      • 100-Gigabit Ethernet QSFP28 transceivers

      • 40-Gigabit Ethernet QSFP+ transceivers

      • Access ports

      • Uplink ports

    On a QFX10016 switch running Enhanced Layer 2 software, there are 16 slots, which you can populate with two types line cards:

    QFX10016 with Line Card QFX10000-36Q (ELS)

    • QFX10000-36Q, a 36-port 40-Gigabit Ethernet quad small form-factor pluggable plus transceiver (QSFP+) or 12-port 100GbE QSFP28 line card

      The QFX10000-36Q line card consists of 36 quad small form-factor pluggable plus (QSFP+) ports that support 40-Gigabit Ethernet optical transceivers. Out of these 36 ports, 12 ports are QSFP28 capable. The QSFP+ ports are dual speed and can support either 40-Gigabit or 100-Gigabit Ethernet optical transceivers. The line card can support 10-Gigabit Ethernet by channelizing the 40-Gigabit ports. Channelization is supported on fiber break-out cable using standard structured cabling techniques.

      With 100-Gigabit Ethernet using QSFP28 optical transceivers, when a QSFP28 transceiver is inserted into the ports marked with a fine black line underneath the socket and the port is configured for 100-Gigabit Ethernet, the two adjacent ports are disabled and the QSFP28 socket is enabled for 100-Gigabit Ethernet.

      You can use 40-Gigabit Ethernet using QSFP+ optical transceivers.

      With 10-Gigabit Ethernet using breakout cabling and attached optical transceivers, when configured for channelization, the system converts the 40-Gigabit Ethernet port into 4 independent 10-Gigabit Ethernet ports.

      Any of the 36 ports 0 through 35 can be configured as either uplink or access ports.

      Each of the 12 QSFP28 ports supports:

      • 100-Gigabit Ethernet QSFP28 transceivers

      • 40-Gigabit Ethernet QSFP+ transceivers

      Each of the 36 QSFP+ ports supports:

      • 40-Gigabit Ethernet QSFP+ transceivers

      • Access ports

        You can use 40-Gigabit Ethernet QSFP+ transceivers in any downstream port.

      • Uplink ports

        You can configure all the QSFP+ ports as uplinks.

      Every second and sixth port in a 6XQSFP cage on a QFX10000-36Q supports 100-Gigabit Ethernet using QSFP28 transceivers. These 100-Gigabit Ethernet ports work either as 100-Gigabit Ethernet or as 40-Gigabit Ethernet, but are recognized as 40-Gigabit Ethernet by default. When a 40-Gigabit Ethernet transceiver is inserted into a 100-Gigabit Ethernet port, the port recognizes the 40-Gigabit Ethernet port speed. When a 100-Gigabit Ethernet transceiver is inserted into the port and enabled in the CLI, the port recognizes the 100-Gigabit Ethernet speed and disables two adjacent 40-Gigabit Ethernet ports. You can also use an 100-Gigabit Ethernet transceiver and run it at 40-Gigabit Ethernet by using the CLI to set the port speed to 40-Gigabit Ethernet.

      The 40-Gigabit Ethernet ports can operate independently, be channelized into four 10-Gigabit Ethernet ports, or bundled with the next two consecutive ports and channelized into twelve 10-Gigabit Ethernet ports as a port range. Only the first and fourth port in each 6XQSFP cage are available to channelize a port range. The port range must be configured using the set chassis fpc pic port channel-speed command. For example, to channelize the first switch port, use the set chassis fpc 0 pic 0port 1channel-speed 10g command.

    QFX10016 with Line Card QFX10000-30C and QFX10000-30C-M (ELS)

    QFX10000-30C and QFX10000-30C-M, a 30-port 100-Gigabit or 40-Gigabit Ethernet QSFP28 line card. The QFX10000-30C and QFX10000-30C-M ports auto detect the type of transceiver installed and set the configuration to the appropriate speed.

    Each QSFP28 socket supports:

    • 100-Gigabit Ethernet using QSFP28 optical transceivers. When a QSFP28 transceiver is inserted into any of the ports, the QSFP28 socket is enabled for 100-Gigabit Ethernet.

    • 40-Gigabit Ethernet using QSFP+ optical transceivers. When a QSFP+ transceiver is inserted into any of the ports, the QSFP+ socket is enabled for 40-Gigabit.

      Any of the 30 ports 0 through 29 can be configured as either uplink or access ports, and of the 30 QSFP28 ports supports:

      • 100-Gigabit Ethernet QSFP28 transceivers

      • 40-Gigabit Ethernet QSFP+ transceivers

Logical Part of an Interface Name on a Switch Running QFabric Software Package for QFX series, NFX Series, EX4600, QFabric System

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: device-name (QFabric systems only): type-fpc/pic/port.logical-unit-number. For example, if you issue the show ethernet-switching interfaces command on a system with a default VLAN, the resulting display shows the logical interfaces associated with the VLAN:

When you configure aggregated Ethernet interfaces, you configure a logical interface, which is called a or a . Each LAG can include up to eight Ethernet interfaces, depending on the switch model.

Logical Part of a Channelized Interface Name on a Switch Running Enhanced Layer 2 Software for QFX series, NFX Series, EX4600, QFabric System

Channelizing enables you to configure four 10-Gigabit Ethernet interfaces from a 40-Gigabit Ethernet QSFP+ interface. By default, a 40-Gigabit Ethernet QSFP+ interface is named et-fpc/pic/port. The resulting 10-Gigabit Ethernet interfaces appear in the following format: xe-fpc/pic/port:channel, where channel can be a value of 0 through 3.

For example, if an et interface named et-0/0/3 is channelized to four 10-Gigabit Ethernet interfaces, the resulting 10-Gigabit Ethernet interface names will be xe-0/0/3:0, xe-0/0/3:1, xe-0/0/3:2, and xe-0/0/3:3:

Wildcard Characters in Interface Names for QFX series, NFX Series, EX4600, QFabric System

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 (" ").

Physical Part of an Interface Name for OCX1100

Interfaces in Junos OS are specified as follows:

type-fpc/pic/port

The convention is as follows:

  • type—The OCX Series device interfaces use the following media types:

    • xe—10-Gigabit Ethernet interface

    • et—40-Gigabit Ethernet interface

    • em—Management interface

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

    • On standalone OCX Series switches, the FPC number is always 0.

      The FPC number indicates the slot number of the line card that contains the physical interface.

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

    • PIC 0 provides six 40-Gbps QSFP+ ports and 48 10-Gigabit Ethernet interfaces.

  • port—Interfaces use the following convention for port numbers:

    • PIC 0 can support 48 network access ports (10-Gigabit Ethernet ports) labeled 1 through 48 and 6 40-Gbps QSFP+ ports labeled 49 through 54.

Wildcard Characters in Interface Names for OCX1100

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 (" ").

See Also

Understanding Management Interfaces

You use management interfaces to access devices remotely. Typically, a management interface is not connected to the in-band network, but is connected to a device in the internal network. Through a management interface, you can access the device over the network using utilities such as ssh and telnet and configure it from anywhere, regardless of its physical location. As a security feature, users cannot log in as root through a management interface. To access the device as root, you must use the console port. You can also use root to log in using SSH.

Note:

Before you can use management interfaces, you must configure the logical interfaces with valid IP addresses. Juniper Networks does not support configuring two management interfaces in the same subnet.

Management interface port ranges vary based on device type (and platform support depends on the Junos OS release in your installation):

  • QFX3500 devices:

    The valid port range for a management interface (me) on a QFX3500 device is between 0 and 6, with a total of seven available ports. On a QFX3500 standalone switch, however, you can only configure me0 and me1 as management interfaces. The management interfaces are labeled C0 and C1, and they correspond to me0 and me1. On a QFX3500 Node device, the RJ-45 management interfaces and SFP management interfaces correspond to me5 and me6

  • QFX3600 devices:

    There are two RJ-45 management interfaces (labeled C0 and C1) and two SFP management interfaces (labeled C0S and C1S). On a QFX3600 standalone switch, the RJ-45 management interfaces and SFP management interfaces correspond to me0 and me1. On a QFX3600 Node device, the RJ-45 management interfaces and SFP management interfaces correspond to me5 and me6. Each pair of management interfaces correspond to one Ethernet interface—for example, both RJ-45 management interfaces (labeled C0 and C0s) can correspond to me0, and both SFP management interfaces (labeled C1 and C1S) can correspond to me1. By default, both RJ-45 management interfaces are active. If you insert an SFP interface into the SFP management port (C0S, for example), the SFP interface would become the active management interface, and the corresponding RJ-45 management interface (C0) is disabled.

    Note:

    On a QFX3600 device, you can use either the RJ-45 or the SFP management interfaces, but not both at the same time.

  • On QFX5100, QFX5200, and EX4600 switches, there is one RJ-45 management interface (labeled C0 and one SFP management interface (labeled C1), and they correspond to em0 and em1. You can use both management interfaces simultaneously.

  • On QFX10002 and QFX10008 switches, there is one RJ-45 management interface (labeled MGMT and one SFP management interface (labeled MGMT), and they correspond to em0 and em1. Although the CLI permits you to configure two management Ethernet interfaces within the same subnet, only one interface is usable and supported.

  • On QFX10008 and QFX10016 switches, if you are using em1 for management purpose, then you cannot directly access the backup RE em1 from external network. Indirectly you can access the backup RE from external network, by following these steps:

    • Login to primary RE using SSH/Telnet to its em1.

    • Access backup RE using the following command:

  • On OCX Series switches:

    There is one RJ-45 management interface (labeled MGMT), which corresponds to em0. The em0 interface always has the status up in show command outputs, even if the physical port is empty. The me0 interface is a virtual interface between Junos and the host operating system, therefore its status is independent from the status of the physical port.

  • QFabric system:

    On a QFabric system, there are management interfaces on the Node devices, Interconnect devices, and Director devices. However, you cannot access the management interfaces on the Node devices or Interconnect devices directly. You can only manage and configure these devices using the Director device. You can connect to the management interface over the network using utilities such as SSH.

    For information on how to use management interfaces on a QFabric system, see Performing the QFabric System Initial Setup on a QFX3100 Director Group and Gaining Access to the QFabric System Through the Default Partition.