syslog error

[kunjuttan]

Hi all,
I am getting a following error in syslog file.Pls suggest..

Jun 28 23:55:17 BILPBI vmunix: 1/0/12/1/0: 'World-wide name' (unique identifier) for device at nport ID 0x10200 has
Jun 28 23:55:17 BILPBI vmunix: changed. If the device has been replaced intentionally, please use the
Jun 28 23:55:17 BILPBI vmunix: fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
Jun 28 23:55:17 BILPBI vmunix: 1/0/12/1/0: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
Jun 28 23:55:17 BILPBI vmunix: returned by nport ID 0x10200. FLOGI/PLOGI Fail Code = 0x6.
Jun 28 23:55:17 BILPBI vmunix:
Jun 28 23:55:17 BILPBI vmunix: 1/0/12/1/0: Unable to access previously accessed device at nport ID 0x10200.
Jun 28 23:55:17 BILPBI vmunix: 1/0/12/1/0: 'World-wide name' (unique identifier) for device at nport ID 0x10300 has
Jun 28 23:55:17 BILPBI vmunix: changed. If the device has been replaced intentionally, please use the
Jun 28 23:55:17 BILPBI vmunix: fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
Jun 28 23:55:17 BILPBI vmunix: 1/0/12/1/0: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
Jun 28 23:55:17 BILPBI vmunix: returned by nport ID 0x10300. FLOGI/PLOGI Fail Code = 0x6.
Jun 28 23:55:17 BILPBI vmunix:
Jun 28 23:55:17 BILPBI vmunix: 1/0/12/1/0: Unable to access previously accessed device at nport ID 0x10300.
Jun 28 23:55:17 BILPBI EMS [4698]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/TL_adapter/1_0_12_1_0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 307888149 -r /adapters/events/TL_adapter/1_0_12_1_0 -n 307888161 -a
Jun 28 23:55:17 BILPBI EMS [4698]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/TL_adapter/1_0_12_1_0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 307888149 -r /adapters/events/TL_adapter/1_0_12_1_0 -n 307888162 -a
Jun 28 23:55:17 BILPBI EMS [4698]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/TL_adapter/1_0_12_1_0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 307888149 -r /adapters/events/TL_adapter/1_0_12_1_0 -n 307888163 -a
Jun 28 23:55:19 BILPBI vmunix: 1/0/14/1/0: 'World-wide name' (unique identifier) for device at nport ID 0x11700 has
Jun 28 23:55:19 BILPBI vmunix: changed. If the device has been replaced intentionally, please use the
Jun 28 23:55:19 BILPBI vmunix: fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
Jun 28 23:55:19 BILPBI vmunix: 1/0/14/1/0: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
Jun 28 23:55:19 BILPBI vmunix: returned by nport ID 0x11700. FLOGI/PLOGI Fail Code = 0x6.
Jun 28 23:55:19 BILPBI vmunix:
Jun 28 23:55:19 BILPBI vmunix: 1/0/14/1/0: Unable to access previously accessed device at nport ID 0x11700.
Jun 28 23:55:19 BILPBI vmunix: 1/0/14/1/0: 'World-wide name' (unique identifier) for device at nport ID 0x11800 has
Jun 28 23:55:19 BILPBI vmunix: changed. If the device has been replaced intentionally, please use the
Jun 28 23:55:19 BILPBI vmunix: fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
Jun 28 23:55:19 BILPBI vmunix: 1/0/14/1/0: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
Jun 28 23:55:19 BILPBI vmunix: returned by nport ID 0x11800. FLOGI/PLOGI Fail Code = 0x6.
Jun 28 23:55:19 BILPBI vmunix:
Jun 28 23:55:19 BILPBI vmunix: 1/0/14/1/0: Unable to access previously accessed device at nport ID 0x11800.
Jun 28 23:55:19 BILPBI EMS [4698]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/TL_adapter/1_0_14_1_0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 307888154 -r /adapters/events/TL_adapter/1_0_14_1_0 -n 307888164 -a
Jun 28 23:55:19 BILPBI EMS [4698]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/TL_adapter/1_0_14_1_0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 307888154 -r /adapters/events/TL_adapter/1_0_14_1_0 -n 307888165 -a
Jun 28 23:55:19 BILPBI EMS [4698]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/TL_adapter/1_0_14_1_0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 307888154 -r /adapters/events/TL_adapter/1_0_14_1_0 -n 307888166 -a

[Torsten.]

>> Jun 28 23:55:17 BILPBI vmunix: 1/0/12/1/0: Unable to access previously accessed device at nport ID 0x10200.
Jun 28 23:55:17 BILPBI vmunix: 1/0/12/1/0: 'World-wide name' (unique identifier) for device at nport ID 0x10300 has
Jun 28 23:55:17 BILPBI vmunix: changed. If the device has been replaced intentionally, please use the
Jun 28 23:55:17 BILPBI vmunix: fcmsutil(1M) command's replace_dsk option to allow the new device to be used.





Any recent changes like a replaced FC disk or tape?

[madhuchakkaravarthy]

hi

r u doing any zoning in switches.

regards

MC

[kunjuttan]

nothing done..

[Torsten.]

Could you send an "ioscan -fn" please? What is on path 1/0/12/1/0?

[madhuchakkaravarthy]

hi

fcmsutil /dev/fcd0 get remote [local N_port_id]

check with other server some thing might be mismatched

regards

MC

[Vijaykumar_1]

Execute this to get the event logs,

/opt/resmon/bin/resdata -R 307888154 -r /adapters/events/TL_adapter/1_0_14_1_0 -n 307888164 -a

Also check with ioscan if the device exists,

ioscan -fnH 0/14/1/0

[stephen peng]

I met this situation when I replaced a fault controller of a va7400 in SAN enviroment, and I consider it was similiar to what you met. If you ioscan 1/0/12/1/0, LUNs on this path should be NO_HW.
I followed hints at syslog.log, fcmsutil /dev/td*(HBA at 1/0/12/1/0) replace_dsk 0x10200
to fix it. then it worked fine.

[stephen peng]

first of all, get it clear what has changed in the SAN enviroment!

[Elmar P. Kolkman]

It looks like something fundamentally has changed in your environment, for instance settings on the fibrechannel switches. Because you have 2 adapters and both have problems accessing the devices.

Try to do the 'replace_dsk' for some of the devices to see if that solves the issue, but also take time to talk to your colleagues who have been at work at the moment these messages started to occur... Probably someone has some info to share...