Zoning Illustration of the Change Step by Steps

7/22/2019 Zoning Illustration of the Change Step by Steps

1/27

Zoning illustration of the changes, step by step

Case: Perform a zoning of a server to utilize a netapp clusterred filershared storage and illustration of the changes in the switch

configuration.server: labserver1

switch: sw001

clusternetapp filers: netapp001, netapp002

zoning backup server: 140.190.71.105

zone configuration: Labswitch1

labserver1 wwpn hba0 88:88:88:80:88:88:88:88

labserver1 wwpn hba1 88:88:88:81:88:88:88:88

netapp001/netapp002 wwn: 50:0a:09:80:86:27:c0:87

aliases naming:

a_labserver1_hba0 (servers hba #1)

a_labserver1_hba1 (servers hba#2)

a_netapp001_002 (netapp cluster )

zones naming:

z_netapp001_002_labserver1_a

A. Save the switch parameter to a remote server.

sw001:admin> configupload

Protocol (scp, ftp, local) [ftp]: yes

Server Name or IP Address [host]: 140.190.71.105

User Name [user]: nurledge

File Name [config.txt]: sw001_bkp_june0910

Section (all|chassis [all]): yes

Password:
http://nurledge-storage.blogspot.com/2010/06/zoning-illustration-of-changes-step-by.htmlhttp://nurledge-storage.blogspot.com/2010/06/zoning-illustration-of-changes-step-by.htmlhttp://nurledge-storage.blogspot.com/2010/06/zoning-illustration-of-changes-step-by.html


2/27

configUpload complete: All config parameters are uploaded

Show current configuration status

sw001:admin> cfgshow

Defined configuration:

cfg: Labswitch1

vSpherezone; labfiler

zone: labfiler

10:00:00:00:C9:4C:0D:F1; 50:0A:09:82:86:27:C0:87;

50:0A:09:82:96:27:C0:87

zone: vSpherezone

50:0A:09:82:96:27:C0:87; 50:0A:09:82:86:27:C0:87;

vSphereESXserver

alias: vSphereESXserver

50:01:43:80:00:C1:E7:08

Effective configuration:

cfg: Labswitch1

zone: labfiler

10:00:00:00:c9:4c:0d:f1

50:0a:09:82:86:27:c0:87

50:0a:09:82:96:27:c0:87

zone: vSpherezone

50:0a:09:82:96:27:c0:87

50:0a:09:82:86:27:c0:87

50:01:43:80:00:c1:e7:08

Create aliases and zone


3/27

sw001:admin> alicreate "a_labserver1","88:88:88:80:88:88:88:88"

sw001:admin> alicreate "a_sw001_002","50:0a:09:80:86:27:c0:87"

sw001:admin> zonecreate "z_sw001_002_labserver1_a","a_labserver1;a_sw001_002"

Display current configuration



cfg: Labswitch1

vSpherezone; labfiler

zone: labfiler

10:00:00:00:C9:4C:0D:F1; 50:0A:09:82:86:27:C0:87;

50:0A:09:82:96:27:C0:87

zone: vSpherezone

50:0A:09:82:96:27:C0:87; 50:0A:09:82:86:27:C0:87;

vSphereESXserver

zone: z_sw001_002_labserver1_a

a_labserver1; a_sw001_002

alias: a_labserver1

88:88:88:80:88:88:88:88

alias: a_sw001_002

50:0a:09:80:86:27:c0:87


50:01:43:80:00:C1:E7:08


cfg: Labswitch1

zone: labfiler


4/27

10:00:00:00:c9:4c:0d:f1

50:0a:09:82:86:27:c0:87

50:0a:09:82:96:27:c0:87

zone: vSpherezone

50:0a:09:82:96:27:c0:87

50:0a:09:82:86:27:c0:87

50:01:43:80:00:c1:e7:08

Notice; the change is only appear under aliases and zoning.

Add the zone to the zone configuration

sw001:admin> cfgadd "Labswitch1","z_sw001_002_labserver1_a"



cfg: Labswitch1

vSpherezone; labfiler; z_sw001_002_labserver1_a

zone: labfiler

10:00:00:00:C9:4C:0D:F1; 50:0A:09:82:86:27:C0:87;

50:0A:09:82:96:27:C0:87

zone: vSpherezone

50:0A:09:82:96:27:C0:87; 50:0A:09:82:86:27:C0:87;

vSphereESXserver



alias: a_labserver1

88:88:88:80:88:88:88:88

alias: a_sw001_002


5/27

50:0a:09:80:86:27:c0:87


50:01:43:80:00:C1:E7:08


cfg: Labswitch1

zone: labfiler

10:00:00:00:c9:4c:0d:f1

50:0a:09:82:86:27:c0:87

50:0a:09:82:96:27:c0:87

zone: vSpherezone

50:0a:09:82:96:27:c0:87

50:0a:09:82:86:27:c0:87

50:01:43:80:00:c1:e7:08

Notice the zone now appear in defined zone configuration but not under effective configuration.

Enable the zoning

sw001:admin> cfgenable "Labswitch1"

You are about to enable a new zoning configuration.

This action will replace the old zoning configuration with the

current configuration selected. If the update includes changes

to one or more traffic isolation zones, the update may result in

localized disruption to traffic on ports associated with

the traffic isolation zone changes

Do you want to enable 'Labswitch1' configuration (yes, y, no, n): [no] yes

zone config "Labswitch1" is in effect

Updating flash ...


6/27



cfg: Labswitch1

vSpherezone; labfiler; Backuptest; Unix_Server;

z_sw001_002_labserver1_a

zone: labfiler

10:00:00:00:C9:4C:0D:F1; 50:0A:09:82:86:27:C0:87;

50:0A:09:82:96:27:C0:87

zone: vSpherezone

50:0A:09:82:96:27:C0:87; 50:0A:09:82:86:27:C0:87;

vSphereESXserver



alias: a_labserver1

88:88:88:80:88:88:88:88

alias: a_sw001_002

50:0a:09:80:86:27:c0:87


50:01:43:80:00:C1:E7:08


cfg: Labswitch1

zone: labfiler

10:00:00:00:c9:4c:0d:f1

50:0a:09:82:86:27:c0:87

50:0a:09:82:96:27:c0:87


7/27

zone: vSpherezone

50:0a:09:82:96:27:c0:87

50:0a:09:82:86:27:c0:87

50:01:43:80:00:c1:e7:08


88:88:88:80:88:88:88:88

50:0a:09:80:86:27:c0:87

Notice the zone is now also appeared in effective configuration.

Step to undo the zoning

sw001:admin> cfgremove "Labswitch1","z_sw001_002_labserver1_a"



cfg: Labswitch1

vSpherezone; labfiler;

zone: labfiler

10:00:00:00:C9:4C:0D:F1; 50:0A:09:82:86:27:C0:87;

50:0A:09:82:96:27:C0:87

zone: vSpherezone

50:0A:09:82:96:27:C0:87; 50:0A:09:82:86:27:C0:87;

vSphereESXserver



alias: a_labserver1

88:88:88:80:88:88:88:88

alias: a_sw001_002


8/27

50:0a:09:80:86:27:c0:87


50:01:43:80:00:C1:E7:08


cfg: Labswitch1

zone: labfiler

10:00:00:00:c9:4c:0d:f1

50:0a:09:82:86:27:c0:87

50:0a:09:82:96:27:c0:87

zone: vSpherezone

50:0a:09:82:96:27:c0:87

50:0a:09:82:86:27:c0:87

50:01:43:80:00:c1:e7:08


88:88:88:80:88:88:88:88

50:0a:09:80:86:27:c0:87

Notice the zone definition disappeared from defined configuration only.

sw001:admin> cfgenable "Labswitch1"

You are about to enable a new zoning configuration.

This action will replace the old zoning configuration with the

current configuration selected. If the update includes changes

to one or more traffic isolation zones, the update may result in

localized disruption to traffic on ports associated with

the traffic isolation zone changes

Do you want to enable 'Labswitch1' configuration (yes, y, no, n): [no] yes


9/27

zone config "Labswitch1" is in effect

Updating flash ...



cfg: Labswitch1

vSpherezone; labfiler; Backuptest; Unix_Server

zone: labfiler

10:00:00:00:C9:4C:0D:F1; 50:0A:09:82:86:27:C0:87;

50:0A:09:82:96:27:C0:87

zone: vSpherezone

50:0A:09:82:96:27:C0:87; 50:0A:09:82:86:27:C0:87;

vSphereESXserver



alias: a_labserver1

88:88:88:80:88:88:88:88

alias: a_sw001_002

50:0a:09:80:86:27:c0:87


50:01:43:80:00:C1:E7:08


cfg: Labswitch1

zone: labfiler

10:00:00:00:c9:4c:0d:f1

50:0a:09:82:86:27:c0:87


10/27

50:0a:09:82:96:27:c0:87

zone: vSpherezone

50:0a:09:82:96:27:c0:87

50:0a:09:82:86:27:c0:87

50:01:43:80:00:c1:e7:08

Notice the zone is no longer appears in defined and effective configuration

Delete the zone, aliases

sw001:admin> zonedelete "z_sw001_002_labserver1_a"

sw001:admin> alidelete "a_labserver1"

sw001:admin> alidelete a_sw001_002



cfg: Labswitch1

vSpherezone; labfiler;

zone: labfiler

10:00:00:00:C9:4C:0D:F1; 50:0A:09:82:86:27:C0:87;

50:0A:09:82:96:27:C0:87

zone: vSpherezone

50:0A:09:82:96:27:C0:87; 50:0A:09:82:86:27:C0:87;

vSphereESXserver


50:01:43:80:00:C1:E7:08


cfg: Labswitch1

zone: labfiler


11/27

10:00:00:00:c9:4c:0d:f1

50:0a:09:82:86:27:c0:87

50:0a:09:82:96:27:c0:87

zone: vSpherezone

50:0a:09:82:96:27:c0:87

50:0a:09:82:86:27:c0:87

50:01:43:80:00:c1:e7:08

The configuration is restored to the original form.

Posted byabu maryam at6:43 AMNo comments:

Labels:brocade

saving zoning parametersBefore making any change to a switch configuration, it is good practice to save theinformation i.e parameters to a diffent location i.e. a server.

Identify the server which you re going to upload the configuration and typeconfigupload.

ab001:admin> configuploadProtocol (scp, ftp, local) [ftp]:

Server Name or IP Address [host]: 140.199.72.100User Name [user]: nurledgeFile Name [config.txt]: lab001_bkp_june10Section (allchassis [all]):Password:configUpload complete: All config parameters are uploadedlab001:admin>

To restore the configuration from the backup you made; use commandconfigdownload.

Posted byabu maryam at12:40 AMNo comments:Labels:brocade

Comons CLI commands used to administer Brocade ZoningComons CLI commands used to administer Brocade Zoning.

Zone Alias
http://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/zoning-illustration-of-changes-step-by.htmlhttp://nurledge-storage.blogspot.com/2010/06/zoning-illustration-of-changes-step-by.htmlhttp://nurledge-storage.blogspot.com/2010/06/zoning-illustration-of-changes-step-by.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/zoning-illustration-of-changes-step-by.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/saving-zoning-parameters.htmlhttp://nurledge-storage.blogspot.com/2010/06/saving-zoning-parameters.htmlhttp://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/saving-zoning-parameters.htmlhttp://nurledge-storage.blogspot.com/2010/06/saving-zoning-parameters.htmlhttp://nurledge-storage.blogspot.com/2010/06/saving-zoning-parameters.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/saving-zoning-parameters.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/comons-cli-commands-used-to-administer.htmlhttp://nurledge-storage.blogspot.com/2010/06/comons-cli-commands-used-to-administer.htmlhttp://nurledge-storage.blogspot.com/2010/06/comons-cli-commands-used-to-administer.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/saving-zoning-parameters.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/saving-zoning-parameters.htmlhttp://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/saving-zoning-parameters.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/zoning-illustration-of-changes-step-by.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/zoning-illustration-of-changes-step-by.htmlhttp://www.blogger.com/profile/10136011519775536047


12/27

aliAdd -Add a member to a zone alias.aliCreate -Create a zone alias.aliDelete -Delete a zone alias.aliRemove -Remove a member from a zone alias.aliShow -Show zone alias definition.

ZoningzoneAdd -Add a member to a zone.zoneCreate -Create a zone.zoneDelete -Delete a zone.zoneRemove -Remove a member from a zone.zoneShow -Show zone information.

QuickLoop ZoningqloopAdd -Add a member to a QuickLoop.qloopCreate -Create a QuickLoop.

qloopDelete -Delete a QuickLoop.qloopRemove -Remove a member from a QuickLoop.qloopShow -Show QuickLoop information.

Zone ConfigurationcfgAdd -Add a zone to a zone configuration.cfgCreate -Create a zone configuration.cfgDelete -Delete a zone configuration.cfgRemove -Remove a zone from a zone configuration.cfgShow -Show zone configuration definition.

Configuration ManagementcfgClear -Clear all zone configurations.cfgDisable -Disable a zone configuration.cfgEnable -Enable a zone configuration.cfgSave -Save zone configurations in flash memory.cfgShow -Show zone configuration definition.cfgTransAbort -Abort the current zoning transaction.Posted byabu maryam at12:28 AMNo comments:Labels:brocade

Zoning Steps

Zoning Steps:

1. Create alias (this step is optional)2. Define zone3. Define zone configuration4. Enable zone configuration

1. Create alias (this step is optional)
http://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/comons-cli-commands-used-to-administer.htmlhttp://nurledge-storage.blogspot.com/2010/06/comons-cli-commands-used-to-administer.htmlhttp://nurledge-storage.blogspot.com/2010/06/comons-cli-commands-used-to-administer.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/comons-cli-commands-used-to-administer.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/zoning-steps.htmlhttp://nurledge-storage.blogspot.com/2010/06/zoning-steps.htmlhttp://nurledge-storage.blogspot.com/2010/06/zoning-steps.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/comons-cli-commands-used-to-administer.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/comons-cli-commands-used-to-administer.htmlhttp://www.blogger.com/profile/10136011519775536047


13/27

An alias is a name assigned to a device or group of devices. By creating an alias youcan assigna familiar name to a device, or you can group multiple devices into a single name.

An alias must be a unique alpha-numeric string beginning with an alpha character. Theunderscore character ( _ ) is allowed and alias names are case sensitive

Aliases can greatly simplify the administrative process; however, they are not requiredtodefine zones.

i.e alicreate "a_host1_hba0","50:06:0b:00:00:bc:be:22"

or alicreate "a_host1_hba1","1,2"

2. Define zone

A zone is a group of devices that can communicate with each other. Zone membershipcaninclude ports, WWNs, or aliases, or any combination of these. And, a device can beincluded inmore than one zone.

To define a zone, specify the list of members to be included and assign a unique zonename;the zone name must be a unique alpha-numeric string beginning with an alphacharacter.

i.e. zonecreate z_aixhosts","a_aix01;a_aix02;a_aix03;10:00:00:60:69:00:00:8a;1,2"

3. Define Zone Configuration

A zone configuration is a group of zones that are enforced whenever that zoneconfiguration isenabled. And, a zone can be included in more than one zone configuration.

To define a zone configuration, specify the list of zones to be included and assign azoneconfiguration name; the zone configuration name must be a unique alpha-numeric stringbeginning with an alpha character.

i.e cfgadd "production1","z_aixhosts"

4. Enable zone configuration


14/27

To enable a zone configuration, select the zone configuration to be enabled. Theconfigurationis downloaded to the switch hardware.

i.e cfgenable production1

note: use cfgsave to save the modified zone configuration. i.e. cfgsavePosted byabu maryam at12:08 AMNo comments:Labels:brocade

Tuesday, June 8, 2010

Specify alias by portTo specify by port number, you must specify switch domain ID and port number, forexample, 2,12 indicates switch domain ID 2, port number 12. When a member is

specified by port number all devices connected to the port are included in the zone.

i.e

admin> aliCreate "A_ServerA_hba0", "1,3"admin> aliCreate "A_ServerA_hba1, "2,3"Posted byabu maryam at7:29 PMNo comments:Labels:brocade

identify principle from fabrichow command

Look for ">"; that's mr Principle

switch:admin> fabricShowSwitch ID Worldwide Name Enet IP Addr FC IP Addr Name-------------------------------------------------------------------------0: fffc40 10:00:00:60:69:00:06:56 192.168.64.59 192.168.65.59 "sw5"1: fffc41 10:00:00:60:69:00:02:0b 192.168.64.180 192.168.65.180>"sw180"2: fffc42 10:00:00:60:69:00:05:91 192.168.64.60 192.168.65.60 "sw60"3: fffc43 10:00:00:60:69:10:60:1f 192.168.64.187 0.0.0.0 "sw187"The Fabric has 4 switchesGroup ID Token

-----------------0: fffb01 40:05:00:00:10:00:00:60:69:00:00:15Posted byabu maryam at9:45 AMNo comments:Labels:brocade

Checklist power down/up a FabricChecklist for Initial Bring UpDetermine the topology of your system. Determine which are the core
http://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/zoning-steps.htmlhttp://nurledge-storage.blogspot.com/2010/06/zoning-steps.htmlhttp://nurledge-storage.blogspot.com/2010/06/zoning-steps.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/zoning-steps.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/specify-alias-by-port.htmlhttp://nurledge-storage.blogspot.com/2010/06/specify-alias-by-port.htmlhttp://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/specify-alias-by-port.htmlhttp://nurledge-storage.blogspot.com/2010/06/specify-alias-by-port.htmlhttp://nurledge-storage.blogspot.com/2010/06/specify-alias-by-port.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/specify-alias-by-port.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/identify-principle-from-fabrichow.htmlhttp://nurledge-storage.blogspot.com/2010/06/identify-principle-from-fabrichow.htmlhttp://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/identify-principle-from-fabrichow.htmlhttp://nurledge-storage.blogspot.com/2010/06/identify-principle-from-fabrichow.htmlhttp://nurledge-storage.blogspot.com/2010/06/identify-principle-from-fabrichow.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/identify-principle-from-fabrichow.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/checklist-power-downup-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/checklist-power-downup-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/checklist-power-downup-fabric.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/identify-principle-from-fabrichow.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/identify-principle-from-fabrichow.htmlhttp://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/identify-principle-from-fabrichow.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/specify-alias-by-port.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/specify-alias-by-port.htmlhttp://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/specify-alias-by-port.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/zoning-steps.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/zoning-steps.htmlhttp://www.blogger.com/profile/10136011519775536047


15/27

switches and which are the edge switches.Power on each switch and verify the POST completes successfully.Set the IP addresses on each switch.Run diagnostic tests on each switch to verify hardware (optional).Upgrade the firmware and install software licenses on each switch.

Configure the fabric parameters and software features.Reboot and verify each switch.Connect ISLs to form a large fabric.Verify the fabric configuration.Power on the storage devices.Power on the host devices.Verify the SAN.

Checklist for Recovering from Power FailureMake sure all switches and devices are powered off.Power on the core switches.

Power on the first edge switch.Power on the remaining edge switches.Verify the fabric configuration.Power on the storage devices.Power on the host devices.Verify the SAN.Posted byabu maryam at9:13 AMNo comments:Labels:brocade

Shutting Down & Powering up a FabricShutting Down the Fabric

Perform the following steps to successfully shut down the fabric:1. Shut down all host devices.2. Shut down all storage devices.3. Shut down all edge switches.4. Shut down all core switches.

Bringing up steps:

1. Make sure all switches and devices are powered off.

2. Power on the fabric:a. Power on the core switches.b. Power on the first edge switch to merge the core switches and the edge switch asone fabric.c. Power on the remaining edge switches.3. Verify the fabric configuration.4. Power on the devices:a. Power on or connect the storage devices.
http://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/checklist-power-downup-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/checklist-power-downup-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/checklist-power-downup-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/checklist-power-downup-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/shutting-down-powering-up-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/shutting-down-powering-up-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/shutting-down-powering-up-fabric.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/checklist-power-downup-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/checklist-power-downup-fabric.htmlhttp://www.blogger.com/profile/10136011519775536047


16/27

b. Power on or connect the host devices.5. Verify the SAN.Posted byabu maryam at9:04 AMNo comments:Labels:brocade

High level Steps To Create a SAN Fabric1. Determine the fabric topology.2. Power on each switch, and go through the Power-On Self-Test (POST).3. Configure each switch:a. Configure each switch for network access.b. Run diagnostic tests to verify hardware.c. Upgrade the firmware and install software licenses.d. Configure the fabric parameters and software features.4. Reboot each switch and then verify the switch configuration.5. Connect ISLs to form a large fabric.6. Verify the fabric configuration.7. Load the desired zoning configuration onto the fabric.8. Connect devices to the fabric.9. Power on the devices:a. Power on or enable the storage devices.b. Power on or enable the host devices.10. Verify the SAN.Posted byabu maryam at6:42 AMNo comments:Labels:brocade

single vs dual fabric

Dual Fabrics

For mission critical applications, Brocade strongly recommends that you install a dualfabric, which allows you to upgrade each fabric separately with no loss of service(provided that you have configured failover software).For example, to upgrade the dual fabric shown in the picture, you first upgrade Fabric 1by deactivating the link from the host to Fabric 1. The host continues to access the data
http://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/shutting-down-powering-up-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/shutting-down-powering-up-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/shutting-down-powering-up-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/shutting-down-powering-up-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/high-level-steps-to-create-san-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/high-level-steps-to-create-san-fabric.htmlhttp://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/high-level-steps-to-create-san-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/high-level-steps-to-create-san-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/high-level-steps-to-create-san-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/high-level-steps-to-create-san-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/single-vs-dual-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/single-vs-dual-fabric.htmlhttp://3.bp.blogspot.com/_0I_uthM9dc4/TA5HxAGa3OI/AAAAAAAAAAs/xQnrUcVrZxg/s1600/dual_fab.bmphttp://nurledge-storage.blogspot.com/2010/06/single-vs-dual-fabric.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/high-level-steps-to-create-san-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/high-level-steps-to-create-san-fabric.htmlhttp://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/high-level-steps-to-create-san-fabric.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/shutting-down-powering-up-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/shutting-down-powering-up-fabric.htmlhttp://www.blogger.com/profile/10136011519775536047


17/27

through Fabric

2. After Fabric 1 is upgraded, reconnect the host to Fabric 1, disconnect the link fromthe host to Fabric 2, and upgrade Fabric 2.Posted byabu maryam at6:35 AMNo comments:

Labels:brocade

SAN terminology

Posted byabu maryam at6:30 AMNo comments:Labels:brocade

How to merge two Brocade fabricsHow to merge two Brocade fabrics

Author DetailsAuthor: NetworkAdminKB.comCreated: 2009-04-02Modified: 2009-06-02Article Content

Information:
http://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/single-vs-dual-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/single-vs-dual-fabric.htmlhttp://nurledge-storage.blogspot.com/2010/06/single-vs-dual-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/single-vs-dual-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/san-terminology.htmlhttp://nurledge-storage.blogspot.com/2010/06/san-terminology.htmlhttp://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/san-terminology.htmlhttp://nurledge-storage.blogspot.com/2010/06/san-terminology.htmlhttp://nurledge-storage.blogspot.com/2010/06/san-terminology.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/san-terminology.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/how-to-merge-two-brocade-fabrics.htmlhttp://nurledge-storage.blogspot.com/2010/06/how-to-merge-two-brocade-fabrics.htmlhttp://2.bp.blogspot.com/_0I_uthM9dc4/TA5GMvLDqWI/AAAAAAAAAAk/RGjgep3MRAc/s1600/san_term.bmphttp://nurledge-storage.blogspot.com/2010/06/how-to-merge-two-brocade-fabrics.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/san-terminology.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/san-terminology.htmlhttp://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/san-terminology.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/single-vs-dual-fabric.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/single-vs-dual-fabric.htmlhttp://www.blogger.com/profile/10136011519775536047


18/27

Basic fabric merges arent very difficult from a technical stand point. However, manynetwork administrators fail to do the proper research up front and therefore run intoissues that can easily be avoided. To make sure the merge is successful administratorsshould focus on keeping things simple and avoid doing to much during the mergeprocess. Then after the merge is successful go back and add any additional

configuration needed to handle load and fault tolerance.

Below are the basic steps and research you need to do in order to perform a basicmerge of two Brocade fabrics. A basic fabric merge consists of the followingassumptions

* No long distance ISLs are involved.* Only one ISL between each switch will be implemented (no Trunking).* No advance configuration of the switches.

* All Switches are from the same vendor (Brocade in this case).

Research and Preliminary Steps

1) Verify root and admin level userids and password for all switches.

2) Verify support agreements are in place should you need help with an issue.

