6760740 and 6894410

The XSCF might go down and require a reboot, or you might see console error messages and a core dump (ereport.chassis.software.core) when one of these conditions occurs:

• A local account has been created with a user ID explicitly assigned to a value larger than 65536 (adduser -u uid).
• An LDAP account has been used that has a UID value larger than 65536.

Use only user accounts with a user ID (UID) value between 100 and 60000. This is the range of auto-assigned UIDs for the XSCF command adduser.

6789066

In the settimezone -c adddst command, when you set eight or more letters to the abbreviation of time zone and the name of Daylight Saving Time, execution of the showlogs command induces a segmentation fault and results in an error.

Specify the abbreviation of time zone and the name of Daylight Saving Time in seven letters or less.

6851009

If certain changes occur on a standalone NTP server, the XSCF connection to the NTP server is lost, and XSCF uses instead its local clock. This problem occurs with a standalone NTP server, that is, with an NTP server that syncs the time with its own local clock (LCL), not with a higher-stratum NTP server. Changes that can trigger this change include:

• Rebooting the NTP server
• Modifying the date by even one second
• Changing the NTP server stratum

Check whether the XSCF LCL and the NTP server are both set to 127.127.1.0. If so, change one of them.

Note - Before making any changes, ensure that your change has no impact on other NTP clients.

• To change the value on the NTP server, change the NTP host configuration file (/etc/inet/ntp.conf) to a different value, then reboot the XSCF to apply the changes. Other values include 127.127.1.1, 127.127.1.2, and 127.127.1.3.
• To change the value on the XSCF side, use the setntp command, as in the following example:

setntp -m localaddr=2 - sets the value to 127.127.1.2

6879471

Audit log shows Advanced Directory or LDAP/SSL users as "proxyuser" rather than their actual user ID. This error might be seen when viewing audit logs created from previous XCP versions, after downgrading to a previous XCP version and viewing logs created by a later XCP release, and in some other cases.

None.

6893578

Users who have been authenticated via Active Directory or LDAP/SSL can run the console(8) command to obtain a domain console. The showconsolepath(8) command displays such console users as proxyuser rather than as their real username.

There is no 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

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.

6745410

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

Use kmdb instead of kadb.

6872501

Cores are not offlined when requested by the XSCF. This CR affects only Solaris 10 5/09 and Solaris 10 10/09 releases.

There is no workaround.

6888928

IPMP interface fails since probe packets are not sent through that interface. Problem occurs with M3000/M4000/M5000/M8000/M9000 servers running the Solaris 10 10/09 OS and IPMP, or any Solaris release running IPMP with Patch 141444-09 installed.

Disable probe-based failure detection. See InfoDoc 211105 (86869).

6572827

The prtdiag -v command reports PCI bus types incorrectly. It reports “PCI” for PCI-X leaf devices and “UNKN” for legacy PCI devices.

No workaround is available.

6623226

The Solaris command 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.

6680733

Sun Quad-port Gigabit Ethernet Adapter UTP (QGC) & Sun Dual 10 GigE Fiber XFP Low Profile Adapter (XGF) NICs might panic under high load conditions.

There is no workaround available.

6689757

Sun Dual 10 GigE Fiber XFP Low Profile Adapter (XGF) with a single or improperly installed XFP optical transceivers might cause the following error to show on the console:

The XFP optical transceiver is broken or missing.

Check and make sure that both XFP optical transceivers are firmly seated in the housing.

Do not mix INTEL and Sun XFP optical transceivers in the same Adapter.

Do NOT plumb a port with the ifconfig command if the port does not contain an XFP optical transceiver or it contains one but the transceiver is not in use.

6725885

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

The cfgadm output for SB1-SB15 can be ignored.

6556742

The system panics when DiskSuite cannot read the metadb during DR. This bug affects the following cards:

• SG-XPCIE2FC-QF4, 4-Gigabit PCI-e Dual-Port Fiber Channel HBA
• SG-XPCIE1FC-QF4, 4-Gigabit PCI-e Single-Port Fiber Channel HBA
• SG-XPCI2FC-QF4, 4-Gigabit PCI-X Dual-Port Fiber Channel HBA
• SG-XPCI1FC-QF4, 4-Gigabit PCI-X Single-Port Fiber Channel HBA

Panic can be avoided when a duplicated copy of the metadb is accessible via another Host Bus Adaptor.

6608404

Hot-plug of the X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP card might cause other network devices to fail.

There is no workaround.

6720261

If your domain is running Solaris 10 5/08 OS, the system might panic/trap during normal operation:

Set the following parameter in the system specification file (/etc/system):

set heaplp_use_stlb=0

Then reboot the domain.

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

Power off and power on the chassis, then retry the operation.

Advanced Directory and LDAP/SSL man pages

Not yet added:
The new setad(8), setldapssl(8), showad(8), and showldapssl(8) man pages. You can use the man(1) command to view these man pages online. Also see the notes about setad(8) and setldapssl(8) in TABLE 3-7

password(8) and setpasswordpolicy(8)

Not yet added:

Most value ranges are 1 - 999999999.

setdualpowerfeed(8)

Not yet added: “The dual power feed mode cannot be used with 100V power on M4000/M5000 servers.”

sethttps(8)

Not yet added to EXTENDED DESCRIPTION:
“The size of the file to be generated by sethttps(8) grows with the total character count typed in the operands for configuring self-certification authority, creating a self-signed web server certificate, and creating a CSR. If the file to be generated is too large for XSCF, the command fails with an error. If you see this error, reduce the number of characters in the operands and execute the sethttps(8) command again”

