Zone Configuration of Brocade

Zone Configuration of Brocade explains how zoning is used to control communication between hosts and storage in a SAN.
This lesson covers zoning concepts, types, and the steps to configure zones safely on Brocade switches.

Types-of-configuration

Objects of a Zone

  • Members: WWN (World Wide Name) numbers of HBAs (Host Bus Adapters), disks, and storage subsystems are given alias names called members.
  • Zones: A combination of multiple members is called a zone.
  • Configs: A combination of zones or a single zone is called a config. There may be any number of configs, but only one config can be enabled at a time.

Types of Zoning

  1. WWPN Zoning
    • Based on the World Wide Port Name (WWPN) of devices.
    • Each HBA and storage port has a unique WWPN.
    • Provides flexibility as zoning remains unchanged if a device is moved to another port.
    • Type: Hard Zoning
      Example:
      zonecreate “Zone_A”, “20:00:00:25:B5:11:22:33; 10:00:00:90:FA:55:66:77”
  1. Domain, Index Zoning (Port Zoning)
    • Based on physical switch ports, identified by domain ID and port index.
    • Tied to the switch’s hardware layout.
    • If a device moves to another port, the zone must be updated.
    • Type: Hard Zoning
      Example:
      zonecreate “Zone_B”, “1,2; 1,5”
  1. Mixed Zoning
    • Combines WWPN and port-based zoning.
    • Useful for hybrid environments where flexibility and physical port control are both needed.
    • Type: Session-Based Zoning
      Example:
      zonecreate “Zone_C”, “20:00:00:25:B5:11:22:33; 1,5”

Zoning Enforcement

  • Soft Zoning (Logical Zoning):
    • Restricts visibility by limiting the devices a host can see.
    • Does not enforce access at the hardware level.
    • Devices can bypass soft zoning using manual configuration, which makes it less secure.
  • Hard Zoning (Physical Zoning):
    • Enforced at the ASIC (Application-Specific Integrated Circuit) level.
    • Ensures devices can only communicate if they are part of the same zone.
    • Provides strict access control, enhancing security.
    • Examples: WWPN Zoning, Domain, Index Zoning (Port Zoning)
  • Session-Based Zoning:
    • Used in mixed zoning environments.
    • Combines elements of both WWPN and port zoning, allowing flexibility for dynamic environments.

Brocade switches typically use hard zoning for secure and reliable fabric partitioning.

Zoning Enforcement

  • Soft Zoning (Logical Zoning):
    • Restricts visibility by limiting the devices a host can see.
    • Does not enforce access at the hardware level.
    • Devices can bypass soft zoning using manual configuration, which makes it less secure.
  • Hard Zoning (Physical Zoning):
    • Enforced at the ASIC (Application-Specific Integrated Circuit) level.
    • Ensures devices can only communicate if they are part of the same zone.
    • Provides strict access control, enhancing security.
    • Examples: WWPN Zoning, Domain, Index Zoning (Port Zoning)
  • Session-Based Zoning:
    • Used in mixed zoning environments.
    • Combines elements of both WWPN and port zoning, allowing flexibility for dynamic environments.

Brocade switches typically use hard zoning for secure and reliable fabric partitioning.

Configuration in Fabric

  • Defined Config: Contains all created zones but is not active.
  • Enabled Config: The active configuration currently running in the fabric.
  • You can create multiple configurations, but only one can be enabled at a time.
  • Example commands:
    cfgcreate “Config_A”, “Zone_A; Zone_B” cfgenable “Config_A”

    To view available configurations:

cfgshow

To check enabled configurations:

cfgactvshow

Creating a Zone for a New Server

Scenario

  • Server WWPN: 10:00:00:25:B5:11:22:33

  • Storage WWPN: 50:06:01:60:3A:E0:45:67

  • Zone Configuration Name: CFG_PROD_SAN

Step 1: Create an Alias for the Server
  • Create the alias when the server is being zoned for the first time.
    alicreate "ALI_SRV_APP01_HBA1","10:00:00:25:B5:11:22:33"
Step 2: Create or Reuse the Storage Alias

  • If the storage alias already exists, reuse it

  • If it does not exist, create it once
    alicreate “ALI_STG_POWERSTORE_P1”,“50:06:01:60:3A:E0:45:67”

Step 3: Create the Zone (Single-Initiator Zoning)
  • zonecreate "ZONE_APP01_TO_POWERSTORE","ALI_SRV_APP01_HBA1;ALI_STG_POWERSTORE_P1"
Step 4: Create or Update the Zone Configuration
  • Option 1: Create a New Configuration (First-Time Setup)
    • Use this only if no configuration exists on the fabric.
      cfgcreate "CFG_PROD_SAN","ZONE_APP01_TO_POWERSTORE"
Option 2: Add the Zone to an Existing Configuration
  • If the configuration already exists, skip cfgcreate and use:
    cfgadd "CFG_PROD_SAN","ZONE_APP01_TO_POWERSTORE"
Step 5: Save the Configuration
  • cfgsave
Step 6: Enable the Configuration
  • cfgenable "CFG_PROD_SAN"
Zoning Completed
  • The server APP01 is now successfully zoned to the storage and can detect LUNs after host-side rescans.
Important Notes (Best Practices)

  • ✔ Only one active configuration is allowed per fabric

  • ✔ Always use aliases, never raw WWPNs

  • ✔ Follow single-initiator zoning

  • ✔ Run cfgshow and zoneshow before enabling

  • ✔ Perform zoning during approved maintenance windows

Previous Lesson
Next Lesson
Scroll to Top