Submirror 0: d31 State: Needs Maintenance Submirror 1: d32
metadetach d30 d32
metadetach -f d30 d32
metaclear d32
metastat -p
metainit -f d32 1 1 c0t1d0s5
metattach d30 d32
metastatgrep -i progress
Wednesday, August 19, 2009
Friday, August 14, 2009
Memory Errors after Firmware upgrade on T2000
On the T1000/T2000, when POST encounters a single CE, the associated DIMM is declared faulty and half of system's memory is deconfigured and unavailable for Solaris. Since PSH (Predictive Self-Healing) is the primary means for detecting errors and diagnosing faults on the Niagara platforms, this policy is too aggressive.
Steps to follow to resolve this issue ( Set diag level to minimum and reboot server)
sc> setsc diag_level min
sc> setsc diag_mode normal
sc>console -f
# shutdown -y -i6 -g0
Steps to follow to resolve this issue ( Set diag level to minimum and reboot server)
sc> setsc diag_level min
sc> setsc diag_mode normal
sc>console -f
# shutdown -y -i6 -g0
Thursday, August 13, 2009
/opt/SUNWexplo/bin/curl.sparc -T vmcore.0 https://supportfiles.sun.com/curl?file=CASE#-vmcore.0\&root=cores
If you want to upload a core files which are more than 2 GB, use above command
vmcore.0 - Local file name
CASE#-vmcore.0 - Destination file name
cores - Destination directory name
Choice of directories available on destination side.
* cores
* europe-cores/asouth/incoming
* europe-cores/ch/incoming
* europe-cores/de/incoming
* europe-cores/fr/incoming
* europe-cores/se/incoming
* europe-cores/uk/incoming
* iplanetcores
* explorer
* explorer-amer
* explorer-apac
* explorer-emea
If you want to upload a core files which are more than 2 GB, use above command
vmcore.0 - Local file name
CASE#-vmcore.0 - Destination file name
cores - Destination directory name
Choice of directories available on destination side.
* cores
* europe-cores/asouth/incoming
* europe-cores/ch/incoming
* europe-cores/de/incoming
* europe-cores/fr/incoming
* europe-cores/se/incoming
* europe-cores/uk/incoming
* iplanetcores
* explorer
* explorer-amer
* explorer-apac
* explorer-emea
Thursday, July 30, 2009
Clear Faults on Sun Fire2900
lom> showchs -b
lom>showchs -c /N0/SB0 -v
lom>service
lom[service]>setchs -s ok -r "Case#" -c /N0/RP2
lom[service]>setchs -s ok -r "Case#" -c /N0/SB0
Tuesday, July 21, 2009
Monday, July 13, 2009
Command to enable the disable component-Solaris
-> showcomponent
-> enablecomponent
-> clearasrdb
It will clear all disbled components
-> showcomponent
-> enablecomponent
-> clearasrdb
It will clear all disbled components
-> showcomponent
Friday, June 19, 2009
Below is SUN man page output for better understanding :
# fmdump -v -u d05a9f16-e969-4988-d340-dea1b54bd307TIME
UUID SUNW-MSG-IDAug 17 07:18:43.9562 d05a9f16-e969-4988-d340-dea1b54bd307 SUN4U-8000-2S100% fault.memory.dimmFRU: mem:///component=J0202rsrc: mem:///component=J0202
Once the DIMM(s) have been replaced, the command fmadm faulty should be run to see the status of the memory involved.
Example:
# fmadm faulty
STATE RESOURCE / UUID——– ———————————————————————-degraded mem:///component=J02029f32d247-869f-c9f2-949b-d9ec88b09640——– ———————————————————————-
Then fmadm repair should be run to remove the memory from the faulty list.
# fmadm repair mem:///component=J0202
fmadm: recorded repair to mem:///component=J0202
Verifying the results: After issuing the above commands, you can check the status of memory modules by issuing fmadm faulty command. this time it will not list any results.
# fmdump -v -u d05a9f16-e969-4988-d340-dea1b54bd307TIME
UUID SUNW-MSG-IDAug 17 07:18:43.9562 d05a9f16-e969-4988-d340-dea1b54bd307 SUN4U-8000-2S100% fault.memory.dimmFRU: mem:///component=J0202rsrc: mem:///component=J0202
Once the DIMM(s) have been replaced, the command fmadm faulty should be run to see the status of the memory involved.
Example:
# fmadm faulty
STATE RESOURCE / UUID——– ———————————————————————-degraded mem:///component=J02029f32d247-869f-c9f2-949b-d9ec88b09640——– ———————————————————————-
Then fmadm repair should be run to remove the memory from the faulty list.
# fmadm repair mem:///component=J0202
fmadm: recorded repair to mem:///component=J0202
Verifying the results: After issuing the above commands, you can check the status of memory modules by issuing fmadm faulty command. this time it will not list any results.
Subscribe to:
Posts (Atom)
Welcome to the UNIX world