Nexsus load balancing mechanism for FcoE Mappings

On the Nexus 5000, the default load balancing mechanism on the LACP port-channel is source-destination. If we leave it in this state, all the FCoE traffic will take the same link in the port channel when the Nexus 5000 is forwarding frames to the upstream device. To enable the Nexus 5000 to load balance using exchange IDs, we configure it for ‘source-dest-port’ load balancing. Nexus5000(config)# port-channel load-balance ethernet ? destination-ip    Destination IP address destination-mac   Destination…

Read More

Example:Mapping VSANs to VLANs

Example:Mapping VSANs to VLANs The following example shows how to configure the FCoE VLAN and a virtual Fibre Channel interface: SUMMARY STEPS 1.    Enable the associated VLAN and map the VLAN to a VSAN. For Cisco Nexus 7000, ensure you are in the storage VDC. 2.    Configure the VLAN on a physical Ethernet interface. 3.    Create a virtual Fibre Channel interface and bind it to a physical Ethernet interface. For Cisco Nexus 7000, ensure you are in the…

Read More

Nexus 5500 to Nexus 7000 Multi-Hop FCoE Configuration Example

Configure In order to begin this process, you must verify that: The Nexus 7000 has the FCoE feature enabled. The module F1 is licensed for FCoE. The system Quality of Service (QoS) is set correctly. The storage Virtual Device Contexts (VDC) are created. The dedicated and shared interfaces are configured. In order to configure the Nexus 7000 Switch for Multi-Hop FCoE, complete these steps. Enter these commands: default_vdc(config)# license fcoe module 1 default_vdc(config)#system qos default_vdc(config-sys-qos)# service-policy…

Read More

Nexus FCoE Design and Configuration

Nexus FCoE Design and Configuration I have been deploying more and more FCoE solutions on Nexus 5500s lately and thought it best to write down my design/config here for reference the next time I perform a deployment. What always throws me is that the vPC is intelligent enough to keep the FCoE VLANs isolated per FC storage best-practices (i.e. VLAN 11 on Fabric A, VLAN 12 on Fabric B), but allows the Data VLAN (i.e. VLAN…

Read More