C H A P T E R 3 - Dynamic Reconfiguration Release Notes

C H A P T E R 3

Dynamic Reconfiguration Release Notes

Some dynamic reconfiguration (DR) software on Sun Fire high-end systems runs on the domain, and some runs with SMS on the system controller (SC). This chapter describes SC-side DR as it runs with the SMS 1.4.1 release. For information about domain-side DR, refer to the appropriate version of the Solaris Release Notes Supplement for Sun Hardware.

Slot 1 DR

Sun Fire high-end systems support up to 18 expander boards, each of which includes two slots. Slot 0 is the upper assembly, which contains a CPU/Memory board, and Slot 1 is the lower assembly. Slot 1 can contain a MaxCPU board, hsPCI assembly, hsPCI+, or wPCI assembly.

Note - If a MaxCPU board is in Slot 1, the boards in that expander cannot be in different domains. See Known Limitations.

Solaris 9 4/03 was the first Solaris 9 release to support DR operations on a board in Slot 1, and Solaris 8 2/02 with certain patches was the first Solaris 8 release to support it. Domains running the base Solaris 9 release continue to support DR on CPU/Memory boards. For complete Slot 1 DR support, SMS 1.3, SMS 1.4, or SMS 1.4.1 is required on the SC, and you should run the latest version for the most complete set of features and the latest bug fixes.

Known Limitations

When Slot 1 of an expander board contains a MaxCPU board, the boards in that expander cannot be safely configured into different domains. If one board is configured in a domain, any attempt to configure the other into a different domain will fail. The board is marked Failed and an error message similar to the following is written to the POST log:

FAIL Slot SBx: MaxCPU in use in Slot IOx [...]

A subsequent attempt to DR the board causes an insufficient-condition error message.

Power-cycling the board to clear the failed state allows the board to be the target of an allowable DR operation; that is, one that would not result in a split-slot condition.

Note - If you need this configuration because you are upgrading from SMS 1.3, which did support MaxCPU spit-slot configurations, contact your Sun Service Representitve and refer to RFE number #4863496.

DR Documentation Notes

For release notes that pertain to DR on the domain side, see the Solaris Release Notes Supplement for Sun Hardware that corresponds to the Solaris version running on your domains. That document accompanies each Solaris release and update.

Known Bugs

This section contains important SMS-side bugs that involve DR on the Sun Fire high end system.

DCA Doesn't Detect Failed Network Connection (BugId 4628314)

DCA doesn't detect a failed network connection, which can cause a DR command to hang.

Workaround: Kill any remote DR commands that appear to be hung.

Known Hardware Bugs

GigaSwift Ethernet MMF Link Goes Down With CISCO 4003 Switch After DR Attach (BugId 4709629)

Attempting to execute a DR operation on a system with Sun GigaSwift Ethernet MMF Option X1151A, part number 595-5773, attached to certain CISCO switches causes the link to fail. The problem is caused by a known bug in the following CISCO hardware/firmware:

CISCO WS-c4003 switch (f/w: WS-C4003 Software, Version NmpSW: 4.4(1))

CISCO WS-c4003 switch (f/w: WS-C4003 Software, Version NmpSW: 7.1(2))

CISCO WS-c5500 switch (f/w: WS-C5500 Software, Version McpSW: 4.2(1) and NmpSW: 4.2(1))

This problem is not seen on CISCO 6509 switch.

Workaround: Use another switch or consult Cisco for a patch.