Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 17
Registered: ‎10-09-2016
Accepted Solution

Problem with connecting new SAN Storage to switch

Hi

I have bought a new san storage (HP MSA 2040) , the problem is when I connect this new device to the san switch, it cannot see any initiators on my fabric network and its connection status in my switch interface is INVALID (see attachment photo port 14 , 15)

 

any suggestion any help

 

thank you

 

ps: sry for my bad eng

 

Brocade Moderator
Posts: 254
Registered: ‎08-31-2009

Re: Problem with connecting new SAN Storage to switch

Hello,

 

Please can you provide the output of the CLI commands below:

 

switchshow

portcfgshow

porterrshow

portshow 14

portshow 15

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Brocade Moderator
Posts: 215
Registered: ‎03-29-2011

Re: Problem with connecting new SAN Storage to switch

Hi,

 

when I look at the first picture, the new storage is connected two ports - 14 and 15 - which is your EZ switch setup is configured for hosts. Based on the second picture, the new storage is correctly logged into the new servers and thus logged into the switch. Since you connected the storage to ports planned tio be used for hosts, there will be no zoning.  per the first picture

 

"... To change the port connection type assignements you must re-run Setup and seelctTypical Zoning Again.."

 

or you need to edit the zoning.




If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Occasional Contributor
Posts: 17
Registered: ‎10-09-2016

Re: Problem with connecting new SAN Storage to switch

CentralSAN:admin> switchshow
switchName: CentralSAN
switchType: 71.2
switchState: Online
switchMode: Native
switchRole: Principal
switchDomain: 1
switchId: fffc01
switchWwn: 10:00:00:05:33:7c:01:c0
zoning: ON (cfg)
switchBeacon: OFF

Index Port Address Media Speed State Proto
==============================================
0 0 010000 id N8 Online FC L-Port 1 public
1 1 010100 id N8 Online FC L-Port 1 public
2 2 010200 id N8 Online FC L-Port 1 public
3 3 010300 id N8 Online FC F-Port 50:01:43:80:12:08:a6:6c
4 4 010400 id N8 Online FC L-Port 1 public
5 5 010500 id N8 Online FC F-Port 50:01:43:80:12:08:ce:96
6 6 010600 id N8 Online FC F-Port 50:01:43:80:12:08:78:72
7 7 010700 id N8 Online FC F-Port 50:01:43:80:12:08:ce:00
8 8 010800 id N8 Online FC F-Port 50:01:43:80:12:08:ce:92
9 9 010900 -- N8 No_Module FC
10 10 010a00 id N8 No_Light FC
11 11 010b00 id N2 Online FC F-Port 50:01:43:80:12:08:a6:74
12 12 010c00 id N8 No_Light FC
13 13 010d00 id N8 Online FC F-Port 20:70:00:c0:ff:25:dc:8c
14 14 010e00 id N8 Online FC F-Port 24:70:00:c0:ff:25:dc:8c
15 15 010f00 id N8 No_Light FC
16 16 011000 -- N8 No_Module FC (No POD License) Disabled
17 17 011100 -- N8 No_Module FC (No POD License) Disabled
18 18 011200 -- N8 No_Module FC (No POD License) Disabled
19 19 011300 -- N8 No_Module FC (No POD License) Disabled
20 20 011400 -- N8 No_Module FC (No POD License) Disabled
21 21 011500 -- N8 No_Module FC (No POD License) Disabled
22 22 011600 -- N8 No_Module FC (No POD License) Disabled
23 23 011700 -- N8 No_Module FC (No POD License) Disabled
CentralSAN:admin>


CentralSAN:admin> portcfgshow

Ports of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-----------------+---+---+---+---+-----+---+---+---+-----+---+---+---+-----+---+---+---
Speed AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN
Fill Word 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
AL_PA Offset 13 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Trunk Port ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON
Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
VC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked L_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked G_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Disabled E_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked E_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
ISL R_RDY Mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
RSCN Suppressed .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Persistent Disable .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
LOS TOV enable .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NPIV capability ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON
NPIV PP Limit 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255 255
QOS E_Port AE AE AE AE AE AE AE AE AE AE AE AE AE AE AE AE
Mirror Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Rate Limit .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Credit Recovery ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON
Fport Buffers .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Port Auto Disable .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
CSCTL mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..

Fault Delay 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

 

