Supported Platforms
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.
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
| Type | Purpose |
|---|---|
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. |
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 QFX3500 standalone switch with a LAG on another QFX3500 standalone switch to create a MC-AE. The MC-AE provides load balancing and redundancy across the two QFX3500 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. |
Special Interfaces
Table 2 lists the types of special interfaces supported on the QFX Series.
Table 2: Special Interface Types and Purposes
| Type | Purpose |
|---|---|
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. |
Ethernet Interfaces | You can configure Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet interfaces to connect o other servers, storage, and switches. You can configure 40-Gigabit data plane uplink ports to connect a Node device to an Interconnect device. |
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 interface (RVI) | QFX Series products use a Layer 3 routed VLAN interface (RVI) named 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 functions as a logical router, eliminating the need for having both a switch and a router. The RVI (the vlan interface) 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. |
