Sponsored Content
Full Discussion: Hardware problem diagnosing
Operating Systems Solaris Hardware problem diagnosing Post 302284799 by pupp on Friday 6th of February 2009 10:44:43 AM
Old 02-06-2009
few options here...

diag levels at the OBP.

at the os level, look through dmesg (/var/adm/messages). look at fmstat and fmdump. if you have a sc you can view logs and xscf can use fmstat as well. if there are any 3rd party devices that you think may have failed, look at their website and see if they have any utilities.

what exactly is your problem?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

PCMCIA Hardware Problem

Hi, I have a Dell Inspiron 4000 that I am using to run Redhat Linux 7.1. This machine had 128Mb of RAM in it, and I upgraded to 512Mb. Since this, the PCMCIA cards have disappeared from the system running under Linux, although they still work under windows and the file "/var/lib/pcmcia/stab"... (1 Reply)
Discussion started by: ghoti
1 Replies

2. Solaris

hardware problem?

Can someone tell me what the following means? We have a v440 running Solaris 9. What do the patterns actually mean? May 17 12:12:03 ibasdb02 cediag: Revision: 1.78 @ 2005/02/11 15:5 :29 UTC May 17 12:12:03 ibasdb02 cediag: Analysed System: SunOS 5.9 with UP 117171-17 (MPR active) May 17... (5 Replies)
Discussion started by: hshapiro
5 Replies

3. UNIX for Advanced & Expert Users

Hardware HBA problem

I have worked with Qlogic (Sun) fiber cards a lot and with Emulex fiber cards only a little. Here is the scenario: I have a Sun 490 with 3 Emulex cards in it. A pair are for the 6120 array that is attached, the other is a direct attach so our SAN for Veritas Netbackup to back up the system.I... (0 Replies)
Discussion started by: lm_admin_dh
0 Replies

4. Solaris

Hardware Raid related problem

Dear All I would Like to know that if suppose c1t0d0 is of 72 gb hard disk and system boot from this hard disk and c1t1d0 is of 147gb hard disk. Can we implement hardware raid (Mirror) between these two hard disks of different capacity if raid crontroller is present in the server Kind regards (4 Replies)
Discussion started by: girish.batra
4 Replies

5. Solaris

problem in finding a hardware problem

Hi I am right now facing a strange hardware problem. System get booted with the following error: Fatal Error Reset CPU 0000.0000.0000.0003 AFSR 0100.0000.0000.0000 SCE AFAR 0000.07c6.0000.1000 SC Alert: Host System has Reset It happen 4 or 5 times and get the same error every time.I... (8 Replies)
Discussion started by: girish.batra
8 Replies

6. Linux

Hardware problem diagnosing

Hey guys how to do diagnose Linux for hardware problems/issues. This is a general question for all common hardware components under Linux server. (1 Reply)
Discussion started by: sbn
1 Replies

7. HP-UX

Hardware problem diagnosing

Hey guys how to do diagnose HP-UX for hardware problems/issues. This is a general question for all common hardware components under HP-UX server. (4 Replies)
Discussion started by: sbn
4 Replies

8. Solaris

Sun Fire v440 hardware problem (can't get ok>)

First of all it's shut down 60 second after power on and write on console : SC Alert: Correct SCC not replaced - shutting managed system down! This is cured by moving out battery from ALOM card. Now server start to loop during the testing. That's on the console: >@(#) Sun Fire V440,Netra... (14 Replies)
Discussion started by: Alisher
14 Replies

9. Solaris

Hardware Problem

Dear: the Cureent PC Dell GX620 the Current Hardware 4 GB ram 80 HDD what i do remove old 4GB ram and install 8 GB remove old HDD and install new on 160GB try to install the Unix Sun Solaris after booting and when arrive to step which i should select interactive error meg... (7 Replies)
Discussion started by: hosney00ux
7 Replies

10. Solaris

Hardware faulty, but which hardware?

Hi folk, I have this hardware faunty message, but dont know which hardware is this ? can you guide me ? --------------- ------------------------------------ -------------- --------- TIME EVENT-ID MSG-ID SEVERITY ---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies
fmstat(1M)                                                System Administration Commands                                                fmstat(1M)

NAME
fmstat - report fault management module statistics SYNOPSIS
fmstat [-asz] [-m module] [interval [count]] DESCRIPTION
The fmstat utility can be used by administrators and service personnel to report statistics associated with the Solaris Fault Manager, fmd(1M) and its associated set of modules. The Fault Manager runs in the background on each Solaris system. It receives telemetry informa- tion relating to problems detected by the system software, diagnoses these problems, and initiates proactive self-healing activities such as disabling faulty components. You can use fmstat to view statistics for diagnosis engines and agents that are currently participating in fault management. The documenta- tion for fmd(1M), fmadm(1M), and fmdump(1M) describes more about tools to observe fault management activities. If the -m option is present, fmstat reports any statistics kept by the specified fault management module. The module list can be obtained using fmadm config. If the -m option is not present, fmstat reports the following statistics for each of its client modules: module The name of the fault management module, as reported by fmadm config. ev_recv The number of telemetry events received by the module. ev_acpt The number of events accepted by the module as relevant to a diagnosis. wait The average number of telemetry events waiting to be examined by the module. svc_t The average service time for telemetry events received by the module, in milliseconds. %w The percentage of time that there were telemetry events waiting to be examined by the module. %b The percentage of time that the module was busy processing telemetry events. open The number of active cases (open problem investigations) owned by the module. solve The total number of cases solved by this module since it was loaded. memsz The amount of dynamic memory currently allocated by this module. bufsz The amount of persistent buffer space currently allocated by this module. The fmstat utility requires the user to posses the SYS_CONFIG privilege. Refer to the System Administration Guide: Security Services for more information about how to configure Solaris privileges. OPTIONS
The following options are supported: -a Print all statistics for a module, including those kept on its behalf by fmd. If the -a option is not present, only those statistics kept by the module are reported. If the -a option is used without the -m module, a set of global statistics associated with fmd are displayed. -m module Print a report on the statistics associated with the specified fault management module, instead of the default statistics report. Modules can publish an arbitrary set of statistics to help Sun service the fault management software itself. The module statistics constitute a Private interface. See attributes(5) for information on Sun's rules for Private interfaces. Scripts should not be written that depend upon the values of fault management module statistics as they can change without notice. -s Print a report on Soft Error Rate Discrimination (SERD) engines associated with the module instead of the default module statistics report. A SERD engine is a construct used by fault management software to determine if a statistical threshold measured as N events in some time T has been exceeded. The -s option can only be used in combination with the -m option. -z Omit statistics with a zero value from the report associated with the specified fault management module. The -z option can only be used in combination with the -m option. OPERANDS
The following operands are supported: count Print only count reports, and then exit. interval Print a new report every interval seconds. If no interval and no count are specified, a single report is printed and fmstat exits. If an interval is specified but no count is speci- fied, fmstat prints reports every interval seconds indefinitely until the command is interrupted. EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 A fatal error occurred. A fatal error could be the failure to communicate with fmd(1M). It could also be that insufficient privi- leges were available to perform the requested operation. 2 Invalid command-line options were specified. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWfmd | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ The command-line options are Evolving. The human-readable default report is Unstable. The human-readable module report is Private. SEE ALSO
fmadm(1M), fmd(1M), fmdump(1M), attributes(5) System Administration Guide: Security Services SunOS 5.10 8 Mar 2004 fmstat(1M)
All times are GMT -4. The time now is 04:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy