fabric port has "F" instead of "CU"

Answered Question
Oct 21st, 2010
User Badges:

Hello,

4 ports on a MDS 9513 director are configured as Ficon.

3 have the correct "CU" state as viewed in Device manager, 1 port has "F" state.

In the Ficon tab the showing "F" port shows invalid.

IBM disk system port is set to Ficon.


What can I do to chandge it to CU?

TKX,

Ivy

Correct Answer by Michael Brown about 6 years 8 months ago

Thanks for the update.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
ivybeccukbc Fri, 10/22/2010 - 03:25
User Badges:

More information:


Port Address 64(0x40) is up in vsan 500
    Port number is 64(0x40), Interface is fc3/16
    Port name is
    Port is not admin blocked
    Prohibited port addresses are 250-253,255(0xfa-0xfd,0xff)
    Admin port mode is FX
    Port mode is F
    Peer is unknown                                                              <--------------------------- should be Peer is type 002107 model 932 manufactured by IBM

Port Address 65(0x41) is up in vsan 500
    Port number is 65(0x41), Interface is fc3/17
    Port name is
    Port is not admin blocked
    Prohibited port addresses are 250-253,255(0xfa-0xfd,0xff)
    Admin port mode is FX
    Port mode is F
    Peer is type 002107 model 932 manufactured by IBM

ivybeccukbc Fri, 10/22/2010 - 05:00
User Badges:

Hello,

The port is in a production environment "development" and cannot be toggled right now.

It has to wait for a "service" weekend.

I could not find any further information in the Cisco MDS 9000 Family CLI Configuration Guide, Release 4.x

Tkx,

Ivy

ivybeccukbc Tue, 11/09/2010 - 03:34
User Badges:

Hello,

The port was toggled and is still in "F" instead of "CU"

Actually we have two ports acting like this, both are on the same director FDBEMF5C1 and in VSAN 500:

fc2/19 ficon 21 and fc3/16 ficon 40

both show ficon invalid and are not in the ficon flogi

How do I get these ports to act as proper ficon ports again?

Tkx,

Ivy

Michael Brown Tue, 11/23/2010 - 10:15
User Badges:
  • Cisco Employee,

Ivy,


When the ports show as F and not CU do they still work okay for the mainframe to access the control unit?  If so, what I suspect is happening is that the PWWN that is being used on that control unit is not known to the SAN-OS version to be a control unit.  If you can post a 'show flogi database vsan X' and indicate a working and a non-working interface I can confirm for you if this is a known issue.  Also, what version of SAN-OS and Fabric Manager are you using?


-Mike

ivybeccukbc Tue, 11/23/2010 - 22:56
User Badges:

Hello Mike,


The ports work OK with Mainframe.

The SAN Device Manager is 4.2(1b), Fabric Manager is 4.2(1b).


FDBEMF5C1# show flogi database vsan 500


--------------------------------------------------------------------------------

INTERFACE        VSAN    FCID           PORT NAME               NODE NAME      

--------------------------------------------------------------------------------



DASD 40-41

fc1/9                 500   0x650900       50:05:07:63:05:10:45:06      50:05:07:63:05:ff:c5:06 = CU

fc2/9                 500   0x652100       50:05:07:63:05:08:85:06      50:05:07:63:05:ff:c5:06 = F (should be CU)




DASD 44-45







fc2/16                500   0x652800       50:05:07:63:07:11:00:3f      50:05:07:63:07:ff:c0:3f = CU

fc3/16                500   0x654000       50:05:07:63:07:1c:40:3f      50:05:07:63:07:ff:c0:3f = F (should be CU)



The Node Names are the same!


Rgds,


Ivy

Michael Brown Wed, 11/24/2010 - 06:44
User Badges:
  • Cisco Employee,

Thanks Ivy,


Still investigating this for you.  One more favor, can you please post the output from a 'show fcns database vsan 500' for me?  If the output is large, you can prune out other ports, but I would like to see the entries for fc 1/9, 2/9, 2/16 and 3/16.  4.2(1b) is FICON certified by IBM.  4.2(7b) is the latest FICON certified code.


