For the first time I configured dhcp client on Solaris.
Example: Interface name: nxge0
1. Remove existing manual configuration by deleting /etc/hostname.nxge0
2. touch /etc/dhcp.nxge0 (it’s empty file)
3. ifconfig nxge0 dhcp start
4. ifconfig nxge0 dhcp status (this will give lease details)
Frequently used commands in OBP:
#1 ok setenv auto-boot? false
to verify use “ok printenv auto-boot?“
When you need trouble shoot solaris server at OK prompt, you have to disable the auto boot feature
#2 ok banner
Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 333MHz), No Keyboard
OpenBoot 3.15, 128 MB memory installed, Serial #number.
Ethernet address number, Host ID: number.
You can find OBP version, Server model, Serial number, Host ID and Ether net mac address from Banner command
Note: Mac address displayed is Port 0 (zero) of on board network card. For Example I have quad port onboard NIC card and two Quad Port PCI-e Cards. Out of total 12 mac address, one displayed here is from onboard zero port. This clarity will help whe you are troubleshooting “ok boot net – install” trouble shoot errors.
#3 ok setenv local-mac-address? true
When you configure IPMP you have to set local-mac-address? to True, then only each NIC card use it’s Mac address which is very important for IPMP.
#4 set device alias and enable nvram
ok nvalias <alias> <device-path>
ok nvunalias <alias> <device-path>
Example:
{0} ok nvalias bootdisk /pci@400/pci@1/pci@0/pci@4/scsi@0/disk@w5xxxc500xxxxxxfd5,0:a
{0} ok setenv use-nvramrc? true
{0} ok setenv boot-device bootdisk
These two are required to set alis names to the disk and network devices. As we have many disks in system, this will help to set alias as bootdisk and mirrordisk to identify the boot disk and mirror disk from OK promt among many disk devices.
Note: After using nvunalias command if you refer devalias command it will still show the alias details, when you run reset-all, then it will not show them.
You can do this from OS using eeprom
eeprom nvramrc=”devalias bootdisk /pci@400/pci@1/pci@0/pci@4/scsi@0/disk@wx000cx00xxxxxfd5,0:a devalias mirrordisk /pci@400/pci@2/pci@0/pci@4/scsi@0/disk@wx000cx00xxxxxxxx,0:a“
eeprom use-nvramrc?=true
#5 Verify network interface connectivity and check MAC address of the NIC ports
{2} ok watch-net-all
/pci@1f,700000/network@1
/pci@1f,700000/network@1: link down
/pci@1d,700000/pci@2/pci@4/network@2
/pci@1d,700000/pci@2/pci@4/network@2: 100 Mbps half duplex link up
Watch ethernet packets
‘.’ is a good packet and ‘X’ is a bad packet
Press any key to stop
using network device alias
ok> cd /net1
ok> .properties
Using Network device physical path
or cd /pci@1d,700000/pci@2/pci@4/network@2
ok> .properties
#6 ok show-devs
will list all the devices
#7 ok setenv diag-switch? true
ok setenv diag-level max (available diag levels are: net/max/min/menus)
Other test options available at OK prompt are
probe-scsi (use show-devs for PCI devices)
probe-scsi-all (use show-devs for PCI devices)
test net (tests primary network controller)
test-all (tests all devices)
watch-net and watch-net-all (for all interface)
#8 boot options
ok boot (boots with default device mentioned in “boot-device”)
ok boot -s (boot to single user mode for maintenance)
ok boot net – install (used to boot through jumpstart boot servers for building OS through jumpstart)
ok boot net:speed=100,duplex=full,dhcp – install (Jumpstart boot through dhcp with preferred network settings instead of rarp , this removes the limitation of both boot servers and client in the same LAN)
ok boot -a (interactive boot, used to supply alternate boot files like /etc/system if default one is corrupted)
ok boot -r (reconfigure reboot, new device added to the sytem, this will create device files in OS)
ok boot disk2 kernel/sparcv9/unix -asv ( Boot single user, interactive, 64-bit and from disk device disk2. I never used this)
ok boot -F failsafe (I beleive it’s only for solaris 10 and above with SMF implementation this maintenance mode option available and saved Sys Admins from searching for boot CD or troubleshooting jumpstart to boot through net to go to maintenance mode for resetting root password or doing fsck on boot file systems)
boot -v or boot -m verbose (to see more messages on boot)
ok boot -m milestone=none (This command instructs the svc.startd daemon to temporarily disable all services and start sulogin on the console)
Reference web links about OBP:
http://it.toolbox.com/wiki/index.php/Open_Boot_PROM_-_OK_Prompt
http://docs.oracle.com/cd/E19963-01/html/821-1451/gkkvd.html
http://irtfweb.ifa.hawaii.edu/~spex/computers/techdocs/1201-hilodog/SunOBP_Quick_Ref.pdf
http://www.adminschoice.com/booting-problems-in-solaris
http://www.shrubbery.net/~heas/sun-feh-2_1/General/OBP.html
{0} ok boot -F failsafe
Boot device: /pci@400/pci@1/pci@0/pci@4/scsi@0/disk@wx000cx00xxxxxfdx,0:a File and args: -F failsafe
SunOS Release 5.10 Version Generic_147440-01 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
Configuring devices.
Searching for installed OS instances…
ROOT/zfsroot was found on root.
Do you wish to have it mounted read-write on /a? [y,n,?] y
mounting root on /a
An out of sync boot archive was detected on root.
The boot archive is a cache of files used during boot and
should be kept in sync to ensure proper system operation.
Do you wish to automatically update this boot archive? [y,n,?] y
Updating boot archive on root.
The boot archive on root was updated successfully.
# cd /a
# cp etc/shadow etc/shadow.21dec2012
# vi etc/shadow
root::6445::::::
:wq!
# init 6
I have sparc T4-1 with onboard quad port and two PCIe quad port network cards installed on slot 0(zero) and slot 1(one)
Slot 0(zero) PCI-E network card:
Slot 0- Port0 – mapped to nxge0
Slot 0- Port1 – mapped to nxge1
Slot 0- Port2 – mapped to nxge2
Slot 0- Port3 – mapped to nxge3
Slot 1 (one) PCI-E network card:
Slot 1- Port0 – mapped to nxge4
Slot 1- Port1 – mapped to nxge5
Slot 1- Port2 – mapped to nxge6
Slot 1- Port3 – mapped to nxge7
Onboard quad port card:
Onboard – Port0 – mapped to igb0
Onboard- Port1 – mapped to igb1
Onboard- Port2 – mapped to igb2
Onboard- Port3 – mapped to igb3
Click on igb and nxge for more details
igb network card: Intel 82575 1Gb PCI Express NIC Driver
nxge: Sun 10/1 Gigabit Ethernet network driver
I have installed Oracle VM Server for Sparc 2.2 on Sparc T4-1 server
Pre requisites:
supported Platforms: http://docs.oracle.com/cd/E35434_01/html/E23810/gentextid-296.html#LDSRNldomssupportedplatforms
OS: Solaris 10 8/11 or Solaris 11 SRU 7 (Support Repository Update)
http://docs.oracle.com/cd/E35434_01/html/E23810/gentextid-296.html#LDSRNldomsrequiredsoftwarepatches
For Sparc T4-1 required firmware patch: 148822-01
148822-01 Synopsis: Obsoleted by: 148822-02 FIRMWARE: SPARC T4-1 – Sun System Firmware 8.2.0.a
Date: May/22/2012
We have uptodate firmware i.e.: 148822-04
Synopsis: Obsoleted by: 148822-04 FIRMWARE: SPARC T4-1 – Sun System Firmware 8.2.1.b
Date: Aug/31/2012
Installation:
Welcome to the Oracle VM Server for SPARC installer.
You are about to install the LDoms Manager package, SUNWldm, that will enable
you to create, destroy and control other domains on your system. You will
also be given the option of running the Oracle VM Server for SPARC Configuration
Assistant (ldmconfig) to setup the control domain and create guest domains.
If the Solaris Security Toolkit (SST) is installed, you will be prompted to
optionally harden your control domain.
Installing LDoms packages.
pkgadd -n -d “./Product” -a pkg_admin SUNWldm.v
Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
Installation of <SUNWldm> was successful.
pkgadd -n -d “./Product” -a pkg_admin SUNWldmp2v
Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
Installation of <SUNWldmp2v> was successful.
Oracle VM Server for SPARC Configuration
Once installed, you may configure your system for a basic LDoms
deployment. If you select “y” for the following question, the Oracle
VM Server for SPARC Configuration Assistant (tty) will be launched
following a successful installation of the packages.
(You may launch the Configuration Assistant at a later time with the
command: /usr/sbin/ldmconfig, or use the GUI Configuration Assistant
which is bundled in the Oracle VM Server for SPARC zip file – see
README.GUI for more details)
Select an option for configuration:
y) Yes, launch the Configuration Assistant after install
n) No thanks, I will configure the system manually later
Enter y or n [y]:n
Verify installed packages:
bash-3.2# pkginfo -l SUNWldmp2v
PKGINST: SUNWldmp2v
NAME: LDoms P2V tool
CATEGORY: application
ARCH: sparc
VERSION: 2.2.0.0,REV=2012.04.19.14.10
BASEDIR: /
VENDOR: Oracle Corporation
DESC: Oracle VM Server for SPARC Physical-to-Virtual (P2V) Migration Tool
PSTAMP: scapen-on10-020120419141017
INSTDATE: Dec 21 2012 15:20
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 19 installed pathnames
6 shared pathnames
12 directories
3 executables
264 blocks used (approx)
bash-3.2# pkginfo -l SUNWldm
PKGINST: SUNWldm
NAME: LDoms Manager software
CATEGORY: application
ARCH: sparc.sun4v
VERSION: 2.2.0.0,REV=2012.04.19.14.10
BASEDIR: /
VENDOR: Oracle Corporation
DESC: Oracle VM Server for SPARC – Virtualization for SPARC T-Series
PSTAMP: scapen-on10-020120419141012
INSTDATE: Dec 21 2012 15:20
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 79 installed pathnames
18 shared pathnames
23 directories
22 executables
5851 blocks used (approx)
Verify the ldms
bash-3.2# svcs|grep ldmd
online 15:20:55 svc:/ldoms/ldmd:default
bash-3.2# ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-c– UART 64 32256M 0.2% 1d 4h 38m
Save and Restore ldm configuration:
bash-3.2# tar -cvpf /var/tmp/autosave.tar var/opt/SUNWldm/autosave-*
a var/opt/SUNWldm/autosave-_Default_SP_Config/ 0K
a var/opt/SUNWldm/autosave-_Default_SP_Config/md-primary.bin 61K
a var/opt/SUNWldm/autosave-_Default_SP_Config/hv-md.bin 22K
a var/opt/SUNWldm/autosave-_Default_SP_Config/timestamp 1K
a var/opt/SUNWldm/autosave-_Default_SP_Config/sp-pri.bin 88K
a var/opt/SUNWldm/autosave-_Default_SP_Config/sp-timestamp 1K
to restore
cd /
tar -xvpf /var/tmp/autosave.tar
Saving and Restorig LDOM constraint Database
backup and restore the xml file: /var/opt/SUNWldm/ldom-db.xml
create default services after installing the LDOM manager:
3 defaults services need to be created on primary ldom:
virtual control concentrator service (vcc) service for use by the virtual network terminal server
daemon (vntsd) and as a concentrator for all logical domain consoles.
virtual disk server (vds) to allowimporting virtual disks into a logical domain
virtual switch service (vsw) to enable networking between virtual network (vnet)
devices in logical domains
VCC # ldm add-vcc port-range=5000-5100 vcc_primary primary
VDS # ldm add-vds vds0_primary primary
VSW # ldm add-vsw net-dev=nxge0 vsw0_primary primary
MAC address to vsw can be manually set using below command: only on Solaris 10:
primary# ldm add-vsw mac-addr=2:04:4f:fb:9f:0d net-dev=nxge0 primary-vsw0 primary
list services:
#ldm list-services primary
VCC
NAME LDOM PORT-RANGE
vcc_primary primary 5000-5100
VSW
NAME LDOM MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
vsw0_primary primary 00:14:4f:fb:af:0d nxge0 0 switch@0 1 1 1500 on
VDS
NAME LDOM VOLUME OPTIONS MPGROUP DEVICE
vds0_primary primary
bash-3.2# ldm set-vcpu 8 primary
bash-3.2# ldm list-constraints primary
bash-3.2# ldm start-reconf primary
Initiating a delayed reconfiguration operation on the primary domain.
All configuration changes for other domains are disabled until the primary
domain reboots, at which time the new configuration for the primary domain
will also take effect.
bash-3.2# ldm set-memory 1G primary
——————————————————————————
Notice: The primary domain is in the process of a delayed reconfiguration.
Any changes made to the primary domain will only take effect after it reboots.
——————————————————————————
bash-3.2#
bash-3.2# ldm add-config initial
bash-3.2# ldm list-config
factory-default
initial [current]
bash-3.2#sync;sync
bash-3.2# /usr/sbin/shutdown -y -g0 -i6
How to stop all domains:
1. power down all domains OS to OK prompt
2. primary# ldm stop-domain -a
3. primary# ldm unbind-domain ldom
To remove all guest domains, run above 3 steps and below one step
4. ldm remove-domain -a
How to upgrade LODM Manager:
1. svcadm disable ldmd
2. pkgrm SUNWldm
3. Instll the new package (copied to /var/tmp)
cd /var/tmp;pkgadd -Gd. SUNWldm.v
4. ldm list (verify)
How to disable logical domain manager and remove the package?
1. svcadm disable ldmd
2. pkgrm SUNWldm; pkgrm SUNWldmp2v
Documents:
Oracle®VMServer for SPARC 2.2 Administration Guide : E23807.pdf
http://dbhk.wordpress.com/category/ldom/
http://gdesaboyina.wordpress.com/2012/08/03/parsing-ldom-db-xml/
http://docs.oracle.com/cd/E35434_01/pdf/E23807.pdf
http://unixsecure.net/ldom-%E2%80%93-ldm-configuration-lost-when-control-domain-reboots/
This example is just to demonstrate how to save and restore guest domain.
Backup the xml file
#ldm list-constraints -x test-ldg1 > /var/tmp/test-ldg1.xml
bring down the guest domain OS -> stop the guest domain -> unbind the guest domain
# ldm list test-ldg1
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
test-ldg1 inactive —— 16 8G
#ldm destroy test-ldg1
#ldm list (will not show test-ldg1 guest domain)
Impot the guest domain using backu xml file /var/tmp/test-ldg1.xml
#ldm add-domain -i /var/tmp/test-ldg1.xml
Verify the domain details
# ldm list test-ldg1
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
test-ldg1 inactive —— 16 8G
bind the guest domain -> start the domain -> start the OS on guest domain
#ldm add-domain -i /var/tmp/test-ldg1.xml
Status is inactive
test-ldg1 inactive —— 16 8G
#ldm bind test-ldg1
Status is bound
test-ldg1 bound —— 5000 16 8G
#ldm start test-ldg1
LDom test-ldg1 started
status is Active
test-ldg1 active -t—- 5000 16 8G 3.8% 2s
Disclaimer: I test following procedure to rename the guest domain. It worked for me, but it’s may not be the right procedure. Do not try on your prod environment
Rename the Guest domain:
==========================
Bring down the guest domain OS to OK prompt
bash-3.2# ldm list old-ldg1
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
old-ldg1 active -t—- 5000 16 8G 6.2% 23h 17m
#ldm stop-domain old-ldg1
LDom old-ldg1 stopped
bash-3.2# ldm list old-ldg1
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
old-ldg1 bound —— 5000 16 8G
Then run unbind command, it will change to inactive state
bash-3.2# ldm unbind old-ldg1
bash-3.2# ldm list old-ldg1
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
old-ldg1 inactive —— 16 8G
Save the guest domain configuration to a xml
bash-3.2# ldm list-constraints -x old-ldg1 > /var/tmp/old-ldg1.xml
Create copy of the xmls
cp -p /var/tmp/old-ldg1.xml /var/tmp/new-ldg1.xml
bash-3.2# grep -i sngcgpsqap31 /var/tmp/old-ldg1.xml
<Content xsi:type=”ovf:VirtualSystem_Type” ovf:id=”old-ldg1″>
<gprop:GenericProperty key=”vol_name”>sngcgpsqap31_sys</gprop:GenericProperty>
<gprop:GenericProperty key=”vol_name”>sngcgpsqap31_sys</gprop:GenericProperty>
<gprop:GenericProperty key=”block_dev”>/dev/zvol/dsk/root/vdsk_sngcgpsqap31_sys</gprop:GenericProperty>
bash-3.2# cp /var/tmp/old-ldg1.xml /var/tmp/new-ldg1.xml
psqap31.xmlerl -pi -e ‘s/old-ldg1/new-ldg1/g’ /var/tmp/ldg-sngcg
bash-3.2# grep -i sngcgpsqap31 /var/tmp/new-ldg1.xml
<Content xsi:type=”ovf:VirtualSystem_Type” ovf:id=”new-ldg1″>
<gprop:GenericProperty key=”vol_name”>sngcgpsqap31_sys</gprop:GenericProperty>
<gprop:GenericProperty key=”vol_name”>sngcgpsqap31_sys</gprop:GenericProperty>
<gprop:GenericProperty key=”block_dev”>/dev/zvol/dsk/root/vdsk_sngcgpsqap31_sys</gprop:GenericProperty>
bash-3.2# ldm add-domain -i /var/tmp/new-ldg1.xml
bash-3.2# ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- UART 8 1G 1.1% 1d 3h 24m
new-ldg1 inactive —— 16 8G
bash-3.2# ldm bind new-ldg1
bash-3.2# ldm start new-ldg1
LDom new-ldg1 started
bash-3.2# ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- UART 8 1G 4.8% 1d 3h 25m
new-ldg1 active -t—- 5000 16 8G 3.5% 2s
Verify connecting to new guest domain console:
bash-3.2# telnet localhost 5000
Trying 127.0.0.1…
Connected to localhost.
Escape character is ‘^]’.
Connecting to console “new-ldg1″ in group “new-ldg1″ ….
Press ~? for control options ..
{0} ok
telnet> quit
Connection to localhost closed.
bash-3.2#
Basic requirements for IPMP
Two types of IPMP:
Terminology:
Data Addresses: Conventional address configured to interface.
Test Addresses: used by in.mpathd for probe based failure detection.
IP link: Physical connection to network switch
To configure link based IPMP, we do not required test address. So configure the two interface hostname files
Ex., nxge0 and nxge4
echo “myhost netmask + broadcast + group ipmp0 up” > /etc/hostname.nxge0
echo “group ipmp0 up” > /etc/hostname.nxge4
then restart the network services
svcadm disable network/physical
svcadm enable network/physical
Jan 7 18:26:52 myhost in.mpathd[1501]: No test address configured on interface nxge4; disabling ed failure detection on it
Jan 7 18:26:52 myhost in.mpathd[1501]: No test address configured on interface nxge0; disabling probe-based failure on it
Then ifconfig output will look like below. Notice that nxge4 do not have IP configured.
nxge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.0.100netmask ffffff80 broadcast 165.40.63.127
groupname ipmp0
ether 0:xx:xx:xx:xx:xx
nxge4: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
groupname ipmp0
ether 0:xx:xx:xx:xx:xx
Then verify the failover and back with ‘if_mpadm” command
root@myhost # if_mpadm -d nxge0
Jan 7 18:28:29 myhost in.mpathd[1501]: Successfully failed over from NIC nxge0 to NIC nxge4
root@myhost # if_mpadm -r nxge0
Jan 7 18:28:43 myhost in.mpathd[1501]: Successfully failed back to NIC nxge0
While testing ran a ping test
H:\>ping 192.168.0.100-t
Pinging 192.168.0.100with 32 bytes of data:
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=39ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Request timed out. –here tested failover to nxge4
Reply from 192.168.0.100: bytes=32 time=39ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Request timed out.—here tested failback to nxge0
Reply from 192.168.0.100: bytes=32 time=39ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Reply from 192.168.0.100: bytes=32 time=38ms TTL=244
Ping statistics for 192.168.0.100:
Packets: Sent = 25, Received = 23, Lost = 2 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 39ms, Average = 38ms
Control-C
Note: For trouble shooting you can test network connectivity from OK prompt with watch-net command
/pci@400/pci@2/pci@0/pci@6/network@0
1000 Mbps full duplex Link up
Looking for Ethernet Packets.
‘.’ is a Good Packet. ‘X’ is a Bad Packet.
Type any key to stop.
………………………………………
/pci@400/pci@1/pci@0/pci@8/network@0
1000 Mbps link up
Looking for Ethernet Packets.
‘.’ is a Good Packet.
Type any key to stop.
…………………………………………
Reference
http://docs.oracle.com/cd/E23823_01/pdf/816-4554.pdf
https://blogs.oracle.com/stw/entry/using_ipmp_with_link_based
First let’s start with how to access ILOM:
1. if NetMgmt port configured, using ssh you can login to the ILOM
2.If you configure SerialMgmt Port, then when you connect to serial port, you will access ILOM
3. if you connect to console thorught netmgmt or serial mgmt ports and you connect Operating System. Use #. (Hash symbol with . (dot)) which will take you to the ILOM.
From ILOM to go back to the Host Operating System then start the console service ->start /SP/console
-> start /SP/console ==>ILOM CLI prompt
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type #.
bash-3.2# –> OS prompt
Serial console stopped.
-> ==>ILOM CLI prompt
Notes on ILOM CLI follow hierarchial Architecture
ILOM Target types:
/SP – configuring ILOM service processor (SP)
/SYS – inventory/environmental and hardware management
/HOST – monitoring and managing host operating system.
Blade Platforms:
/CMM – Blade platform this replace SP, used to configure ILOM Chassis Monitoring Module
/CH – Blade platform this replace /SYS and provides inventory, environmentals and hardware management
ILOM CLI commands:
cd
create
delete
dump
exit
help
load
reset
set
show
start
stop
version
ILOM CLI Syntax:
command [options] [target] [properties
ex.,: set /SP/services/https port=80 servicestate=enabled
User Management ILOM CLI:
Roles in CLI: Admin|Operator (a), User Management (u), Console (c), Reset and Host control (r) and Read Only (o)
1. Add a local user
create /SP/users/user1 password=password role=a|u|c|r|o|s
2. Delete a local user
delete /SP/users/user1
3. Change a local user's properties
set /SP/users/user1 role=operator
4. Display information about all local users
show -display [targets|properties|all ] -level all /SP/users
5. Display information aboutLDAP settings
show /SP/clients/ldap
6. Change LDAP settings
set /SP/clients/ldap binddn=proxyuser bindpw=proxyuserpassword defaultrole=a|u|c|r|o|s address=ipaddress
Set ILOM clock to sync with NTP server
set /SP/clients/ntp/server/1 address=ntpIPAddress
To configure IP on NetMgmt port set values to the /SP/network properties
Properties:
commitpending = (Cannot show property)
dhcp_server_ip = (none)
ipaddress = (none)
ipdiscovery = (none)
ipgateway = (none)
ipnetmask = (none)
macaddress = xx:xxx:xx:xx:xx:xx
managementport = /SYS/MB/SP/NETMGMT
outofbandmacaddress = xx:xx:xx:xx:xx:xx
pendingipaddress = (none) –>IPV4 address
pendingipdiscovery = (none)
pendingipgateway = (none) –> Gateway
pendingipnetmask = (none) –> Netmask
pendingmanagementport = /SYS/MB/SP/NETMGMT
sidebandmacaddress = xx:xx:xx:xx:xx:xx
state = disabled
you can configure above values using set command
set /SP/network pendingipaddress=192.168.1.10
set /SP/network pendingipnetmask=255.255.255.0
set /SP/network pendingipgateway=192.168.1.1
Configuring SNMP and email alert:
set /SP/alertmgmt/rules/1…15 type=snmtrap snmp_version=3 comunity_or_username=username destination=ipaddress level=down|critical|major|minor
set /SP/alertmgmt/rules/1…15 type=email destination=somemail@abc.com level=down|critical|major|minor
To enable web access to ILOM, can http
set /SP/services/http port=80 secureredirect=enabled|disabled servicestate=enabled|disabled
set /SP/services/https port=xxx servicestate=enabled|disabled
HOST system commands (*warning: if your host is up and running, HOST commands can cause outage)
To start the host system ->start /SYS
To stop the host system -> stop /SYS
Force shutdown (required when host hung)->stop -f /SYS
Reset the host system (required when host hung) ->reset /SYS
start a sessions to connect to host console -> /SP/console
stop the console session -> /SP/console
Filtering output options:
Users with admin roles -> show /SP/users -level all role==”a*”
SNMP trap alerts ->show /SP/alertmgmt -level all type==”snmptrap”
List services which are disabled -> show /SP/services -level all servicestate==disabled
List memory moduels with some part number -> show /SYS -level all type==”DIMM” fru_part_number==07014642
list all hard disks -> show /SYS -level all type==”Hard Disk”
How to backup the ILOM configuration
cd /SP/config
set passphrase=passphrase
set dump_uri=transfer_method://username:password@ipaddress_or_hostname/directorypath/filename
set dump_uri=scp://adminuser:userpswd@x.x.x.x/Backup/Lab9/SP-backup.config
How to Restore the ILOM configuration
Note: you have to login ILOM with user which has Admin,User Management, Console, Reset, Host control and Read only (a,u,c,r,o) roles.
cd /SP/config
set passphrase=passphrase
set load_uri=transfer_method://username:password@ipaddress_or_hostname/directorypath/filename
How to update ILOM Firmware
Pre requisite: Shutdown the host running on the hardware whose ILOM firmware you are upgrading
1.Login to ILOM CLI with user which has Admin role
2. ->version
3. Download the zip file packge and copy to TFTP server that is accessible from network
4.load -source <supported_protocol>://<server ip>/<path_to_firmware_image/<filename.xxx>
Do you want to preserve the configuration (y/n)?y
Once firmware loades it automaticall reboots to complete the firmware update
ILOM CLI is based on DMTF CLP (Distributed Management Task Force specification Server Management Command-Line Specification, Version 11.0a.8 Draft
Reference: http://www.fujitsu.com/downloads/SPARCE/manuals/sparc-t5e/ilom3.0-cli-en-01.pdf
disclaimer: Please refer vendor provided instructions and follow carefully.
Step: 1
Go to this Oracle site and find the suitable firmware level for your server or refer your internal engineering documents to know upgrade level.
http://www.oracle.com/technetwork/systems/patches/firmware/release-history-jsp-138416.html
I need upgrade to SysFW 8.2.2.c, this comes with Oracle Patch “148822-05”
Step2: Login to oracle site with valid support id and download the patch. (Most of the enterprise organizations have engineering team, who test these patches and upload to internal repositories)
Step3: copy the “148822-05.zip” to the servers, where you need upgrade the firmware and unzip it.
Step4: Pre tasks
cd /tmp/patch/148822-05
./sysfwdownload [image].pkg (in my case the image name “Sun_System_Firmware-8_2_2_c-SPARC_T4-1.pkg
(if you observer image file name has all information like this firmware is for Sun Sparc hardware,it’s version is 8.2.2.c and it’s for Sparc T4-1 model. This is first level of defense to avoid loading wrong firmware image)
When downloading it will show progress in format “….(10%)….” it ends with download completed successfully
shutdown -i0 -g0 -y
OK> type #. to go to ILOM mode in console
show /HOST/boodmode (note config parameter value for LDOM servers)
show /HOST/ will display the current versions of Hypervisor, OpenBoot, Post and sysfw_version
(sysfw_version is the one we mentioned above)
Verify downloaded image is correct or not with “show /SP/firmware/localimage” and verify upload date and Version. (Here second level of defense comes, if valid image is not uploaded instead of version it will show invalid image).
stop the system to poweroff competely “stop /SYS”
Verify the key_switch state “show /SYS keyswitch_state” it should be in normal state. If it’s in locked state change to normal
“set /SYS keyswitch_state=Normal” Check if value set properly.
After completing all pre checks now we are ready to upgrade the firmware
load -source /SP/firmware/localimage
This will show progress in … and once it complete, it will reboot the ILOM.
Once it’s completed, change the bootmode “set /HOST/bootmode=”config-name”” (This is important for the LDOM servers)
start the system “start /SYS”
go to console to see the server boot progress
console /HOST/console
disclaimer: Please refer vendor provided instructions and follow carefully.
Step: 1
Go to this Oracle site and find the suitable firmware level for your server or refer your internal engineering documents to know upgrade level.
http://www.oracle.com/technetwork/systems/patches/firmware/release-history-jsp-138416.html
I need upgrade to SysFW 8.2.2.c, this comes with Oracle Patch “148822-05”
Step2: Login to oracle site with valid support id and download the patch. (Most of the enterprise organizations have engineering team, who test these patches and upload to internal repositories)
Step3: copy the “148822-05.zip” to the servers, where you need upgrade the firmware and unzip it.
Step4: Pre tasks
cd /tmp/patch/148822-05
./sysfwdownload [image].pkg (in my case the image name “Sun_System_Firmware-8_2_2_c-SPARC_T4-1.pkg
(if you observer image file name has all information like this firmware is for Sun Sparc hardware,it’s version is 8.2.2.c and it’s for Sparc T4-1 model. This is first level of defense to avoid loading wrong firmware image)
When downloading it will show progress in format “….(10%)….” it ends with download completed successfully
shutdown -i0 -g0 -y
OK> type #. to go to ILOM mode in console
show /HOST/boodmode (note config parameter value for LDOM servers)
show /HOST/ will display the current versions of Hypervisor, OpenBoot, Post and sysfw_version
(sysfw_version is the one we mentioned above)
Verify downloaded image is correct or not with “show /SP/firmware/localimage” and verify upload date and Version. (Here second level of defense comes, if valid image is not uploaded instead of version it will show invalid image).
stop the system to poweroff competely “stop /SYS”
Verify the key_switch state “show /SYS keyswitch_state” it should be in normal state. If it’s in locked state change to normal
“set /SYS keyswitch_state=Normal” Check if value set properly.
After completing all pre checks now we are ready to upgrade the firmware
load -source /SP/firmware/localimage
This will show progress in … and once it complete, it will reboot the ILOM.
Once it’s completed, change the bootmode “set /HOST/bootmode=”config-name”” (This is important for the LDOM servers)
start the system “start /SYS”
go to console to see the server boot progress
console /HOST/console
more…
disclaimer: Please refer vendor provided instructions and follow carefully.
Step: 1
Go to this Oracle site and find the suitable firmware level for your server or refer your internal engineering documents to know upgrade level.
http://www.oracle.com/technetwork/systems/patches/firmware/release-history-jsp-138416.html
I need upgrade to SysFW 8.2.2.c, this comes with Oracle Patch “148822-05”
Step2: Login to oracle site with valid support id and download the patch. (Most of the enterprise organizations have engineering team, who test these patches and upload to internal repositories)
Step3: copy the “148822-05.zip” to the servers, where you need upgrade the firmware and unzip it.
Step4: Pre tasks
cd /tmp/patch/148822-05
./sysfwdownload [image].pkg (in my case the image name “Sun_System_Firmware-8_2_2_c-SPARC_T4-1.pkg
(if you observer image file name has all information like this firmware is for Sun Sparc hardware,it’s version is 8.2.2.c and it’s for Sparc T4-1 model. This is first level of defense to avoid loading wrong firmware image)
When downloading it will show progress in format “….(10%)….” it ends with download completed successfully
shutdown -i0 -g0 -y
OK> type #. to go to ILOM mode in console
show /HOST/boodmode (note config parameter value for LDOM servers)
show /HOST/ will display the current versions of Hypervisor, OpenBoot, Post and sysfw_version
(sysfw_version is the one we mentioned above)
Verify downloaded image is correct or not with “show /SP/firmware/localimage” and verify upload date and Version. (Here second level of defense comes, if valid image is not uploaded instead of version it will show invalid image).
stop the system to poweroff competely “stop /SYS”
Verify the key_switch state “show /SYS keyswitch_state” it should be in normal state. If it’s in locked state change to normal
“set /SYS keyswitch_state=Normal” Check if value set properly.
After completing all pre checks now we are ready to upgrade the firmware
load -source /SP/firmware/localimage
This will show progress in … and once it complete, it will reboot the ILOM.
Once it’s completed, change the bootmode “set /HOST/bootmode=”config-name”” (This is important for the LDOM servers)
start the system “start /SYS”
go to console to see the server boot progress
console /HOST/console
more…
