HowTo Install redhat package with YUM command without RHN

I think it’s not too late to play with Redhat Enterprise Server :-). Need a kind of a distraction from Solaris, and other Ora** HW/SW product.. hahaha.

I just install RHEL version 6.4. trying to use yum command to install rpm-build package, but it showing below error messages:

[root@redhat64 ~]# yum install rpm-build
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Setting up Install Process
No package rpm-build available.
Error: Nothing to do

By default, if you check with “yum repolist all” command, there are 2 repo source with status disabled:

[root@redhat64 ~]# yum repolist all
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
repo id                              repo name                                                                   status
rhel-source                          Red Hat Enterprise Linux 6Server - x86_64 - Source                          disabled
rhel-source-beta                     Red Hat Enterprise Linux 6Server Beta - x86_64 - Source                     disabled
repolist: 0
[root@redhat64 ~]#

Check the Redhat repository configuration file, there are two repo name, both are pointed to redhat website:

[root@redhat64 ~]# cd /etc/yum.repos.d/
[root@redhat64 yum.repos.d]# ls
rhel-source.repo
[root@redhat64 yum.repos.d]# more rhel-source.repo 
[rhel-source]
name=Red Hat Enterprise Linux $releasever - $basearch - Source
baseurl=ftp://ftp.redhat.com/pub/redhat/linux/enterprise/$releasever/en/os/SRPMS/
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

[rhel-source-beta]
name=Red Hat Enterprise Linux $releasever Beta - $basearch - Source
baseurl=ftp://ftp.redhat.com/pub/redhat/linux/beta/$releasever/en/os/SRPMS/
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-beta,file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
[root@redhat64 yum.repos.d]# 

We need to register to RHN in order to use those repo source, even you try to enable the repo, by editing the line “enable=0” to “enable=1” but it won’t work. The easy way is build a local repository from your current redhat’s DVD / ISO file:

# mkdir /cdrom
# mount /dev/cdrom /cdrom

Rename existing repo file “rhel-source.repo” to “rhel-source.repo.backup” or whatever you want.
Create another repo file name, example “dvd.repo”:

# vi dvd.repo
[dvd-source]
name=RHEL 6.4 dvd repo
baseurl=file:///cdrom/Server
enabled=1
gpgcheck=0

Check your repo config, Test  and try to install the package:
# yum repolist
# yum install rpm-build

[root@redhat64 yum.repos.d]# yum repolist
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
repo id                                               repo name                                                    status
dvd-source                                            RHEL 6.4 dvd repo                                            3,648
repolist: 3,648
[root@redhat64 yum.repos.d]# yum install rpm-build
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

dvd-source                                                                                        | 3.9 kB     00:00 ...

dvd-source/primary_db                                                                             | 3.1 MB     00:00 ...
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package rpm-build.x86_64 0:4.8.0-32.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

=========================================================================================================================
 Package                     Arch                     Version                         Repository                    Size
=========================================================================================================================
Installing:
 rpm-build                   x86_64                   4.8.0-32.el6                    dvd-source                   126 k

Transaction Summary
=========================================================================================================================
Install       1 Package(s)

