Solaris Reference – How to Create a New Domain on Sun Enterprise 10K
Below Procedure describes how to add a new two-board domain, using Sun direct attach boot storage to an existing Sun Enterprise 10000 platform.
You will use the System Service Process (SSP) as a boot server for the domain’s new operating system. The SSP is a SPARC workstation or SPARC server that enables you to control and monitor the Sun Enterprise 10000 system. You can use a Sun Ultra 5 or Sun Enterprise 250 workstation, or a Sun Netra T1 server as an SSP.
As an example, we are creating a new domain called “bob” on a platform called “enterprise-host,” using system boards 1 and 12, running the Solaris 8 Operating System on ip address 192.168.100.1.
Complete Procedure for Creating a New Domain on a Sun Enterprise 10000 Platform.
Step 1. Inserting the New Hardware
- Select 2 empty slots for the new boards to be inserted into, or select present but unused System Boards currently in the platform.
- The domain must have the following to be able to support an operatingsystem.
- 1 to 4 CPUs on the system board.
- Memory (The system boards only support fully populated banks of 32 MB or 128 MB memory. Mixing memory in a board is not supported.)
- Sbus or PCI mezzanine with at least 1 supported Host Bus Adaptor (HBA) for the boot.
- At least one Sbus or PCI network interface for the net boot from the boot server.
- Insert the new hardware.
- On the MAIN ssp, Power on the new boards:
enterprise-host:bob% power -on -sb 1 12
Step 2. Running the Autoconfig Command
CAUTION: Run the autoconfig command only on the new or moved boards. Incorrectly running the autoconfig command could cause running domains to fail.
- On MAIN SSP as user ssp:
enterprise-host:bob% setfailover off
- Run Autoconfig:
enterprise-host:bob% autoconfig sysboard1 (ensure there is no space between sysboard and board #)
Do not reboot yet
enterprise-host:bob% autoconfig sysboard12
Now reboot the SSP.
Note: in this case there is no need to sync the SSPs because failover is set to ‘off’.
- When the SSP is back up (confirmed by running showfailover):
enterprise-host:bob% setfailover on (this should sync the SSP’s)
Step 3. Preparing the SSP Domain Environment
- Verify that you have a eeprom image for your domain that is NOT being used for an existing domain.
- Log in to MAIN SSP as user ssp.
enterprise-host:bob% cd $SSPVAR/.ssp_private/eeprom_save
- Select an unused eeprom image if you have one, for example, eeprom.image_8:
enterprise-host:bob% mv eeprom.image_8 eeprom.image.bob
NOTE: It is always better to move the unused file to the name of the domain rather than coping the file. Moving the unused file reduces the chance of the file being reused and causing duplicate host ids on your platform. If you do not have a spare image, request a new key from Sun Microsystems so that you can create an image.To create an image, use the Sun supplied key and serial number with the sys_id command. To determine if an image is used, you can check it’s mac address and compare to the current domains.
|enterprise-host:bob% sys_id -d -f eeprom.image_8
IDPROM in eeprom.image_8
Format = 0x01
Machine Type = 0x80
Ethernet Address = 0:0:be:a6:7f:9a
Manufacturing Date = Wed Dec 31 19:00:00 1969
Serial Number (Host ID) = 0xa67f9a
Checksum = 0x3f
enterprise-host:bob% domain_create -d bob -b 1 12 -o 5.8 -p enterprise-host
Answer “Yes” to proceed.
Step 4. Powering on the Domain
- First change to the correct domain environment:
enterprise-host:joe% domain_switch bob
NOTE: Failure to change to the correct domain environment could result in crashing an existing domain.
- Power on the boards, if they’re not powered on already:
enterprise-host:bob% power -on -sb 1 12
enterprise-host:bob% bringup -A off(This is the equivalent of autoboot=false.)
The domain will now post with level 16 diagnostics.
- Confirm the domain passes a single pass level 16.
- Because this is all new hardware, re-run the bringup with a level 127 to fully test the hardware:
enterprise-host:bob% bringup -A off -l127
enterprise-host:bob% netcon -g (to connect to the domain after Open Boot PROM handover)
Step 5. Setting Up for Net Boot
1. It is recommended to use a private network between the SSP and Domains to install o/s. Or if the customer has a jumpstart server on the subnet allready, point to that.
2. Verify that the network interface you will use is connected to the network:
>ok watch-net-all (to check for traffic)
>ok show-nets(to get path for nvalias cmd)
3. Identify the interface to which the cable is connected:
>ok nvalias bootnet <selected interfac. e >
4. Confirm the Mac address (presuming a local_mac_address?=false):
>ok banner Ethernet address 0:0:be:b9:2b:3f (example Mac/ethernet address)
5. As root on the SSP, add bob to /etc/hosts: 192.168.100.1 bob
6. As root on the SSP, add bob to /etc/ethers: 0:0:be:b9:2b:3f bob
7. Change directories to the boot image directory:
root# cd /export/install/8/Solaris_8/Tools
8. Set up bootparams etc:
root# ./add_install_client bob sun4u
9. On netcon session:
> ok boot bootnet – install (or the equivalent for the Solaris 9 OS)
10. Answer install questions. For the Solaris 8 OS installation, select “no” reboot.
11. root# ls -l /dev/rdsk/c0t0d0s0 (or the disk you installed the new OS on ) Take note of this path.
|root# /etc/halt>ok show-disks
12. Select the path to disk above:
>ok nvalias bootdisk <path to disk with new os >
13. Console login: ….
14. Enter the following, which will allow you to correct the host name and public ip address, if required:
15. Boot, configure to the correct addresses, and patch to EIS Standard.
NOTE: There are specific patches required on an Sun Enterprise 10000 domain above and beyond the standard recommended OS patch bundle. Contact your service representative for a list of these patches or source them from the EIS CD.