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.

4816837

System hangs when executing parallel hot-plug operation with SP DR in suspend phase.

There is no workaround.

6459540

The DAT72 internal tape drive connected to M4000/M5000/M8000/M9000 servers might time out during tape operations.

The device might also be identified by the system as a QIC drive.

Add the following definition to /kernel/drv/st.conf:

tape-config-list=
"SEAGATE DAT    DAT72-000",
"SEAGATE_DAT____DAT72-000",
"SEAGATE_DAT____DAT72-000";
SEAGATE_DAT____DAT72-000=1,0x34,0,0x9639,4,0x00,0x8c,0x8c,
0x8c,3;

There are four spaces between SEAGATE DAT and DAT72-000.

6522017

Domains using the ZFS file system cannot use DR.

Set the maximum size of the ZFS ARC lower. For detailed assistance, contact your authorized service representative.

6531036

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

There is no workaround.

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

6588650

On occasion, a M4000/M5000/M8000/M9000 server is unable to DR after an XSCF failover to or from backup XSCF.

There is no workaround.

6589644

When XSCF switchover happens on an M8000/M9000 server after the system board has been added using the addboard command, the console is no longer available.

The console can be recovered by pressing
Ctrl-q (the “Ctrl” key and the “q” key).

6592302

Unsuccessful DR operation leaves memory partially configured.

It might be possible to recover by adding the board back to the domain with an addboard
-d command. Otherwise try deleteboard(8) again.

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

6674266 and 6611966

DR deleteboard(8) and moveboard(8) operations might fail.

Example for messages on domain:

drmach: WARNING: Device driver
failure: /pci
dcs: <xxxx> config_change_state:
Hardware specific failure:
unconfigure SB1: Device driver
failure: /pci

Try DR operations again.

6745410

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

Use kmdb instead of kadb.

6794630

An attempt to use the GUI to install Solaris in a domain larger than 2TB might fail.

Use the command-line interface to install Solaris.

6872501

Cores are not offlined when requested by the XSCF.

Use fmdump(1M) with its -v option on the Service Processor to identify the faulty core. Once identified, use psradm(8) on the domain to offline the core.

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.

There is no workaround.

6724307

Scheduler decisions are occasionally unbalanced.

Sometimes two threads will be on one core (causing both to run at about half speed) while another core is idle. For many OpenMP and similar parallel applications, the application performance is limited by the speed of the slowest thread.

Uneven scheduling is not common, perhaps 1 in 50 or 1 in 100 decisions. But if there are 128 threads running, then the application might have at least one uneven schedule event.

Use processor sets to prevent uneven threads to core assignment.

6800734

deleteboard hang in a domain

There is no workaround.

6821108

DR and "showdevices" do not work after XSCF reboot.

Reboot the XSCF service processor twice. Half the SAs are deleted the first time and half are deleted the second time, so the second addition succeeds and IPsec communication is reestablished.

6827340

DR and Memory patrol may fail due to SCF command error.

There is no workaround.

6588555

Resetting the XSCF during a DR operation on permanent memory might cause domain panic.

Do not start an XSCF reset while a DR operation is underway. Wait for the DR operation to complete before starting the reset.

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.

If posible, use the card in x8 slot. Otherise, there is no workaround.

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.

6511374

Memory translation warning messages might appear during boot if memory banks were disabled due to excessive errors.

After the system is rebooted, the fmadm repair command can be used to prevent a recurrence of the problem on the next boot.

6533686

When XSCF is low on system resources, DR deleteboard or moveboard operations that relocate permanent memory might fail with one or more of these errors:

SCF busy 
DR parallel copy timeout

This applies only to Quad-XSB configured System Boards hosting multiple domains.

Retry the DR operation at a later time.

6535018

In Solaris domains that include SPARC64 VII processors, workloads that make heavy use of the Solaris kernel might not scale as expected when you increase the thread count to a value greater than 256.

For Solaris domains that include SPARC64 VII processors, limit domains to a maximum of 256 threads.

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.

6589833

