
If you disable FCoE transit, FIP and FCoE traffic are handled as normal Ethernet frames and no FIP snooping ACLs are generated.
The VLAN-specific and FIP snooping configuration is disabled and stored until you re-enable FCoE transit and the configurations are
re-applied.
Enable FIP Snooping on VLANs
You can enable FIP snooping globally on a switch on all VLANs or on a specified VLAN.
When you enable FIP snooping on VLANs:
•
FIP frames are allowed to pass through the switch on the enabled VLANs and are processed to generate FIP snooping ACLs.
•
FCoE traffic is allowed on VLANs only after a successful virtual-link initialization (fabric login FLOGI) between an ENode and an
FCF. All other FCoE traffic is dropped.
•
You must configure at least one interface for FCF (FCoE Forwarder) mode on a FIP snooping-enabled VLAN. You can configure
multiple FCF trusted interfaces in a VLAN.
•
A maximum of eight VLANS are supported for FIP snooping on the switch. When enabled globally, FIP snooping processes FIP
packets in traffic only from the first eight incoming VLANs. When enabled on a per-VLAN basis, FIP snooping is supported on up
to eight VLANs.
Configure the FC-MAP Value
You can configure the FC-MAP value to be applied globally by the switch on all or individual FCoE VLANs to authorize FCoE traffic.
The configured FC-MAP value is used to check the FC-MAP value for the MAC address assigned to ENodes in incoming FCoE
frames. If the FC-MAP value does not match, FCoE frames are dropped. A session between an ENode and an FCF is established by
the switch-bridge only when the FC-MAP value on the FCF matches the FC-MAP value on the FIP snooping bridge.
Configure a Port for a Bridge-to-Bridge Link
If a switch port is connected to another FIP snooping bridge, configure the FCoE-Trusted Port mode for bridge-bridge links.
Initially, all FCoE traffic is blocked. Only FIP frames with the ALL_FCF_MAC and ALL_ENODE_MAC values in their headers are
allowed to pass. After the switch learns the MAC address of a connected FCF, it allows FIP frames destined to or received from the
FCF MAC address.
FCoE traffic is allowed on the port only after the switch learns the FC-MAP value associated with the specified FCF MAC address
and verifies that it matches the configured FC-MAP value for the FCoE VLAN.
Configure a Port for a Bridge-to-FCF Link
If a port is directly connected to an FCF, configure the port mode as FCF. Initially, all FCoE traffic is blocked; only FIP frames are
allowed to pass.
FCoE traffic is allowed on the port only after a successful fabric login (FLOGI) request/response and confirmed use of the
configured FC-MAP value for the VLAN.
FLOGI and fabric discovery (FDISC) request/response packets are trapped to the CPU. They are forwarded after the necessary
ACLs are installed.
Impact on Other Software Features
When you enable FIP snooping on a switch, other software features are impacted. The following table lists the impact of FIP
snooping.
FCoE Transit
313
Содержание 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 ...