10-21-2010 03:55 AM
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
Solved! Go to Solution.
12-02-2010 08:08 AM
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
12-02-2010 10:09 PM
Hello Mik,
That's what I did.
I ran all the show... one after the other.
Have a close look.
Rgds,
Ivy
12-03-2010 06:34 AM
Not my day Ivy...I missed the attachment ..doh!
I am investigating and will get back to you.
-Mike
12-03-2010 06:41 AM
Hello Mik,
I thank you for helping us!
Have a nice weekend,
Ivy
12-06-2010 08:23 AM
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
12-07-2010 01:50 AM
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
12-13-2010 01:59 AM
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
12-13-2010 09:51 AM
Thanks for the update.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide