Brocade 200E Switch
 
Brocade 3850 Fabric Switch
 
Brocade 3900 Switch
 
Brocade 5300 Switch
 
Brocade 5100 Switch
 
Brocade 300 Switch
 
Brocade 48000 Director
 
Brocade 24000 Director
 
Brocade DCX-4S Backbone
 
Brocade 12000 Fabric Switch
 
Brocade 7500 Switch
 
Brocade 5000 Switch
 
Brocade 4100 Switch
 
Brocade DCX Backbone
 

PLA-Support>Sun Systems>DISK>Switch>SN-DK: Brocade Switch
 
_Old GCS Categories>Sun Microsystems>Switches>Brocade
 

Applies to:

Goal

This document aims to show how to analyze zoning on Brocade switches.

1. General commands to look at
2. Searching for specific devices and their zoning

Solution

Steps to Follow

1. General commands

• Is zoning enabled?

Use this command to display the effective zone configuration information:

primaryfcs:admin> cfgactvshow

Effective configuration:

No Effective configuration

This means zoning is disabled and the default zone configuration is used.
Use this command to display the Default Zone access mode:

primaryfcs:admin> defzone --show

Default Zone Access Mode

committed - No Access

transaction - No Transaction

This means that all ports are fenced and no devices can connect to another.
The other options is:

committed - All Access

This means all devices can connect to each other.

If cfgactvshow reads:

switch:admin> cfgactvshow

Effective configuration:

cfg: c4

zone: z3 33:07:06:05:04:03:02:01

zone: z4 44:01:23:45:67:89:a0:bc

40:01:23:45:67:89:a0:bc

There is a zoning configuration (c4) in effect. Zoning is enabled
Note: There can be multiple defined configurations, but only one configuration can be effective (in use).

• Consider using SAN Health / DCFM

Viewing zoning configurations are easier using DCFM or SAN Health. Please check https://login.brocade.com/ for these tools.
SAN Health can be downloaded/installed and used free of charge.

• CLI commands

The main command to list the configurations is cfgshow:

switch:admin> cfgshow

Defined configuration:

cfg: USA1 Blue_zone

cfg: USA_cfg Red_zone; Blue_zone

zone: Blue_zone

1,1; array1; 1,2; array2

zone: Red_zone

1,0; loop1

alias: array1 21:00:00:20:37:0c:76:8c; 21:00:00:20:37:0c:71:02

alias: array2 21:00:00:20:37:0c:76:22; 21:00:00:20:37:0c:76:28

alias: loop1 21:00:00:20:37:0c:76:85; 21:00:00:20:37:0c:71:df

Effective configuration:

cfg: USA_cfg

zone: Blue_zone

1,1

21:00:00:20:37:0c:76:8c

21:00:00:20:37:0c:71:02

1,2

21:00:00:20:37:0c:76:22

21:00:00:20:37:0c:76:28

zone: Red_zone

1,0

21:00:00:20:37:0c:76:85

21:00:00:20:37:0c:71:df

Here you see configuration USA_cfg exists of 2 zones Blue_zone and Red_zone .
Each zone lists its zone members. In this case it is a mix of WWN and <Domain,Port>. Preference is all WWN definitions though.
Another interesting command is nszonemember (the output is from a different configuration than the above) :
To display each local device's online zoned device data:

switch:admin> nszonemember -a

Port: 4 Pid: 0xb00400 Aliases: ix360_131_201_6a

Zoned Members: 2 devices

Pid: 0xb00400 Aliases: ix360_131_201_6a

Pid: 0xba1ee8 Aliases: trimm101b_3

Port: 12 Pid: 0xb00c01 Aliases: dl360_130159a

Zoned Members: 2 devices

Pid: 0xb00c01 Aliases: dl360_130159a

Pid: 0xbd1bef Aliases: nstor4b_8

Port: 13 Pid: 0xb00d00 Aliases: ix360_131_196p5

Zoned Members: 2 devices

Pid: 0xb00d00 Aliases: ix360_131_196p5

Pid: 0xe07d00 Aliases: hds9200_6p4 hds9200_6p4

<output truncated>

To display all the unzoned devices in the fabric:

switch:admin> nszonemember -u

Pid: 0xb01ea9; Aliases: trimm32b_1

