Sun Microsystems Ultra 450 Manual
  1. Manuals
  2. Brands
  3. Sun Microsystems Manuals
  4. Server
  5. Sun Ultra 450
  6. Manual
Sun Microsystems Ultra 450 Manual

Sun Microsystems Ultra 450 Manual

Hide thumbs Also See for Ultra 450:
Table of Contents

Advertisement

Quick Links

Download this manual
Enlarged version
Sun Microsystems, Inc.
901 San Antonio Road
Palo Alto, , CA 94303-4900
U.S.A
Part No: 805-4452
September 1998, Revision A

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Ultra 450 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Sun Microsystems Ultra 450

Summary of Contents for Sun Microsystems Ultra 450

  • Page 1 Sun Microsystems, Inc. 901 San Antonio Road Palo Alto, , CA 94303-4900 U.S.A Part No: 805-4452 September 1998, Revision A...
  • Page 2 Sun, Sun Microsystems, the Sun logo, SunSoft, SunDocs, SunExpress, Ultra, Ultra Enterprise, AnswerBook, SunDocs, OpenBoot, Solstice DiskSuite, Solstice SyMON, UltraSCSI,and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.

  • Page 3: Table Of Contents

    Contents Preface v Configuring Disk Slot Associations Overview 1 Setting Disk Slot Associations 2 System Configuration Parameters 5 UPA Probing 6 PCI Probing 6 Memory Interleaving 8 Environmental Monitoring and Control 9 Automatic System Recovery 10 “Soft” Deconfiguration via Status Property 10 “Hard”...
  • Page 4 Adding the Disk Drive 17 Configuring the Solaris Environment Configuring the New Disk Drive In Your Application 18 Configuring the New Disk Drive for a UNIX File System (UFS) 18 Adding a Disk to a Solstice DiskSuite Disk Set 19 Replacing a Faulty Hot-Pluggable Disk Drive 19 Prepare Spare Drives 20 Identifying the Faulty Disk Drive 20...

  • Page 5: Preface

    Preface Platform Notes: Sun Ultra 450 Workstation and Ultra Enterprise 450 Server contains the following information for system administrators and advanced users of Ultra 450 workstations or Ultra Enterprise 450 servers: 4 OpenBoot commands and variables for configuring various aspects of system...
  • Page 6 Typographic Conventions Typographic Conventions TABLE P–1 Typeface or Symbol Meaning Examples The names of commands, files, and Edit your .login file. AaBbCc123 directories; on-screen computer Use ls -a to list all files. output. % You have mail. What you type, when contrasted AaBbCc123 % su with on-screen computer output.
  • Page 7 Shell Prompts TABLE P–2 (continued) Sun Documentation on the Web The docs.sun.com web site enables you to access Sun technical documentation on the Web. You can browse the docs.sun.com archive or search for a specific book title or subject at: http://docs.sun.com Sun Welcomes Your Comments You can email your comments to us at docfeedback@sun.com.
  • Page 8 ♦ September 1998, Revision A viii...

  • Page 9: Configuring Disk Slot Associations

    Sun Ultra 450 workstation or Ultra Enterprise 450 server. Overview The internal disk array in a Sun Ultra 450 workstation or Ultra Enterprise 450 server can accommodate up to 20 low-profile UltraSCSI disk drives. The basic system configuration includes support for one to four disk drives connected to a 4-slot...

  • Page 10: Setting Disk Slot Associations

    8-bay storage expansion kits: 1. Power on the system. See “How to Power On the System” in the Sun Ultra 450 Workstation Owner’s Guide or Ultra Enterprise 450 Server Owner’s Guide. 2. When the system banner is displayed on the monitor, press Stop-a on the Sun keyboard.
  • Page 11 3. Enter the following command to perform a reconfiguration boot: ok boot -r This command rebuilds the device trees for the system, incorporating any newly installed options. After a device has been added to a device tree, it can be recognized by the system.
  • Page 12 ♦ September 1998, Revision A...

  • Page 13: System Configuration Parameters

    CHAPTER System Configuration Parameters This chapter describes the NVRAM configuration variables and OpenBoot PROM (OBP) commands available for configuring the following aspects of Ultra 450 system behavior: 4 UPA probing 4 PCI probing 4 Memory interleaving 4 Environmental monitoring and control 4 Automatic System Recovery (ASR) NVRAM configuration variables covered in this chapter include:...

  • Page 14: Upa Probing

    PCI Probing Of the six PCI buses on the Ultra 450 system , bus 0 (/pci@1f,4000 in the device tree) is unique in that it is the only PCI bus that contains motherboard (non plug-in) devices such as standard Ethernet and SCSI controllers.
  • Page 15 pci0-probe-list. This variable controls both the probing order and exclusion of devices on PCI bus 0. The values in the pci0-probe-list are defined in the following table. Values in the pci0-probe-list TABLE 2–2 PCI Device Number Function UPA-PCI bus bridge (not probed) EBus/Ethernet interface (always probed, never included in probe list) On-board SCSI controller for removable media devices and external SCSI port...

  • Page 16: Memory Interleaving

    Memory Interleaving Memory interleaving in an Ultra 450 system is controlled by the NVRAM variable memory-interleave. The following table shows the various settings for this variable and the effect each setting has on memory configuration. For a related discussion about memory interleaving and memory configuration guidelines, see “About Memory”...

  • Page 17: Environmental Monitoring And Control

    Environmental Monitoring and Control Environmental monitoring and control capabilities for an Ultra 450 system reside at both the operating system level and the OBP firmware level. This ensures that monitoring capabilities are operational even if the system has halted or is unable to boot.

  • Page 18: Automatic System Recovery

    Automatic System Recovery The automatic system recovery (ASR) feature allows an Ultra 450 system to resume operation after experiencing certain hardware faults or failures. Power-on self-test (POST) and OpenBoot diagnostics (OBDiag) can automatically detect failed hardware components, while an auto-configuring capability designed into the OBP firmware allows the system to deconfigure failed components and restore system operation.

  • Page 19: Asr User Override Capability

    NVRAM variable asr-disable-list, which is simply a list of device tree paths separated by spaces. ok setenv asr-disable-list /pci/ebus/ecpp /pci@1f,4000/scsi@3 The Ultra 450 OBP will use this information to created disabled status properties for each node listed in the variable asr-disable-list. “Hard” Deconfigure Override For overriding those subsystems that require “hard”...

  • Page 20: Auto-Boot Options

    If a system fails power-on diagnostics, then auto-boot? is ignored and the system does not boot unless the user does it manually. This behavior is obviously not acceptable for a degraded boot scenario, so the Ultra 450 OBP provides a second NVRAM-controlled switch called auto-boot-on-error?. This switch controls whether the system will attempt a degraded boot when a subsystem failure is detected.

  • Page 21: Reset Scenarios

    NVRAM variable diag-switch? is set to true. The default setting for this variable is false. To support ASR in an Ultra 450 system, it is desirable to be able to run firmware diagnostics (POST/OBDiag) on any or all reset events. Rather than simply changing the default setting of diag-switch? to true, which carries with it other side effects (see the OpenBoot 3.x Command Reference Manual), the Ultra 450 OBP provides a...
  • Page 22 In the following example, the diag-trigger variable is used to trigger POST and OpenBoot diagnostics on all resets except XIR resets. ok setenv diag-switch? true ok setenv diag-trigger soft-reset ♦ September 1998, Revision A...

  • Page 23: Disk Drive Hot-Plug Procedures

    CHAPTER Disk Drive Hot-Plug Procedures The Sun Ultra 450 workstation and Ultra Enterprise 450 server support hot-plugging of internal disk drives. This hot-plug feature enables you to install a new disk drive, or remove and replace a failed disk drive, without shutting down the operating system or powering off the system.

  • Page 24: Adding A Hot-Pluggable Disk Drive

    4 Adding a disk drive to a system to increase storage capacity. See “Adding a Hot-Pluggable Disk Drive” on page 16. 4 Replacing a faulty disk drive while the system is running. See “Replacing a Faulty Hot-Pluggable Disk Drive” on page 19. When you intend to replace a faulty drive, prepare replacement disks ahead of time to simplify replacement later.

  • Page 25: Adding The Disk Drive

    Figure 3–1 Slot Numbers for Internal Disk Array Adding the Disk Drive Refer to the Sun Ultra 450 Workstation Owner’s Guide or Ultra Enterprise 450 Server Owner’s Guide for drive installation instructions. Configuring the Solaris Environment After physically installing the disk drive, you must create a new device entry for the drive in the /devices, /dev/dsk, and /dev/rdsk hierarchies.

  • Page 26: Configuring The New Disk Drive In Your Application

    # drvconfig # disks 2. To verify that the new disk has been created, type: # ls -lt /dev/dsk | more lrwxrwxrwx 1 root root 41 Jan 30 09:07 c0t3d0s0 -> ../../devices/pci@1f,4000/scsi@3/sd@ lrwxrwxrwx 1 root root 41 Jan 30 09:07 c0t3d0s1 -> ../../devices/pci@1f,4000/scsi@3/sd@ lrwxrwxrwx 1 root root...

  • Page 27: Adding A Disk To A Solstice Disksuite Disk Set

    2. Select a disk slice for your UFS file system and create a new file system on the slice: # newfs /dev/rdsk/cwtxdysz For example: newfs /dev/rdsk/c0t3d0s2 Refer to the newfs(1M) man page for more information. 3. If necessary, create a mount point for the new file system: # mkdir mount_point where mount_point is a fully qualified path name.

  • Page 28: Prepare Spare Drives

    The way in which you replace a faulty disk drive depends on the application you are using. Each application is different, but requires that you: 1. Determine which disk drive is failing or has failed 2. Remove the disk 3. Add the replacement drive 4.

  • Page 29: Replacing The Disk Drive In Your Application

    Figure 3–2 Disk Slot Numbers and LED Locations In order to perform a disk hot-plug procedure, you need to know the slot number of the faulty disk (0 through 19) and its logical device name (for example, c2t3d0). If you know the disk slot number, it is possible to determine the logical device name, and vice versa.

  • Page 30: Unix File System (Ufs)

    UNIX File System (UFS) The following procedure describes how to deconfigure a disk being used by one or more UFS file systems. Caution - These procedures should be performed only by a qualified system administrator. Performing hot-plug operations on an active disk drive can result in data loss if performed incorrectly.
  • Page 31 Removing and Replacing the Disk Drive Refer to the Sun Ultra 450 Workstation Owner’s Guide or Ultra Enterprise 450 Server Owner’s Guide for instructions on how to remove and replace disk drives.

  • Page 32: Solstice Disksuite

    If you have saved a disk partition table using the format utility and the replacement disk type matches the old disk type, then you can use the format utility"s partition section to configure the partition table of the replacement disk. See the select and label commands in the partition section. If the replacement disk is of a different type than the disk it replaced, you can use the partition size information from the previous disk to set the partition table for the replacement disk.
  • Page 33 If the disk label can still be read, save the disk partitioning at this time. Note - Save all the disk partitioning information immediately after configuring metadevices or file systems for use when recovering from device failure later. Use the prtvtoc command to save the partition information. # prtvtoc /dev/rdsk/cwtxdys0 >...
  • Page 34 # umount /export/home2 Removing and Replacing the Disk Drive Refer to the Sun Ultra 450 Workstation Owner’s Guide or Ultra Enterprise 450 Server Owner’s Guide for instructions on how to remove and replace disk drives. Restoring the Solstice DiskSuite Diskset Files Use the following procedure to configure a slice on a disk to be used with the...

  • Page 35: Removing A Hot-Pluggable Disk Drive

    2. Replace any database replicas. For example: # metadb -a -l 2000 -c 2 c1t2d0s0 3. Reattach any submirrors. For example: # metattach d20 d21 4. Re-create hotspares for each hotspare pool that contained a slice on the new disk. For example: # metahs -a hsp001 c1t2d0s1 5.

  • Page 36: Identifying The Faulty Disk Drive

    3. Reconfigure the operating environment In all cases you must select the disk and stop any activity or applications on it, unmount it, physically remove the drive, and configure the Solaris environment to recognize that the drive is no longer there. Then you must configure your application to operate without this device in place.

  • Page 37: Removing A Disk Drive From Your Application

    logical device name from a physical device name (such as /devices/pci@6,4000/scsi@4,1/sd@3,0). To make the necessary translation from one form of disk identifier to another, see Chapter 4. Once you have determined both the disk slot number and logical device name, you are ready to continue with this procedure. Removing a Disk Drive From Your Application Continue the hot disk removal by following the instructions for your specific application:...

  • Page 38: Solstice Disksuite

    # umount /export/home # umount /export/home2 Removing the Disk Drive Refer to the Sun Ultra 450 Workstation Owner’s Guide or Ultra Enterprise 450 Server Owner’s Guide for instructions on how to remove disk drives. Solstice DiskSuite The following procedure describes how to deconfigure a disk in use by Solstice DiskSuite.
  • Page 39 4. Delete database replicas. If there are database replicas on the disk, these must be deleted. For example: # metadb -d c1t2d0s0 5. Replace slices or clear metadevices. If any slices of the disk are in use by submirrors or within RAID metadevices, they can be replaced by other available slices.
  • Page 40 Removing the Disk Drive Refer to the Sun Ultra 450 Workstation Owner’s Guide or Ultra Enterprise 450 Server Owner’s Guide for instructions on how to remove disk drives. ♦ September 1998, Revision A...

  • Page 41: Mapping Between Logical And Physical Device Names

    Mapping Between Logical and Physical Device Names This chapter contains procedures for translating between the various logical and physical names used to identify internal disk drives in a Sun Ultra 450 workstation or Ultra Enterprise 450 server running the Solaris 7 operating environment. Overview Both the Sun Ultra 450 workstation and the Ultra Enterprise 450 server can accommodate up to 20 internal UltraSCSI disk drives.

  • Page 42: Mapping From Error Message To Disk Slot Number And Unix Logical Name

    Note - If you use Solstice SyMON software to monitor your Ultra Enterprise 450 server, there is no need to perform the following procedures. Solstice SyMON displays disk slot numbers together with physical and logical device names in its Physical View and Logical View consoles. For additional details, please see the Solstice SyMON User’s Guide supplied with your version of Solstice SyMON.

  • Page 43: Mapping From Unix Logical Name To Disk Slot Number

    lrwxrwxrwx 1 root root 45 Jan 30 09:07 c12t3d0s6 -> ../../devices/pci@6,4000/scsi@4,1/sd@3 lrwxrwxrwx 1 root root 45 Jan 30 09:07 c12t3d0s7 -> ../../devices/pci@6,4000/scsi@4,1/sd@3 The resulting output indicates the associated UNIX logical device name. In this example, the logical device name is c12t3d0. 3.

  • Page 44: Mapping From Disk Slot Number To Unix Logical Name

    Substitute the string disk@ for sd@ in the physical device name determined in Step 1 on page 34. The result in this example is /pci@1f,4000/scsi@3/disk@0. Use the grep command to find this name in the output of the prtconf command: % prtconf -vp | grep /pci@1f,4000/scsi@3/disk@0 bootpath: "/pci@1f,4000/scsi@3/disk@0,0:a"...
  • Page 45 % ls -l /dev/rdsk | grep /pci@1f,4000/scsi@3/sd@3 lrwxrwxrwx 1 root root 45 Jan 30 09:07 c0t3d0s0 -> ../../devices/pci@1f,4000/scsi@3/sd@3, lrwxrwxrwx 1 root root 45 Jan 30 09:07 c0t3d0s1 -> ../../devices/pci@1f,4000/scsi@3/sd@3, lrwxrwxrwx 1 root root 45 Jan 30 09:07 c0t3d0s2 -> ../../devices/pci@1f,4000/scsi@3/sd@3, lrwxrwxrwx 1 root root...

This manual is also suitable for:

Ultra enterprise 450

Table of Contents