Archive

Archive for May, 2011

Symantec Netbackup 7.1 reference manual(commands) download

May 30th, 2011 No comments

Extend filesystem in vxvm which connects to SAN fibre channel storage

May 28th, 2011 No comments

Firstly, please refer to http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Online_Storage_Reconfiguration_Guide/scanning-storage-interconnects.html for some pre-checking, like memory usage, sync etc.
Then, we should scan for new disk connected to hba one by one(issue_lip, Scenario:fabric on Linux with Emulex hbas), we should check dmpnodes are ALL in ENABLED state before moving on to another hba. This is because when scanning for new disks, we expect to result in disabling paths on that controller – and moving on only when the paths are confirmed enabled again. And during all procedures, tail -f /var/log/messages would help.

1) Checked the messages file for any existing issues. Identified and eliminated concerns of I/O error messages which have occured for some time:
May 29 04:11:05 testserver01 kernel: end_request: I/O error, dev sdft, sector 0^M
May 29 04:11:05 testserver01 kernel: Buffer I/O error on device sdft, logical block 0^M
May 29 04:11:05 testserver01 kernel: end_request: I/O error, dev sdft, sector 0^M
/var/log/messages.1:May 27 22:48:04 testserver01 kernel: end_request: I/O error, dev sdjt, sector 8
/var/log/messages.1:May 27 22:48:04 testserver01 kernel: Buffer I/O error on device sdjt3, logical block 1
2)Saved some output for comparison later:
syminq -pdevfile > /var/tmp/syminq-pdevfile-prior
We expected device as hyper 2C27 so I looked for this device in the output and, as expected, did not find it.
vxdisk -o  alldgs list > /var/tmp/vxdisk-oalldgs.list
3)Checked the current state of the vm devices dmp subpaths:
for disk in `vxdisk -q list | awk '{print $1}'`
do
echo $disk
vxdmpadm getsubpaths dmpnodename=${disk}
done | tee -a /var/tmp/getsubpaths.out
Checked the output to make sure all but the root disk(expected) had two enabled paths: NAME         STATE[A]   PATH-TYPE[M] CTLR-NAME  ENCLR-TYPE   ENCLR-NAME    ATTRS
================================================================================
cciss/c0d0   ENABLED(A)   -          c360       OTHER_DISKS  OTHER_DISKS
sda
NAME         STATE[A]   PATH-TYPE[M] CTLR-NAME  ENCLR-TYPE   ENCLR-NAME    ATTRS
================================================================================
sda          ENABLED(A)   -          c0         EMC          EMC0             -
sddc         ENABLED(A)   -          c1         EMC          EMC0             -
sdae
NAME         STATE[A]   PATH-TYPE[M] CTLR-NAME  ENCLR-TYPE   ENCLR-NAME    ATTRS
================================================================================
sdeh         ENABLED(A)   -          c1         EMC          EMC0             -
sdp          ENABLED(A)   -          c0         EMC          EMC0             -
sdaf
NAME         STATE[A]   PATH-TYPE[M] CTLR-NAME  ENCLR-TYPE   ENCLR-NAME    ATTRS
================================================================================
sdej         ENABLED(A)   -          c1         EMC          EMC0             -
sdq          ENABLED(A)   -          c0         EMC          EMC0             -
sdai
NAME         STATE[A]   PATH-TYPE[M] CTLR-NAME  ENCLR-TYPE   ENCLR-NAME    ATTRS
================================================================================
sdai         ENABLED(A)   -          c0         EMC          EMC0             -
sdfr         ENABLED(A)   -          c1         EMC          EMC0             -
... etc
Ran other commands like
vxdg list (to ensure all diskgroups where enabled)
df -k (no existing filesystem problems)

NOTE:

