Difference between revisions of "Using ILOM on T5120/T5220"

Latest revision as of 04:26, 18 May 2012

All of these are true and correct for T5120/T5220. I'm sure most of this works for other systems that use ILOM 3.0 code!

Default Service Processor (SP) Username/Password

 Username: root
 Password: changeme

Changing the default SP password

 set /SP/users/root password

Starting the system

 start /SYS

Access the console

 start /SP/console

Sending a Break to the OS

So the boot PROM on T2 processor based systems works very differently. As the boot PROM code is shared by the base OS with any LDOM's that may be present. As such, the boot PROM code is loaded into memory on startup of the hardware, or the LDOM, and then dropped. So it's not always running as it is on older systems. So in order to break to the boot PROM you need to do the following:

1. From the SP, send the break:

 set /HOST send_break_action=break

2. From the SP, start the console

 start /SP/console

3. At the console, you will see the following prompt:

 c)ontinue, s)ync, r)eset?

You want to reset, so:

 c)ontinue, s)ync, r)eset? r

4. Type #. to break out of the console and back to the SP.

5. Send the break signal again to force the boot PROM to break and stop at the OK prompt

 #.
 set /HOST send_break_action=break

6. Now start the console again to get to the OK prompt.

 start /SP/console

Seem overly complicated to you? I think so too!! Oh and you need to be quick about it, as the system is rebooting and will continue to do so unless you send that break in then you want it.

Changing the state of the system

The old ILOM/ALOM would allow you to simply power on and power off with the commands 'poweron' and 'poweroff' respectively. Ingenious! In ILOM 3.0 it's a bit more complicated:

To power on:

 start /SYS

To power off:

 stop /SYS

To reset the entire system:

 reset /SYS

How to Create an ALOM CMT Compatibility Shell

This will allow you to use an ALOM like interface for controlling your server. Useful for applying firmware updates, seeing real output when a server won't boot and nostalgia!

1. Log onto the server with username: root. When powered on, the server boots to the ILOM login prompt. The factory default password is changeme.

 SUNSPxxxxxxxxxxxx login: root
 Password:
 Waiting for daemons to initialize...
 Daemons ready
 Oracle Integrated Lights Out Manager
 Version 3.0.0.0
 Copyright (c) 2010, Oracle and/or its affiliates.  All rights reserved.
 Use is subject to license terms.
 Warning: password is set to factory default.

2. Create a user named admin, set the admin account role to Administrator and the CLI mode to alom

 -> create /SP/users/admin
 Creating user...
 Enter new password: ********
 Enter new password again: ********
 Created /SP/users/admin
 
 -> set /SP/users/admin role=Administrator
 Set 'role' to 'Administrator'
 -> set /SP/users/admin cli_mode=alom
 Set 'cli_mode' to 'alom'
 

Note - The asterisks in the example will not appear when you enter your password.

You could also combine the create and set commands on a single line:

 -> create /SP/users/admin role=Administrator cli_mode=alom
 Creating user...
 Enter new password: ********
 Enter new password again: ********
 Created /SP/users/admin

3. Log off the root account after you have finished creating the admin account.

 -> exit

4. Log into the ALOM CLI shell (indicated by the -> prompt) from the ILOM login prompt.

 SUNSPxxxxxxxxxxxx login: admin
 Password:
 Waiting for daemons to initialize...
 Daemons ready
 Oracle Integrated Lights Out Manager
 Version 3.0.0.0
 Copyright (c) 2010, Oracle and/or its affiliates.  All rights reserved.
 Use is subject to license terms.
 
 sc>

Give SP a static IP

1. Set the SP to use a static IP

  set /SP/network pendingipdiscovery=static 

2. Set your preferred IP

  set /SP/network pendingipaddress=192.168.1.15

3. Set the default gateway

  set /SP/network pendingipgateway=192.168.1.1 

4. Set the subnet mask

  set /SP/network pendingipnetmask=255.255.255.0 

5. Check that it's ready

  show /SP/network 

which will look something like this:

  -> show /SP/network
  
   /SP/network
      Targets:
          test
  
      Properties:
          commitpending = (Cannot show property)
          dhcp_server_ip = none
          ipaddress = 0.0.0.0
          ipdiscovery = dhcp
          ipgateway = 0.0.0.0
          ipnetmask = 0.0.0.0
          macaddress = 00:21:28:XX:XX:XX
          pendingipaddress = 192.168.1.15
          pendingipdiscovery = static
          pendingipgateway = 192.168.1.1
          pendingipnetmask = 255.255.255.0
          state = enabled
  
      Commands:
          cd
          set
          show

6. Apply the change

  set /SP/network commitpending=true 

7. Check that it worked

  show /SP/network 

which will look something like this:

  -> show /SP/network
  
   /SP/network
      Targets:
          test
  
      Properties:
          commitpending = (Cannot show property)
          dhcp_server_ip = none
          ipaddress = 192.168.1.15
          ipdiscovery = static
          ipgateway = 192.168.1.1
          ipnetmask = 255.255.255.0
          macaddress = 00:21:28:XX:XX:XX
          pendingipaddress = 192.168.1.15
          pendingipdiscovery = static
          pendingipgateway = 192.168.1.1
          pendingipnetmask = 255.255.255.0
          state = enabled
  
      Commands:
          cd
          set
          show