3) Check that the Brocade Fabric License is installed on all Switches

a. This is also called the Full Fabric License

b. Order and install license if not already installed.

4) Upgrade the Fabric OS (aka: Switch Firmware, or FOS) as needed on every switch tomeet all the following requirements:

a. Compatibility with all Storage Arrays

i. Check with your vendor

b. Compatibility with all HBA drivers, BIOS, firmware, etc.

i. Check with your vendor

c. Compatibility with other Fabric OSs

i. Check with your switch vendor (Brocade or your reseller)

ii. In general try to get the same Fabric OS installed on all switches. If not exactly the


19/27

same they need to be within the same major version level and possibly the minor oneas well.

1. Version 5.3.0c = major.minor.revision

5) Check Domain IDs of all Switches

a. In a Fabric no two switches can have the same Domain ID. Find and correct anyissues now, or plan to correct the Domain ID issue during the merge.

6) Check Zone and Alias Names

a. Zone and Alias Names cannot be duplicated between the two fabrics. Find andcorrect any duplicate zone or alieas names. A simple solution to this issue is to prefix allnames with a fabric label (fabA_, fabB_, etc.)

7) Check for duplicate IP addresses assigned to the switches.

a. Most director class FC switches have multiple IPs so check them all.

8) Check for incompatible Fabric Parameters on the switches to be merged.

