Information About Software

This section includes the following sections:


XCP Issues and Workarounds

TABLE 3 lists XCP issues and possible workarounds.


TABLE 3 XCP Issues and Workarounds

ID

Description

Workaround

6565422

 

The latest communication field in the showarchiving(8) command is not updated regularly.

Disabling and re-enabling archiving refreshes the latest communication field in showarchiving(8) output.

6624646

Sun Connection Update Manager GUI might fail to register correctly.

Use the CLI if you run into any GUI registration issues.

6723305

 

The XSCF Web does not show the correct daylight saving time.

No workaround is available. Use the showlogs(8) command to determine time during daylight savings time.

6726679

 

SNMP trap is not sent after XSCF watchdog time out. This occurs intermittently. SNMP traps will not be notified after the watchdog timeout occurs in XSCF and XSCF reset.

No workaround is available.

 

6735711

 

setemailreport(8) command cannot handle recipient email addresses that are longer than 255 characters.

Use email address with fewer than 255 characters.

6737039

WAN boot of M3000 servers fails intermittently with a panic early in the boot process. Sample output:

ERROR: Last Trap: Fast Data Access MMU Miss
%TL:1 %TT:68 %TPC:13aacc %TnPC:13aad0 %TSTATE:1605
%PSTATE:16 ( IE:1 PRIV:1 PEF:1 )
DSFSR:4280804b ( FV:1 OW:1 PR:1 E:1 TM:1 ASI:80 NC:1 BERR:1 )
DSFAR:fda6f000 DSFPAR:401020827000 D-TAG:6365206f66206000

Poweroff and poweron the chassis, then retry the operation.

6741770

 

SNMP trap host configuration changes are not valid until setsnmp disable and setsnmp enable.

Modify the SNMP setting:

XSCF> setsnmp disable
XSCF> setsnmp enable

6741895

When FRUs are cold-replaced (with the system off), (after poweron) the monitor process might not generate entries in the monitor log identifying the replacement operation that has occurred.

No workaround is available.

6742395

Power failure at the commercial AC supply connector to the UPS does not send notification/send trap.

No workaround is available.

6742502

The browser interface displays only the last two digits of the non-audit log size limit.

Do not set Archive Log limit to ’0’. Use the showarchiving(8) command to determine log size limit.

6742951

The setlogarchiving(8) command accepts ’-1’ for the Audit log limit and then sets the limit as "Unlimited".

No workaround is available.

 

6743842

The password command indicates that the [user] operand is optional but will fail if a [user] operand is not included when other options are specified.

No workaround is available.

 

Specify the [user] operand to use the password command when you specify other options.

6744772

Logs will not be archived when logarchiving limits are exceeded, and there is no warning message to indicate that logs are no longer being archived.

Periodically, run the showarchiving(8) command and adjust limits as needed.

Or, as the used log archiving space approaches the defined limit manually rotate the existing logs on the log archiving host.

6755112

 

During the domain operation, after the XSCF reset due to the XSCF unit failure, the hardware status shows Deconfigure in the status of CPU and memory.

Replace the motherboard unit only. When no failure is found on the memory, you do not need to replace the memory.

6755113

 

During the firmware update, there might be the following output message and a XSCF panic might occur.

kernel BUG in jffs2_do_read_inode 
at fs/jffs2/readinode.c:XXX!

Reset XSCF and use the flashupdate(8) command again.

6755986

In Internet Explorer 6 or 7, clicking on the [Reset] button then the [OK] button from the Settings->Audit->Add Policy poupup screen will log the user out with message:

Error
Session Error
Session ID has been expired

Log back into the browser interface and use the backspace key to clear text in the ’User’ text box of the popup screen instead of using the Reset button.

6757064

The error log "XSCF FMEM write error" recorded and the firmware update might fail.

Power off (AC OFF) the system, and power on (AC ON) again. Then, re-execute the firmware update.

6757614

The network configuration on the XSCF Web does not support the function equivalent to the setnetwork -r option. And when you specified localhost or localdomain to the host name or the domain name, the error message "SessionID has expired" appears.

Use the setnetwork -r command on the XSCF shell.

6761674

The first usage of the OBP command probe-scsi-all might not show all devices connected via the external SAS port.

Retry the probe-scsi-all command.



Solaris OS Issues and Workarounds

This section contains information about Solaris OS issues. TABLE 4 lists issues you might encounter, depending upon which Solaris OS release you are using.

Solaris Issues for All Supported Releases

