Users Guide

OS10(config‐pmap‐c‐nqos)# pause
OS10(config‐pmap‐c‐nqos)# pfc‐cos 3
7. Disable LLFC on the interface that connects to CNA 2.
OS10(config)# interface ethernet 1/1/1
OS10(conf‐if‐eth1/1/1)# no flowcontrol receive
8. Enable PFC mode on the interface that connects to CNA 2.
OS10(config)# interface ethernet 1/1/1
OS10(conf‐if‐eth1/1/1)# priority‐flow‐control mode on
9. Apply the service policy on the interface that connects to CNA 2.
OS10(config)# interface ethernet 1/1/1
OS10(conf‐if‐eth1/1/1)# service‐policy input type network‐qos pmap1
10. Configure the interface that connects to FCF.
OS10(config)# interface fibrechannel 1/1/21
OS10(config-if‐fc1/1/21)# vfabric 2
Support for untagged VLAN in FCoE
In SmartFabric mode, OS10 provides support to use any untagged VLAN for FCoE Ethernet uplinks and Ethernet server ports,
which are part of the FCoE VLAN.
The FCoE uplink identifies FIP Snooping bridge (FSB) mode at the switch. You must configure the same untagged VLAN on the
FCoE uplinks and server ports for the FCoE sessions to come up.
In SmartFabric mode, you can assign any untagged VLAN to Ethernet server ports that belong to a FCoE VLAN that has one or
more FC Gateway uplinks. The FC Gateway uplink identifies N-Port Proxy Gateway (NPG) mode at the switch. Also you can
assign any untagged VLAN to Ethernet server ports that belong to a FCoE VLAN that has one or more FC Direct attach uplinks.
The FC Direct attach uplink identifies F-Port mode at the switch.
Restrictions
● SmartFabric mode does not support multiple FCoE uplinks from the same IOM.
● In FCoE mode, the untagged VLAN on the server port and the FCoE uplink must be the same. This condition ensures that
the untagged FIP VLAN discovery packets in the L2 frame, switch to the untagged VLAN.
● You cannot configure multiple FCoE uplinks corresponding to different untagged VLANs.
Single FCF per vFabric
This feature presents all available operational Fibre Channel uplinks in a fabric as a single logical unit. The uplinks are presented
as one logical Fibre Channel Forwarder (FCF) to the end points connected to the same fabric.
Whenever the first FC uplink becomes operationally up and completes the initial login to upstream switch successfully, the
logical FCF becomes active and is projected to the end devices.
NOTE: This behavior may vary if the you have configured a delay FCF advertisement timer.
The logical FCF must be projected only if there is at least one operationally up FC uplink; this FC uplink must have successfully
completed the initial login with upstream switch at the time of timer expiry. This behavior achieves better load balancing during
boot-up and bulk configuration.
Even though all the uplinks are projected as one FCF, when a request for session establishment is received, the system finds the
optimally loaded FC uplink. The load balancing algorithm makes use of the link's session count and the link speed as factors for
session re-balancing. Session count of the uplink is the count of both Fabric login sessions (FLOGI) and Fabric discovery
sessions (FDISC) in that uplink. Link speed will be the speed of the FC uplinks. End devices do not have control over the link
chosen for session establishment. This behavior ensures better load balancing across the available uplinks. After the session is
established, the FCoE/FC data traffic is re-directed to the appropriate port to which the login request was associated.
486
Fibre Channel