The DR addboard command might cause a system hang if you are adding a Sun StorageTek Enterprise Class 4-Gigabit Dual-Port Fiber Channel PCI-E HBA card (SG-XPCIE2FC-QF4) at the same time that an SAP process is attempting to access storage devices attached to this card. The chance of a system hang is increased if the following cards are used for heavy network traffic:

• X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP
• X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet Fiber XFP Low profile Adapter

There is no workaround.

6614737

The DR deleteboard(8) and moveboard(8) operations might hang if any of the following conditions exist:

A DIMM has been degraded.

The domain contains system boards with different memory size.

Avoid performing DR operations if any of the following conditions exist:

• Degraded memory - To determine whether the system contains degraded memory, use the XSCF command showstatus.
• Differing memory sizes - To determine whether the domain contains system boards with different memory sizes, display the list of memory sizes using the XSCF command showdevices or the prtdiag command on the domain.

If a DR command hangs, reboot the domain to recover.

6619224

For Solaris domains that include SPARC 64 VII processors, a single domain of 256 threads or more might hang for an extended period of time under certain unusual situations. Upon recovery, the uptime command will show extremely high load averages.

For Solaris domains that include SPARC 64 VII processors, do not exceed a domain size of 256 virtual processors in a single Solaris domain. This means a maximum of 32 CPUs in a single domain configuration (maximum configuration for an M8000 server).

6632549

fmd service on domain might fail to go into maintenance mode after DR operations.

Issue the following command on the domain:

# svcadm clear fmd

6660197

DR might cause the domain to hang if either of the following conditions exist:

• A domain contains 256 or more CPUs.
• Memory error occurred and the DIMM has been degraded.

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

set drmach:drmach_disable_mcopy = 1

1. Reboot the domain.

6679370

The following message may be output on the console during system boot, addition of the External I/O Expansion Unit using hotplug, or an FMEMA operation by DR.

SUNW-MSG-ID: SUN4-8000-75, TYPE: 
Fault, VER: 1, SEVERITY: Critical
...
DESC:
A problem was detected in the
PCIExpress subsystem.
Refer to http://sun.com/msg/SUN4-
8000-75 for more information.
...

Add the following to /etc/system, then reboot the domain.

set pcie_expected_ce_mask = 0x2001

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.

5076574

A PCIe error can lead to an invalid fault diagnosis on a large M8000/M9000 domain.

Create a file /etc/fm/fmd/fmd.conf containing the following lines;

setprop client.buflim 40m
setprop client.memlim 40m

6348554

Using the cfgadm -c disconnect command on the following cards might hang the command:

• SG-XPCIE2FC-QF4, Sun StorageTek Enterprise Class 4-Gigabit Dual-Port Fiber Channel PCI-E HBA
• SG-XPCIE1FC-QF4, Sun StorageTek Enterprise Class 4-Gigabit Single-Port Fiber Channel PCI-E HBA
• SG-XPCI2FC-QF4, Sun StorageTek Enterprise Class 4-Gigabit Dual-Port Fiber Channel PCI-X HBA
• SG-XPCI1FC-QF4, Sun StorageTek Enterprise Class 4-Gigabit Single-Port Fiber Channel PCI-X HBA

Do not perform cfgadm -c disconnect operation on the affected cards.

6402328

Customers using more than six IOUA (Base I/O Card) cards in a single domain might experience panic during a period of high I/O stress.

Limit the maximum number of IOUAs in a single domain to 6.

6472153

If you create a Solaris Flash archive on a sun4u server other than an M4000/M5000/M8000/M9000 server, then install it on one of these servers, the console’s TTY flags will not be set correctly. This can cause the console to lose characters during stress.

ust after installing Solaris OS from a Solaris Flash archive, telnet into the M4000/M5000/M8000/M9000 server to reset the console’s TTY flags as follows:

# sttydefs -r console
# sttydefs -a console -i "9600 \hupcl opost onlcr crtscts" -f "9600"

This procedure is required only once.

6505921

Correctable error on the system PCIe bus controller generates an invalid fault.

Create a file /etc/fm/fmd/fmd.conf containing the following lines;

setprop client.buflim 40m

setprop client.memlim 40m

6522433

The incorrect motherboard might be identified by fmdump for cpu faults after reboot.

Check system status on XSCF.

6527811

The showhardconf(8) command on the XSCF cannot display PCI card information that is installed in the External I/O Expansion Unit, if the External I/O Expansion Unit is configured using PCI hot-plug.

There is no workaround. When each PCI card in the External I/O Expansion Unit is configured using PCI hot-plug, the PCI card information is displayed correctly.

6536564

showlogs(8) and showstatus(8) command might report wrong I/O component.

To avoid this problem, issue the following commands on the domain.

# cd /usr/platform/SUNW,SPARCEnterprise \ /lib/fm/topo/plugins

# mv ioboard.so ioboard.so.orig

# svcadm restart fmd

Contact a service engineer if the following messages are displayed:

SUNW-MSG-ID: SUNOS-8000-1L, TYPE:

Defect, VER: 1, SEVERITY: Minor

EVENT-TIME: Sun May 6 18:22:24 PDT 2007

PLATFORM: SUNW,SPARC-Enterprise,

CSN: BE80601007, HOSTNAME: sparc

6545143

There is a low probability that a system panic can occur during trap processing of a TLB miss for a user stack address. The problem can occur if the user stack is unmapped concurrently with the user process executing a flush windows trap (ta 3). The panic message will contain the following string:

bad kernel MMU trap at TL 2

There is no workaround.

6545685

If the system has detected Correctable MemoryErrors (CE) at power-on self-test (POST), the domains might incorrectly degrade 4 or 8 DIMMs.

Increase the memory patrol timeout values used via the following setting in /etc/system and reboot the system:

set mc-opl:mc_max_rewrite_loop = 20000

6546188

The system panics when running hot-plug (cfgadm) and DR operations (addboard and deleteboard) on the following cards:

• X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP
• X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet Fiber XFP Low profile Adapter

There is no workaround.

6551356

The system panics when running hot-plug (cfgadm) to configure a previously unconfigured card. The message “WARNING: PCI Expansion ROM is not accessible” will be seen on the console shortly before the system panic. The following cards are affected by this defect:

• X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP
• X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet Fiber XFP Low profile Adapter

Use cfgadm -c disconnect to completely remove the card. After waiting at least 10 seconds, the card might be configured back into the domain using the cfgadm -c configure command.

6559504

Messages of the form nxge: NOTICE: nxge_ipp_eccue_valid_check: rd_ptr = nnn wr_ptr = nnn will be observed on the console with the following cards:

• X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP
• X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet Fiber XFP Low profile Adapter

These messages can be safely ignored.

6563785

Hot-plug operation with the following cards might fail if a card is disconnected and then immediately reconnected:

• SG-XPCIE2SCSIU320Z Sun StorageTek PCI-E Dual-Port Ultra320 SCSI HBA
• SGXPCI2SCSILM320-Z Sun StorageTek PCI Dual-Port Ultra320 SCSI HBA

After disconnecting a card, wait for a few seconds before re-connecting.

6564934

Performing a DR deleteboard operation on a board which includes Permanent Memory when using the following network cards results in broken connections:

• X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP
• X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet Fiber XFP Low profile Adapter

Reconfigure the affected network interfaces after the completion of the DR operation. For basic network configuration procedures, refer to the ifconfig man page for more information.

6568417

After a successful CPU DR deleteboard operation, the system panics when the following network interfaces are in use:

• X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP
• X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet Fiber XFP Low profile Adapter

Add the following line to /etc/system and reboot the system:

set ip:ip_soft_rings_cnt=0 

6571370

Use of the following cards have been observed to cause data corruption in stress test under laboratory conditions:

• X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP
• X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet Fiber XFP Low profile Adapter

Add the following line in /etc/system and reboot the system:

set nxge:nxge_rx_threshold_hi=0 

6584984

The busstat(1M) command with -w option might cause M8000/M9000 server domains to reboot.

There is no workaround. Do not use busstat(1M) command with -w option on pcmu_p.

6589546

prtdiag does not show all IO devices of the following cards:

