Changing disk ownership on Netapp cluster

Change to special advanced mode
FILER1> priv set advanced
Warning: These advanced commands are potentially dangerous; use
them only when directed to do so by NetApp personnel.

Show UNOWNED disks
FILER1*> disk show -n
disk show: No disks match option -n.

Turn off auto disk ownership
FILER1*> options disk.auto_assign off

Remove ownership on disk
FILER1*> disk remove_ownership 0a.80
Disk 0a.80 will have its ownership removedVolumes must be taken offline. Are all impacted volumes offline(y/n)?? y

Show UNOWNED disks
FILER1*> disk show -n
DISK OWNER POOL SERIAL NUMBER
------------ ------------- ----- -------------
0a.80 Not Owned NONE 3QQ1JM8K00009951WAX4

To change disk ownership to FILER2
FILER2> priv set advanced

Assign disks to FILER2
FILER2*> disk assign all

Turn ON auto disk ownership again on FILER1
FILER1*> options disk.auto_assign on

To get out of advanced mode
FILER1*> priv set
FILER2*> priv set

Change NetApp disk ownership

Changing Disk Ownership

All current NetApp storage controller systems can assume ownership of any disks it can see regardless of physical cabling through the use of software based ownership. This gives you flexibility in provisioning disks in a clustered environment. Changing ownership used to require fighting with the disk reassign command or downtime to go into maintenance mode. A little known option to the disk assign command will allow you to change ownership without taking downtime.



Examples

controller1> disk assign –s unowned 0a.23 - remove ownership on system that owns the disk (controller1).
controller2> disk show –n - the disk shows up as unowned with the physical address it has on controller2
controller2> disk assign 0b.23 - take ownership of the unowned disk on the partner system


What It Means To You

Before software disk ownership, you had to take downtime to physically move disks from one cluster partner to another to expand a fast growing aggregate or to provide another spare drive. With the –s unowned option you can reassign ownership of a spare disk without taking downtime. This also makes reassignment of disks on a new FAS2050, 3140 and 3170 cluster easier (on power up, these systems which share a single chassis have a tendancy to randomly take possession of internal SAS/SATA disks in a higgledy-piggledy manner ).

How do I subscribe to the Optional or Supplementary channels in RHN Classic ?

If using Red Hat Network (RHN) Classic

• Log into the Customer Portal at https://access.redhat.com (as a user with Organization Administrator role).
• On the Subscriptions main menu tab, select RHN Classic > Registered Systems
• Choose the relevant system in the system list.
• Click on Alter Channel Subscriptions.
• Select the RHN Tools for RHEL5/6, Server/Workstation Optional for RHEL5/6 or **Optional Productivity Apps (RHEL5) channel for Optional, or select the RHEL Server/Workstation Supplementary (RHEL6) or RHEL Supplemental (RHEL5) channel for Supplementary.
• Click the Change Subscriptions button at the bottom of the page.

Red Hat Enterprise Linux 6.3 registration is failing with "ImportError: /usr/lib64/python2.6/site-packages/_xmlplus/parsers/pyexpat.so: symbol XML_SetHashSalt, version EXPAT_2_0_1_RH not defined in file libexpat.so.1 with link time reference"

Issue

Unable to register system when trying to execute rhn_register


Environment

Red Hat Enterprise Linux 6.3
python-2.6.6-29.el6_2.2.x86_64.rpm
python-libs-2.6.6-29.el6_2.2.x86_64.rpm


Resolution

Update the python and python-libs packages to the latest version.
Download python-libs-2.6.6-36.el6.x86_64.rpm and python-2.6.6-36.el6.x86_64.rpm on the client system (from RHN/Satellite) and then execute the below mentioned command to install these packages on your system:

# yum install python-libs-2.6.6-36.el6.x86_64.rpm python-2.6.6-36.el6.x86_64.rpm

How do I apply package updates from the Red Hat Network?

Prerequisite: registration

Systems must be registered before updates from RHN can be applied.

Red Hat Enterprise Linux 5 and later

Before installing an update, make sure all previously released errata relevant to the system have been applied.

To access updates when using Red Hat Enterprise Linux 5, launch the graphical update tool through Applications -> System Tools -> Software Updater, or from the command line via the following command:

# pup


To access updates when using Red Hat Enterprise Linux 6, launch the graphical update tool through System -> Administration -> Software Update, or from the command line via the following command:

# gpk-update-viewer


For a command line interface, use the following command to update the operating system:

# yum update


To install a specific package, such as vsftpd, use the following command:

# yum install vsftpd



To update a specific package, such as bind, use the following command:

# yum update bind

How can I access Red Hat Network via an HTTP proxy?

Red Hat Enterprise Linux 3, 4 , 5 and 6 all use the rhn_register command when registering the machine with RHN or RHN Satellite.

1) Open /etc/sysconfig/rhn/up2date for editing

2) Change the following:

   enableProxy=0

   To the following:

   enableProxy=1


3) If proxy authentication is required, set enableProxyAuth to 1:

   enableProxyAuth=1

4) Enter the user's password (if required) for the http proxy where it states the following:

   proxyPassword=

5) Enter the user's username (if required) for the http proxy where it states the following:

   proxyUser=

6) Enter the URL for the proxy server, in host:port format, in the following line:

   httpProxy=

7) Save the file.

create a volume group

mkvg -y datavg hdisk3

route command for windows

route add 10.0.9.0 mask 255.255.255.0 gateway 192.168.98.1 -p


10.0.9.0 is IP range of destination network

192.168.98.1 is default gateway of source network

Increasing the size of a LUN

You can increase the size of your thinly provisioned or space-reserved LUNs with the lun resize command.

About this task

If the configured size of a LUN is filled and you cannot write additional blocks to that LUN, you can increase the size of the LUN with the lun resize command, provided your volume contains enough space. For example, if you configure the size of a LUN to be 50 GB and all 50 GB of that LUN is filled with data, you can use the lun resize command to increase the size of your LUN provided the volume has available space.

You do not have to take your LUN offline to increase the size of that LUN. When you increase the size of your LUN, Data ONTAP automatically notifies the initiator that the LUN size has increased.

You can grow a LUN to approximately 10 times its original size. For example, if you create a 100 GB LUN, you can grow that LUN to approximately 1,000 GB. However, you cannot exceed 16 TB, which is the approximate maximum LUN size limit.

Use the lun resize command to increase the size of your LUN.

Example

lun resize /vol/italy/venice +10g

Above command will increase lun size of  venice lun  by 10GB.

lun resize /vol/italy/venice -10g

Above command will decrease lun size of venice lun by 10GB.

create thin provisioned lun

Command to create a thin provisioned lun in NetApp

lun create -s size -t type -o noreserve /vol/path

Example

lun create -s 40g -t windows -o noreserve /vol/italy/venice

Above command will create a 40GB thin provision lun of type Windows.

-o noreserve is the parameter which tells NetApp to create a thin provisioned lun.

luns mapped to a initiator group

Below is the command used to find out luns mapped to a initiator group

lun show -v -g initiatorgroup

Example

lun show -v -g italy_ig

Clone existing lun

Below is the command to clone a single lun with in the volume,

clone start /vol/italy/MASTER_W2K8ENT /vol/italy/venice_os

this command will be usefull when you have a master OS lun and want to create copies of OS lun.

Add wwns to existing initiator group

igroup add initiatorgroup wwn

Example

igroup add Server8 10:01:39:54:00:40:E2:02