Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Problem Resolution Sure Solution 1003518.1 : Resolving "NVRAM CRC Error: NVRAM Must be Reinitialized" on Sun StorEdge[TM] 3510 Array
PreviouslyPublishedAs 204945 Symptoms Though the occurence of this error is very low, this document will help to resolve the "NVRAM CRC Error! NVRAM must be reinitialized" error generated by the Sun StorEdge[TM] 3510 array hence referred as SE3510. Note: We have seen this issue happening with SE3510 but there is also a probability of this occurring even on SE3511 and SE3310. Resolution We may see the error message as below, only if we we have established a tip session with the SE3510 and when the SE3510 is reset or power cycled: "NVRAM CRC Error! NVRAM must be reinitialized." When this happens, the array looses all its customized settings including the lun maps. Normally, the customer would not be connected to the array using tip session, so the error may not be visible. But if the customer complains that he looses all the luns on the host and has to manually map the luns when he resets the array, then the error may be apparent. To confirm if the error is present, connect to the controller using tip and reset the array and check for the above error message. If you get the error message, follow the action plan below to resolve the problem. 1. Copy NVRAM to the disk with the procedure as below: From a Tip Session On the Firmware Menu --------------------------------------- a. Choose >system Functions> controller maintenance> save NVRAM to disks. Note: A confirmation dialog box appears. b. Choose Yes to confirm. Note: A prompt confirms that the NVRAM information has been successfully saved. 2. From the sccli, reset the nvram, example follows:- # sccli sccli: selected device /dev/rdsk/c1t216000C0FF8015C6d0s2 [SUN StorEdge 3510 SN#0015C6] sccli> reset nvram Following warning appears along with a confirmation prompt, press y. WARNING: The configuration of the array controller will be erased. Factory default parameters will take effect at next controller reset. Logical devices may not be accessible until mappings are reconfigured. Are you sure? y The NVRAM is reset and is on factory settings now. 3. Power cycle the SE3510 and see if the NVRAM error message still appears. 4. If it does not appear, please go to (6) below. 5. If the error still appears, replace the controller and send it for CPAS (Corrective Preventative Action System) and on the newly replaced controller we should not see the error and the problem should be resolved. Note: Please upgrade the controller firmware along with SES/PLD firmware on the newly replaced controller, if needed. 6. If the NVRAM error does not appear, copy the NVRAM from the disk back to the controller I.E. Restore NVRAM from disk as follows:- RESTORING THE NVRAM CONFIGURATION From a Tip Session on the Firmware Menu --------------------------------------- a. Choose >system Functions>Controller maintenance>Restore nvram from disks. Note: A confirmation message appears. b. Press Yes to confirm. Note: A prompt notifies you that the controller NVRAM data has been successfully restored from disks. 7. Check if everything works fine (we can reset the array and see if the error appears). Most likely, for this error, replacing the controller would only work but it may be worth trying to see if restoring NVRAM to factory defaults works thereby avoiding a controller replacement. Product Sun StorageTek 3511 SATA Array Sun StorageTek 3510 FC Array Sun StorageTek 3310 SCSI Array Sun StorageTek 3320 SCSI Array Internal Comments For Internal Sun Use Only Please see bug 5072698 Getting "NVRAM CRC Error! NVRAM must be reinitialized" on SE3510 while resetting. NVRAM, CRC, SE3510, sccli, reset Previously Published As 77390 Change History Date: 2004-07-15 User Name: C139400 Action: Approved Comment: corrected title, spelling, usage, format, taken out of first person, applied KE procedures Version: 0 Date: 2004-07-15 User Name: C139400 Action: Accepted Comment: Version: 0 Attachments This solution has no attachment |
||||||||||||
|