Sun Microsystems Enterprise 250 Platform Notes
  1. Manuals
  2. Brands
  3. Sun Microsystems Manuals
  4. Server
  5. Enterprise 250
  6. Platform notes
Sun Microsystems Enterprise 250 Platform Notes

Sun Microsystems Enterprise 250 Platform Notes

Hide thumbs Also See for Enterprise 250:
Table of Contents

Advertisement

Quick Links

Download this manual
Platform Notes: Sun Enterprise
250 Server
Sun Microsystems, Inc.
901 San Antonio Road
Palo Alto, CA 94303-4900
U.S.A
Part No.: 805-4453-10
October 1998 , Revision A
Send comments about this document to:
docfeedback@sun.com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Enterprise 250 and is the answer not in the manual?

Questions and answers

Related Manuals for Sun Microsystems Enterprise 250

Summary of Contents for Sun Microsystems Enterprise 250

  • Page 1 Platform Notes: Sun Enterprise 250 Server Sun Microsystems, Inc. 901 San Antonio Road Palo Alto, CA 94303-4900 U.S.A Part No.: 805-4453-10 October 1998 , Revision A Send comments about this document to: docfeedback@sun.com...
  • Page 2 Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd. Sun, Sun Microsystems, le logo Sun, Java, le logo Java Coffee Cup, et Solaris sont des marques de fabrique ou des marques déposées, ou marques de service, de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc.

  • Page 3: Preface

    Preface Platform Notes: Sun Enterprise 250 Server contains the following information for system administrators and advanced users of Sun Enterprise 250 servers: OpenBoot™ commands and variables for configuring various aspects of system behavior Detailed software-related procedures for adding, removing, or replacing...
  • Page 4 C shell, Bourne shell, and Korn shell. Shell Prompts TABLE P-1 Shell Prompt C shell machine_name% C shell superuser machine_name# Bourne shell and Korn shell Bourne shell and Korn shell superuser Platform Notes: Sun Enterprise 250 Server • September 1998...
  • Page 5 Related Documentation Related Documentation Titles TABLE P-3 Application Title Hardware installation and service Sun Enterprise 250 Server Owner’s Guide System and network administration Solaris System Administrator AnswerBook Miscellaneous Solaris on Sun Hardware AnswerBook Solaris Handbook for Sun Peripherals Solaris 7 Sun Hardware Platform Guide...
  • Page 6 We are interested in improving our documentation and welcome your comments and suggestions. You can email your comments to us at: docfeedback@sun.com. Please include the part number of your document in the subject line of your email. Platform Notes: Sun Enterprise 250 Server • September 1998...

  • Page 7: Table Of Contents

    Contents Preface iii System Configuration Parameters 1 UPA Probing 2 PCI Probing 2 Environmental Monitoring and Control 4 Automatic System Recovery 5 “Soft” Deconfiguration via Status Property 5 “Hard” Deconfiguration 5 ASR User Override Capability 6 Auto-Boot Options 7 Reset Scenarios 8 Disk Drive Hot-Plug Procedures Overview 11 Adding a Hot-Pluggable Disk Drive 12...
  • Page 8 Mapping From Error Message to Disk Slot Number and UNIX Logical Name 34 Mapping From UNIX Logical Name to Disk Slot Number 36 Mapping From Disk Slot Number to UNIX Logical Name 37 viii Platform Notes: Sun Enterprise 250 Server • September 1998...

  • Page 9: System Configuration Parameters

    C H A P T E R System Configuration Parameters This chapter describes the NVRAM configuration variables and OpenBoot PROM (OBP) commands available for configuring the following aspects of Sun Enterprise 250 system behavior: “UPA Probing “PCI Probing “Environmental Monitoring and Control “Automatic System Recovery...

  • Page 10: Upa Probing

    Ultra Port Architecture (UPA) bus, a switched system bus that provides up to 32 port ID addresses (or slots) for high-speed motherboard devices like CPUs, I/O bridges, and frame buffers. The Enterprise 250 server provides up to three active ports for the following subsystems.
  • Page 11 pci0-probe-list. This variable controls both the probing order and exclusion of devices on PCI Bus 0. The values that you can specify in the pci0-probe-list are defined in the following table. Probe Values TABLE 1-2 PCI Device Number Function PCI slot 2 (as labeled on system rear panel) On-board SCSI controller for internal and external SCSI devices PCI slot 1 (as labeled on system rear panel) PCI slot 0 (as labeled on system rear panel)

  • Page 12: Environmental Monitoring And Control

    Environmental Monitoring and Control Environmental monitoring and control capabilities for Enterprise 250 servers 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 13: Automatic System Recovery

    Automatic System Recovery The automatic system recovery (ASR) feature allows Enterprise 250 servers 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 14: 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@1f,2000 /pci@1f,4000/scsi@3,1 The Enterprise 250 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 15: Auto-Boot Options

    Note – There are duplications between the soft and hard overrides. If possible, the hard override commands asr-enable and asr-disable should be used. You can generate a list of valid parameters for asr-disable and asr-enable by issuing either command without parameters. ok asr-disable ? Invalid subsystem name: Known 'enable/disable' subsystem components are:...

  • Page 16: Reset Scenarios

    NVRAM variable diag-switch? is set to true. The default setting for this variable is false. To support ASR in Enterprise 250 servers, 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 Enterprise 250 OBP provides a...
  • Page 17 Note – diag-trigger has no effect unless diag-switch? is set to true. Reset Diagnostic Trigger Settings and Effects TABLE 1-4 Setting Function Runs diagnostics only on power-on resets. power-reset (default) Runs diagnostics only on power-on resets, fatal hardware errors, and error-reset watchdog reset events.
  • Page 18 Platform Notes: Sun Enterprise 250 Server • September 1998...

  • Page 19: Disk Drive Hot-Plug Procedures

    C H A P T E R Disk Drive Hot-Plug Procedures The Sun Enterprise 250 server supports “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 20: Adding A Hot-Pluggable Disk Drive

    1. Select a slot for the new disk drive. The Enterprise 250 server’s internal disk array can accommodate up to six UltraSCSI disk drives. The figure below shows the system’s six internal disk slots. Disk slots are numbered from 0 to 5.
  • Page 21 FIGURE 2-1 2. Insert the new disk drive into the selected slot. Refer to the Sun Enterprise 250 Server Owner’s Guide for drive installation instructions. 3. Use the drvconfig command to create a new device entry for the drive in the...
  • Page 22 Press RETURN when ready to continue Here, physical_device_name is the full physical device name determined in Step 4. You can safely ignore the warning message since the Enterprise 250 SCSI bus does not require quiescing. 6. Press Return to complete the hot-plug operation.

  • Page 23: Configuring The New Disk Drive Within Your Application

    7. To verify that the new disk has been created, type: # ls -lt /dev/dsk | more lrwxrwxrwx 1 root root 41 Jan 30 09:07 c0t11d0s0 -> ../../devices/pci@1f,4000/scsi@3/sd@b,0:a lrwxrwxrwx 1 root root 41 Jan 30 09:07 c0t11d0s1 -> ../../devices/pci@1f,4000/scsi@3/sd@b,0:b lrwxrwxrwx 1 root root 41 Jan 30 09:07 c0t11d0s2 ->...

  • Page 24: Configuring The New Disk Drive For A Unix File System (Ufs)

    See the vfstab(4) man page for more details. 5. Mount the new file system using the mount command: # mount mount_point where mount_point is the directory you created. The file system is ready to be used. Platform Notes: Sun Enterprise 250 Server • September 1998...

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

    Adding a Disk to a Solstice DiskSuite Disk Set You can use any disk you add to the system for Solstice DiskSuite (SDS) new or existing metadevices. Refer to the Solstice DiskSuite documentation for information on configuring the disk drive. Replacing a Faulty Hot-Pluggable Disk Drive This section contains information on configuring your system to replace a disk drive...

  • Page 26: Identifying The Faulty Disk Drive

    To make the necessary translation from one form of disk identifier to another, see the Chapter Mapping Between Logical and Physical Device Names. Once you have determined both the disk slot number and logical device name, you are ready to continue with this procedure. Platform Notes: Sun Enterprise 250 Server • September 1998...

  • Page 27: Replacing The Disk Drive Within Your Application

    Replacing the Disk Drive Within Your Application Continue the disk replacement by following the instructions for your specific application. “UNIX File System (UFS) “Solstice DiskSuite UNIX File System (UFS) The following procedure describes how to deconfigure a disk being used by one or more UFS file systems.
  • Page 28 A large number of error messages may be displayed in the system console and in the /var directory during the umount operation. If the umount operation does not complete, you may have to restart the system. Platform Notes: Sun Enterprise 250 Server • September 1998...
  • Page 29 (/dev/rdsk/c0t11d0s2). You must specify slice 2, which represents the entire disk. Note that this command also accepts a physical device name as an alternative. You can safely ignore the warning message since the Enterprise 250 SCSI bus does not require quiescing.

  • Page 30: Solstice Disksuite

    2. Type su and your superuser password. 3. If possible, save the partition table for the disk you intend to replace. If the disk label can still be read, save the disk partitioning at this time. Platform Notes: Sun Enterprise 250 Server • September 1998...
  • Page 31 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 > saved_partition_table_file For example: # prtvtoc /dev/rdsk/c0t11d0s0 > /etc/c0t11d0s0.vtoc 4.
  • Page 32 For each file system returned, type: # umount file_system where file_system is the first field for each line returned in Step 4. For example: # umount /export/home # umount /export/home1 Platform Notes: Sun Enterprise 250 Server • September 1998...
  • Page 33 (/dev/rdsk/c0t11d0s2). You must specify slice 2, which represents the entire disk. Note that this command also accepts a physical device name as an alternative. You can safely ignore the warning message since the Enterprise 250 SCSI bus does not require quiescing.

  • Page 34: Removing A Hot-Pluggable Disk Drive

    Solaris environment to recognize that the drive is no longer there. Then you must configure your application to operate without this device in place. Platform Notes: Sun Enterprise 250 Server • September 1998...

  • Page 35: Identifying The Faulty Disk Drive

    Identifying the Faulty Disk Drive Disk errors may be reported in a number of different ways. Often you can find messages about failing or failed disks in your system console. This information is also logged in the /usr/adm/messages file(s). These error messages typically refer to a failed disk drive by its UNIX physical device name (such as /devices/pci@1f,4000/scsi@3/sd@b,0) and its UNIX device instance name (such as sd11).

  • Page 36: Removing A Disk Drive From Your Application

    3. Stop any activity or application processes on the file systems to be deconfigured. 4. Back up your system. 5. Determine what file system(s) are on the disk: # mount | grep cwtx 6. Unmount any file systems on the disk. Platform Notes: Sun Enterprise 250 Server • September 1998...
  • Page 37 Note that this command also accepts a physical device name as an alternative. You can safely ignore the warning message since the Enterprise 250 SCSI bus does not require quiescing. 8. Remove the disk drive from its slot.

  • Page 38: Solstice Disksuite

    If any slices of the disk are used by hotspare pools, they can be replaced by other available slices. For example: # metahs -r all c0t11d0s1 c0t8d0s1 7. Unmount any file systems on the disk. Platform Notes: Sun Enterprise 250 Server • September 1998...
  • Page 39 Note that this command also accepts a physical device name as an alternative. You can safely ignore the warning message since the Enterprise 250 SCSI bus does not require quiescing. 9. Remove the disk drive from its slot.
  • Page 40 Platform Notes: Sun Enterprise 250 Server • September 1998...

  • 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 Enterprise 250 server running the Solaris 2.x operating environment. Overview The Enterprise 250 server can accommodate up to six 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 Enterprise 250 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 2. Determine the UNIX logical device name by listing the contents of the /dev/rdsk directory. Use the grep command to filter the output for any occurrence of the UNIX physical device name determined in Step 1: % ls -l /dev/rdsk | grep /pci@1f,4000/scsi@3/sd@b lrwxrwxrwx 1 root root...

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

    4. If the output does not provide a slot number, the device is either a removable media device (CD-ROM or tape drive) or an external device. Platform Notes: Sun Enterprise 250 Server • September 1998...

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

    Mapping From Disk Slot Number to UNIX Logical Name This section describes how to translate from a known disk slot number (0 through 5) to a UNIX logical device name such as c0t11d0. The example in this procedure assumes a known disk slot number of 4. 1.
  • Page 46 1 root root 45 Nov 24 10:41 c0t11d0s7 - > ../../devices/pci@1f,4000/scsi@3/sd@b,0:h,raw The resulting output indicates the associated UNIX logical device name. In this example, the logical device name is c0t11d0. Platform Notes: Sun Enterprise 250 Server • September 1998...

Table of Contents