Document Audience: | INTERNAL |
Document ID: | I1146-1 |
Title: | StorEdge 6320 Systems with MIRE 1.2.3.1 Service Processor software will not complete an "unconfigure" operation. |
Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
Update Date: | 2004-12-10 |
____________________________________________________
*** Sun Confidential: Internal Use and Authorized VARs Only ***
__________________________________________________________________
This message including any attachments is confidential information
of Sun Microsystems, Inc. Disclosure, copying or distribution is
prohibited without permission of Sun. If you are not the intended
recipient, please reply to the sender and then delete this message.
__________________________________________________________________
FIELD INFORMATION NOTICE
(For Authorized Distribution by Sun Services)
FIN #: I1146-1
Synopsis: StorEdge 6320 Systems with MIRE 1.2.3.1 Service Processor software will not complete an "unconfigure" operation.Create Date: Dec/10/2004
SunAlert: No
Top FIN/FCO Report: No
Products Reference: Sun StorEdge 6320
Product Category: Storage / Array
Product Affected:
Systems Affected:
-----------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- SE6320 All Sun StorEdge 6320 -
X-Options Affected:
-------------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- - - - -
Parts Affected:
----------------------
Part Number Description Model
----------- ----------- -----
- - -
References:
BugID: 5089904
Issue Description:
-------------------------------------------------------------------------
| Change History: |
| =============== |
| Dec/10/04 Removed patches 115589-08, 116819-04 and replaced them with |
| M1.2.4. Added NOTE regarding Release 1.2.3.1. |
| |
-------------------------------------------------------------------------
An "unconfigure" operation on a StorEdge 6320 system with Service Processor
software version 1.2.3.1 will not successfully complete. As a result, customers
will be unable to change the IP address of the system.
NOTE: Release 1.2.3.1 was a point release for the factory only, and was never
released as a downloadable baseline image to the field. 1.2.3.1 fixed
a yield problem with the SPA tray that was severely limiting production.
1.2.3.1 is functionally identical to version 1.2.3 and only a small
number of systems shipped to the field with the 1.2.3.1 version
To determine the SP software release for the StorEdge 6320, log on to the SP
as root, and run "cat /etc/release". The release version is listed at the
bottom of the output.
This issue can occur when logging into the system as the setup user and
selecting Option 2 (unconfigure). A message similar to the following will
be written to the /var/tmp/se6000configure.log file.
DEB(21379): ERR: Default config file '/opt/SUNWse9ntcu/config.sys'
does not exist!
There is no other indication that the operation failed.
This issue results from a typo in the M1.2.3.1 release, causing the unconfigure
script to break. It is addressed by a simple workaround (see below) or by
installing the latest SP baseline image, M1.2.4 or later.
Implementation:
---
| | MANDATORY (Fully Proactive)
---
---
| X | CONTROLLED PROACTIVE (per Sun Geo Plan)
---
---
| | REACTIVE (As Required)
---
Corrective Action:
The following recommendation is provided as a guideline for authorized
Sun Services Field Representatives who may encounter the above
mentioned issue.
There are two ways to fix this issue for the StorEdge 6320:
1) Log on to the SP
a. Edit /usr/local/bin/ntc_config
b. Search for "9nt" and, if found, change to "nt".
c. Save changes.
Sample session:
[sp0]# cd /usr/local/bin
[sp0]# vi ntc_config
/9nt
if found
x
:wq
[sp0]# exit
Or
2) Install the latest SP Baseline Image, M1.2.4 or later.
See FIN I1072-1 for details on how to obtain the latest
baseline image.
Comments:
Remember that when using the vi editor through the NTC, Control-C
should be used instead of Escape (Esc).
________________________________________________________________________
NOTE: FIN Tracking Instructions for Radiance/SPWeb:
--------------------------------------------------
If a Radiance case involves the application of a FIN to solve a customer
issue, please complete the following steps in Radiance/SPWeb prior to
closing the case:
o Select "Field Information Notice" in the REFERENCE TYPE field.
o Enter FIN ID number in the REFERENCE ID field.
For example; I1111-1.
If possible, include additional details in the REFERENCE SUMMARY field
(ie. implementation complete, customer declined, etc.)
________________________________________________________________________
Implementation Notes:
--------------------
In case of "Mandatory" FINs, Sun Services will attempt to contact
all known customers to recommend proactive implementation.
For "Controlled Proactive" FINs, Sun Services mission critical
support teams will initiate proactive implementation efforts for
their respective accounts as required.
For "Reactive" FINs, Sun Services and partners will implement
the necessary corrective actions as the need arises.
Billing Information:
-------------------
Warranty: On-Site Labor Rates are based on specified Warranty deliverables
for the affected product.
Contract: On-Site Labor Rates are based on the type of service contract.
Non Contract: On-Site implementation by Sun is available based on On-Site
Labor Rates defined in the Price List.
________________________________________________________________________
All FIN documents are accessible via Internal SunSolve. Type "sunsolve"
in a browser and follow the prompts to Search Collections.
For questions on this document, please email:
finfco-manager@Sun.com
The FIN and FCO homepage is available at:
http://sdpsweb.central/FIN_FCO/index.html
For more information on how to submit a FIN, go to:
http://pronto.central/fin.html
To access the Service Partner Exchange, use:
https://spe.sun.com
________________________________________________________________________