TABLE 4 lists Solaris OS issues that you might encounter in any supported release of Solaris OS.


TABLE 4 Solaris OS Issues and Workarounds for All Supported Releases

CR ID

Description

Workaround

6531036

The error ‘message network initialization failed appears repeatedly after a boot net installation.

No workaround is available. This message can be safely ignored.

6532215

volfs or dscp services might fail when a domain is booted.

Restart the service. To avoid the problem, issue the following commands.

# svccfg -s dscp setprop start/timeout_seconds=count: 300
# svccfg -s volfs setprop start/timeout_seconds=count: 300
# svcadm refresh dscp
# svcadm refresh volfs

6572827

The prtdiag -v command reports PCI buss types incorrectly. It reports "PCI" for PCI-X leaf devices and "UNKN" for legacy PCI devices.

No workaround is available.

6623226

lockstat(1M) or the dtrace lockstat provider might cause a system panic.

Do not use the Solaris lockstat(1M) command or the dtrace lockstat provider.

6660168

If a ubc.piowbeue-cpu error occurs on a domain, the Solaris Fault Management cpumem-diagnosis module might fail, causing an interruption in FMA service. If this happens, you will see output similar to the following sample in the console log:

SUNW-MSG-ID: FMD-8000-2K, TYPE: Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Fri Apr  4 21:41:57 PDT 2008
PLATFORM: SUNW,SPARC-Enterprise, CSN: 2020642002, HOSTNAME: <hostname>
SOURCE: fmd-self-diagnosis, REV: 1.0
EVENT-ID: 6b2e15d7-aa65-6bcc-bcb1-cb03a7dd77e3
DESC: A Solaris Fault Manager component has experienced an error that required the module to be disabled.  Refer to http://sun.com/msg/FMD-8000-2K for more information.
AUTO-RESPONSE: The module has been disabled.  Events destined for the module will be saved for manual diagnosis.
IMPACT: Automated diagnosis and response for subsequent events associated with this module will not occur.

REC-ACTION: Use fmdump -v -u <EVENT-ID> to locate the module. Use fmadm reset <module> to reset the module

If fmd service fails, issue the following command on the domain to recover:

# svcadm clear fmd 

Then restart cpumem-diagnosis:

# fmadm restart cpumem-diagnosis

6668237

After DIMMs are replaced the corresponding DIMM faults are not cleared on the domain.

Use the following commands:

# fmadm repair fmri|uuid 
# fmadm rotate

6723202

The raidctl command cannot be used to create a hardware RAID using the onboard SAS/LSI controller on the M3000 server.

The raidctl command can be used to view disk/controller status, and can be used on any PCI Host Bus Adapter (HBA) installed in the system.

No workaround is available. This issue will not be fixed.

6725885

cfgadm will display non-existent M3000 system boards (SB1 to SB15).

The cfgadm output for SB1-SB15 can be ignored.

6745410

Boot program ignoresthe Kadb option which causes the system not to boot.

Use kmdb instead of kadb.

6765239

If a SAS device containing multiple SAS targets is connected to the external SAS port, it will not work properly. The enumeration of target IDs within the device may change across reboots.

Do not connect a device containing multiple SAS targets to the external SAS port. Use a Sun StorageTek Host Bus Adaptor (SG-XPCIE8SAS-E-Z). Alternatively, check for the availability of a patch for this defect.



Documentation Updates

This section contains late-breaking software information that became known after the M3000 server documentation set was published.

The corrections for Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF Reference Manual, if not otherwise specified, also apply to the man pages, which XSCF provides. These corrections supersede the information on the man pages.

TABLE 5 lists known documentation corrections.


TABLE 5 Documentation Corrections

Document

Issue

Change

Sun SPARC Enterprise M3000/M4000/M5000/ M8000/M9000 Servers XSCF Reference Manual and XSCF man pages

traceroute(8) command

The following description appears under Privileges but is incorrect:

  • To execute the command to DSCP address: fieldeng

 

The following description should appear under OPERANDS but does not:

When used to specify DSCP address to host, an error occurs.

Sun SPARC Enterprise M3000/M4000/M5000/ M8000/M9000 XSCF User’s Guide

setloginlockout(8) showloginlockout(8) command

These commands are not available in this XCP release.

Sun SPARC Enterprise M3000/M4000/M5000/ M8000/M9000 Administration Guide

setloginlockout(8) showloginlockout(8) command

These commands are not available in this XCP release.