Sys-Admin Information's

Problems running glance on HP-UX

Hendrawan — Tue, 26 May 2009 06:27:13 +0000

Do you know what’s glance?
Glance is a system performance monitoring and diagnostic capabilities software from HP. Glance is more powerful when your running on HP-UX environment, cause they collect all information that require for monitoring the system in a real time. But, there’s no 100% perfect software, yesterday I have a little problem when running with glance, but as usually, we solve the problem like a pieces of cake.

here’s the summary about the problem

== Fatal Nums Error == C.03.72.00 09/29/03 ==
User: aragon(/dev/pts/tf) Date: Fri May 22 15:58:14
File: nums.C Line: 479 Product id: Glance
System: superdome B.11.11 9000/800
Errno: 0 (Error 0)
Connection to midaemon lost — check midaemon process and status.mi
== End of Error Msg =============================

Litte magic comes bellow

sh> su -
sh> mwa stop
sh> ps -ef | grep midaemon
       root  5005     1 11 09:19:20 ?         0:18 /opt/perf/bin/midaemon
       root  5680  2490  2 09:25:41 pts/5     0:00 grep midaemon
sh> kill -9 5005
sh> mwa start

and then try glance again.

FTP Refused connection on HP-UX

Hendrawan — Sat, 09 May 2009 05:27:23 +0000

When we try connected to HPUX server with FTP client with another user except root, sometimes we got a small problem with that.
But don’t be afraid, we got some workaround here.

Ok now let’s start the trial
1. First we try to connect to HPUX server with FTP from any client, with user “oracle”.

bash> ftp rohan
Connected to rohan.
220 rohan FTP server (Revision 3.0 Version wuftpd-2.6.1 Wed Dec 19 08:27:34 GMT2007) ready.
User (rohan:(none)): oracle
331 Password required for oracle.
Password: *****
530 Login incorrect.
Login failed.
ftp> bye
221 Goodbye.

2. Logging all connection
Back to HPUX, now we try to log all connection, including ftp.

sh> inetd -l

Check if the log was run properly

sh> tail -f /var/adm/syslog/syslog.log
Sep  2 08:35:51 rohan ftpd[22988]: FTP server (Revision 3.0 Version wuftpd-2.6.1 Wed Dec 19 08:27:34 GMT 2007) ready.
Sep  2 08:35:54 rohan ftpd[22988]: FTP LOGIN REFUSED (shell not in /etc/shells) FROM 10.14.14.12 [10.14.14.12], oracle

As you can see, inetd logging was run properly. But wait, see end of line of log, yes!! that the answer for that mysterious small problem on ftp connection.

3. Add user shell on listing system shell
Like i said before, in the line of log on syslog file, that’s the answer for this problem. Ok. Now we do like syslog said.

sh> grep oracle /etc/passwd
oracle:RHMbMFlgIVmB.:109:106::/home/oracle:/bin/bash

mmm, oracle used “bash” on default shell, on HPUX “bash” was not default install, ok next, we add that “bash” shell at default listing shell on HPUX.

sh> echo '/bin/bash' >> /etc/shells

4. Gotcha!!
All set. now we try to ftp again from client to HPUX server, with oracle user.

dos> ftp rohan
Connected to rohan.
220 rohan FTP server (Revision 3.0 Version wuftpd-2.6.1 Wed Dec 19 08:27:34 GMT2007) ready.
User (rohan:(none)): oracle
331 Password required for oracle.
Password:*****
230 User oracle logged in.
ftp> ls
200 PORT command successful.
150 Opening ASCII mode data connection for file list.
.cshrc
.exrc
.login
.profile
.sh_history
stage
.bash_history
226 Transfer complete.
ftp: 68 bytes received in 0.00Seconds 68000.00Kbytes/sec.
ftp> by
221-You have transferred 0 bytes in 0 files.
221-Total traffic for this session was 367 bytes in 1 transfers.
221-Thank you for using the FTP service on rohan.
221 Goodbye.

it’s work, easy like a pie, don’t forget to check syslog.

sh> tail -f /var/adm/syslog/syslog.log
Sep  2 08:43:23 rohan ftpd[23227]: Data port : 20
Sep  2 08:43:23 rohan ftpd[23227]: FTP server (Revision 3.0 Version wuftpd-2.6.1 Wed Dec 19 08:27:34 GMT 2007) ready.
Sep  2 08:43:27 rohan ftpd[23227]: FTP LOGIN FROM 10.10.14.172 [10.10.14.172], oracle
Sep  2 08:43:31 rohan ftpd[23227]: FTP session closed

Tulisan lama ini dibuat kembali, untuk teman yang baru training HP-UX 11.31 di singapur.
Gimana man masih blum bisa juga, nih gue kasih solvingnya,
hahahaha..

Boot archive error or corrupt

Hendrawan — Fri, 01 May 2009 06:50:45 +0000

A few weeks ago, I got a little problem with my solaris box, namely solaris won’t boot because the boot archive was corrupt, *sigh*. Anyway the boot archive in solaris 10 was contain kernel module and configuration file was needed for solaris to startup the system.

Error:

module /platform/i86pc/boot_archive error 3 bad or corrupt data while decompressing file

Workaround:

Boot up your solaris in “solaris failsafe mode”, next solaris image will mount with writeable mode on “/a” mount point

sh> rm -f /a/platform/i86pc/boot_archive
sh> bootadm update-archive -R /a
sh> reboot

IP multipathing on Solaris 10 with Hanic (NIC Redundancy with one IP)

Hendrawan — Sat, 25 Apr 2009 09:20:55 +0000

Hanic ?
Do you know what’s that.
Yes, Hanic is NIC Redundancy with one IP, hanic was made by “Partha Subramanian”, and based on perl, hanic more simply and powerfull than IPMP, the default solaris IP multipathing. Why hanic was simply, in hanic we unnecessary to defined all requirement for respective NIC , just install, run and ready to failover.

Bellow, this is the step by step for hanic used.

1. First of all, we must got the hanic source as usually

bash> wget http://www.sun.com/bigadmin/scripts/submittedScripts/hanic.tar.gz

2. Show your NIC for me

bash> ifconfig e1000g0 plumb
bash> ifconifg e1000g1 plumb

bash> vi /etc/hosts
192.168.85.3    training.bascomp.org    training

3. Install hanic on your system

bash> gunzip hanic.tar.gz|tar xvf -
bash> cd hanic
bash> chmod +x *
bash> ./hanic.install

As usually software installation you must follow the guide, something like this.
Define your primary and secondary NIC, type your IP Address, your netmask and then reboot your system, for completed the installation.

bash> init 6

4. Failover IP Address

bash> hanic -monitor;hanic -cleanup
bash> hanic -status
 
STATUS - HA NIC Monitoring
-------------------------------------------------
State       Active(Passive)    PID
-------------------------------------------------
Running     e1000g1(e1000g0)   1081
-------------------------------------------------

Oke. seem to be hanic work as predictable, furthermore we test the fail over with “switch” command, whereabout “switch” do the switch ip address from primary NIC to secondary NIC.

bash> ifconfig -a
e1000g1: flags=1000843&lt;UP,BROADCAST,RUNNING,MULTICAST,IPv4&gt; mtu 1500 index 6
inet 192.168.85.3 netmask ffffff00 broadcast 192.168.85.255
ether 8:0:27:86:2e:c4

bash> hanic -status
 
STATUS - HA NIC Monitoring
-------------------------------------------------
State       Active(Passive)    PID
-------------------------------------------------
Running     e1000g1(e1000g0)   1081
-------------------------------------------------

bash> hanic -switch
 
bash> hanic -status
 
STATUS - HA NIC Monitoring
-------------------------------------------------
State       Active(Passive)    PID
-------------------------------------------------
Running     e1000g0(e1000g1)   1081
-------------------------------------------------
 