Also, what type of device is attached to the ports that show as F?  Are these the same nodes attached to the ports that show CU?


Thanks,

Mike

ivybeccukbc Wed, 11/24/2010 - 22:50
User Badges:

Hello Mike,


FDBEMF5C1# sh fcns database vsan 500

VSAN 500:
--------------------------------------------------------------------------
FCID        TYPE  PWWN                    (VENDOR)        FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0x650100    N     50:05:07:63:07:13:00:3f (IBM)           scsi-fcp FICON:CU f..
0x650300    N     50:05:07:63:07:13:40:3f (IBM)           scsi-fcp FICON:CU f..
0x650400    N     50:05:07:64:01:22:23:02 (IBM)           FICON:CH
0x650900    N     50:05:07:63:05:10:45:06 (IBM)           scsi-fcp FICON:CU f..
0x650a00    N     50:05:07:64:01:62:21:81 (IBM)           FICON:CH
0x650b00    N     50:05:07:63:04:00:00:5a (IBM)           scsi-fcp FICON:CU f..
0x650d00    N     50:05:07:64:01:66:22:c4 (IBM)           fcsb2-ch-cu fcsb..ch
0x651000    N     50:05:07:63:07:1c:00:3f (IBM)           scsi-fcp FICON:CU f..
0x651100    N     50:05:07:63:05:03:05:06 (IBM)           scsi-fcp FICON:CU f..
0x651300    N     50:05:07:64:01:22:2a:3e (IBM)           FICON:CH
0x651400    N     50:05:07:64:01:62:2a:3e (IBM)           FICON:CH
0x651600    N     50:05:07:64:01:26:20:e1 (IBM)           fcsb2-ch-cu fcsb..ch
0x651900    N     50:05:07:63:07:03:00:3f (IBM)           scsi-fcp FICON:CU f..
0x651b00    N     50:05:07:63:07:03:40:3f (IBM)           scsi-fcp FICON:CU f..
0x651c00    N     50:05:07:64:01:22:2a:61 (IBM)           FICON:CH
0x652100    N     50:05:07:63:05:08:85:06 (IBM)           scsi-fcp fcsb2-ch-cu
0x652200    N     50:05:07:64:01:62:2a:33 (IBM)           FICON:CH
0x652300    N     50:05:07:63:04:10:00:5a (IBM)           scsi-fcp FICON:CU f..
0x652500    N     50:05:07:64:01:66:22:b6 (IBM)           fcsb2-ch-cu fcsb..ch
0x652800    N     50:05:07:63:07:11:00:3f (IBM)           scsi-fcp FICON:CU f..
0x652900    N     50:05:07:63:05:08:05:06 (IBM)           scsi-fcp FICON:CU f..
0x652b00    N     50:05:07:64:01:22:2a:41 (IBM)           FICON:CH
0x652c00    N     50:05:07:64:01:62:29:f8 (IBM)           FICON:CH
0x652e00    N     50:05:07:64:01:26:12:41 (IBM)           fcsb2-ch-cu fcsb..ch
0x653100    N     50:05:07:63:07:10:00:3f (IBM)           scsi-fcp FICON:CU f..
0x653200    N     50:05:07:64:01:26:23:44 (IBM)           fcsb2-ch-cu fcsb..ch
0x653300    N     50:05:07:63:07:10:40:3f (IBM)           scsi-fcp FICON:CU f..
0x653400    N     50:05:07:64:01:22:2a:53 (IBM)           FICON:CH
0x653800    N     50:05:07:63:04:03:80:5a (IBM)           scsi-fcp FICON:CU f..
0x653a00    N     50:05:07:64:01:62:2a:42 (IBM)           FICON:CH
0x653b00    N     50:05:07:63:04:03:00:5a (IBM)           scsi-fcp FICON:CU f..
0x653d00    N     50:05:07:64:01:e2:21:81 (IBM)           FICON:CH
0x654000    N     50:05:07:63:07:1c:40:3f (IBM)           scsi-fcp fcsb2-ch-cu
0x654100    N     50:05:07:63:05:10:05:06 (IBM)           scsi-fcp FICON:CU f..
0x654300    N     50:05:07:64:01:22:2a:62 (IBM)           FICON:CH
0x654400    N     50:05:07:64:01:a6:22:c4 (IBM)           fcsb2-ch-cu fcsb..ch
0x654700    N     50:05:07:63:04:00:40:5a (IBM)           scsi-fcp FICON:CU f..
0x654900    N     50:05:07:63:07:00:00:3f (IBM)           scsi-fcp FICON:CU f..
0x654a00    N     50:05:07:64:01:26:23:af (IBM)           fcsb2-ch-cu fcsb..ch
0x654b00    N     50:05:07:63:07:00:40:3f (IBM)           scsi-fcp FICON:CU f..
0x654c00    N     50:05:07:64:01:e2:2a:62 (IBM)           FICON:CH
0x655000    N     50:05:07:63:04:13:80:5a (IBM)           scsi-fcp FICON:CU f..
0x655200    N     50:05:07:64:01:62:2a:61 (IBM)           FICON:CH
0x655300    N     50:05:07:63:04:13:00:5a (IBM)           scsi-fcp FICON:CU f..
0x655500    N     50:05:07:64:01:e2:21:8b (IBM)           FICON:CH
0x655800    N     50:05:07:63:07:11:40:3f (IBM)           scsi-fcp FICON:CU f..
0x655900    N     50:05:07:63:05:03:85:06 (IBM)           scsi-fcp FICON:CU f..
0x655b00    N     50:05:07:64:01:22:2a:12 (IBM)           FICON:CH
0x655c00    N     50:05:07:64:01:a6:22:b6 (IBM)           fcsb2-ch-cu fcsb..ch
0x655f00    N     50:05:07:63:04:10:40:5a (IBM)           scsi-fcp FICON:CU f..
0x656100    N     50:05:07:63:07:13:80:3f (IBM)           scsi-fcp FICON:CU f..
0x656300    N     50:05:07:63:07:10:80:3f (IBM)           scsi-fcp FICON:CU f..
0x656400    N     50:05:07:64:01:26:23:7c (IBM)           fcsb2-ch-cu fcsb..ch
0x656a00    N     50:05:07:64:01:66:20:e1 (IBM)           fcsb2-ch-cu fcsb..ch
0x656b00    N     50:05:07:63:04:00:80:5a (IBM)           scsi-fcp FICON:CU f..
0x656d00    N     50:05:07:64:01:e6:20:d6 (IBM)           fcsb2-ch-cu fcsb..ch
0x657100    N     50:05:07:63:05:03:45:06 (IBM)           scsi-fcp FICON:CU f..
0x657300    N     50:05:07:64:01:26:22:b6 (IBM)           FICON:CH fcsb2-ch-cu
0x657700    N     50:05:07:63:04:03:40:5a (IBM)           scsi-fcp FICON:CU f..
0x657900    N     50:05:07:63:07:03:80:3f (IBM)           scsi-fcp FICON:CU f..
0x657b00    N     50:05:07:63:07:00:80:3f (IBM)           scsi-fcp FICON:CU f..
0x657c00    N     50:05:07:64:01:26:22:ce (IBM)           fcsb2-ch-cu fcsb..ch
0x658200    N     50:05:07:64:01:66:12:41 (IBM)           fcsb2-ch-cu fcsb..ch
0x658300    N     50:05:07:63:04:10:80:5a (IBM)           scsi-fcp FICON:CU f..
0x658500    N     50:05:07:64:01:e6:20:e1 (IBM)           fcsb2-ch-cu fcsb..ch
0x658900    N     50:05:07:63:05:08:45:06 (IBM)           scsi-fcp FICON:CU f..
0x658b00    N     50:05:07:64:01:26:22:c4 (IBM)           FICON:CH fcsb2-ch-cu
0x658f00    N     50:05:07:63:04:13:40:5a (IBM)           scsi-fcp FICON:CU f..
0x65fe00    N     26:00:00:05:9b:78:fd:c2 (Cisco)         FICON:CUP
0x750200    N     50:05:07:63:07:1c:40:80 (IBM)           scsi-fcp FICON:CU f..
0x750800    N     50:05:07:63:05:03:04:fa (IBM)           scsi-fcp FICON:CU f..
0x750a00    N     50:05:07:63:06:08:03:0c (IBM)           scsi-fcp FICON:CU f..
0x750b00    N     50:05:07:63:07:10:00:80 (IBM)           scsi-fcp FICON:CU f..
0x750d00    N     50:05:07:63:03:00:03:fc (IBM)           scsi-fcp FICON:CU f..
0x750e00    N     50:05:07:64:01:a6:1b:d2 (IBM)           fcsb2-ch-cu fcsb..ch
0x751000    N     50:05:07:63:03:03:03:fc (IBM)           scsi-fcp FICON:CU f..
0x751400    N     50:05:07:63:07:13:00:80 (IBM)           scsi-fcp FICON:CU f..
0x751600    N     50:05:07:63:05:10:04:fa (IBM)           scsi-fcp FICON:CU f..
0x751700    N     50:05:07:64:01:e6:1c:63 (IBM)           fcsb2-ch-cu fcsb..ch
0x751a00    N     50:05:07:63:07:11:40:80 (IBM)           scsi-fcp FICON:CU f..
0x752000    N     50:05:07:63:05:03:44:fa (IBM)           scsi-fcp FICON:CU f..
0x752200    N     50:05:07:63:06:08:43:0c (IBM)           scsi-fcp FICON:CU f..
0x752300    N     50:05:07:63:07:10:40:80 (IBM)           scsi-fcp FICON:CU f..
0x752500    N     50:05:07:63:03:00:43:fc (IBM)           scsi-fcp FICON:CU f..
0x752600    N     50:05:07:64:01:a6:1c:83 (IBM)           fcsb2-ch-cu fcsb..ch
0x752800    N     50:05:07:63:03:03:43:fc (IBM)           scsi-fcp FICON:CU f..
0x752c00    N     50:05:07:63:07:13:40:80 (IBM)           scsi-fcp FICON:CU f..
0x752e00    N     50:05:07:63:05:10:44:fa (IBM)           scsi-fcp FICON:CU f..
0x752f00    N     50:05:07:64:01:e6:1c:77 (IBM)           fcsb2-ch-cu fcsb..ch
0x753200    N     50:05:07:63:07:01:00:80 (IBM)           scsi-fcp FICON:CU f..
0x753600    N     50:05:07:64:01:66:1c:70 (IBM)           FICON:CH fcsb2-ch-cu
0x753800    N     50:05:07:63:05:03:84:fa (IBM)           scsi-fcp FICON:CU f..
0x753a00    N     50:05:07:63:06:08:83:0c (IBM)           scsi-fcp FICON:CU f..
0x753b00    N     50:05:07:63:07:10:80:80 (IBM)           scsi-fcp FICON:CU f..
0x753d00    N     50:05:07:63:03:00:83:fc (IBM)           scsi-fcp FICON:CU f..
0x753e00    N     50:05:07:64:01:a6:1c:7f (IBM)           fcsb2-ch-cu fcsb..ch
0x754000    N     50:05:07:63:03:03:83:fc (IBM)           scsi-fcp FICON:CU f..
0x754400    N     50:05:07:63:07:13:80:80 (IBM)           scsi-fcp FICON:CU f..
0x754600    N     50:05:07:64:01:66:1c:63 (IBM)           fcsb2-ch-cu fcsb..ch
0x754700    N     50:05:07:64:01:26:1b:d2 (IBM)           FICON:CH fcsb2-ch-cu
0x754a00    N     50:05:07:63:07:0c:00:80 (IBM)           scsi-fcp FICON:CU f..
0x754e00    N     50:05:07:64:01:66:1c:7f (IBM)           FICON:CH fcsb2-ch-cu
0x755000    N     50:05:07:63:05:08:04:fa (IBM)           scsi-fcp FICON:CU f..
0x755200    N     50:05:07:63:06:08:c3:0c (IBM)           scsi-fcp FICON:CU f..
0x755300    N     50:05:07:63:07:00:00:80 (IBM)           scsi-fcp FICON:CU f..
0x755500    N     50:05:07:63:03:10:43:fc (IBM)           scsi-fcp FICON:CU f..
0x755600    N     50:05:07:64:01:a6:1c:70 (IBM)           fcsb2-ch-cu fcsb..ch
0x755800    N     50:05:07:63:03:13:03:fc (IBM)           scsi-fcp FICON:CU f..
0x755c00    N     50:05:07:63:07:03:00:80 (IBM)           scsi-fcp FICON:CU f..
0x755e00    N     50:05:07:64:01:66:1c:85 (IBM)           fcsb2-ch-cu fcsb..ch
0x755f00    N     50:05:07:64:01:26:1c:83 (IBM)           FICON:CH fcsb2-ch-cu
0x756200    N     50:05:07:63:06:03:03:0c (IBM)           scsi-fcp FICON:CU f..
0x756600    N     50:05:07:64:01:66:1b:d2 (IBM)           fcsb2-ch-cu fcsb..ch
0x756700    N     50:05:07:63:06:03:83:0c (IBM)           scsi-fcp FICON:CU f..
0x756800    N     50:05:07:63:05:08:44:fa (IBM)           scsi-fcp FICON:CU f..
0x756a00    N     50:05:07:63:07:00:40:80 (IBM)           scsi-fcp FICON:CU f..
0x756d00    N     50:05:07:63:03:10:03:fc (IBM)           scsi-fcp FICON:CU f..
0x757000    N     50:05:07:63:03:13:43:fc (IBM)           scsi-fcp FICON:CU f..
0x757400    N     50:05:07:63:07:03:40:80 (IBM)           scsi-fcp FICON:CU f..
0x757600    N     50:05:07:64:01:66:1c:78 (IBM)           fcsb2-ch-cu fcsb..ch
0x757700    N     50:05:07:64:01:26:1c:70 (IBM)           fcsb2-ch-cu fcsb..ch
0x757a00    N     50:05:07:63:06:03:43:0c (IBM)           scsi-fcp FICON:CU f..
0x757e00    N     50:05:07:64:01:66:1c:83 (IBM)           fcsb2-ch-cu fcsb..ch
0x757f00    N     50:05:07:63:06:03:c3:0c (IBM)           scsi-fcp FICON:CU f..
0x758000    N     50:05:07:63:05:08:84:fa (IBM)           scsi-fcp FICON:CU f..
0x758200    N     50:05:07:63:07:00:80:80 (IBM)           scsi-fcp FICON:CU f..
0x758500    N     50:05:07:63:03:10:83:fc (IBM)           scsi-fcp FICON:CU f..
0x758800    N     50:05:07:63:03:13:83:fc (IBM)           scsi-fcp FICON:CU f..
0x758c00    N     50:05:07:63:07:03:80:80 (IBM)           scsi-fcp FICON:CU f..
0x758e00    N     50:05:07:64:01:66:1c:bc (IBM)           fcsb2-ch-cu fcsb..ch
0x758f00    N     50:05:07:64:01:26:1c:7f (IBM)           fcsb2-ch-cu fcsb..ch
0x75fe00    N     22:00:00:05:9b:7a:ce:c2 (Cisco)         FICON:CUP