You can get your  <dmpnodename>  by running:
# vxdisk path | grep emcC5D3
Note, it is listed as DANAME (and not SUBPATH)
4)Tried to scan the first scsi bus
root@testserver01# pwd
/sys/class/scsi_host/host0
root@testserver01# echo '- - -' > scan
Waited to see if the scan would detect any new devices. Monditor the messages log for any messages relating to the scan.
Checked output of syminq and checked the subpaths for each dmpnode as above. All remained ENABLED and no change.
5. Moved on to issuing a force lip to the fibre path
a. issuing the forcelip
root@testserver01# pwd
/sys/class/fc_host/host0
root@testserver01# echo "1" > issue_lip
The command returned and I monitored the messages log. Waited for the disabled path messages to appear (as expected):
May 31 02:44:49 testserver01 kernel: VxVM vxdmp V-5-0-112 disabled path 8/0x80 belonging to the dmpnode 201/0x540
May 31 02:44:49 testserver01 kernel: VxVM vxdmp V-5-0-112 disabled path 67/0xa0 belonging to the dmpnode 201/0x5f0
May 31 02:44:49 testserver01 kernel: VxVM vxdmp V-5-0-112 disabled path 67/0xb0 belonging to the dmpnode 201/0x6c0
May 31 02:44:49 testserver01 kernel: VxVM vxdmp V-5-0-112 disabled path 128/0x60 belonging to the dmpnode 201/0x160
... etc
I checked the output of vxdmpadm getsubpaths for each device to confirm the paths had gone offline:
NAME         STATE[A]   PATH-TYPE[M] CTLR-NAME  ENCLR-TYPE   ENCLR-NAME    ATTRS
================================================================================
sddw         ENABLED(A)   -          c0         EMC          EMC0             -
sdiv         ENABLED(A)   -          c1         EMC          EMC0             -
sddm
NAME         STATE[A]   PATH-TYPE[M] CTLR-NAME  ENCLR-TYPE   ENCLR-NAME    ATTRS
================================================================================
sdbg         DISABLED     -          c0         EMC          EMC0             -
sdgq         ENABLED(A)   -          c1         EMC          EMC0             -
sddn
NAME         STATE[A]   PATH-TYPE[M] CTLR-NAME  ENCLR-TYPE   ENCLR-NAME    ATTRS
================================================================================
sddz         ENABLED(A)   -          c0         EMC          EMC0             -
sdix         ENABLED(A)   -          c1         EMC          EMC0             -
sddo
NAME         STATE[A]   PATH-TYPE[M] CTLR-NAME  ENCLR-TYPE   ENCLR-NAME    ATTRS
================================================================================
sdbh         DISABLED     -          c0         EMC          EMC0             -
sdgr         ENABLED(A)   -          c1         EMC          EMC0             -
sddp

Not all the paths were affected at once - a few minutes wait confirms they all go down as expected. The secondary path remains ENABLED, as expected.
I waited a little longer to get some estimation for how long all the paths took to go down - estimate was around 4 minutes.
b. Rescaning the fibre channel.
Before moving to the other path I get volume manager to rescan the device bus to trigger dmp to wake up the DISABLED paths.
root@testserver01# vxdisk scandisks fabric
I wait until all the primary paths become ENABLED again, checking for the dmp enabled messages in the messages log:
May 31 02:49:43 testserver01 kernel: VxVM vxdmp V-5-0-148 enabled path 129/0x90 belonging to the dmpnode 201/0x10
May 31 02:49:43 testserver01 kernel: VxVM vxdmp V-5-0-148 enabled path 129/0x50 belonging to the dmpnode 201/0x20
May 31 02:49:43 testserver01 kernel: VxVM vxdmp V-5-0-148 enabled path 128/0x40 belonging to the dmpnode 201/0x30
May 31 02:49:43 testserver01 kernel: VxVM vxdmp V-5-0-148 enabled path 129/0x30 belonging to the dmpnode 201/0x40
.... etc
And also check vxdmpadm getsubpaths command until all primary paths return to ENABLED state.
I did the same for the second host controlller at /sys/class/fc_host/host1
6)Checking for new disk device:
Try syminq and/or symcfg disco

After this, you can extend vxvm filesystem to the size you want, and re-import devices after that. Please refer to http://www.doxer.org/extending-filesystems-on-lvm-vxvmvxfs-how-to/ for more details.

panic cpu thread page_unlock is not locked issue when using centos xen to create solaris 10

May 25th, 2011 No comments

Don't panic.

You can allocate more memory to solaris virtual machine(like 1024Mb) and try again.

In the Sun Forums thread, they say that 609 MB is the lowest you can go. You can give it a little more memory size if allowed.

Use xming, xshell, putty, tightvnc to display linux gui on windows desktop (x11 forwarding when behind firewall)

May 24th, 2011 10 comments

Q1:How do I run X11 applications through Xming when there's no firewall?

Step 1 - Configure Xming

Let's assume that you want to run xclock on solaris/linux server 192.168.0.3, and want the gui display on your pc whose ip is 192.168.0.4.

Firstly, download xming, install it on your windows pc system.

You can go to http://sourceforge.net/projects/xming/files/ to download.

After this, you need set 192.168.0.3(linux/solaris) to the allowed server list on your windows. Edit X0.hosts which locates at the installation directory of xming(For example, C:\Program Files\Xming\X0.hosts), add a new entry in it:192.168.0.3, the ip address of linux/solaris that you want to run x11 utility from.

Then, restart xming(C:\Program Files\Xming\xming.exe) on your windows.

Step 2 - Connect to remote host, configure it, and run X11 application

Log in linux/solaris server 192.168.0.3. Set environment variable DISPLAY to the ip address of your windows, and append a :0 to it:

#export DISPLAY=192.168.0.4:0

Then you must allow X11 forwarding in sshd configuration file. That is, set X11Forwarding to yes in /etc/ssh/sshd_config and restart your sshd daemon.

 And on solaris/linux server(192.168.0.3), run a X11 programe, like

/usr/bin/xclock #or /usr/openwin/bin/xclock on solaris

You will then see a clock gui pop up in your windows pc.

PS: You may need install xorg-x11-xauth on remote host sometimes if you met error starting up xclock

Q2:How do I run X11 applications from remote host when that host is behind firewall?

If the remote host is behind firewall, then the method above will not work as the communication will be blocked if no firewall exception implemented. To run X11 applications from remote host behind firewall, you can follow steps below:

Step 1 - Configure Xming

This step is the same as step 1 in Q1, but I'll paste it here for your convenience:

Let's assume that you want to run xclock on solaris/linux server 192.168.0.3, and want the gui display on your pc whose ip is 192.168.0.4.

Firstly, download xming, install it on your windows pc system.

You can go to http://sourceforge.net/projects/xming/files/ to download.

After this, you need set 192.168.0.3(linux/solaris) to the allowed server list on your windows. Edit X0.hosts which locates at the installation directory of xming(For example, C:\Program Files\Xming\X0.hosts), add a new entry in it:192.168.0.3, which is the ip address of linux/solaris that you want to run x11 utility from.

Then, restart xming(C:\Program Files\Xming\xming.exe) on your windows.

Step 2 - Configure X11 forwarding on putty/xshell

For Xshell:

After entering remote hostname and log on username on Xshell, now nn the Tunneling tab of Advanced SSH Options dialog box, check "Forward X11 Connections to:" and click on "X DISPLAY:" and enter "localhost:0.0" next to it.

xshell_x11_forwarding

For Putty:

After entering remote hostname and log on username on putty, now unfold "Connection" on the left pane, unfold "SSH, and then select "X11". Later, check "Enable X11 forwarding" and enter "localhost:0.0" next to "X display location".

putty_x11_forwarding

Step 3 - Connect to remote host, configure it, and run X11 application

Log in linux/solaris server 192.168.0.3. Set environment variable DISPLAY to localhost:0

#export DISPLAY=localhost:0 #not 192.168.0.4:0 any more!

Then you must allow X11 forwarding in sshd configuration file. That is, set X11Forwarding to yes in /etc/ssh/sshd_config and restart your sshd daemon.

And on solaris/linux server(192.168.0.3), run a X11 programe, like

/usr/bin/xclock #or /usr/openwin/bin/xclock on solaris

You will then see a clock gui pop up in your windows pc.

PS: You may need install xorg-x11-xauth on remote host sometimes if you met error starting up xclock

Q3:How do I connect to remote host through vnc client(such as tightvnc)?

In general, you need first install vnc-server on remote host, then configure vnc-server on remote host. Later install tightvnc client on your PC and connect to remote host.

I'll show details about install vnc-server on remote host below:

yum install gnome*

