Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Interfaces Overview

Juniper Networks QFX Series products 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

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

Table 1: Network Interface Types and Purposes

TypePurpose

Aggregated Ethernet interfaces

You can 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

You can 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

You can 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.

LAN access interfaces

You can 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

You can 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

You can used 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

You can 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 and QFX3600 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.

Special Interfaces

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

Table 2: Special Interface Types and Purposes

TypePurpose

Console port

Each QFX Series product 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.

Loopback interface

All QFX Series products 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 OS for the QFX Series includes management Ethernet interfaces. The management Ethernet interface provides an out-of-band method for connecting to a standalone switch and QFabric system.

Routed VLAN interfaces (RVI and IRB interfaces)

QFX Series products use a Layer 3 routed VLAN interface (called RVI in the original CLI, and called IRB in Enhanced Layer 2 Software) vlan 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 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.

 

Related Documentation

 

Published: 2014-07-23

Previous Page Next Page