Reset iLO admin password

If you have already installed the HP Lights utility then you can use the below steps to reset ILO admin password.

STEP 1: #/sbin/hponcfg -a -w /tmp/Administartor_reset_pw.xml

STEP 2: #vi /tmp/Administartor_reset_pw.xml

The entry will be like below



STEP 3: # /sbin/hponcfg /f Administrator_reset_pw.xml -v (Apply the config)




Reset iLO console from Enclosure SSH session

Author : Bibith Dathan

How to reset ILO from Enclosure SSH session? 

If web interface is not responding and able to connect via Enclosure ssh session
------------------------------------------------------------------------------------------------


ENC>show server list //get the server number

ENC> connect server 1     //this "1" is server number obtained from " show server list " command
hpiLO-> cd /Map1
status=0
status_tag=COMMAND COMPLETED

/Map1

hpiLO-> reset
status=0
status_tag=COMMAND COMPLETED
Resetting iLO.
CLI session stopped

Now reset done on iLO console.






ILO configuration  change including Ip change from OS
---------------------------------------------------------------------

Install the utility ho lights on ur linux machine

#rpm -ivh hponcfg-3.1.1-0.rpm

then follow the below steps

#/sbin/hponcfg -a -w /tmp/ilo.out  // Get configuration
#vi  /tmp/ilo.out //Edit configuration  to reflect changes ( Note this is xml file )
#/sbin/hponcfg -f /tmp/ilo.out -v  //Apply the configuration



Setup and Configure iLO using HP Lights-Out Configuration Utility

Author : Bibith Dathan


Setup and Configure iLO using HP Lights-Out Configuration Utility:
  • HP Lights-Out Online Configuration utility (HPONCFG) is a Windows or Linux operating system based utility available to configure iLO.
  • The HP Lights-Out Configuration Utility (HPONCFG), which is part of latest HP SmartStart CDs Or u can download from HP site.
  • The utility u can download from HP site or you can install it from HP smart CD.


root:serverA# rpm -qf /sbin/hponcfg
hponcfg-3.1.1-0
root:ServerA#


Requirements before using HPONCFG:
  •     The RILOE II, iLO, or iLO 2 Management Interface Driver must be loaded on the server. HPONCFG displays a warning if the driver is not installed.
  •     HPONCFG requires minimum RILOE II, iLO, and iLO 2 firmware versions.  To determine the minimum firmware version required, see the HP SmartStart Scripting Toolkit Linux and Windows Editions Support Matrix.



HPONCFG can be used to perform the following tasks:

    1. Obtain an entire configuration
    2. Obtain a specific configuration
    3. Set a configuration



Value    Meaning

0        The script was sent successfully to the device, or there is no RILOE II,     
          iLO, or iLO 2 present in the system.

1        The script could not be sent to the device.


HPONCFG - command Syntex:

#hponcfg [-help][-?][-reset][-f filename][-l filename] [-w filename][-get_hostinfo][-m firmwarelevel]  [-mouse | -mouse -dualcursor | -mouse -allusers]


Simple steps to config ILO using this utility:


1. #/sbin/hponcfg -a -w /tmp/ilo2.out  (Get configuration )
2. #vi  /tmp/ilo.out -  (Edit configuration  to reflect changes )
     ( Note this is xml file )
3. #/sbin/hponcfg -f /tmp/ilo.out -v  (Appy the configuration)




Setting a specific configuration:

A specific configuration can be sent to the iLO, iLO2, or RILOE II by using the command format:

#HPONCFG /f add_user.xml /l log.txt



Setup and configure ILO using ILO RBSU : Please click here




Setup and Configure ILO console : How to ?



We can configure ILO console using ILO RBSU at first time while install server,

Below will explain how to use ILO RBSU ,

1. Turn ON the Server, press F8 key at the Integrated Lights-Out (iLO) prompt.

 
2. If prompted - Enter user name and Password.
    (use the information which u found on iLO tag)

3. Once you login, you will get iLO RBSU screen.

4. From iLO RBSU, go to Network and select DNS/DHCP option

5. Disable the DHCP (Since we are going to set a static IP for iLO)

6. Now under Network menu, select NIC and TCP/IP settings.

7. Now enter an IP address and Subnet Mask for ILO

8. To Save the settings, please press F10 key.

9. Go to File menu and select Exit to close the iLO Configuration window.

10.Press Enter key to restart Server



To setup ILO using HP Lights Out Utility : Please click here



Boot process of HP Integrity servers



Boot process of HP Integrity servers :





EMS hardware monitoring in HPUX

 EMS hardware monitoring in HP UNIX:

By default, EMS HW Monitoring is enabled on your system (In 11i v3, SFM is enabled by default).
By default, messages regarding major warnings, critical events on hardware being monitored and it will be :

1. Written to /var/adm/syslog/syslog.log
2. E-mailed to root


To send an test event to disk_em monitor

 # /etc/opt/resmon/lbin/send_test_event disk_em


All the events will be saved in - /var/opt/resmon/log/event.log.


EMS hardware monitoring can be reconfigured using the below file (Monitoring Request Manager)

- /etc/opt/resmon/lbin/monconfig


To stop or start EMS Hardware Monitoring

 # /etc/opt/resmon/lbin/monconfig
   Press K for Kill (Disable) Event Monitoring
   Press E for Enabling Event Monitoring

To check the current Monitoring status

# /etc/opt/resmon/lbin/moncheck

o/p will be like below

>/StorageAreaNetwork/events/SAN_Monitor ... NOT MONITORING.
  (Possibly there is no hardware to monitor.)

>/system/events/cpu/cmc ... OK.
 For /system/events/cpu/cmc/cache_errors:
  Events >= 3 (MAJOR WARNING) Goto SYSLOG
  Events >= 3 (MAJOR WARNING) Goto EMAIL; addr=root
  Events >= 1 (INFORMATION) Goto TEXTLOG; file=/var/opt/resmon/log/event.log

.....
.....
>/system/events/system_status ... OK.
 For /system/events/system_status/ui_host/aemhpvm1:
  Events >= 1 (INFORMATION) Goto TEXTLOG; file=/var/opt/resmon/log/event.log
  Events >= 3 (MAJOR WARNING) Goto SYSLOG
  Events >= 3 (MAJOR WARNING) Goto EMAIL; addr=root


How to stop monitoring for  particular hardware?


If you want to stop getting monitoring alerts for any devices, add the H/W address of the device not to be monitored
in "/var/stm/data/tools/monitor/disabled_instances" file and restart (stop and start) EMS services.