yum grouplist
yum groupinstall "X Window System" -y
yum groupinstall "GNOME Desktop Environment" -y
yum groupinstall "Graphical Internet" -y
yum groupinstall "Graphics" -y
yum install vnc-server
echo "DESKTOP="GNOME"" > /etc/sysconfig/desktop
sed -i.bak ‘/VNCSERVERS=/d’ /etc/sysconfig/vncservers
echo "VNCSERVERS=\"1:root\"" >> /etc/sysconfig/vncservers

mkdir -p /root/.vnc
vi xstartup

#!/bin/sh

# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
#xterm -geometry 80×24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#twm &
gnome-terminal &
gnome-session &

vncpasswd ~/.vnc/passwd #set password
chmod 755 ~/.vnc ; chmod 600 ~/.vnc/passwd ; chmod 755 ~/.vnc/xstartup

chkconfig –level 345 vncserver on
chkconfig –list | grep vncserver
service vncserver start

Q4:What if I want one linux box acting as X server, another linux box as X client, and I'm not sitting behind the Linux X server(means I have to connect to the Linux X server through VNC)?

This may sound complex, but it's simple actually.

First, you need install vnc-server on the linux X server following steps in above "Q3: How do I connect to remote host through vnc client(such as tightvnc)?".

Second, install tightvnc viewer on your windows box you sit behind and connect to the linux X server through it(xxx.xxx.xxx.xxx:1 or example). Run xhost + <linux X client> to enable access to X server.

Then, on the linux X client, export DISPLAY to xxx.xxx.xxx.xxx:1 which is the linux X server. Run a X program such as xclock, and you'll see the clock displaying on the X interface on your windows tightvnc viewer.

PS:

1.You can change vncserver’s resolution through editing /usr/bin/vncserver, change the default $geometry = "1024×768″ to any one you like, for example $geometry = "1600×900″. You can also control each user’s vnc resolution setting through adding line like "VNCSERVERARGS[1]="-geometry 1600×900″" in /etc/sysconfig/vncservers

2.For vnc server on ubuntu, you can refer to http://www.doxer.org/ubuntu-server-gnome-desktop-and-vncserver-configuration/

Analysis of output by solaris format -> verify

May 21st, 2011 No comments

Here's the output of format -> verify command in my solaris10:

format> verify

Primary label contents:

Volume name = < >
ascii name =
pcyl = 2609
ncyl = 2607
acyl = 2
bcyl = 0
nhead = 255
nsect = 63
Part Tag Flag Cylinders Size Blocks
0 root wm 1 - 1306 10.00GB (1306/0/0) 20980890
1 var wm 1307 - 2351 8.01GB (1045/0/0) 16787925
2 backup wu 0 - 2606 19.97GB (2607/0/0) 41881455
3 stand wm 2352 - 2606 1.95GB (255/0/0) 4096575
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 unassigned wm 0 0 (0/0/0) 0

Now, let's give it an analysis:

  • Part

Solaris x86 has 9 slices for a disk, and for 8th and 9th, they're preserved by solaris.

  • Tag

This is used to indicate the purpose of the slice. Possible values are:

unassigned, boot, root, swap, usr, backup, stand, home, and public, private(The latter two are used by Sun StorEdge).

  • Flag

wm - this slice is writable and mountable.

wu - this slice is writable and unmountable.

rm - this slice is readable and mountable.

ru - this slice is readable and unmountable.

  • Cylinders

This part shows the start and end cylinder number of the slice.

  • Size

The size of the slice.

  • Blocks

This shows the number of cylinders and sectors of the slice.

Now, let's create a slice and mount the filesystem:

root@test / # format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
0. c1t0d0
/pci@0,0/pci15ad,1976@10/sd@0,0
1. c1t1d0
/pci@0,0/pci15ad,1976@10/sd@1,0
Specify disk (enter its number): 1 #select this disk
selecting c1t1d0
[disk formatted]

FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
! - execute , then return
quit
format> partition #select partition to check and create new slice

PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
! - execute , then return
quit
partition> print #check slice topology
Current partition table (original):
Total disk cylinders available: 2607 + 2 (reserved cylinders)