Ports of Slot 0 16 17 18 19 20 21 22 23
-----------------+---+---+---+---+-----+---+---+---
Speed AN AN AN AN AN AN AN AN
Fill Word 3 3 3 3 3 3 3 3
AL_PA Offset 13 .. .. .. .. .. .. .. ..
Trunk Port ON ON ON ON ON ON ON ON
Long Distance .. .. .. .. .. .. .. ..
VC Link Init .. .. .. .. .. .. .. ..
Locked L_Port .. .. .. .. .. .. .. ..
Locked G_Port .. .. .. .. .. .. .. ..
Disabled E_Port .. .. .. .. .. .. .. ..
Locked E_Port .. .. .. .. .. .. .. ..
ISL R_RDY Mode .. .. .. .. .. .. .. ..
RSCN Suppressed .. .. .. .. .. .. .. ..
Persistent Disable .. .. .. .. .. .. .. ..
LOS TOV enable .. .. .. .. .. .. .. ..
NPIV capability ON ON ON ON ON ON ON ON
NPIV PP Limit 255 255 255 255 255 255 255 255
QOS E_Port AE AE AE AE AE AE AE AE
Mirror Port .. .. .. .. .. .. .. ..
Rate Limit .. .. .. .. .. .. .. ..
Credit Recovery ON ON ON ON ON ON ON ON
Fport Buffers .. .. .. .. .. .. .. ..
Port Auto Disable .. .. .. .. .. .. .. ..
CSCTL mode .. .. .. .. .. .. .. ..

Fault Delay 0 0 0 0 0 0 0 0
where AE:QoSAutoEnable, AN:AutoNegotiate, ..Smiley SurprisedFF, NA:NotApplicable, ??:INVALID,

CentralSAN:admin> portshow 14
portIndex: 14
portName:
portHealth: No Fabric Watch License

Authentication: None
portDisableReason: None
portCFlags: 0x1
portFlags: 0x24b03 PRESENT ACTIVE F_PORT G_PORT U_PORT LOGICAL_ONLINE LOGIN NOELP LED ACCEPT FLOGI
LocalSwcFlags: 0x0
portType: 18.0
POD Port: Port is licensed
portState: 1 Online
Protocol: FC
portPhys: 6 In_Sync portScn: 32 F_Port
port generation number: 26
state transition count: 7

portId: 010e00
portIfId: 4302000a
portWwn: 20:0e:00:05:33:7c:01:c0
portWwn of device(s) connected:
24:70:00:c0:ff:25:dc:8c
Distance: normal
portSpeed: N8Gbps

LE domain: 0
FC Fastwrite: OFF
Interrupts: 0 Link_failure: 0 Frjt: 0
Unknown: 0 Loss_of_sync: 5 Fbsy: 0
Lli: 118 Loss_of_sig: 7
Proc_rqrd: 85 Protocol_err: 0
Timed_out: 0 Invalid_word: 909967
Rx_flushed: 0 Invalid_crc: 0
Tx_unavail: 0 Delim_err: 0
Free_buffer: 0 Address_err: 0
Overrun: 0 Lr_in: 4
Suspended: 0 Lr_out: 0
Parity_err: 0 Ols_in: 0
2_parity_err: 0 Ols_out: 4
CMI_bus_err: 0

Port part of other ADs: No
CentralSAN:admin> portshow 15
portIndex: 15
portName:
portHealth: No Fabric Watch License

Authentication: None
portDisableReason: None
portCFlags: 0x1
portFlags: 0x4001 PRESENT U_PORT LED
LocalSwcFlags: 0x0
portType: 18.0
POD Port: Port is licensed
portState: 2 Offline
Protocol: FC
portPhys: 4 No_Light portScn: 2 Offline
port generation number: 28
state transition count: 8

portId: 010f00
portIfId: 43020008
portWwn: 20:0f:00:05:33:7c:01:c0
portWwn of device(s) connected:

Distance: normal
portSpeed: N8Gbps

LE domain: 0
FC Fastwrite: OFF
Interrupts: 0 Link_failure: 0 Frjt: 0
Unknown: 0 Loss_of_sync: 6 Fbsy: 0
Lli: 94 Loss_of_sig: 13
Proc_rqrd: 85 Protocol_err: 0
Timed_out: 0 Invalid_word: 216276
Rx_flushed: 0 Invalid_crc: 0
Tx_unavail: 0 Delim_err: 0
Free_buffer: 0 Address_err: 0
Overrun: 0 Lr_in: 4
Suspended: 0 Lr_out: 0
Parity_err: 0 Ols_in: 0
2_parity_err: 0 Ols_out: 4
CMI_bus_err: 0

Port part of other ADs: No
CentralSAN:admin>

Brocade Moderator
Posts: 77
Registered: ‎04-27-2009

Re: Problem with connecting new SAN Storage to switch

Hi there,

 

I would agree on Martin.Sjölin's suggestions.

 

TL

If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider.
Brocade Moderator
Posts: 215
Registered: ‎03-29-2011

Re: Problem with connecting new SAN Storage to switch

Hi,

 

as mentionned in earlier post, I suspect you either have to get your zoning updated, please provide the output from the command

 

 

nszonemember 20:70:00:c0:ff:25:dc:8c

nszonemember 24:70:00:c0:ff:25:dc:8c

 

to see what is zoned to the two new storageports.




If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Occasional Contributor
Posts: 17
Registered: ‎10-09-2016

Re: Problem with connecting new SAN Storage to switch

Hi Martin 

Is this "typical zoning" disruptive ?

 

here is outcome of those command that u mentioned before:

CentralSAN:admin> nszonemember 20:70:00:c0:ff:25:dc:8c
5 local zoned members:

Type Pid COS PortName NodeName SCR
N 010d00; 3;20:70:00:c0:ff:25:dc:8c;20:80:00:c0:ff:25:dc:8c; 0x00000003
FC4s: FCP [HP MSA 2040 SAN G210]
Fabric Port Name: 20:0d:00:05:33:7c:01:c0
Permanent Port Name: 20:70:00:c0:ff:25:dc:8c
Device type: Physical Initiator+Target
Port Index: 13
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0100ef; 3;24:70:00:c0:ff:12:1b:83;20:80:00:c0:ff:12:1b:83; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:00:00:05:33:7c:01:c0
Permanent Port Name: 24:70:00:c0:ff:12:1b:83
Device type: Physical Initiator+Target
Port Index: 0
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0101ef; 3;20:70:00:c0:ff:12:1b:83;20:80:00:c0:ff:12:1b:83; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:01:00:05:33:7c:01:c0
Permanent Port Name: 20:70:00:c0:ff:12:1b:83
Device type: Physical Initiator+Target
Port Index: 1
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0102ef; 3;24:70:00:c0:ff:11:a1:b9;20:80:00:c0:ff:11:a1:b9; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:02:00:05:33:7c:01:c0
Permanent Port Name: 24:70:00:c0:ff:11:a1:b9
Device type: Physical Initiator+Target
Port Index: 2
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0104ef; 3;20:70:00:c0:ff:11:a1:b9;20:80:00:c0:ff:11:a1:b9; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:04:00:05:33:7c:01:c0
Permanent Port Name: 20:70:00:c0:ff:11:a1:b9
Device type: Physical Initiator+Target
Port Index: 4
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No

No remote zoned members
CentralSAN:admin> nszonemember 24:70:00:c0:ff:25:dc:8c
5 local zoned members:

Type Pid COS PortName NodeName SCR
N 010e00; 3;24:70:00:c0:ff:25:dc:8c;20:80:00:c0:ff:25:dc:8c; 0x00000003
FC4s: FCP [HP MSA 2040 SAN G210]
Fabric Port Name: 20:0e:00:05:33:7c:01:c0
Permanent Port Name: 24:70:00:c0:ff:25:dc:8c
Device type: Physical Initiator+Target
Port Index: 14
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0100ef; 3;24:70:00:c0:ff:12:1b:83;20:80:00:c0:ff:12:1b:83; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:00:00:05:33:7c:01:c0
Permanent Port Name: 24:70:00:c0:ff:12:1b:83
Device type: Physical Initiator+Target
Port Index: 0
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0101ef; 3;20:70:00:c0:ff:12:1b:83;20:80:00:c0:ff:12:1b:83; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:01:00:05:33:7c:01:c0
Permanent Port Name: 20:70:00:c0:ff:12:1b:83
Device type: Physical Initiator+Target
Port Index: 1
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0102ef; 3;24:70:00:c0:ff:11:a1:b9;20:80:00:c0:ff:11:a1:b9; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:02:00:05:33:7c:01:c0
Permanent Port Name: 24:70:00:c0:ff:11:a1:b9
Device type: Physical Initiator+Target
Port Index: 2
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0104ef; 3;20:70:00:c0:ff:11:a1:b9;20:80:00:c0:ff:11:a1:b9; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:04:00:05:33:7c:01:c0
Permanent Port Name: 20:70:00:c0:ff:11:a1:b9
Device type: Physical Initiator+Target
Port Index: 4
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No

No remote zoned members