bash> ifconfig -a
e1000g0: flags=1000843&lt;UP,BROADCAST,RUNNING,MULTICAST,IPv4&gt; mtu 1500 index 7
inet 192.168.85.3 netmask ffffff00 broadcast 192.168.85.255
ether 8:0:27:82:21:80

5. Failover offline interface
Oke works perfect ha, now lets start second trial, for this situation try to offline the active network interface, and see what’s going, for monitoring this trial, you can see wheter the connection drop or not with ping command.

bash> ifconfig -a
e1000g0: flags=1000843&lt;UP,BROADCAST,RUNNING,MULTICAST,IPv4&gt; mtu 1500 index 3
inet 192.168.85.3 netmask ffffff00 broadcast 192.168.85.255
ether 8:0:27:82:21:80
 
bash> hanic -offline
 
bash> ifconfig -a
e1000g1: flags=1000843&lt;UP,BROADCAST,RUNNING,MULTICAST,IPv4&gt; mtu 1500 index 4
inet 192.168.85.3 netmask ffffff00 broadcast 192.168.85.255
ether 8:0:27:86:2e:c4
 
bash> hanic -status
 
STATUS - HA NIC Monitoring
-------------------------------------------------
State       Active(Passive)    PID
-------------------------------------------------
Running     e1000g1(e1000g0)   1081
-------------------------------------------------

Source from: http://dot.choosen.net/2009/04/06/ip-multipathing-on-solaris-10-with-hanic-nic-redundancy-with-one-ip/

Mirroring/Unmirroring on Solaris 10

Hendrawan — Sat, 25 Apr 2009 07:49:43 +0000

Post kali ini dengan bahasa indonesia tentunya, akan membahas mengenai membuat mirror dan melepaskan mirror di solaris 10 x86.
sekedar informasi, RAID-1 yang dikenal dengan mirror ini sangat populer untuk tingkat data redudansi juga faster writeable performance,
RAID-1 biasanya digunakan untuk system operasi ditempatkan, dan juga untuk aplikasi dengan tingkat penulisan yang tinggi, contoh Redolog.
Memang sangat di yakinin bahwa untuk pembahasan mengenai RAID-1 ini sangat-sangat banyak bertebaran di internet, tapi apalah daya untuk kepentingan dokumentasi kita bahas disini.
Postingan RAID-1 ini menggunakan solaris volume manager (SVM), dan 2 disk dengan size yang sama.

Magic code here.
Dibawah ini adalah kondisi awal sebelum 2 disk baru diinstallasi di system.

sh> cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
sata0/0::dsk/c1t0d0            disk         connected    configured   ok

Kita lanjut untuk rekonfigur boot proses dan updating /dev dan /devices.

sh> devfsadm -C
sh> cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
sata0/0::dsk/c1t0d0            disk         connected    configured   ok
sata0/1::dsk/c1t1d0            disk         connected    configured   ok
sata0/2::dsk/c1t2d0            disk         connected    configured   ok

Oke setelah semua persiapan selesai, kita lanjut dengan membuat RAID-1nya.

sh> format c1t1d0

lalu buat 2 partisi, satu untuk data dan satulagi untuk metadatanya disimpan, biasanya di slice 7.
Setelahnya kita salin format partisi dari disk primary ke disk secondary, dan dilanjut dengan membuat state databasenya.

sh> prtvtoc /dev/rdsk/c1t1d0s2 |fmthard -s - /dev/rdsk/c1t2d0s2
sh> metadb -a -f -c 3 c1t1d0s7 c1t2d0s7

sh> metadb
        flags           first blk       block count
     a m  pc luo        16              8192            /dev/dsk/c1t1d0s7
     a    pc luo        8208            8192            /dev/dsk/c1t1d0s7
     a    pc luo        16400           8192            /dev/dsk/c1t1d0s7
     a    pc luo        16              8192            /dev/dsk/c1t2d0s7
     a    pc luo        8208            8192            /dev/dsk/c1t2d0s7
     a    pc luo        16400           8192            /dev/dsk/c1t2d0s7

