
16
FCoE Transit
The Fibre Channel over Ethernet (FCoE) Transit feature is supported on Ethernet interfaces. When you enable the switch for FCoE
transit, the switch functions as a FIP snooping bridge.
NOTE: FIP snooping is not supported on Fibre Channel interfaces or in a switch stack.
Fibre Channel over Ethernet
FCoE provides a converged Ethernet network that allows the combination of storage-area network (SAN) and LAN traffic on a
Layer 2 link by encapsulating Fibre Channel data into Ethernet frames.
FCoE works with the Ethernet enhancements provided in data center bridging (DCB) to support lossless (no-drop) SAN and LAN
traffic. In addition, DCB provides flexible bandwidth sharing for different traffic types, such as LAN and SAN, according to 802.1p
priority classes of service. DCBx should be enabled on the system before the FIP snooping feature is enabled. For more information,
refer to the
chapter.
Ensure Robustness in a Converged Ethernet Network
Fibre Channel networks used for SAN traffic employ switches that operate as trusted devices. To communicate with other end
devices attached to the Fibre Channel network, end devices log into the switch to which they are attached.
Because Fibre Channel links are point-to-point, a Fibre Channel switch controls all storage traffic that an end device sends and
receives over the network. As a result, the switch can enforce zoning configurations, ensure that end devices use their assigned
addresses, and secure the network from unauthorized access and denial-of-service (DoS) attacks.
To ensure similar Fibre Channel robustness and security with FCoE in an Ethernet cloud network, FIP establishes virtual point-to-
point links between FCoE end-devices (server ENodes and target storage devices) and FCoE forwarders (FCFs) over transit FCoE-
enabled bridges.
Ethernet bridges commonly provide ACLs that can emulate a point-to-point link by providing the traffic enforcement required to
create a Fibre Channel-level of robustness. You can configure ACLs to emulate point-to-point links, providing control over the traffic
received or transmitted into the switch. To automatically generate ACLs, use FIP snooping. In addition, FIP serves as a Layer 2
protocol to:
•
Operate between FCoE end-devices and FCFs over intermediate Ethernet bridges to prevent unauthorized access to the
network and achieve the required security.
•
Allow transit Ethernet bridges to efficiently monitor FIP frames passing between FCoE end-devices and an FCF. To dynamically
configure ACLs on the bridge to only permit traffic authorized by the FCF, use the FIP snooping data.
FIP enables FCoE devices to discover one another, initialize and maintain virtual links over an Ethernet network, and access storage
devices in a storage area network (SAN). FIP satisfies the Fibre Channel requirement for point-to-point connections by creating a
unique virtual link for each connection between an FCoE end-device and an FCF via a transit switch.
FIP provides functionality for discovering and logging into an FCF. After discovering and logging in, FIP allows FCoE traffic to be sent
and received between FCoE end-devices (ENodes) and the FCF. FIP uses its own EtherType and frame format. The following
illustration shows the communication that occurs between an ENode server and an FCoE switch (FCF).
The following table lists the FIP functions.
308
FCoE Transit
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...