Sponsored Content
Full Discussion: T2000 - Fault at MB/FF_POK
Operating Systems Solaris T2000 - Fault at MB/FF_POK Post 302288074 by pupp on Monday 16th of February 2009 11:25:53 AM
Old 02-16-2009
i believe its easier to see through a showenvironment command.
 

10 More Discussions You Might Find Interesting

1. Solaris

t2000 DNS issue

I have an issue with DNS on a solaris t2000 When I set up the zones there was an issue with the /etc/resolv.conf, I had made a typo in my DNS server. I only noticed this after creating my new zones. I have corrected this in the global zone and I am now able to ping and nslookup inthe... (2 Replies)
Discussion started by: james dewitt
2 Replies

2. Solaris

T2000 - devfsadm problem

Hi everyone, I am having a problem when running devfsadm. We have many T2000, but on one of them, that is connected to our SAN, devfsadm reports no new disks. If a reconfiguration reboot is done, the system reports the new disk. But only with a reboot. We have Solaris10 installed and Veritas... (13 Replies)
Discussion started by: jfotop
13 Replies

3. Solaris

T2000 Hardware RAID

Hi, I have a root with hardware RAID on c0t0d0 and c0t2d0. I would like to set the boot device sequence in OBP for both hdds. I have checked in ls -l /dev/rdsk/ for the path of c0t2d0 but it does not exist. Can anyone shed some lights on this? AVAILABLE DISK SELECTIONS: 0.... (12 Replies)
Discussion started by: honmin
12 Replies

4. Solaris

SF T2000 prtdiag problem

Hi, a couple of T2000 servers did not show the component status and the output was too short. There was a patch that needed to be installed. I also updated to the latest recommended patch cluster and OBP patch. After reboot/restart of picl, it worked ok for a couple of weeks. Then suddenly it went... (12 Replies)
Discussion started by: incredible
12 Replies

5. Solaris

T2000 RAID Question

New to the boards here so please bear with me! I have a T2000 server with Solaris 10 installed on it. Disk 0 is the only disk currently being used, as I do NOT have a RAID set up. Disk 1 is just sitting there looking pretty. I'd like to set up a mirrored RAID in order to fully utilize both... (5 Replies)
Discussion started by: phi148
5 Replies

6. Solaris

T2000 Server cannot power on

Hi All, I recently had issues with my new T2000 server. I purchased a new mainboard and swapped the CPU and DIMMs to the new board. Now when i power on the server im unable to do so. I get the following error: ‘SC Alert: Host system poweron failed due to fault at MB/FF_POK.' When i do... (2 Replies)
Discussion started by: Caully
2 Replies

7. Solaris

Raid problem on T2000

Hi all, First post so be gentile :) It's my first time installing Solaris on T2000 server. I have 2 72GB HD's on it. After configuring HW raid and running raidctl command I get this output: bash-3.00# raidctl -l c0t0d0 Volume Size Stripe Status Cache RAID ... (2 Replies)
Discussion started by: Obi-Wan
2 Replies

8. Solaris

Sun T2000 question

This may be a stupid question, but I don't want to take any chances. I have a Sun T2000 in production. I want to run the "resetsc" command on the ALOM controller to active an IP address change. Will resetting ALOM affect the running OS? Thanks (2 Replies)
Discussion started by: soliberus
2 Replies

9. Emergency UNIX and Linux Support

T2000 Alom Upgrade

Hi guys! I need to upgrade the fw version of some T2000 servers, but unfortunately the image downloaded from the Oracle does not work...it seems that the image is not supported on the platform.. bash-3.00$ uname -a SunOS adm01 5.10 Generic_141414-07 sun4v sparc SUNW,Sun-Fire-T200... (5 Replies)
Discussion started by: cecco16
5 Replies

10. 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
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 03:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy