Search This Blog

Thursday, March 29, 2012

New LUN assigned to HP-Unix 11iv3 was in NO_HW status:

New LUN assigned to HP-Unix 11iv3 was in NO_HW status:

In dmesg following error messages was coming;


class : lunpath, instance 59
Evpd inquiry page 83h/80h failed or the current page 83h/80h data do not match the previous known page 83h/80h data on LUN id 0x0 probed beneath the target path (class = tgtpath, instance = 8) The lun path is (class = lunpath, instance 59).Run 'scsimgr replace_wwid' command to validate the change

class : lunpath, instance 58
Evpd inquiry page 83h/80h failed or the current page 83h/80h data do not match the previous known page 83h/80h data on LUN id 0x0 probed beneath the target path (class = tgtpath, instance = 7) The lun path is (class = lunpath, instance 58).Run 'scsimgr replace_wwid' command to validate the change

#check the lunpath number which is seens in the output it may be blocking the disk visisblity:

please run below command :
#scsimgr replace
scsimgr -f replace_wwid -C lunpath -I   ??? <whatt you see in dmesg>



scsimgr replace_wwid -C lunpath -I 58
scsimgr replace_wwid -C lunpath -I 59


#insf
#ioscan -fnC disk   
#dmesg

Friday, January 27, 2012

Changing the disk-naming scheme

You can either use enclosure-based naming for disks or the operating system’s naming scheme. VxVM commands display device names according the current naming scheme.
The default naming scheme is enclosure-based naming (EBN). When you install or upgrade a Storage Foundation product, the naming scheme is set to enclosure-based naming, with the following exception. If you explicitly set the naming scheme for an existing installation to operating system-based naming, the setting is preserved when you upgrade. That is, if you used the vxddladm set namingscheme=osn command for the existing installation, the upgraded 5.1 product retains the operating system-based naming.

To change the disk-naming scheme

Select Change the disk naming scheme from the vxdiskadm main menu to change the disk-naming scheme that you want VxVM to use. When prompted, enter y to change the naming scheme.
Alternatively, you can change the naming scheme from the command line. Use the following command to select enclosure-based naming:

# vxddladm set namingscheme=ebn [persistence={yes|no}] \

[use_avid=yes|no] [lowercase=yes|no]
Use the following command to select operating system-based naming:

# vxddladm set namingscheme=osn [persistence={yes|no}] \

[lowercase=yes|no]
The optional persistence argument allows you to select whether the names of disk devices that are displayed by VxVM remain unchanged after disk hardware has been reconfigured and the system rebooted. By default, enclosure-based naming is persistent. Operating system-based naming is not persistent by default.

By default, the names of the enclosure are converted to lowercase, regardless of the case of the name specified by the ASL. The enclosure-based device names are therefore in lower case. Set the lowercase=no option to suppress the conversion to lowercase.

For enclosure-based naming, the use_avid option specifies whether the Array Volume ID is used for the index number in the device name. By default, use_avid=yes, indicating the devices are named as enclosure_avid. If use_avid is set to no, DMP devices are named as enclosure_index. The index number is assigned after the devices are sorted by LUN serial number.
The change is immediate whichever method you use.

Saturday, September 24, 2011

When you try to shrink Volume/File system using '-' sign in the command as follows, it results in an error..

When you try to shrink Volume/File system using '-' sign in the command as follows, it results in an error..


#/etc/vx/bin/vxresize -g DG Volume_Name -Size
E.g. #/etc/vx/bin/vxresize -g testdg testvol -2g
#/etc/vx/bin/vxresize -g testdg testvol -2g
vxresize: invalid option -- 2
VxVM vxresize INFO V-5-1-10092 usage: vxresize [-hHvMDxsnbf] [-F fstype] [-g diskgroup] [-t tag] [-o verify|override] volume length [media...]


Since '-2g' starts with '-' character, the standard UNIX getopt will treat it as an option.
Resolution:
In order to tell getopt(3) to terminate the option scanning, you have to specify '--'.


#/etc/vx/bin/vxresize -g DG Volume_Name -- -Size
E.g. #/etc/vx/bin/vxresize -g testdg testvol -- -2g

Monday, August 22, 2011

fsadm: You don't have a license to run this program


Error Message: While extending the file system /tmp on xyz server, I was getting the following error message regarding licenses of Online JFS

xyz:/root#fsadm -b 1088M /tmp
fsadm: /etc/default/fs is used for determining the file system type
fsadm: You don't have a license to run this program

Checking the Valid License Key on the server:
xyz:/root#/usr/sbin/vxlicrep -e

VERITAS License Manager vxlicrep utility version 3.02.006
Copyright (C) 1996-2004 VERITAS Software Corp. All Rights reserved.

Creating a report on all VERITAS products installed on this system

vxlicrep ERROR V-21-3-1003 There are no valid VERITAS License keys installed in the system.

Logged in to another server called abcd:
abcd:/home/root # /usr/sbin/vxlicrep -e

VERITAS License Manager vxlicrep utility version 3.00.007
Copyright (C) VERITAS Software Corp 2002. All Rights reserved.

Creating a report on all VERITAS products installed on this system

 -----------------***********************-----------------

   License Key                         = 401441sfdasdfsaf795229591636651
   Product Name                        = VERITAS Volume Manager
   Lic Key Lib Ver                     = ELM
   Key                                 = Invalid,  Expired
   License Type                        = DEMO
   Demo End Date                       = Sun Jul 15 10:00:00 2007
   Site License                        = YES

Features :=
   VxVM                                = Enabled


 -----------------***********************-----------------

   License Key                         = 010afdsafasdf5889805115946529
   Product Name                        = VERITAS File System
   Lic Key Lib Ver                     = ELM
   License Type                        = PERMANENT
   Site License                        = YES

Features :=
   HP_OnlineJFS                        = Enabled


abcd:/home/root # vxlicense -p vxlicrep

vrts:vxlicense: INFO: Feature name: VxVM [95]
vrts:vxlicense: INFO: Number of licenses: 1 (non-floating)
vrts:vxlicense: INFO: Expiration date: Sun Jul 15 10:00:00 2007 (1499.2 days ago)
vrts:vxlicense: INFO: Release Level: 25
vrts:vxlicense: INFO: Machine Class: All
vrts:vxlicense: INFO: Site ID: 0

vrts:vxlicense: INFO: Feature name: HP_OnlineJFS [50]
vrts:vxlicense: INFO: Number of licenses: 1 (non-floating)
vrts:vxlicense: INFO: Expiration date: No expiration date
vrts:vxlicense: INFO: Release Level: 22
vrts:vxlicense: INFO: Machine Class: All
vrts:vxlicense: INFO: Site ID: 0

Here we can see that there is a valid license in the server abcd with no expiration date:
Installing the Same License key on xyz
xyz:/root#vxlicinst -k 010449565889805115946529

VERITAS License Manager vxlicinst utility version 3.02.006
Copyright (C) 1996-2004 VERITAS Software Corp. All Rights reserved.
License key successfully installed in /etc/vx/licenses/lic/010sfasdf565889805115946529.vxlic

xyz:/root#/usr/sbin/vxlicrep -e

VERITAS License Manager vxlicrep utility version 3.02.006
Copyright (C) 1996-2004 VERITAS Software Corp. All Rights reserved.

Creating a report on all VERITAS products installed on this system

 -----------------***********************-----------------

   License Key                         = 010dfasdfsa5889805115946529
   Product Name                        = VERITAS File System
   Lic Key Lib Ver                     = ELM
   License Type                        = PERMANENT
   Site License                        = YES

 Features :=
   HP_OnlineJFS                        = Enabled

Still we are getting error:
xyz:/root#fsadm -b 1088M /tmp
fsadm: /etc/default/fs is used for determining the file system type
fsadm: You don't have a license to run this program

We need to enable the License:
xyz:/root#/sbin/fs/vxfs/vxenablef -a

After Enabling the License:
xyz:/root#fsadm -b 1088M /tmp
fsadm: /etc/default/fs is used for determining the file system type
vxfs fsadm: /dev/vg00/rlvol4 is currently 1048576 sectors - size will be increased