1832267 Members
6153 Online
110041 Solutions
New Discussion

Error on FC

 
Filosofo
Regular Advisor

Error on FC

hello....
we have upgrade the firmware of XP....and afther this operation whi see this error in syslog

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

and I see some disk in NO_HW

Idea?

Thank

Filo
Sistem engeneer expert
4 REPLIES 4
Ivan-Ho
Frequent Advisor

Re: Error on FC

Hi,

Pls try this command insf -H device_path

Good luck.
hung_phanduc
Steven E. Protter
Exalted Contributor

Re: Error on FC

World Wide Names are like NIC Mac addresses. This message seems to have indicated that your fiber card has either been swapped out or moved to a different bus position.

In this situation, any disk allocated to these cards must be re-assigned to the new World Wide Name.

If you have done anything with the Fibre cards, consider corrective action.

If the Firmware upgrade actually triggerred this, then run fcmsutil /dev/td0 (use a real driver) and set up your disk allocation and zoning again.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
G. Vrijhoeven
Honored Contributor

Re: Error on FC

Hi Filo,

IS is on one path or on both paths to the XP that you have lost your disks?

If it is on one path and it is coused by the firmware upgrade, you probebly have to re-arange your VG config. If it is on one path you can use the xpinfo -il command to check out the new device files.


Gideon
James Lynch
Valued Contributor

Re: Error on FC

The Fibre Channel driver uses the World Wide Name (WWN) as a way to keep track of the F/C devices it sees. When the Fibre Channel driver is initialized upon bootup, it creates a mapping of all of the F/C devices, the mapping contains the WWN and the physical hardware path. The F/C driver periodically performs a sanity check to make sure that all of the devices are at the same physical hardware paths. If the driver detects that the WWN for a given device has changed, the driver issues an error message and then denies access to the device. This is used to prevent devices i.e. disk drives from acidentally being pulled from one slot and then being placed into a different slot. You will get these messages when you replace a bad F/C disk drive.

In order to get around this you can either run the fcmsutil command with the "replace_dsk -l" or you can just reboot. The fcmsutil command tells the F/C driver to forget about the previous WWN mapping and recreate a new mapping. Basically, you're telling the F/C that you have made a hardware change and the change is correct. The reboot method works becuase these mappings are normally created upon bootup, so the F/C will assume that the mapping that it is creating is the correct one.

I suspect that when you upgraded the XP firmware, it caused a problem with the WWN mapping. I would try the fcmsutil command first. If that does not work than I would suggest a call to HP Support and speak to a H/W engineer, you could have experienced a H/W failure on one of your devices.

JL
Wild turkey surprise? I love wild turkey surprise!