adding FC10 disks

[dgizaw]

Hi,
I appriciate if any one can help me what should I do to add 4 disks on FC10 disk array hot. I excuted the following commands and got the results as shown below.
#fcmutil /dev/td0 devstat all |grep Loop
device Statistics for Nport_id 0x0000d5(Loop-id 10)
:
:
device Statistics for Nport_id 0x0000ef(Loop_id 0)
#fcmutil /dev/td1 devstat all |grep Loop

device Statistics for Nport_id 0x0000d5(Loop-id 10)
:
:
device Statistics for Nport_id 0x0000ef(Loop_id 0)

[Patrick Wallek · Accepted solution]

Have you already put the disks into the FC10?

If not, insert them and let them spin up and come online (the green light above the disk on the FC10 should be solid).

Then do an 'ioscan -fnC disk' and see if you see the disks.

It is possible that you may have to do an:

# fcmsutil /dev/td0 replace_dsk 0x??
# fcmsutil /dev/td1 replace_dsk 0x??

Where the 0x?? is the Nport ID of the disks you added. Check /var/adm/syslog/syslog.log for any errors with those disks. The NPORT IDs will be echoed there.

Once the disks show up in ioscan as CLAIMED you are set and can use them however you need to.

[dgizaw]

Thank you Patrick,
If I see the disks with ioscan that means I do not need to do the fcmsutil command?

Thanks

[Patrick Wallek]

If you can see the disks in ioscan and the are CLAIMED then you should be good.

You can always try a

# diskinfo /dev/rdsk/c?t?d0

(substitute the appropriate device file -- remember that diskinfo requires the /dev/rdsk file though)

If you get the appropriate output for the disk (model, size, etc.) then that is also a sign that everything is working.

[dgizaw]

Thank you very much Patrick. You gave me confidence to add the disks tomorrow without shutting the system down.


Thank you again

[Torsten.]

If you just *add* disks or devices to fibre channel, it's enough to insert the disk, ioscan and run an insf against it.

If you *replace* you have to run fcmsutil.

The reason is:

The new disk will have a different WWN and the same Nport_id. Your fc driver "thinks" there is something wrong. You have to tell him, it's OK to let the new disk in. Now you can either reboot the system *or*

- run ioscan (new disk will be NO_HW)
- take a look into syslog.log
- find the messages like

0/4/0/0: 'World-wide name' (unique identifier) for device at loop ID 0x05
has changed. If the device has been replaced intentionally, please use the
fcmsutil replace_dsk command to allow the new device to be used.

- now find the right /dev/tdx device and run fcmsutil, e.g.

# fcmsutil /dev/td0 replace_dsk 0x05

- run ioscan again and the device status will be changed from NO_HW to CLAIMED - ready to use