1.Add the HW address in to - /var/stm/data/tools/monitor/disabled_instances
2.Restart the EMS services ( #/etc/opt/resmon/lbin/monconfig )




SAN Migration in Linux / HP UX


There are few ways to migrate a SAN in Linux / Unix.

1.Storage level
2.Host level

In host level , we have few choice

1.Using pvmove ( Not reliable and not suggested by anyone)
2.Using back and restore . 
3.Using LVM mirror.


2. Using backup and restore Method:

Note : Here we required down time for Application which is belongs to the FS

1.Create new VG and New temp FS
2.Down the Application
3. Copy the data using backup tool (fbackup , TSM ,etc)
4. Restore the data to new FS (new mount point)
5.Unmount the existing FS
6. Mount the new LVOLs to old Mount directory

Or else for backup and restore we can use "rsync" command .

Run RSYCN Command like below in background. 

#nohup rsync -apvz --progress --exclude "lost+found/" /SOURCE_DIR/*  /DESTINATION_DIR/ &
3. SAN migration Using LVM mirror

Note :1.  Here we no need of down time. But take a full backup for safety. 
          2. if it is in HP UX , the VG should be created with vgcreate -e option. Otherwise we need to modify the vg using vgmodify (still we required downtime for FS, concern is max_PE_per PV)

1. Add the new storage Disk to VG
2. Mirror the existing LVOLs
3. Once mirror done , Break the mirror
4. Remove the old storage disk from VG


================================

The Below is the Migration steps i followed in Linux.

1. One mounted fs on a plain lvm volume with a single lun:
/dev/mapper/DATA-VG_DATA 92G 74G 14G 85% /mnt/DATA

2. Get new lun working at linux level,


for example using dm-multipath:
mpath13 (3600c0ff000d8230d16de5b4c01000000) dm-24 HP,MSA2312sa
[size=93G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 0:0:0:17 sdu 65:64 [active][undef]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:17 sdab 65:176 [active][undef]

3. Create new physical volume:
[root@nodeA# pvcreate /dev/mapper/mpath13
Physical volume "/dev/mapper/mpath13" successfully created

4. Extend original volume group:
[root@nodeA# vgextend VG_DATA /dev/mapper/mpath13
Volume group "VG_DATA" successfully extended

5. Convert logical volume to a mirror with 2 legs:
[root@nodeA# lvconvert -m 1 /dev/VG_DATA/LV_DATA --corelog
VG_DATA/LV_DATA: Converted: 12.2%
VG_DATA/LV_DATA: Converted: 24.4%
VG_DATA/LV_DATA: Converted: 36.2%
VG_DATA/LV_DATA: Converted: 48.3%
VG_DATA/LV_DATA: Converted: 60.3%
VG_DATA/LV_DATA: Converted: 72.4%
VG_DATA/LV_DATA: Converted: 84.6%
VG_DATA/LV_DATA: Converted: 96.7%
VG_DATA/LV_DATA: Converted: 100.0%
Logical volume LV_DATA converted.



[root@nodeA# vgdisplay VG_DATA -v
Using volume group(s) on command line
Finding volume group "DATA"
--- Volume group ---
VG Name VG_DATA
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 21
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 2
Act PV 2
VG Size 186.25 GB
PE Size 4.00 MB
Total PE 47681
Alloc PE / Size 47616 / 186.00 GB
Free PE / Size 65 / 260.00 MB
VG UUID VLzsFf-vlqq-TmSR-2P53-izm4-dVH1-pcNeii

--- Logical volume ---
LV Name /dev/VG_DATA/LV_DATA
VG Name VG_DATA
LV UUID 9Q9PrO-TBmP-1prT-8PSV-tFxT-3GR0-FE94Q9
LV Write Access read/write
LV Status available
# open 1
LV Size 93.00 GB
Current LE 23808
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:16

--- Logical volume ---
LV Name /dev/VG_DATA/LV_DATA_mimage_0
VG Name VG_DATA
LV UUID w80F3L-JbHv-A5Dt-50dK-8N0k-h3IE-P0GzJL
LV Write Access read/write
LV Status available
# open 1
LV Size 93.00 GB
Current LE 23808
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:25

--- Logical volume ---
LV Name /dev/VG_DATA/LV_DATA_mimage_1
VG Name VG_DATA
LV UUID 5gOfn4-bCNB-tpG3-0gue-hhr9-k63p-E0Jb9U
LV Write Access read/write
LV Status available
# open 1
LV Size 93.00 GB
Current LE 23808
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:26

--- Physical volumes ---
PV Name /dev/dm-13
PV UUID R5henD-M3pW-dNaH-P4Xs-WBjW-fTWo-52nvTz
PV Status allocatable
Total PE / Free PE 23840 / 32

PV Name /dev/dm-24
PV UUID 3pPxpD-DX4U-ay6t-Gf2B-RoKP-Wfoz-rN2Usj
PV Status allocatable
Total PE / Free PE 23841 / 33

Voila.

6. Convert lv to unmirrored, removing the old pv:
[root@nodeA# lvconvert -m 0 /dev/VG_DATA/LV_DATA /dev/dm-13
Logical volume LV_DATA converted.

7. Remove old pv from vg:
[root@nodeA# VG_DATA /dev/dm-13
Removed "/dev/dm-13" from volume group "VG_DATA"

Done!
Now the VG is running with new PV which is from new SAN.

Blogger Tips and TricksLatest Tips And TricksBlogger Tricks