Difference between revisions of "Configuring brocade switch for SAN zoning"

From Notes_Wiki
m
m
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
<yambe:breadcrumb>Switch_configuration_notes|Switch configuration</yambe:breadcrumb>
[[Main Page|Home]] > [[Switch configuration notes]] > [[Configuring brocade switch for SAN zoning]]
=Configure brocade switch for SAN zoning=


Simliar to [[Configuring Cisco MDS 9124 fiber switch for SAN]] configuring brocade switch for SAN can be done in following steps
Simliar to [[Configuring Cisco MDS 9124 fiber switch for SAN]] configuring brocade switch for SAN can be done in following steps
Line 6: Line 5:
# Create zones with all targets and one initiator per zone.
# Create zones with all targets and one initiator per zone.
# Create a configuration (similar to zoneset in case of Cisco) which includes all zones
# Create a configuration (similar to zoneset in case of Cisco) which includes all zones


==Create alias for WWN==
==Create alias for WWN==
To create alias for WWN use:
To create alias for WWN use:
<pre>
<pre>
alicreate "&lt;alias-name&gt;", "&lt;wwn-number&gt;"
alicreate "<alias-name>", "<wwn-number>"
</pre>
</pre>
For example, <tt>alicreate "server2_sw2_port0", "50:00:d3:10:05:01:02:03"</tt>
For example, <tt>alicreate "server2_sw2_port0", "50:00:d3:10:05:01:02:03"</tt>
Line 22: Line 22:
To create zone using aliases use:
To create zone using aliases use:
<pre>
<pre>
zonecreate "&lt;zone-name&gt;", "&lt;alias1&gt;; &lt;alias2&gt;; &lt;alias3&gt;; ... "
zonecreate "<zone-name>", "<alias1>; <alias>; <alias3>; ... "
</pre>
</pre>
Example: <tt>zonecreate "server2_zone", "server2_sw2_port0; storage_port1; storage_port2; storage_port3"</tt>
Example: <tt>zonecreate "server2_zone", "server2_sw2_port0; storage_port1; storage_port2; storage_port3"</tt>
Line 34: Line 34:
To create configuration using zones use:
To create configuration using zones use:
<pre>
<pre>
cfgcreate "&lt;cfg-name&gt;", "&lt;zone1-name&gt;; &lt;zone2-name&gt;; &lt;zone3-name&gt;; ...
cfgcreate "<cfg-name>", "<zone1-name>; <zone2-name>; <zone3-name>; ..."
</pre>
</pre>
Example: <tt>cfgcreate "switch2", "server1_zone; server2_zone; server3_zone ..."</tt>
Example: <tt>cfgcreate "switch2", "server1_zone; server2_zone; server3_zone ..."</tt>
Line 53: Line 53:
To enable configuration (ie apply it on running switch) use:
To enable configuration (ie apply it on running switch) use:
<pre>
<pre>
cfgenable &lt;cfg-name&gt;
cfgenable <cfg-name>
</pre>
</pre>
For example, <tt>cfgenable switch2</tt>
For example, <tt>cfgenable switch2</tt>
Line 68: Line 68:
To see detailed information about port use:
To see detailed information about port use:
<pre>
<pre>
portshow &lt;port-number&gt;
portshow <port-number>
</pre>
</pre>
where &lt;port-number&gt; starts from 0.  For example <tt>portshow 0</tt>.
where &lt;port-number&gt; starts from 0.  For example <tt>portshow 0</tt>.
==Example sequences==
===Example sequence for creating a new zone===
<pre>
switchshow    #OR nsshow to see virtual WWNs
alicreate "ali01", "<wwn>"
zonecreate "zone01", "stor_ali01; stor_ali01; ali01"
cfgadd "cfg01", "zone01"
cfgsave
cfgenable "cfg01"
cfgshow
</pre>
===Example sequence for removing existing zone===
<pre>
cfgshow
cfgremove "cfg01", "zone01"
zonedelete "zone01"
alidelete "ali01"
cfgsave
cfgenable "cfg01"
</pre>
=Using NPIV with brocade switches=
Virtualization hosts often support virtualization of FC HBAs so that LUNs can be mapped directly with VMs.  In case of VMWare it is called Raw Device Mapping and leads to limitation on vMotion, Snapshots, Backup, etc. features.  However, for Hyper-V by using two WWN's apparently even in case of RDM, the VM can be migrated from one host to another - Refer: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831413(v=ws.11)
To use NPIV with brocade switches first validate whether NPIV is enabled at port level or not:
<pre>
portcfgshow <port-number>
</pre>
and validate NPIV Enabled is true / yes
Then to see NPIV WWN use command:
<pre>
nsshow
</pre>
The output would show physical initiator and NPIV initiator differently.
Refer:
* https://www.vmware.com/pdf/vi3_35_25_npiv_config.pdf
Then zoning can be done for VM WWNs similar to the way it is done for physical host.








