Article Number: 000144525
The purpose of this article is to provide the best practice Fiber Channel implementation with S4810 as FSB and S5000 as FCF
The datacenter networking mainly comprise of Ethernet and Storage traffics. The Ethernet segment is called LAN (Local Area Network) and the storage segment is called SAN (Storage Area Network).
Fiber Channel (FC) is a high speed network technology used for connecting different Storage devices.
In the traditional networking environment there is dedicated links for LAN and SAN traffic. Once the FCoE (FiberChannel over Ethernet) technology emerged the Datacenter and Enterprise migrated from traditional infrastructure to converged infrastructure using the same link for carrying data and storage traffic.
Fiber Channel common terminologies
What is FIP (FCoE Initialization Protocol)?
Fiber Channel over Ethernet initialization protocol (FIP) ensures a virtual point-to-point link between Enodes and Fiberchannel Forwarded switches over transit FCoE-enabled bridges.
The below mentioned steps are carried out by FIP.
What is FIP Snooping Bridge (FSB)?
What is FCF (Fiber Channel Forwarders)?
It is a combination of FCoE and FC switch. It accepts the connections from the FSB to pass through it and reach the Fiber Channel switch.
What is N_Port ID Virtualization (NPIV)?
This is a feature which helps multiple N_Port IDs to share a single physical N_Port.
NPIV initialization
What is Zoning?
What is Data Center Bridging (DCB)?
The Data Center Bridging mainly comprises of three factors.
What are the different types of ports?
N_Port (Node Port): A port on the End Node (Either Host or Storage)
F_Port (Fabric Port): A port on the FC switch which provides the necessary information to Node ports.
E_Port (Expansion Port): A port connected between FC switches to form an Inter-Switch Link.
In this document we will discuss scenarios where Dell Datacenter products are carrying Fiberchannel traffic. This will also allow us to show the best practice configuration steps need to be followed.
Deploying the Dell S4810 FSB with Dell S5000 series switch (NPIV)
.
Steps performed to configure Dell S4810 as FSB:
NOTE: FIP snooping is only supported on S4810 Ethernet interfaces in standalone or VLT mode but not in a switch stack. FCoE is also not supported over VLT LAG.
> For example
cam-acl l2acl 4 ipv4acl 4 ipv6acl 0 ipv4qos 2 l2qos 1 l2pt 0 ipmacacl 0 vman-qos 0 ecfmacl 0 fcoeacl 2
# feature fip-snooping
# fip-snooping enable
# protocol lldp
# no disable
# service-class dynamic dot1p
By default vlan 1 will be used as native vlan. It can be changed to other value from 2 – 4094.
Create a vlan by typing below commands
# interface vlan <vlan id>
# no shutdown
# exit
Make the new vlan as default vlan
#default vlan-id <vlan id>
This vlan will only carry the FCoE traffic.
Create a vlan by typing below commands
# interface vlan <vlan id>
# no shutdown
# exit
# portmode hybrid – configuring portmode hybrid will allow the port to communicate on the native/default VLAN untagged, and other vlans can be tagged after wards
# switchport – this will configure the interface as a layer 2 port.
# protocol lldp –
# dcbx port-role auto-downstream – This command will configure the port-role as a dcbx capable downstream port. It will push the dcbx settings to the Server CNA ports if the server CNA is configured as a willing port.
# no shutdown
# exit
# portmode hybrid – configuring portmode hybrid will allow the port to communicate on the native/default VLAN untagged, and other vlans can be tagged after wards
# switchport – this will configure the interface as a layer 2 port.
# fip-snooping port-mode fcf – This allows FIP frames to pass through for FLOGI & FDISC process
# protocol lldp –
# dcbx port-role auto-upstream – This command will configure the port-role as a dcbx capable upstream port. It will learn the dcbx settings from the upstream FCF port.
# no shutdown
# exit
# protocol spanning-tree rstp
# no disable
# bridge-priority <value>
# spanning-tree rstp edge-port
# write memory
Steps performed to configure Dell S5000 as NPIV:
#feature fc
Priorities are mapped to priority groups using the ‘priority-pgid’ command. In this example, priorities 0, 1, 2, 4, 5, 6, and 7 are mapped to priority group 0. Priority 3 is mapped to priority-group 1.
# dcb-map <DCBMAP>
# priority-group 0 bandwidth 60 pfc off [60% bandwidth for LAN traffic with PFC off]
# priority-group 1 bandwidth 40 pfc on [40% bandwidth for SAN traffic with PFC on]
# priority-pgid 0 0 0 1 0 0 0 0 [Map FCoE priority 3 to priority group 1]
# exit
This vlan will only carry the FCoE traffic.
Create a vlan by typing below commands
# Interface vlan <vlan id>
# no shutdown
# exit
# fcoe-map <FCMAP>
# fabric-id <ID> vlan <FCoE VLAN ID> [Link the FCoE MAP to the FCoE VLAN]
# fc-map <0efcxx> [Value ranges from 0EFC00 – 0EFCFF]
# exit
The FCoE MAP needs to be applied to interface connected to FSB (S4810) and to the FC interface connecting to the FC switch.
# interface fi 0/x [Port connected to FC switch]
# fabric <FCMAP> [Apply FCoE MAP]
# no shut
# exit
# interface te 0/x[Port connected to FSB (S4810)]
# dcb-map <DCBMAP>[Apply DCB MAP]
# fcoe-map <FCMAP> [Apply FCoE MAP]
# end
# write memory
Commands for the troubleshooting and what to look for
Check for the fields like status, speed, duplex and VLAN in the output.
Check for MTU settings and make sure there is no CRC or throttles on the interfaces.
Check for FIP Snooping Feature status, Global config status, FC-MAP.
Check for FCF’s MAC address, connecting interface and VLAN fields.
Check for Enode MAC address, interface on which Enode is connected, VLAN, FC-ID and FCF-MAC
Check for FCoE MAC in the output
PowerSwitch S4810-ON, PowerSwitch S5000
21 Feb 2021
3
Solution