a. Use the configshow command and compare values of all fabric.xxxx parameters

b. Verify that all RA_TOV and ED_TOV values are the same on every switch. Per theFC-SW2 standard, these values must be the same on each switch within the fabric.

c. This issue and other advance settings issues are very rare. Basically if you haveimplemented advanced settings on your switches you should know and understandthose settings. If you are using the default settings of the switch you can generallyassume the settings are compatible.

Planning Phase

1) Plan your Principal Switch for the fabric

a. You should not allow the fabric to determine the Principal Switch because all fabricchanges (Zone Changes) should occur at the Principal Switch. This switch should bethe most highly available switch in the fabric.

2) Plan your fabric type

a. The type of fabric being created (Full Mesh or Core-Edge) really doesnt matter forthe merge, but you need to know this to properly plan for your ISLs.


20/27

3) Plan your ISLs

a. Plan which ports will be ISLs

4) Plan any server or storage moves as needed.

a. Minimize these and/or perform them a few days after a successful merge.

5) Determine zone merge method

a. The easiest Zone Merge is to determine which Fabric (Zone Config) will be used asthe foundation to the new Fabric, and disable Zoning on the switches in the other fabric.

i. This is advantageous if you have single switch fabrics.

ii. When you Disable Zoning all existing Zone configurations will be merged, butdisabled.