Total number of entries = 132
FDBEMF5C1#   ^C
FDBEMF5C1#

fc 1/9 and 2/9 are attached to an IBM DS8000 disk system (dasd 40-41)

fc 2/16 and 3/16 are attached to another IBM DS8000 disk system (dasd 44-45)


Kind regards,


Ivy

Michael Brown Mon, 11/29/2010 - 07:32
User Badges:
  • Cisco Employee,

It appears that the control unit did register correctly as an fcsb2 device per the name server entries.  The MDS will then use the RNID (request node ID) or QSA (query security attributes) to determine if the device is a CH or CU.  CU only sends RNID, while CH sends QSA and RNID.  I was not able to locate any open caveats that describe this issue on the MDS 4.2(1b).


Does this always occur on the same 2 ports or does it show on random ports?  Have these ports been flapped since this issue was observed and does the port still show F after the flap?  We may want to collect an fcanalyzer trace while the port is flapped so we can see the frame flow between the CU and the MDS.


If this is urgent, you may want to open a case with Cisco TAC.


- Mike

ivybeccukbc Tue, 11/30/2010 - 03:34
User Badges:

Hello,


It only hapens on these ports and on this director.

The other ports and directors are OK.


On 11 December there is an IODF (change weekend) and then the ports will

be toggled.