Occasional Contributor
Posts: 17
Registered: ‎10-09-2016

Re: Problem with connecting new SAN Storage to switch

hi martin

is this "typical zoning" disruptive?

CentralSAN:admin> nszonemember 20:70:00:c0:ff:25:dc:8c
5 local zoned members:

Type Pid COS PortName NodeName SCR
N 010d00; 3;20:70:00:c0:ff:25:dc:8c;20:80:00:c0:ff:25:dc:8c; 0x00000003
FC4s: FCP [HP MSA 2040 SAN G210]
Fabric Port Name: 20:0d:00:05:33:7c:01:c0
Permanent Port Name: 20:70:00:c0:ff:25:dc:8c
Device type: Physical Initiator+Target
Port Index: 13
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0100ef; 3;24:70:00:c0:ff:12:1b:83;20:80:00:c0:ff:12:1b:83; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:00:00:05:33:7c:01:c0
Permanent Port Name: 24:70:00:c0:ff:12:1b:83
Device type: Physical Initiator+Target
Port Index: 0
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0101ef; 3;20:70:00:c0:ff:12:1b:83;20:80:00:c0:ff:12:1b:83; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:01:00:05:33:7c:01:c0
Permanent Port Name: 20:70:00:c0:ff:12:1b:83
Device type: Physical Initiator+Target
Port Index: 1
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0102ef; 3;24:70:00:c0:ff:11:a1:b9;20:80:00:c0:ff:11:a1:b9; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:02:00:05:33:7c:01:c0
Permanent Port Name: 24:70:00:c0:ff:11:a1:b9
Device type: Physical Initiator+Target
Port Index: 2
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
NL 0104ef; 3;20:70:00:c0:ff:11:a1:b9;20:80:00:c0:ff:11:a1:b9; 0x00000003
FC4s: FCP [HP P2000 G3 FC T230]
Fabric Port Name: 20:04:00:05:33:7c:01:c0
Permanent Port Name: 20:70:00:c0:ff:11:a1:b9
Device type: Physical Initiator+Target
Port Index: 4
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No

No remote zoned members

Brocade Moderator
Posts: 215
Registered: ‎03-29-2011

Re: Problem with connecting new SAN Storage to switch

Hi,

 

from the nszonemember output is clear that you new storage is only zoned with the storage ports 0,1,2,4. 

You will need to create new zones, one for each server (single initiator zoning) which should have access to the new storage.

 

So, in the Switch Manager, you need to go to the "Zoning" section and look in the "View" and "Edit".

 

Zoning will only be impacting the devices touch by the zoning operation - devices removed or added from a zone. 

Servers will normally handling a zoning operation - pending on OS and version, a rediscovery (probing) might be needed.




If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Brocade Moderator
Posts: 215
Registered: ‎03-29-2011

Re: Problem with connecting new SAN Storage to switch

Hi,

 

check out the zoning chapter of ezswitch manager guide

 

http://www.brocade.com/content/html/en/administration-guide/fos-741-ezswitchsetup/GUID-1FA47388-CD98-40FF-BA8C-9BB0BB6AD9BF.html

 

you need to select which type of zoning you want now after you added your new storage

 

  • If you choose  Typical Zoning,  a port-based zoning scheme is created. This zoning scheme creates a two-member zone for every possible pairing of H and S ports connected on the Configure Ports and Connect Devices window. This ensures that any host device connected to an H port is able to communicate with any storage device connected to an S port. This remains true even if you move a device, assuming you connect the device to the correct type of port (H or S).

 

  • If you choose Custom Zoning, you create a device accessibility matrix during setup. The device accessibility matrix creates a device-based zoning scheme. By default, every connected host device can communicate with every connected storage device, as in Typical Zoning. You can use the device accessibility matrix to selectively disallow communications between certain devices, creating a device-partitioning scheme that is enforced by zoning. Because Custom Zoning is device-based, you may freely move your devices to different ports without affecting accessibility relationships. If you add or permanently remove devices, you should reconfigure the accessibility matrix.
  •  If you choose Advanced Zoning, you are given direct access to the zoning database through Web Tools, and you can create a zoning scheme of your own. EZSwitchSetup Switch Manager can validate and display accessibility relationships based on your scheme, and it can replace your scheme with Typical Zoning or Custom Zoning. If you want to edit your scheme, you must return to the EZSwitchSetup switch configuration wizard and select Advanced Management to start Web Tools. For specific information about using Web Tools for zoning, refer to the Web Tools Administrator's Guide.



If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.