iii. This choice of which Zone Config to keep should match with the Principal Switchchoice made earlier.

b. The other (more difficult) method is to manually export all Zone Configurationinformation from each Fabric and import it into the other. Then you will need to namethe Zone Configs in both Fabrics to the same name and verify that all the zoneconfiguration information matches.

6) Order Port Licenses and Fiber cables as needed to perform your merge.

Implementation Phase for Disable Zoning Merge Method

1) Shutdown all servers on the fabric that is to be merged.

2) Disable Zoning on the Principal Switch of the fabric that is to be merged.

a. This should be enough to disable zoning on the whole fabric, if not then DisableZoning on every switch in the fabric that is to be merged.

3) Connect ONE ISL from one merged fabric switch to the target fabric.

a. Use the Brocade Web Interface on the target fabric switch to monitor to the merge.

b. If switches become segmented review the Switch Events for errors and attempt


21/27


22/27

When zoning is disabled, the fabric is in non-zoning state and devices can access otherdevices in the fabric. When zoning is enabled, zoning is enforced throughout the fabricand devices can communicate only within their zones.A switch can maintain any number of zone configurations; however, only one zoneconfiguration can be enabled, or enforced, at a time.

Because multiple configurations reside in the switch, you can switch from oneconfiguration to another as events dictate. For example, you can set up a prespecifiedzone configuration to be enabled at certain times of the day; or, in the event of adisaster, you can quickly enable a defined configuration to implement your disasterpolicy. Zone configurations can be:

Defined

This is the complete set of all zone objects that have been defined in thefabric. When zone objects are defined, the information initially resides in

RAM; it must be saved to ensure that it is saved to flash memory and is notlost during power down or when a new zone configuration is enabled.Changes replicate to all switches in the fabric whenever the zoneinformation is changed. However, changes must be saved to flash memory tobe committed to persistent store (that is, to remain across reboot).

Enabled

This is the zone configuration that is enabled (active). It resides in RAM; itmust be saved to ensure that it is not lost when a new configuration isenabled or during power down. Any changes replicate to all switches in thefabric when the configuration is enabled or saved. Use the cfgEnablecommand to: enable a zone configuration, initiate cfgSave, and propagatezoning throughout the fabric.

Disabled

Use the cfgDisable command to: disable a zoning configuration, initiatecfgSave to save the zoning configuration to the flash, and to propagate thezoning configuration throughout the fabric.

Saved

This is the zone configuration that was last saved. It resides in flash memoryand it is persistent.

Saving a Zone Configuration (refer to the picture)

When it is defined, it resides only in RAM. To transfer


23/27

it to flash memory, to be permanently stored and accessible across reboots, it must besaved. This can be accomplished by either: Saving it directly to flash (the recommended method) Enabling it first, then it is saved to flash.But, until it has been saved to flash, it is not permanently stored and available across