Part Tag Flag Cylinders Size Blocks
0 root wm 1 - 1306 10.00GB (1306/0/0) 20980890
1 var wm 1307 - 2351 8.01GB (1045/0/0) 16787925
2 backup wu 0 - 2606 19.97GB (2607/0/0) 41881455
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 unassigned wm 0 0 (0/0/0) 0

partition> 3 #select an unassigned slice. It will be /dev/rdsk/c1t1d0s3 after saving to format.dat
Part Tag Flag Cylinders Size Blocks
3 unassigned wm 0 0 (0/0/0) 0

Enter partition id tag[unassigned]: stand
Enter partition permission flags[wm]:
Enter new starting cyl[1]: 2352
Enter partition size[0b, 0c, 2352e, 0.00mb, 0.00gb]: $
partition> label #write label to disk
Ready to label disk, continue? y

partition> name #name the current table
Enter table name (remember quotes): hah

partition> quit

FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
! - execute , then return
quit
format> save #save new disk/partition definitions
Saving new disk and partition definitions
Enter file name["./format.dat"]:
format> quit

root@test / # newfs /dev/rdsk/c1t1d0s3 #create filesystem on newly created slice
newfs: construct a new file system /dev/rdsk/c1t1d0s3: (y/n)? y
Warning: 1474 sector(s) in last cylinder unallocated
/dev/rdsk/c1t1d0s3: 4096574 sectors in 667 cylinders of 48 tracks, 128 sectors
2000.3MB in 42 cyl groups (16 c/g, 48.00MB/g, 11648 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
3149856, 3248288, 3346720, 3445152, 3543584, 3642016, 3740448, 3838880,
3937312, 4035744
root@test / # fstyp /dev/dsk/c1t1d0s3 #check the filesystem type
ufs
root@test / # mkdir /hah
root@test / # mount /dev/dsk/c1t1d0s3 /hah #mount filesystem
root@test / # cd /hah/
root@test hah # touch aa #create a file to have a test
root@test hah # ls #finished, congratulations!
aa lost+found

Netbackup wrong report – files not backuped whilst netbackup reported already backuped

May 20th, 2011 No comments

Netbackup reported:

The following "sns*" files in /ftp/ftpst/datain/sns_a/success have been archived:/ftp/ftpst/datain/sns_a/success/sns_closed_09042011_180000_2.data/ftp/ftpst/datain/sns_a/success/sns_closed_09042011_180000_1.data

However, these files were still within the directories.

Here goes my comprehension:

We have had similar issues with other hosts which turns out to be more of an issue in the reporting of the script. It reports on the things it has selected for archiving rather than what has successfully been archived.

If netbackup does not manage to backup the files to tape because e.g. the drives are too busy then it doesn't delete the files but there is nothing in the script to report that this has occurred.

Categories: Hardware, Storage Tags:

dmx srdf failover procedure

May 17th, 2011 No comments

1.Verify that all devices listed by the above command are in the “Synchronized” state:
# symrdf –g dg01 query
2.Once all devices are confirmed as being “Synchronized”, then issue the command to failover:
# symrdf –g dg01 failover -establish
Once complete, the storage status can be checked again:
# symrdf –g livedsms_PRD query
NOTE: Do NOT trust any symcli output on any Solaris 2.6 host when working with the DMX-4.
IMPORTANT: ensure that the Symmetrix device group contains ALL devices:
vxdisk –g dg01 list #From a recent Sun Explorer

3.Import Storage
The vxdg should be imported as per normal:
# vxdctl enable
# vxdg –Cf import dg01
# vxvol –g dg01 startall
# mountall –F vxfs

4.Verify Storage
Ensure that the storage imported by the above commands appears to be correct by examining the output of the following commands:

# df –klFvxfs
# vxprint –g dg01 –v

Categories: Hardware, Storage Tags:

Steps for upgrading milestone to version 2.3

May 16th, 2011 No comments

Firstly, please refer to this page for prerequisite:

Motorola milestone(xt702) rooted and busybox installation

After reading that article through, you can do the following steps:

1.Go to Recovery Console:    wipe data/factory reset    wipe cache partitionThen, shutdown milestone.

2.Run RSDLite on your pc, select Milestone_2.2.1_UK_Package.sbf.

3.Goto Bootloader, connect your milestone and your pc, and click "start". When this finished, reboot your milestone.

4.Now put Milestone_V2.3.2_MuzisoftUpdate_B6.2-SignFile.zip to OpenRecovery\updates. And then put OpenRecovery and update.zip to /sdcard. Wipe again(Refer to step 1). In Recovery Console, focus on "apply sdcard:update.zip" and type OK button. Then, select root phone. After that, reboot system. Then you'll find your system already been rooted. Then, select Milestone_V2.3.2_MuzisoftUpdate_B6.2-SignFile.zip.

5.Wipe again and reboot milestone. You'll find your system now is 2.3!

Categories: Misc Tags:

Motorola milestone(xt702) rooted and busybox installation

May 16th, 2011 No comments

1.Download update.zip & Android SDK & busybox & Motorola ADB driver & RSDLite & OpenRecovery

f
2.You need your system rooted for these operations. You can download update.zip here, put it in your sdcard. Go to Recovery Console. To go to Recovery Console, you need firstly know your bootloader version. Press upper arrow of the four-directions key on your keyboard and booting button to boot your system. Then you can see the version of system bootloader.I.If the version is 90.78, you need press x+booting button, when there appears a triangle, press upper key of voice control and snapshot button to go to Recovery Console.II.If the version is 90.73/90.74, press snapshot button and booting button, when there appears a triangle, press upper key of voice control and snapshot button to go to Recovery Console.In Recovery Console, focus on "apply sdcard:update.zip" and type OK button. Then, select root phone. After that, reboot system. Then you'll find your system already been rooted.

3.Install Motorola ADB driver, after that, connect your usb to your pc(windows media sync). Setting your milestone like this:    Settings -> Applications -> Development -> check USB Debugging  Then, you'll find Motorola A853 info on your pc.

4.Install Android SDK to C:\android, here goes the layout:    C:\android        add-ons        platforms        SDK Readme.txt        SDK Setup.exe        tools5.Run cmd in your pc, unzip busybox and put it in  :\android\tools, it will be C:\android\tools\busybox.In the cmd console, run the following commands:    cd c:\android\tools    adb push c:\android\tools\busybox /sdcard/busybox #This may take several minutes to complete.Now, run:    adb shellCongratulations! You can now operates in your milestone!And, now you can try su to root:    suIf not successful, you'll need root your system again. Please refer to step 2.

Categories: Misc Tags:

How to Reload IAM DNS Configuration

May 13th, 2011 No comments

Firstly, backup your zone file under /apps/bind/var/named/master:

#cp -R /apps/bind/var/named/master /apps/bind/var/named/master_bak

Now, run command to reload:

#rndc -k /apps/bind/etc/rndc.key

PS:

Here's the man page for rndc, rndc.conf, named, named.conf, ndc:

http://www.linuxmanpages.com/man8/rndc.8.php

And, for name service cache daemon, you man refer to nscd man page.

Categories: IT Architecture, Linux, Systems Tags:

Clear error logs from fma before obu firmware patching

May 12th, 2011 No comments

1. Clear logs from fma:
To clear the FMA faults and error logs from Solaris:
a) Show faults in FMA
# fmadm faulty
NOTE: Do not use 'fmadm faulty -a' in this step. When you specify the -a optionall resource information cached by the Fault Manager is listed, includingfaults, which have already been corrected or where no recovery action is needed(see 'fmadm' man page). The listing also include information for resources,that may no longer be present in the system
b) For each fault UUID listed in the 'fmadm faulty' run
# fmadm repair <uuid># fmadm faulty (to make sure the output is clean after repair)
c) Clear ereports and resource cache
# cd /var/fm/fmd# rm e* f* c*/eft/* r*/*
d) Reset the fmd serd modules
# fmadm reset cpumem-diagnosis# fmadm reset cpumem-retire# fmadm reset eft# fmadm reset io-retire
e) Reboot the system
To clear the FMA faults and error logs from Solaris without rebooting the system:
a) Stop the fmd:
# svcadm disable -s svc:/system/fmd:default
b) Remove all files from the FMA log directories. This is very specific to the files found in the FMS directories, all directories must be left intact.
# cd /var/fm/fmd
# find /var/fm/fmd -type f -exec ls {} \;
c) Check that only files within the /var/fm/fmd directory are identified then replace the ls with rm to remove them.
# find /var/fm/fmd -type f -exec rm {} \;
d) Restart fmd after the files are removed
# svcadm enable svc:/system/fmd:default
For more information about clearing logs please see Doc ID 1004229.1
2. Upgrade the SP and OBP firmware by installing patch 145673-02.

