Sun Netra T5220 Server Installation Guide

Powering On the System

This chapter includes instructions for booting the server and for enabling the system controller network management port.

The following topics are included:

• Powering On the System for the First Time
• Enabling the Service Processor Network Management Port
• Logging In To the Service Processor
• Using the Service Processor for Common Operations
• Booting the Solaris Operating System
• Verifying System Functionality

---

Powering On the System for the First Time

This section provides an overview and instructions for powering on your system the first time.

ILOM System Console

When you power on the system, the boot process begins under the control of the Integrated Lights Out Manager (ILOM) system console. The system console displays status and error messages generated by firmware-based tests during system startup.

For a more detailed discussion on configuring the system console and connecting terminals, refer to the Sun Netra T5220 Server Administration Guide.

ILOM Service Processor

After the system console finishes its low-level system diagnostics, the ILOM service processor initializes and runs a higher level of diagnostics. When you access the ILOM service processor using a device connected to the serial management port, you see the output of the ILOM diagnostics.

By default, the network management port is configured to automatically retrieve network configuration using Dynamic Host Configuration Protocol (DHCP) and to allow connections using Secure Shell (SSH).

Once the network management port (NET MGT) has been assigned an IP address, you can connect to the ILOM service processor using SSH.

CLIs, User Accounts, and Passwords for Connecting to the ILOM Service Processor

When connecting to the ILOM service processor for the first time using the serial or network management ports, the default CLI is ILOM, the default user account is root, and the default password is changeme. Examples in this document use the default ILOM CLI.

ILOM also provides an Advanced Lights Out Management (ALOM) compatability CLI that uses commands that resemble the ALOM CMT CLI commands. To access the ALOM compatability CLI, you must first create an admin account with the role of administrator. Once you create the admin account, assign the ALOM compatability CLI as the default CLI (role=administrator, cli=alom). For more information on using the ALOM compatability CLI, refer to the Integrated Lights Out Management 2.0 (ILOM 2.0) Supplement for Sun Netra T5220 Server.

The service processor runs on the 3.3V standby voltage. As soon as AC power is connected to the system, the service processor powers on, runs diagnostics, and initializes the ILOM firmware.

1. Connect a terminal or a terminal emulator (PC or workstation) to the service processor serial management port.

Configure the terminal or terminal emulator with these settings:

• 9600 baud
• 8 bits
• No parity
• 1 Stop bit
• No handshake

2. Turn on the terminal or terminal emulator.

3. Connect the AC power cables to Power Supply 0 and Power Supply 1. Watch the terminal for system messages.

FIGURE 6-1 Rear Panel Power Connectors of a Sun Netra T5220 Server

After the service processor boots, the service processor login prompt is displayed on the serial console. The following example shows a partial output from the service processor boot sequence leading to the login prompt.

U-Boot 1.1.1 (August 23 2007 - 21:30:12)
...
POST cpu PASSED
POST ethernet PASSED
Hit any key to stop autoboot:  0
## Booting image at fe080000 ...
  
IP Protocols: ICMP, UDP, TCP, IGMP
 
Checking all file systems...
fsck 1.37 (21-Mar-2005)
Setting kernel variables ... 
... done. 
Mounting local filesystems... 
Cleaning /tmp /var/run /var/lock. 
 
Identifying DOC Device Type(G3/G4/H3) ... 
OK 
 
Configuring network interfaces...Internet Systems Consortium DHCP 
Client V3.0.1 
Copyright 2007 Internet Systems Consortium. 
All rights reserved. 
For info, please visit http://www.isc.org/products/DHCP 
 
eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX. 
Listening on LPF/eth0/00:14:4f:3f:8c:af 
Sending on   LPF/eth0/00:14:4f:3f:8c:af 
Sending on   Socket/fallback 
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 
eth0: link up, 100 Mbps Full Duplex, auto-negotiation complete. 
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 
Hostname: hostname. 
Starting portmap daemon: portmap. 
Initializing random number generator...done. 
INIT: Entering runlevel: 3 
Starting system log daemon: syslogd and klogd. 
Starting periodic command scheduler: cron. 
Starting IPMI Stack...... Done. 
Starting OpenBSD Secure Shell server: sshd. 
Starting Servicetags listener: stlistener. 
Starting FRU update program: frutool. 
 
hostname login: 

In hard drive HDD0, the Solaris OS is preinstalled.

  If you do not want to start the preinstalled OS, set the OBP parameter auto-boot? to false. For example from the ILOM CLI:

-> bootmode bootscript "setenv auto-boot? false"

---

Enabling the Service Processor Network Management Port

The service processor network management port is not operational until you configure network settings for the service processor. Configure the service processor in this order:

1. After the service processor boots, access the ILOM CLI through the serial management port. See To Log In To the Service Processor Using the Serial Management Port.