reboots.

Note: Only the enabled configuration (in the shaded area) is enforced.Posted byabu maryam at4:21 AMNo comments:Labels:brocade

Hard Zoning or Soft ZoningZone Types

Zones can be hard (hardware enforced) or soft (advisory).

In a hard zone, sometimes referred to as a port zone, zone members are specified byphysical port number. In a soft zone, at least one zone member is specified logically byWorld Wide Name (WWN).

Hard Zones In a hard zone, all zone members are specified as switch ports; anynumberof ports in the fabric can be configured to the zone. When a zone member isspecified by port number, only the individual device port specified isincluded in the zone.

Hard zones are position-dependent, that is, a device is identified by the

physical port to which it is connected. Switch hardware ensures that there isno data transfer between unauthorized zone members. However, devices cantransfer data between ports within the same zone. Consequently, hard zoningprovides the greatest security possible. Use it where security must be rigidlyenforced.

Soft ZonesIn a soft zone, at least one zone member is specified by WWN. A device isincluded in a zone if either the node WWN or port WWN specified matchesan entry in the name server table.

When a device logs in, it queries the name server for devices within the

fabric. If zoning is in effect, only the devices in the same zone(s) arereturned. Other devices are hidden from the name server query reply. Whena WWN is specified, all ports on the specified device are included in thezone.

