Home > Error Failed > Error Failed To Send A Fma Eventrc=-1

Error Failed To Send A Fma Eventrc=-1

Contents

Modifications to ILOM Serial Port Configurations Might Not Be Saved, or Change Unexpectedly (6632937) The ILOM service processor provides the capability to customize the speed of external and server serial ports. zpool status -v pool: pool1 state: ONLINE scrub: resilver completed with 0 errors on Mon Feb 18 11:23:13 2008 config: NAME STATE READ WRITE CKSUM pool1 ONLINE 0 0 0 mirror And I'm happy to report that Solaris' Predictive Self Healing feature (also known as the Fault Management Architecture (FMA)) has been extended to include coverage for T2 Plus. I couldn't find any documentation about ereports on Sun website. http://invictanetworks.net/error-failed/error-failed-to-send-a-fma-eventrc-11.html

This blog will contain information about all three, but primarily focused on topics for Solaris system administrators. This message was reported from the XML Service at address https://xendesktopcontroller:443/scripts/wpnbr.dll [NFuseProtocol.TRequestAppData]. On the X4140 Server, e-mail alerts are not sent. action: Restore the file in question if possible. http://comments.gmane.org/gmane.os.solaris.opensolaris.sysadmin/3420

Error Failed To Send A Fma Eventrc=-1

But here's the magic. Workaround: If this message is encountered, press F1 to allow the system to continue with the boot process. Sometime the server hangs, and we are unable to logon on the server. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'.

action: Wait for the resilver to complete. I restarted the fmd. Again we will access the pool and then consult fmstat to see what is happening (are you noticing a pattern here????). # rm -f /dev/dsk/disk2 # cd /pool1 # find . Error handling and diagnosis have been enhanced to detect and diagnose errors (single-lane/multi-lane/protocol errors) on the coherency plane.

IMPACT: The system's capacity to correct transmission errors between CPU chips has been reduced. In the past we've looked at combinations such as ZFS and Zones or Service Management, Role Based Access Control (RBAC) and Least Privilege. However I was thinking that I might see them in fmdump -e but I don't. But the key point in Isaac's multiplicity discussion is how the cornucopia of Solaris features work together to do some pretty spectacular (and competitively differentiating) things.

All others do not. What does rc=-1 signify? Refer to http://sun.com/msg/ZFS-8000-GH for more information. Do you have or know any documentation about these ereports?

I found some reference that these alerts (dsc, dac) needs to ignored but couldn't find the patch. ===>> not sure about the exact patch id. All Rights Reserved. Error Failed To Send A Fma Eventrc=-1 Device spare1 will spare both pools in case of a problem - which we are about to inflict upon the pools. # zpool create pool1 mirror disk1 disk2 spare spare1 # For the resolution, see “(RHEL 4.5) Sun Fire X4240/X4440 Quad-Core Systems Have Hypertransport Sync Flood Error Under High IO Load (6682186)” on page 30.

BIOS and ILOM Display Different System GUID (6650248) The IPMI specification provides for a System GUID (Globally Unique Identifier) which uniquely identifies the server and is viewable through the server’s ILOM. useful reference Hence you are getting the error message from SC - SC Alert: [ID 599537 daemon.error] Chassis | major:ERROR: Failed to send a fma event(rc=-1) ereport.cpu.ultraSPARC-T2.dac Simple solution for this problem could No SNMP Trap Sent When a Sensor Event Occurs (6675315) The ILOM service processor provides alert mechanisms when events occur. If the SNMP alert functionality cannot be enabled, use one of the following alternate alert mechanisms: IPMI pet traps E-mail alerts (for the Sun Fire X4240 and X4440).

feature is turned on. IMPACT: System performance may be impacted. I haven't explored the FMA test harness enough to know if there is anything in there that would make a good lab. my review here Problem 1: Simple data corruption Time to inflict some harm upon the pool.

Workaround: You can safely ignore information for fan module 3 (fm3) on models which do not support it. The Service Processor reports the correct product name. I restarted the fmd.

Workaround: Use the server’s BIOS Setup to change the mode for the onboard NICs to “MAC Bridge mode.” Solaris FMA Might Report Inaccurate PCI-e Slot Number Information (6653828) For PCI-e cards

Categories Better Developers HomeArchived ForumsXMLJava Server Pages (JSP)DesignerSample CodeDatabase InstallationiSQL*Plus [ARCHIVE]Globalization SupportOracle CommunityAdvanced QueueingOracle Application Exp...User GroupsOracle Help TechnologiesFinancial ServicesDevelopment Tools Arch...HealthcarePL/SQL XML ProgrammingPersonalizationXQueryEmail SDKSQL DeveloperWorkspacesDeveloper Suite (Korean)Applications (Korean)NLS (Korean)Migration (Korean)SQL I could able to see ereports details from the previous errlogs. AUTO-RESPONSE: No other automated response. Automatic FB-DIMM lane failover: The UltraSPARC T2 Plus memory controller seamlessly handles a single lane failover on an FM-DIMM link without a system crash.

Resilvering completed successfully and the data is once again fully mirrored. For example, using the ILOM command line interface (CLI) to configure alerts might not work. You can even export and reimport the pool and you will find a very nice, happy, and thoroughly error free ZFS pool. get redirected here An attempt will be made to activate a hot spare if available.

Configure the Nvidia NIC and any connected port to either the same duplex mode or both ports configured for auto-negotiate. But we're not even done yet. However I was thinking that I might see them in fmdump -e but I don't. ==>> the reason you do not see any fmdump -e output is due to the fact remote errors and produce the proper telemetry so diagnosis engines indict the correct T2 Plus.

I assume these are zfs checksum errors, automagically fixed by the zfs gods? Action : Run 'zpool status -x' and replace the bad device. # zpool status -x pool: pool2 state: DEGRADED status: One or more devices has experienced an error resulting in data TABLE 1 Topics in the Addendum That Apply to Sun Fire X4140/X4240/X4440 Servers Topic PDF page Page Maintenance->Configuration Management Window Description Revised 13 9 ILOM Configuration Corruption (Workaround 2) 17 13