Sun Fire E25K Server
 
Sun Fire E20K Server
 
Sun Fire 12K Server
 
Sun Fire 15K Server
 

GCS>Sun Microsystems>Servers>High-End Servers
 

Applies to:

Goal

Solution

1. Select empty slots for the new system boards and hsPCI.
2. The domain must have the following to be able to support an O/S.
• System board ( containing CPU and memory )
• hsPCI I/O board
• At least 1 PCI HBA for OS boot disk.
• At least 1 PCI network interface ( not technically 'necessary' to load OS but certainly advisable )
3. Insert system boards and hsPCI assembly into desired locations.
4. Login as sms-svc ( platform and domain privileges ).

Step 2. Creating a new domain environment

1. Add boards to your new domain

setupplatform -d R -a sb1 sb7 io1 ( Configures board ACL'S )
addboard -d R sb1 sb7 io1 ( This will ask you to assign boards because domain is down )
setobpparams auto-boot=false

Step 3. Powering on the domain and flashupdate

1. Flashupdate the new boards to the latest versions on the SC's.
   
   setkeyswitch -d R standby
flashupdate -d R -f /opt/SUNWSMS/hostobjs/sgcpu.flash
Answer questions as directed using flashupdate utility.
   
2. After flashupdate power off domain ( new flash images require setkeyswitch off/on to be active )
   
   
   setkeyswitch -d R off
3. Initial test of domain H/W
   CAUTION: Setkeyswitch is the only supported method of testing domains on the starcat platform. Do not use hpost at the command line while there are active domain on the frame.
   
   setkeyswitch -d R on       ( The domain will now post with the default level 16 diagnostics. )
   


4. Connect to console to verify all ok
console -d R

Note -> use "~." without quotations to disconnect from console.   Confirm the domain passed a single pass level 16 ok.
Verify you did not miss any errors by checking for

a. dumps in $SMSVAR/adm/R/dump
b. Errors in last post log $SMSVAR/adm/R/post/*
c. Errors in the platform log $SMSVAR/adm/platform/messages
Since this is all new or relocated hardware, re-run the tests with a level 127 diagnostic to fully test the hardware.


To increase the domain post level temporarily edit the domains .postrc file with the following



$ vi $SMSETC/config/R/.postrc
level 127
verbose 40
err_print 64
no_ioadapt_ok      # if only testing system boards with no i/o
no_obp_handoff   # if only testing system boards with no i/o
$ chmod 644 $SMSETC/config/R/.postrc
$ setkeyswitch -d R on
IMPORTANT: Remove the file $SMSETC/config/R/.postrc after you have tested H/W.

CAUTION: Do not use the sms-svc user home directory, /var/tmp/ or the platform .postrc file to run these tests. If you forget to remove this file then this file will cause ALL domains to run a 127 post on future re-boots.


5. If the domain resources pass post successfully you can then connect to the domain console.
   
   $ console -d R

Step 4. Setting up for net boot

NOTE: Later releases of SMS such as SMS 1.5 and 1.6 are 'secure by default' when installed. This means that they automatically 'harden' the SC by turning off many services and closing a number of ports. (An smsupgrade does not automatically harden, that needs to be done manually.)

For more details, see <Document 1011222.1>, which shows what may need to be re-enabled.
To completely 'unharden' the SC if you find you cannot enable specific services, it is possible to undo the jass hardening by running


/opt/SUNWjass/bin/jass-execute -u

 and following the prompts. It is, however, recommended that the hardening be left in place, and that the specific services be re-enabled per the above document.

1. By default SMS setup the Domain has a permanent l1 connection to the Main SC. We will use this network to boot the domain and perform OS installation or boot a kernel to single user more with "boot -s" from OBP.
2. Setup and verify the network interface which will used with the domain once the OS in installed.
3. Verify that man-net devalias is correct at the domain OBP prompt. Skip to step 5 if this is correct otherwise proceed to step 4 below.
   
   OK devalias man-net .........  ( check the slot corresponds to the location of the first i/o bay in the domain, this should be the equiv. of the last line in show-nets, because the net search path is in reverse order. )
OK show-nets
4. if a "man-net" devalias is not setup then create one.
   
   OK nvalias man-net
   OK nvstore
   
   
5. Confirm Mac address ( presumes you are using local_mac_address=false )
   
   OK banner
   mac:8:0:20:b9:2b:3f ( example Mac address )
   
   
6. As root on the MAIN SC check /etc/hosts for the L1 network entry for your domain.  This should correspond to the entry in $SMSETC/config/MAN.cfg
   
   192.168.100.20 mystarcat_r
7. As root on the MAIN SC check /etc/ethers for correct entry which should correspond to the mac address returned from the output of `banner`.
   

    8:0:20:b9:2b:3f mystarcat_r

8. Install Solaris image on the System Controller.
• Each system controller is pre-installed with room for Solaris images for installing the domains from. The default directory is '/export/install/'. Customers may modify this to fit their environment.
• Insert the Solaris DVD/CD installation CD into the DVD tray on the Main System controller.
• As user root, 'cd' to the "Tools" directory of the Solaris image and run the setup_install_server command. example:
1. ./setup_install_server /export/install/s10_u3
   This will copy and prepare the image to be ready to use as an image for installation from the system controller.
9. Move to the boot image directory on the MAIN SC.
   

   # cd /export/install/SOL-02-02/Solaris_8/Tools

10. create entry for jumpstart installation.
    
    # ./add_install_client mystarcat_r sun4u
**( this will set up the bootparams ...ect )
**( This will also share the install image, and start the NFS server.)
11. On domain console session start the OS jumpstart process
    
    OK boot man-net - install   #( or equiv. for sol 9 ) if you have created a jumpstart profile for this domain, otherwise use `boot man-net` for the standard installation questions to complete your install.
Answer OS install questions. Select "no" auto reboot when prompted.
12. # ls -l /dev/rdsk/c0t0d0s0 ( or whichever disk OS is installed )  Take note of this path.
13. Halt the OS
    
    # halt
14. Set up the devalias to reflect booting off OS just loaded on disk.
    
    OK show-disks
15. Select path to disk above.
    
    OK nvalias bootdisk
OK nvstore
OK setenv boot-device=bootdisk man-net
OK setenv diag-device=bootdisk man-net
**( remember to add you mirror disk into above paths after mirroring )
16. Boot the OS which was installed on the disk.
    
    OK boot bootdisk ......
Console login:

17. Unconfigure the OS if necessary for your environment
    
    # sys-unconfig
**( This will allow you to correct the host name and public ip address if required ) .
18. Reboot
19. Boot, configure to correct addresses as prompted following a sys-unconfig and patch.
    
    NOTE: There are specific patches required on a starcat domain above and beyond the standard recommended O/S patch bundle see My Oracle Support to obtain these patches.
    

  CAUTION: Do not use the working directory as in the SF15K-initial-hpost.sh script or the platform .postrc file to run these tests. Should you forget to remove this file or not Control C out of the test script, then this .postrc file could cause ALL domains to run a 127 post, and if you have added the following lines to test only system boards, the domains may not go to OBP and fail all future re-boots.

  - if testing COD system boards (SMS 1.3 and above) or,
  - if control doesn't want to be sent to OBP after finishing POST

This solution has no attachment