About how to do firmware patch, please refer to http://www.doxer.org/obu-firmware-patching/

Recovering from temporary loss of san storage

May 9th, 2011 No comments

Typically, you will see entries in the messages file relating to  some fibre channel paths being offline and possibly coming online.
If all paths to the san storage are lost, then veritas will disable the disk groups, however the filesystems will still be mounted.

df -k will return messages like  "Cannot stat filesystem"

To recover, you need to

1/ Unmount any filesystems that are mounted from the disk groups that are disabled.
You may find that there are processes that were trying to write to files in these filesystems and that you cannot unmount. You will probably have to kill the processes. the only thing to be careful of is websphere processes. If its a websphere system that is impacted, call the websphere team out first before starting to unmount / kill processes etc.
for redhat systems, the umount is the opposite of solaris, so do a lazy umount of the parent directory
so, for /apps/test/results
umount -l /apps/test
should take care of it.

2/ Once all filesystems that are affected have been unmounted, you can deport the vxdgs
3/ Import the vxdgs
From the vxdg man page
When a disk group is imported, all  disks  in  the               disk  group  are  stamped with the host's host ID.               Typically, a disk group cannot be imported if  any               of  its disks are stamped with a non-matching host               ID.  This provides a sanity check in  cases  where               disks can be accessed from more than one host.
If it is certain that a disk  is  not  in  use  by               another host (such as because a disk group was not               cleanly deported), the -C option can  be  used  to               clear  the  existing  host  ID on all disks in the               disk group as part of the import.  A host  ID  can               also be cleared using vxdisk clearimport.

4/ Check volume status with vxprint -Ath and start the volumes

5/ Mount the filesystems either from entries in /etc/vfstab or /etc/fstab or if its VCS cluster then use vcs to bring mount points only online.
For any databases, eg oracle, make sure things like /apps/ora are mounted before you try to mount the database filesystems, otherwise there is no orahome dbs will not start

6/ If its databases, then talk to the dbas before starting any of the services. they may want to run some checks before starting databases.
7/ Start any services that need to be started, either under vcs or manually from start script. You may need help from the applicqation support team.

Categories: Hardware, Storage Tags:

cdsdisk in vxvm

May 9th, 2011 No comments

Confused by "auto:cdsdisk" from outputs of vxdisk list?

For a disk to be accessible by multiple platforms, the disk must be consistently recognized by the platforms, and all platforms must be capable of performing I/O on the disk.

CDS disks contain specific content at specific locations to identify or control access to the disk on different platforms.

The same content and location are used on all CDS disks, independent of the platform on which the disks are initialized.

Categories: Hardware, Storage Tags:

Description of the Solaris Boot Archives bootadm

May 7th, 2011 No comments

Please download it here:
solaris10-boot-archive (bootadm, failsafe)

com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeErro r: Unable to start the CoordinatorComponentImpl

May 6th, 2011 No comments

When I tried to start nodeagent and app server of websphere, it said in /apps/WebSphere/Profiles/Node-stage01-04/logs/nodeagent/SystemErr.log:

[06/05/11 00:17:36:556 BST] 0000000a SystemErr     R com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeErro
r: Unable to start the CoordinatorComponentImpl

Then, I found this page:http://www-01.ibm.com/support/docview.wss?uid=swg21293285

I tried to look for RMM jar file, but failed. There's no this file under install_root.

Then, I re-run the startNode.sh for twice, magiccally, this resolved itself. Now the nodeagent and app server are both booting themselves ok.

Weird!

 

remove mnt resource of vcs

May 3rd, 2011 No comments

Target: remove mnt_prd-ora-grdctl from group SG_dbPRD

Here is the steps:

haconf -makerw
hares -delete mnt_prd-ora-grdctl
haconf -dump -makero