<yambe:breadcrumb>Switch_configuration_notes|Switch configuration</yambe:breadcrumb>
[[Main Page|Home]] > [[Switch configuration notes]] > [[Configuring brocade switch for SAN zoning]]

Latest revision as of 05:55, 19 April 2022

Home > Switch configuration notes > Configuring brocade switch for SAN zoning

Simliar to Configuring Cisco MDS 9124 fiber switch for SAN configuring brocade switch for SAN can be done in following steps

  1. Configure aliases for all WWNs connected to brocade switch
  2. Create zones with all targets and one initiator per zone.
  3. Create a configuration (similar to zoneset in case of Cisco) which includes all zones


Create alias for WWN

To create alias for WWN use:

alicreate "<alias-name>", "<wwn-number>"

For example, alicreate "server2_sw2_port0", "50:00:d3:10:05:01:02:03"

  • 'alishow' can be used see defined aliases.
  • 'alidelete' can be used to delete defined aliases.


Create zone using aliases

To create zone using aliases use:

zonecreate "<zone-name>", "<alias1>; <alias>; <alias3>; ... "

Example: zonecreate "server2_zone", "server2_sw2_port0; storage_port1; storage_port2; storage_port3"

  • 'zoneshow' can be used to see defined zones.
  • 'zonedelete' can be used to delete defined zones.


Create configuration using zones

To create configuration using zones use:

cfgcreate "<cfg-name>", "<zone1-name>; <zone2-name>; <zone3-name>; ..."

Example: cfgcreate "switch2", "server1_zone; server2_zone; server3_zone ..."

  • 'cfgshow' can be used to see defined configurations.
  • 'cfgdelete' can be used to delete defined configuration.


Save defined configuration

To save defined configuration use:

cfgsave


Enable configuration

To enable configuration (ie apply it on running switch) use:

cfgenable <cfg-name>

For example, cfgenable switch2


List WWN seen by switch

To list all WWN seen by switch use:

switchshow


See detailed port information

To see detailed information about port use:

portshow <port-number>

where <port-number> starts from 0. For example portshow 0.


Example sequences

Example sequence for creating a new zone

switchshow    #OR nsshow to see virtual WWNs
alicreate "ali01", "<wwn>"
zonecreate "zone01", "stor_ali01; stor_ali01; ali01"
cfgadd "cfg01", "zone01"
cfgsave
cfgenable "cfg01"
cfgshow


Example sequence for removing existing zone

cfgshow
cfgremove "cfg01", "zone01"
zonedelete "zone01"
alidelete "ali01"
cfgsave
cfgenable "cfg01"



Using NPIV with brocade switches

Virtualization hosts often support virtualization of FC HBAs so that LUNs can be mapped directly with VMs. In case of VMWare it is called Raw Device Mapping and leads to limitation on vMotion, Snapshots, Backup, etc. features. However, for Hyper-V by using two WWN's apparently even in case of RDM, the VM can be migrated from one host to another - Refer: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831413(v=ws.11)

To use NPIV with brocade switches first validate whether NPIV is enabled at port level or not:

portcfgshow <port-number>

and validate NPIV Enabled is true / yes

Then to see NPIV WWN use command:

nsshow

The output would show physical initiator and NPIV initiator differently.

Refer:


Then zoning can be done for VM WWNs similar to the way it is done for physical host.



Home > Switch configuration notes > Configuring brocade switch for SAN zoning