• SG-XPCIE2FC-EM4 Sun StorageTek Enterprise Class 4-Gigabit Dual-Port Fiber Channel PCI-E HBA
• SG-XPCIE1FC-EM4 Sun StorageTek Enterprise Class 4-Gigabit Single-Port Fiber Channel PCI-E HBA

Use prtdiag -v for full output.

6663570

DR operations involving the lowest numbered CPU might cause the domain to panic.

Do not use DR to remove the system board that hosts the CPU with the lowest CPU ID. Use the Solaris prtdiag command to identify the CPU with the lowest CPU ID.

6303418

M9000 server with a single domain and 11 or more fully populated system boards might hang under heavy stress.

Do not exceed 170 CPU threads.

Limit the number of CPU threads to one per CPU core by using the Solaris psradm command to disable the excess CPU threads. For example, disable all odd-numbered CPU threads.

6416224

System performance can degrade using a single NIC card with more than 5,000 connections.

Use multiple NIC cards to split network connections.

6441349

I/O error can hang the system.

There is no workaround.

6485555

On-board Gigabit Ethernet NVRAM corruption could occur due to a race condition. The window of opportunity for this race condition is very small.

There is no workaround.

6496337

The “cpumem-diagnosis” module may fail to load after uncorrectable error(UE) panic. Systems will function correctly but events normally automatically diagnosed by FMA using this module will require manual diagnosis.

Example:

SUNW-MSG-ID: FMD-8000-2K, TYPE:
Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Thu Feb 15 15:46:57 JST
2007
PLATFORM: SUNW,SPARC-Enterprise,
CSN: BE80601007, HOSTNAME: col2-ffem7-
d0

If the problem has already occurred, use this

workaround:

1. Remove the cpumemdiagnosis file:

# rm /var/fm/fmd/ckpt/cpumemdiagnosis \ /cpumem-diagnosis

1. Restart fmd service:

# svcadm restart fmd

To avoid this problem in advance, add the following line in the file /lib/svc/method/svc-dumpadm:

#
savedev=none
rm -f /var/fm/fmd/ckpt/cpumemdiagnosis \ 
/cpumem-diagnosis
#

6495303

The use of a PCIe Dual-Port Ultra320 SCSI controller card (SG-(X)PCIE2SCSIU320Z) in IOU Slot 1 on a Sun SPARC Enterprise M4000/M5000 server might result in a system panic.

Do not use this card in IOU Slot 1.

6498283

Using the DR deleteboard command while psradm operations are running on a domain might cause a system panic.

There is no workaround.

6499304

Unexpected message is displayed on console and CPU isn’t offlined when numerous correctable error(CE) occur.

Example:

SUNW-MSG-ID: FMD-8000-11, TYPE:
Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Fri Feb 2 18:31:07 JST
2007
PLATFORM: SPARC-Enterprise, CSN:
BE80601035, HOSTNAME: FF2-35-0

Check CPU status on XSCF.

6502204

Unexpected error messages may be displayed on console on booting after CPU UE panic.

Example:

SUNW-MSG-ID: FMD-8000-11, TYPE:
Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Tue Jan 9 20:45:08 JST
2007
PLATFORM: SUNW,SPARC-Enterprise,
CSN: 2030636002, HOSTNAME: P2-DC1-
16-d0

If you see unexpected messages, use the showdomainstatus(8) command to check system status on XSCF.

6502750

Inserted or removed hotplugged PCI card may not output notification message.

There is no workaround.

6508432

A large number of spurious PCIe correctable errors can be recorded in the FMA error log.

To mask these errors, add the following entry to /etc/system and reboot the system:

set pcie:pcie_aer_ce_mask = 0x2001

6508434

The domain may panic when an additional PCI-X card is installed or a PCI-X card is replaced using PCI hot-plug.

Do not insert a different type of PCI-X card on the same PCI slot by using PCI hot-plug.

6510861

When using the PCIe Dual-Port Ultra320 SCSI controller card (SG-(X)PCIE2SCSIU320Z), a PCIe correctable error causes a Solaris panic.

Add the following entry to /etc/system to prevent the problem:

set pcie:pcie_aer_ce_mask = 0x31c1

6520990

When a domain reboots, SCF might not be able to service other domains that share the same physical board. DR operation can exceed the default timeout period and panic can occur.

