Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 17
Registered: ‎08-08-2012

The stuck F-Ports !

ISSUE ENVIROMENTS: B48000 6.3.1(JCSAN02)/B48000 5.2.0(SAN02)、IFR with DWDM

 

ISSUE DESCRIPTION:
There are some random and aperiodic problematical F-ports that are mainly TLs' driver ports appeared on the SAN02.
Everytime I could temporarily resolve it via reset the problematical F-port, then it would work finely at least one week (and more than one month above)!
1) Sometimes the problem only influences the relevant F-ports on the remote end of LSAN while the problematical F-port works finely on the local farbric SAN02.
2) Sometimes the poblem influences all the relevant F-ports on both ends of LSANs including the local farbric SAN02.

 

But it is so strange that not only there was almost no error statistics about the problematical F-port, but also the problematical F-port can be fcpinged successfully with each other relevant F-ports Zoning! And it also seems obivously that all source influenced F-ports just cannot pass PLOGI to the target problematical F-port via the source hosts' cmd/debug infomation !

I think that it should not be caused by the Session Based HARD Zoning because the symptom about for many other F-ports with such Zonings have frequently appeared in errdump while they still always work finely !


The attached file for supportshow at 15/10/02 was for issue scenarios 1), and the other attached file for supportshow at 16/05/12 was for issue scenarios 2).

 

The following output are the problematical F-ports which happened randomly and aperiodically on SAN02:

 

SAN02:admin>
SAN02:admin>
SAN02:admin> switchshow|grep -Ei "50:03:08:c0"
50 4 2 013200 id N4 Online F-Port 50:03:08:c0:02:56:30:0e
51 4 3 013300 id N4 Online F-Port 50:03:08:c0:02:56:30:14
54 4 6 013600 id N4 Online F-Port 50:03:08:c0:02:56:30:26
55 4 7 013700 id N4 Online F-Port 50:03:08:c0:02:56:30:2c
186 4 26 01ba00 id N4 Online F-Port 50:03:08:c0:02:56:30:02
187 4 27 01bb00 id N4 Online F-Port 50:03:08:c0:02:56:30:20
104 9 8 016800 id N4 Online F-Port 50:03:08:c0:02:56:30:1a
105 9 9 016900 id N4 Online F-Port 50:03:08:c0:02:56:30:08
SAN02:admin>
SAN02:admin>

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

Re: The stuck F-Ports !

The firmwares you are running are very very old!

 

Consider upgrading your firmware, and if your problem is not solved, at least you will have more statistics about this behavior. I bet that after the upgrade you will never see this again.

Occasional Contributor
Posts: 17
Registered: ‎08-08-2012

Re: The stuck F-Ports !

I see that almost everyone would say the firmware version was too older at last,   but I also still do not think the abnormal symptom should be relevant to the older version because it focuses only on the above 8 problematical F-Ports !

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

Re: The stuck F-Ports !

New firmwares brings new resiliency features and correction to current code. Deny this line of thinking is risky. There are lots of defects related to RSCN in those older firmwares and at the and, the solution WILL BE the code upgrade. As an enthusiast in SAN and Storage, I Like to investigate problems, but as a Professional, I must keep in mind that the environment integrity comes first! Hope you find your answers. I would suggest you to look ad the Defects secions from the next few releases later than you are running. But keep in mind that this may be unnecessary effort. But, just in case. The port wwpns of those ports are similar. Is that an storage or a tape library ?
Occasional Contributor
Posts: 17
Registered: ‎08-08-2012

Re: The stuck F-Ports !

[ Edited ]

They are some random and aperiodic problematical F-ports of the same TLs' driver ports appeared on the SAN02 !

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

Re: The stuck F-Ports !

Can you share with us the model of the TL/Drive ? probably a nodefind in the wwpn of one drive will be sufficient.
Occasional Contributor
Posts: 17
Registered: ‎08-08-2012

Re: The stuck F-Ports !

[ Edited ]

That is Scalar i6000 TL which  can be easily found with Driver Port/NodeSymb "HP Ultrium 6 Fibre Channel" in the SupportShow !

 

It is impossible that the problem is Scalar i6000 itself because:
1) Sometimes the Scalar i6000 at least worked finely in the issue scenario 1)  !
2) We have checked the Scalar i6000 all right with OEM QUANTUM everytime !

Occasional Contributor
Posts: 17
Registered: ‎08-08-2012

Re: The stuck F-Ports !

Anyone can help me ! ?

External Moderator
Posts: 4,780
Registered: ‎02-23-2004

Re: The stuck F-Ports !

can you please collect follow info and send me by email ?

 

from 48000, the port in question where the Scalar is connected:

 

"portcfgshow" and from "errorshow"

 

what is exact FW release from Scalar Library ?

 

Additional, is not a warranty, but as suggested by anovelli, you should upgrade the FOS to 6.2.x or higher it is most probable the issue is related to Old FOS Release.

TechHelp24
Occasional Contributor
Posts: 17
Registered: ‎08-08-2012

Re: The stuck F-Ports !

Thanks !

 

The problematical F-ports about the Scalar i6000 TL have already been output via switchshow in my above first post!
And also I have already uploaded the entire SupportShow attach files for both scenarios in my above first post !!

Join the Community

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