My Oracle Support Banner

Sun StorEdge[TM] T3+/6120/6320 logging excessive “unsupported opcode 35” messages when attached to Microsoft Windows 2000 hosts (Doc ID 1017619.1)

Last updated on SEPTEMBER 12, 2019

Applies to:

Sun Storage 6120 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 6320 System - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage T3 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage T3+ Array - Version Not Applicable to Not Applicable [Release N/A]
All Platforms

Symptoms

In multi-platform SAN configurations where Microsoft Windows 2000 systems are attached to Sun StorEdge[TM] T3+/6120 or 6320 arrays, it is possible for the array to log repeated OP 35 Invalid command opcode messages into the syslog file. In some cases the number of messages can be so high that they fill the entire log file, which means other important messages are lost.

Example:

Aug 04 07:36:04 FCC0[1]: N: u1ctr unsupported opcode 35 lun 4
Aug 04 07:36:04 FCC0[1]: N: u1ctr (ITL 9 0 4 TT 20 TID 4C28 OP 35) Invalid command opcode
Aug 04 07:36:22 FCC0[1]: WARNING: 30 messages were dropped

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.