VA7410 warning

[Jeff_Traigle]

We noticed one of our VA7410 with 3 attached DSA2405s has a warning status earlier today, but no amber LEDs. It's not manageable via Command View SDM as it stands now. ("Index Out of Bounds Error" when trying to use the GUI and "Error: Invalid slot: 128. Please retry." when trying to issue "armdsp -a" from the command line.)

The warning status is "Target Addressing Conflict". I'm not sure what this means. Each DS2405 has a unique ID and each LCC is set to the same ID on each DS2405. By connecting to the console port, I did see that JA2 has nothing in the identification column of the "dsp -f" output although it shows as good status. Maybe this is the culprit for the warning status?

Anyone seen this before and know how to resolve?

[Sameer_Nirmal]

The warning message might be related to and the caused by the blank ID colume of the JA2. The messages indicates a device at JA2 failed to aquire its address on the loop for some reason. Maybe it's the LCC issue.

I would check vfplog and "dsp -s" to see if they show something useful information about possible culprit.

[Jeff_Traigle]

Warning State > dsp -s

SUBSYSTEM SETTINGS:
Capacity Depletion Threshold: 0
Subsystem Level RAID Control: AutoRAID
Enable Manual Override: FALSE
Manual Override Destination: FALSE
Enable Optimize Policy: TRUE
Read Cache Disable: FALSE
Write Cache Enable: FALSE
Enable Prefetch: TRUE
Rebuild Priority: LOW
Unit Attention: TRUE
Disabl Sec Path Presentation: FALSE
Volume Set Partitioning: FALSE
Write Working Set Interval: 0x21C0

RESILIENCY SETTINGS
Enable Secure Mode: TRUE
Disable NVRAM on UPS Absent: FALSE
Disable NVRAM on WCE False: FALSE
Disable Read Hits: FALSE
Force Unit Access Response: 1
Lock Write Cache On: TRUE
Resiliency Threshold: 4 s
Single Controller Warning: TRUE

DISK SETTINGS
Auto Include: TRUE
Auto Rebuild: TRUE
Hot Spare Mode: Automatic
Max Drives per Subsystem: 105

LUN SETTINGS
LUN Creation Limit: 1024
Maximum LUN Creation Limit: 1024
Migrating Write Destination: FALSE
Security Enabled: TRUE

PORT SETTINGS
Controller 1 Host Port1
Loop ID: 110
Link Topology: Direct Fabric Attach
OS Behavior: HP-UX
Port WWN: 0x50060b000014ced8
Queue Full Threshold: 750
Data Rate: 2 GB/sec
Controller 1 Host Port2
Loop ID: 109
Link Topology: Direct Fabric Attach
OS Behavior: HP-UX
Port WWN: 0x50060b000014ced9
Queue Full Threshold: 750
Data Rate: 2 GB/sec
Controller 1 JBOD Port1
Data Rate: 2 GB/sec
Controller 1 JOBD Port2
Data Rate: 2 GB/sec
Controller 2 Host Port1
Loop ID: 108
Link Topology: Direct Fabric Attach
OS Behavior: HP-UX
Port WWN: 0x50060b000014b51c
Queue Full Threshold: 750
Data Rate: 2 GB/sec
Controller 2 Host Port2
Loop ID: 107
Link Topology: Direct Fabric Attach
OS Behavior: HP-UX
Port WWN: 0x50060b000014b51d
Queue Full Threshold: 750
Data Rate: 2 GB/sec
Controller 2 JBOD Port1
Data Rate: 2 GB/sec
Controller 2 JOBD Port2
Data Rate: 2 GB/sec

STATUS
Subsystem State: 1

The Subsystem is TESTING.
WARNINGS
Target Addressing Conflict

[Jeff_Traigle]

Not sure what the time basis and time stamp of the critical event being in 2145 means.

Warning State > log -p 1

Event Logs Report
Page Code: 1
Revision: 2
Current Controller Time: 12h:46m:25s, 9-0-2009
Time Basis: 9h:38m:4s, 6-12-2007
Page Length: 0x1cbb88

Entry 1
Event Type: 0x2
Sequence Number: 978342
Time Stamp: 15h:23m:24s, 6-10-2008
Module ID: 0x0b6
Controller SN: 00PR02146194
Process ID: 0x12d
Slot: 0x0
Event Length: 0x4b
Event Code: 0x1da
Loop Pair: 0x0
Enclosure ID: 0x1
Slot: 0x80
Component: 0xff
Event Unique Information:
Disk Drive Update Buffer Position 10 Status 0x01 Raw Data 0x011a0203
Warning State > log -ps 1

Event Logs Report
Page Code: 2
Revision: 2
Current Controller Time: 12h:46m:53s, 9-0-2009
Time Basis: 45h:25m:9s, 7-13-2145
Page Length: 0x37e68

Entry 1
Event Type: 0x1
Sequence Number: 399589
Time Stamp: 10h:29m:13s, 3-4-2008
Module ID: 0x016
Controller SN: 00PR02146194
Process ID: 0xffffffff
Slot: 0x0
Event Length: 0xe5
Event Code: 0x140
Count: 0x1
Enclosure ID: 0x0
Slot: 0x0
Component: 0x81
Subcomponent: 0xff
Event Unique Information:
Ckpt 0x160008: 0x00000000 ctlr 0 loop 1
backend: Scan Inquiry timeout
LoopID = 0x07, NPortID = 0xda byteLen = 0x000000ff
CDB = 0x00000000000000000000
Sense: 00/00/00/00 NumActive: 0 CurrTime: 0x07cae22f Launch: 0x07cae210
Warning State > log -pc 1

Event Logs Report
Page Code: 5
Revision: 2
Current Controller Time: 12h:47m:3s, 9-0-2009
Time Basis: 45h:25m:9s, 7-13-2145
Page Length: 0x8e8

Entry 1
Event Type: 0x1
Sequence Number: 404
Time Stamp: 45h:25m:9s, 7-13-2145
Module ID: 0x0ab
Controller SN: FAKE_SERIAL#
Process ID: 0xffffffff
Slot: 0x0
Event Length: 0xb
Event Code: 0x144
Count: 0x1
Enclosure ID: 0x0
Slot: 0x0
Component: 0xff
Subcomponent: 0xff
Event Unique Information:

[Jeff_Traigle]

Thought I'd bump this up to the top again with some additional information since I see I only pasted an old log entry in the previous post. Attached are the "log -ps" and "log -pc" entries that have occurred this month. We had a blip that caused some LVM errors on a few systems last night so there's some additional concern about the array.

[Disk Array_1]

This means that there're two disks with same hardware loop id. In this case one of the drives is being assigned "soft id". You can see it in the logs

Warnings:
39 (SOFT_ADDRESS_WARNING)

Have any disks been replaced recently?

BTW, non-manageability through command view is another problem, not related to this one. Just restart command view daemons.

[Jeff_Traigle]

Array has been decommissioned without resolution to these issues.