Setelah konfirm, lanjut dengan membuat raid 1 nya.

sh> metainit -f d70 1 1 c1t1d0s3
sh> metainit -f d71 1 1 c1t2d0s3
sh> metainit d69 -m d70
sh> metattach d69 d71

sh> metastat d69
d69: Mirror
    Submirror 0: d70
      State: Okay         
    Submirror 1: d71
      State: Resyncing    
    Resync in progress: 35 % done
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 4194304 blocks (2.0 GB)
 
d70: Submirror of d69
    State: Okay         
    Size: 4194304 blocks (2.0 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c1t1d0s3          0     No            Okay   Yes 
 
 
d71: Submirror of d69
    State: Resyncing    
    Size: 4194304 blocks (2.0 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c1t2d0s3          0     No            Okay   Yes

Terlihat sedang dalam proses resync (Resync in progress: 35 % done),
kita lanjut dengan membuat mount pointnya.

sh> newfs -f 4096 /dev/md/rdsk/d69
sh> mkdir /apps
sh> vi /etc/vfstab
/dev/md/dsk/d69 /dev/md/rdsk/d69 /apps ufs 2 yes -

shell> mountall
shell> df -F ufs -h|grep apps
/dev/md/dsk/d69        1.9G   2.0M   1.9G     1%    /apps

Oke lanjut dengan Unmirroringnya, biar komplit.
Lakukan “metadetach” untuk membuat one-way mirror.

sh> umount /apps
sh> metadetach d69 d71
d69: submirror d71 is detached

Verfiy…

sh> metastat d69
d69: Mirror
    Submirror 0: d70
      State: Okay         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 4194304 blocks (2.0 GB)
 
d70: Submirror of d69
    State: Okay         
    Size: 4194304 blocks (2.0 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare

Tahap akhir adalah, “metaclear” untuk meng-clear mirror dan submirrornya.

sh> metaclear -r d69
d69: Mirror is cleared
d70: Concat/Stripe is cleared
sh> metaclear d71
d71: Concat/Stripe is cleared

Jangan lupa untuk menghilangkan “/apps” dari /etc/vfstabnya.

PowerPath show “unlic” status

Hendrawan — Mon, 23 Mar 2009 13:02:32 +0000

Unlic indicates that unlicensed PowerPath is running for a CLARiiON array (no license key has been installed), Unlicensed defaults to “basic Fail/Over policy, we made change yet.

bash> powermt display dev=emcpower0a|grep policy
state=alive; policy=BasicFailover; priority=0; queued-IOs=0

bash> powermt display dev=emcpower0a
Pseudo name=emcpower0a
CLARiiON ID=CK200071500374 [SERVER]
Logical device ID=60060160F0CE1A00185D33F95722DD11 [LUN 25 SERVER]
state=alive; policy=BasicFailover; priority=0; queued-IOs=0
Owner: default=SP B, current=SP B       Array failover mode: 1
==============================================================================
---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---
###  HW Path                I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
3072 pci@8,700000/SUNW,qlc@3/fp@0,0 c5t5006016239A02677d0s0 SP A2     active  alive      0      0
3072 pci@8,700000/SUNW,qlc@3/fp@0,0 c5t5006016A39A02677d0s0 SP B2     active  alive      0      0
3074 pci@8,700000/SUNW,qlc@3,1/fp@0,0 c6t5006016339A02677d0s0 SP A3     unlic   alive      0      0
3074 pci@8,700000/SUNW,qlc@3,1/fp@0,0 c6t5006016B39A02677d0s0 SP B3     unlic   alive      0      0

Workaround
1. powermt check_registration
2. powermt set policy=co dev=all (Set the Policy to co = Clariion Optimization)
3. powermt display dev=all
4. powermt save

bash> powermt display dev=emcpower0a|grep policy
state=alive; policy=CLAROpt; priority=0; queued-IOs=0

bash> powermt display dev=emcpower0a
Pseudo name=emcpower0a
CLARiiON ID=CK200071500374 [SERVER]
Logical device ID=60060160F0CE1A00185D33F95722DD11 [LUN 25 SERVER]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP B       Array failover mode: 1
==============================================================================
---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---
###  HW Path                I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
3072 pci@8,700000/SUNW,qlc@3/fp@0,0 c5t5006016239A02677d0s0 SP A2     active  alive      0      0
3072 pci@8,700000/SUNW,qlc@3/fp@0,0 c5t5006016A39A02677d0s0 SP B2     active  alive      0      0
3074 pci@8,700000/SUNW,qlc@3,1/fp@0,0 c6t5006016339A02677d0s0 SP A3     active  alive      0      0
3074 pci@8,700000/SUNW,qlc@3,1/fp@0,0 c6t5006016B39A02677d0s0 SP B3     active  alive      0      0

Rename Volume Group on HP-UX (quick & dirty)

Hendrawan — Sun, 22 Mar 2009 10:37:32 +0000

Can you explain how to rename a volume group (VG)?, How to rename your Volume Group on HP-UX ? and many more question about how to rename the volume group. here I show you the magic of how to rename your Volume Group.

bash> bdf|grep /rdbms/oradata/a
/dev/vg07/lvol1    5144576 3515198 1527542   70% /rdbms/oradata/a

We will rename VG07 to VG20, backup your data first.

Backup VG config First

bash> vgcfgbackup /dev/vg07
Volume Group configuration for /dev/vg07 has been saved in /etc/lvmconf/vg07.conf

Ok, now deactivate the first volume group

bash> vgchange -a n /dev/vg07
Volume group "/dev/vg07" has been successfully changed.

Export Vg07 dengan nama ‘vg20.map’

bash> vgexport -v -s -m /tmp/vg20.map /dev/vg07
Beginning the export process on Volume Group "/dev/vg07".
/dev/dsk/c5t0d0
Volume group "/dev/vg07" has been successfully removed.

Create New Volume group (VG20)

bash> mkdir /dev/vg20
bash> mknod /dev/vg20/group c 64 0x1a0000

Import VG nya

bash> vgimport -v -s -m /tmp/vg20.map /dev/vg20
Beginning the import process on Volume Group "/dev/20".
Logical volume "/dev/vg20/lvol1" has been successfully created
with lv number 1.
Volume group "/dev/vg20" has been successfully created.

Last but not least, Enable the VG

bash> vgchange -a y /dev/vg20
Activated volume group
Volume group "/dev/vg20" has been successfully changed.

System Administrator Appreciation Day

Hendrawan — Fri, 25 Jul 2008 07:48:26 +0000

A sysadmin unpacked the server for this website from its box, installed an operating system, patched it for security, made sure the power and air conditioning was working in the server room, monitored it for stability, set up the software, and kept backups in case anything went wrong. All to serve this webpage

A sysadmin installed the routers, laid the cables, configured the networks, set up the firewalls, and watched and guided the traffic for each hop of the network that runs over copper, fiber optic glass, and even the air itself to bring the Internet to your computer. All to make sure the webpage found its way from the server to your computer.

A sysadmin makes sure your network connection is safe, secure, open, and working. A sysadmin makes sure your computer is working in a healthy way on a healthy network. A sysadmin takes backups to guard against disaster both human and otherwise, holds the gates against security threats and crackers, and keeps the printers going no matter how many copies of the tax code someone from Accounting prints out.

A sysadmin worries about spam, viruses, spyware, but also power outages, fires and floods.

When the email server goes down at 2 AM on a Sunday, your sysadmin is paged, wakes up, and goes to work.

A sysadmin is a professional, who plans, worries, hacks, fixes, pushes, advocates, protects and creates good computer networks, to get you your data, to help you do work — to bring the potential of computing ever closer to reality.

Happy Sysadmin Day..all of you.
http://www.sysadminday.com/