Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 6
Registered: ‎12-03-2014

Initiator cannot Plogi but can see it in NS

Hi Guys,

I have met a strange issue, we have an initiator connected at port 10/22, and it is zoned to the target.

We can fcping the initiator and it does exist in the naming server.

 

Index Slot Port Address Media Speed State Proto
============================================================

214   10   22   02ca40   id    N16        Online      FC  F-Port  50:00:14:42:f0:02:68:00

 

But the target cannot see the initiator. And fcpprobeshow reports this F_Port is offline.

 

INV_VPLX_Core_Fabric_B:FID10:admin> fcpprobeshow 10/22


port 214 an F_Port and it is offline.

 

When moving the cable from this 10/22 to other port on the same blade, it can Plogi and fcpprobeshow can give the online and rest of the outputs.

Really confuse about why in some ports of this blade cannot work but some of them works.

Frequent Contributor
Posts: 107
Registered: ‎04-05-2011

Re: Initiator cannot Plogi but can see it in NS

Hello Trucky,

 

Can you share with us the portcfgshow from both working and non working ports?

 

Occasional Contributor
Posts: 6
Registered: ‎12-03-2014

Re: Initiator cannot Plogi but can see it in NS

Hi Anovelli,

Both working and non-working ports have exactly the same config.

I also used portcfgdefault command to set the port config to default, and mannually compared both portcfg are the same.

 

The are 16G ports on FC16-48 of a DCX8510-8 director. FOS version v7.4.1b (upgraded recently, hope it can solve the issue, but it does not). Considered a whole power reset, in the upgrade, CP blades take turns to activated with new code, another power cycle can help?

I even tried slotpoweroff of this blade 10, and powered it on, but no success. Because I have already swapped the cables, the problem fixed in the ports, and SFP swap does not work. So maybe some backend ASCI control level, or software level is not working properly. I also suspect ports within same port group have the issue, but other port group on this blade also suffers this issue.

The F_Port offline happened randomly, but all of them are shown online and existing in the name server database.

 

 

Frequent Contributor
Posts: 107
Registered: ‎04-05-2011

Re: Initiator cannot Plogi but can see it in NS

Hello Trucky,

 

Can you attach a supportshow here ?

 Also, can you get a portlogdumpport <portindex> just after you plug the cable in the problematic port?

 

You say that the por is displayed in NS. Can you try to issue a nodefind <wwpn> and post output ?

Occasional Contributor
Posts: 6
Registered: ‎12-03-2014

Re: Initiator cannot Plogi but can see it in NS

Hi Anovelli,

This is a remote environment, so cannot provide plugin dump information right now.

Below is the nodefind output of the Vplex port, it exist in the fabric

INV_VPLX_Core_Fabric_B:FID10:root> nodefind 50:00:14:42:f0:02:68:00
Local:
Type Pid COS PortName NodeName SCR
N 02f140; 2,3;50:00:14:42:f0:02:68:00;50:00:14:40:43:f0:02:68; 0x00000003
Fabric Port Name: 20:3a:00:05:33:b4:6f:02
Permanent Port Name: 50:00:14:42:f0:02:68:00
Device type: Physical Unknown(initiator/target)         //this always be like this for those problematic ports, cannot identify it's a initiator or target
Port Index: 58
Share Area: Yes
Device Shared in Other AD: No
Redirect: No
Partial: No
LSAN: No
Aliases:

 

Also the initiator can be found in the NS:

 

INV_VPLX_Core_Fabric_B:FID10:root> nodefind 10:00:00:00:c9:71:67:cb
Remote:
Type Pid COS PortName NodeName
N 250400; 2,3;10:00:00:00:c9:71:67:cb;20:00:00:00:c9:71:67:cb;
FC4s: IPFC FCP
PortSymb: [34] "Emulex PPN-10:00:00:00:C9:71:67:CB"
NodeSymb: [50] "Emulex LPe12002-M8 FV2.01A12 DV10.0.720.0 LXH3SER9"
Fabric Port Name: 20:17:00:05:33:6b:48:64
Permanent Port Name: 10:00:00:00:c9:71:67:cb
Device type: Physical Initiator
Port Index: 23
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
Aliases:

 

initiator and target are zoned correctly, is it possiable that Plogi get lost in the fabric?

Occasional Contributor
Posts: 6
Registered: ‎12-03-2014

Re: Initiator cannot Plogi but can see it in NS

This a port belongs to the same VPLEX and connected to the same slot 4 of the 8510, but this time the port number is 33:

 

INV_VPLX_Core_Fabric_B:FID10:root> nodefind 50:00:14:42:f0:02:f1:01
Local:
Type Pid COS PortName NodeName SCR
N 02b380; 2,3;50:00:14:42:f0:02:f1:01;50:00:14:40:43:f0:02:f1; 0x00000003
FC4s: FCP
Fabric Port Name: 2e:31:00:05:33:b4:6f:02
Permanent Port Name: 50:00:14:42:f0:02:f1:01
Device type: Physical Target
Port Index: 305
Share Area: Yes
Device Shared in Other AD: No
Redirect: No
Partial: No
LSAN: No
Aliases:

 

INV_VPLX_Core_Fabric_B:FID10:root> fcpprobeshow 4/33


port 305 is F-Port and it is online.
nodes probed: 0
successful PLOGIs: 0
successful PRLIs: 0
successful INQUIRies:0
successful LOGOs: 0
outstanding IUs: 0
probing state: 3
probing TOV: 0
probing count: 0
probing next: 0
pmap: 0x00000000, 0x00000000, 0x01000000, 0x00000000
update map: 0x00000000, 0x00000000, 0x01000000, 0x00000000
npiv pmap: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
npiv update map: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000

list of devices(may include old NPIV devices):

 

Join the Community

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