Soft zones are name server-dependent and therefore provide more flexibility- new devices can be attached without regard to physical location. However,
http://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/zone-enforcement.htmlhttp://nurledge-storage.blogspot.com/2010/06/zone-enforcement.htmlhttp://nurledge-storage.blogspot.com/2010/06/zone-enforcement.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/zone-enforcement.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/hard-zoning-or-soft-zoning.htmlhttp://nurledge-storage.blogspot.com/2010/06/hard-zoning-or-soft-zoning.htmlhttp://nurledge-storage.blogspot.com/2010/06/hard-zoning-or-soft-zoning.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/zone-enforcement.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/zone-enforcement.htmlhttp://www.blogger.com/profile/10136011519775536047


24/27

the switch does not control data transfer so there is no guarantee against datatransfer from unauthorized zone members. Use soft zoning where flexibilityis important and security can be ensured by the cooperating hosts.

In addition to hard and soft zones, a third type of zone is also available:

Broadcast ZoneOnly one broadcast zone can exist within a fabric. It is namedbroadcast and it is used to specify those nodes that are to receive broadcast traffic.

This type of zone is hardware enforced; the switch controls data transfer to aport.Posted byabu maryam at2:40 AMNo comments:Labels:brocade

Monday, May 31, 2010

Usefull Brocade Switch commands

Brocase switchesSome Usefull Brocade Switch commands

aliadd Add a member to a zone aliasalicreate Create a zone alias

alidelete Delete a zone aliasaliremove Remove a member from a zone aliasalishow Print zone alias information

cfgadd Add a member to a configuration

cfgclear Clear all zone configurationscfgcreate Create a zone configurationcfgdelete Delete a zone configuration

cfgdisable Disable a zone configurationcfgenable Enable a zone configuration

cfgremove Remove a member from a configurationcfgsave Save zone configurations in flashcfgshow Print zone configuration information

cfgsize Print size details of zone databasecfgtransabort Abort zone configuration transaction

cfgtransshow Print zone configurations in transaction buffer

fabportshow Display contents of a particular port's data

fabricshow Print fabric membership infofabstateclear Clears the fabric state information

fabstateshow Displays the fabric state informationfabstatsshow Displays the fabric statistics informationfabswitchshow Display fabric switch state information

nsaliasshow Display local Name Server information with Aliases

nsallshow Print global Name Server informationnscamshow Print local Name Server Cache information

nsshow Print local Name Server information information
http://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/06/hard-zoning-or-soft-zoning.htmlhttp://nurledge-storage.blogspot.com/2010/06/hard-zoning-or-soft-zoning.htmlhttp://nurledge-storage.blogspot.com/2010/06/hard-zoning-or-soft-zoning.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/hard-zoning-or-soft-zoning.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/05/usefull-brocade-switch-commands.htmlhttp://nurledge-storage.blogspot.com/2010/05/usefull-brocade-switch-commands.htmlhttp://nurledge-storage.blogspot.com/2010/05/usefull-brocade-switch-commands.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/06/hard-zoning-or-soft-zoning.html#comment-formhttp://nurledge-storage.blogspot.com/2010/06/hard-zoning-or-soft-zoning.htmlhttp://www.blogger.com/profile/10136011519775536047


25/27

nszonemember Display the information of all the online devices

switchshow Print switch and port statusswitchuptime Displays the amount of time for which the switch

is up

portdisable Disable a specified port

portenable Enable a specified port

zoneadd Add a member to a zonezonecreate Create a zonezonedelete Delete a zone

zonehelp Print zoning help info

zoneremove Remove a member from a zone

zoneshow Print zone information

Posted byabu maryam at10:03 PMNo comments:Labels:brocade

how to do zoning