Rgds,


Ivy

Michael Brown Tue, 11/30/2010 - 08:26
User Badges:
  • Cisco Employee,

Ivy,


Is is possible that the configuration on those array ports are set up to support open systems?    When the ports are flapped, would it be possible to leave 1 problem port shutdown, while all the others are brought up.  Then we can start an fcanalyzer trace from the supervisor and bring up the problem port with the trace running?  This way we can collect the frames from the array and see if it is sending in the RNID as we are expecting.


Thanks,

Mike

Michael Brown Wed, 12/01/2010 - 10:28
User Badges:
  • Cisco Employee,

Ivy,


Can you send me the output from these commands please.


show fcns database detail | beg 650900


then hit ctrl + c to stop the display


show fcns database detail | beg 652100


then hit ctrl + c to stop the display


show fcns  database detail | beg 652800


then hit ctrl + c to stop the display


show fcns  database detail | beg 655400


then hit ctrl + c to stop the display


I would like to confirm that all devices are registered the same in the FC nameserver details.


Thanks,

Mike

Michael Brown Thu, 12/02/2010 - 08:08
User Badges:
  • Cisco Employee,

Hi Ivy,


I fat fingered the last FCID on you in my previous post.


It should have been


show fcns database detail | beg 654000


The other 3 should have provided some output.


