syslog mesgs

[Ali Imran Abbas]

I am receiving following messages about the fcp interface in my syslog.log file.

Feb 3 23:43:10 usunx45 vmunix: 0/0/2/1/0/4/0: Device at device id 0x620513 has disappeared from Name Server GPN_FT
Feb 3 23:43:10 usunx45 vmunix: (FCP type) response, or its 'Port World-Wide Name' has changed.
Feb 3 23:43:10 usunx45 vmunix: device id = loop id, for private loop devices
Feb 3 23:43:10 usunx45 vmunix: device id = nport ID, for fabric/public-loop devices
Feb 3 23:43:10 usunx45 vmunix: System won't be able to see LUNs behind this port.
Feb 3 23:43:10 usunx45 vmunix:
Feb 3 23:43:10 usunx45 vmunix: 0/0/2/1/0/4/0: Device at device id 0x623013 has disappeared from Name Server GPN_FT
Feb 3 23:43:10 usunx45 vmunix: (FCP type) response, or its 'Port World-Wide Name' has changed.
Feb 3 23:43:10 usunx45 vmunix: device id = loop id, for private loop devices
Feb 3 23:43:10 usunx45 vmunix: device id = nport ID, for fabric/public-loop devices
Feb 3 23:43:10 usunx45 vmunix: System won't be able to see LUNs behind this port.
Feb 3 23:43:10 usunx45 vmunix:
Feb 3 23:43:16 usunx45 vmunix: 0/0/2/1/0/4/0: Device at device id 0x620d13 is back in Name Server GPN_FT (FCP type)
Feb 3 23:43:16 usunx45 vmunix: response, and its 'Port World-Wide Name' remains the same as
Feb 3 23:43:16 usunx45 vmunix: original.
Feb 3 23:43:16 usunx45 vmunix: device id = loop id, for private loop devices
Feb 3 23:43:16 usunx45 vmunix: device id = nport ID, for fabric/public-loop devices
Feb 3 23:43:16 usunx45 vmunix: System will be able to see LUNs behind this port
Feb 3 23:43:16 usunx45 vmunix: (might need to run 'ioscan' first).
Feb 3 23:43:16 usunx45 vmunix:
Feb 3 23:43:16 usunx45 vmunix: 0/0/2/1/0/4/0: Device at device id 0x620913 is back in Name Server GPN_FT (FCP type)
Feb 3 23:43:16 usunx45 vmunix: response, and its 'Port World-Wide Name' remains the same as
Feb 3 23:43:16 usunx45 vmunix: original.
Feb 3 23:43:16 usunx45 vmunix: device id = loop id, for private loop devices
Feb 3 23:43:16 usunx45 vmunix: device id = nport ID, for fabric/public-loop devices
Feb 3 23:43:16 usunx45 vmunix: System will be able to see LUNs behind this port
Feb 3 23:43:16 usunx45 vmunix: (might need to run 'ioscan' first).
Feb 3 23:43:16 usunx45 vmunix:
Feb 3 23:43:16 usunx45 vmunix: 0/0/2/1/0/4/0: Device at device id 0x620513 is back in Name Server GPN_FT (FCP type)
Feb 3 23:43:16 usunx45 vmunix: response, and its 'Port World-Wide Name' remains the same as
Feb 3 23:43:16 usunx45 vmunix: original.
Feb 3 23:43:16 usunx45 vmunix: device id = loop id, for private loop devices
Feb 3 23:43:16 usunx45 vmunix: device id = nport ID, for fabric/public-loop devices
Feb 3 23:43:16 usunx45 vmunix: System will be able to see LUNs behind this port
Feb 3 23:43:16 usunx45 vmunix: (might need to run 'ioscan' first).
Feb 3 23:43:16 usunx45 vmunix:

Any body has an idea how to resolve this problem?

[Steven E. Protter]

Shalom,

Options:
You don't have a problem the message indicates a new card.

Reboot the system, that runs ioscan and cleans out this stuff.

You have a card going bad and want to get it replaced quickly.

Your about a SITREP, situation report, or background, that includes OS, what has been done lately something like that. Then I won't have to guess.

SEP

[Torsten.]

> device has disappeared

> device is back

Did you change anything with the array or zoning config?

[Ali Imran Abbas]

We have a separate guy who manage san, I think I need to ask him. Should I forward this message to him?

[Bill Hassell · Accepted solution]

This is a VERY common error message when someone resets a tape drive or tape silo. What it means is that the device at 0/0/2/1/0/4/0 has been turned off, the cable pulled out, or physically removed and the fibre card is complaining that it disappeared. Modern fibre cards keep track of all the devices they see and complain when a device disappears. Try this command:

ioscan -knfH 0/0/2/1/0/4/0

and see what is there. If it is a tape drive, see if someone has been servicing the unit. This is one of the reasons that tapes need to have their own SAN switch so you can filter messages like this. Now if this is a disk, then you have more serious problems starting with someone playing with the fibre cables to a SAN admin changing zones or ports.