Increase the DR timeout period by setting the following statement in /etc/system and reboot your system.:

set drmach:fmem_timeout = 30

6527781

The cfgadm command fails while moving the DVD/DAT drive between two domains.

There is no workaround. To reconfigure DVD/Tape drive, execute reboot -r from the domain exhibiting the problem.

6530178

DR addboard command can hang. Once the problem is observed, further DR operations are blocked. Recovery requires reboot of the domain.

There is no workaround.

6530288

cfgadm(1M) command may not correctly show Ap_Id format.

There is no workaround.

6534471

Systems might panic/trap during normal operation.

Disable the kernel large pages TLB programming. In the file /etc/system, change the heaplp_use_stlb variable to 0:

set heaplp_use_stlb=0

6535564

PCI hot-plug to PCI slot #0, #1 or External I/O Expansion Unit may fail on XSB added by DR.

Use DR instead of PCI hot-plug if need to add or remove PCI card on the XSB.

6539084

There is a low probability of a domain panic during reboot when the Sun Quad GbE UTP x8 PCIe (X4447A-Z) card is present in a domain.

6539909

Do not use the following I/O cards for network access when you are using the boot net install command to install the Solaris OS:

• X4447A-Z/X4447A-Z, PCIe Quad-port Gigabit Ethernet Adapter UTP
• X1027A-Z/X1027A-Z, PCIe Dual 10 Gigabit Ethernet Fiber XFP

Use an alternative type of network card or onboard network device to install the Solaris OS via the network.

6542632

Memory leak in PCIe module if driver attach fails.

There is no workaround.

Advanced Directory and LDAP/SSL man pages

Four new man pages related to these features:
setad(8), setldapssl(8), showad(8), and showldapssl(8). You can use the man(1) command to view these man pages online.

adduser(8)

Added the following information: “If the Service Processor is configured to use Lightweight Directory Access Protocol (LDAP), Active Directory, or LDAP/SSL for user account data, the user name and UID (if specified) must not already be in use locally or in LDAP, Active Directory, or LDAP/SSL.”

applynetwork(8)

Modified for clarity.

ioxadm(8)

Modified to include new information.

password(8)

Modified value ranges for clarity. Most are 1 - 999999999.

setdscp(8)

Added the following text:

“The specified netmask must be a subset of the default netmask based on network class.

setdualpowerfeed(8)

Modified to include the statement: “The dual power feed mode cannot be used with 100V power on M4000/M5000 servers.”

sethostname(8)

Added information in EXTENDED DESCRIPTION.

sethttps(8)

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”

setldap(8)

Added the following information: “An XSCF user account user name cannot match an LDAP user name and an XSCF user account number (UID) cannot match an LDAP UID number. “

setnameserver(8)

• Added to OPERANDS:
  “You cannot specify the loopback address (127.0.0.0/8), the network address, or a broadcast address.”
• 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 were 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)

Modified -m in OPTIONS, and 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.”

Also, added information about xscf#0-lan#0 and xscf#0-lan#1.

setntp(8)

• Added to OPERANDS:
  “You cannot specify the loopback address (127.0.0.0/8), the network address, or a broadcast address.”
• 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.

setpacketfilters(8)

This new man page was added in the XCP 1092 release.

setpasswordpolicy(8)

Modified value ranges for clarity. Most are 1 - 999999999.

setroute(8)

• Added to OPTIONS:
  “You cannot specify the loopback address (127.0.0.0/8), the network address, or a broadcast address.”
• 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)

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.”

setupplatform(8)

Added the following information: “An XSCF user account user name cannot match an LDAP user name and an XSCF user account number (UID) cannot match an LDAP UID number. “

showdevices(8)

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)

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

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)

Added to EXAMPLES: A new example of a M3000 server with DC power, added PCI card information, and added -M option.

showlogs(8)

Added:
-M option, new information for Status and Detail log/Power log in EXTENDED DESCRIPTION, and other references to Pow.Fail/Recov.

showpacketfilters(8)

This new man page was added in the XCP 1092 release.

Active Directory and LDAP/SSL

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

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.