setnameserver(8)

• Not yet added to OPERANDS:
  “You cannot specify the loopback address (127.0.0.0/8), the network address, or a broadcast address.”
• Not yet added to OPTIONS:
  New options for registering a specified domain name to the DNS search path:
  -c addsearch
  -c delsearch

Along with the addition of DNS search path, related descriptions for DNS search path will be added to applynetwork(8), sethostname(8), and shownameserver(8). For details, see the online versions of these man pages as of the XCP 1091 release.

setnetwork(8)

Not yet added to OPERANDS:

“You cannot specify the loopback address (127.0.0.0/8), the network address, a broadcast address, or a class D or E (224.0.0.0 - 255.255.255.255) address.”

setntp(8),

• Not yet added to OPERANDS:
  “You cannot specify the loopback address (127.0.0.0/8), the network address, or a broadcast address.”
• Not yet added to OPTIONS: A new option for setting the local clock of XSCF:
  -m localaddr=value.

Along with the addition of clock address, related descriptions for local addresses will be added to showntp(8). For details, see the online version of the setntp(8) and showntp(8) man pages.

setroute(8)

• Not yet added to OPTIONS:
  “You cannot specify the loopback address (127.0.0.0/8), the network address, or a broadcast address.”
• Not yet changed in OPTIONS:
  Old text - “If you specified 0.0.0.0 in the -n option, do not specify the -m option.”
  New text - “If you specified 0.0.0.0 in the -n option, you must specify 0.0.0.0 in the -m option or you must omit the -m option.”

setupfru(8)

Not yet added to EXTENDED DESCRIPTION:
“Although a CMU with two CPUMs can be configured into Quad-XSB mode on an M8000/M9000 server, the server generates a "configuration error" message for these XSBs because they do not have at least one CPUM and memory.”

showdevices(8)

Not yet added to EXTENDED DESCRIPTION:
“The showdevices(8) command displays a complete list of devices when executed right after a Solaris OS boot or a DR operation. However, when executed at other times, showdevices does not display a complete list if the Solaris OS has unloaded drivers for any unused devices. To be certain the displayed list is complete, run the devfsadm command with the -v option on the domain before running showdevices. For more information about the devfsadm command, see the Solaris devfsadm(1M) man page.”

showenvironment(8)

Not yet added:
“Airflow volume information is not supported on the M4000/M5000 servers.”

Not yet replaced:
Old text - “The power consumption information is displayed on the M3000/M4000/M5000 servers.”
New text - “The power consumption information is displayed on the M3000 server.”

showhardconf(8)

Not yet added to EXAMPLES: A new example of a M3000 server with DC power.

setad(8)

• Not yet added to OPERANDS:
  “A user domain can be configured explicitly through the setad userdomain command on XSCF, or entered at login prompt using the form, user@domain.”
• Future change expected: Addition to SYNOPSIS and OPTIONS:
  “-p proxy specifies the proxy server to be used for transfers. The default transfer type is http, unless modified using the -t proxy_type option. The value for proxy must be in the format servername:port.”
  “-t proxy_type specifies the proxy type as http, socks4, or socks5. The deafult is http.”
• Not yet changed in the description of the timeout operand:
  “Configure transaction timeout, in seconds. seconds can be 1 to 20. The default is 4. If the specified timeout is too brief for the configuration, the login process or retrieval of user privilege settings could fail.”
• Not yet changed in Example 6:
  “userdomain can take the form of UserPrincipalName (UPN) or Distinguished Name (DN).”

setldapssl(8)

• Not yet changed in OPERANDS:
  “Enable or disable use of the usermap. When enabled, user attributes specified with the usermap operand, rather than userdomain, are used for user authentication.”
• Future change expected: Addtion to SYNOPSIS and OPTIONS:
  “-p proxy specifies the proxy server to be used for transfers. The default transfer type is http, unless modified using the -t proxy_type option. The value for proxy must be in the format servername:port.”
  “-t proxy_type specifies the proxy type as http, socks4, or socks5. The deafult is http.”
• Not yet changed in Example 6:
  “userdomain can take the form of Distinguished Name (DN) only.”
• Future change expected: Addition of Examples for the binddn, bindpw, and searchbase operands.
• Not yet changed in the description of the timeout operand:
  “Configure transaction timeout, in seconds. seconds can be 1 to 20. The default is 4. If the specified timeout is too brief for the configuration, the login process or retrieval of user privilege settings could fail.”

Active Directory and LDAP/SSL

Not yet added. See Active Directory and LDAP/SSL of these Product Notes.

Power Consumption Monitoring Limitation

Added in the 1090 update of this document:

In the following cases, inaccurate power consumption values might be shown in the MIB, in the showenvironment power command output, and on the XSCF Web:

• During or for a short time after server power-on or power-off.
• During or for a short time after active replacement of a power supply unit.

To ensure the values are accurate, wait one minute, then check the values again.

XSCF Unit/Firmware Updates

Not yet changed in Chapter 8.1.10:
Replace steps 2 and 3 in these sections:

• Confirming That the XSCF Firmware is Updated When the XSCF Unit is Replaced (in a System with a Single XSCF Unit or Both Replacement in a System with Redundant XSCF Units
• Confirming That the XSCF Firmware is Updated When the MBU is Replaced (in the M3000 Server)

The replacement steps are:

2. If the replacement unit and the replaced unit have different versions, a message is displayed. In this case, the firmware is not updated automatically. The operator must match the number of the firmware versions.

3. When you update, follow the procedure in "Updating XCP From External Media" or "Updating XCP from the Network." After updating, confirm the version.