Total download size: 126 k
Installed size: 315 k
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.

  Installing : rpm-build-4.8.0-32.el6.x86_64 [                                                                     ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [####                                                                 ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [#####                                                                ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [######                                                               ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [#######                                                              ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [########                                                             ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [#################                                                    ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [#########################                                            ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [###############################                                      ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [#################################                                    ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [###################################                                  ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [####################################                                 ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [#########################################                            ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [##########################################                           ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [###########################################                          ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [############################################                         ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [##############################################                       ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [################################################                     ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [#################################################                    ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [########################################################             ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [#########################################################            ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [##########################################################           ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [################################################################     ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [##################################################################   ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [###################################################################  ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64 [#################################################################### ] 1/1
  Installing : rpm-build-4.8.0-32.el6.x86_64                                                                         1/1

dvd-source/productid                                                                              | 1.7 kB     00:00 ...
  Verifying  : rpm-build-4.8.0-32.el6.x86_64                                                                         1/1
Installed:
  rpm-build.x86_64 0:4.8.0-32.el6                                                                                        
Complete!
[root@redhat64 yum.repos.d]#
##################

We can also build a local http or ftp repository server, will talk later on another post.

MPT Firmware Fault, code 0800

Getting below error messages during my Sparc M5000 machine boot up:

{20} ok boot
Boot device: root  File and args:
MPT Firmware Fault, code 0800

read failed
ERROR: FCode Aborted.

The file just loaded does not appear to be executable.
{20} ok Sep  9 09:56:27 dm6-sc0 fmd: SOURCE: sde, REV: 1.16, CSN: BEF0850709  EVENT-ID: 49817271-d01d-4ece-8098-a362c9e52f71 Refer to http://www.sun.com/msg/SCF-8001-KC for detailed information.

Can’t find any clue what does “MPT Firmware Fault, code 0800” error code mean on MOS. Technical support asked to power cycle twice, including replacing the IOU, but the problem still persistent.

Anyway, after perform troubleshooting, below step solved my problem:

[boot into single user mode via DVD or Network, perform FSCK, mount root file system, installboot, then update boot-archive:

{29} ok boot net -s
# fsck -F ufs -y /dev/rdsk/c0t0d0s0

** /dev/rdsk/c0t0d0s0
BAD SUPERBLOCK AT BLOCK 16: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS?  yes
FOUND ALTERNATE SUPERBLOCK 80032 WITH MKFS
USE ALTERNATE SUPERBLOCK?  yes

FOUND ALTERNATE SUPERBLOCK AT 80032 USING MKFS
If filesystem was created with manually-specified geometry, using
auto-discovered superblock may result in irrecoverable damage to
filesystem and user data.

CANCEL FILESYSTEM CHECK?  yes

Please verify that the indicated block contains a proper
superblock for the filesystem (see fsdb(1M)).

FSCK was running in YES mode.  If you wish to run in that mode using
the alternate superblock, run `fsck -y -o b=80032 /dev/rdsk/c0t0d0s0′.

——————-

Owh, there was bad superblock issue, so I need to find the superblock backup then re-run fsck with -o b=<backup_superblock> option:

# newfs -Nv /dev/rdsk/c0t0d0s0
mkfs -F ufs -o N /dev/rdsk/c0t0d0s0 81937152 -1 -1 8192 1024 160 1 167 8192 t 0 -1 8 128 n
Warning: 5376 sector(s) in last cylinder unallocated
/dev/rdsk/c0t0d0s0:     81937152 sectors in 13337 cylinders of 48 tracks, 128 sectors
40008.4MB in 834 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
…………….
super-block backups for last 10 cylinder groups at:
81009696, 81108128, 81206560, 81304992, 81403424, 81501856, 81600288,
81698720, 81788960, 81887392
#

# fsck -F ufs -y -o b=81887392 /dev/rdsk/c0t0d0s0

*continue fsck to other slices

# mount /dev/dsk/c0t0d0s0 /mnt
# installboot /mnt/usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0
# bootadm update-archive -fv -R /mnt

Solaris 11 ZFS Root Recovery

[SOLARIS 11 ZFS ROOT RECOVERY:

* Boot system into single user via network or CDROM.
boot net -s
boot cdrom -s

* On X86 machine, you need edit grub and append -s on kernel line OR boot CDROM with Solaris-11-Text image/media, then select option “3 shell” on “Welcome to the Oracle Solaris Installation Menu”.
* If it ask username: root/solaris or root/password

# mkdir /a /b
# zpool import -R /a -f rpool
# zfs mount –o mountpoint=/b rpool/ROOT/solaris
# vi /b/etc/shadow

*Remove the root password section, it will become look like this:
root::15356::::::

*Note that by default, the new Solaris 11 doesn’t allow blank password
*To allow empty passwords at login:

# vi /b/etc/default/login
*Switch this line “PASSREQ=YES” to “PASSREQ=NO”

*If you access the system via SSH, also check the directive PermitEmptyPasswords in “/etc/ssh/sshd_config”
PermitEmptyPasswords yes

# cd /
# umount /b
# zpool export -f rpool
# reboot

How To replace M4000/M5000 XSCF board

XSCF or eXtended System Control facility unit is known as service processor for M-Series server.
The XSCF unit is a cold replacement component. This means the entire server must be powered off and the power cords disconnected to replace the XSCF unit. Execute “showhardconf” or “showstatus” command to make sure the XSCF is faulted.

XSCF> showhardconf


*   XSCFU Status:Degraded,Active; Ver:0101h; Serial:BFxxxxxxx  ;
+ FRU-Part-Number:CF00541-0481 04   /541-0481-04       ;

I hv been asked by some people on how to backup XSCF configuration before replacing the XSCF board. They presume the XSCF configuration need to backup first because there are only 1 XSCF board on M4000/M5000 server. In fact no need to backup the config because there was a backup copy of XSCF configuration on Operator Panel, both XSCF and Operator Panel always synchronizing its data each time XSCF bootup or there was a changes on XSCF configuration. Thats way there is a restriction to replace both XSCF and Operator Panel simultaneously.

Okay, if you ready to replace the XSCF board, below are the instruction:

[Shutdown the OS, Power off the server and unplug the power cord and XSCF ethernet cables.

[Use proper ESD grounding technique and anti static mat, replace the XSCF board:

*M4000 XSCF board location:

*M5000 XSCF board location:

# Plug all cables then power on server, wait till the new XSCF board startup. It will reboot around 2-3 times. you will see the messages of XSCF and OPNL synchronize its data during startup:

…..
initialize XSCF common database (OWN)  —  complete
synchronize setup data (XSCF -> OPNL)  —  complete
initialize XSCF common database (ACTIVE)  —  complete
wait for database synchronization  —  complete
execute S00clis_all  —  complete
…..

[If the boot process is finished, then try to log in. If you see below error messages:

XCP version of Panel EEPROM and XSCF FMEM mismatched,
Panel EEPROM=1090, XSCF FMEM=1100

Then you need to upgrade the XSCF firmware. Download the latest firmware from MOS, then perform firmware upgrade.

[XSCF FIRMWARE UPGRADE:

*VIA FTP:

XSCF> getflashimage -l        >CHECK CURRENT FIRWARE
XSCF> getflashimage -u AZIZ ftp://10.32.17.61/FFXCP1112.tar.gz    >> aziz is username, 10.32.17.61 is ftp server on my laptop
Password: *******
0MB received
1MB received
2MB received
3MB received
4MB received
5MB received
6MB received
7MB received
8MB received

Download successful: 42660 Kbytes in 50 secs (987.298 Kbytes/sec)
Checking file…
MD5: 73ca6370dc6c636f2e3845b66caa203a
XSCF> getflashimage -l

XSCF> flashupdate -c check -m xcp -s 1112
XCP update is possible with domains up

XSCF> flashupdate -c update -m xcp -s 1112
The XSCF will be reset. Continue? [y|n] :y
Checking the XCP image file, please wait a minute
XCP update is started (XCP version=1112:last version=1081)
OpenBoot PROM update is started (OpenBoot PROM version=02180000)

*VIA USB:
– checked version, update firmware
XSCF> version -c xcp -v

XSCF> getflashimage file:///media/usb_msd/FFXCP1112.tar.gz

Note the different of M-Series firmware file below:
getflashimage file:///media/usb_msd/IKXCP1112.tar.gz    >>for M3000
getflashimage file:///media/usb_msd/FFXCP1112.tar.gz    >>for M4000/5000
getflashimage file:///media/usb_msd/DCXCP1112.tar.gz    >>for M8000/M9000

XSCF> flashupdate -c check -m xcp -s 1112
XCP update is possible with domains up

XSCF> flashupdate -c update -m xcp -s 1112

XSCF> version -c xcp -v
XCP0 (Reserve): 1110 <<XCP0 will take few minutes to finish update
OpenBoot PROM : 02.29.0000
XSCF          : 01.11.0000
XCP1 (Current): 1112 <<updated already
OpenBoot PROM : 02.29.0000
XSCF          : 01.11.0002
OpenBoot PROM BACKUP

XSCF> version -c cmu -v

[If you hv finished on upgrading the firmware or there are no firmware issue, then make sure the device status again with “showhardconf” and “showstatus” command.

[Continue powering on the domain:

XSCF> poweron -d0
DomainIDs to power on:00
Continue? [y|n] :y
Poweron canceled due to invalid system date and time.
XSCF>

Wait, did you see above error messages? yes the domain unable to boot because the system date and time is invalid.

#set the new date and time, Example for 24 Oct 2012 @ 10:23:

XSCF> setdate -u -s 102410232012.00
Wed Oct 24 10:23:00 UTC 2012
The XSCF will be reset. Continue? [y|n] :y

#If you want to change the timezone, run the settimezone command. example:

XSCF> settimezone -c settz -s Asia/Jakarta

#DONE. Now power on the domain again.

How to Configure SL24 / SL48 with Netbackup

SL24 and SL48 are the Oracle’s entry level of Autoloader/Tape Library.

Check here for complete documentation.

L24/48 Library are using a single SCSI ID and two logical unit numbers (LUN). LUN 0 controls the tape drive and LUN 1 controls the robotic. So, its require an HBA that supports multiple LUNs. If multiple LUN support is not enabled, the host server cannot scan beyond LUN 0 to discover the Library. It just sees the tape drive.

To check the device and connectivity status from Solaris, please use the show_FCP_dev option: “cfgadm -o show_FCP_dev -al”, instead of “cfgadm -al” command. The robotic or changer will not shown if you use standard “cfgadm -al” command.
If the changer detected already by “cfgadm -o show_FCP_dev -al” command but still not detected by NBU sgscan command, check your NBU device configuration. You need to modify the st.conf file in order to detect the devices on two LUNs.

[Find the following line in the st.conf file:

name=”st” target=0 lun=0;

Replace that line and the following lines through target 5 with the following. Doing so modifies the st.conf file to include searches on non-zero LUNs:

name="st" target=0 lun=0;
name="st" target=0 lun=1;
name="st" target=1 lun=0;
name="st" target=1 lun=1;
name="st" target=2 lun=0;
name="st" target=2 lun=1;
name="st" target=3 lun=0;
name="st" target=3 lun=1;
name="st" target=4 lun=0;
name="st" target=4 lun=1;
name="st" target=5 lun=0;
name="st" target=5 lun=1;
name="st" parent="fp" target=0;
name="st" parent="fp" target=1;
name="st" parent="fp" target=2;
name="st" parent="fp" target=3;
name="st" parent="fp" target=4;
name="st" parent="fp" target=5;
name="st" parent="fp" target=6;

Click here for complete information on how to configure tape drive and robotic devices for Netbackup.

If the SL24/SL48 has the SAS tape drives and you are using LSI SAS HBA, please check and upgrade the SAS HBA driver.

There was an issue with the LSI SAS1 (3GB) HBA with a firmware level of 1.26.00 and below, where the HBA will not see any SAS devices connected to it. Check below document (MOS access required) for more detail.

HBA – LSI SAS HBA Firmware Issue, SAS Devices Not Being Seen by Server (Doc ID 1350564.1)

ERROR: Last Trap: Instruction Access Exception

{0} ok boot
Boot device: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk@0,0:a File and args:
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,Sun-Fire-T200/ufsboot
Loading: /platform/sun4v/ufsboot
ERROR: Last Trap: Instruction Access Exception

If you got above error messages when powering on Sun Server (T-series, T1000/T2000), and the boot process stuck in there, do not call Oracle support or open SR via MOS unless you try below simple troubleshooting step:

Try to unplug all USB devices – ie USB keyboard + mouse, KVM etc, then connect your laptop/PC to server via serial port then reboot the server. IF the error messages are disappeared, I believe the server will able to boot as usual.

This issue are mostly related with USB keyboard /mouse or other USB related devices. It could be the USB devices or the USB port of the server it self. Try to plug the USB device on another port then reboot the server again. For T2000 there are 4 USB port on the back and 2 USB port on the front.

How to reset/recover Integrated Lights Out Manager (ILOM) password

The default user and password of ILOM is “root/changeme”, but if you hv changed the password already and due for some reason you forgot the password, here are the step by step to revocer the ILOM password.

First of all, try to change the password with ipmitool, but if its still doesn’t work, try below step:

Notes:
– You must be physically present at the server to perform this procedure.
– This procedure uses the default user account to enable you to recover a lost password or to re-create the root user account.
– You cannot change or delete the default user account.

1. Connect to ILOM via serial console and log in using the default user account.
SUNSP-xxxxxxxx login: default
Press and release the physical presence button.
Press return when this is completed…

2. Prove physical presence at your server.
Press and release the physical presence button.

The Physical Presence button on the Sun SPARC Enterprise T5xxx servers and X-Series is the Locator button:

But, for Sparc T3/T4 model, the physical presence are on rear side, except for T3-1b/T4-1b:
SPARC T3-1/T4-1: (rear) pin-hole to the left of the USB ports
SPARC T3-2/T4-2: (rear) pin-hole to the left of NET0
SPARC T3-4/T4-4: (rear) to the right of OK LED, above the USB port
SPARC T3-1b/T4-1b: (front) Locate button/Physical Presence (White LED)

3. Return to your serial console and press Enter.

You will be prompted for a password.

4. Type the password for the default user account: defaultpassword

5. Reset the account password or re-create the root account.

-> set /SP/users/root password
Enter new password: ********
Enter new password again: ********

6. Type “exit” to leave default login
7. try login with your new root password

—————-

Update for The “Physical Presence” button locations by server:
locate_button

Physical Presence for SPARC T4-1 : rear, pin/hole between net3 and usb0 (red circle)

SPARC_T4_1_rear_zoom

NOTES
– T7-x, S7-x and all platforms forward should use the Locator button (front/rear) as the Physical Presence switch
– To perform some procedures documented in the Oracle ILOM core documentation, you must create a serial connection to the server and activate the Physical Presence switch on the server. For information about creating a serial connection, refer to the installation guide for the server.
– If the physical presence/locator button is not working and/or can not be located, then as temporary workaround the physical presence check can be disabled:
– -> show /SP check_physical_presence
– -> set /SP check_physical_presence=false
– -> show /SP check_physical_presence
and it can be later enabled
– -> show /SP check_physical_presence
– -> set /SP check_physical_presence=true
– -> show /SP check_physical_presence
– For more information look at the documents below:
– T Series Server Documentation
– Oracle Integrated Lights Out Manager (ILOM) 3.x Documentation

If you have MOS access, read more on doc : 1509660.1

Oracle Support Document 1509660.1 (How to locate the “Physical Presence” button on SPARC T3-x, T4-x, T5-x, T7-x, S7-x Servers)

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1509660.1