Sponsored Content
Full Discussion: M4000 fault
Operating Systems Solaris M4000 fault Post 302535619 by callmebob on Friday 1st of July 2011 09:52:17 AM
Old 07-01-2011
Sorted, rogue scsi cable causing, strange but once they were both unplugged it booted?????????
 

10 More Discussions You Might Find Interesting

1. Solaris

M4000 graphics card

Hi Guys, Anyone know any commands to verify the graphics card is installed correctly on an M4000? show-displays just comes back and echoes nothing. Also there is on input-device or output-device variable when you run printenv. This in itself is worrying. Any advice would be... (4 Replies)
Discussion started by: callmebob
4 Replies

2. UNIX for Dummies Questions & Answers

Help with restarting SUN m4000 server

I'm trying to power on our SUN m4000 server after a recent shutdown. When I try to connect to the xscf console I'm getting prompted for a password. The system is not asking for a login just a password. Below is the output from the xscf console. Anyone know how I can safely get back to the... (0 Replies)
Discussion started by: orahi001
0 Replies

3. Solaris

fmadm on an M4000

Hi people, Hoping someone has maybe done this before? I'm trying to run fmadm from the xcsf prompt on an M4000 and it won't run, complaining about insufficient privileges, even though the user has supposedly been setup with fieldeng privileges. Anyone got any ideas? Cheers Rgrds... (10 Replies)
Discussion started by: callmebob
10 Replies

4. Solaris

Single maintence mode cannot run any command on M4000

Hii All I was building two M4000 servers and one was successfully installed. Other one /usr has been unmounted. my putty session got disconnected and i connected to console where it asked for root single maintence # # init 0 not foung # df -h not found # xscf>poweroff -a xscf>... (8 Replies)
Discussion started by: seems
8 Replies

5. Solaris

M4000 Server Issue

Dear Team, This time i am facing some problems in Sun SPARC M4000 server. I have a doubt, when we are upgrading the firmware if XSCF , the OBP is also upgraded. What about server OBP, Is that upgardation need to be done separately ? what about DVD-ROM, HARD DISK firmware.... (3 Replies)
Discussion started by: sudhansu
3 Replies

6. Solaris

M4000 Memory Fault

Hi Guys and Gals, Does anyone know how to track down a faulty DIMM on the memory board of an M4000? showhardconf tells me which board it is, but was wondering if there was a way to track it down to a DIMM? Thanks in advance Martin (5 Replies)
Discussion started by: callmebob
5 Replies

7. Programming

Using gdb, ignore beginning segmentation fault until reproduce environment segmentation fault

I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this : i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ... (6 Replies)
Discussion started by: pooyair
6 Replies

8. Solaris

M4000 Mode Switch

Hello, I'm set to go out to our M4000 to reset the XSCF password, since the person who set it up doesn't remember what password they setup. I have all the steps, but the only question I can't find an answer to is around the mode switch. Right now, based on prtdiag, the mode switch is in... (2 Replies)
Discussion started by: QuickNull
2 Replies

9. Solaris

CPU/processor/cores in M4000

Hi Gurus Can someone help me in explaining the below outputs . psrinfo -p 4 /usr/sbin/psrinfo -pv The physical processor has 4 virtual processors (0-3) SPARC64-VI (portid 1024 impl 0x6 ver 0x93 clock 2150 MHz) The physical processor has 4 virtual processors (8-11) SPARC64-VI... (3 Replies)
Discussion started by: ningy
3 Replies

10. Solaris

How to Display M4000 XSCF IP from Solaris OS?

Hi All, I have an Oracle M4000 server with Solaris 10 OS. I have access to Solaris root prompt. But I don't know the XSCF IP of this server. Is there any way to display XSCF IP from Solaris OS? (2 Replies)
Discussion started by: byrusber
2 Replies
fmd(1M) 						  System Administration Commands						   fmd(1M)

NAME
fmd - fault manager daemon SYNOPSIS
/usr/lib/fm/fmd/fmd [-V] [-f file] [-o opt=val] [-R dir] DESCRIPTION
fmd is a daemon that runs in the background on each Solaris system. fmd receives telemetry information relating to problems detected by the system software, diagnoses these problems, and initiates proactive self-healing activities such as disabling faulty components. When appro- priate, the fault manager also sends a message to the syslogd(1M) service to notify an administrator that a problem has been detected. The message directs administrators to a knowledge article on Sun's web site, http://www.sun.com/msg/, which explains more about the problem impact and appropriate responses. Each problem diagnosed by the fault manager is assigned a Universal Unique Identifier (UUID). The UUID uniquely identifes this particular problem across any set of systems. The fmdump(1M) utility can be used to view the list of problems diagnosed by the fault manager, along with their UUIDs and knowledge article message identifiers. The fmadm(1M) utility can be used to view the resources on the system believed to be faulty. The fmstat(1M) utility can be used to report statistics kept by the fault manager. The fault manager is started automatically when Solaris boots, so it is not necessary to use the fmd command directly. Sun's web site explains more about what capabilities are cur- rently available for the fault manager on Solaris. OPTIONS
The following options are supported -f file Read the specified configuration file prior to searching for any of the default fault manager configuration files. -o opt=value Set the specified fault manager option to the specified value. Fault manager options are currently a Private interface; see attributes(5) for information about Private interfaces. -R dir Use the specified root directory for all pathnames evaluated by the fault manager, instead of the default root (/). -V Print the fault manager's version to stdout and exit. EXIT STATUS
The following exit values are returned: 0 Successful completion 1 An error occurred which prevented the fault manager from initializing, such as failure to open the telemetry transport. 2 Invalid command-line options were specified. FILES
/etc/fm/fmd Fault manager configuration directory /usr/lib/fm/fmd Fault manager library directory /var/fm/fmd Fault manager log directory ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWfmd | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), fmadm(1M), fmdump(1M), fmstat(1M), syslogd(1M), attributes(5), smf(5) http://www.sun.com/msg/ NOTES
The Fault Manager is managed by the service management facility, smf(5), under the service identifier: svc:/system/fmd:default The service's status can be queried using the svcs(1) command. Administrators should not disable the Fault Manager service. SunOS 5.11 17 Nov 2004 fmd(1M)
All times are GMT -4. The time now is 11:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy