users@glassfish.java.net

[Fwd: [Community Leaders] java.net Scheduled Outage 5pm-6pm, Thursday July 16th]

From: Shreedhar Ganapathy <Shreedhar.Ganapathy_at_Sun.COM>
Date: Wed, 15 Jul 2009 16:03:56 -0700

Scheduled Outage Notice from Collab


-------- Original Message --------
Subject: [Community Leaders] java.net Scheduled Outage 5pm-6pm,
Thursday July 16th
Date: Wed, 15 Jul 2009 15:44:33 -0700
From: Eric Renaud <erenaud_at_collab.net>
Reply-To: communityleaders_at_communityleads.dev.java.net
Organization: CollabNet, Inc.
To: Announcement <announcement_at_java-net.dev.java.net>, Community Leads
<communityleaders_at_communityleads.dev.java.net>



_java.net Scheduled Outage Announcement_

Date: *Thursday July 16th*
Time/Duration: *5p - 6p, PDT*

Reason: A patch to the Solaris 10 firmware must be applied to the
server hosting java.net.
              A potential for unplanned downtime exists without this
patch being applied.


Patch Details (do note that the kernel patch mentioned below has already
been applied):

> The Fault Manager receives error reports from numerous sub-systems and
> arranges for the appropriate fault diagnosis and automated responses.
>
> The Message ID: FMD-8000-0W indicates that the Fault Manager received an
> error report it did not expect. This can indicate a mismatch in the
> versions of various software components, a misconfiguration of the
> system, automated diagnosis software may not have been loaded or be
> currently available, or a defect in the software.
>
> For SPARC based systems running Solaris 10, the kernel patch 127111 and
> Solaris FMA patch 119578 are particularly critical and should be
> examined. Ensure that any dependencies documented in the patch README
> files are noted and addressed.
>
> For x64 based systems running Solaris 10, the kernel patch 127112 and
> Solaris FMA patches 118344 and 125370 are particularly critical and
> should be examined. Ensure that any dependencies documented in the patch
> README files are noted and addressed.
>
> The recommended actions for the system administrator are:
>
> 1.) Run *pkgchk -n SUNWfmd* to confirm that there are no
> errors, ensuring that the fault management software is installed properly.
>
> 2.) Ensure the latest firmware/patches are installed on the system.
>
> 3.) Check the *NOTE* below for issues that may be particular to
> your platform.
>
> 4.) If the failure persists, error telemetry will have to be
> examined by your Authorized Service Provider.
>
>
> NOTE
>
> *
> *
>
> Information applicable to the 'Sun SPARC Enterprise
> M4000/M5000/M8000/M9000' platforms
> can be found in Troubleshooting Doc #217751
> <http://sunsolve.sun.com/search/document.do?assetkey=1-65-217751-1>
>
> For 'Sun Fire T1000, Sun Fire T2000, Netra T2000, Sun SPARC Enterprise
> T5120,and T5220' systems, please make sure that the software and
> firmware patch levels are as follows:
>
> 1.) Solaris 5.10: kernel patch 127111-08 or higher
>
> 2.) Solaris 5.10: FMA Patch 119578-30 or higher
>
> 3.) System firmware:
>
> T5120 and T5220 firmware patch 127580-05 or higher
>
> T2000 firmware patch 127576-03 or higher
>
> Netra T20000 firmware patch 127578-03 or higher
>
> T1000 firmware patch 127577-03 or higher
>
> *Also Note -* On some system platforms there could be additional
> information that may disclose a hardware fault, see the following:
>
> On Sun SPARC Enterprise Mx000 systems, please check the output of
> "showstatus" and "fmdump" from the xscfu for possible hardware faults.
>
> On Sun Fire 12K, 15K, 20K and E25K systems, please check the output of
> "showlogs -E -p e list 3" from the main system controller for
> information about possible hardware faults.
>
> On Sun Fire 3800, 48x0, 6800, v1280, E2900, E4900, E6900 and Netra
> 1280/1290 systems, please check the output of "showlogs -v" from the
> main system controller for information about possible hardware faults.
>