Skip to main content
NetApp Knowledge Base

Why isnt Brocade zoning enabled after setting up a zone?

Views:
3,432
Visibility:
Public
Votes:
2
Category:
flexpod-with-infrastructure-automation
Specialty:
brocade
Last Updated:

Applies to

  • Brocade zoning 
  • Flexpod

Answer

Brocade zoning is not enabled after setting up a zone.

Created a zone on a Brocade switch but zoning does not show up in zoneshow or cfgshow.

When creating a zone on Brocade using the GUI or CLI, you must enable the configuration before saving.

Example:

brocade2400:admin> switchshow

 

switchName: brocade2400
switchType: 3.4
switchState: Online
switchRole: Principal
switchDomain: 1
switchId: XXX01
switchWwn: 10:00:00:XX:XX:XX:XX:XX
switchBeacon: OFF
port 0: id No_Light
port 1: -- No_Module
port 2: id No_Light
port 3: id No_Light
port 4: id No_Light
port 5: id No_Light
port 6: id No_Light
port 7: id No_Light

The basic steps to creating a zone on a Brocade switch are:

  1. Create aliases (optional, makes device management easier to read and administer) - alicreate
  2. Create the zone - zonecreate
  3. Create the zone configuration - cfgcreate
  4. Enable the configuration - cfgenable
  5. Save the configuration - cfgsave

Example:

alicreate switch1,10:00:00:XX:XX:XX:XX:XX     (Creates an alias)
zonecreate ZNE_switch1,switch1  (Create zones)
cfgcreate PROD_faba,ZNE_switch1  (Creates the zone configuration)
cfgenable PROD_faba    (Enables the zone configuration)
cfgsave      (Save the config)

Aliases make managing larger fabrics simpler because they allow you to use human readable formats. Zone configurations allow you to create one or more zones and group them together so that they can be managed as a single configuration. The configuration that is in effect is the effective configuration. While many configurations can exist on a switch, only one can be active at a given time. It is necessary to save the configuration in order to make it persistent across reboots.

Additional Information

Add your text here.

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.