For more details, please see ourCookie Policy.


Fibre Channel (SAN)

Reply
Contributor
Posts: 37
Registered: ‎08-08-2012
Accepted Solution

​The strange behavior of some F-Port!

[ Edited ]

​Just only one specific F-Port not work fine with few specific F-Ports in its local zone!

 

It might be another strange symptom that the F-Port(JCPMSDB2_BAK) can work fine with its all corresponding zonemembers except for the two F-Ports( (JCYKTAPE1;JCYKTAPE3)!
That means JCPMSDB2_BAK can work fine with JCYKTAPE2 in the same problemtic JCPMSDB2_TapeZone, and also JCYKTAPE1/3 can work fine with all other corresponding zones!
Notes: all the corresponding zones with JCPMSDB2_BAK and JCYKTAPE<n> use the HARD WWN addressing schema,and also they are all right from fcping with each other !

 

 

CMSFZSAN02:admin>
CMSFZSAN02:admin> 
CMSFZSAN02:admin> 
CMSFZSAN02:admin> zoneshow JCPMSDB2_37DS5020
                zone: JCPMSDB2_37DS5020
                          PMS2VTape2_WWN; PMS2VTL; JCPMSDB2_BAK

CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin> zoneshow JCPMSDB2_TapeZone
                zone: JCPMSDB1_TapeZone
                          JCPMSDB2_BAK; JCYKTAPE1; JCYKTAPE2; JCYKTAPE3

CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin> zoneshow JCPMSDB1_TapeZone
                zone: JCPMSDB1_TapeZone
                          JCPMSDB1_BAK; JCYKTAPE1; JCYKTAPE2; JCYKTAPE3

CMSFZSAN02:admin>

CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin> alishow JCYKTAPE1
               alias: JCYKTAPE1
                        50:03:08:c0:02:40:18:03

CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin> alishow JCYKTAPE3
                alias: JCYKTAPE3
                         50:03:08:c0:02:40:18:18

CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin> fcping 10:00:00:00:c9:83:a1:18 50:03:08:c0:02:40:18:18
Source: 10:00:00:00:c9:83:a1:18
Destination: 50:03:08:c0:02:40:18:18
Zone Check: Zoned

Pinging 10:00:00:00:c9:83:a1:18 [0x01ed00] with 12 bytes of data:
received reply from 10:00:00:00:c9:83:a1:18: 12 bytes time:317 usec
received reply from 10:00:00:00:c9:83:a1:18: 12 bytes time:204 usec
received reply from 10:00:00:00:c9:83:a1:18: 12 bytes time:202 usec
received reply from 10:00:00:00:c9:83:a1:18: 12 bytes time:200 usec
received reply from 10:00:00:00:c9:83:a1:18: 12 bytes time:218 usec
5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout
Round-trip min/avg/max = 200/228/317 usec

Pinging 50:03:08:c0:02:40:18:18 [0x01dd00] with 12 bytes of data:
received reply from 50:03:08:c0:02:40:18:18: 12 bytes time:231 usec
received reply from 50:03:08:c0:02:40:18:18: 12 bytes time:688 usec
received reply from 50:03:08:c0:02:40:18:18: 12 bytes time:227 usec
received reply from 50:03:08:c0:02:40:18:18: 12 bytes time:217 usec
received reply from 50:03:08:c0:02:40:18:18: 12 bytes time:232 usec
5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout
Round-trip min/avg/max = 217/319/688 usec
CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin> fcping 10:00:00:00:c9:83:a1:18 50:03:08:c0:02:40:18:03
Source: 10:00:00:00:c9:83:a1:18
Destination: 50:03:08:c0:02:40:18:03
Zone Check: Zoned

Pinging 10:00:00:00:c9:83:a1:18 [0x01ed00] with 12 bytes of data:
received reply from 10:00:00:00:c9:83:a1:18: 12 bytes time:313 usec
received reply from 10:00:00:00:c9:83:a1:18: 12 bytes time:207 usec
received reply from 10:00:00:00:c9:83:a1:18: 12 bytes time:202 usec
received reply from 10:00:00:00:c9:83:a1:18: 12 bytes time:216 usec
received reply from 10:00:00:00:c9:83:a1:18: 12 bytes time:202 usec
5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout
Round-trip min/avg/max = 202/228/313 usec

Pinging 50:03:08:c0:02:40:18:03 [0x01df00] with 12 bytes of data:
received reply from 50:03:08:c0:02:40:18:03: 12 bytes time:725 usec
received reply from 50:03:08:c0:02:40:18:03: 12 bytes time:227 usec
received reply from 50:03:08:c0:02:40:18:03: 12 bytes time:215 usec
received reply from 50:03:08:c0:02:40:18:03: 12 bytes time:215 usec
received reply from 50:03:08:c0:02:40:18:03: 12 bytes time:229 usec
5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout
Round-trip min/avg/max = 215/322/725 usec
CMSFZSAN02:admin>
CMSFZSAN02:admin>
CMSFZSAN02:admin>

Regular Contributor
Posts: 166
Registered: ‎02-05-2014

Re: ​The strange behavior of some F-Port!

Hello Owen,

 

As you mentioned the problem is resolved.

Kind regards,
Erwin van Londen
Brocade Distinguished Architect
http://www.erwinvanlonden.net The Fibre Channel blog



Q&A -> https://hackhands.com/elo/


-------

Join the Community

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