2. Configure the service processor. See Configuring the Service Processor Network Management Port.

3. Commit the changes to the service processor parameters. See Step 7 in To Power On the System for the First Time.

You can now use the network management port at any time to access the service processor. See To Log In To the Service Processor Using the Network Management Port.

---

Logging In To the Service Processor

If you are powering on the system for the first time after installation, use the service processor serial port to power on the system and run POST. See To Log In To the Service Processor Using the Serial Management Port.

If the network management port has already been configured, you can use it instead of the serial management port. See To Log In To the Service Processor Using the Network Management Port.

After the service processor boots, access the ILOM CLI to configure and manage the system. The ILOM CLI prompt (->) is displayed at the first time the service processor is booted. The default configuration provides an ILOM CLI root user account. The default root password is changeme. Change the password using the service processor ILOM CLI password command.

1. If this is the first time the system has been powered on, use the password command to change the root password.

...
Starting OpenBSD Secure Shell server: sshd. 
Starting Servicetags listener: stlistener. 
Starting FRU update program: frutool. 
 
hostname login: root 
Password: changeme 
 
Copyright 2007 Sun Microsystems, Inc. All rights reserved. 
Use is subject to license terms. 
...
Federal Acquisitions: Commercial Software -- Government Users Subject to Standard License Terms and Conditions. 
... 
 
Warning: password is set to factory default. 
 
-> set /SP/users/root password 
Enter new password: ******** 
Enter new password again: ******** 
 
-> 

2. Enter root for the login name followed by your password.

...
hostname login: root 
Password: password (nothing displayed) 
Waiting for daemons to initialize... 
 
Daemons ready 
 
Sun(TM) Integrated Lights Out Manager 
 
Version 2.0.0.0 
 
Copyright 2007 Sun Microsystems, Inc. All rights reserved. 
Use is subject to license terms. 
 
-> 

Configuring the Service Processor Network Management Port

Use this procedure only when:

• You are unable to use DHCP and SSH on your network.
• You need to modify the ILOM service processor network management port settings.

In this procedure, you connect to the ILOM service processor using the serial management port to manually reconfigure the network management port.

Set these network parameters according to the specific details of your network configuration:

• /SP/network state - Specifies whether the service processor is on the network or not
• /SP/network pendingipaddress - IP address of the service processor
• /SP/network pendingipgateway - IP address of the gateway for the subnet
• /SP/network pendingipnetmask - Netmask for the service processor subnet
• /SP/network pindingipdiscovery - Specifies whether the service processor uses DHCP or static IP address assignment
• /SP/network commitpending - Commits the service processor to use the pending settings

Configure these parameters with the set command. The usage is as follows:
set target property=value where /SP/network is the target and pendingipaddress=xx.x.xx.xxx, for example, is the property=value. The following example sets the pending service processor IP address:

-> set /SP/network pendingipaddress=xx.x.xx.xxx 
Set 'pendingipaddress' to 'xx.x.xx.xxx' 

1. Set the /SP/network state parameter to enabled.

-> set /SP/network state=enabled 
Set 'state' to 'enabled' 

2. Enable and disable SSH connections as needed.

-> set /SP/services/ssh state=enabled
Set 'state' to 'enabled'
-> set /SP/services/ssh state=disabled
Set 'state' to 'disabled'

See the Integrated Lights Out Management 2.0 (ILOM 2.0) Supplement for Sun Netra T5220 Server for more information about SSH support in ILOM.

3. Choose one of these methods to configure the service processor using information from your network administrator:

• Use DHCP to retrieve the network settings. Go to Step 4.
• Configure a static IP configuration. Go to Step 5.

4. If you choose to use DHCP, set pendingipdiscovery to dhcp.

-> set /SP/network pendingipdiscovery=dhcp 
Set 'pendingipdiscovery' to 'dhcp' 

Go to Step 6.

5. If you choose to use a static IP configuration, set the parameters pendingipdiscovery, pendingipaddress, pendingipgateway, and pendingipnetmask as follows.

a. Set the service processor to accept a static IP address.

-> set /SP/network pendingipdiscovery=static 
Set 'pendingipdiscovery' to 'static' 

b. Set the IP address for the service processor.

-> set /SP/network pendingipaddress=service-processor-IPaddr 
Set 'pendingipaddress' to 'service-processor-IPaddr' 

c. Set the IP address for the service processor gateway.

-> set /SP/network pendingipgateway=gateway-IPaddr 
Set 'pendingipgateway' to 'gateway-IPaddr' 

d. Set the netmask for the service processor.

-> set /SP/network pendingipnetmask=255.255.255.0 
Set 'pendingipnetmask' to '255.255.255.0' 