Cookbook to create a zone and add it to a config01. Create the alias for the Device WWNs

swd77:admin> alicreate "ET_CM0_CA0_P1", "21:40:00:0b:5d:6a:05:82"swd77:admin> alicreate "test1_fcd0", "50:01:43:80:03:3a:86:ca"

02. Create a new zone called test1

swd77:admin> zonecreate "test1", "ET_CM0_CA0_P0;test1_fcd0"

03. Add the zone to SAN0 config

swd77:admin> cfgadd "SAN0", "test31"

04. Save the zone to flash memeory

swd77:admin> cfgsave

05. Enable the modified configuration

swd77:admin> cfgenable SAN0

06. Verify the zone

swd77:admin> zoneshow

Defined configuration:cfg: SAN0 aembwpd1; aemtest3

zone: aembwpd1Aembwpd1_P0; ET_CM0_CA0_P0

zone: test1

ET_CM0_CA0_P0; aemtest3_fcd0alias: Aembwpd1_P0

50:01:43:80:02:9a:92:f0alias: ET_CM0_CA0_P0

20:40:00:0b:5d:6a:05:82

alias: ET_CM0_CA0_P121:40:00:0b:5d:6a:05:82
http://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/05/usefull-brocade-switch-commands.htmlhttp://nurledge-storage.blogspot.com/2010/05/usefull-brocade-switch-commands.htmlhttp://nurledge-storage.blogspot.com/2010/05/usefull-brocade-switch-commands.html#comment-formhttp://nurledge-storage.blogspot.com/2010/05/usefull-brocade-switch-commands.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/05/how-to-do-zoning.htmlhttp://nurledge-storage.blogspot.com/2010/05/how-to-do-zoning.htmlhttp://nurledge-storage.blogspot.com/2010/05/how-to-do-zoning.htmlhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/05/usefull-brocade-switch-commands.html#comment-formhttp://nurledge-storage.blogspot.com/2010/05/usefull-brocade-switch-commands.htmlhttp://www.blogger.com/profile/10136011519775536047


26/27

alias: test1_fcd0

50:01:43:80:03:3a:86:ca


cfg: SAN0zone: aembwpd1

50:01:43:80:02:9a:92:f0

20:40:00:0b:5d:6a:05:82zone: test1

20:40:00:0b:5d:6a:05:8250:01:43:80:03:3a:86:ca

switchshowcommand

switchshow [-portcount | -iscsi]

swd77:admin> switchshow -portcount

FC ports = 24

swd77:admin> switchshow

switchName: swd77

switchType: 71.2switchState: OnlineswitchMode: Native

switchRole: Principal

switchDomain: 1switchId: fffc01

switchWwn: 10:00:00:05:1e:9b:db:72zoning: ON (SAN0)switchBeacon: OFF

Area Port Media Speed State Proto

=====================================0 0 id N4 Online F-Port 50:01:43:80:02:9a:92:f0

1 1 id N4 Online F-Port 50:01:43:80:02:9a:92:4c2 2 id N4 Online F-Port 50:01:43:80:03:3a:86:ca3 3 id N4 No_Light

4 4 id N4 No_Light5 5 id N4 No_Light6 6 id N4 No_Light

7 7 id N4 Online F-Port 20:40:00:0b:5d:6a:05:828 8 id N4 No_Light

9 9 id N4 No_Light10 10 id N4 No_Light11 11 id N4 No_Light

12 12 id N4 No_Light



15 15 id N4 Online F-Port 21:40:00:0b:5d:6a:05:8216 16 -- N8 No_Module (No POD License) Disabled

17 17 -- N8 No_Module (No POD License) Disabled18 18 -- N8 No_Module (No POD License) Disabled

19 19 -- N8 No_Module (No POD License) Disabled20 20 -- N8 No_Module (No POD License) Disabled21 21 -- N8 No_Module (No POD License) Disabled

22 22 -- N8 No_Module (No POD License) Disabled23 23 -- N8 No_Module (No POD License) Disabled


27/27

To delete an alias

Switch1:admin> alidelete "test1_fcd0"

To Delete a Zone

Switch1:admin> zonedelete "test01"

To remove test4 zone from configuration SAN1

Switch2:admin> cfgremove "SAN1", "test4"

Posted byabu maryam at10:01 PMNo comments:Labels:brocade
http://www.blogger.com/profile/10136011519775536047http://www.blogger.com/profile/10136011519775536047http://nurledge-storage.blogspot.com/2010/05/how-to-do-zoning.htmlhttp://nurledge-storage.blogspot.com/2010/05/how-to-do-zoning.htmlhttp://nurledge-storage.blogspot.com/2010/05/how-to-do-zoning.html#comment-formhttp://nurledge-storage.blogspot.com/2010/05/how-to-do-zoning.html#comment-formhttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/search/label/brocadehttp://nurledge-storage.blogspot.com/2010/05/how-to-do-zoning.html#comment-formhttp://nurledge-storage.blogspot.com/2010/05/how-to-do-zoning.htmlhttp://www.blogger.com/profile/10136011519775536047

Documents

Zoning Illustration of the Change Step by Steps