Operating System - HP-UX
1748228 Members
4383 Online
108759 Solutions
New Discussion

Re: Change librairie MSL - fcmsutil older WWN

 
SOLVED
Go to solution
MiKL
Occasional Contributor

Change librairie MSL - fcmsutil older WWN

Hello,

I have 3 servers with HP-UX 11v2.
After a change of librairie MSL, the autoch and the driver are in NO_HW on 2 servers.
The "fcmsutil / dev / fcdx get remote" command sends back the older WWN.
On switch FC, the WWN is indeed the new and the zoning is correct.


On the 1st server the new WWN were directly detected by fcmsutil and the devices are CLAIMED.
I made a "rmsf -H" of the autoch and of tape and an "insf -e".Devices are not created.

 

The older on 2 servers:

$fcmsutil /dev/fcd1 get remote all

                    Target N_Port_id is = 0x160000
                           Target state = DSM_UNOPENED
                          Symbolic Name = HP Ultrium 4 Fibre Channel S/N-HU18524JB9 Port-0
                              Port Type = N_PORT
                          FCP-2 Support = YES
            Target Port World Wide Name = 0x500110a000933a42
            Target Node World Wide Name = 0x500110a000933a41

$fcmsutil /dev/fcd0 echo 0x150000
ERROR: Device with nport_id 0x150000 not found.

The new on the 1st server:

$fcmsutil /dev/td3 get remote all

                    Target N_Port_id is = 0x160000
                           Target state = DVS_READY
                          Symbolic Name = HP Ultrium 4 Fibre Channel S/N-HU18524JB9 Port-0
                              Port Type = N_PORT
   SLER Capable (supports Retry) = YES
            Target Port World Wide Name = 0x500110a0008e9d5a
            Target Node World Wide Name = 0x500110a0008e9d59

Thanks for your help.

4 REPLIES 4
Torsten.
Acclaimed Contributor

Re: Change librairie MSL - fcmsutil older WWN

What MSL model is it and what exactly has changed?


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
MiKL
Occasional Contributor

Re: Change librairie MSL - fcmsutil older WWN

A MSL 2024 LTO-4.

Torsten.
Acclaimed Contributor
Solution

Re: Change librairie MSL - fcmsutil older WWN

Did you replace the complete library chassis without rebooting the server?

 

Now the Lib has new WWNs.

 

Do a "ioscan" on the server and look into the syslog file.

 

It tells you to do a

 

# fcmsutil /dev/fcd__ replace_dsk 0x____ (nPort-ID)

 

the values are noted in the syslog file.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
MiKL
Occasional Contributor

Re: Change librairie MSL - fcmsutil older WWN

Thank's :smileywink:

 

$fcmsutil /dev/fcd0 replace_dsk 0x160000

$fcmsutil /dev/fcd0 get remote 0x160000 |grep 'World Wide Name'
            Target Port World Wide Name = 0x0000000000000000
            Target Node World Wide Name = 0x0000000000000000
$ioscan -fnH 0/0/4/1/0/4/0
$fcmsutil /dev/fcd0 get remote 0x160000 |grep 'World Wide Name'
            Target Port World Wide Name = 0x500110a0008e9d5a
            Target Node World Wide Name = 0x500110a0008e9d59