Pid: 0xb01eaa; Aliases: trimm32b_2

Pid: 0xb01eab; Aliases: trimm32b_3

Pid: 0xb01eac; Aliases: trimm32b_4

Pid: 0xb01fad; Aliases: trimm32a_5

Pid: 0xb01fae; Aliases: trimm32a_6

Pid: 0xb01fb1; Aliases: trimm32a_7

Pid: 0xb01fb2; Aliases: trimm32a_8

Pid: 0xdc2800; Aliases:

Totally 9 unzoned devices in the fabric.

2. Searching for specific devices in the zoning configuration.

• nodefind

This command can be used with 3 operands:
WWN | PID | ALIAS
In this example we are searching the Name Server database for a specific WWN

switch:user> nodefind 20:00:00:e0:8b:01:ce:d3

Remote:

Type Pid COS PortName NodeName

NL 020eef; 3;20:00:00:e0:8b:01:ce:d3;20:00:00:e0:8b:01:ce:d3;

Fabric Port Name: 20:0e:00:60:69:51:0b:ba

Permanent Port Name: 20:00:00:e0:8b:01:ce:d3

Device type: Physical Target

Port Index: 14

Share Area: No

Device Shared in Other AD: No

Aliases:

If there is no device matching the given WWN, PID, or alias, the message "No device found" is
displayed. This means we first need to figure out why the device is not logged into the nameserver (this is not the scope of this document).

• nsShow / nscamshow

This will list the local nameserver database (from the switch where the command is issued)
nscamshow will show the nameserver databases that were imported from other switches in the fabric.
nsshow : nscamshow will show the complete nameserver database of all switches in the fabric.

• nszonemember

Providing a WWN as operand with nszonemember we can find which devices are zoned with it:

switch:admin> nszonemember 10:00:00:00:c8:23:0b:ad

3 local zoned members:

Type Pid COS PortName NodeName SCR

NL 041901; 2,3;10:00:00:00:c9:26:0e:ae;20:00:00:00:c9:26:0e:ae; 3

Fabric Port Name: 20:09:00:60:69:50:06:78

Permanent Port Name: 10:00:00:00:c9:26:0e:ae

Device type: Physical Initiator

NL 0416e2; 3;22:00:00:20:37:d9:6b:b3;20:00:00:20:37:d9:6b:b3; 0

FC4s: FCP [SEAGATE ST318304FC 0005]

Fabric Port Name: 20:06:00:60:69:50:06:78

Permanent Port Name: 22:00:00:20:37:d9:6b:b3

Device type: Physical Target

NL 0416e4; 3;22:00:00:20:37:d9:61:ac;20:00:00:20:37:d9:61:ac; 0

FC4s: FCP [SEAGATE ST318304FC 0005]

Permanent Port Name: 22:00:00:20:37:d9:61:ac

Device type: Physical Target

No remote zoned members

As you can see it also lists if the devices are remote (on another switch in the fabric) or local (on the same switch as this WWN)

• fcping

Sends a Fibre Channel Extended Link Service (ELS) Echo request to a pair of ports or to a single
destination.

switch:admin> fcping 0x020800 22:00:00:04:cf:75:63:85

Source: 0x20800

Destination: 22:00:00:04:cf:75:63:85

Zone Check: Zoned

Pinging 0x20800 with 12 bytes of data:

received reply from 0x20800: 12 bytes time:1159 usec

received reply from 0x20800: 12 bytes time:1006 usec

244 Fabric OS Command Reference

53-1001337-01

2 fcPing

received reply from 0x20800: 12 bytes time:1008 usec

received reply from 0x20800: 12 bytes time:1038 usec

received reply from 0x20800: 12 bytes time:1010 usec

5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout

Round-trip min/avg/max = 1006/1044/1159 usec

Pinging 22:00:00:04:cf:75:63:85 [0x217d9] with 12 bytes of data:

Request timed out

Request timed out

Request timed out

Request timed out

Request timed out

5 frames sent, 0 frames received, 0

Will tell if the 2 devices can communicate and also if they are zoned together .
Note that ELS Echo may not be supported on all devices. In such cases, the response could be either an ELS reject or a request timeout.
If you receive unavailable there is a problem communicating.

This solution has no attachment