fcmsutil replace_dsk?? Please help!

[Tim Medford]

Greetings all. I am in the process of switching from one physical storage array to another, on an rp5470 running hpux 11.11. I have dual fibre channel cards.

I have these device files:
/dev/dsk/c14t0d0 (td0) 0/1/0/0
/dev/dsk/c15t0d0 (td1) 0/3/0/0

/dev/dsk/c14t0d1 (td0) 0/1/0/0
/dev/dsk/c15t0d1 (td1) 0/3/0/0

I have done vgreduce to all volume groups so that everything is channeled through c14t0dx and then I disabled the inactive card using fcmsutil /dev/td1 disable.

I unplugged the fibre from card at address 0/3/0/0 and plugged the new cable into it.

When I now re-enable the card at /dev/td1 and ran insf -e but the device files and hardware addresses look the same?? I'm getting a bunch of errors in the syslog saying use fcmsutil with the replace_dsk option.

I was expecting to see the new luns with new device file names.

Can you tell me which step(s) I missed?

Thanks!

[Uday_S_Ankolekar · Accepted solution]

You need to run /opt/fcms/bin/fcmsutil /dev/td(n) replace_dsk nportid command.

you will see nportid in syslog file.

-USA..

[Tim Medford]

Thanks Uday.

This is what is in the syslog, so it looks like the port ID is 0xef? This will not harm any of the luns/devices going through the other card at /dev/td0??


Apr 20 12:31:17 saifdev vmunix: 0/3/0/0: 'World-wide name' (unique identifier) for device at nport ID 0xef has
Apr 20 12:31:17 saifdev vmunix: changed. If the device has been replaced intentionally, please use the
Apr 20 12:31:17 saifdev vmunix: fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
Apr 20 12:31:17 saifdev vmunix: 0/3/0/0: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
Apr 20 12:31:17 saifdev vmunix: returned by nport ID 0xef. FLOGI/PLOGI Fail Code = 0x6.
Apr 20 12:31:17 saifdev vmunix:
Apr 20 12:31:17 saifdev vmunix: 0/3/0/0: Unable to access previously accessed device at nport ID 0xef.

[Uday_S_Ankolekar]

0xef is looks like your nport id.
Use replace_dsk command as mentioned above.

Have a look at this doc for more information

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062908600

-USA..

[Deoncia Grayson_1]

As Uday stated above use the fcmsutil replace_dsk to get rid of the syslog errors, but make sure you do it down both paths,

fcmsutil /dev/td0 replace_dsk 0xef

fcmsutil /dev/td1 replace_dsk 0xef

[Tim Medford]

Thanks everyone, the problem has been resolved.

Thanks to the miracle of ISEE a support engineer called right as I was getting ready to do this and we talked through the whole process.