EMC Clariion with HP-UX V3 Agile DSF

Wednesday 27 Apr 2011 by Hell-me | No Comments
Filed under: HPUX
  • To disable legacy DSF's run the command rmsf -L.
  • The CLARiiON array (CX3 series, CX300, CX500, and CX700) must be running the FLARE-Operating-Environment release 26 or later and is required to support HP-UX 11iv3. This version of FLARE introduced the ALUA support for HP-UX 11i v3.
  • Configure the initiators for ALUA failover mode (failover mode4).
  • CLARiiON Open and HP No Auto Trespass initiator types are supported with HP-UX 11iv3 (11.31). CLARiiON Open initiator type implements peripheral device addressing resulting in expected HP-UX behavior of creating only eight legacy device special files (DSFs) per target port.
  • HP No Auto Trespass initiator type implements the Volume Set Addressing method. You must configure only HP No AutoTrespass if there are any legacy DSFs dependencies that have the format /dev/dsk/c2t1d0 and /dev/rdsk/c2t1d0.You may configure either CLARiiON Open or HP No Auto Trespass if there are no legacy DSFs dependencies and only
    persistent DSFs (also known as agile DSFs) are utilized that have the format /dev/disk/disk42 and /dev/rdisk/42.

Note: If using the Unisphere/Navisphere agent.config file, ensure that the
appropriate OptionsSupported setting is in the file, otherwise the initiator
setting on the array will be changed when the Unisphere/Navisphere agent
starts up. To maintain the Unisphere/Navisphere Manager initiator setting,
uncomment the OptionsSupported line in the agent.config file and change it
to state OptionsSupported ArrayType.

  • HP-UX v3 detect SPA/SPB with Disk , and status WDUNB :

Class     I  H/W Path  Driver S/W State   H/W Type     Description
===================================================================
disk      0  64000/0xfa00/0x1   esdisk   CLAIMED     DEVICE       HP      P2000 G3 FC
disk      3  64000/0xfa00/0xb   esdisk   CLAIMED     DEVICE       DGC     CX4-480WDUNB

If  Using PowerPath exclude path with :

#powermt unamange dev=disk3

#powermt save

Verify with :

# powermt display unmanaged
CLARiiON ID=CKM001009xxxxx
Logical device ID=50060160C6E0055450060160C6Exxxxx
Vendor ID=DGC     ; Product ID=CX4-480WDUNB
===============================================
-------------------- Host ---------------------
HW Path                            I/O Paths
===============================================
32/0/2/2/0/0/0.0x5006016946e0xxxxx.0x4000000000000000 c13t0d0
32/0/2/2/0/0/0.0x5006016346e0xxxxx.0x4000000000000000 c14t0d0
33/0/2/2/0/0/0.0x5006016146e0xxxxx.0x4000000000000000 c15t0d0
33/0/2/2/0/0/0.0x5006016b46e0xxxxx.0x4000000000000000 c16t0d0


HP Data Protector - OMNIDC Corrupted

Sunday 2 Jan 2011 by Hendrawan | No Comments
Filed under: Data Protector

If you find corrupted in DC binary files after checking IDB on HP Data protector,
you can remove the DC binary files and recreate them. Please find resolution below

Log

# omnidbcheck -extended
Check Level             Mode            Status
==================================================
Core                    -core           OK
Filenames               -filenames      OK
DCBF(presence and size) -bf             OK
SIBF(readability)       -sibf           OK
OMNIDC(consistency)     -dc             Corrupted: 1 major errors detected
DONE!

Resolution
1. Check all Check_* files in Omni Log (/var/opt/omni/server/log),
below i found error in check_dc.txt file.

Medium ID:                             Mpos[Bin/Db]  Offset Details 	Results
===============================================================================
0a344561:4c1dc756:223f:0005           Some Mpos are missing!      	Corrupted

2. Find, Identify and remove the media

omnimm -media_info 0a344561:4c1dc756:223f:0005 -detail
omnimm -export 0a344561:4c1dc756:223f:0005

3. Fix the IDB errors

omnidbutil -remap_dcdir
omnidbutil -fixmpos
omnidbcheck -dc –detail

The IDB should be ok again, if you still face problem you can contact HP support


Glassfish Autostartup Script on Linux

Wednesday 29 Sep 2010 by Hendrawan | 3 Comments
Filed under: Linux

Are you dizzy looking everywhere for the auto startup for Glassfish, please enjoy the cake below

#!/bin/bash
#
# chkconfig: 3 80 05
# description: Startup script for Glassfish
 
GLASSFISH_HOME=/opt/glassfish/bin;
GLASSFISH_OWNER=gfish;
GLASSFISH_ADMIN=admin;
GLASSFISH_DOMAIN=bascomp;
GLASSFISH_PASSWORD=/home/gfish/.asadminpwdgfish;
export GLASSFISH_HOME GLASSFISH_OWNER GLASSFISH_PASSWORD GLASSFISH_ADMIN GLASSFISH_DOMAIN
 
start() {
        echo -n "Starting Glassfish: "
        su $GLASSFISH_OWNER -c "$GLASSFISH_HOME/asadmin start-domain --user $GLASSFISH_ADMIN --passwordfile $GLASSFISH_PASSWORD $GLASSFISH_DOMAIN"
        echo "done"
}
 
stop() {
        echo -n "Stopping Glassfish: "
        su $GLASSFISH_OWNER -c "$GLASSFISH_HOME/asadmin stop-domain $GLASSFISH_DOMAIN"
        echo "done"
}
 
case "$1" in
        start)
                start
                ;;
        stop)
                stop
                ;;
        restart)
                stop
                start
                ;;
        *)
                echo $"Usage: Glassfish {start|stop|restart}"
                exit
esac
sh> chmod +x /etc/init.d/glassfish
sh> chkconfig --add glassfish
sh> chkconfig --level 35 glassfish on
sh> /etc/init.d/glassfish start

The path to the password file ".asadminpwdgfish" is /home/gfish/.asadminpwdgfish.
It contains the password in the following format:

AS_ADMIN_password=FillyourGlassfishPasswordHere

Reinstall grub on HP Smart Array

Friday 23 Apr 2010 by Hendrawan | No Comments
Filed under: Linux

Hi guys, long time no see. :d,
I want to share a triki or stupid trick on MBR problem.

Yesterday, I was fix a boot problem of HP Blade 460C with CentOS 5.4 i386 installed in my customer, some people in the Net fix that problem with reinstalling grub with grub-install command, I assume they have /dev/sda or /dev/hda on boot device, but since HP comes with RAID Controller (SMART ARRAY) hardware, the sda or hda seem not be use in here, because boot or any disk device come with /dev/cciss/c0d0.

So a workaround for solving this problem is just change boot device and device map on grub configuration.

See my old configuration bellow.

-/etc/grub.conf-------
# grub.conf generated by anaconda
#
#
#boot=/dev/sda
# default=0 # commented out by Proliant HBA install script
default=2
fallback=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
[...]
-/boot/grub/device.map----
# this device map was generated by anaconda
(hd4)     /dev/cciss/c0d0
(hd0)     /dev/sda

Now change "#boot=/dev/sda" with "boot=/dev/cciss/c0d0" in /etc/grub.conf
and "(hd0) /dev/sda" with "(hd0) /dev/cciss/c0d0" in /boot/grub/device.map

after that just running simple grub command bellow

bash> grub --batch --device-map=/boot/grub/device.map --config-file=/boot/grub/grub.conf
grub> root (hd0,0)
grub> setup (hd0)
grub> quit

Restart and hope this help


Save the earth by 60 minutes

Saturday 27 Mar 2010 by Hendrawan | No Comments
Filed under: Oot

Sysinfo.bascomp.org will turn off its service, on this day at 20.30-21.30 western Indonesia time, To celebrate the earth hour.
Let us turn off the notebook, computer, gadget, or even your data center, for the sake of the survival of our earth

may the force be with you


« Older Entries

  • Search