3.3Issues Affecting B100x and B200x Server Blades That are Running Solaris x86

The known problems listed in this section have been observed to affect both B100x and B200x server blades. They are presented in three groups:

Section 3.3.1, “Issues for Which You Must Apply a Workaround or Perform an Operational Procedure” on page 3-8

Section 3.3.2, “Error Messages That Can be Safely Ignored” on page 3-13

Section 3.3.3, “Other Issues” on page 3-16

3.3.1Issues for Which You Must Apply a Workaround or Perform an Operational Procedure

4962226: Warning: Jumpstart on Solaris x86 Is Not Single Shot

Caution – In some circumstances a system administrator might choose to boot a blade from the network to recover from possible errors on its hard disk. If you have configured the blade to perform a Jumpstart installation, any subsequent network boot of the blade will by default result in a Jumpstart installation being performed. This will erase the contents of the hard disk. Therefore, to prevent the blade from executing a Jumpstart installation (after the first operating system installation), we recommend you remove the SjumpsCF and SsysidCF option names from the blade’s client-specific macro after the initial Jumpstart installation has completed. (This network booting behavior is different from that of blades running SPARC Solaris.)

3-8Sun Fire™ B1600 Chassis and B100s, B100x, and B200x Blade Product Notes • May 2004

Page 26
Image 26
Sun Microsystems AND B100S, B1600, B100X, B200X BLADE manual