This example uses 255.255.255.0 to set the netmask. Your network environment subnet might require a different netmask. Use a netmask number most appropriate to your environment.

6. Use the show /SP/network command to verify that the parameters were set correctly.

-> show /SP/network 
  /SP/network 
     Targets: 
     Properties: 
         commitpending = (Cannot show property) 
         dhcp_server_ip = xx.x.xx.x 
         ipaddress = xx.x.xx.x 
         ipdiscovery = dhcp 
         ipgateway = xx.x.xx.x 
         ipnetmask = 255.255.252.0 
         macaddress = 00:14:4F:3F:8C:AF 
         pendingipaddress = xx.x.xx.x 
         pendingipdiscovery = static 
         pendingipgateway = xx.x.xx.x 
         pendingipnetmask = 255.255.255.0 
         state = enabled 
     Commands: 
         cd 
         set 
         show 
-> 

7. Commit the changes to the service processor network parameters.

-> set /SP/network commitpending=true 
Set 'commitpending' to 'true' 

It is not necessary to reset the service processor for new network values to take effect. To commit the changes to the service processor network parameters, use the
set /SP/network commitpending=true command. See Step 7 in Configuring the Service Processor Network Management Port.

  Type the reset /SP command.

You are prompted to confirm that you want to reset the service processor. Reply y when prompted.

-> reset /SP 
Are you sure you want to reset /SP (y/n)? y 

The service processor resets, runs diagnostics, and returns to the login prompt.

... 
hostname login: root 
Password: password (nothing displayed) 
Waiting for daemons to initialize... 
 
Daemons ready 
 
Sun(TM) Integrated Lights Out Manager 
 
Version 2.0.0.0 
 
Copyright 2007 Sun Microsystems, Inc. All rights reserved. 
Use is subject to license terms. 
 
-> 

  Open an SSH session and connect to the service processor by specifying its network address.

% ssh root@xx.xxx.xx.x 
...
Are you sure you want to continue connecting (yes/no)? yes 
...
Password: password (nothing displayed) 
Waiting for daemons to initialize...
 
Daemons ready 
 
Sun(TM) Integrated Lights Out Manager 
 
Version 2.0.0.0 
 
Copyright 2007 Sun Microsystems, Inc. All rights reserved. 
Use is subject to license terms. 
 
-> 

---

Using the Service Processor for Common Operations

1. Perform the following steps to verify that there are no faults:

a. Set the virtual keyswitch to diag mode so that POST will run in Service mode.

-> set /SYS keyswitch_state=diag

b. To initiate the power on sequence, type the start /SYS command.

You see an ILOM CLI alert message on the system console. This message indicates that the system has reset.

-> start /SYS
Are you sure you want to start /SYS (y/n)? y
Starting /SYS
 
-> 

c. Switch to the system console to view POST output.

-> start /SP/console

Watch the POST output for possible fault messages. The following output is a sign that POST did not detect any faults:

.
.
.
0:0>POST Passed all devices. 
0:0> 
0:0>DEMON: (Diagnostics Engineering MONitor) 
0:0>Select one of the following functions 
0:0>POST:Return to OBP. 
0:0>INFO: 
0:0>POST Passed all devices. 
0:0>Master set ACK for vbsc runpost command and spin... 

2. Check the POST execution result with the following command:

-> show /SYS/faultmgmt -level all

3. Use the set /SYS keyswitch_state=normal command to return the virtual keyswitch to Normal mode (default) so that the system can power on and start the boot process.

-> set /SYS keyswitch_state=normal

Output from POST, OpenBoot, and the Solaris OS is displayed in the system console using the network console on the service processor.

  Type the start /SP/console command.

Multiple users can be connected to the console, but only one can be attached.

-> start /SP/console 
Are you sure you want to start /SP/console (y/n)? y 
Serial console started.  To stop, type #.

After you issue the start /SYS command, the CPU and memory controllers initialize, and eventually OpenBoot initializes. After a number of system console messages, the ok prompt appears, or the system will boot into the Solaris OS.

The following example output is a small section of the complete output.

-> start /SYS
Find dropin, Copying Done, Size 0000.0000.0000.1110 
Find dropin, (copied), Decompressing Done, Size 0000.0000.0006.06e0 cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu vpci mem32base, mem64base, cfgbase: e800000000 e000000000 e900000000 
pci /pci@780: Device 0 pci pci 
/pci@780/pci@0: Device 0 Nothing there
/pci@780/pci@0: Device 1 pci pci 
 
....................
 
/pci@7c0/pci@0: Device a Nothing there
/pci@7c0/pci@0: Device b Nothing there
/pci@7c0/pci@0: Device c Nothing there
/pci@7c0/pci@0: Device d Nothing there
/pci@7c0/pci@0: Device e Nothing there
/pci@7c0/pci@0: Device f Nothing there
Probing I/O buses
 
