Juniper QFX3000-G QFabric, Deployment Manual, Page: 88 / 652

The 10-Gigabit Ethernet interfaces that connect to FCoE devices must include a native
VLAN to transport FIP traffic because FIP VLAN discovery and notification frames are
exchanged as untagged packets.
Each FCoE VLAN interface can present multiple VF_Port interfaces to the FCoE network.
•
One or more native FC interfaces. The native FC interfaces transport traffic between
the gateway and the FC switch or FCF.
TIP: If the network does not use a dual-rail architecture for redundancy,
configure more than one native FC interface for each local FC fabric to
create redundant connections between the FCoE devices and the FC
network. If one physical link goes down, any sessions it carried can log in
again and connect to the FC network on a different interface.
All of the FC and FCoE traffic that belongs to a local FC fabric on a Node device must
enter and exit that Node device. This means that the FC switch or FCF and the FCoE
devices in the Ethernet network must be connected to the same Node device. The
interfaces that connect to the FC switch and the interfaces that connect to the FCoE
devices must be included in the local FC fabric. You cannot configure a local FC fabric
that spans more than one Node device.
Traffic flows from FC and FCoE devices that are not in the same local FC fabric remain
separate and cannot communicate with each other through the FCoE-FC gateway.
NOTE: The QFabric system enforces commit checks to ensure that local FC
fabrics and FCoE VLANs on FCoE-FC gateways do not span more than one
Node device.
Related
Documentation
Overview of Fibre Channel on the QFX Series
•
•
Understanding an FCoE-FC Gateway
•
Understanding FCoE-FC Gateway Functions
•
Understanding Interfaces on an FCoE-FC Gateway
Understanding CoS Fabric Forwarding Class Sets
Supported Platforms
QFabric System
Copyright © 2015, Juniper Networks, Inc. 62
QFX3000-G QFabric System Deployment Guide