스토리지 MSA1000 nport ID 충돌 관련 문의드립니다.

[argares]

안녕하십니까.  

nport ID 변경 관련 문의드립니다.

syslog.lgo

Sep 30 12:26:24 TKDE vmunix: 0/5/2/0: WARNING: It appears that there are (or were) more than one device with
Sep 30 12:26:24 TKDE vmunix: the same address (nport ID) setting of 0x0. One of them will be ignored.
Sep 30 12:26:24 TKDE vmunix:
Sep 30 12:26:24 TKDE EMS [2703]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/TL_adapter/0_5_2_0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 177143815 -r /adapters/events/TL_adapter/0_5_2_0 -n 177143809 -a
Sep 30 12:32:29 TKDE vmunix: 0/5/2/0: WARNING: It appears that there are (or were) more than one device with
Sep 30 12:32:29 TKDE vmunix: the same address (nport ID) setting of 0x0. One of them will be ignored.

eventlog

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Sep 30 12:26:24 2013

TKDE sent Event Monitor notification information:

/adapters/events/TL_adapter/0_5_2_0 is >= 1.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time..........: Mon Sep 30 12:26:24 2013
Severity............: CRITICAL
Monitor.............: dm_TL_adapter
Event #.............: 52
System..............: TKDE

Summary:
Adapter at hardware path 0/5/2/0 : Found more than one device with the
same address (nport ID).

Description of Error:

lbolt value: -286160118

Address conflict encountered by device at nport id 0x0

Probable Cause / Recommended Action:

HA is the "hard address" (port ID), configured via a switch or
console, that the device is trying to acquire. Our adapter cards
themselves don't have hard addresses.
It appears that there are (or were) more than one device with the
same address (loop ID) setting. One of them will be ignored.
Look for two (or more) devices on the loop which have the reported
address setting.Change the address settings so that all devices on
the loop have a unique addresses, or remove the overlapping
devices.
Even after you change the address settings on the devices, it
may be necessary to reset or power-cycle both the devices whose
settings have been changed, and any remaining device with the
address setting which encountered the conflict.

Additional Event Data&colon;
System IP Address...: 000.00.00.000
Event Id............: 0x5248ef6000000000
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x5248ef6000000000
Additional System Data&colon;
System Model Number.............: 9000/800/rp4440
OS Version......................: B.11.11
EMS Version.....................: A.04.20
STM Version.....................: A.53.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#52

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v

Component Data&colon;
Physical Device Path....: 0/5/2/0
Vendor Id...............: 0x0000103C
Serial Number(WWN)......: 500110A00011953A

I/O Log Event Data&colon;

Driver Status Code..................: 0x00000034
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 61 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:
00000001 EEF18B0A 00000001 00000001 00000000 2F75782F 6B65726E 2F6B6973
752F544C 2F737263 2F636F6D 6D6F6E2F 7773696F 2F74645F 6465762E 63

rp4440  에 HP MSA1000 스토리지가 듀얼 광케이블로  연결되어있습니다.

포럼 검색해보니 N_port를 변경해보라는 글이 있는데

1. 아래의 방법으로 nport ID 를 변경 하는게 맞는지 문의 드립니다.

     #/opt/fcms/bin/fcmsutil /dev/td0 replace_dsk 0x01

2. 발생 원인 과

3. 해결 방법이 어떤게 있는지 문의 드립니다.

4. I/O 성능과 시스템 안정성에 미치는 영향 또한 문의 드립니다.

1.의 방법이 맞다면 저렇게 했을 경우 다른 문제발생 소지가 있는것들이 있는지요....

두서 없는 질의라 죄송하며 과련 로그 정보 첨부합니다...... 꾸뻑~