Netra T5220, No Keyboard
...
 
 
{0} ok

To understand the various devices and their path names as represented in the OpenBoot device tree, refer to TABLE 6-1 for disks and TABLE 6-2 for optional PCI cards.

---

Booting the Solaris Operating System

The Solaris OS is preinstalled on the servers on the disk in slot 0. The Solaris OS is not configured (that is, the sys-unconfig command was run in the factory). If you boot the system from this disk, you will be prompted to configure the Solaris OS for your environment.

1. At the ok prompt, boot from the disk that contains the Solaris OS.

• If you know which disk to boot from, skip this step and perform Step 2.
• If you need to determine which disk to boot from, issue the show-disks command at the ok prompt to see the path to the configured disks, similar to the following:


ok show-disks a) /pci@7c0/pci@0/pci@2/pci@0,2/LSILogic,sas@4/disk q) NO SELECTION Enter Selection, q to quit: q ok

2. Type the boot command at the ok prompt.

Use the value from Step 1 to construct the boot command. You must append the target to the disk path.

In the following example, the system is being booted from disk 0 (zero) on a Sun Netra T5220 server from Oracle. Thus, @0,0 is appended to the disk path.

ok boot /pci@7c0/pci@0/pci@2/pci@0,2/LSILogic,sas@4/disk@0,0 
Boot device: / pci@7c0/pci@0/pci@2/pci@0,2/LSILogic,sas@4/
disk@0,0 
File and args:
Notice: Unimplemented procedure 'encode-unit' in /pci@7c0/pci@0/pci@2/pci@0/LSILogic,sas@4
Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
FCode UFS Reader 1.12 00/07/17 15:48:16.
Loading: /platform/SUNW,Ontario/ufsboot
Loading: /platform/sun4v/ufsboot
SunOS Release 5.10 Version /net/spa/export/spa2/ws/pothier/grlks10-ontario:12/01/2004 64-bit
...
 
DEBUG enabled
misc/forthdebug (159760 bytes) loaded
/platform/sun4v/kernel/drv/sparcv9/px symbol intr_devino_to_sysino multiply defined
...
os-tba FPU not in use
configuring IPv4 interfaces: ipge0.
Hostname: wgs94-181
The system is coming up. Please wait.
NIS domain name is xxx.xxx.xxx.xxx
starting rpc services: rpcbind keyserv ypbind done.
Setting netmask of lo0 to 255.0.0.0
Setting netmask of bge0 to 255.255.255.0
Setting default IPv4 interface for multicast: add net 224.0/4: gateway wgs94-181
syslog service starting.
volume management starting.
Creating new rsa public/private host key pair
Creating new dsa public/private host key pair
The system is ready.
wgs94-181 console login:

  If it is necessary to reset the system, use the shutdown -g0 -i6 -y command.

# shutdown -g0 -i6 -y

It is not necessary to power the system off and on to simply reset the system.

If a simple reset does not clear a system problem, you can power the system off and on with this procedure.

1. Shut down the Solaris OS.

At the Solaris OS prompt, type the shutdown -g0 -i0 -y command and then type h when prompted to halt the Solaris OS and to return to the ok prompt.

# shutdown -g0 -i0 -y
# svc.startd: The system is coming down.  Please wait.
svc.startd: 91 system services are now being stopped.
Jun 12 19:46:57 wgs40-58 syslogd: going down on signal 15
svc.startd: The system is down.
syncing file systems... done
Program terminated
r)eboot, o)k prompt, h)alt? 

2. Switch from the system console prompt to the service processor console prompt by issuing the #. escape sequence.

ok #.
-> 

3. Using the ILOM CLI, type the stop /SYS command to perform a graceful shutdown of the system.

-> stop /SYS 
Are you sure you want to stop /SYS (y/n)? y 
Stopping /SYS 
 
-> 

4. Type the start /SYS command.

-> start /SYS 
Are you sure you want to start /SYS (y/n)? y 
Starting /SYS 
 
-> 

5. Reconnect to the system console with the start /SP/console command.

-> start /SP/console 
Are you sure you want to start /SP/console (y/n)? y 
Serial console started.  To stop, type #. 

The systems displays various messages, followed by the ok prompt.

---

Verifying System Functionality

After powering on the system for the first time, you can use the Sun Validation Test Suite (SunVTS) software to verify the functionality and performance of any installed components, as well as its network connections. Refer to the SunVTS documentation at http://www.oracle.com/technetwork/indexes/documentation/index.html for more information.

^{1 (TableFootnote) The logical device names might appear differently on your system, depending on the number and type of add-on disk controllers installed.}

Sun Netra T5220 Server Installation Guide

E21356-01

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.