API Guide

ZoneName ZoneMember
================================================
hba2 *20:01:00:0e:1e:e8:e4:99
20:35:78:2b:cb:6f:65:57
50:00:d3:10:00:ec:f9:05
50:00:d3:10:00:ec:f9:1b
50:00:d3:10:00:ec:f9:1f
hba1 *10:00:00:90:fa:b8:22:19
*21:00:00:24:ff:7b:f5:c8
OS10# show fc zoneset set
ZoneSetName ZoneName ZoneMember
==========================================================
set hba1 21:00:00:24:ff:7b:f5:c8
10:00:00:90:fa:b8:22:19
21:00:00:24:ff:7f:ce:ee
21:00:00:24:ff:7f:ce:ef
hba2 20:01:00:0e:1e:e8:e4:99
50:00:d3:10:00:ec:f9:1b
50:00:d3:10:00:ec:f9:05
50:00:d3:10:00:ec:f9:1f
20:35:78:2b:cb:6f:65:57
F_Port on Ethernet
OS10 supports configuring F_Port mode on an Ethernet port that connects to converged network adapters (CNA). After
enabling F_Port mode, configure a vfabric and apply the vfabric to Ethernet ports connected to CNA. You can configure only
one vfabric in F_Port mode.
You can apply the configured vfabric to multiple Ethernet interfaces. You can also add Ethernet interfaces to a port-channel and
apply the vfabric to the port-channel.
Example configuration
OS10(config)# feature fc domain-id 100
OS10(config)# vfabric 100
OS10(conf-vfabric-100)# name 100
OS10(conf-vfabric-100)# vlan 1023
OS10(conf-vfabric-100)# fcoe fcmap 0xEFC64
OS10(conf-vfabric-100)# zoneset activate set
OS10(conf-vfabric-100)# zone default-zone permit
OS10(conf-vfabric-100)# exit
OS10(config)# interface ethernet 1/1/30
OS10(conf-if-eth1/1/30)# vfabric 100
Pinning FCoE traffic to a specific port of a port-
channel
You can isolate FIP and FCoE traffic by configuring a pinned port at the FCoE LAG.
FCoE LAG is the port-channel used for FIP and FCoE traffic in the intermediate switches between server and storage devices.
VLT provides Active/Active LAN connectivity on converged links by forwarding traffic in multiple paths to multiple upstream
devices without STP blocking any of the uplinks. This works for Ethernet traffic, but FCoE requires dedicated links for each SAN
Fabric. FCoE traffic sent on VLT breaks SAN fabric isolation.
The FC sessions form between FC nodes and FCoE sessions happen between Ethernet nodes.
To form FC or FCoE sessions, the fabric login request and reply must traverse the switch through the same port. The fabric
login request initiated from the server through the switch reaches the SAN Fabric. The login accept response is hashed out to
any of the ports in the port-channel. If the server receives the response on a different port than where the request was sent,
the server keeps retrying the request. Because of this action, the FC or FCoE sessions learnt based on the login accept
Fibre Channel
333