What I am looking for is the detailed infomration from the nameserver for the 2 devices that show as FICON:CU and the 2 that show F.  There is no way to query the name server detailed display for a single FCID, so with the commands I posted, we can esentially query the entire database, but begin at a specified point, which is the FCIDs of the working and non working devices.


Thanks,

Mike

ivybeccukbc Thu, 12/02/2010 - 22:09
User Badges:

Hello Mik,


That's what I did.

I ran all the show... one after the other.

Have a close look.


Rgds,


Ivy

Michael Brown Fri, 12/03/2010 - 06:34
User Badges:
  • Cisco Employee,

Not my day Ivy...I missed the attachment ..doh!


I am investigating and will get back to you.


-Mike

ivybeccukbc Fri, 12/03/2010 - 06:41
User Badges:

Hello Mik,

I thank you for helping us!

Have a nice weekend,

Ivy

Michael Brown Mon, 12/06/2010 - 08:23
User Badges:
  • Cisco Employee,

I confirmed with engineering that the name server entry for FICON:CU is added as a result of the MDS sending RNID to the attaching device, and the ACC (accept frame) that is returned from the device contains data that the MDS uses to determine that the device is a control unit.  My guess here is that the attached ports did not send ACC to the MDS RNID, or the data in the ACC was not usable by the MDS to determine that the device is a CU.


I would recommend that you open a support case with your MDS support vendor and they can assisg with trace collection and anlysis to get to root cause.


-Mike

ivybeccukbc Tue, 12/07/2010 - 01:50
User Badges:

Hello Mike,


There is a EMC² Powerlink Service Request: 37638460 (10 November 2010)


This Saturday 11 December (IODF weekend) the ports will be toggled. (vary off, vary on)


Rgds,


Ivy

ivybeccukbc Mon, 12/13/2010 - 01:59
User Badges:

Problem solved!


Hello Mik,

I thank you for all the effort you put in this case!

The problem was solved this weekend. (IODF weekend)

As per your advice the ports were toggled and are now in "CU" state.

It was the IBM DS8000 DASD ports toggling that solved it.

Kind regards,

Ivy

Actions

This Discussion

 

 

Trending Topics: Storage Networking