Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1310667.1
Update Date:2018-04-03
Keywords:

Solution Type  Technical Instruction Sure

Solution  1310667.1 :   How to remove and replace a Starcat System Control Peripheral Board SCSI Cable:ATR:1542:4  


Related Items
  • Sun Fire E25K Server
  •  
  • Sun Fire 12K Server
  •  
  • Sun Fire 15K Server
  •  
  • Sun Fire E20K Server
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: SPARC-CAP VCAP
  •  




In this Document
Goal
Solution


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU CAP

Applies to:

Sun Fire E25K Server - Version Not Applicable and later
Sun Fire E20K Server - Version Not Applicable and later
Sun Fire 12K Server - Version Not Applicable and later
Sun Fire 15K Server - Version Not Applicable and later
Information in this document applies to any platform.

Goal

How to remove and replace a Starcat System Control Peripheral Board SCSI Cable

Solution


CAP PROBLEM OVERVIEW: System Controller Peripheral Board SCSI Cable Failure

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED:

Starcat Traning

TASK COMPLEXITY: 4

TIME ESTIMATE: 180 minutes

DELIVERY REQUIREMENT:

Immediate

FIELD ENGINEER INSTRUCTIONS

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? N/A

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

If the affected SCper is the spare goto "Shutdown Spare SC"

  1. Powering Off a System Control (SC) Board
    • If this is the main SC ensure the spare SC is available.
    • Sync the main to the spare
      sc% setdatasync backup
      If no messages are reported in /var/opt/SUNWSMS/adm/platform/messages and the command completes, the setdatasync backup was successful.
    • As a superuser on the main SC, make a backup copy of the SMS configuration:
      sc# smsbackup directory
    • From the main SC, failover (switch over) to the spare SC by typing:
      sc% setfailover force
    • On the main SC, verify that it has assumed the main role and that failover is disabled by typing:
      sc% showfailover -r
      MAIN
      sc% showfailover
      SC Failover Status: DISABLED
    • On the main SC, disable the failover mechanism by typing:
      sc% setfailover off
    • Verify the failover is DISABLED by typing:
      sc% showfailover
      SC Failover Status: DISABLED

      Note: Before shutting down and replacing an SC make sure that clock from the other SC to all components is in a good state. To check this run "showboards -c" command for SMS 1.4 and later. ( See Document ID: *1006413.1- Check clock status before replacement of System controller*for more information )
    • Shutdown the spare sc:
      sc_spare# shutdown -y -g seconds -i 0
    • Power off the spare (inactive) SC from the main SC by typing the following SMS command:
      sc% poweroff scx
  2. Remove the SC Peripheral Board
  3. Remove the SCSI Cable
    • At the center SCSI access panel, remove the four M3x6 flathead screws and remove the access panel.
    • Disconnect and replace the SCSI ribbon cable connector.
  4. Install the center SCSI access panel and secure with the four M3x6 flathead screws.
    • Remove the connector protective cover from the board being installed and inspect the connector for any damaged or gaps between the pins.
    • Ensure board alignment tabs are not bent.
    • Inspect the mating connector before inserting the new board.
  5. Install SC Peripheral Board
  6. Power on SC Peripheral Board. ( From the main SC type: )
    sc% resetsc
  7. Verify System Control (SC) Peripheral Board
    • Monitor SCPOST for any error messages during SC boot. SCPOST messages are output to an SMS console. To read SC SMS console messages, you must attach a console cable and terminal to the SC.
    • Ensure that Solaris software can communicate to all the peripheral devices.
      • For the DVD-ROM, insert a CD and ensure it mounts properly.
      • For hard disks, check that the /dev/dsk and /dev/rdsk entries are correct and that the Solaris software can access the disks (format, prtvtoc).
      • For the DAT drive, check that the /dev/rmt entries are correct and that the Solaris software can access the tape device (mt status).

OBTAIN CUSTOMER ACCEPTANCE

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:  N/A

PARTS NOTE:  N/A

REFERENCE INFORMATION:
Service Manual: http://download.oracle.com/docs/cd/E19065-01/servers.e25k/index.html


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback