Posts Tagged ‘SPARC TSERIES SERVER’

ISSUE WITH UPLOADING FIRMWARE TO THE SERVICE PROCESSOR(Sysfwdownload: Download Failure – Status = 2)

November 27th, 2021, posted in Solaris
Share

ISSUE WITH UPLOADING FIRMWARE TO THE SERVICE PROCESSOR(Sysfwdownload: Download Failure – Status = 2)

 

Tried to load a firmware package from solaris 10 to the Service Processor on a T5240 machine and it failed with status = 2. Most of the time the issue will be due to the service processor being slow, having too many stale connections. There might be few other things which contributes to the issue. Check the solutions below, if this is not the issue you are seeing then you will have to contact oracle support with the snapshot of ilom, server patch level and the commands you are running.

 

ISSUE:
# pwd
/var/tmp/147310-08

ls -ltr
total 31406

-r–r–r– 1 root root 183 Sep 10 2012 LEGAL_LICENSE.TXT
-rwxr-xr-x 1 root root 8196 Jan 21 2013 sysfwdownload.README
-rwxr-xr-x 1 root root 21308 Jan 21 2013 sysfwdownload
-rwxr-xr-x 1 root root 184 Jan 21 2013 license.txt
-rwxr-xr-x 1 root root 11821 Jan 21 2013 Install.info
-rwxr-xr-x 1 root root 72 Jan 21 2013 copyright
-rwxr-xr-x 1 root root 15990784 Jan 21 2013 Sun_System_Firmware-7_4_5-SPARC_Enterprise_T5140+T5240.pkg
-rwxr-xr-x 1 root root 1291 Jan 21 2013 SPARC_Enterprise_T5140+T5240_metadata.xml
-rw-r–r– 1 root root 12781 Feb 10 2013 README.147310-08
-rw-r–r– 1 root root 19426 Feb 10 2013 147310-08.html

./sysfwdownload Sun_System_Firmware-7_4_5-SPARC_Enterprise_T5140+T5240.pkg
sysfwdownload: download failure – status = 2


SOLUTION 1:
Login to the ILOM/SC and reset the service processor.
sc>resetsc
Are you sure you want to reset the SC (y/n)? y
Performing reset on the SC
Once the service processor is up, now try to load the firmware from solaris operating system to the service processor.
#cd /var/tmp/147310-08
./sysfwdownload Sun_System_Firmware-7_4_5-SPARC_Enterprise_T5140+T5240.pkg
If resetting service processor didn’t help then see solution 2 is applicable for you.


SOLUTION 2:
You have to login to the ilom using “sunservice” account and your ilom user password. If the SP is running a 7.1.x based FW release (ILOM 2.0), the sunservice account is present by default and you can login directly (there is no need for getting an escalation mode key)
After you login to the ilom with the “sunservice” account, check the output of df -h and see if /coredump file system is filled up. If its filled up then this might be your issue.
Login: sunservice
Password: <enter your regular ilom user password here>

Copyright 2007 Sun Microsystem, Inc. All rights reserved.
WARNING: The “sunservice” account is provided solely to allow
Sun Services to perform diagnosis and recovery tasks. Customer use of
the “sunservice” account may interfere with the correct operation of
ILOM and is not supported other than to perform recovery procedures as
documented by Sun Microsystems. Normal ILOM operations should always be
performed using the root account. Further usage of the “sunservice”
account implies your agreement with these terms.
[(flash)root@myilom:~]# df -h

Filesystem                Size      Used Available Use% Mounted on
/dev/mtdblock4            9.7M      9.7M         0 100% /
sshi                     1.0M    308.0k    716.0k  30% /var
sshimi                   1.0M    372.0k    652.0k  36% /var/log
tmpfs                    62.3M         0     62.3M   0% /dev/shm
/dev/tffsa1              31.0M     29.1M    258.0k  99% /store
/dev/loop0               23.2M      4.9M     17.1M  22% /persist
/dev/loop1                3.9M      1.1M      2.5M  31% /conf
/dev/tffsa3              53.0M     53.0M         0 100% /coredump

cd to the coredump directory and remove the files with *core*. Do Not remove any other files which doesn’t contain *core* in the file name.
After removal:
[(flash)root@myilom:/coredump]# df -h

Filesystem                Size      Used Available Use% Mounted on
/dev/mtdblock4            9.7M      9.7M         0 100% /
sshi                     1.0M    308.0k    716.0k  30% /var
sshimi                   1.0M    384.0k    640.0k  38% /var/log
tmpfs                    62.3M         0     62.3M   0% /dev/shm
/dev/tffsa1              31.0M     29.1M    258.0k  99% /store
/dev/loop0               23.2M      4.9M     17.1M  22% /persist
/dev/loop1                3.9M      1.1M      2.5M  31% /conf
/dev/tffsa3              53.0M      4.0M     46.2M   8% /coredump

Now try to load the firmware from the solaris operating system to the service processor.

#cd /var/tmp/147310-08
./sysfwdownload Sun_System_Firmware-7_4_5-SPARC_Enterprise_T5140+T5240.pkg
Share

REMOVE A FILE STARTING WITH A Dash “-“

September 26th, 2021, posted in Solaris
Share

ls |grep -i file
–file1

$ rm –file1
rm: illegal option — file1
usage: rm [-fiRr] file …

rm “–file1”
rm: illegal option — file1
usage: rm [-fiRr] file …

Solution:
$ rm ./–file1
$ ls|grep -i file

Share

ENABLE HTTPS ON ORACLE M SERIES SERVERS(XSCF)

September 4th, 2021, posted in Solaris
Share

If you have not enabled https on your M series servers, this is how you enable it.

 

Description From Oracle :
Hypertext Transfer Protocol (HTTP) over an authenticated/encrypted connection allows you to use the XSCF web browser securely. This is called the HTTPS service. Authentication is provided with a certificate authority and private keys. To use the HTTPS service, you must enable it, and provide an optional port number. The default port is 443. To enable HTTPS service, use the sethttps command”


1) Login to your xscf of the server through ssh
Assuming you have already configured network on xscf and enable ssh. If not, you can login through console/console server, configure network interface on xscf and then you can proceed with further steps.


2) Once you are in xscf, check the status of https
XSCF> showhttps
HTTPS status: disabled
 


3) Generate a self signed certificate.
XSCF> sethttps -c selfsign US California Irvine mycompany myemail@myemail.com
CA key and CA cert already exist. Do you still wish to update? [y|n] :y
Enter passphrase:
Verifying – Enter passphrase:


4) Check the HTTPS Status
XSCF> showhttps
HTTPS status: disabled
Server key: installed in Jul 16 12:46:20 MST 2013
CA key: installed in Jul 16 12:46:18 MST 2013
CA cert: installed in Jul 16 12:46:18 MST 2013
CSR:
—–BEGIN CERTIFICATE REQUEST—–
MIIB0zCCATwCAQAwgZIxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlh
MQ8wDQYDVQQHEwZDdWx2ZXIxDTALBgNVBAoTBENpdHkxDDAKBgNVBAsTA1NQRTER
MA8GA1UEAxMIRUlTLVVOSVgxLTArBgkqhkiG9w0BCQEWHmVpcy11bml4LXNlcnZp
Y2VzQHNwZS5zb255LmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA54QN
BSBfflQBtIgL3LqRKTqHixMP/TTmeMANy8yz723hcLDBTT9EarKkDb2IVqHE
ENb5mp8N7hJpGDzUPhn3XdD0+XoP2iaFeqQtihMqCob/bC21Me6gQDIdZoRK4sRj
FJ0ODjdB9sDj4KFKUkE4TIh3Jimz8wHn4VXbqGECAwEAAaAAMA0GCSqGSIb3DQEB
BAUAA4GBALMsMV5NugRnZwJfGiQbB6KNILMbCHg8xrF9IarFopt7uLDOxUoKvjQb
NDoGF+/tjxrADEZqSAmWeqiVZyI/0e2lU58si4TFZwEtjv6wopJVRkyg9XLfNe7
FB5DkBOI2Rihn6+SP0C3c/OOWNKo5BKekbeXennuWMJJbHDvRW6U
—–END CERTIFICATE REQUEST—–
It will be still disabled, we haven’t enabled the https yet.


5) Now we shall enable https:
XSCF> sethttps -c enable
Continue? [y|n] :y
Please reset the XSCF by rebootxscf to apply the https settings.


6) Reset XSCF
XSCF> rebootxscf
The XSCF will be reset. Continue? [y|n] :y
execute S10ioxoffXSCF>   —  complete
Jul 16 12:48:35 myhost XSCF[104]: XSCF shutdown sequence start
execute K000end  —  complete
execute K100end  —  complete
execute K101end  —  complete
<Lines Omitted>


7) Once the XSCF is up check the https status, now it will be enabled.
XSCF> showhttps
HTTPS status: enabled
Server key: installed in Jul 16 12:52:04 MST 2013
CA key: installed in Jul 16 12:52:04 MST 2013
CA cert: installed in Jul 16 12:52:04 MST 2013
CSR:
—–BEGIN CERTIFICATE REQUEST—–
MIIB0zCCATwCAQAwgZIxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlh
MQ8wDQYDVQQHEwZDdWx2ZXIxDTALBgNVBAoTBENpdHkxDDAKBgNVBAsTA1NQRTER
MA8GA1UEAxMIRUlTLVVOSVgxLTArBgkqhkiG9w0BCQEWHmVpcy11bml4LXNlcnZp
Y2VzQHNwZS5zb255LmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA54QN
BSBfflQBtIgL3LqRKTqHixMP/TTmeMANy8yz723hcLDBTT9EarKkDb2IVqHE
ENb5mp8N7hJpGDzUPhn3XdD0+XoP2iaFeqQtihMqCob/bC21Me6gQDIdZoRK4sRj
FJ0ODjdB9sDj4KFKUkE4TIh3Jimz8wHn4VXbqGECAwEAAaAAMA0GCSqGSIb3DQEB
BAUAA4GBALMsMV5NugRnZwJfGiQbB6KNILMbCHg8xrF9IarFopt7uLDOxUoKvjQb
NDoGF+/tjxrADEZqSAmWeqiVZyI/0e2lU58si4TFZwEtjv6wopJVRkyg9XLfNe7
FB5DkBOI2Rihn6+SP0C3c/OOWNKo5BKekbeXennuWMJJbHDvRW6U
—–END CERTIFICATE REQUEST—–


8) Login to XSCF from your web browser and confirm everything is operational.
https://<your_xscf_hostname_or_ip>


REFERENCES :
Share

Capture Snapshot From ILOM

July 25th, 2021, posted in Solaris
Share
1)
-> cd /SP/diag/snapshot
 
2) specify the host and directory where the snapshot will be transferred. 
-> set dump_uri=ftp://<valid_ftpuser>@ip_address//<directory>
Enter remote user password: *******
Set ‘dump_uri’ to ‘ftp://root@<ip_address>//tmp’

3) Check status of “snapshot”
-> show

/SP/diag/snapshot

   Targets:

   Properties:

       dataset = normal
       dump_uri = (Cannot show property)
       encrypt_output = false
       result = Running  <– check for completed status

4) Check for the completion of snapshot
-> show

/SP/diag/snapshot

   Targets:

   Properties:

       dataset = normal
       dump_uri = (Cannot show property)
       encrypt_output = false
       result = Collecting data into
ftp://root@<ip_address>//tmp/v4v-t5120a-sp_<ip_address>_2013-08-10T17-43-27.zip
Snapshot Complete.

Done.
References:
Share